( x) I am using just the Node-RED package and got modbus-serial package installed with itĭocker image running under Windows (so linux vm). Export flow and change "unitId": "2", to "unitId": 2, import the result and deployĬreated docker container with docker run -d -it -p 1880:1880 -p 10502:10502 -name mynodered nodered/node-red used docker exec to connect to it and ran npm install node-red-contrib-modbus.Attempt a query (using unit-id = 2) and it times out.Query with unit-id = 1 works successfully.Minimal reproduction of the problem with instructions Manually updating the node config (export, edit, import) to change Unit-Id from a string to number resolves the issue.Ĭhanging the Unit-Id makes the server respond to queries targeting that unit id. The data type of the given CIMPLICITY point is not supported.Changing the Unit-Id in a 'Modbus Flex Server' prevents it from responding to any queries. The next two messages give the register mapping parameters (and array size) of the current and duplicate records. I've tested the ESP32 code with aModbus Client Simulator and it is everything ok. I've read about this STATUS, and the answers were that possibly the IP Adress of the Modbus Server was incorrect, but in fact that's not true. If the two records do not specify the same Modbus data address, check the array size of the CIMPLICITY point specified in the Duplicate register mapping and ensure that sufficient data addresses are reserved.ĭuplicate point identifier detected (see next two messages).ĭetected two register-mapping records that specify the same CIMPLICITY point. The problem is that the ModbusClient DataBlock returns the ERROR parameter as TRUE, and the STATUS parameter as 16 80A4. The low register limit equals or exceeds the high register limit.ĭuplicate register reference detected (see next two messages).ĭetected two register mapping records that specify the same Modbus data address (server address and register reference). Modbus register limits record specifies an invalid pair of limits. The following message contains the record.Įnsure that the record starts with a valid record prefix or a valid comment character.įor the given type of record, some or all of the required fields are missing, or are not properly delimited.įor the given type of record, the given field is not defined or contains invalid characters.įor the given type of record, the given field specifies an invalid parameter value (for example, the value is out of range). The configuration file must contain at least one register mapping record (prefix "RM").Ĭonfiguration file contains the following invalid record (see next message).ĭetected a record that is not a comment nor a blank line nor a valid definition. The configuration file must contain a record with the prefix "IP".Ĭonfiguration file contains more than one trace log parameters record.Įnsure that the configuration file contains only one record with the prefix "TF".Ĭonfiguration file contains more than one Modbus register limits record.Įnsure that the configuration file contains only one record with the prefix "RL".Ĭonfiguration file does not contain any register mapping record. If necessary, replace the file with a backup copy, or rebuild the file using the provided template.Ĭonfiguration file contains more than one IP address parameters record.Įnsure that the configuration file contains only one record with the prefix "IP".Ĭonfiguration file does not contain any IP address parameters record. The configuration file could not be read.Ĭheck the file for invalid control characters. The following message provides more details.Įnsure that a valid configuration file exists in the required directory.Įnsure that another application is not currently using the file. ![]() ![]() The configuration file could not be opened. Because of this, the modbus server is easily overflow with socket used only for one thing. These error messages include the following:Įrror opening configuration file (see next message). The Modbus TCP Server Interface logs informational, warning, and error messages to the CIMPLICITY project status log. Hello Late answer I know, but: I had the same trouble and see the modbus system use a socket for each modbus read or write. If an error is detected, an error message is logged. Modbus TCP Server Interface Startup Error Messages On startup, the Modbus TCP Server Interface Modbus TCP Server Configuration Overview validates the contents of the configuration file. On startup, the Modbus TCP Server Interface Modbus TCP Server Configuration Overview validates the contents of the configuration file. For the most up-to-date documentation, go here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |