Is it possible to upload a new OS to a CR1000 without a direct serial connection? In my case, I'm communicating with the datalogger using LoggerNet over TCP/IP. The datalogger has a NL115 device.
Yes, take a look at this tutorial for more details.
There is also an article in a recent Update:
* Last updated by: Janet on 4/28/2010 @ 11:09 AM *
Thank you, Janet. I uploaded the new OS, but now I can't remotely connect to the CR1000. I'm guessing it's because I had assigned the CR1000 a static IP address, which might have been wiped out when I sent the new OS. Do you think that's what happened? If so, do I have to go over to the site to direct connect and fix the TCP/IP settings?
Is there anything I could do to keep this from happening again next time? I read the article about the default.cr1 file option, but I don't understand what I'm supposed to put in that file.
That is probably what happened, the IP address got reset in addition to other settings. Did you have a PakBus address set in the CR1000? If so, it may have been reset to 1. An easy thing to try is setup a new IP connection in LoggerNet with a CR1000 PB address 1 and see if you can connect.
The default.cr1 program is designed to retain any critical communications settings. In your case it may look something like this:
Public Batt_volt, counter As Long
counter = counter + 1
Post again if you have other questions.
I would like to remotely update the operating system on a CR1000 running OS 29 to the current version 32.05. I'm worried about losing the remote link. I've a Raven modem on the switched 12 vdc port and using the RS232 port configured as PPP. I've put together the short default.cr1 file below. I've tested the program and it seems to work as expected, switching the PPP setting to RS232 and turning the switched 12vdc port to on. Suggestions/comments would be great. Thanks
BeginProg SetStatus ("pppinterface",1) Scan (1,Sec,0,0) SW12 (1) NextScan EndProg
To increase chances of maintaining settings, I believe Campbell recommends sending OS via the "File Control" button in the "Connect" screen. Note you'll have to select the "*.obj" file type (after pressing "Send") because the default is for the software to look for only datalogger program files.
I haven't had trouble losing settings for several years now when doing it this way, including loggers CR6, CR800, CR1000, CR1000x, and CR300. Some of my loggers are thousands of miles away, so it is scary but I've developed much confidence due to many successes.
The default program mentioned by @GeodeNZ is a good idea just in case you lose the program and your modem operates on SW12. I believe you can also add a command to the default program to change the pakbus address. Otherwise try PB=1 if you can't connect after sending new OS.
Also, note that sending a new OS to a logger that uses a modem connected to SW12 will power cycle the modem, so you'll lose connection and will have to wait a couple minutes for the modem to reconnect to the network before you reconnect to the logger.
I used file control for sending the OS and the logger settings were retained. Pretty slick, thanks!