arkansascontrols
Lifetime Supporting Member
Ok, I'm stumped. Here's the scenario
I'm trying to isolate a performance issue with one particular Display that reads 14 Float tags. So in order to narrow this down I created a test display that does nothing except read the same tags and just pops the values into a listbox.
When I reboot my PC and load FactoryTalk View Studio, I can run the Single Test Display in test mode (No Client loaded) with RSLinx Active, and it takes about .2 seconds to read the 14 tags and put them in the listbox.
When I load the Client and launch the Test Display it takes about 28 seconds. No there is not a TYPO there! 200 ms before the client load, 28 Seconds after it loads.
Here's where it gets interesting. If I shut down the client and go back to Studio and run the display in test mode again, this time it takes about 28 seconds. If I reboot and run before loading the Client, I'm back to .2 secs.
BTW, this is not a network issue, I'm running PLC's in a emulator on the local machine during development. And it's not a RSLinx Issue, I can run a Test Client on the same tags and it updates the entire taggroup in around .2 sec before and after the Client Loads.
There are no tags loading and no processes running in the Client when the main display loads, so my Test Display isn't fighting for resources.
Any help would be appreciated.
I'm trying to isolate a performance issue with one particular Display that reads 14 Float tags. So in order to narrow this down I created a test display that does nothing except read the same tags and just pops the values into a listbox.
When I reboot my PC and load FactoryTalk View Studio, I can run the Single Test Display in test mode (No Client loaded) with RSLinx Active, and it takes about .2 seconds to read the 14 tags and put them in the listbox.
When I load the Client and launch the Test Display it takes about 28 seconds. No there is not a TYPO there! 200 ms before the client load, 28 Seconds after it loads.
Here's where it gets interesting. If I shut down the client and go back to Studio and run the display in test mode again, this time it takes about 28 seconds. If I reboot and run before loading the Client, I'm back to .2 secs.
BTW, this is not a network issue, I'm running PLC's in a emulator on the local machine during development. And it's not a RSLinx Issue, I can run a Test Client on the same tags and it updates the entire taggroup in around .2 sec before and after the Client Loads.
There are no tags loading and no processes running in the Client when the main display loads, so my Test Display isn't fighting for resources.
Any help would be appreciated.