Host Engineering Forum
General Category => Do-more CPUs and Do-more Designer Software => Topic started by: pbw on July 16, 2023, 06:38:33 PM
-
Hi,
I have a BX-DM1E-10AR3 in the field...and I tried connecting to it and while I can connect to it, I cannot find the program, it's like it's missing. (See attached)
Note: When initially connecting I noticed it had a watchdog error wich I cleared.
Is there anything I could do to get the program from it?
-
There's no good reason to NOT have a $Main code block. I've only seen this happen when the project is corrupt, or the comm connection to the CPU is sketchy which corrupts the project when it gets read from the CPU.
When you were connecting to the CPU, did DmDesigner tell you the offline and online projects did NOT match? and ask you to pick which one to open ? If so, which one did you pick ?
-
The upload failed on the "Unable to decode MOVE instruction". This is the critical failure. We need to figure out what is wrong.
Do you have a copy of the DISK project? If so, do you think that is a copy of what is in the PLC?
EDIT:
You can also do PLC->Create Image File and select the defaults (i.e. the program) to generate an image of the program. If you can, email that file to support@hosteng.com. That image file would be better than the disk project since we would be getting the actual image of the program in the PLC.
-
When you were connecting to the CPU, did DmDesigner tell you the offline and online projects did NOT match? and ask you to pick which one to open ? If so, which one did you pick ?
Yes! I picked "Go Online and View PLC Project"
-
The upload failed on the "Unable to decode MOVE instruction". This is the critical failure. We need to figure out what is wrong.
Do you have a copy of the DISK project? If so, do you think that is a copy of what is in the PLC?
EDIT:
You can also do PLC->Create Image File and select the defaults (i.e. the program) to generate an image of the program. If you can, email that file to support@hosteng.com. That image file would be better than the disk project since we would be getting the actual image of the program in the PLC.
Yes, I have a copy of the Disk Project...I think It's current....I will email both.
-
Got your files. The .dmd project file was fine. I was able to load your .bin into my PLC, and then I was able to READ the Project into Designer. I did NOT get an error attempting to decode a MOVE instruction ("decode" is from opcode values => instruction, "encode" is done on the WRITE to PLC instruction=>opcode)
Since I was able to read the program/project, I looked at the "MOVE" instruction that is at (absolute) address @10160. It is actually a sub-instruction of the COPY "macro" instruction. It's setting a field in a data block array indexed with the value 0.
I then did a "compare" of the READ PLC program against the .dmd file you emailed and the only difference was the DISK .dmd file had some EMAIL instructions in a rung at the top of $Main. EDIT: Oops - had that backwards - the .dmd file did NOT have emails, but the PLC copy DID have a bunch at top of $Main..
I will do some more investigation.
-
What version of Designer are you using (full version, e.g. 2.9.4)? I was able to READ the project from the PLC with both my Alpha Debug version of pre-released Designer 2.10, AND with (latest) Production 2.9.4. I may need to test it with another version of Designer if yours is different.
-
Another question/request. Can you email or post a screen shot of your System Information Event Logs tab?
PLC->System Information... click on the Event Logs tab
One way to screen capture, do Alt+PrintScreen key that captures the current focus/top window and put it in the clipboard, then paste that into paint or something. Another alternative is to do Save to File button from the Event Logs dialog and attach/email the file.
-
What version of Designer are you using (full version, e.g. 2.9.4)? I was able to READ the project from the PLC with both my Alpha Debug version of pre-released Designer 2.10, AND with (latest) Production 2.9.4. I may need to test it with another version of Designer if yours is different.
2.9.4 Booter 1.1.0
-
Another question/request. Can you email or post a screen shot of your System Information Event Logs tab?
PLC->System Information... click on the Event Logs tab
One way to screen capture, do Alt+PrintScreen key that captures the current focus/top window and put it in the clipboard, then paste that into paint or something. Another alternative is to do Save to File button from the Event Logs dialog and attach/email the file.
Event Log
-
2.9.4 Booter 1.1.0
The screen shot shows the Firmware version is 2.9.4 (latest firmware is 2.9.7 - hence the asterisk)
Do Help->About in Designer to see the Designer software version. Latest software version is 2.9.4
Generally speaking, the first two digits of both Software and Firmware refer to the "Do-more Technology Version", which is the feature set, e.g. DmT 2.9 which added features not available in 2.8 or lower). However, the 3rd digit is independent for each, incremented based on updates to the firmware vs updates to the software (2.9.7 latest f/w, 2.9.4 latest s/w).
-
It's 2.9.1
-
I recommend getting 2.9.4 - it definitely had some bug fixes.
-
Will do, I must have missed the update.
Thanks
-
DEFINITELY a Designer bug in 2.9.1 that we fixed in 2.9.2 (from the 2.9.4 Updates.pdf file):
5. Adjusted Anomalies
h. Connect to PLC - converting PLC Opcodes to Element properly handles array of a BYTE or WORD struct field (2.9.2).
EDIT:
I remember this critical error post getting sent out shortly after 2.9.1 shipped.
https://forum.hosteng.com/index.php?topic=3592.0
-
Update: I Updated the PLC Firmware, reconnected and I was able to read the Program from it.
Looks Good!
Thanks for your help.
-
Update: I Updated the PLC Firmware, reconnected and I was able to read the Program from it.
Looks Good!
Thanks for your help.
You mean you updated Designer software (not PLC firmware, although that's also important but for other reasons). Designer 2.9.1 had a bug in it that misreads your program in that one rare situation when Designer reads it back from the PLC. Designer 2.9.2 addressed that issue. Make sure you are running the latest Designer software (2.9.4) and not 2.9.1 (Help->About in Designer software).
-
I was running Designer 2.9.1.....downloaded and installed 2.9.4....then updated PLC firmware...disconnected from PLC...reconnected, and then I was able to read the project from the PLC.
-
I was running Designer 2.9.1.....downloaded and installed 2.9.4....then updated PLC firmware...disconnected from PLC...reconnected, and then I was able to read the project from the PLC.
PERFECT!