SB1000 Support

Troubleshooting

• SB1000 does not power on Check the external supply and connectors, then contact support if the unit remains unresponsive.
• SB1000 Ethernet link is slow or missing Separate physical Ethernet link from IP access and check cable and switch behavior.
• SB1000 Wi-Fi is unstable or unavailable Check the 2.4 GHz network, signal conditions, credentials, and IP configuration.
• SB1000 RS485 communication is not working Check mode, request/response evidence, and wiring before using the isolated loopback self-test.
• Which TCP port should I use for an SB1000 Modbus connection? Choose the service for the physical RS485 bus. The optional SB1000 management interface is a separate service.
• TCP connects, but Modbus reads time out A TCP connection confirms access to a listener. Check whether the request reaches the correct RS485 bus and receives a valid field-device reply.
• Modbus reports “Illegal data address” or exception 02 Check the register table, address convention, and the entire requested range.
• A negative value becomes a large positive number Match the signedness and width specified by the field device, then apply its scaling.
• A float is enormous, tiny, or plausible but wrong Verify the starting register, width, actual encoding, and byte/word order against a known value.
• Values are 10, 100, or 1,000 times too large or too small Separate raw decoding, scaling, and unit conversion, and apply each once.
• A small read works, but reading a block fails Larger requests can cross unsupported addresses or exceed the field device's limits.
• Readings are frozen, delayed, or different from Diagnostics Compare actual polling, raw data, source update rate, and cache age before changing the decoder.
• SB1000 reports “A/B swapped” An address responded during the optional inverted-polarity scan. Check the physical data-line wiring and verify it with a normal scan.
• The scan reports “Conflict”, “Garbled”, or “Wrong parity” These results help narrow a fault; they are not interchangeable diagnoses.
• Scanning works, but the BMS stopped communicating Commissioning reserves the serial ports. Restore and verify normal operation after testing.
• A Modbus write is acknowledged, but the equipment does not change Check the write definition and feedback, then determine whether the field device accepted the intended action.
• The app says saved, but the SB1000 setting did not change Distinguish an NFC write from a confirmed apply result and refresh the device snapshot before retrying a conflict.
• MQTT values stop updating, or expected points never appear Check broker connection, the configured point set, and source-device communication separately.
• The network link is on, but I cannot open SB1000 Check the actual IP configuration and web service separately from the physical link.
• The BACnet system cannot discover SB1000 or its objects Separate device discovery, object configuration, and the Modbus source.
• A BACnet value is stale, unreliable, or remains at a command Inspect source quality, COV/polling, and Hold versus Follow the bus behavior.
• The phone cannot read SB1000 over NFC Check reader availability, antenna placement, scan completion, and the device's NFC policy.
• The device library is missing my model, or a library point is wrong Match the exact equipment and validate a small definition against its register map.
• Communication fails when more clients or points are added Establish a one-client baseline, then separate serial load from connection and memory limits.