issues  

Messages by Thread

• [I] [Bug]: (S7-light) Issue when reading multiple variables from the same address via GitHub
  • Re: [I] [Bug]: (S7-light) Issue when reading multiple variables from the same address via GitHub
  • Re: [I] [Bug]: (S7-light) Issue when reading multiple variables from the same address via GitHub
  • Re: [I] [Bug]: (S7-light) Issue when reading multiple variables from the same address via GitHub
  • Re: [I] [Bug]: (S7-light) Issue when reading multiple variables from the same address via GitHub
  • Re: [I] [Bug]: (S7-light) Issue when reading multiple variables from the same address via GitHub
  • Re: [I] [Bug]: (S7-light) Issue when reading multiple variables from the same address via GitHub
• [I] [Bug]: (S7-light) Issue when reading Db Addresses which are undefined via GitHub
  • Re: [I] [Bug]: (S7-light) Issue when reading Db Addresses which are undefined via GitHub
  • Re: [I] [Bug]: (S7-light) Issue when reading Db Addresses which are undefined via GitHub
• [I] [Bug]: Unhandled Netty ConnectTimeoutException via GitHub
  • Re: [I] [Bug]: Unhandled Netty ConnectTimeoutException via GitHub
  • Re: [I] [Bug]: Unhandled Netty ConnectTimeoutException via GitHub
  • Re: [I] [Bug]: Unhandled Netty ConnectTimeoutException via GitHub
  • Re: [I] [Bug]: Unhandled Netty ConnectTimeoutException via GitHub
  • Re: [I] [Bug]: Unhandled Netty ConnectTimeoutException via GitHub
  • Re: [I] [Bug]: Unhandled Netty ConnectTimeoutException via GitHub
  • Re: [I] [Bug]: Printed StackTrace for Netty ConnectTimeoutException via GitHub
• [I] [Bug]: S7 protocol leaks memory via GitHub
  • Re: [I] [Bug]: S7 protocol leaks memory via GitHub
  • Re: [I] [Bug]: S7 protocol leaks memory via GitHub
  • Re: [I] [Bug]: S7 protocol leaks memory via GitHub
  • Re: [I] [Bug]: S7 protocol leaks memory via GitHub
  • Re: [I] [Bug]: S7 protocol leaks memory via GitHub
  • Re: [I] [Bug]: S7 protocol leaks memory via GitHub
• [I] does plc4j-driver-s7 0.13.0 not support s7-200 via GitHub
• [I] [Bug]: S7 Read Request gets timed out after approximately 5-10 minutes via GitHub
  • Re: [I] [Bug]: Timeout Exceptions After 5–10 Minutes When Reading 207 Memory Blocks with S7 Protocol in v0.13.0 (Works in v0.12.0) via GitHub
  • Re: [I] [Bug]: Timeout Exceptions After 5–10 Minutes When Reading 207 Memory Blocks with S7 Protocol in v0.13.0 (Works in v0.12.0) via GitHub
  • Re: [I] [Bug]: Timeout Exceptions After 5–10 Minutes When Reading 207 Memory Blocks with S7 Protocol in v0.13.0 (Works in v0.12.0) via GitHub
  • Re: [I] [Bug]: Timeout Exceptions After 5–10 Minutes When Reading 207 Memory Blocks with S7 Protocol in v0.13.0 (Works in v0.12.0) via GitHub
  • Re: [I] [Bug]: Timeout Exceptions After 5–10 Minutes When Reading 207 Memory Blocks with S7 Protocol in v0.13.0 (Works in v0.12.0) via GitHub
  • Re: [I] [Bug]: Timeout Exceptions After 5–10 Minutes When Reading 207 Memory Blocks with S7 Protocol in v0.13.0 (Works in v0.12.0) via GitHub
  • Re: [I] [Bug]: Timeout Exceptions After 5–10 Minutes When Reading 207 Memory Blocks with S7 Protocol in v0.13.0 (Works in v0.12.0) via GitHub
  • Re: [I] [Bug]: Timeout Exceptions After 5–10 Minutes When Reading 207 Memory Blocks with S7 Protocol in v0.13.0 (Works in v0.12.0) via GitHub
  • Re: [I] [Bug]: Timeout Exceptions After 5–10 Minutes When Reading 207 Memory Blocks with S7 Protocol in v0.13.0 (Works in v0.12.0) via GitHub
  • Re: [I] [Bug]: Timeout Exceptions After 5–10 Minutes When Reading 207 Memory Blocks with S7 Protocol in v0.13.0 (Works in v0.12.0) via GitHub
• [I] [Bug]: Fix the broken Docker tests for OPC-UA via GitHub
• [I] [Feature Request]: Where is modbus batch write implemented? via GitHub
  • Re: [I] [Feature Request]: Where is modbus batch write implemented? via GitHub
  • Re: [I] [Feature Request]: Where is modbus batch write implemented? via GitHub
  • Re: [I] [Feature Request]: Where is modbus batch write implemented? via GitHub
  • Re: [I] [Feature Request]: Where is modbus batch write implemented? via GitHub
• Re: [I] [Bug]: Modbus: Reading Coils as an array returns only the first value via GitHub
  • Re: [I] [Bug]: Modbus: Reading Coils as an array returns only the first value via GitHub
  • Re: [I] [Bug]: Modbus: Reading Coils as an array returns only the first value via GitHub
• [I] [Bug]: Consumers added to PlcSubscriptionRequest are never after subscription is executed even though PlcSubscriptionEvent happens via GitHub
  • Re: [I] [Bug]: Consumers added to PlcSubscriptionRequest are never after subscription is executed even though PlcSubscriptionEvent happens via GitHub
• [I] [Bug]: Modbus - Number of threads repetitively increase at each reconnection. via GitHub
  • Re: [I] [Bug]: Modbus - Number of threads repetitively increase at each reconnection. via GitHub
  • Re: [I] [Bug]: Modbus - Number of threads repetitively increase at each reconnection. via GitHub
  • Re: [I] [Bug]: Modbus - Number of threads repetitively increase at each reconnection. via GitHub
  • Re: [I] [Bug]: Modbus - Number of threads repetitively increase at each reconnection. via GitHub
  • Re: [I] [Bug]: Modbus - Number of threads repetitively increase at each reconnection. via GitHub
  • Re: [I] [Bug]: Modbus - Number of threads repetitively increase at each reconnection. via GitHub
  • Re: [I] [Bug]: Modbus - Number of threads repetitively increase at each reconnection. via GitHub
  • Re: [I] [Bug]: Modbus - Number of threads repetitively increase at each reconnection. via GitHub
  • Re: [I] [Bug]: Modbus - Number of threads repetitively increase at each reconnection. via GitHub
  • Re: [I] [Bug]: Modbus - Number of threads repetitively increase at each reconnection. via GitHub
  • Re: [I] [Bug]: Modbus - Number of threads repetitively increase at each reconnection. via GitHub
  • Re: [I] [Bug]: Modbus - Number of threads repetitively increase at each reconnection. via GitHub
• [I] [Bug]: When reading an array of bits, the old s7 driver seems to hang. via GitHub
  • Re: [I] [Bug]: When reading an array of bits, the old s7 driver seems to hang. via GitHub
  • Re: [I] [Bug]: When reading an array of bits, the old s7 driver seems to hang. via GitHub
• [I] [Bug]: The s7 driver causes issues when writing arrays of bits via GitHub
  • Re: [I] [Bug]: The s7 driver causes issues when writing arrays of bits via GitHub
• [I] [Bug]: The block optimizer used in s7-light causes errors, if a tag references the same byte multiple times via GitHub
  • Re: [I] [Bug]: The block optimizer used in s7-light causes errors, if a tag references the same byte multiple times via GitHub
  • Re: [I] [Bug]: The block optimizer used in s7-light causes errors, if a tag references the same byte multiple times via GitHub
• [I] [Bug]: When using the new block-optimizer in the s7-light driver, when reading multiple BOOL values located in the same byte produces errors via GitHub
  • Re: [I] [Bug]: When using the new block-optimizer in the s7-light driver, when reading multiple BOOL values located in the same byte produces errors via GitHub
• [I] [Bug]: Building "with-python" if "update-generated-code" and "enable-all-checks" is active, fails via GitHub
  • Re: [I] [Bug]: Building "with-python" if "update-generated-code" and "enable-all-checks" is active, fails via GitHub
• [I] [Bug]: Building with enabled "enable-all-cheks" profiles fails on Arch Mac machines via GitHub
  • Re: [I] [Bug]: Building with enabled "enable-all-cheks" profiles fails on Arch Mac machines via GitHub
• [I] [Bug]:Eclipse Milo OPC UA server, Invalid RSA Key via GitHub
• Re: [I] [Feature Request]: ads connection problem via GitHub
  • Re: [I] [Feature Request]: ads connection problem via GitHub
  • Re: [I] [Feature Request]: ads connection problem via GitHub
  • Re: [I] [Feature Request]: ads connection problem via GitHub
  • Re: [I] [Feature Request]: ads connection problem via GitHub
• [I] [Bug]: Secure ADS with Beckhoff ADS PLC via GitHub
  • Re: [I] [Bug]: Secure ADS with Beckhoff ADS PLC via GitHub
  • Re: [I] [Bug]: Secure ADS with Beckhoff ADS PLC via GitHub
  • Re: [I] [Bug]: Secure ADS with Beckhoff ADS PLC via GitHub
  • Re: [I] [Bug]: Secure ADS with Beckhoff ADS PLC via GitHub
  • Re: [I] [Feat]: Secure ADS with Beckhoff ADS PLC via GitHub
  • Re: [I] [Feat]: Secure ADS with Beckhoff ADS PLC via GitHub
  • Re: [I] [Feat]: Secure ADS with Beckhoff ADS PLC via GitHub
  • Re: [I] [Feat]: Secure ADS with Beckhoff ADS PLC via GitHub
  • Re: [I] [Feat]: Secure ADS with Beckhoff ADS PLC via GitHub
  • Re: [I] [Feat]: Secure ADS with Beckhoff ADS PLC via GitHub
  • Re: [I] [Feat]: Secure ADS with Beckhoff ADS PLC via GitHub
  • Re: [I] [Feat]: Secure ADS with Beckhoff ADS PLC via GitHub
• [I] [Bug]: Umati Sample Server BadIdentityTokenInvalid via GitHub
• [I] [Bug]: Getting error while reading struct type node value and it's attributes via GitHub
  • Re: [I] [Bug]: Getting error while reading struct type node value and it's attributes via GitHub
  • Re: [I] [Bug]: Getting error while reading struct type node value and it's attributes via GitHub
• [I] [Bug]: Integration Issues with Rockwell ControlLogix PLC via GitHub
  • Re: [I] [Bug]: Integration Issues with Rockwell ControlLogix PLC via GitHub
  • Re: [I] [Bug]: Integration Issues with Rockwell ControlLogix PLC via GitHub
  • Re: [I] [Bug]: Integration Issues with Rockwell ControlLogix PLC via GitHub
  • Re: [I] [Bug]: Integration Issues with Rockwell ControlLogix PLC via GitHub
• [I] [Bug]: OPCUA is not authenticating with Basic256Sha256 certificate via GitHub
• [I] [Bug]: Mobus RTU nio event loop via GitHub
  • Re: [I] [Bug]: Mobus RTU nio event loop via GitHub
• [I] [Bug]: The results returned by Modbus RTU read operations are always byte arrays via GitHub
  • Re: [I] [Bug]: The results returned by Modbus RTU read operations are always byte arrays via GitHub
• [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
  • Re: [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
  • Re: [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
  • Re: [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
  • Re: [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
  • Re: [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
  • Re: [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
  • Re: [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
  • Re: [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
  • Re: [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
  • Re: [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
  • Re: [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
  • Re: [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
  • Re: [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
  • Re: [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
  • Re: [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
  • Re: [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
  • Re: [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
  • Re: [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
  • Re: [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
  • Re: [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
  • Re: [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
  • Re: [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
  • Re: [I] [Feature Request]: Force Function Code 6 when writing modbus tag via GitHub
• [I] [Feature Request]: Max Modbus Registers per Query via GitHub
  • Re: [I] [Feature Request]: Max Modbus Registers per Query via GitHub
  • Re: [I] [Feature Request]: Max Modbus Registers per Query via GitHub
  • Re: [I] [Feature Request]: Max Modbus Registers per Query via GitHub
  • Re: [I] [Feature Request]: Max Modbus Registers per Query via GitHub
• [I] [Bug]: Issue in connecting to OPCUA server after manually upgrading to 0.13.0-SNAPSHOT via GitHub
  • Re: [I] [Bug]: Issue in connecting to OPCUA server after manually upgrading to 0.13.0-SNAPSHOT via GitHub
  • Re: [I] [Bug]: Issue in connecting to OPCUA server after manually upgrading to 0.13.0-SNAPSHOT via GitHub
  • Re: [I] [Bug]: Issue in connecting to OPCUA server after manually upgrading to 0.13.0-SNAPSHOT via GitHub
  • Re: [I] [Bug]: Issue in connecting to OPCUA server after manually upgrading to 0.13.0-SNAPSHOT via GitHub
  • Re: [I] [Bug]: Issue in connecting to OPCUA server after manually upgrading to 0.13.0-SNAPSHOT via GitHub
  • Re: [I] [Bug]: Issue in connecting to OPCUA server after manually upgrading to 0.13.0-SNAPSHOT via GitHub
  • Re: [I] [Bug]: Issue in connecting to OPCUA server after manually upgrading to 0.13.0-SNAPSHOT via GitHub
  • Re: [I] [Bug]: Issue in connecting to OPCUA server after manually upgrading to 0.13.0-SNAPSHOT via GitHub
  • Re: [I] [Bug]: Issue in connecting to OPCUA server after manually upgrading to 0.13.0-SNAPSHOT via GitHub
  • Re: [I] [Bug]: Issue in connecting to OPCUA server after manually upgrading to 0.13.0-SNAPSHOT via GitHub
  • Re: [I] [Bug]: Issue in connecting to OPCUA server after manually upgrading to 0.13.0-SNAPSHOT via GitHub
  • Re: [I] [Bug]: Issue in connecting to OPCUA server after manually upgrading to 0.13.0-SNAPSHOT via GitHub
  • Re: [I] [Bug]: Issue in connecting to OPCUA server after manually upgrading to 0.13.0-SNAPSHOT via GitHub
  • Re: [I] [Bug]: Issue in connecting to OPCUA server after manually upgrading to 0.13.0-SNAPSHOT via GitHub
  • Re: [I] [Bug]: Issue in connecting to OPCUA server after manually upgrading to 0.13.0-SNAPSHOT via GitHub
  • Re: [I] [Bug]: Issue in connecting to OPCUA server after manually upgrading to 0.13.0-SNAPSHOT via GitHub
  • Re: [I] [Bug]: Issue in connecting to OPCUA server after manually upgrading to 0.13.0-SNAPSHOT via GitHub
• [I] Docs aren't verbose enough via GitHub
  • Re: [I] Docs aren't verbose enough via GitHub
  • Re: [I] Docs aren't verbose enough via GitHub
  • Re: [I] Docs aren't verbose enough via GitHub
  • Re: [I] Modbus arrays aren't supported in NiFi via GitHub
  • Re: [I] Modbus arrays aren't supported in NiFi via GitHub
  • Re: [I] Modbus arrays aren't supported in NiFi via GitHub
• [I] [Bug]: Plc4x NiFi processors can't recieve array data via GitHub
  • Re: [I] [Bug]: Plc4x NiFi processors can't recieve array data via GitHub
  • Re: [I] [Bug]: Plc4x NiFi processors can't recieve array data via GitHub
  • [I] [Bug]: Plc4x NiFi processors can't recieve array data via GitHub
  • Re: [I] [Bug]: Plc4x NiFi processors can't recieve array data via GitHub
  • Re: [I] [Bug]: Plc4x NiFi processors can't recieve array data via GitHub
  • Re: [I] [Bug]: Plc4x NiFi processors can't recieve array data via GitHub
  • Re: [I] [Bug]: Plc4x NiFi processors can't recieve array data via GitHub
  • Re: [I] [Bug]: Plc4x NiFi processors can't recieve array data via GitHub
• [I] [Feature Request]: Modbus: Support for Word Swap via GitHub
  • Re: [I] [Feature Request]: Modbus: Support for Word Swap via GitHub
  • Re: [I] [Feature Request]: Modbus: Support for Word Swap via GitHub
  • Re: [I] [Feature Request]: Modbus: Support for Word Swap via GitHub
  • Re: [I] [Feature Request]: Modbus: Support for Word Swap via GitHub
  • Re: [I] [Feature Request]: Modbus: Support for Word Swap via GitHub
• [I] PLC4X OPC UA connection succeeds, but no data sent to Kafka via GitHub
• Re: [I] [Bug]: Modbus: ModbusOptimizer doesn't check tag specific endianness via GitHub
  • Re: [I] [Bug]: Modbus: ModbusOptimizer doesn't check tag specific endianness via GitHub
  • Re: [I] [Bug]: Modbus: ModbusOptimizer doesn't check tag specific endianness via GitHub
  • Re: [I] [Bug]: Modbus: ModbusOptimizer doesn't check tag specific endianness via GitHub
• [I] Kafka Connect and OPC UA Integration via GitHub
  • Re: [I] Kafka Connect and OPC UA Integration via GitHub
  • Re: [I] Kafka Connect and OPC UA Integration via GitHub
  • Re: [I] Kafka Connect and OPC UA Integration via GitHub
  • Re: [I] Kafka Connect and OPC UA Integration via GitHub
• [I] [Bug]: Modbus: Reading single discrete-input throws ArrayIndexOutOfBoundsException via GitHub
  • Re: [I] [Bug]: Modbus: Reading single discrete-input throws ArrayIndexOutOfBoundsException via GitHub
  • Re: [I] [Bug]: Modbus: Reading single discrete-input throws ArrayIndexOutOfBoundsException via GitHub
  • Re: [I] [Bug]: Modbus: Reading single discrete-input throws ArrayIndexOutOfBoundsException via GitHub
  • Re: [I] [Bug]: Modbus: Reading single discrete-input throws ArrayIndexOutOfBoundsException via GitHub
  • Re: [I] [Bug]: Modbus: Reading single discrete-input throws ArrayIndexOutOfBoundsException via GitHub
  • Re: [I] [Bug]: Modbus: Reading single discrete-input throws ArrayIndexOutOfBoundsException via GitHub
• [I] [Bug]: Response failure with S7315-2PN/DP. The last packet is not processed. via GitHub
  • Re: [I] [Bug]: Response failure with S7315-2PN/DP. The last packet is not processed. via GitHub
  • Re: [I] [Bug]: Response failure with S7315-2PN/DP. The last packet is not processed. via GitHub
  • Re: [I] [Bug]: Response failure with S7315-2PN/DP. The last packet is not processed. via GitHub
  • Re: [I] [Bug]: Response failure with S7315-2PN/DP. The last packet is not processed. via GitHub
  • Re: [I] [Bug]: Response failure with S7315-2PN/DP. The last packet is not processed. via GitHub

• Earlier messages