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.