Forum Replies Created
-
Posts
-
From my observations, Server Modules do not have isolation like drivers. A logical error leading to an exception will stop the Server. I tried using Thread and I ran into various problems. After that, I switched to Task, in case of an error in the task, it simply closes.
The bots in the module are called about 10 times per second, it is necessary to take this into account.Scripts can’t transfer data to devices. It is only possible to transfer to the device via the AutoControl Module, which can be configured to work in channels.
I can’t tell you about the broadcast address, probably not than yes. This should be built into the driver and is not so easy to implement (I did this on one device, but not Modbus)
I’m also in favor of a dynamic approach. Maybe there is some way to teach Mimic to work with language files located in the lang folder? and by choosing the right language, would the mnemonic scheme change the labels in the appropriate languages?
I can’t tell you who is changing the port, but the server, when sending to port 502, expects it to return to port 502.
copy the contents of the response from wireshark to modbus parser from the data block and find out. if there is an adequate response, then configure the firewall.
However, this will require advanced Mimic components (paid), specifically ExtraMarkup from the components.
You can create a circuit in the new Mimic editor and make the sound play cyclically while the page is open.
Yes, if the address requires 0 for the device, this may be the reason. Another option is to send a broadcast address to the device – 254 or 255 in Modbus mode when it is connected to TCP. Such things should be specified in the device documentation.
And start with one register, specifying in the settings to start with 0 or 1. Do you also have the exact device address = 1 ? Depending on the device, the device ID may be ignored in Modbus TCP mode, or it may have to correspond to some value.
