Kindly suggest if the following marker tags can be added for defining Modbus parameter points in the library:
{
"baud": {
"dis": "Baud Rate",
"doc": "Marker tag to represent the baud rate (in bits per second) used in serial communication, typically for Modbus RTU configuration."
},
"dataBits": {
"dis": "Data Bits",
"doc": "Marker tag indicating the number of data bits used in serial communication. Common values include 7 or 8, as required by Modbus RTU."
},
"stopBits": {
"dis": "Stop Bits",
"doc": "Marker tag denoting the number of stop bits in a Modbus serial connection, generally set to 1 or 2."
},
"parity": {
"dis": "Parity",
"doc": "Marker tag to identify the parity setting for Modbus communication. Typical options include: none, even, or odd."
}
}
Rick JenningsFri 25 Jul
Hi Jayesh,
Recently in the Haystack Labs working group we have modeled aspects of communication protocols described here.
Take a look at an example of how these specs are applied in a community example here.
There is ongoing work to refine these specs and it seems you may have suggestions on how we can improve.
I would suggest you consider joining the Haystack Labs working group. See here for more details.
Jayesh Shirsath Fri 25 Jul
Kindly suggest if the following marker tags can be added for defining Modbus parameter points in the library:
{
}
Rick Jennings Fri 25 Jul
Hi Jayesh,
Recently in the Haystack Labs working group we have modeled aspects of communication protocols described here.
Take a look at an example of how these specs are applied in a community example here.
There is ongoing work to refine these specs and it seems you may have suggestions on how we can improve.
I would suggest you consider joining the Haystack Labs working group. See here for more details.
Kind regards,
Rick