The option to update "Control for Linux SL" is not shown in the "deploy control SL tool", I can see and update the gateway but not the control (3.5.21 SP4). Has the way to update control SL changed? In the process of fault finding I removed the control SL entirely from my target, then I had to revert to version 3.5.21.0 SP 1 to re-install "Control SL 4.17.0.0". So I thought it was just a matter of using SP1 to update also to 4.18.0.0, but after installing the files for 4.18.0.0 in the SP1-version,...
There seems to have been included an updated in the last release 4.9.0.0 or am I wrong (I think I tried out these settings previously without giving the result I wanted contrary to what I see today)? Now an empty check box for "display variable name" is effective, and will present the Variable with the "Description" instead. Perfect! Seems to be some minor formatting still that needs adjustment. See attached screenshot. The apostrophe "'" between "description" I suppose should not be there? Also...
Trying the web-version of trend-data. This seems to be a impressive tool, but I lack/cant find a number of what I would think are important parts. There does not seem to be a way to get away from the dot.notated variable naming in the legend.. A developer might want the dot-notation but an end-customer will surely not. For instance I want to display 12 temperatures, instead of t1, t2 etc.. they will be named. gvl_io.unit[1].trend.temps.t1_a gvl_io.unit[1].trend.temps.t1_b gvl_io.unit[1].trend.temps.t1_c...
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...