Gateway and runtime (Control for linux SL) on a debian linux. Thanks for your check. Good to know. I will probably travel there in about a months time so that will give me better possibility for further testing. (on a side note, I dont get mail-updates on forum-subscriptions, need to check the topics manually)
*** The system may be in an inconsistent state, please reboot *** *Exception* Async service: ServiceGroup=17, IP=0x5fa45617, Component=CmpSrv Every time at the instant that I Login to the system a message that the "system may be in an inconsistent state, please reboot" is written in the log. If I logout and repeat login a new entry is set. My system is a "Control for linux SL" running on a debian linux host. Im running it on my desk without any IO attached so message might be caused from that, but...
An update note. Still using linux/Qemu. Still happy, but sometimes some things are harder. I lost the "bridge" connection to my VM (meaning for instance I couldnt "scan network" and find local units. Have spent tons of hours to find out why. Finally it seems the traffic got blocked by the firewall/iptables so needed to set rules for that. So friendly note that rules must allow forward traffic to/from you configured host bridge device.
I have a Hmi that acts as an interface for many (mostly identical) units. This is managed by a sort of "mux" where you select which unit that should be presented on the HMI. Backbone is solved by a HMI-gvl defined as reference/pointer to "unit-data", which then can be set to the individual units. While this works for most data I still have not sorted how to solve this for the trend recordings. One solution would be to have already "mux:ed" data values as source for the/one trend. However then the...
I have a Hmi that acts as an interface for many (mostly identical) units. This is managed by a sort of "mux" where you select which unit that should be presented on the HMI. Backbone is solved by a HMI-gvl defined as reference/pointer to "unit-data", which then can be set to the individual units. While this works for most data I still have not sorted how to solve this for the trend recordings. One solution would be to have already "mux:ed" data values as source for the/one trend. However then the...
You should use PLCnext if your device-hw is a PLCnext-un it. As I understand it you are using "CODESYS Control Win V3 x64".
The structure should be the same independent of which runtime version. Im using Codesys control for linux SL. Ie, add an ethernet device, then profinet controler then phoenix PN bus coupler.
Pretty much my configuration, see attached.