For a full OPC UA data MonitoredItem queue, discardOldest true removes the oldest queued notification and appends the new one. False replaces the most recently queued value with the new value; it does not simply reject the incoming sample. Inspect the Overflow information bit and the revised queue size before interpreting a notification stream as…
An OPC UA deadband compares the current value with the last value pushed to the MonitoredItem queue, not necessarily the last sample or the last value displayed by the client. The change must be strictly greater than the threshold. For percentage deadband, the threshold depends on EURange, so a range change can alter notification behavior…
A slow OPC UA trend can be limited by three separate schedules: when the underlying source changes its exposed value, when a MonitoredItem samples it, and when the Subscription publishes queued notifications. Reducing the publishing interval cannot reveal a source update that has not happened, and reducing sampling cannot force a delayed Publish response to…
Persist a node reference using its namespace URI, identifier type and identifier value, then resolve the URI through the target server’s current NamespaceArray. Do not persist only a numeric namespace index and assume it still identifies the same naming authority after a new Session. A stale index can resolve to an existing but entirely different…
A SecureChannel supplies protected message transport; a Session supplies application-level state and user association. Renewing a channel’s SecurityToken normally keeps the same channel and Session. Recovering through a new channel requires the surviving Session to be associated through ActivateSession. Creating a new Session on every token renewal confuses two lifecycles and can unnecessarily disrupt application…
Determine whether the serial interface returns locally transmitted bytes before using received bytes as evidence of a peer response. Some Modbus operations have normal responses identical to their requests, so byte equality and a valid checksum cannot distinguish local echo from a real reply. Echo handling needs a qualified interface contract, not a rule that…
Modbus function 24, hexadecimal 0x18, returns a two-byte Byte Count, a separate two-byte FIFO Count and up to thirty-one queued register values. It is not a holding-register response with a one-byte count. Validate both counts and the exact PDU length before exposing values, and do not interpret a successful read as a dequeue operation. This…
For Modbus Read Coils and Read Discrete Inputs, the first requested item occupies bit zero of the first response data byte. Subsequent items advance toward bit seven, then continue at bit zero of the next byte. The mapping is relative to the request’s starting address; it is not aligned to an absolute eight-address boundary. This…
Model MQTT enhanced authentication as a connection-level exchange with its own phase and lifetime. Initial authentication finishes with a successful CONNACK; reauthentication finishes with a successful server AUTH. During reauthentication, other packets can continue under the previous authentication. A publish acknowledgement must not accidentally complete authentication, and a delayed authentication callback must not modify a…
A negative PUBACK or PUBREC completes the corresponding MQTT PUBLISH as an acknowledged failure; it is not an instruction to retransmit that packet. Record the reason, close the correct protocol state and route the application record to an explicit corrective policy. A successful socket write or a callback named “publish complete” cannot replace this classification….