We have a number of sites which are connected to the AX supervisor by GPRS wireless modems, so the connection can not remain active all the time due to data costs and looking for the best practice in this situation.

I have installed the nHaystack service on the supervisor and can see local HistroySpace via skyspark builder, so any history points coming back to the supervisor are available for me to work with.

However am I right in thinking that as I am using the histories in the supervisor (which are exported from the station each night for control sensor readings) and not having nHaystack on the remote station, I am going to lose out on automatically mapping ControlPoints and Histories together so that only one Haystack rec is generated?

Any suggestion on best practice in this setup to minimise wireless data usage?

Thanks for your help.

Richard (Newbie)

I think you are saying that you have a supervisor that has imported ControlPoints, and imported Histories for those points as well?

If that is the case, then NHaystack can handle this automatically for you. It can figure out when an imported ControlPoint and an imported History really belong to the same point down on the jace. It will then only generate one Haystack rec.

So you should not have to install nhaystack on the remote stations. Give it a try, it should work just fine. Let me know if you have any problems.