Write to simulator Task code error response

[MarkTTU]

Just getting started on a new program and using the simulator to validate some loops, but I keep getting an error when writing an update from Domore designer to the simulator:

"Comm error while writing documentation to PLC"
"Task code error response"
"Code = 5 : Address was out of range."

I get this error whether I'm doing it as a run mode write or not.

If I disconnect from the simulator and then connect to it the program transfers to the simulator and works fine.

Any thoughts?

[MarkTTU]

I still haven't figured out what's wrong, but in the mean time, is there any way to disable writing the documentation to the PLC? Since this is all just in simulation I don't need the documentation written over to the PLC and if I could disable that it'd sure make iterative testing quicker...

[BobO]

I still haven't figured out what's wrong, but in the mean time, is there any way to disable writing the documentation to the PLC? Since this is all just in simulation I don't need the documentation written over to the PLC and if I could disable that it'd sure make iterative testing quicker...

The short answer is no, documentation, program, and sysconfig are all tightly coupled.

That is somewhat moot though. This error suggests something more fundamentally wrong. There is no way you are running out of documentation memory, so the comm itself is goobered up. You might try running the simulator on a different PC and connecting to it through a normal link.

[MarkTTU]

Tried running a simulator on a different PC and connecting to it from the first PC running Domore Designer with the same results.

I suspect there's something goofy in my documentation that's crashing something else along the way. It appears that if I reboot then I can write to the simulator once, but after that if I try to write again it will crash. I'll email you my program so you can take a look. Other than a LOT of documentation with  there's not much to it. For what it's worth I've got a little over 40,000 bits with nicknames.

[BobO]

For anyone who sees this in the future, it was actually that the program had massive amounts of documentation which was causing an issue with the REST API tag lookup table. Wasn't really breaking the controller, it was running out of documentation memory because the tag table was so large. A future DmD version will provide at least two ways to work around this, but this shouldn't be a problem for 99% of users.

[MarkTTU]

For anyone who sees this in the future, it was actually that the program had massive amounts of documentation which was causing an issue with the REST API tag lookup table. Wasn't really breaking the controller, it was running out of documentation memory because the tag table was so large. A future DmD version will provide at least two ways to work around this, but this shouldn't be a problem for 99% of users.

Thanks again for the quick email response and diagnosis!