Applies to: IP Voyager, user guide 3500883-0001 Rev D. Not Voyager NEO or IP+.
Work through these checks
Read the BDU indicators
Green Power means BDU powered; green GPS means a valid position; green Network means connection established. Red Fault calls for details in the web interface. Record which lights are present.
What the result means: Each named light answers a different question: power, valid location, network connection or a detected fault. A green Network light does not by itself show that the affected application delivered data. For red Fault, retain the web status detail rather than assigning an antenna diagnosis from the colour alone.
Read local Home status
From an authorized Ethernet/WLAN client, open http://192.168.128.100 if that documented address remains valid. Read Network Status and GPS position validity; direction/elevation stay blank until GPS is obtained.
What the result means: A responding local page confirms access to the terminal interface, not the complete satellite path. Blank satellite direction/elevation fields can reflect missing GPS position. In the separate Status window, Signal Quality and Signal Strength measure different things; different levels are normal and are not alone a fault verdict.
Record before changing profiles
Capture fault wording and time privately. Ethernet and Wi-Fi use separate subnets. Do not copy one interface’s static settings to the other or use Quick Connect merely as a test.
What the result means: A problem confined to one local interface needs that interface’s existing address and gateway context. Pair those observations with the exact current status code and original summary log for support. Quick Connect, Reset Terminal and Restore Factory Defaults change operational state; none is needed to preserve these observations.
When to stop and get help
Keep 1 m from ADU sides/top and 20 cm from WLAN antenna. Stop during electrical storms. No enclosure work, PIN guesses, reset, paid streaming or APN changes. Installation faults need qualified service.
What to tell support
Before contacting support, record the exact Rev D terminal identity, software version, time of failure, Power/GPS/Network/Fault lights, Home network state and GPS validity. Identify whether Ethernet or WLAN is affected and preserve the current address/gateway privately. For a data failure, include requested and actual rate, profile state and exact status code. Save the terminal summary log through Properties; collecting evidence does not require Reset Terminal, Restore Factory Defaults or a new paid connection.
Common questions
How can the fault evidence be saved?
Rev D describes Properties > Extract Terminal Summary Log. Save the original file privately with the fault time and software version. This is separate from Reset Terminal and Restore Factory Defaults; do not select either to collect a log.
Why can the actual data rate differ from the requested rate?
Home shows both; subscription and capacity can constrain allocation. In Fixed Rate streaming, an unavailable requested rate denies the connection. Record both rates and profile state for support instead of raising the rate or changing a paid streaming profile.
Do status codes 14 and 16 mean an antenna failure?
Rev D associates 14 with service authorization and 16 with an unsubscribed service option/APN settings. Ask the provider to check the account and provisioned parameters. These codes alone do not establish an antenna defect; preserve the current configuration.
Can a changing signal meter or stopped data have another explanation?
Rev D says the meter varies with channel type. It also identifies overheating as one cause of stopped data despite a connection. Let an overheated unit cool and involve authorized support; do not open it or assume every fluctuation requires antenna realignment.
Why does Wi-Fi work while Ethernet receives no address?
IP Voyager 3500883-0001 Rev D, printed page 10, separates Ethernet DHCP from the dedicated WLAN DHCP server. Working Wi-Fi does not establish that Ethernet DHCP is enabled. Record the affected interface and its address and gateway privately. Ask the network administrator to inspect the existing Ethernet DHCP setting: when disabled, Ethernet clients require the configured static addressing scheme. The Ethernet and WLAN subnets must differ. Do not invent addresses, change NAT/Relay mode or reset the terminal to test this.
Original troubleshooting guidance based on the official sources below. Menu names can change. This is an independent guide, not a manufacturer service bulletin or a bench-tested repair.
