Search talk: WHERE TO FIND SHR BLOCK

 
<< < 1 .. 26 27 28 29 30 .. 243 > >> (Page 28 of 243)

Post by erictur on CODESYS Control for Linux ARM SL (32 bit) on Moxa UC-3100 IPC CODESYS Forge talk (Post)
UC3100 comes with Arm Cortex-A8 1 GHz and belongs to Moxa Industrial Linux 1 (Debian 9) for Arm-based Computers. I tried to install the CODESYS Control for Linux ARM SL (32 bit) on Moxa UC-3100 IPC. Unfortunately, the Third-party requirements: - libc >= 2.27 (required by CodeMeter Runtime) of the CODESYS Control for Linux ARM SL cannot be met on the Debian 9, which comes with glibc 2.24. I read the post by @johnlee (Getting Start with Codesys Control for Linux SL) (https://forge.codesys.com/forge/talk/Runtime/thread/0a515ced3f/). Where he discusses installation of CODESYS Control for Linux ARM SL on Debian 9. There was CODESYS Linux runtime v3.5.14 availble and it was successfully intalled on the Debian 9. However, the CODESYS Store has the oldest version V4.1.0.0 32 bit available. There is no way to find the CODESYS Linux runtime v3.5.14. So is there any work around for this? Or I cannot install the CODESYS Runtime on any of the Moxa IPCs based on the Moxa Industrial Linux 1 (Debian 9)?
Last updated: 2025-07-10

Post by xcqt on Oop best practice CODESYS Forge talk (Post)
Hi all, I’m currently trying to improve my OOP structure in CODESYS and I’m looking for some input on how others approach this. I understand the basics like inheritance, interfaces, abstract FBs, methods, and properties, but I still struggle a bit with the overall architecture and what’s considered clean or scalable in bigger projects. As an example, I’m working on two different energy meter function blocks: FB_EnergyMeter_MQTT reads data from MQTT (strings) FB_EnergyMeter_Modbus reads data from Modbus (words) Both have their own Update() method and implement the same interface (something like IF_EnergyMeter). Later on, I’ll probably add more meter types, but they should all behave the same from the controller’s point of view. Now, there’s a FB_GridControl block that needs power data from these meters. I see two options here: Define the meter blocks inside FB_GridControl and call them directly (for example fbModbusMeter.UpdateModbus()). Keep the meter blocks outside and pass them into FB_GridControl as interface references, so the control block doesn’t know which specific type of meter it’s dealing with. Option 2 feels cleaner and more flexible to me, but I’m not entirely sure how to handle the data flow in that case. Should I pass the meter instance through an interface reference (REFERENCE TO IF_EnergyMeter)? Or is there a better way to link the external FBs to the control block? I’d like to hear how you structure this kind of setup or see an example from someone who has done something similar. EDIT: I think i need to do something like this fbModbusUpdateInput(wInput:= wWordValue); fbMqttUpdateInput(strInput:= strStringValue); IF bUseMqtt THEN Meter REF = fbMqttUpdateInput; ELSE Meter REF = fbModbusUpdateInput; END_IF fbControl.SetMeter(UsedMeter := Meter); Or am i thinking wrong? Thanks, Thomas
Last updated: 2025-10-16

Post by arundara on Variable Sync Issue In Soft Plc Redundancy CODESYS Forge talk (Post)
Hello, I was trying to create a redundancy POC for our application where we read data from few modbus tcp devices. As there is a limitaion that modbus tcp device support only for single master device, we wanted to test how the variable sync happens in redundancy mode. For that i have used the redundancy sample code added a variable "b" under a condition. What i observed was while active controller is running, if passive controller is powerup, passive controller is able to sync all the data configured for redundacny. But after that the variable data which resided under a condition is not synching from active to passive controller. I have attached the image where i have highlighter the variable. Can some help me to understand how redundacny work in codesys soft plc and if there is a solution to sync variable which are under condition, please explain the same or suggestion to achieve the same. Hardware - Raspberry Pi (2 qty) Redundancy licence used - yes in both controllers. Codesys runtime - 4.9.0.0 Codesys software version - V3.5 SP19 if i have posted this question in wrong section, please do let me know in whcih section i have to post this question.
Last updated: 2023-12-01

Post by trusty-squire on parker servo and position CODESYS Forge talk (Post)
@gepert, When you say "I do not turn off power", are you saying you don't power off the drive, or you don't turn of the MC_POWER function block? I read your statement as you don't kill actual electrical power. MC_POWER should stay enabled. @Gustavo, not related to problem at all, but when you say 1.6 Nm is only enough torque to unscrew a loose bottle cap, I think that's a bit low. A quick mental math I use is 1 Nm is almost the same force as 1kG applied to a 10cm wrench. So 1.6kG applied to a 10cm wrench is still not a huge force, but more than enough to be felt if trying to turn the shaft by hand.
Last updated: 2024-08-06

Post by elsmart on Sequential read and triggering of Modbs RTU channels in application CODESYS Forge talk (Post)
Hello I need some help understanding how to use Modbus RTU (COM port) in Codesys enviroment. I defined a Modbus Server device (slave) in device tree and added some channels to read from (function 3). Also I set trigering mode to Application. I have a POU in which I want to trigger each channel one after the other something like this (C code for better visualisation): for (int i = 0; i < channelsCount; i++) { triggerChannel(channelsArray[i]); // Start transmission while(channel.xBusy); // Wait for transmission to complete } I have found ModbusChannel function block documentation but examples are scarce. I don't understand how rising edge triggering works. What would be the best solution for achieving sequntial channel triggering? What is the common way to read multiple Modbus channels once every time a specified POU is executed?
Last updated: 2025-05-16

Post by alexgooi on Function Blocks and arrays of function blocks CODESYS Forge talk (Post)
Hi Jack, I think you have to look at a FB in a different way. A Function block (Class) can contain its own data. In other words don't define loose data in your GVL, but define a instance of a FB (Object) in your GVL: Example: Function_Block Basic_Class VAR_INPUT Open_Command: BOOL; END_VAR VAR_OUTPUT Opened: BOOL; END_VAR if Open_Command then Opened := TRUE; ELSE Opened := FALSE; END_IF Global Variables Objects: ARRAY[1..100] OF Basic_Class; //Here you ar defining you objects END_VAR In your code you can directly acces the data and couple it to the IO: GVL.Objects[1].Open_Command := %IX0.0; %QX0.0 := GVL.Objects[1].Opened; //To call the code itself use: GVL.Objects[1](); If you want to take this a step further you are also able to add methods and properties to the FB/Class end thereby creating a OOIP program
Last updated: 2024-02-15

how to add module to raspberry pi CODESYS Forge talk (Thread)
how to add module to raspberry pi
Last updated: 2020-11-24

how to set custom from/to timestamp in Trend CODESYS Forge talk (Thread)
how to set custom from/to timestamp in Trend
Last updated: 2020-03-31

Unable to connect to git remotes through Codesys. CODESYS Forge talk (Thread)
Unable to connect to git remotes through Codesys.
Last updated: 2023-11-10

How to adapt Codesys Control SL to custom board CODESYS Forge talk (Thread)
How to adapt Codesys Control SL to custom board
Last updated: 2024-08-09

Unable to Connect to Modbus RTU Device CODESYS Forge talk (Thread)
Unable to Connect to Modbus RTU Device
Last updated: 2024-08-26

Unable to Connect to Modbus RTU Device CODESYS Forge talk (Thread)
Unable to Connect to Modbus RTU Device
Last updated: 2024-08-26

Unable to Connect to Modbus RTU Device CODESYS Forge talk (Thread)
Unable to Connect to Modbus RTU Device
Last updated: 2024-08-26

Unable to Connect to Modbus RTU Device CODESYS Forge talk (Thread)
Unable to Connect to Modbus RTU Device
Last updated: 2024-08-26

Unable to Connect to Modbus RTU Device CODESYS Forge talk (Thread)
Unable to Connect to Modbus RTU Device
Last updated: 2024-08-26

Unable to Connect to Modbus RTU Device CODESYS Forge talk (Thread)
Unable to Connect to Modbus RTU Device
Last updated: 2024-08-26

Unable to Connect to Modbus RTU Device CODESYS Forge talk (Thread)
Unable to Connect to Modbus RTU Device
Last updated: 2024-09-03

Unable to Connect to Modbus RTU Device CODESYS Forge talk (Thread)
Unable to Connect to Modbus RTU Device
Last updated: 2024-09-04

How to revert to previous version library CODESYS Forge talk (Thread)
How to revert to previous version library
Last updated: 2024-09-06

Unable to add alarm configuration object to project CODESYS Forge talk (Thread)
Unable to add alarm configuration object to project
Last updated: 2024-09-27

Trying to connect Codesys OPC server to Ignition CODESYS Forge talk (Thread)
Trying to connect Codesys OPC server to Ignition
Last updated: 2025-01-22

How to use libdoc to implement libraries in multiple languages CODESYS Forge talk (Thread)
How to use libdoc to implement libraries in multiple languages
Last updated: 2025-03-13

Is it possible to add regions to ST-code? CODESYS Forge talk (Thread)
Is it possible to add regions to ST-code?
Last updated: 2025-07-10

Codesys to Android App to Cloud Database CODESYS Forge talk (Thread)
Codesys to Android App to Cloud Database
Last updated: 2022-03-10

How to map to values in CAN BUS CODESYS Forge talk (Thread)
How to map to values in CAN BUS
Last updated: 2021-04-29

<< < 1 .. 26 27 28 29 30 .. 243 > >> (Page 28 of 243)

Showing results of 6057

Sort by relevance or date