Activity for risele
-
risele modified a comment on discussion Engineering 🇬🇧
You are welcome. Also note, that it's valid only if you modbus-device use same real/float value representation (IEEE 754). That's true for most of systems. But some devices may have other representation, such as integer + position of the decimal point, for example 123.456 is integer = 123456 and position = 3 Also note, that, ones again, depending on endianess of each system, you may also need to swap not just words, but bytes. TYPE u_Real : UNION rVal:REAL; wVal:ARRAY[0..1] OF WORD; bVal:ARRAY[0..3]...
-
You are welcome. Also note, that it's valid only if you modbus-device use same real/float value representation (IEEE 754). That's true for most of systems. But some devices may have other representation, such as integer + position of the decimal point, for example 123.456 is integer = 123456 and position = 3 Also note, that, ones again, depending on endianess of each system, you may also need to swap not just words, but bytes. TYPE u_Real : UNION rVal:REAL; wVal:ARRAY[0..1] OF WORD; bVal:ARRAY[0..3]...
-
First, if you don't need to change conversion rules in runtime, take a look at "Unit conversion" module (Application -> add object -> UnitConversion). You can specify there biderectional conversion with different units, limits and so on. Second, since MODBUS don't have "real" types but only general 16-bit registers and Real is 32-bit, generally you need a byte-was conversion Real <> two Words. Note, that depending on the devices on both sides, there are two options: Real-> Word1, Word2 or Real->...
-
First, if you don't need to change conversion rules in runtime, take a look at "Unit conversion" module (Application -> add object -> UnitConversion). You can specify there biderectional conversion with different units, limits and so on. Second, since MODBUS don't have "real" types but only general 16-bit registers and Real is 32-bit, generally you need a byte-was conversion Real <> two* Words. Note, that depending on the devices on both sides, there are two options: Real-> Word1, Word2 or Real->...
-
You actually can use copilot by PLCOpen XML file exporting/importing. It's fine to work with it directly (at least, the Codex do it quite well).
-
Have the same issue: I'm making a test setup for modbus devices testing and calibration. One is run for every possible address, and it starts with minimal request: if the device is found, it continue to work with it, otherwise it's set to Disabled temporary. Those state machines are running under FOR cycle, and disabled are just skipped. Every instance have its own timer for not running too frequently and a start delay, so the actual requests are separate in time. I also check not for a single error,...
-
Have the same issue: I'm making a test setup for modbus devices testing and calibration. One is run for every possible address, and it starts with minimal request: if the device is found, it continue to work with it, otherwise it's set to Disabled temporary. Those state machines are running under FOR cycle, and disabled are just skipped. Every instance have its own timer for not running too frequently and a start delay, so the actual requests are separate in time. I also check not for a single error,...
-
It's already fine to use, with help of exporting/importing as PLC_Open, at least CODEX is good in editing directly at XML and/or providing changes description separately.
-
Hi, it seems I have fixed issues with arrays of structs. Also added option for rootless JSON exporting/uploading And multidimensional arrays! https://github.com/Risele/PRO_JSON/ Hope it will work for you: I made brief tests at my structures only. PS: made with help of AI agent, found it's quite good if you give him project/files exported as PLCOpenXML.
-
Hi, I created a FB that read JSON file and convert it to the normal DUTs with this library. May be usefull for somebody: https://github.com/Risele/CodesysJSONFile/ There are project at Win3 Virtual controller + exported code (normal .export and xml) Also I made some notes about library limitations I found. Leaving here for others. Naming The names in JSON and in ST-based JSONVARs should match exactly. For JSON fields of {"field":"value", "otherField":3.14 } ST-struct should be: TYPE JSONST STRUCT...