16
Support Questions / Re: AvancedHMI Application slow to start up -- uses up lots of RAM at first
« on: September 08, 2013, 01:28:28 AM »
Hi, Archie,
A PLC that I communicate with using the EthernetIPforCLXComm driver went down tonight at one of the plants. The AdvancedHMI program that I wrote reads data from that PLC as well as another PLC that uses the EthernetIPforPLCSLCMicroCom driver. With the one PLC not responding, the program was very sluggish and wasn't working very well at all. I implemented the change to PCCCSubscription that you suggested and the application is running like normal again!
This leads me to a few questions:
(I'm using v 3.5.7)
Thanks!
A PLC that I communicate with using the EthernetIPforCLXComm driver went down tonight at one of the plants. The AdvancedHMI program that I wrote reads data from that PLC as well as another PLC that uses the EthernetIPforPLCSLCMicroCom driver. With the one PLC not responding, the program was very sluggish and wasn't working very well at all. I implemented the change to PCCCSubscription that you suggested and the application is running like normal again!
This leads me to a few questions:
- Does the suggested change work for both types of PLC drivers I mentioned, or just the EthernetIPforCLXComm?
- Even with disabled subscriptions set to true on both drivers, I'm still getting data on the PLC that is up and running. I must not be understanding what disabling subscriptions does. Does it mean only disable new subscriptions but subscriptions ARE still created for controls that were built and assigned at design time?
- What is the benefit of getting the processor type?
- My initial thoughts are to always put this change in all of my advancedhmi apps from here on out since it seems to make them more bullet proof. So, to pose question #3 in a different way, would this be a bad thing?
(I'm using v 3.5.7)
Thanks!