MVI56-MCMR Comm Fail Detection
You need to be logged in to get access to the forums. You can do so here
|
cjblake
|
Monday 11 December 2006 8:13:17 am |
|
|
MVI56-MCMR Comm Fail Detection
I received a reply to this but it was in terms of the MCM module. I believe the situation is different for the MCMR. The User-Defined data structures are different between the MCM and the MCMR. I still do not understand if I need to perodically toggle the MCMRCmdExecute[0] bit in the first rung of the MSG_BLKS ladder routine.?? It appears that I do in order to get the Status from the module. I have been watching the different points in the Tag Database trying to determine what parameter will change when I disconnect and re-connect the cable to the slave device. There is a Port1Current Error Status that seems reasonable to use but it does not appear to be consistent in the status.
I appreciate your help.
|
|
jsanders
|
Thursday 14 December 2006 4:05:53 pm |
|
|
RE:MVI56-MCMR Comm Fail Detection
Yes, there are some differences in the way the MCM and the MCMR bring in general module status information. In the MCM, the status is updated as part of every new Local:1:1.Data input image. To get the same information for the MCMR, you have to request it with the special MSG rung and you do have to toggle the trigger bit whenever you want it updated.
HOWEVER....
To get the best communication health information for either the MCM or MCMR module when the module is a Master, you would want to use the Command Error Pointer to put the Command Error List into your Read Data area, and hence it shows up in the ReadData array. The setup for this is the same for the MCM or the MCMR. This uses a different mechanism; and , therefore, does not require toggling the MSG in the MCMR.
If the MCM or the MCMR are being used as Slaves, you will have to resort to using the general Status information, already discussed.
|
