A BACnet value is stale, unreliable, or remains at a command

Identify what is being displayed

  1. Read the object's reliability/status and compare with the Modbus source diagnostics. A visible value can be the last successful reading after a source failure.
  2. Check whether the COV subscription was accepted and is still active. If denied or expired, use the client's supported resubscription/polling arrangement. Check thresholds before assuming that no change notification means failure.
  3. Compare source update rate, configured polling, and available freshness information. Firmware exposing proprietary property 1306 reports time since the last successful poll.
  4. For a writable object, inspect the active write priority and whether the client has relinquished its command.
  5. Check SB1000's writable-point mode. Hold keeps Present_Value under the priority array until relinquished. Follow the bus writes a command once, then reports the field device's value.
  6. Read actual equipment feedback. A retained command, a Modbus setpoint, and physical feedback can be different points.

Expected result

The displayed value and quality reflect the intended command/readback behavior and acceptable age. Restore or release test commands afterward. Include object identity, priority/mode, source status, and timestamped values if the difference is unexplained.

Communication fails when more clients or points are added

Reduce to a measurable baseline

  1. Close unused test clients and browser sessions. Read one known-good point from one client and record response time/error counts.
  2. Add requests gradually. Several TCP clients share the serial bus; Ethernet speed does not remove RTU response times.
  3. Check polling intervals, retry counts, serial timeouts, and requests to missing devices. A client timeout that triggers retries before the previous request completes can increase congestion.
  4. Group only supported contiguous registers and respect the field device's smaller block limits and complete-value requirements.
  5. Check available device resource/status information and the installed release's connection limits. Limits can be shared across services rather than allocated separately to each port.
  6. If appropriate to the required data age, examine register caching. It can reduce repeated bus reads, but it changes freshness and does not fix a bad register definition.

Wi-Fi, TLS, browser sessions, and protocol services share device resources. Do not use a universal “points lost per feature” number as a capacity guarantee.

Expected result

The required client/point set runs with acceptable response time, freshness, and error rate. Record the smallest configuration that fails, active services, versions, polling/retry settings, and observed resource/connection messages for support.

SB1000 Wi-Fi is unstable or unavailable

Separate radio and network problems

  1. Confirm the access point offers 2.4 GHz 802.11 b/g/n service. SB1000 cannot join a 5 GHz-only network.
  2. Check SSID/password and whether the intended Wi-Fi mode is active.
  3. Compare reception outside the metal cabinet or with the access point temporarily nearer. A metal enclosure can substantially reduce signal.
  4. Check the actual DHCP/static address, subnet, gateway, and DNS. If Wi-Fi joins but local clients cannot reach SB1000, investigate routing or client isolation.
  5. Compare using Ethernet to determine whether the fault is limited to Wi-Fi.
  6. On a heavily configured unit, check resource status and other active services. Wi-Fi consumes memory, but there is no universal point-capacity deduction that applies to every configuration.

Expected result

The unit joins the intended network and remains reachable with acceptable signal conditions. If the cabinet prevents reliable radio operation, use Ethernet or revise the access-point/enclosure arrangement. Record access-point model, location/signal observations, firmware, and the exact connection stage that fails.

Readings are frozen, delayed, or different from Diagnostics

Find where the value stops changing

  1. Check that the external client is still sending reads and receiving successful responses. A displayed last value can remain after communication fails.
  2. Confirm the field device's own measurement update rate. A fast poll cannot create newer data than the device measures.
  3. Check whether SB1000's register cache is enabled. In firmware with this feature it defaults to off; its configurable lifetime is 1–60 seconds, with 5 seconds as the default when used.
  4. Inspect cache ages/hits where available. A cache hit can answer a request without a new RS485 transmission.
  5. Use a Diagnostics one-shot read of the documented point to obtain a bus request that bypasses this cache on firmware with this feature. Compare its raw reply with the client's raw result during a known field change.
  6. If both are slow, reduce competing polling and investigate absent devices, retries, serial timeouts, or another master. If the raw data changes but the display does not, examine the client point's update/deadband/display settings.

Choose polling and maximum acceptable data age for the point's purpose. A successful cached response and a fresh field measurement are different events.

Expected result

The measured delay is understood and acceptable, and communication failures are represented with appropriate quality/age in the receiving system. Include timestamps, cache settings, and raw comparisons if it is not.