*$#@^%!) Odyssey database is corrupt. Instead of 1x's at 3600 it is at 360. Spike Energy is a flat line. I actually can see one month it is good, next month bad and then good again. This has happened on many machines this month and I must get it fixed! Odyssey 2.3 Enpac data collector. Can anyone fix this for me, I am willing to pay, just no Rockwells rate. Thanks in advance..

Mike,

Are you sure this is a database problem? You might try running the "check database" in SQL Talk Interactive program. The instructions should be in you software manual somewhere.

Usually when the Spike Energy is a flat line, the cable or connector is bad (sometimes intermittent). I suggest you check the cable and connectors. Could even be the connector in the Enpac or the associated board.

Good Luck,
John J

Mike,

I agree w/ John. CHeck to ensure you have the "check transducer" box selected. SOunds like connector,cable.

Dave

At first it looks like a cable issue but it is not. I collect an IPS spectrum before spike energy and a plain acceleration spectrum after the spike energy (all with the same button push)and they get data. Whenever the Spike Energy is bad then I know the IPS will be bad, Data is there and the amplitudes look good but instead of 1x's motor at 1785 it is at 178. 2x line is at 720, not 7200. I ran check database and update statistics to no avail.

Let me review the hotfixes for 2.3. What is the last ones you installed??
One of them had soemthing to do with a factor of 10, but don't remember what it was. @.3 was a long time ago.

Dave

Mike, this sounds like a database problem but might be a data collector problem. I've got two Enpacs that both have a "glitch". Ever once in a while I will take some data and find that the spectrum frequencies are 1/2 of what they should be i.e. 30 hz is at 15 hz and so on. Also, when this happens, the spike energy will be 0. If the data collector is in the auto advance mode you will never see it until you down load the data. All it takes to fix it is turning the unit off then back on. Your problem could be a variation on this... as I've said both of my Enpacs will do this, not often, but often enough that I always look close at the first spectrum in a route to make sure it is not happening.

Are you using a Lemo to BNC connector on your Enpac? I've recently found out that the Lemo to BNC connector for the Enpac has a grounding issue that can screw with your data . . . RAEntek recommends straight Lemo to BNC cable, without the adapter.

Jamie, thanks but I am not using a lemo to BNC. Ed, you only have to check the first location in the route? If it is good then I can expect the rest of the route to be OK? What op sys ver on the Enpac are you using? Ed, have you talked to RA Entek about this?

Yes, you only have to check the 1st location in the route, if it is good all the rest of the points will be good. Basically you have to check it every time you turn the unit on. I'm not using a lemo to bnc adapter either. Opsys version is 2.22. I upgraded to the next version opsys but had to go back because the units would not pass calibration check with the latest version. My enpacs have had the problem with every Opsys from 2.0 up, so It is probably a hardware problem not software. I sent one of the units back to Entek, but they could not find a problem. The Enpacs are actually really good boxes, I love the size and the capabilities. But this glitch is annoying....