MVI46 Slave status checking
You need to be logged in to get access to the forums. You can do so here
|
tracyfearson
|
Tuesday 06 June 2006 8:17:54 am |
|
|
MVI46 Slave status checking
I have a continuous emission monitoring system that performs a 2 step communication process for data acquisition.
The computer talks to the compact logix plc. There is communication monitoring setup for this step.
The Compactlogix PLC speaks to a MIR9000 via a Prosoft MCM module via serial modbus communication. This link has failed and stopped updating the data to the PLC several times. No error is generated by the system.
I need to setup ladder logic to output an alarm function when this link fails. I was not the person that setup the original PLC ladder logic and documentation on it is limited.
I have located a COP command with the appropriate Dest (MCM1.slaveStatus.P2.SlaveStatus[MCM1.BP.Blockindex] that according to page 81 of the manual should read the slave status.
Logic is also in the PLC to enable and disable slave polling.
There is no logic to generate an alarm on repeated comm fails.
How would I add this to the PLC?
|
|
jsanders
|
Tuesday 06 June 2006 6:20:31 pm |
|
|
RE:MVI46 Slave status checking
Please see relavent discussions from other forums at the following links:
http://prosoft-technology.com/pro...mvi56_mcm_determine_the_slave_status
http://prosoft-technology.com/pro...e_status_error_status_command_errors
http://prosoft-technology.com/pro...x/mvi69_mcm_slave_status_information
http://prosoft-technology.com/pro...rax/module_communication_error_codes
Even though not all of these discussions talk specifically about the MVI56-MCM, all ProSoft MCM modules use a similar driver and the Command Error List exists in nearly identical form on all. The explanations in these other entries thoroughly explain the use of the Command Error List as a way to monitor communications health when the ProSoft module's port is a Modbus Master.
|
