Our full technical support staff does not monitor this forum. If you need assistance from a member of our staff, please submit your question from the Ask a Question page.


Log in or register to post/reply in the forum.

Problem with AM16/32 and CR1000


edgage May 3, 2011 03:11 PM

Hi all,
I'm having big issues with a setup involving differential voltage measurements on an AM16/32 connected to a CR1000. The data are junk - lots of NANs and otherwise nonsensical output, from all sensors connected to the MUX. I've tried different iterations of the program, gone through the wiring bunches of times, all to no avail. The setup is identical to 4 other sites as far as the hardware, sensors, and programs; no other sites have given me the same problems. One potentially telling "symptom" is that the switching on the MUS is all stuttered. Unlike my other functioning, which have a nice regular pace to the switching, the bad set up has a very irregular rhythm to the clicks associated with the switching. At this stage, I'm thinking some hardware issue may be at fault, but would it be at the CR1000 end (clock? but it is synched with my PC) or the MUX? Not sure what to do next. I'd swap out other units to do a process of elimination, but this would take hours of unconnecting/connecting plus data loss at other sites. What should I do next?
THANKS!!!


Dana May 3, 2011 04:30 PM

First thing to check is to make sure the device is properly grounded (refer to the product manual).

The next thing to check would be the battery voltage. The AM16/32 requires a higher operating voltage than the CR1000. The specs are 11.3 V for –55C to +40C and 11.8 VDC for +40C to +85C, where the datalogger will operate down to approx. 9.6V Also, the relay actuation time is a function of temperature and battery voltage (refer to the product manual).

If neither of these resolves the issue, you'll want to contact your CSI office directly so they can ask more thorough questions.

Dana W.

Log in or register to post/reply in the forum.