Use of the 'MTM__SlaveStation_Connected' signal.
-
We are using the 'MTM__SlaveStation_Connected' signal to detect if the Modbus communication is established but while everything seems to be working fine the output of this signal remains 'off'
The output of the 'Connecting' block is sometimes 'on'.
I expected that the 'MTM__SlaveStation_Connected' signal would be 'steady-on' after the communication is established.
-
Hi Kris,
you are right about the expected behaviour of the "MTM_SlaveStation_Connected" signal.
The behaviour you are facing can mean some failure in communication. Please, can you turn on all I/O driver diagnostic messages (see screenshot) and share a bit of the System Log with us? (REXYGEN Studio -> Target -> Show System log -> right click -> Export Items -> All items)
Kind Regards,
Tomas -
@cechurat Please find the logfiles below. I do have at the moment 8 Modbus slaves configured but which are not online yet. The one and only slave which is communicating is the one that is not showing 'on' when connected. Although the data is coming just fine.
-
@apollo Hi Kris,
thanks for the log. I don't see anything suspicious.
Can you send me the .rio file of the MTM configuration?I noticed that the _Fresh signal is 3-4s - why does it take so long to refresh the value?
Can you try to add MTM__SDSSHE39706_Status signal?
Cheers,
Tomas -
It is because the time is (or was) set at 5s but changing it to the default '0.00' doesn't change.
I have now another slave online and this is working fine. But with this one, I'm only using holding registers while the other one is a mix ... see .rio file attached
-
@cechurat said in Use of the 'MTM__SlaveStation_Connected' signal.:
Can you try to add MTM__SDSSHE39706_Status signal?
Cheers,
TomasIt is showing a counter (15bit) which is running down, over and over.
-
@apollo Hi Kris,
thanks for the .rio file. It says that MTM__Node0_temperature is read from Slave TS-SH-E397-01 however the signals _Connected, _Connecting and _Status refer to Slave SDSSHE39706, which is not up and running at the moment if I'm not mistaken. (and therefore Status shows time to next reconnect in ms and _Connecting is sometimes UP for a while (where while = response timeout))
Just change the auxiliary flags to MTM__TS-SH-E397-01_xxx and you should be able to see relevant information about the connection to the Slave.
Cheers,
Tomas -
Oops, my apologies for waisting your time.... stupid mistake, should have seen this.
Now it's working. BTW, how to interpret the Status value?
-
@cechurat said in Use of the 'MTM__SlaveStation_Connected' signal.:
Status shows time to next reconnect in ms
