We encountered this issue several times on different kind of machines with various OES/Twincat versions. After a lot of searching and testing and tickets to the helpdesk, we couldn't find the rootcause in the PLC code, so it must be some kind of bug in the OES sourcecode, or something .NET related maybe. Every state hangs in NOT READY, and you cannot do anything in the HMI after one mode change. Usually this happens, when someone with a differently configured laptop downloads the code, and later someone else tries to download again on it. You can solve the issue 2 ways: 1. Change your Windows sorting setting to "technical". This is more like a prevention, and not 100% proven to solve this issue, but it can help in the future. 2. Get a totally different machine's project or empty project and do an "activate config". After the download is finished, a lot of errors will pop up (since nothing matches). Just ignore the errors and do another "activate config" with your original project. Also deploy HMI config and standards. Don't know why, but this is the only way that solved the problem. Funny thing is, that even if you try to do "activate config" straight with the original project, it will not work. But if you active the config of a totally different project and then the original, it works. By the way, there was already a topic about this, I started it a year ago: https://community.developer.bosch.com/t5/Control-plus/HMI-state-freezing-after-download-V1/m-p/75914#M784
... View more
