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.

CR1000 OS update sending problem


graywacke Nov 21, 2012 01:22 AM

I trying to update the OS of our CR1000 logger from OS 22 to OS 25 using and following the instruction in the device config but during the OS sending time, the message below prompted me:

Dialog Box "OS Send Failed":
Invalid fragment signature received. The whole operating system could not be send. The device will probably not reboot after this. In order to recover, the operating system must be resent.


After that failure in sending the OS, I CANT CONNECT ANYMORE TO THE LOGGER even thru the RS232 or CS I/O.

Please help me to resolve this problem. Thanks....


Sam Nov 22, 2012 05:41 PM

Are you using a USB to serial cable? If so, I have seen this reported many times by customers.
Try lowering the baud rate on the connection, say 9600, and resend the OS again using Device Configuration Utility through the RS-232 port.


jtrauntvein Nov 24, 2012 07:00 AM

When you send an operating system to the data logger using the boot mode protocol. One of the first things that the data logger does is to erase flash memory where the operating system image is stored. If the process is interrupted after this, only the boot loader is left. This is the reason why you can no longer communicate with the datalogger.

That said, since the data logger boot loader is still working, you can try to send the operating system again using devconfig. The advice given above regarding a reduction of baud rate is, unfortunately, unworkable since the data logger boot loader will accept only 115200 baud. You may be able to ensure success of the operation by closing all applications but devconfig.

I recently found a vulnerability in devconfig's low level serial code where, if characters are received before a call to WaitCommsEvent(), that data will not trigger a read unless further data is received, The datalogger's boot mode protocol is unfortunately vulnerable to this. If your problems persist, I can send you a pre-release copy of devconfig that may well address this problem. If needed, send me an email at Jon at campbellsci dot com.

* Last updated by: jtrauntvein on 11/24/2012 @ 7:01 AM *


mkvakic May 28, 2014 12:38 AM

Hello everyone,

This is and older post, but i didn't want to open a new thread.

The problem is the same.
I've tried replacing the operating system to the 27 one with the latest dev config tool.

It is connected through a usb-rs232 cable.
I've tried changing the baud rates and input voltages but to no avail.

Is there anything else i could try?
Thank you very much.

Kind regards,
Marko


EarlyBird May 28, 2014 01:07 AM

Marko,

Does DevConfig connect to the logger? If not then it is probably the USB-RS232 adapter, this is a common problem. I have tried and failed with a variety of adapters but found one that works and I keep it safe, I have had it for ten years now.

Campbells sell an adapter that works with their loggers.


mkvakic May 28, 2014 02:38 AM

Dear Bird,

Yes, the sending of the OS starts but always finishes at a certain point (irregular).
I've tried connecting it to battery aswell.
Really not sure what the problem is...

What is the usb/rs232 cable brand?
Is it maybe Pro***fic?

Thanks,
Marko


EarlyBird May 28, 2014 02:44 AM

As it connects the cable is good and the settings are correct.

I would contact Campbells and ask for advise.


aps May 28, 2014 04:12 AM

When you send an OS to the logger via the Send OS screen of the Device configuration program it is always sent at 115200 baud. We have found quite a few serial USB interfaces that whilst they will initially connect to the logger cannot send data reliably at full speed to the logger.

Apart from trying another cable, you could check on the Prolific Website for any driver updates for your cable (Prolific ones are not normally updated by Windows updates) as they have had various updates to improve reliability of connection - this won't help with low grade manufacture though.

You could also try loading the operating system into the logger by sending it by a different route, with a lower connection speed. To do this connect to the logger at a lower baud rate and then use the option to send a program but browse to the OS OBJ file instead of a program. (This will not work now with early loggers which only had 2MB of memory)

* Last updated by: aps on 5/28/2014 @ 4:13 AM *


mkvakic May 28, 2014 08:15 AM

Hello all,

The problem was solved using a different cable.

Thank you for the quick answers.
Cheers,
Marko


EarlyBird May 28, 2014 12:07 PM

Problem solved is good news. USB to RS232 problem again!

You are welcome.


Schiedeck Feb 22, 2019 10:48 AM

I need urgent HEEELLLLLPPPPP.

I need this same problem with CR800. The old version was CR800.Std.28.02 to new version CR800.Std.32.03.

I checked the serial USB interface and updated driver profilic. It´s ok.

But always the same "OS Send Failed - Invalid fragment signature received. The whole operating system could not be send. The device will probably not reboot after this. In order to recover, the operating system must be re-sent".

The failure occurs at different "fragments".....

I don´t know what to do anymore.

Please HELP ME


flaviomagina Nov 10, 2019 05:39 PM

I have the same problem with CR1000 OS update: "OS Send Failed - Invalid fragment signature received. The whole operating system could not be send. The device will probably not reboot after this. In order to recover, the operating system must be re-sent".

Now, I can not perform communication by RS232 cable and the datalogger become not acessible.

Please Help me Campbell !

Thanks

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