When using a Datapack 1500 sometimes I find the need to take readings at different setting than what are put into the database. My practice is to go into off-route data, select spectrum or waveform data, make my settings and hit store.

The collector then averages and I have to enter a command that tells it to stop and store the data (sorry, but I don't have it handy to check this step exactly). I never get a prompt telling me where to store it and the help file in the Datapack tells me that it will be stored with the current route point.

When I download it to Odyssey I find the data store separately from the point I intended. It is stored in the second level of the heirarchy which would be the area level in RBMware, but I'm not sure about Odyssey. It only contains the point description and no machine name so I can't tell what machine it belongs to. It is not stored in the unscheduled heading, but at the same level.

Any suggestions?

Thanks,

This message has been edited. Last edited by: Danny Harvey,

In the load/unload screen in Odyssey, unload options, select "Unscheduled data smart mode" this will put the off route data in the measurement pane of your machine location as an offroute data point. It will have a code for the measurement parameters such as 499APF011. If you don't want to do this and keep the data in the Off Route Data hierarchy then all you have to do is hit "edit point" after you collect the data in the dataPAC and change one of the names to help you locate it later. I use the POSITION field usually.

Ron,

Thanks, but I already checked that and it is set as you recommend.

I'll use the edit point method until I can firgure out what is wrong.

Any ideas on how I can figure out where the data I have belongs?

Thanks,

Danny

Danny, I have 3 levels in my hierarchy. So, I also have 3 levels in Unscheduled. I have UNSCHEDULED/OFF ROUTE DATA/STORE. This causes the LOCATION ID of the point where you collected the off route data to be copied into the location pane of the UNSCHEDULED train. The only time it is a problem is when the location ID of two different machines is the same. If that happens I check the date to get the right data or like I said, adjust the point context slightly. I also will make notes when I collect off route to help me find it later.