Skip Navigation LinksHughesNet KB
1277 
State Codes 
Last modified on
2/4/2011 2:42 PM 

Introduction:

The following tables show State Codes and the corresponding message that is displayed for your satellite modem.

Quick Links:

For DW40x0, DW60x0, DW7x00, HN7x00S satellite modem Rx Codes, click here.
For DW40x0, DW60x0, DW7x00, HN7x00S satellite modem Tx Codes, click here.
For HN9x00 satellite modem, click here.

Procedure/Solution:

Rx Codes DW40x0, DW60x0, DW7x00, HN7x00S<
Numeric Rx Code Message Displayed Platforms Comments / Root Cause
0 The receiver is not connected. DW4000 This should be a transient state at startup or if the IRU is not connected.
1 The receiver is in pointing mode. All Indicates that the user is performing antenna pointing. In this mode, the transmitter is disabled for safety reasons since the installer is working near the antenna.
2 The receiver is in factory or NOC mode. All This status is for testing purpose only and should not been seen by users.
3 The receiver is not locked to a signal. All Indicates that the terminal is unable to lock to the outroute signal. In this case, SQF is greater than 0 but less than 30. Can occur if:
  • There is a weather outage at the site or at the NOC.
  • The antenna is mispointed.
  • The LNB is not operating correctly, either due to the connection via cable to the receive connector or due to an LNB failure.
  • There is an outroute issue at the NOC.
4 The receiver is locked to the wrong network. All Occurs if the receiver is locked to an outroute that is different from what is configured on the terminal. SQF = 30 in this case. Typically happens in a new install, if a user gets moved to a different satellite as part of recommissioning, or if configuration information gets corrupted.
5 The receiver is operational. All This is a normal operating state where the receiver is receiving data from the NOC. This is the only state when the transmitter will operate normally.
6 The receiver is not detecting any signal. HN7000S Indicates that there is something faulty between the LNB and the receive connector. This could be due to problems in the LNB, cables, receive connector, or receive unit.
7 The receiver is locked to a unknown network. All Indicates that the receiver is locked to a non-HughesNet outroute or (rarely) that the timing unit is not working on this outroute.
8 The receive cable and transmit cable are switched. HN7000S Indicates that the receive cable is plugged into the "SAT OUT" connection and transmit cable is plugged into the "SAT IN" connection.
9 The receive cable is shorted. HN7000S Indicates that the receive cable is shorted. This occurs when the center (inner) conductor is touching the external braid (outer conductor). It could also indicate internal hardware failure.

Back to Top

Tx Codes DW40x0, DW60x0, DW7x00, HN7x00S

For information related to a Tx code, click the corresponding link:

 

TxCode Message Displayed Platforms Comments/Root Cause
TxCode0 The transmitter is not connected to the receiver DW40x0 If this state persists for at least 10 seconds, it indicates that either the user has not installed a two-way system or there is a problem in the connection between the IRU and ITU. If an ITU is present on the system and none of the ITU LEDs are lit or flashing, then one of the following is likely the cause:
  • IRU-ITU cable not properly connected to the IRU or ITU
  • Incorrect power supply is being used
  • Bad IRU-ITU cable
  • IRU Failure
TxCode1 The transmitter has been disabled by the Network Operations Center All This status appears when a unit is disabled. If the NOC does not support automated cross-polarization, the unit is disabled when first installed onto the network and must be manually enabled by the network operations center once the installer has met the cross-polarization and installation specs and requests that the NOC enable the unit. A unit may be disabled for short periods of time by the NOC for service troubleshooting or if any virus activity is seen from the site. It may also be disabled if the user discontinues two-way service.
TxCode2 The transmitter has been placed in test mode by the Network Operations Center All This state occurs when the NOC staff places the unit into special transmission modes to measure the performance of a user's unit. One example is that cross-polarization requires that a special continuous carrier by transmitted by the unit. When in this mode, the unit is unable to transmit user traffic to the NOC.
TxCode3 The transmitter is locking to the receive carrier. The transmitter is locking to the receive carrier All This status should correlate to one of the following issues: Upon initial startup or locking to the receive carrier, this is a normal state for up to 15 seconds. DW40x0s 4.2 and higher (DW4000 4.2 and higher) try to automatically recover from this state.
TxCode4 The transmitter is not responding to commands sent from the receiver DW40x0s This indicates that there is something not properly operating in the IRU/ITU configuration. DW40x0 (except DW4000) attempt to recover from this state automatically. DW4000 shows a DiagApp message from where corrective action can be executed.
TxCode5 The transmitter is not locked to the network timing All This may occur due to weather related issues, installation problems, unit problems or due to NOC-related service issue. If SQF is in the 30s, this may occur due to loss of a large number of timing messages
TxCode6 The transmitter is not available because the receiver is not detecting a signal or is not locked to the correct network All This status should correlate to the receive status indicating a problem.
TxCode7 The transmitter is not available because the satellite receiver is not tuned for normal operation All When the unit is placed into special modes like antenna pointing mode, then the unit cannot transmit.
TxCode8 The transmitter is available All This is the normal operational state of the transmitter if it is installed. The unit is available for transmitting user data.
TxCode9 The transmitter is adjusting for optimal network timing All The unit is currently in a special mode where it measures its power and timing and is adjusting both to properly operate in the network. When in this mode, the transmitter is able to send small amounts of data (~1-2kbps). It will enter this mode at installation until it succeeds. It may enter this mode at NOC operator command or when the antenna is installed into a different location and repointed using the antenna pointing program. This is a normal state for a unit when it is first installed
TxCode10 The transmitter is unable to communicate with the Network Operations Center All This state indicates that the unit is not able to transmit user data because of a large number of packets unable to be received by the NOC. This could be a result of weather conditions causing lost packets or NOC equipment failure.
TxCode11 The transmitter is not available because the receiver software is out of date All This state indicates that the terminal software is not recent enough to operate on the network. New software will be required from time to time due to network infrastructure and capability upgrades. The system will always back-support software for a period of time, but may at times obsolete software to ensure maximum network efficiency.
TxCode12 The transmitter is not receiving network control messages from the Network Operations Center All This state indicates a NOC equipment outage on the server that controls return channel bandwidth.
TxCode13 The transmitter is unable to range because it cannot communicate with the Network Operations Center All Requests to range are not making it to the NOC. This state may indicate many root causes:
  • NOC does not receive ranging information from the unit.
  • The unit is unable to achieve enough transmit power for the NOC to receive.
  • Timing is incorrect due to entering the improper zip code or latitude/longitude information.
  • Transmit ODU is not properly operating or is not properly connected to the unit
TxCode14 The transmitter is not available because ranging has failed All This state indicates that the NOC was unable to complete ranging for the site. This likely indicates that ranging capability is not currently operating correctly in the NOC.
TxCode15 The transmitter is waiting for a ranging request to be processed by the Network Operations Center All This state occurs if the system (esp. DNCC) is busy with adjusting power and timing for other users. This can also occur due to problems on the Aloha inroute or due to misconfiguration of inroutes
TxCode16 The transmitter is waiting for a transmit request to be processed by the Network Operations Center All This state occurs if the system (esp. DNCC) is overloaded with users going active and is unable to provide bandwidth to a user going active. This can also occur due to problems on the inroutes or due to misconfiguration of inroutes.
TxCode17 The satellite transmitter is unable to obtain an available transmission rate All This occurs if the unit cannot successfully range at any of the available inroute rates.
The possible causes are:
  • In case of DW40x0s, ITU may be first generation and the system may not support 128K inroutes. In this case, the ITU must be replaced.
  • Unit could not achieve enough power to transmit on the lowest available inroute rate. This is likely caused by an installation/transmit power problem or due to bad weather or obstruction in front of antenna.
  • Cumulative Aloha Metric for a particular rate went to zero.
TxCode18 The transmitter is requesting a transmit pointing test All The unit is in this state when it sends a request to the NOC for an ACP test and has not yet received the response from the NOC. This can occur if:
  • Inroute group may be misconfigured
  • ACP server may be down or having problems
TxCode19 The transmitter is queued for a transmit pointing test All The unit is in this state when the ACP test cannot be started right away due to other units in the system performing the same test.
TxCode20 The transmitter is performing a transmit pointing test All The unit is in this state when either an ACP test is being performed manually or the periodic ACP test is in progress. If this is manual ACP, the unit remains in this state until the user exits pointing mode or the NOC times out the pointing. If this is the auto ACP test, the unit should exit the state at the completion of the test. If this is the periodic test, it should exit this state within 5 seconds.
TxCode21 The transmitter is disabled because a transmit pointing test failed All The unit failed the ACP test, which means that it did not meet the specifications required by the satellite provider for cross-pol versus co-pol. This can occur during:
  • initial installation
  • an upgrade/RMA process that required ACP (antenna could have been manually cross-poled in the past)
  • troubleshooting that initiated ACP test.
TxCode22 The transmitter is disabled because a transmit pointing test cannot be performed All This may occur if:
  • Inroute group being used by the terminal is misconfigured
  • ACP server is not operational correctly
TxCode23 The transmitter is disabled pending a transmit pointing test All Units will only enter this mode on systems that support periodic ACP revalidations. The unit is expected to be in this mode for typically no more than 2 minutes (based on the short randomization interval configured in the ACP server) at periodic intervals. This is also likely to occur upon powerup after the unit has been turned off for more than a day. If the unit remains in this state for more than 2 minutes, then the ACP server in the NOC is likely experiencing an outage
TxCode24 The transmit cable is not connected HN7000S This may occur if:
  • Transmit cable is not plugged securely
  • Transmit cable is not plugged into the antenna securely
  • The Transmit (aka Satellite Out) connector is loose or damaged
  • Transmit cable is damaged
  • Antenna connector or antenna is damaged.
    Note: In the past, you would have seen Tx10/13. Tx 24 replaces Tx10/13 for some of the local install issues. Not seeing Tx24 doesn't guarantee that the cable or ODU/radio is good
TxCode25 Uplink reset is in progress DW7000 & HN7000S Series This may occur if:
  • The uplink sequencer cannot complete the initialization process within the max time allowed.
TxCode26 No inroute groups support Closed Loop Timing DW7000 & HN7000S Series This may occur if:
  • The NOC is configured incorrectly and the available inroutes to the unit does not support CLT.
  • The unit is configured incorrectly and should not have CLT enabled.
TxCode27 The transmit cable and receive cable are switched. HN7000S This may occur if:
  • The receive cable is plugged into the SAT OUT connection and transmit cable is plugged into the SAT IN connection.

Back to Top

HN9000 State Codes

Click the State Code below to view the associated information.

HN9X00 State Code HN9X00 State Name HN9x00 Phase >Explanation >Troubleshooting/Additional Information
1 Starting Up in Boot Commissioning The HN9X00 is starting up in Boot phase. Initial code that is displayed if the System Control Center has been accessed and the unit is initially being powered up or after a hard reboot.
2 Waiting for Installation Parameters Commissioning This code occurs ONLY if the HN9X00 is not yet installed and the installation parameters have not yet been submitted. This code should be displayed when the System Control Center (SCC) has been accessed and the installation parameters have not been entered for installation.
3 Coarse Pointing in Progress Commissioning This code occurs during HN9X00 installation ONLY. Antenna pointing is in the progress of coarse or fine pointing. The site is in the process of the installer doing coarse or fine pointing the antenna.
4 Acquiring Beacon in Boot Commissioning This code occurs during auto indoor unit (IDU) replacement ONLY. The HN9X00 is searching for a beacon. This code occurs when the user is replacing a unit and should last for only a short period of time, followed by State Code 7.
5 Acquiring PTP SNR in Boot Commissioning This code occurs during auto IDU replacement ONLY. The HN9X00 is searching for a point to point signal. This code occurs when the user is replacing a unit and should last for only a short period of time (but longer than State Code 4), followed by State Code 7.
6 Waiting for Uplink Polarization Change Commissioning This code occurs during HN9x00 installation ONLY. The HN9X00 is waiting for installer switching uplink polarization. This code occurs only during installation. A polarization change is needed.
7 Downlink Established in Boot Commissioning The HN9x00 is in Boot phase. Downlink has been established i.e., The beacon is being tracked and TIPs are being received. This code occurs when the satellite establishes contact with the unit in Boot Phase.
8 Waiting for MIPs in Boot Commissioning The HN9X00 is in boot phase and is waiting for indirect and direct Management Information Packets (MIPs). The unit is in Boot Phase and is receiving second set of data.
9 Downloading Commissioning Software Commissioning The HN9X00 is in boot phase and is downloading commissioning software. The unit is in Boot phase and is downloading the commissioning software.
10 Waiting for Antenna Pointing Complete Commissioning This code occurs during HN9X00 installation ONLY. The HN9X00 is waiting for antenna pointing validation to complete This code occurs immediately if antenna pointing is not completed after code 9. The unit is waiting for the installer to confirm that antenna pointing is complete.
11 Starting Up in Commissioning Commissioning The HN9x00 is starting up in Commissioning phase. This code occurs after the unit verifies the downloaded commissioning software and antenna pointing is complete.
12 Downlink Established in Commissioning Commissioning The downlink has been established i.e., the beacon is being tracked and TIPs are being received. This code occurs immediately after code 11, TIPS are being received.
13 Waiting for MIPs in Commissioning Commissioning The HN9X00 is in commissioning phase and is waiting for indirect and direct MIPs. This code occurs immediately after code 12, MIPS are being received.
14 Probing in Progress Commissioning This code occurs during installation ONLY. Probing is the process used to determine the required timing and power offsets from nominal values that the terminal has to apply for optimal operation. This code occurs immediately after code 13, MIPS are being received. The remote site is attempting to set power levels for satellite communication (ranging). This state occurs if new installation parameters were entered in the Boot phases.
15 Probing Failure Commissioning This code occurs during installation ONLY. Probing has failed. This code occurs if a probing (ranging) error occurs.
16 Registering HN9X00 Commissioning The HN9X00 is registering. The unit has completed all prerequisites.
17 HN9X00 Registration Failure Commissioning Registration has failed. The unit has not authenticated. The registration failure reason will be displayed on the Local User Interface (LUI) advanced screen.
18 Waiting for Capacity Keys Commissioning The HN9X00 is waiting for capacity keys. The unit has authenticated and has requested the capacity keys.
19 Reconciling Profiles in Commissioning Commissioning The HN9X00 is in commissioning phase. The HN9X00 is reconciling profiles. The unit is establishing the site configuration and has requested the Operational software.
20 Downloading Operational Software Commissioning The HN9X00 is in commissioning phase. The HN9X00 is downloading operational software. The unit is receiving the Operational software.
21 Starting Up in Operation Operational The HN9x00 is starting up in Operational phase. The site has received and is loading the Operational software.
22 Downlink Established in Operational Operational The HN9X00 is in operational phase. The downlink has been established i.e., the beacon is being tracked and TIPs are being received. The site has established the downlink, beacon signal is tracked and the TIPS are being received.
23 Waiting for MIPs in Operational Operational The HN9X00 is in operational phase and is waiting for indirect and direct MIPs. The site has established the downlink, beacon signal is tracked and the TIPS are being received.
24 Reconciling Profile in Operational Operational The HN9X00 is in operational phase. Profiles are being distributed to various subsystems. The site has established the downlink, beacon signal is tracked, TIPS and MIPS are being received, and the unit is setting internal profiles.
25 Fully Operational Operational The HN9X00 is fully operational. The HN9x00 is fully operational.
26 Rx Connectivity Down Problematic Receive cable connectivity tests have failed. Confirm that the satellite receive cable is connected.
27 No Beacon Problematic The HN9X00 is unable to track the beacon. Determine if there is any bad weather in the area. Confirm that the satellite receive cable is connected. Determine if the antenna is mispointed.
28 No TIPs Problematic The HN9X00 is not receiving TIPs from the satellite. Determine if there is any bad weather in the area. Confirm that the satellite receive cable is connected. Determine if the antenna is mispointed.
29 Tx Connectivity Down Problematic Transmit cable connectivity tests have failed. Confirm that the satellite transmit cable is connected.
30 Too Many Bad Slots Problematic The HN9X00 is experiencing a large number of bad slots in transmission. The transmit packets being sent are incomplete. Possible causes are a weather issue, bad transmitter, or a bad cable.
31 ECL Active Problematic The HN9000 transmission has been shutdown due to Emission Control Logic (ECL). The unit transmissions exceeded FCC regulations and has been shutdown.
32 Barred Restricted Operation The HN9X00 transmission has been barred. Contact Technical Support, click here.
33 Suspended Restricted Operation The HN9X00 has been put in a suspended state. Contact Technical Support, click here.
34 Maintenance Restricted Operation The HN9X00 has been put in a maintenance state. Contact Technical Support, click here.
35 Out of Service Restricted Operation The HN9X00 has been put in an out-of-service state. Contact Technical Support, click here.
36 Unknown Terminal State Restricted Operation The HN9X00 has been put in an out-of-service state. Contact Technical Support, click here.

Back to Top