Hello there!
I am working on 2 different CR1000's (with same computer). I am preparing to upgrade the OS on both. I have successfully connecte to one of them and backed it up.
The second I cannot connect to with the Device Configuration Utility (version 2.13), but I can connect via the Connect screen.
I get the following when attempting to connect to the CR1000 with Device Configuration Utility:
-------------
Could not locate PakBus devices
15:58:48.229
Fault
"PakBus framing error","Invalid low level signature"
15:59:02.963
Fault
"PakBus framing error","Invalid low level signature"
---------------
I am using a USB to serial adapter with Windows 10 and Loggernet 4.4.2 As I mentioned before, with the same setup I have no trouble connecting to a different CR1000.
Any ideas about what to do next to get it to connect?
Below is status on the CR1000 in question:
Status Summary
11/30/16 3:54:41 PM
RecNum: 65
TimeStamp: 10/24/34 5:37:16 PM
OSVersion: CR1000.Std.17
OSDate: 090604
OSSignature: 23,663
SerialNumber: 28978
RevBoard: 017.008
StationName: 28978
PakBusAddress: 1
ProgName:
StartTime: 10/24/34 4:54:14 PM
RunSignature: 43,690
ProgSignature: 0
Battery: 16.46667
PanelTemp: 19.67785
WatchdogErrors: 0
LithiumBattery: 0.8262816
Low12VCount: 0
Low5VCount: 0
CompileResults: No Program
StartUpCode: 0
ProgErrors: 1
VarOutOfBound: 0
SkippedScan: 0
SkippedSystemScan: 0
ErrorCalib: 0
MemorySize: 4,194,304
MemoryFree: 3,857,196
CPUDriveFree: 491,520
USRDriveFree: 0
CommsMemFree(1): 14,015,014
CommsMemFree(2): 304
FullMemReset: 0
CardStatus: No Card Present.
CardBytesFree: -1
MeasureOps: 43
MeasureTime: 0
ProcessTime: 0
MaxProcTime: 0
BuffDepth: 0
MaxBuffDepth: 0
LastSystemScan: 10/24/34 5:37:16 PM
SystemProcTime: 4,042
MaxSystemProcTime: 27,170
PortStatus(1): false
PortStatus(2): false
PortStatus(3): true
PortStatus(4): true
PortStatus(5): true
PortStatus(6): true
PortStatus(7): true
PortStatus(8): true
PortConfig(1): Input
PortConfig(2): Input
PortConfig(3): TX
PortConfig(4): RX
PortConfig(5): TX
PortConfig(6): RX
PortConfig(7): TX
PortConfig(8): RX
SW12Volts: false
Security(1): 0
Security(2): 0
Security(3): 0
RS232Power: false
RS232Handshaking: 0
RS232Timeout: 0
CommActiveRS232: true
CommActiveME: false
CommActiveCOM310: false
CommActiveSDC7: false
CommActiveSDC8: false
CommActiveCOM320: false
CommActiveSDC10: false
CommActiveSDC11: false
CommActiveCOM1: false
CommActiveCOM2: false
CommActiveCOM3: false
CommActiveCOM4: false
CommConfigRS232: 4
CommConfigME: 4
CommConfigCOM310: 4
CommConfigSDC7: 4
CommConfigSDC8: 4
CommConfigCOM320: 0
CommConfigSDC10: 4
CommConfigSDC11: 4
CommConfigCOM1: 0
CommConfigCOM2: 4
CommConfigCOM3: 4
CommConfigCOM4: 4
BaudrateRS232: 115,200
BaudrateME: 9,600
BaudrateSDC: 115,200
BaudrateCOM1: 0
BaudrateCOM2: 9,600
BaudrateCOM3: 9,600
BaudrateCOM4: 4,800
IsRouter: false
PakBusNodes: 50
CentralRouters(1): 0
CentralRouters(2): 0
CentralRouters(3): 0
CentralRouters(4): 0
CentralRouters(5): 0
CentralRouters(6): 0
CentralRouters(7): 0
CentralRouters(8): 0
BeaconRS232: 0
BeaconME: 0
BeaconSDC7: 0
BeaconSDC8: 0
BeaconSDC10: 0
BeaconSDC11: 0
BeaconCOM1: 0
BeaconCOM2: 0
BeaconCOM3: 0
BeaconCOM4: 0
VerifyRS232: 0
VerifyME: 0
VerifySDC7: 0
VerifySDC8: 0
VerifySDC10: 0
VerifySDC11: 0
VerifyCOM1: 0
VerifyCOM2: 0
VerifyCOM3: 0
VerifyCOM4: 0
MaxPacketSize: 1,000
USRDriveSize: 0
IPInfo: ppp ip: 0.0.0.0 ppp mask: 255.0.0.0 ppp gw: 0.0.0.0
IPGateway: 0.0.0.0
TCPPort: 6,785
pppInterface: 1
pppIPAddr: 0.0.0.0
pppUsername:
pppPassword:
pppDial: PPP
pppDialResponse: CONNECT
IPTrace: 0
Messages:
CalGain(1): 0
CalGain(2): -0.6734008
CalGain(3): 0
CalGain(4): 0
CalGain(5): 0
CalGain(6): 0
CalGain(7): 0
CalGain(8): 0
CalGain(9): 0
CalGain(10): 0
CalGain(11): 0
CalGain(12): 0
CalGain(13): 0
CalGain(14): 0
CalGain(15): 0
CalGain(16): 0
CalGain(17): 0
CalGain(18): 0
CalSeOffset(1): 0
CalSeOffset(2): 6
CalSeOffset(3): 0
CalSeOffset(4): 0
CalSeOffset(5): 0
CalSeOffset(6): 0
CalSeOffset(7): 0
CalSeOffset(8): 0
CalSeOffset(9): 0
CalSeOffset(10): 0
CalSeOffset(11): 0
CalSeOffset(12): 0
CalSeOffset(13): 0
CalSeOffset(14): 0
CalSeOffset(15): 0
CalSeOffset(16): 0
CalSeOffset(17): 0
CalSeOffset(18): 0
CalDiffOffset(1): 0
CalDiffOffset(2): 0
CalDiffOffset(3): 0
CalDiffOffset(4): 0
CalDiffOffset(5): 0
CalDiffOffset(6): 0
CalDiffOffset(7): 0
CalDiffOffset(8): 0
CalDiffOffset(9): 0
CalDiffOffset(10): 0
CalDiffOffset(11): 0
CalDiffOffset(12): 0
CalDiffOffset(13): 0
CalDiffOffset(14): 0
CalDiffOffset(15): 0
CalDiffOffset(16): 0
CalDiffOffset(17): 0
CalDiffOffset(18): 0
Nevermind. I just noticed the baud rate for RS232 was set to 115,200 when I read my post. Hopefully my silly mistake will help someonelse :)
No question is silly, glad you got it figured out.
It looks like the CR1000 lithium battery needs to be replaced. See the CR1000 manual section 9.2 for replacement instructions. You'll want to do that before sending it back to work.
Here's an article with more information on the importance of having a good internal battery: https://www.campbellsci.com/blog/datalogger-spare-tire-lithium-battery
Thank you for the links Janet!
We have three CR1000's in all. I am in process of backup, OS upgrade and battery replacement prior to use and redeployment. Likely to have a few more 'silly' questions along the way. I appreciate the quick response on the boards.
Dear All,
I have a same problem. lithium battery was low.
I change it with new lithium battery 3.6v, which made in China. I bought it from our market.
Then I try to send last OS to the data logger CR1000, which i downloaded from Campbell Scientfic site, I have lost connection with logger.
But i remeber before, i could establish connection with logger after replacing the battery. Even I click bucup batton and finished successfully. My next step must be switch off logger, then switch on during the send OS to logger. At this moment i have lost connection with RS232.
May be it is not quality and low battery.
may be, it is main reason.
best regards