issues  

Messages by Thread

• [I] [Bug]: Cannot invoke "Object.getClass()" because "value" is null via GitHub
  • Re: [I] [Bug]: Cannot invoke "Object.getClass()" because "value" is null via GitHub
  • Re: [I] [Bug]: Cannot invoke "Object.getClass()" because "value" is null via GitHub
• [I] [Feature Request]: Go - support s7 reading via GitHub
  • Re: [I] [Feature Request]: Go - support s7 reading via GitHub
  • Re: [I] [Feature Request]: Go - support s7 reading via GitHub
  • Re: [I] [Feature Request]: Go - support s7 reading via GitHub
  • Re: [I] [Feature Request]: Go - support s7 reading via GitHub
• [I] [Bug]: Vulnerability analysis reports com.fasterxml.jackson.core:jackson-core:2.19.2 with GHSA-72hv-8253-57qq via GitHub
  • Re: [I] [Bug]: Vulnerability analysis reports com.fasterxml.jackson.core:jackson-core:2.19.2 with GHSA-72hv-8253-57qq via GitHub
• [I] [Feature Request]: show the name of PLC in logged warnings via GitHub
  • Re: [I] [Feature Request]: show the name of PLC in logged warnings via GitHub
• Re: [I] [Feature Request]: Java Canopen - Sending NMT Commands via GitHub
• [I] [Bug]: PlcConnectionException: Unsupported transport tcp when upgrading from 0.11.0 to 0.13.1 via GitHub
  • Re: [I] [Bug]: PlcConnectionException: Unsupported transport tcp when upgrading from 0.11.0 to 0.13.1 via GitHub
• [I] [Bug]: Modbus TCP hiccup when another connection is established via GitHub
  • Re: [I] [Bug]: Cached Modbus TCP hiccup when another connection is established via GitHub
  • Re: [I] [Bug]: Cached Modbus TCP hiccup when another connection is established via GitHub
  • Re: [I] [Bug]: Cached Modbus TCP hiccup when another connection is established via GitHub
  • Re: [I] [Bug]: Cached Modbus TCP hiccup when another connection is established via GitHub
• [I] [Bug]: java.lang.NullPointerException via GitHub
  • Re: [I] [Bug]: java.lang.NullPointerException via GitHub
  • Re: [I] [Bug]: java.lang.NullPointerException via GitHub
• [I] [Bug]: NullPointerException via GitHub
  • Re: [I] [Bug]: NullPointerException via GitHub
• [I] [Bug]: some asymmetry in tag-handling via GitHub
  • Re: [I] [Bug]: some asymmetry in tag-handling via GitHub
  • Re: [I] [Bug]: some asymmetry in tag-handling via GitHub
  • Re: [I] [Bug]: some asymmetry in tag-handling via GitHub
  • Re: [I] [Bug]: some asymmetry in tag-handling via GitHub
  • Re: [I] [Bug]: some asymmetry in tag-handling via GitHub
  • Re: [I] [Bug]: some asymmetry in tag-handling via GitHub
• [I] [Bug]: can't connect modbus-rtu via GitHub
  • Re: [I] [Bug]: can't connect modbus-rtu via GitHub
• [I] [Feature Request]: better error message when data-content doesn't mach data-spec in S7 via GitHub
  • Re: [I] [Feature Request]: better error message when data-content doesn't mach data-spec in S7 via GitHub
  • Re: [I] [Feature Request]: better error message when data-content doesn't mach data-spec in S7 via GitHub
• [I] [Feature Request]: Add polling interval for CHANGE_OF_STATE subscription type via GitHub
  • Re: [I] [Feature Request]: Add polling interval for CHANGE_OF_STATE subscription type via GitHub
  • Re: [I] [Feature Request]: Add polling interval for CHANGE_OF_STATE subscription type via GitHub
  • Re: [I] [Feature Request]: Add polling interval for CHANGE_OF_STATE subscription type via GitHub
  • Re: [I] [Feature Request]: Add polling interval for CHANGE_OF_STATE subscription type via GitHub
• [I] [Bug]: Using the real Netty Reactor model saves resources and reduces resource leaks via GitHub
  • Re: [I] [Bug]: Using the real Netty Reactor model saves resources and reduces resource leaks via GitHub
  • Re: [I] [Bug]: Using the real Netty Reactor model saves resources and reduces resource leaks via GitHub
  • Re: [I] [Bug]: Using the real Netty Reactor model saves resources and reduces resource leaks via GitHub
  • Re: [I] [Bug]: Using the real Netty Reactor model saves resources and reduces resource leaks via GitHub
  • Re: [I] [Bug]: Using the real Netty Reactor model saves resources and reduces resource leaks via GitHub
  • Re: [I] [Bug]: Using the real Netty Reactor model saves resources and reduces resource leaks via GitHub
• [I] [Bug]: S7 STRING handling via GitHub
  • Re: [I] [Bug]: S7 STRING handling via GitHub
  • Re: [I] [Bug]: S7 STRING handling via GitHub
  • Re: [I] [Bug]: S7 STRING handling via GitHub
  • Re: [I] [Bug]: S7 STRING handling via GitHub
  • Re: [I] [Bug]: S7 STRING handling via GitHub
  • Re: [I] [Bug]: S7 STRING handling via GitHub
• [I] [Bug]: An exception occurred when the connection was closed while using a network proxy, resulting in a thread leak. via GitHub
  • Re: [I] [Bug]: An exception occurred when the connection was closed while using a network proxy, resulting in a thread leak. via GitHub
• [I] [Bug]: outdated entity used in pom.xml via GitHub
  • Re: [I] [Bug]: outdated entity used in pom.xml via GitHub
• [I] [Bug]: Connection is not possible - Unable to find endpoint matching via GitHub
  • Re: [I] [Bug]: Connection is not possible - Unable to find endpoint matching via GitHub
• [I] How does modbus-tcp read the string type defined by the plc? via GitHub
  • Re: [I] How does modbus-tcp read the string type defined by the plc? via GitHub
• [I] [Bug]: When user and password is required to log in, but no user password is provided, the connection to opcua hangs. via GitHub
  • Re: [I] [Bug]: When user and password is required to log in, but no user password is provided, the connection to opcua hangs. via GitHub
  • Re: [I] [Bug]: When user and password is required to log in, but no user password is provided, the connection to opcua hangs. via GitHub
• [I] [Bug]: Invalid lenByte - Issue connecting to Eclipse Milo OPC UA server with 4096-bit certificate using PLC4X SDK via GitHub
• [I] [Bug]: Invalid address cause Null Pointer Exception via GitHub
  • Re: [I] [Bug]: Invalid address cause Null Pointer Exception via GitHub
  • Re: [I] [Bug]: Invalid address cause Null Pointer Exception via GitHub
  • Re: [I] [Bug]: Invalid address cause Null Pointer Exception via GitHub
  • Re: [I] [Bug]: Invalid address cause Null Pointer Exception via GitHub
• [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
  • 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
  • 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
  • Re: [I] [Bug]: Fix the broken Docker tests for OPC-UA via GitHub
  • Re: [I] [Bug]: Fix the broken Docker tests for OPC-UA via GitHub
  • Re: [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
  • 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
  • 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
  • Re: [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
  • 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

• Earlier messages