El005 fails to program

Guest · Post by **Guest** » Tue Jun 17, 2008 1:22 pm

Hi,

After being able to program an EL005 (connected to a EL040 current monitor) correctly, it now fails when I try to updated the configuration.

After clicking 'Program' in the configuration control panel, I get the following sequence of messages:

Halt samping
- 0-

Erase configuration
- 0 -

Rewrite configuration
- 0 -

Restarting...
- 0 -

Updating time...
- 0 -

Updating time...
Operation failed

The red LED on the EL005 flashes quickly and continously. The LED on the EL040 doesn't flash at all.

Any suggestions about what might be going wrong?

ziko · Post by **ziko** » Tue Jun 24, 2008 2:52 pm

Hi what version of the software are you using?

Kind regards

Guest · Post by **Guest** » Sat Jul 05, 2008 7:26 pm

Software version is R5.20.0 - 32 bit

picojohn · Post by **picojohn** » Mon Jul 07, 2008 11:34 am

Hello guest,

Please refer to the following forum link: http://www.picotech.com/support/viewtopic.php?t=4038

Regards
John

Guest · Post by **Guest** » Tue Jul 08, 2008 8:38 pm

Thanks for the prompt reply.

I've run the logloader routine on port com1, and that reported result=success once completed.

I then ran the enviromon r5.20.0, and things seem to have got worse. Whereas before the logload had been run, I could connect through port com1 ok, but unable to proceed beyond updating time ... operation failed, I now get an instant report of Warning, logger not found port com1.

If I attempt to connect with the logger e.g. through change converter address, it reports .... Get Logger Version - Operation failed.

Is it worth regressing the logload back to an earlier version of enviromon? Can you advise how I can recover and regain port com1 access to the logger. note - the connection through com1 was fine during the logload routine. I didn't disconnect the serial lead, but after the successful logload, the logger could no longer be found on com1. Not clear why logload found the logger, but enviromon cannot.

picojohn · Post by **picojohn** » Wed Jul 09, 2008 2:50 pm

Did you reset and re-configure after the logload? If not, please try that.

Regards
John

Guest · Post by **Guest** » Wed Jul 09, 2008 8:03 pm

Hi John

Realised what the serial port problem was. The PC defaults the com port setting to 9600, and I was setting the logger to this baud rate, when in fact I needed to set the PC to the logger default of 57600. Changing the baud rate to 57600 on the PC, conducting a clear, and reconfigure fixed it. Logger now programmed OK, and taking readings.

thanks for your support