I cannot connect the CR3000 with device configuration 2.12
I can connect to the CR3000 using Loggernet.
CR3000 OS 29 --> tried several different loggers
Just calibrated 16 Mar 2016
Windows 7
Using USB to serial cable adaptor into logger rs-232 port
The same set-up WILL connect to the CR1000s OS 29 without a problem.
Error message:
15:52:51.158
Fault
"PakBus framing error","Invalid low level signature"
15:52:51.644
Fault
"PakBus framing error","Invalid low level signature"
15:52:56.17
Fault
"PakBus framing error","Invalid low level signature"
15:52:56.652
Fault
"PakBus framing error","Invalid low level signature"
I do not have a problem connecting to a CR3000 with OS 29 using DevConfig 2.12 with a USB to RS-232 adapter. It sounds like the wrong com port is selected or the baud rate isn't right.
Are you using the same RS-232 cable and com port that you tried with a CR1000 so you know the com port selection is correct? In DevConfig, make sure the correct com port is selected as well as baud rate. It remembers what you used the last time you connected to that type of device, and it may not be correct. It may not match what was selected for the CR1000.
In case the baud rate is not correct, and you don't know what it is, you can select "Unknown" in the device list, Make sure to re-select the com port number in case it's different after doing this. Click on "Identify Datalogger Type" in the section to the right. (Not the Connect button). DevConfig will go through the different baud rates and hopefully connect.
Once connected you can change the CR3000 baud rate for the RS-232 port if you need to.
Framing errors means the packets are being corrupted in transmission. It usually means there is a problem with your serial cable hardware or the USB driver. We recommend using only cables that use FTDI chips.
Here is a blog article about trouble shooting USB to RS232 cables:
https://www.campbellsci.com/blog/usb-rs-232-adapter-cable-issues
As JDavis points out, framing errors can happen because of dropped bytes or improperly synchronised baud rates. This can also happen if your CR3000 program has code that is writing data to the RS-232 port while devconfig is trying to use the same port for PakBus.
Fixed the problem! In short, it was a government firewall/ access problem. Jtrauntvein gave us the clue.
The laptop now needs an administrator logon to run DevCon 2.12 correctly. We are not exactly sure why, but several of our laptops now have this problem.
The upgraded Junos Pulse (now Pulse Secure) combined with the stand alone Devise Configuration 2.12 and CR3000 OS29 tripped some kind of security feature. All the new security upgrades automatically installed when I powered down the laptop. The next time I turned on the laptop, the new settings took affect and interfered with “users” directly access DevCon 2.12 and the CR3000.
For unknown reasons, a direct USB to RS-232 through Logger net, Devise Configuration 2.05, the CR1000s OS29 or CR3000 OS28 was not affected and still works correctly.