Long Wait Times

[RBPLC]

I've noticed with some actions I perform in DMD there are issues with getting the "wheel of death"/DMD Not Responding. For example, if I go to open a data view and then close out without actually opening a data view I get a software no response for 1-2 minutes. This issue happens both in simulator and when working with actual hardware. There are other places where these long no-response times are occurring as well. Are there specific settings that need to be turned on/off that would prevent his type of behavior?  I'm running software version 2.6.2.

[BobO]

I've noticed with some actions I perform in DMD there are issues with getting the "wheel of death"/DMD Not Responding. For example, if I go to open a data view and then close out without actually opening a data view I get a software no response for 1-2 minutes. This issue happens both in simulator and when working with actual hardware. There are other places where these long no-response times are occurring as well. Are there specific settings that need to be turned on/off that would prevent his type of behavior?  I'm running software version 2.6.2.

About the only time I ever see long delays is if comm is broken, or if there are network drives involved. Windows can be an absolute pig at times opening file dialogs.

[RBPLC]

Same issue with just opening Simulator projects.

[RBPLC]

BobO, based on your response I looked at comms links. I had an ethernet ECOM module in my links which was unplugged when I was noticing the long wait times. I deleted the ECOM link and the latency issues seem to go away. Does this mean that at any time DMD can't find links that there is the potential for these long wait times?

[franji1]

What kind of PC are you using?

Do you see the same behavior on other PCs?

[RBPLC]

I'm using an older custom built desktop running windows 10 professional but I believe I've seen similar issues running DMD on an hp zbook laptop running windows 10 professional (I'd have to attempt to replicate this on the laptop to confirm).

[BobO]

BobO, based on your response I looked at comms links. I had an ethernet ECOM module in my links which was unplugged when I was noticing the long wait times. I deleted the ECOM link and the latency issues seem to go away. Does this mean that at any time DMD can't find links that there is the potential for these long wait times?

I wouldn?t think that bad links would have a specific impact, other than possibly changing Windows networking behavior, which is where I would guess the problem is. All a link contains is the comm device settings, but at startup we attempt to talk to all of them just to see if they are there. If there is a busted connection, Windows may be attempting to hit a network adapter (virtual, wireless, etc) that is causing the delays.

The other big slowdown i see on occasion is when I have multiple designer sessions open, and one is online to a device that isn?t answering. Pretty common in my world (while developing), but that doesn?t really break anything, just slows the comm down on the functional session. Certainly nothing like you are describing.