IEC 61499 is probably something more complex than what you have correctly said so the prospects are interesting but we cannot ignore that it came out almost 20 years ago and has not won many hearts. I started to explore this world with a PLCnext controller because I love these devices based on RT Linux and Codesys is somehow usable with them but I have made little progress and I feel like inside a nutshell in the middle of the sea ;-) Gary's voluminous and precious book is always on my desk...
IEC 61499 is probably something more complex than what you have correctly said so the prospects are interesting but we cannot ignore that it came out almost 20 years ago and has not won many hearts. I started to explore this world with a PLCnext controller because I love these devices based on RT Linux and Codesys is somehow usable with them but I have made little progress and I feel like inside a nutshell in the middle of the sea ;-)
Hello otdeveloper, I am very interested in this topic. I have been dedicated to IEC 61499 for some time and I would like to understand if the time has come to adopt it in the real world of automation or if it will continue to fill up research papers only.
Thank you very much Morberis, tomorrow morning I will try to read and write other registers and I will try to understand if it's a shifting problem. Currently the registers are set as in the attached image but I noticed the same strange behavior also in the default setting. I hope the night brings advice...
Hi all, as you can see in the image, I am using a Raspberry pi as a Modbus TCP Slave. I have a simple test application with 3 Coils (Start 1000), 3 Discrete Input (Start 2000), 3 Holding Registers (Start 3000) and 3 Input Registers (Start 4000). If I send a Read Coil (0x01) at address 1000 and read all the 3 coils together (QModMaster on the left) I get 3 zeros and this is ok. If I send a Read Coil at address 1000 and read only one coil, I get 0 and also this is ok. If I send a Read Coil at address...
Hi all, as you can see in the image, I am using a Raspberry pi as a Modbus TCP Slave. I have a simple test application with 3 Coils (Start 1000), 3 Discrete Input (Start 2000), 3 Holding Registers (Start 3000) and 3 Input Registers (Start 4000). If I send a Read Coil (0x01) at address 1000 and read all the 3 coils together (QModMaster on the left) I get 3 zeros and this is ok. If I send a Read Coil at address 1000 and read only one coil, I get 0 and also this is ok. If I send a Read Coil at address...
Hi all, as you can see in the image, I am using a Raspberry pi as a Modbus TCP Slave. I have a simple test application with 3 Coils (Start 1000), 3 Discrete Input (Start 2000), 3 Holding Registers (Start 3000) and 3 Input Registers (Start 4000). If I send a Read Coil (0x01) at address 1000 and read all the 3 coils together (QModMaster on the left) I get 3 zeros and this is ok. If I send a Read Coil at address 1000 and read only one coil, I get 0 and also this is ok. If I send a Read Coil at address...
Hallo, Ich habe das gleiche Problem ("Identification between CODESYS and ETS is not equal! No exchange of data possible!" und Status: KNX: not running) mit Codesys V3.5 SP16 Patch 2, CODESYS Control Win V3 3.5.16.20, KNX Library 4.0.1.0 und Demo project KNX-Messestand_2018_2.project. Jede Hilfe wird geschätzt, Marcello