With my being "brought up" using the old DOS version of CSI and having to adapt to the MTwin and then RBM version of CSI, I have never used the "new" program RBMwizard enough to actually know what it does with the machines and their configurations it creates.

I had to "extract" out some machines and put them in another database, both (databases)were built by the wizard, and now the wizard fault frequencies are not there, even though I chose to copy the "configuration" data also. Have chosen to use "all sources" in globals, still not there.

Wonder why the wizard does not put them (fault frequencies) in the measurement point definitions like a live person does?

Any one know where I can find these lost fault frequencies and retrieve them? Or am I going to have to manually enter them through the measurement point definitions, which is not to bad a job, but would be nice if wizard would turn them loose and let me have them back.

I searched CSI papers but all I really saw was how to setup a "consultant friendly" configuration, but that seems to be too late right now.

Any help will be greatly appreciated.

http://www.compsys.com/drknow/pubtnot.nsf/9f0e142090062.../Zipper%20Manual.doc

Ralph,

Did you assign the measurement points to each shaft on the configurations (click the little box on the lower left of the page with the configuration showing). I had some that didn't show up in plotting and was going through the configuration to try to see why and found the points were not assigned to the shafts. After I did this everything worked ok.

Jim,

These machines were working before pulling them out of the database and inserting them in a different database.
When they got into the other database, they do not have the assigned fault frequencies that RBMwizard assigned.

Ralph,

Jim is correct, you will need to assign the points to the shafts. If you click Edit Measurement Points under the Configuration Tab you can see if you have any that are unassigned.
Good Luck

Jim and Good Vibes,

I must not be understanding what you are saying.

Are you talking about when the "shafts" and faults are being built or after I have "extracted" the machines out of one database (the original one) and have these "machines" in the new database? I am not at the computer where the problem is so I can't try what you suggested until I return to the customer's site.

I will ask an additional question along ther same line,,,,,,,,,,,.......
What if I need to "adjust" the faults built when using the wizard to build the machine, how do I get to them? Might be an elementary question, but..........

I am the first to admit, I do not use the wizard and am at a lose as to what is going on with the lose of the faults in the extraction procedure.

Where is CSI when one needs them?

Where is Bill K?

Ralph,

First of all make sure you are set up tp display faults from the configured machine. When on Spectral Display screen click "Globals" then click on "Analysis Options" Make sure you have "combine all sources on the fault frequency source line.

If this has the proper selection open the wizard program, select the machine that doesn't display the fault frequencies and click "configure". The machine should be displayed in the configuration window. A little button on the lower left is "edit mp", click it. When the next window opens click "assign", expand both sides of the window and if the "shafts" on the left side doesn't have points under them, drag the points from the right side to the correct shaft. When this is done click close this window then click close and save at the top right of the next window. This should let the fault frequencies be displayed when the data is plotted.

No "MP" click area.

Does this mean it has lost all of the original configuration that was in the original database where wizard set it up?

This message has been edited. Last edited by: Ralph Stewart,

When you go to the wizard and click on the machine and click configure does a machine configuration screen come up with a machine in it?

Jim,

This is what I see.

What I did was use the DButly program and copy some machines from the original database to a different database. The database I copied from still has the RBMWIZARD faults working. The database where I copied to, does not have them working now.
I had the "transfer equipment configuration" checked to transfer the conf.

Ralph,

I have never tried what you have done. Have you tried selecting User Warehouse on the screen you showed to see if the configurations are in that file. Try selecting User Warehouse and Existing Configuration and see if anything is there.

They are not there Jim.

I think they were lost in the transfer through DButly from one database to the other.

Ralph,

Have you tried clicking on the recalculate speeds button in the configure mp's part of Wizard?

I may be wrong, but if built in wizard, that info doesnt change unless you rebuild in wizard.

I think why the datbase you copied doesnt have the info, is whats built in wizard wont copy from dbase, to get wizard info you build in wizard and edit in wizard...

I think.. not sure... you may can go into wizard, and use the dbase to build another dbase in wizard... then copy and edit in wizard...

its too confusing, but from classes, whats built in wizard has to be edited in wizard...

if you made changes to a dbase built in wizard, then edited in dbase... but later added machines in wizard and click build again.. it will overwrite the editing you did in dbase..

am I making sense... I think I am confusing myself.

I am sure you are close to correct Mike.

I never use wizard. The customer has been using it and we are trying to change some machines from one database to another, I do not believe it works.

OK.

All is not lost.

I want to thank all you guys who tried to help me on this.

After getting caught up a little and having an hour or two to sit down and examine the sitution without the hassle of the world biting at my a--, The path to the solution of this "problem" is quite easy to handle. It just takes a little pushing and shoving is a few non linear directions to munipulate things that are not really a funtional part of the program. Maybe I should say, not listed on the instruction sheet.

The old saying "when all else fails, read the directions" did not work on this.