Host Engineering Forum
General Category => Do-more CPUs and Do-more Designer Software => Topic started by: RBPLC on February 21, 2022, 07:56:51 PM
-
I am getting the attached message when I delete rungs.
Edit:
And when I paste and when I Accept.
-
That is a Microsoft library error - not good.
Make sure you have backups (autosave only saves the last 4 saved copies). Not sure what is going on.
Definitely close Designer then re-open the project.
If you can duplicate it, if we had a copy of your project that would help us to possibly figure out the issue with the steps it took to duplicate it.
Email it to support at hosteng.com
-
In the same project I am also running into the following after upgrading the controller to OS 2.9.1 and Booter 1.1.0:
This project is in progress and hasn't been deployed yet. After upgrading the controller, I can open the project and when attempting to connect I get the attached error about unable to decode the MOVE instruction. The project and controller are not the same. The project opened from disk appears to be correct. The controller has the basic hardware configuration but no Programs, Tasks etc. I continue to open the DISK project. At that point I can write the project to the PLC and save. Everything appears to be working correctly. I close the project, re-open it and the same thing happens over again. Inconsistencies between project and PLC with PLC showing no Programs, Task etc.
Edit:
Same thing occurs if I don't close the project but simply disconnect from the PLC and try to reconnect. I get the same unable to decode MOVE instruction message.
-
That is a Microsoft library error - not good.
Make sure you have backups (autosave only saves the last 4 saved copies). Not sure what is going on.
Definitely close Designer then re-open the project.
If you can duplicate it, if we had a copy of your project that would help us to possibly figure out the issue with the steps it took to duplicate it.
Email it to support at hosteng.com
I've emailed the project file.
-
We got your project. I edited, Accepted, deleted rungs, added rungs, copy/pasted, etc., all without duplicating any of your symptoms. So, I gave it to franji1, and he's going to take a closer look at it using debug code. Thanks for your help.
-
Did you see the unable to decode move message?
-
I hate when my parameter is incorrect.
-
Did you see the unable to decode move message?
I just found "something" in the decode (PLC Opcode -> Designer Instruction/Parameters). Will let you know...
-
I just hit this same error a few seconds ago. I was attempting to go online with a BRX processor, using a project file on my computer (launched by picking the project file in the file browser.)
I canceled the program load and exited 2.9. 2.8 opened the file and connected without issues.
-
We have it down to a very simple program. Easily duped. Probably a decode bug introduced when that code was touched for sub structs. Should be an easy fix.
-
Any struct array reference to a field that is the :W1, :B1, :B2, or :B3 of a DWORD will decode incorrectly. So SDT[V0].Year (which is :W1) will fail. Yuk. Yuk, yuk, yuk. Don't know how this snuck through, but we'll get a new build out ASAP.
-
How's this going? Initially I was very concerned as I thought this tanked my controller but after seeing it's currently more of an annoyance, I don't have to fix it right now. I upgraded another controller to 2.9 and saw the similar unable to decode the MOVE popup.
-
We have a Designer 2.9.2 Release Candidate being banged on. Production should be very soon.
Be careful because the instruction parameters WILL CHANGE, sometimes as an error, sometimes not (i.e. if there IS a corresponding W0 or B0 field, it WON'T report the error, but just show up as a "difference between disk and PLC". Make sure you utilize the DISK copy (it still has the correct W1/B1/B2 offset field)
-
How's this going? Initially I was very concerned as I thought this tanked my controller but after seeing it's currently more of an annoyance, I don't have to fix it right now. I upgraded another controller to 2.9 and saw the similar unable to decode the MOVE popup.
It's fixed. We'll be releasing 2.9.2 very soon.
The specific problem is it's incorrectly decoding array references to structures with BYTE or WORD members not at the start of a DWORD. In cast terms, struct members that are :W1, :B1, :B2, or :B3. So for example, SDT[V0].Year fails to decode when the program is read up. This was a small hole in the decode function that got refactored when adding nested structures.
We've found a few of things like that, but all we know about are fixed.
-
Thanks for getting this fixed. Logged on to the problem PLC this morning after the update with no error messages. Also thanks for putting the Add button back in under the Modbus Scanner tool.