Personal Data

Username:
tim-manning
Joined:
2020-01-17 12:30:49+00:00

Projects

  • No projects to display.

Skills

  • No skills entered.

User Activity

  • Posted a comment on discussion Engineering 🇬🇧 on CODESYS Forge

    It was very painful, however we (me and the other on the project team - didn't want you to think I was referring to myself in the 3rd person) worked around it. And, like you, we all learned to commit early and commit often. One of the thing we did notice was that SVN didn't always like it when we renamed objects like POUs, structures, etc. Refactoring variables didn't seem to cause any issues. So, we got in the habit of creating a copy of the object with the name we wanted, performing a commit, then...

  • Posted a comment on discussion Engineering on CODESYS Forge

    After doing an SVN merge, I had some conflicts. After resolving the conflicts, when I attempt to commit the project to the repository, I get the message 'The object GUID nnnnnnnn-nnnn-nnnn-nnnn-nnnnnnnnnnnn' is not valid' Clicking OK closes the window. Does anyone know how to resolve this issue? Using the equivalent of Codesys 3.5 SP15 Patch 5, with SVN add on 4.2.5.0

  • Posted a comment on discussion Visualization on CODESYS Forge

    I have to believe that someone has already figured this out, but I am a little bit stumped. I am using WebVisu, and I want to display a time stamp from the Controller on a WebVisu screen. The time stamp in the controller is UTC, but I need to display this time as the local time, based on the timezone on the user's PC. How do I do this? I am using Codesys 3.5 SP 15.

  • Posted a comment on discussion Engineering on CODESYS Forge

    You are probably right. When doing this in the past, I always had the luxury of having a driver that handled queuing for me. The application could just issue requests and wait for the response. I'll look into creating a message queue to handle all of the requests for all of the potential devices hanging off of a port. It shouldn't be too hard.

  • Posted a comment on discussion Engineering on CODESYS Forge

    I think the proposed logic would handle this: cycle 1 - Execute instance 1 (execute.1 OFF to ON) cycle 2 - look for instance 1 done (execute.1 should go from ON to OFF) cycle 3 - If Instance 1 done, Execute instance 2 (execute.2 OFF to ON) cycle 4 - look for instance 2 done (execute.2 should go from ON to OFF) cycle 5 - If Instance 2 done, Execute instance 3 (execute.3 OFF to ON), cycle 6 - look for instance 2 done (execute.3 should go from ON to OFF) ... etc. So, by the time we get back to the first...

  • Modified a comment on discussion Engineering on CODESYS Forge
  • Posted a comment on discussion Engineering on CODESYS Forge

    The current results are as follows: First device referenced in code - communications are successful every scan Second (and later) device reference in code - communications fail every scan From your question, it sounds like the application needs to handle queuing the messages when using ModbusRequest2. Our requirement is this: Communicate to up to 8 devices (per communication port) every second. When using the Modbus Driver in the device tree, all I needed to do was create 8 slave devices per port,...

  • Posted a comment on discussion Engineering on CODESYS Forge

    The current results are as follows: First device referenced in code - communications are successful every scan Second (and later) device reference in code - communications fail every scan From your question, it sounds like the application needs to handle queuing the messages when using ModbusRequest2. Our requirement is this: Communicate to up to 8 devices (per communication port) every second. When using the Modbus Driver in the device tree, all I needed to do was create 8 slave devices per port,...

View All