robbudge

We are doing this already with Grafana & Influx. We have a script that creates a DataDump file, then will call Curl via Shell to POST the data dump. i am currently looking into mqtt, but not how well the message structure will handle large data sets

Ok, just a Update. I have stripped the screen back and still IDLE draw time is 300ms, Active (Machine Running ) is 450ms. Now my button action is loading the required command into a string. I have a sequence monitoring the String length and then executes the string if the length >1. The first thing i noticed is the string did not always populate from the button action especially if i was using the mouse up action. When i changed the button to Mouse Down the string always gets populated. As the sequence returns the string to once executed i can verify that first the command is loaded into the string, and secondary the string has been executed. The 'Master Start' & 'Master Stop' channels are only read in the PLC and control a group start sequence. When the machine is running and the screen is busy the String Command does get cleared (So its Executed) but the OPC Tag stays TRUE not the String Command's target of FALSE. if i then switch to blank page with the buttons also on the stop command works fine. I'm confused how a Execute command running in a sequence can be effected by the screen re-draw activity. I'm going to change the priority of the Sequence to see if that helps.

Ok, so offloading the command to a sequence doesn't really solve the problem as the click is often missed. so im back looking at my graphics. Question about processing time. Between Split Colors & Color threshold is there much processing time difference ? i would suspect that split color is probably the most intensive but by how much. That screen currently has 20 Objects that utilize split colors. i was thinking of changing to color threshold, or simply 3 different symbol options Green Closed / OFF, Yellow mid / active , Green Open / ON

Most of the components are very heavily loaded and consist of multiple symbols and rules . shape for the background with multiple conditions and rules value with blink based on status text status, from any array. fill graphic based on value plus other items. off loading to a sequence to process the command string might be the way to go.

ok, so its is a resource issue. My development the screen draw time maxes at 200ms, on the runtime we max out a 850ms when all objects are active. so the next question is how do make sure the Quick Action or the event on the buttons work correctly. One thought was to simply load the command into a string then call a function or begin a sequence that executes the command string. this would require quite a lot of work but thats my first thoughts. Upgrading the on site hardware isn't really an option, we run a Quad 2.14 ghz IP69K Stainless Steel HMI. now performance could be lower than normal as i am viewing via VNC so that is additional work. With the piece of equipment stopped the draw time is 400ms.

I have a set of simple start and stop buttons. The Action is set to quick sequence and are very basic Pasturizer_Master_Start[0]=0 & Pasturizer_Master_Start[0]=1 Now i have copied the buttons to a blank page and they operate almost instantly. on the page in question with lots of active graphics the start normally works fine. once the machine is running and the screen update is busy with all the changing variables, then the stop button is very slow or doesn't work at all. I switch screens to the blank page with a copy of the buttons and the stop is instant. I suspect this is a result of the screen draw time and the quick sequence running in the same thread as the screen draw. The page is only set to update rate of 1/s so i'm guessing its the amount of symbols and values on the page causing the problem. i have a similar response to any popup windows that are called for on the same page. is there any way i can show thaw page draw time on the runtime licensed machine to verify if thats the issue. Also do you have any other suggestions without creating a sequence for every button command. Communications is via OPC with the updated DLL, its almost as if DF is so busy updating all the graphics on the screen the OPC Write gets missed or dropped.

On occasion for both static text and Variable Display, we require the text to be vertical, also for variable display alignment options would be really good