What could be the reason that the colors are different for two equal objects? for example in the lower image you can see the two yellow bargraphs on the left. The one from the 'Oil Press IN' has the correct color, the left one seems to be less bright. The same for the three purple ones on the right side, there it is the middle one which is normall.

@cechurat
Thank you for taking a look at it.

That's correct, these clients are still to be installed.

The idx parameter in the error message does this one refer to the clients in the config file, starting from idx=0 for the first entry?

@cechurat
In the meanwhile, I succeeded to get the communication up & running by reducing the Maxrequest value from 15 to 1.
But still with some error messages from time to time.

I do also have some Modbus clients which are already configured but not online yet. could it be that they cause some issues?

exportModbusRex_20210303.csv

modbus_cfg.rio

apollo_exec.mdl

This is the data which we want to read out :

If period is not set to 1sec then there is no data at all, only error messages.
Data from registers configured at line 17 to 21 in the above list are also not showing.

If only the first chunk of 56 registers is configured everything is working more or less fine (with socket errors from time to time)

Is there anything I can do to improve this?

In the future, we need to read the same data not from one but from four devices. Would it make sense to sort the registers in this file in such a way that there is never a consecutively reading from the same device? Or doesn't it matter what the sequence is in this list?

@cechurat The hardware is installed and now I'm trying to get the Modbus TCP communication up and running.

Data is coming in but I get these error messages regularly (I'm using the 'passive' feature) :

@cechurat

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.:

Can you try to add MTM__SDSSHE39706_Status signal?

Cheers,
Tomas

It is showing a counter (15bit) which is running down, over and over.

@cechurat

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

modbus_cfg.rio

@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.

exportLog20210203.csv

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.