Hello, we have the same problem here. Our configuration in the following: Codesys V3.5 SP19 running on Exor Exware700Q Profinet network connected on Eth1 IOLink Master Turck TBEN-S2-4IOL version 3.5.9.0 IOLink sensors E+H & Sick (Pressure, T°) We installed the codesys IO link package and have the codesys IO Link SL licence activated (on a dongle) Our problem is the following: we got the IODD files from E+H & Sick we add the devices in the codesys device repository with success They appear in the...
Hello, we have the same problem here. Our configuration in the following: Codesys V3.5 SP19 running on Exor Exware700Q Profinet network connected on Eth1 IOLink Master Turck TBEN-S2-4IOL version 3.5.9.0 IOLink sensors E+H & Sick (Pressure, T°) We installed the codesys IO link package and have the codesys IO Link SL licence activated (on a dongle) Our problem is the following: we got the IODD files from E+H & Sick we add the devices in the codesys device repository with success They appear in the...
hello, i have similar problem these last week. i am running a older version of rpi MC ( 4.0.0.0) on powerIO H1M100. in my case, i even have no message recorded at all, new messages are logged only when a reboot is triggered. i also have OPC UA communication with another rpi where i run nodered . i monitor the status of the communication to inform me when the system stop working sending a notification by telegram... the app was running for month without major trouble. i did only minor changes in the...
hello, i have similar problem these last week. i am running a older version of rpi MC ( 4.0.0.0) on powerIO H1M100. in my case, i even have no message recorded at all, new messages are logged only when a reboot is triggered. i also have OPC UA communication with another rpi where i run nodered . i monitor the status of the communication to inform me when the system stop working sending a notification by telegram... the app was running for month without major trouble. i did only minor changes in the...
Hello, my codesys system running on a raspberry pi target is sometime crashing for any reason. In that case, I need to reboot but I noticed that the logger does not contain any message older than the reboot time. How can I get the log of event that caused the crash and could help me in the diagnosis before crash? Thanks for any help.
Thanks Timvh, it was the perfect answer! now build of my application is working without error.
Hello All, I have an home automation control system running on H1M100 PowerIO target running well for 9 month (this target is using raspberry MC SL and PowerIO has a wonderfull HVAC library). I developped it on V3.5 SP16 but this last weeks I have sometime some problems with OPC_UA or runtime suddendly stop. I decided to upgrade to V3.5 SP17 because i know the target as a runtime compatible with SP17. After update all library in the project and building the application I got this error message. [ERROR]...
Hello, i am running an HVAC application running codesys with HVAC library and ruuning on a powerIO target H1M100 based onnRaspberry Pi. The app is working without any codesys trouble for 3 month now. This week at the morning of 1st of march,I noticed that the webvisu could not be reached from whatever browser. after a download, it was again reachable from everywhere but the next change only where not working anymore giving some strange time out message an only possibility to dowload now is a full...