Post by eschwellinger on No Visu on RasPi ^{CODESYS Forge talk (Post)}
..on 4.12.0.0 release there it will be possible to deploy RemoteTargetvisu which is what you expect now. (next week)
Last updated: 2024-06-20

Post by yannickasselin on Lenze i950 Servo and WAGO PFC200 ^{CODESYS Forge talk (Post)}
I don't have time to go through the whole manual but as I said earlier, the servo drive does not support any of the modes needed for SoftMotion Light to work. If you want to use the full SoftMotion, you could use SMC_Homing function block to do the homing. This function block does not use the Homing Mode. It still uses the CSP mode and does the logic in Codesys runtime instead of in the servo drive. Read the documentation about it to see if it fits your needs. But if your controller only supports SoftMotion Light, I am afraid you will not be able to use the i950. I do a lot of motion stuff with different servo brands. Some support all the modes needed for SoftMotion Light and some don't. You really need to make sure the modes are supported before choosing a brand over another. I tend not to use brand specific controllers in order not to be limited by their supported features. I usually choose a PC (Linux or Windows) and install the Codesys runtime and licences myself. This is the most flexible way to use Codesys in my opinion. Depending on how many axes are needed in your project, a full SoftMotion license may not be more expensive than SoftMotion Light because SoftMotion is available as Application based license whereas SoftMotion Light is not. But of course, SoftMotion is harder on the CPU than SoftMotion Light.
Last updated: 2 days ago

Post by pikebuster on Help for a newbie ^{CODESYS Forge talk (Post)}
Can somebody help me with this? I have problem with the button! This task must be solved using Sequential Function Chart (SFC), IEC 61131-3. TASK Create an SFC program to control a traffic light at an intersection. Description: You will program a traffic light that has three phases: Green, Yellow, and Red. The traffic light must follow these rules: Green light is on for 10 seconds. Yellow light is on for 3 seconds. Red light is on for 10 seconds. If the pedestrian button is pressed, the system must keep the red light on for 20 seconds during the next cycle. After the pedestrian has “crossed,” the system should return to its normal cycle. Basic Steps: Initialization: Start by setting the traffic light to Red. Green Phase: After 10 seconds, switch to Green. Yellow Phase: After 10 seconds in the Green phase, switch to Yellow. Red Phase: After 3 seconds in the Yellow phase, switch back to Red. Loop: Repeat the cycle. Use, for example, lamp symbols in the visualization module to simulate the traffic light. You may also add a simple pedestrian light if desired.
Last updated: 2025-03-11

Post by jv-certhon on Io driver Scan functionality ^{CODESYS Forge talk (Post)}
Hello, Codesys IDE is 3.5.21.30 IoDrvBase is: 3.5.17.8 I am working on implementing Codesys on our I/O product line, using the IO driver examples, and the Linux UDS socket approach. I have sucessfully created an implemetation where I have a Device with mutiple slots, on which I can plug modules. These modules represent our IO modules, and communication is successful. (For this question the assumtion can be made that Codesys commucates with 1 'master' device, which handles further communcation with the IO modules. For the next part of the question it can be assumed that the Master device has a list of which modules are attached/available) I'm now trying to implement the 'Scan for Devices...' feature, but I'm completetly lost on what to do once the IoDrvScanModules method is called in my IoDrvFB. I'm guessing that the ppConnectorList has to be filled with the found devices, but I have no idea if that is the correct approach. And Codesys is not triggering my breakpoints in the method, which makes things more difficult. I hope someone could provide some examples or guidance on what steps I should take to implement the scan feature. Thanks in advance.
Last updated: 2025-11-26

Reboot the device ^{CODESYS Forge talk (Thread)}
Reboot the device
Last updated: 2017-11-28

Visualization Scaling the Keypad ^{CODESYS Forge talk (Thread)}
Visualization Scaling the Keypad
Last updated: 2025-08-06

Post by e13740e on Сalling the context menu from the keyboard ^{CODESYS Forge talk (Post)}
Hello, the request is no longer relevant. Thank you. Working with the Main Menu bar via the Alt key is the most effective method. It has absolutely everything there. Calling the context menu via the keyboard is not necessary.
Last updated: 2025-10-09

Post by e13740e on Сalling the context menu from the keyboard ^{CODESYS Forge talk (Post)}
Hello, the request is no longer relevant. Thank you. Working with the Main Menu bar via the Alt key is the most effective method. It has absolutely everything there. Calling the context menu via the keyboard is not necessary.
Last updated: 2025-10-09

Accessing the underlying OS ^{CODESYS Forge talk (Thread)}
Accessing the underlying OS
Last updated: 2021-11-05

Using the filesystem? ^{CODESYS Forge talk (Thread)}
Using the filesystem?
Last updated: 2014-02-21

Release the axis ^{CODESYS Forge talk (Thread)}
Release the axis
Last updated: 2020-05-29

XYchart the bare minimum? ^{CODESYS Forge talk (Thread)}
XYchart the bare minimum?
Last updated: 2020-11-11

Setting the RTC clock ^{CODESYS Forge talk (Thread)}
Setting the RTC clock
Last updated: 2023-03-30

HMI on the BBB ^{CODESYS Forge talk (Thread)}
HMI on the BBB
Last updated: 2016-08-12

Modify the keypad ^{CODESYS Forge talk (Thread)}
Modify the keypad
Last updated: 2016-02-25

The GetText function ^{CODESYS Forge talk (Thread)}
The GetText function
Last updated: 2010-06-15

Breakpoint at the beginning ^{CODESYS Forge talk (Thread)}
Breakpoint at the beginning
Last updated: 2017-07-20

Bug on the website ^{CODESYS Forge talk (Thread)}
Bug on the website
Last updated: 2017-09-15

installing the runtime system ^{CODESYS Forge talk (Thread)}
installing the runtime system
Last updated: 2018-01-04

Interpreting the Symbol File ^{CODESYS Forge talk (Thread)}
Interpreting the Symbol File
Last updated: 2008-01-09

Configuring the Memory ^{CODESYS Forge talk (Thread)}
Configuring the Memory
Last updated: 2020-08-26

Seeking the SysLibSymbols.lib ^{CODESYS Forge talk (Thread)}
Seeking the SysLibSymbols.lib
Last updated: 2011-07-20

Post by testlogic on Sending Sequential Modbus TCP Packets ^{CODESYS Forge talk (Post)}
I have a Modbus TCP slave device where I need to do sequential writes to the same register. The register I'm writing to is kind of like a command line, each packet is a command word encoded in Hexadecimal. I am having difficulty implementing this system in CoDeSys 3.5 SP19. I feel like the structure of the program should be something along the lines of (Pseudocode): ModbusTCPSend(Command Register, Command1) ModbusTCPSend(Command Register, Command2) ModbusTCPSend(Command Register, Command3) I have tried to implement this with a rising edge trigger wMot1OPCode := 16#E1; //Stop Motor & Kill Program xMot1SendOP := TRUE; //Send OP on rising edge xMot1SendOP := FALSE; //Reset wMot1OPCode := 16#9E; //Disable Motor xMot1SendOP :=TRUE; //Send OP on rising edge xMot1SendOP := FALSE; //Reset Where "wMot1OPCode" is the IO map for writing to the command register, and "xMot1SendOP" is the rising edge trigger for that modbus channel. However, this doesn't work. The device never responds to the modbus commands. It seems like the trigger variable is switched too quickly for modbus to send the packet. I know the modbus register is working, because I can set the channel to cyclic and the device will respond. However, I can't use this reliably because I need each command to be sent once, in order. Cyclic keeps re-sending the commands and seems like it could miss a command as well if one was sent in-between cycle time. I have also trying using the Application trigger as described by https://faq.codesys.com/pages/viewpage.action?pageId=24510480, but this is also not working for me. See attached picture for my FBD code. This seems like a simple function, I can't tell what I'm doing wrong here. Thanks for the help.
Last updated: 2024-03-06

Post by dogulas on OPC UA C# client connecting to OPC UA CODESYS server ^{CODESYS Forge talk (Post)}
Noob alert! I’m just getting my feet wet with CODESYS. I have a “Hello World” project in the CODESYS IDE. I’m using the Win SoftPLC on the same computer. I’ve added a Communication Manager under the Application node. Under that is “OPC UA Server -> IEC Symbol Publishing 01”. I also added “OPC_UA_Symbols -> Information Model”. I’m not sure I need the second thing. I was grasping at straws. I also set up several dummy symbols in the IEC Symbol Publishing 01 node. In my C# application, I am trying to get an instance of EndpointDescription from CoreClientUtils.SelectEndpoint(“opc.tcp://localhost:1217/Gateway-1”, useSecurity: false, 15000). I wasn’t sure about the “Gateway-1”. I found that in the CODESYS IDE under the project -> Communication Settings. When I execute the previous method call in C#, I get: “BadSecureChannelClosed”. I have no idea what that means. Any pointers to documentation are welcome.
Last updated: 2024-08-16

Post by janderson on Ethercat scan for devices not picking up EL7041 as a softmotion axis ^{CODESYS Forge talk (Post)}
it appears that the different revisions have different PDOs. I am currently trying to use the rev25. I have tried to use the rev24 (the device repository entry not from 'scan for devices') and i keep getting 'invalid output mapping' or 'invalid input mapping' in the ethercat log. I cant even get the bus to run from the device description that comes from 'scan for devices'...
Last updated: 2023-09-18

Sort by relevance or date