General questions about communication protocols

Router variable returns nonsense value or zero

The range of the data type that is declared on the variable may have been exceeded. The default data type is dint, int, etc. I recommend changing the data type for this variable to lreal or lint
Make sure the bus on the serial line is properly terminated
If it is a Modbus communication protocol, then it may be a bad setting to read the byte order, eg for real - 3412

Serial communication protocol returns communication error, but correct values are read in the variable browser

Check if the bus is terminated on the PLC.
Increase the maximum duration of the telegram on the communication channel - after making the change it is necessary to play the report on the PLC

After entering the Who-is query, the connection will not be anchored on the BACnet

Check your computer's firewall settings or antivirus program

When communicating via SSCP / SoftPLC link and Modbus TCP sWindowsRT there is no communication resp. the connection does not open

Check your computer's firewall settings or antivirus program

After playing the report, data from some PLCs stopped reading

Most likely, it's caused by a reference to "Data Source," which may lead to a different path. This problem can occur, for example, when playing an assembly from another PLC. Before playing the report, it is necessary to check whether the path to "Data Source" is below a valid path.

I can't communicate with sPLC over SSCP TCP

Check that the endpoint is set correctly on the SSCP TCP device or that it leads to valid data. Deploy, HwConfig or Custom.
Check if the user is set correctly on the SSCP TCP device, ie password (default data are - Engineering (admin / rw), Full Control (user / rw), Read Only (readonly / rw)) and device address

Variable viewers often display a communication error for read variables

If the data is read from time to time or write, but the variable browser sometimes displays a communication error, so try to properly terminate the bus by activating BUS-END or by inserting a 120 ohm resistor on the first and last device on the bus.
Increase the maximum telegram duration in the communication channel properties and upload the configuration.

I can't detect the device after autodetection on Modbus

Make sure you have the serial line parameters set correctly on the communication channel and recorded in the report.
Check the serial line for duplicate addresses on the device, or disconnect other devices on the bus and try auto-detection again.
Check for a short circuit.
In the communication channel properties for 'Max. telegram duration (Recovery) "increase the set value and play the report
Domat module autodetection is primarily tuned to Domat devices, and modules may not always be detected through this feature.

I can't detect devices after M-Bus autodetection

Make sure you have the serial line parameters set correctly on the communication channel and recorded in the report.
Check the serial line for duplicate addresses on the device, or disconnect other devices on the bus and try auto-detection again.
Check the bus for a short circuit
In the communication channel properties, select "Number of attempts" increase the value and upload the configuration
The device may have a primary address of "0", try detection with this setting.
Try detecting via a secondary address.

Can I communicate with the device via a secondary address?

Yes, select "Use secondary address" in the M-Bus device properties.

The calculated value, eg the energy of the zm-bus device, does not correspond to the value I observe on the m-bus device

Copy the monitor log and send it to technical support.

Communication error is sometimes read for IEC 62056-21 communication protocol data

Check that the bus is properly terminated and, if necessary, terminate it with a 120 ohm resistor.
In the report for communication protocol 62056-21, increase the "Read timeout" and play the report.

Correct data is not read via Modbus RTU / TCP

If the transmission and reception proceed without a problem, then check whether there is a problem with the address / register differences. Set the value of the register, which you read one lower or higher.