| Key | Issue Type | Summary | Resolution | Note |
|---|---|---|---|---|
| MODBUS-277 | Bug | Exception with Modbus FB in some special circumstances |
Fixed | |
| MODBUS-272 | Bug | Status Icon of Modbus TCP Server is not updated, if no request is sent after reconnect |
Fixed | |
| MODBUS-267 | Bug | ModbusFB library - RTU Master - COM port cannot be opened after a new download |
Won't Fix | [[GENERAL]] SysCom issue. Only appears on secific runtime. => Not related to modbus. |
| MODBUS-261 | Improvement | Modbus: Library Properties for Online Help |
Fixed | |
| MODBUS-260 | Improvement | Add a possibilty to allow Unit ID 0 |
Won't Fix | [[GENERAL]] 0xFF is the correct value for UnitID that a Client shall use (see spec). UnitID = 0 is used for Broadcasts. A Server (that is not a TCP/Serial) Gateway can accept UnitID = 0. It must accept 0xFF. So your device is faulty. |
| MODBUS-256 | Bug | ModbusFB SysComHandler.SendAsciiFrame calculates incorrect LRC |
Fixed | |
| MODBUS-244 | Epic | Modbus TCP Master: Support Redundant TCP-Connection |
Fixed | |
| MODBUS-239 | Epic | Modbus Client: CPU redundancy support |
Fixed | |
| MODBUS-237 | Improvement | Publish state information from Modbus devices |
Fixed | |
| MODBUS-236 | Improvement | IoDrvModbus: newer versions require SysTimeRtcGet |
Cannot Reproduce | [[GENERAL]] Only very legacy version affected. Newer version don't require the SysTiemRTC lib anymore. Anyway: this is not a bug. It's an obsoletey requirement. |
| MODBUS-235 | Bug | Modbus TCP Master: cable redundancy: check/align timing when connection is lost |
Won't Fix | [[GENERAL]] Obsolete: Behaviour will change due to implementation of "Preferred Line" features for Modbus Redundancy |
| MODBUS-234 | Bug | Modbus Function Blocks library: Server.Start logs wrong supportedFCs |
Fixed | |
| MODBUS-233 | Bug | Function Block: ModbusServer doku correction |
Fixed | |
| MODBUS-230 | Bug | Modbus TCP Master: Response Timeout Delayed by 2 Sec |
Fixed | |
| MODBUS-226 | Bug | Exception in SysComRead Results in CheckRequest |
Fixed | |
| MODBUS-222 | Improvement | ModbusFB for ModbusTCP should usable if no SysCom is available on the runtime system |
Fixed | |
| MODBUS-197 | Improvement | Modbus Standalone API: Add license metric attributes |
Fixed | |
| MODBUS-189 | Improvement | Documentation is missing for MAX_MODBUS_CHANNELS |
Fixed | |
| MODBUS-130 | Bug | Modbus TCP Slave: With RTE and LwIP stack socket could not be opened after Reset warm or cold |
Won't Fix | [[GENERAL]] Must be fixed in the RTE runtime system. Therefore won't fix |
| MODBUS-53 | Improvement | QoS / counter information for each channel |
Won't Fix | [[GENERAL]] The needed information is already provided by the function block that represents the client. |