From a connected device to your first live data
Start with the relationship between the device, gateway and host system. Then verify communication, point mapping and live values, one link at a time, when commissioning your SUNFULL product.
Start with who supplies data and who reads it
The acquisition side connects to field devices. The forwarding side connects to the host system. Check the protocol, communication role and physical interface separately.
Connect field devices to a building management system
This example connects Modbus RTU devices to a BACnet/IP system. Check the device point list, then match the gateway's acquisition and forwarding capabilities.
HVAC devices & controllers
- Device address and communication settings
- Register map and access permissions
- Actual serial interface and wiring
Modbus RTU
Acquire · Map · Forward
- Configure device communication
- Check points and data types
- Provide data through a supported protocol
BACnet/IP
Building management system
- Confirm the system's BACnet role
- Check object and instance identifiers
- Read and verify representative points
This is a selection example. BACnet forwarding hardware includes supported BAC and HMI models. Check each model's documents for acquisition coverage, interface counts and the specific BACnet protocol.
Find Modbus RTU → BACnet/IP productsProtocol support does not define the physical interfaces
Check Ethernet, RS485, RS232, CAN, KNX and two-wire MBus port counts and electrical requirements separately. Supporting a protocol does not mean every model has the corresponding physical port.
BACnet support also requires compatible communication roles
BACnet/IP, BACnet MS/TP and BACnet/SC are different connection methods. Confirm the acquisition or forwarding direction and roles such as client or server. A shared protocol name alone does not establish interoperability.
Build the first data connection in four steps
Verify a few well-understood points before adding more devices and points. This is a general commissioning sequence; consult the model's manual for the actual configuration interface and parameter limits.
- 01
Communication: connect one device first
Confirm that the device and gateway acquisition side use the same protocol and compatible communication parameters. Establish the connection before adding points.
- For serial connections, check the interface type, device address, baud rate, parity and stop bits. Follow the device manuals for wiring, termination and bus limits.
- For network connections, check addresses, subnet, ports and access permissions. Avoid IP conflicts. Cross-subnet communication requires suitable routing or protocol-specific network configuration.
Verification target: stable communication with one known device. - 02
Point mapping: give both sides the same meaning
Map acquired registers, objects or variables to points the host system can use. Point names alone do not establish what a value means.
- Check address offsets, data types, byte order, units, scaling and read/write permissions against the device point list.
- Check the forwarding-side object or variable identifiers and types. Avoid duplicates or conflicts, and verify reading first.
Verification target: a clear correspondence between device points and forwarded points. - 03
Live values: compare the device with the host system
Choose representative points that can be checked in the field. Observe whether changes travel correctly through the complete data connection.
- Compare the device display or known state with the gateway's acquired value and the host system's value. Confirm units and decimal places.
- Check update times and available quality or communication status information. Distinguish valid readings from initial values, retained values after a disconnection and errors.
Verification target: matching values with the same meaning and timing at each stage. - 04
Diagnostics & records: verify before expanding
Locate the affected part of the connection before adding more devices or points. Change one condition at a time.
- Check the device connection, acquisition status, point mapping and forwarding access in order. Use the diagnostic information provided by the equipment.
- Save or back up the verified configuration using the product's supported method. Record models, versions, topology and point lists; recheck update intervals and device load after expanding.
Verification target: a configuration and verification record that can be reviewed later.
Troubleshoot along the direction of the data
First distinguish a missing connection from an incorrectly interpreted value or a host system that has not received the data.
No response or the device cannot be found
- Check the actual physical interface, device power and wiring, then check serial settings or network reachability.
- Check the device address, protocol version and communication role. The acquisition driver must match the actual device and the model's documented support.
- If the device is reachable but the protocol still does not respond, check protocol ports, access permissions, firewall rules and device connection limits.
Communication works, but values are wrong or not updating
- Use the point list to check addresses, object types, data types, byte order, units and scaling.
- Check whether the physical value is actually changing, then compare acquisition, forwarding and software display update behavior.
- Verify one point against the field device before applying the same mapping to similar points. Avoid copying an incorrect mapping across a batch.
The gateway has data, but the host system cannot read it
- Confirm compatible forwarding protocol and system roles, and verify that the selected model supports the required forwarding function.
- Check forwarding-side addresses, identifiers, ports and mappings. For BACnet, confirm the specific protocol and network scope. For OPC UA, check the endpoint and security settings.
- Have the host system read one verified point before adding more objects, variables and devices.
Bring the site details for a clearer diagnosis
Prepare the gateway model and version, device model, network or wiring topology, acquisition and forwarding protocols, point list and error information. For product selection, include interface counts, device counts and point requirements.
+86 21 20252795