The following information provides a general understanding of troubleshooting the WRG1830/ ZFR183x Pro Series Wireless Field Bus:
Symptom | Possible causes |
---|---|
The WRG does not start the network. | Confirm that the ZFR1831 Coordinator Radio is connected to the ZFR port on the WRG Gateway. |
The Network Engine cannot discover the WEFCs on the Remote Field Bus. | Confirm that the Ethernet cable from the associated Ethernet switch is connected to the Ethernet port on the WRG Gateway. |
A Network address conflict exists in which there are two WRG Gateways on the same trunk with the same Remote Field Bus Trunk address. | Verify that the Wireless Field Buss Network Address is unique and not shared by another network. |
Intermittent BACnet IP Communications. | Refer to the Remote Field Bus section of Communications Bus Technical Bulletin (LIT-12011034). |
In CCT, the controller information (or device discovery dialogue) shows an incorrect MS/TP address for a controller. |
|
Symptom | Possible cause |
---|---|
WRG Gateway is not recognized as a valid device to the NAE. | The Network Engine has to be at version 7.0 or higher to have RFB capability. NCE does not support remote field bus. |
The WRG Gateway cannot discover WEFCs. | The ZFR Coordinator Router is in a panel or not properly installed. |
WEFC does not come online. | WEFC does not have Address Switch 128 set to ON. (FEC/FAC/IOM/VMA). |
Symptom | Possible cause |
---|---|
The ZFR Router or the WRZ shows intermittent offline at the network engine. | Ensure that a wireless interference source (such as microwave oven or 2.4 GHz cordless phone) is not installed near the toggling ZFR Pro router, the WRZ, or the ZFR Pro Coordinator Radio. |
Field devices installed on the trunk have duplicate MS/TP trunk addresses. Note: An address conflict can exist between a coordinator and field controllers within the address range of 4 through 119. |
Each field controller and coordinator on the FC bus must have a unique MS/TP address. Cycle power to the controller to force the controller to start communicating with its unique address. |
The ZFR Router does not join the network. | Ensure that the PAN IDs are set correctly. |
Ensure network is open to add devices. |
Symptom | Possible cause |
---|---|
The WRG cannot see the WRZ. | The MS/TP address of the WRZ Sensor does not match the MS/TP address of the WEFC. |
The WRZ Sensor values are unreliable. | The factory calibration jumper (J5) is not installed. |