Host Engineering Forum
General Category => Do-more CPUs and Do-more Designer Software => Topic started by: ksasikumar on May 31, 2022, 12:06:10 PM
-
Hello!
I have been using the Do-More Simulator to test some programs and noticed that the simulator keeps getting disconnected or closes completely while in run mode. I am not sure if this is a simulator bug or if there is an issue with the program I am running specifically. My program mainly uses FileRead instructions - which are reading from the Simulator's "SD card" folder.
Is this a known issue?
-
Hello!
I have been using the Do-More Simulator to test some programs and noticed that the simulator keeps getting disconnected or closes completely while in run mode. I am not sure if this is a simulator bug or if there is an issue with the program I am running specifically. My program mainly uses FileRead instructions - which are reading from the Simulator's "SD card" folder.
Is this a known issue?
Not that we are aware of. We're happy to look at the program and see if there is anything amiss. You can email it to support@hosteng.com.
-
It might be worth noting that the simulator has a 30 minute timeout where you have to restart it to keep using it.
-
That's good to know, but this is an immediate disconnection on Run mode. It kind of goes back and forth connected-disconnected rapidly and then finally the simulator closes itself.
-
I received your email, ksasikumar, and can duplicate the issue.
We're looking into it. We'll keep you posted.
-
Hmmm....
Two issues. Not sure how it's gone this long without someone finding them, but fortunately they are only in the sim and not in the PLC.
1. When a file is open and the sim is switched to program mode there is a hard crash. This may manifest as the sim closing unexpectedly.
2. The FilePointer and EndOfFile fields are not being properly updated.
Because the EndOfFile never gets set, the program overruns the string array you've set up, which then causes comm errors from reading beyond the array limit.
Both were easy fixes. We're dropping a maintenance release next week, so this fix will be in it.
-
That's great. Thanks for the speedy response!