Hello gentlemen,

Has anyone in their years of work with CSI products seen an error message: " SHAFT PROBE NOT ENABLED ON CAL. VALUES NOT SET, PRESS RESET TO CONTINUE "

This is a new database for permanent wiring on converting lines. I have looked and looked at what mistake I made, ran dbfix, look at measurement pts, over and over and I cant find anything about the setup that shouldnt work.

The kicker is.. It will not collect route data, without giving me this error message, but I can go into analyze and acquire data on that same pt. That made me think of something in my route creation was wrong, so I deleted my routes, and recreated them, I have extracted the databases out into new names and tried to run. Same error message.

I am STUMPED!!

Thanks,
Mike

Shaft probe was the magic shotgun muzzle cleaner that was used to measure shaft voltage/current with. Can you by mistake somewhere tricked the thingy to belive it has that device connected and not a accel? Then it will not find the shaft thingy and be sad..... There was some special setup for that shaft probe so look at the measurement setup in the database and check that it´s set for normal accel and all the other settings. Olov

Thanks Oli

I have looked and looked, it is setup as I always do. Acc > Vel , assigned AP set by Orders, LOR, Avgs

I just cant see it .... it has to be about to slap me in the face!!

What have you gotten for values on this page?

Here it is Ralph,
Thanks for taking a look.
I see you have begun using integration and overall override, Is this something you found useful?

Mike,

Are these just regular accelerameters or what are they? Is it setup sort of like the DS of the big machine?

The above setup is from a client and I have not actually gotten to check why CSI originally set this up this way.

quote:

" SHAFT PROBE NOT ENABLED ON CAL. VALUES NOT SET, PRESS RESET TO CONTINUE "

Is this the message you see or is the word "ON" actually "OR". With "NOT ENABLED ON CAL. VALUES NOT SET" sort of does not sound right. But then again a lot of things I see in the new version don't sound right either.

Typo Ralph, thanks for catching that.

Correct wording is.
SHAFT PROBE NOT ENABLED OR CAL. VALUES NOT SET. PRESS RESET TO CONTINUE

This is version 4.9 not 5.1 btw.

This is occuring with my handheld pole, cable and accelermeter that works on all other databases.Eventually I will be connecting to a switch box.

I also went into data statistics options, and reset to last 12 just in case something about that was screwy.

I have never had this problem, went thru the same steps I always do in created or editing databases, and I just cant find whats wrong.

The weird part !!!! Is I can go into analyze and acquire data, I just cant collect the route data without this error message

This message has been edited. Last edited by: MikeH,

Now that is strange. Huh?

This meassge sounds like it is expecting somethng that is not there when it reads the measurement point definition, doesn't it.

Did you build this through Wizard or like we always did?

Can you extract out one of the machines and send me and maybe I can see what is wrong. Two heads are always better than one when trying to solve something. Might be plain as day to someone else. But like you, I have never ran across this error.

ralph_stewart@alertanalytical.com

I used wizard to just go as far as getting the file structure the way we do.

databasename\databasename to create the .rbm file.

you then get the message that none exist and do you want to create it, YES.. and then I add the databasename.mdb file

I am thinking that may be it, that I should have setup the database from the getgo from dbutly... but I know I have done it before as I mentioned above.. that just gets the file structure like we use, I never hit execute or build.
Then I go in dbase and add pts... I am really confused here..

I will see if I can get it small enough... its hard to get anything to go out on email anymore.

Thanks for your help
Mike

Are you sure your units type code is set to Vel>>Acc and not to Shaft current? The route point is looking for the current probe and I can't think of anywhere else you would make that setting. Which data collector are you using?

Also, your full scale range is set to 0.1, is that where you set it? I don't think this has anything to do with your error message I'm just curious if you intentionally set it that low.

Hey Joe, thanks for the advice

Yes.. Acc > Vel and Acc > Acc for peakvue

Yes.. .10 is what I have been using for 12 yrs.

Thanks,

I am thinking I will have to start completely over.

Mike

quote:

I HAVE FOUND THE PROBLEM, NOW IF I CAN FIND WHAT I AM DOING WRONG.

I deleted all my AP SETS for this database, then the generic sets by CSI showed back up.

I then got on GENERAL SET and created new sets numbered 1, 99, 100, 101, 102, 103.

All the same set but with numbers to coincide with the measurement pts ap set assignments.

Now when I load the... (more)

Can't find your post, only what was in the email when you posted. What is after the "more"?
I am thinking maybe one of the might have been set something like this. Was it or what?

I thought I had it but didnt.. started over from scratch.. stills same issue

very small dbase attached.. thanks for your help.

Mike

CMAG2.rbm (134 Kb, 9 downloads)

Mike,

Have you tried it without the "fullband" parameter? The instructions say it goes with a shaft probe. Is this the problem? Never used it but worth a try to change it.

yes... that was it.

vHFD set to 20khz works.. didnt realize FULLBAND was shaft probe...

alllllllllll dayyyyyyyyyy.... and yet sooooooo simple or me sooooooo stupid.

Thanks

Maybe this will help someone else

Mike

vHFD

Mike,

I loaded the route you had set up into my 2130 and when I tried to collect data I got an error saying basically that no sensor bias voltage was detected. I went back and ungrouped the first two measurement points and I was able to collect data without a problem. I don't use grouping so I'm not sure how this affects things but it seems like the problem lies in this area. Maybe this info will help.

When I posted this I saw that you and Ralph found the problem. Take Care.

Thanks Joe..
Itwas the FULLBAND setting.. didnt read the instructions.. Thankfully Ralph did !!!

Kinda confusing .. maybe CSI should put a note in the drop down about that... for those of us who DONT read INSTRUCTIONS!!!

Mike,

Thanks for posting this. And thanks to Ralph for the diligence in tracking it down. It's these little bits of info that can save a person's sanity. And it is what makes this board so fabulous.