<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Activity for elee123</title><link href="https://forge.codesys.com/u/elee123/activity/" rel="alternate"/><id>https://forge.codesys.com/u/elee123/activity/</id><updated>2022-02-04T22:16:20.229000Z</updated><subtitle>Recent activity for elee123</subtitle><entry><title>elee123 posted a comment on discussion Engineering 🇬🇧</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/815a136787/?limit=25#79fe" rel="alternate"/><published>2022-02-04T22:16:20.229000Z</published><updated>2022-02-04T22:16:20.229000Z</updated><author><name>elee123</name><uri>https://forge.codesys.com/u/elee123/profile/</uri></author><id>https://forge.codesys.com/forge/talk/Engineering/thread/815a136787/?limit=25#79fe</id><summary type="html">Hi all, I am hoping you will be able to advise on why I have lost the connection via codesys to my eaton XC303 PLC. I was connected and monitoring values and then I was updating an HMI that uses the codesys protocol to integrate tags. When I downloaded the new HMI project I lost the connection to the PLC. Eaton support answer is to power cycle the PLC, however this is a remote system and don't have a means to do so. Is there anything remotely I can get to try to restore this connection, without a...</summary></entry><entry><title>elee123 posted a comment on discussion Engineering 🇬🇧</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/c10a59cc78/?limit=25#4fd2" rel="alternate"/><published>2021-06-25T14:01:11.071000Z</published><updated>2021-06-25T14:01:11.071000Z</updated><author><name>elee123</name><uri>https://forge.codesys.com/u/elee123/profile/</uri></author><id>https://forge.codesys.com/forge/talk/Engineering/thread/c10a59cc78/?limit=25#4fd2</id><summary type="html">Using codesys v3 and have been using the Oscat DLOG CSV utility for some time now with success. However, recently I have noticed that it is no longer working and I get errors 2, 4 &amp; 5 in ERROR_C indicating SysFileClose, SysFileWrite and SysFileSetPos Errors. If I just change the file name on the current DLOG then it works again. Old File name e.g. - #A_#D_#H_log New File name - #D_#H_log Why is it ok when I take out the date placeholders? Is there a bug there? The only resolution is to restart and...</summary></entry></feed>