[Mikhail]

Hello,
Probably, another solution is needed in that case. Please provide screenshots of your settings for better understanding.

[Mikhail]

While in the USA the comma is used as the 1000 separator, in Europe it is the period.

Please create a new topic. Some simple actions may be needed.

[Mikhail]

Likely, the channel properties are incorrect. Make sure that the tag code of the channel is set.

[Mikhail]

Please send screenshots:
1. A screenshot of the correct command when you send it from the Administrator app.
2. Screenshot of a command when you send it with a button.

[Mikhail]

Use the Modbus parser to validate your requests.

[Mikhail]

1. I recommend to use short Tag codes for your convenience.
2. When you send a command, specify the tag code in the Command code field.
Command value is data to send, just a number.

[Mikhail]

Note that ILLEGAL DATA ADDRESS is the answer of your device.

[Mikhail]

Hello,

If you have communication logs from the previous version, compare the Modbus packets with the new version using https://rapidscada.net/modbus/

[Mikhail]

Hi,
You right, it will be useful.

[Mikhail]

Please provide screenshots of the settings, and commands sent.

[Mikhail]

Hi,

May be some other application affected network communications. Windows update also may be the cause.
I would prefer Linux for server software that needs to run 24/7.

[Mikhail]

You don’t need to add commands in the device properties. You can just write data to elements of subscriptions.

[Mikhail]

Hi,

In the Administrator app, right-click the device, choose Send command. Type the tag code as a command code and send. Does it work? If not, check a communication line log.

[Mikhail]

Link in the store is https://rapidscada.net/store/Module/en/KpDbImportPlus

[Mikhail]

Dear Bryan,

Please copy in this topic a part of a communication line log that contains error details.

[Author]

Posts