Navien LonWorks Gateway, Руководство по установке и эксплуатации

Страница: 20 / 48

20 Troubleshooting
Appendix A.1 Lost or Incorrect IP Address
1. Ensure that FieldServer Toolbox is loaded onto the local PC.
Otherwise, download the FieldServer Toolbox.zip via the Sierra
Monitor website’s Software Downloads.
2. Extract the executable file and complete the installation.
Ethernet Port
Figure 34: Ethernet Port Location
3. Connect a standard Cat-5 Ethernet cable between the user’s PC
and gateway.
4. Double click on the FS Toolbox Utility and click Discover Now
on the splash page.
5. Check for the IP Address of the desired gateway.
6. If correcting the IP Address of the gateway: click the settings
icon
on the same row as the gateway, then click Network
Settings, change the IP Address and click Update IP Settings to
save.
Appendix A.2 Viewing Diagnostic
Information
1. Type the IP Address of the gateway into the web browser or
use the FieldServer Toolbox to connect to the gateway.
2. Click on Diagnostics and Debugging Button, then click on
view, and then on connections.
3. If there are any errors showing on the Connection page, refer
to
Appendix A.3
for the relevant wiring and settings.
Figure 35: Error Messages Screen
Appendix A.3 Check Wiring and Settings
●
No COMS on Modbus RTU side. If the Tx/Rx LEDs are not flashing
rapidly then there is a COM issue. To fix this, check the following:
-
Visual observations of LEDs on the gateway (
Appendix A.4
).
-
Check baud rate, parity, data bits, stop bits.
-
Check device address.
- Verify wiring.
- Verify device is connected to the same subnet as the gateway.
- Verify the Modbus device(s) were listed in the Web
Configurator (
Section 6.2
).
●
Field COM problems:
-
If Ethernet protocols are used, observe Ethernet LEDs on the
gateway (
Appendix A.4
).
- Check dipswitch settings (using correct baud rate and device
instance).
-
Verify IP Address setting.
-
Verify wiring.
Note
If the problem persists, a Diagnostic Capture needs to
be taken and sent to support. ( Appendix A.5 )
Appendix A. Troubleshooting