ProSoft MVI56E-MNETC Client Communication monitoring

dalporto

Lifetime Supporting Member
Join Date
Jun 2021
Location
Montreal, QC
Posts
313
Hi all.

I have a Modbus ProSoft module in my setup with a capability of 30 clients (0-29), which I'm trying to monitor the Ethernet Connection from a 1756-L82. I need to know if the link is up or down on 5-6 Modbus Ethernet devices. Each device will be located on a different "client".

So far I found that I need to set / pick the client I want to update using MNETC.STATUS.ClientID (0-29) then trigger the MNETC.STATUS.ClientStatsTrigger bit each time:

1714567607377.png

This will give me something like that:

1714567558274.png

So if I kill the comm on one client and I ask that said client while the comm is down, I will get something different than "0" on MNETC.STATUS.ClientStatus[0].CurErr. In that case when I force a full download in the Schneider PLC I'm polling on client 0, that would give me a 1 like you can see on MNETC.STATUS.ClientStatus[0].LastErr, which is kind of weird if I compare it with the doc that I'm not sure if I understand correctly since it doesn't make much sense with those tables:

1714567847222.png
1714567957173.png
1714567866622.png
1714567980165.png

First, is that the proper way to monitor the communication? Since it's not "live data" I'll need to write something to have it scan each client I'm using and trigger the stupid bit periodically, which seem counter-productive.

I can setup an heartbeat on some of the devices I'll be polling, but not all, so I'll need to find a way to monitor those anyway.

I'll probably ask ProSoft at some point, but so far I got answers from them that aren't any clearer or helpful that what's in their manuals, it's often cryptic.

Thanks.
 
I have some experience with MNET/MCM modules and we use the Command Error to monitor communication status. If Command Error pointer is not equal to zero then enable a Timer to trigger an alarm after 30 seconds. The most common problem we see on MCM (RS485) is Error -11.

I have not set this up on an MNETC but it appears to me that you could use the Client Status.CurrErr for this as long as you only have one device per Client. If you had multiple devices per client and you only cared about one of the module status's this could be a problem as I'm sure it would cause an error if one out of two were not communicating.

Another option would be to use the Response data by moving ClientStatus.Responses into another integer and if the two become equal for say 10-30 seconds then you know there is nothing responding because that should be constantly changing to not allow your timer to be done.
 

Similar Topics

Hi all. I just received my brand new Prosoft Modbus modules and I'm playing with one in a L82 rack. I managed to set it up well enough so I...
Replies
4
Views
814
Controller: 1756-L84E v.35 Prosoft MVI56E-MNETC for ModbusTCP/IP I'm having an issue with some of my write commands. The write command that...
Replies
3
Views
488
Hi All, I just wanted to confirm something regarding this module. What I understood from the manual, is that if RS-485 mode is selected (jumper...
Replies
2
Views
597
Hi all, I wonder what's the best type of cable to use for RS-485 2 wire + GND That is, Data+, Data- & GND I know that Belden 9841 (not...
Replies
10
Views
1,528
Does anyone have and is able to share a firmware file for the ProSoft MVI56E-MNET module (Modbus module for a Rockwell PLC)? I have an...
Replies
0
Views
1,569
Back
Top Bottom