Executing windows cmd command ^{CODESYS Forge talk (Thread)}
Executing windows cmd command
Last updated: 2023-01-12

Codesys App - acces to linux cmd ? ^{CODESYS Forge talk (Thread)}
Codesys App - acces to linux cmd ?
Last updated: 2022-04-03

Online - Datei in Steuerung schreiben - per CMD ^{CODESYS Forge talk (Thread)}
Online - Datei in Steuerung schreiben - per CMD
Last updated: 2011-04-12

[ Windows ] How to Restart PLC in CMD line ? ( a Stop followed by a Start ) ^{CODESYS Forge talk (Thread)}
[ Windows ] How to Restart PLC in CMD line ? ( a Stop followed by a Start )
Last updated: 2020-03-27

Post by eschwellinger on Connection to device closed ^{CODESYS Forge talk (Post)}
is there a way to check the plclog on Opus A3 by using cmd line under Linux? This log is what you need to check for the disconnection problem
Last updated: 2023-08-24

Post by forest on SM Drive license error ^{CODESYS Forge talk (Post)}
Hi, when it comes about license, I used INVTmatic Studio, which uses Codesys, for programming INVT plc. I bought Codesys Modbus license, it was not expensive, and then realised that INVT didn't have License Manager option (greyed out in program) which is needed for using of Codesys License. I contacted support from INVT, but developers told me that option is still not available. So depending on environment for programming Codesys, you can or not use Modbus license. Good thing about this version of Modbus TCP it works both direction. I could send commands and receive feedbacks from drive. But communication stops after 30 mins. So I used simple version of ethernet modbus which is somewhere in INVT or Condesys library (I can check tomorrow) which works only one way. I could send cmd to drive, and control it, but didn't have any feedback, like some readings back in PLC. which is bad, but at least I could start it and it didn't fail after 30 mins.
Last updated: 2024-01-10

Post by jrsantab on Remote connection to ifm PLC & HMI ^{CODESYS Forge talk (Post)}
We have finally solved the problem. The version of the Gateway in the computer that worked (3.5.11.0) and the one that didn't (3.5.17.30) was different. We have three different Codesys 3.5 versions installed because we work with different controllers. I believe that, depending on the sequence you follow to install the versions you get a different Gateway version. To solve the problem you first have to disable the "obsolete" services. Open services, serach for (in our case) CODESYS Gateway V3 Version 3.5.11.0 CODESYS ServiceControl Version 3.5.11.0 I stopped the services and changed to Manual Start. Then you have to create the new services. In our case, from a Command Prompt session (cmd): SC CREATE "Codesys GatewayService Rigual" binpath="C:\Program Files\CODESYS 3.5.17.30\GatewayPLC\GatewayService.exe" and then SC CREATE "CODESYS ServiceControl Version 3.5.17.30" binpath="C:\Program Files\CODESYS 3.5.17.30\GatewayPLC\CODESYSControlService.exe" remember also to set them as Automatic Start!
Last updated: 2024-04-22

Sort by relevance or date