NPort Troubleshooting Guidelines Q:I often have trouble operating NPort, but how can I troubleshoot by myself? A: Moxa recommends that you follow well-defined, step by step guidelines, to troubleshoot the problem. Go To Guidelines!
NPort Hardware Examination 1.2Does NIC's "Link“ LED light up? 1.1Does NPort's “Ethernet" LED light up? 1.0NPort does not work properly 1.4Proper Operation Mode? 1.3Able to PING NPort from your host? Select ProperOP Mode
NPort Operation Mode Examination 2.0 Real Com Mode 3.0TCP Server Mode 4.0TCP Client Mode 5.0UDP Mode
2.0 Real COM Mode 2.1Able to install driver? 2.2 Able to open NPort’s Com Port? 2.0Real Com Mode 2.3Driver Advanced Functions 6.0serial Tell Engineer which point you have done!
3.0 TCP Server Mode 3.0 TCP Server Mode 3.1Remote TCP Client program connects with NPort properly? 3.0TCP Server Mode 6.0 serial Tell Engineer which point you have done!
4.0 TCP Client Mode 4.0 TCP Client Mode 4.1NPort connects with remote TCP Server program properly? 4.0TCP Client Mode 6.0 serial Tell Engineer which point you have done!
5.0 UDP Mode 5.0 UDP Mode 5.1 remote UDP program cannot Rx/Tx data properly 5.0UDP Mode 6.0 serial Tell Engineer which point you have done!
6.0 Serial Settings 6.0 Serial Settings Checklist: • Cable wiring issue • a. RS-232 : 3 or 8 wire • b. RS-422 : 4 wires point-to-point • c. RS-485 : 4 wire or 2 wire daisy-chain • Serial comm. Parameter • Must be the same as your serial device’s • Cable length • a. RS-232 : 15 m @ 9600 bps • b. RS-422 : 1.2 km @ 9600 bps • c. RS-485 : 1.2 km @ 9600 bps • RS-422/RS-485 driving Terminator Pull high / Pull low 1K or 150K • Flow control • If you use RTS/CTS, you must have correct RTS, CTS wiring. 6.0 serial
1.1 Does NPort's “Ethernet" LED light up? CASE STUDY Checklist: • Use straight-through Ethernet cable to connect NPort with HUB or Switch. • EthernetCable length < 100 meters • Ethernet port of HUB or Switch works normally
1.2 Does NIC's "Link“ LED light up? Checklist: • Use stright-through Ethernet cable to connect NPort with HUB or Switch. • NIC installed normally. • Ethernet Cable length < 100 meters. • Ethernet port of HUB or Switch works normally
1.3 Able to PING NPort from your host? Checklist: • Confirm if the IP configuration is proper 1) No router NPort & Host must be on the same network subnet. 2) Across routera) The gateway & routing must be proper use "tracert" to follow up. b) Make sure routers don't filter PING (ICMP) c) Open proper TCP/UDP ports by MOXA FAQ #441
1.4 Proper Operation Mode? Checklist: • Real COMmode by default • Select the proper NPort operation mode in the [operation setting] menu • Remember to select to make settings active [Save and Restart] / [Apply Change]
2.1 Able to install driver? Checklist: • NAT environment Use NATP mapping • Across Router/Firewall Check filter rule, open UDP port # 4800 • Connection quality Ping response time must less than 1000 ms • installation proceduresRefer to user’s manual for step by step instructions
2.2 Able to Open NPort’s Com Port? Checklist: • Across Router/Firewall? Open TCP #950(~965) & #966(~981) • Access Right Check Accessible IP Table • DHCP Issue a) Use fixed IPs for NPort & hostb) Map specific IPs for NPort & host • TCP Port occupied? Check connection status • COM port No. conflict? Check if anyone is using the same COM number • Save configuration Apply Change
2.3 Driver Advanced Functions Checklist: • Disable FIFOIf your serial device experiences serious data lost, then "disable FIFO” • Classical modeIf response time is very critical for your system, i.e. you use XON/XOFF flow control, you can use this mode. • Enable Fast FlushWith Real COM mode to avoid driver querying NPort continuously when using PurgeComm function.
3.1 Remote TCP Client program connects with NPort properly? Checklist: • Improper TCP listen port Mustmatch your TCP Client Program • DHCP Issue Use fixed IPs for NPort & hostMap specific IPs with MAC for NPort & host • IP address authorization Destination IP must be blank or match your host's IP. • TCP Port is occupied Check connection status • Router filtering Open the specific TCP port.
4.1 NPort connects with remote TCP Server program properly ? • Checklist: • Improper TCP Destination port Mustmatch your TCP Server Program • DHCP Issue Use fixed IPs for NPort & hostMap specific IPs with MAC for NPort & host • Incorrect Destination IP Must be blank or match your host's IP • Router filtering Open the specific TCP port
5.1 Remote UDP program cannot Rx/Tx data properly Checklist: • Data lost a) Purify your network traffic if possible b) Your AP must handle the resending mechanism when data is lost c) Change to using TCP Server/Client • Improper UDP port Must match your program • DHCP Issue • Use fixed IPs for NPort & hostMap specific IPs with MAC for NPort & host • Router filtering • Open the specific UDP port