MWX Hang up

[ATU]

I started having an issue with an MWX instruction that just does nothing. It doesn't fault or give me a success. It just sits there all alone in a stage. I made sure the program is not looping back through the stage. I don't have any conflicts on the port or the device. The device status shows the instruction as "Locked" .  What does that tell me? The idle time toggles from 0 to 1.  I have never seen this before. This was working. If I shut the stage off, I get a fault "Device instruction terminated before completion @0000081A (MWX at Mod3_RL_Axis4@27)" Help

[ATU]

I went back and changed the device to another one already in the program and it worked. So I changed all the other uses for the device, 3 in that program to the other device and deleted that one. Downloaded, saved. Then I recreated the device and used the new one as before. All works fine. Somehow that device got corrupted. I have a copy of that program, do you want to look at it?

[BobO]

I went back and changed the device to another one already in the program and it worked. So I changed all the other uses for the device, 3 in that program to the other device and deleted that one. Downloaded, saved. Then I recreated the device and used the new one as before. All works fine. Somehow that device got corrupted. I have a copy of that program, do you want to look at it?

Sometimes the problem is something in retentive memory that gets flushed in the process of recreating stuff, so the project itself may not be the issue, but, if putting that project back into a unit results in the failure coming back, then I definitely want to see it.

[BobO]

Another thing that you can try in the future is to export the project without the SysConfig, and then import again. That has been known to clean things up.

One of the biggest strengths and weaknesses of Do-more is our continuous improvement of it. From version to version we are patching stuff in the background. I think sometimes that process isn't as clean as we would like, and older projects acquire some entropy over time.

[ATU]

I loaded the old program in and it worked fine.

[BobO]

I loaded the old program in and it worked fine.

Probably something stuck in retentive memory then. Clearing probably would have fixed it.

[ATU]

The original problem was 5 modbusTCP devices that were on the same TCP port. The device I was talking with could only handle 4 at one time.  2 of the MWX instructions were in this lock up mode. So I broke off  the 5th device on its own port. However, the 2 that locked up continued to do so even after I changed the port.  I had to recreate both devices before it started working again.  I didn't know about the load/reload trick.  Maybe  a utility to clean up and initialize old revisions would be nice to have? Working on long projects, I go through several revisions before its finished.

[BobO]

Maybe  a utility to clean up and initialize old revisions would be nice to have? Working on long projects, I go through several revisions before its finished.

I don't mean to imply that there is any known junk in the project to fix. There are already internal integrity checks being run, and we fix everything we learn about. We have seen some occasions where dumping the documentation has helped, and I'm speculating that going through an export/import without the binary copy of the SysConfig might restore something amiss. About the only time we ever do that in house is when alpha or beta development versions break something and we are trying to recover code.

[ATU]

Sorry, didn't intend to infer that. I didn't even know the export utility existed until today.  That is probably a better way to migrate an old project that was done several revisions ago.

[BobO]

Sorry, didn't intend to infer that. I didn't even know the export utility existed until today.  That is probably a better way to migrate an old project that was done several revisions ago.

We make every effort to transparently migrate projects when you open them. That process is usually 100% once released. If for any reason it isn't, export/import might be helpful.

The Export and Import are located on the File menu. The export format is mostly human readable text, with the exception of the SysConfig text-encoded binary. Much of the SysConfig content is exported outside of the binary, and the binary section can be omitted.

[franji1]

The best way to do it is to re-configure all your configurable devices in a new project exactly like you had.

Then do Tools->Insert Instructions from File at the Code-Block level into that NEW project.  The device names must match.

Only simple devices get imported without a #BEGIN SYSCONFIG section.  Anything with any kind of complexity requires that you have them defined via the UI.  File->Import Project would require the SYSCONFIG section to exist for any complex devices.  Hence, the Tools->Insert Instructions from File is required to get anything to import via TXT file w/non-trivial devices without a SYSCONFIG section.

[ATU]

I had this same issue again on an MWX instruction. It just sits there. It ran for weeks without issue and now its just stuck on an MWX instruction. No fault, no System error or warning. Anything you want me to check before I reboot the CPU?

[BobO]

I had this same issue again on an MWX instruction. It just sits there. It ran for weeks without issue and now its just stuck on an MWX instruction. No fault, no System error or warning. Anything you want me to check before I reboot the CPU?

Can you send me the project, so I maybe can offer some guidance?

[ATU]

Yup

[ATU]

Did you receive it?