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.

unable to collect data from CR10x


AMK Aug 13, 2012 11:28 PM

Hello Forum,
I have a question regarding "collect now" from the loggernet connect screen.
I am connecting via 900Mhz radios that are currently in a lab. I've configured an IP/ethernet base station with multiple remote RS232 900Mhz radios. Each remote radio is connected to a logger via a SC105 adapter.
I can connect wireless to the logger, I can send programs, I can view Num Display, Graphs, and all the associated data in real-time. However, when I press "Collect Now", the Collecting Data pop-up opens, the animation begins, 0%, then a second popop opens and shows a unable to establish a connection with logger, it looks like loggernet disconnects, a short pause, and then loggernet connects again.
Does anyone have any ideas why this may be happening? I have the base station and the remote radio in the same room.
Thanks,
Adam K>

* Last updated by: AMK on 8/13/2012 @ 6:32 PM *


kirving Mar 19, 2013 04:07 AM

I'm seeing the same symptoms using a direct rs232 connection via an SC232B module and a CR10X. I started downloading the data using LoggerNet 4.0 on a laptop, was going fine until the laptop battery died. The logger seems fine, and I suspect the issue is some setting in loggernet in this case.


kirving Mar 19, 2013 10:53 PM

The LoggerNet 'troubleshooting' display showed that the logger was failing to set the data pointer using the 'G' command (or similar), I'm guessing due to problems with the logger memory. The behavior of LoggerNet -- to disconnect, show the 'unable to establish communications' message, and then reconnect -- is not particularly useful, but the issue was probably not with LoggerNet's state as I first thought.

We've seen similar problems before in our fleet of aging CR10X loggers, usually with high memory locations, and the simplest fix is to reset the logger pointers (somehow) to avoid using those locations.

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