+- Logic Machine Forum (https://forum.logicmachine.net)
+-- Forum: LogicMachine eco-system (https://forum.logicmachine.net/forumdisplay.php?fid=1)
+--- Forum: Visualization (https://forum.logicmachine.net/forumdisplay.php?fid=9)
+--- Thread: Graphic Performance Problem in different firmwares (/showthread.php?tid=950)
Graphic Performance Problem in different firmwares - savaskorkmaz - 18.08.2017
We have some touch panels which has android 4.2.2 system and we have a fullscreen application which shows LM4 graphics in that touchpanel. Because of android 4.2.2 web view engine, our touch panel does not have support for web socket technology. Because of that we have to use 20150907 LM4 firmware otherwise command buttons are not working with newest LM4 firmware.
Here is the problem :
Our LM4 projects including graphics are prepared in our office with a LM4 and new firmware , We got backup . And we loaded to the LM42S which is located in the site and this has old firmwares.
Problem is that button feedbacks are working very slow. For example , we have normal switch toogle button. When we push that button, in graphic , it turns to yellow on png after 4 seconds. (Button sttatus is same with main group address not a different group address)
Even when we completed this test with a new lappop pc and newest chrome browser, buttons are working very slow in graphic. But when we upgrade new firmware, problem is solving and it works very fast.
But we cannot use new firmware in the site because of touchpanel is not supporting button actions with new LM4 firmware.
How we can improve our graphic performance with old firmware ? We cannot start project from zero level because it has lots of man / days. There are lots of LM4
Regards,
RE: Graphic Performance Problem in different firmwares - admin - 18.08.2017
You can look into network activity in browser developer tools (F12). Old firmware used long-polling, so any bus activity caused data reload via AJAX. It is slower than websockets, but should not be as slow as 4 seconds. Either there's too much bus activity or some script causing a slow-down.