I have 2 CR200X data loggers that I'm trying to connect to using 9XTend-PKG-R RS-232/485 RF modems. I was able to connect to them and collect data while connected to the serial on my laptop but when I try to connect via RF I keep getting the following errors:
Failure: 1/24/2012 11:01:31.945
Open failed
Failure: 1/24/2012 11:02:04.058
Open failed
Failure: 1/24/2012 13:40:08.777
PakBus framing error","Invalid low level signature
Failure: 1/24/2012 13:40:46.388
PakBus framing error","frame is misquoted
Failure: 1/24/2012 13:40:46.685
PakBus framing error","Invalid low level signature
Failure: 1/24/2012 13:41:15.747
PakBus framing error","Invalid low level signature
Failure: 1/24/2012 16:41:03.880
transaction failure","unreachable destination","check/set clock
Warning: 1/24/2012 16:55:15.562
transaction failure","timed out or resource error","check/set clock
Warning: 1/24/2012 16:55:29.321
transaction failure","timed out or resource error","check/set clock
Failure: 1/24/2012 16:55:43.080
transaction failure","timed out or resource error","check/set clock
Failure: 1/24/2012 11:01:31.945
Open failed
Failure: 1/24/2012 11:02:04.058
Open failed
Also, the sensor that we are using is an SDI-12 type.
The most likely cause of this is a baud rate mismatch between the remote radio and the datalogger. The CR200X requires a baud rate of 9600 BPS, no parity, 8 data bits, and one stop bit. If any of these parameters are incorrect, the packet data will be garbled.
I'm having a similar problem with one of my systems. I have 4 weather stations on a PakBus network and communicating with FreeWave FGR-115RC transceivers. This has been working for years, and the same setup is still working on another site. It seems that this problem started when our collection computer died and was replaced. We reinstalled LoggerNet Admin, but now we keep getting the same errors as reported above. I've tried modifiying the baud rate w/o success, and checked to settings on the transceivers to see if anything had changed. Nothing that I can see. I've been struggling with this for months.
A few days ago, I discovered that if I just reboot the computer, everything works just fine, and data is downloaded from the CR3000 dataloggers, and I can also connect to them to view tables via LoggerNet Admin. This is only good for a few minutes however (maybe 5 minutes) and I'm back to getting the PakBus framing error messages.
I have none of these issues on the collection computer at the other site. The settings are the same as far as I can tell. I mention to our IT people that there must be something different in the Windows 10 OS between the two systems, but they reject that theory.
Any suggestions on how I can troubleshoot this? Right now, my solution is to just reboot until my data download is caught up.
Thanks for any help.