martinav (Customer) asked a question.
Do-More Designer 2.9.4 and now 2.10.1 freezes regularly
I have been experiencing interface freezing in Do-More Designer in 2.9.4, and the problem continued after update to 2.10.1. It takes 1-2min, and it will release. It does not fully crash. Just a very annoying and regular freeze. Any idea what is causing this? The BRX works fine during a freeze. Seems to just be the designer. Please advise.
*UPDATED*
I almost always have DMD in Edit mode, and All Status enabled.
We have had issues with I/O System View, but that lockup does not release.
List out all the views you have opened and have status ON. Turning I/O System View status OFF may help.
If you have a ton of status, Designer will govern the comm and slow it down so that the GUI is responsive.
DBWin32 is a utility that ships with Designer - it records debug messages (not just from Designer) - there may be some clues there what's going on. Try launching that when you start Designer then see if anything gets logged whenever Designer freezes. You may want to reboot your PC and start "fresh" before using DBWin32.
Project Browser, Data, and I/O System. I'll close I/O system. I dont really need it anyway. Dont know how it got turned on, to be honest.
Next time it locks up, see if you can ping the PLC. Bring up a cmd prompt and type ping with the ip address of your PLC and see if you get good responses.
PLC seems to work find from the cmore panel during freeze. I/O was turned off during this. Heres some other stuff.
Text in that dbwin32 window: Scrolls constantly with this message:
28004: IsUIThreadResponsive dwDeltaSysTime(115959) dwCurrentSysTimeInMS(66651253)
28004: IsUIThreadResponsive dwDeltaSysTime(115997) dwCurrentSysTimeInMS(66651291)
28004: IsUIThreadResponsive dwDeltaSysTime(115997) dwCurrentSysTimeInMS(66651291)
28004: IsUIThreadResponsive dwDeltaSysTime(116014) dwCurrentSysTimeInMS(66651308)
BRX screen: no error
Yes, BRX pings fine during domore freeze.
Freezes ocurr so frequent now, its becoming unusable.
*UPDATE*
Freeze continues even with "No Status" and Data views closed.
It also seem to happen when I leave the program and do something else, the go back into the program. I get spinny circle and it stuck for 1-2min.
Yeah, the GUI is overwhelmed doing status. It's trying to slow down comm, but something is eating up the GUI.
Your comm is very fast, processing 189 transactions and reporting status on over 5000 elements every second. The GUI is not able to keep up.
Question: How many views are you doing live status ON at a time (wondering how you are doing 5000 elements every second)?
Try this:
No, that was with status and data views already turned off. Nothing it happening visually at all. So, there is no turning anything back on that will make a difference. Its broken with nothing.
This seems to happen when the screen is 'inactive'. Almost like there is some sort of standby thing going on. But, I am not aware of this kind of thing on a Win11 PC.
**UPDATE**
No that is not true either. I was working in an active window, then picked on "Edit Mode" and it froze. All with status turned off and no views open.
***ANother Update***
I uninstalled 2.10.1... and 2.9.4 was still there, so I uninstalled it too. On re-installation, I get this message:
I even put the PLC in STOP mode. issue remains. even after this exercise.
Its almost all the time now. I need something ASAP. This is stopped my project entirely!
It doesn't sound like an install issue. Install 2.10, then when you go into edit mode, there should be a message box that is popping up - this is your lockup. Let me know if there is a dialog or not.
If you don't see a dialog, - just hit the ESC key and see if that fixes the "lockup".
That was just an example. The software will lockup even if there is NO interaction with it. It just happend to do it the last time when I picked edit mode. Subsequent selections worked, and no dialog. But, then freezes up again.
I confirmed that ESC does not affect a freeze. It proceeds regardless.
Question: How many views are you doing live status ON at a time (wondering how you are doing 5000 elements every second)?
Try this: