dslreports logo
site
spacer

spacer
 
    All FAQs Site FAQ DSL FAQ Cable Tech About DSL Distance DSL Hurdles »»
spc

spacer




how-to block ads



The definitions for the error codes were researched by installguy. Thanks installguy!

TX Code 0 ITUST_NONE: The transmitter is not connected to the receiver.

If this state persists over at least 10 seconds, then the system is not properly functioning. If an ITU is present on the system but this message appears, first check the LEDs on the ITU. If neither is flashing, then one of the following is likely the cause.

IRU-ITU cable not properly connected to the IRU or ITU.
In this situation, the ITU does not receive power or does not have the communication link established. Please check that the cable is properly connected and secured.
ITU/ IRU version mismatch.
If operating software prior to 4.0.0.40, the ITU version must be less than or equal to 3
ITU Failure.
In this case, the ITU might need to be swapped out.

TX Code 1 ITUST_DISABLED: The transmitter has been disabled by the Network Operations Center.

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. It may also be enabled if the user discontinues 2-way service. Contacting the networks operations center and requesting that the unit be enabled can only correct a persistence of this condition.

TX Code 2 ITUST_TEST: The transmitter has been placed in test mode by the Network Operations Center.

This state occurs when the NOC staff places the unit into special transmission modes to measure the performance of a users 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. If the unit is not expected to be in test mode, the network operations center must be contacted to remove the unit from test mode.

TX Code 3 ITUST_NOLOCK: The transmitter is locking to the receive carrier.

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 10 seconds. If this persists for more than 10 seconds, try disconnecting and reconnecting the IFL and wait 10 seconds to check for recovery. If the situation persists, then the ITU and IRU must be replaced.

TX Code 4 ITUST_BADIF: The transmitter is not responding to commands set from the receiver.

This indicates that there is something not properly operating in the IRU/ITU configuration. The expected actions to attempt to recover are as follows:

Perform Activate ITU from the Adapter Diagnostic Utility to see if the system recovers
Perform a reset of the IRU (power-cycle the unit) which will reset the IRU and ITU
Check the IRU/ITU cable to ensure it is connected and secure
If it cannot be resolved via resets, replace the power support, IRU/ITU cable, and the ITU
This could also be caused if the power supply is faulty.

TX Code 5 ITUST_NOTIME: The transmitter is not locked to network timing.

No action is necessary if this occurs from time to time and quickly resolves itself. If this issue persists, it is likely due to a NOC-related service issue. If this problem is occurring on a user unit while it is not occurring on other units in the network, then it could be caused by one of the following:

Marginal Receive power: If the receive signal strength is in the 30''s, then this is causing sufficient dropped packets to lead to loss of network timing information. Use standard approaches to peak the receive power or re-point the antenna.
ITU Failure: Swap out the ITU.


TX Code 6 ITUST_NORX: The transmitter is not available because the receiver is not detecting a signal or is not locked to the correct network.

This status should correlate to the receive status indicating a problem.

Refer to the receive status messages to deal with this issue.

TX Code 7 ITUST_RXMODE: The transmitter is not available because the receiver is not tuned for normal operation.

When the unit is placed into special modes like antenna pointing mode, then the unit cannot transmit. By exiting the antenna pointing function, this should be resolved. In the worse case, a PC reboot (or restart of the navigator) should resolve this.

TX Code 8 ITUST_OK: The transmitter is available.

This is the normal operational state of the transmitter if it is installed.

TX Code 9 ITUST_RANGE: The transmitter is adjusting for optimal network timing.

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 dish is installed into a different location and re-pointed using the antenna pointing program. This is a normal state for a unit when it is first installed.

TX Code 10 ITUST_RTX: The transmitter is unable to communicate with the Network Operations Center.

This state indicates that the unit has stopped attempting 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 on the return channel equipment. Also, verify that the cable connecting the ITU to the ODU is in place, secure, and not damaged. Replace cable if necessary.

TX Code 11 ITUST_BADVER: The transmitter is not available because the receiver software is out of date.

This state indicates that the client software is not recent enough to operate on the network. New client 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. If this message appears, new software is needed on the client machine.

TX Code 12 ITUST_BADDNCC: The transmitter is not receiving network control messages from the Network Operations Center.

This state indicates a NOC equipment outage on the server that controls return channel bandwidth (the DNCC). This problem should be reported to the NOC for service recovery.

TX Code 13 ITUST_RRTX: The transmitter is unable to range because it cannot communicate with the Network Operations Center.

This state may indicate many root causes. It occurs when the NOC does not receive ranging information from the unit. This could occur because the unit is unable to achieve enough transmit power for the NOC to receive. It could also occur because timing is incorrect due to entering the improper zip code or latitude/longitude information. It could also occur if the transmit ODU is not properly operating or is not properly cabled to the ITU. Severe weather conditions may also cause this to occur.

TX Code 14 ITUST_RBAD: The transmitter is not available because ranging has failed.

This state indicates that the NOC was unable to complete ranging if a user. The NOC needs to re-enable ranging to ensure successful ranging by users. This likely indicates that ranging capability is not currently operating correctly in the NOC.

TX Code 15 ITUST_RBUSY: The transmitter is waiting for a ranging request to be processed by the Network Operations Center.

This state occurs if the system is busy with adjusting power and timing for other users. This can be resolved by the NOC by adding more ranging capacity. Otherwise, the user must wait for a turn ranging.

TX Code 16 ITUST_ABUSY: The transmitter is waiting for a transmit request to be processed by the Network Operations Center.

This state occurs if the system is overloaded with users going active and is unable to provide bandwidth to a user going active. This indicates an overloading of the network with users. NOC operations should be contacted about increasing capacity.

TX Code 17 ITUST_NORATE: The transmitter is unable to obtain an available transmission rate.

This occurs if the unit cannot successfully range at any of the available inroute rates.

The possible causes are:

First generation ITU is used on a system that does not have 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.

TX Code 18 ITUST_XREQ: The transmitter is requesting a transmit pointing test.

(Automatic CrossPol (ACP) Only) The unit is in this state when the antenna pointing program on the PC requests that the unit perform a transmit pointing test. The unit remains in this state until the NOC responds that the unit is either performing the test or queued to perform the test.

This is a normal state for installation. The unit may also periodically go into this state for short periods of time (<5 seconds) for periodic system checks that are performed on the antenna pointing to ensure that it continues to meet the cross-polarization requirements.

TX Code 19 ITUST_XQUE: The transmitter is queued for a transmit pointing test.

(Automatic CrossPol (ACP) Only) The unit is in this state when the antenna pointing program on the PC requests that the unit perform a transmit pointing test and the NOC has responded that the unit is queued. It also may occur periodically when the system is rechecking the pointing of the antenna. This occurs when other users have requested transmit pointing. This is a normal state for installation.

TX Code 20 ITUST_XTEST: The transmitter is performing a transmit pointing test.

(Automatic CrossPol (ACP) Only) The unit is in this state when either the antenna pointing program on the PC requests that the unit perform a transmit pointing test or the periodic system check is performing the antenna pointing test. This occurs once the NOC has provided the resources to initiate the test. If this is a PC pointing function, the unit remains in this state until the user exits pointing mode or the NOC times out the pointing. If this is the periodic test, it should exit this state within 5 seconds.

TX Code 21 ITUST_XFAIL: The transmitter is disabled because a transmit pointing test failed.

(Automatic CrossPol (ACP) Only) The unit failed the transmit pointing test, which means that it did not meet the specifications required by the satellite provider for cross-pol versus co-pol. This is likely due to an installation problem. The installer needs to fine-point the antenna to improve the cross-pol result and then re-execute the transmit pointing. The unit will not transmit until the cross-pol passes.

TX Code 22 ITUST_XPEND: The transmitter is disabled pending a transmit pointing test.

Units will only enter this mode on systems that support automated cross-polarization periodic rechecks. The unit is expected to be in this mode for up to 2 minutes at periodic intervals. This is also likely to occur upon power up 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 auto-cross-polarization system in the Network Operations Center is likely experiencing an outage.

TX Code 23 ITUST_XNONE: The transmitter is disabled because a transmit pointing test cannot be performed.

A unit is placed into this mode when it cannot perform transmit pointing upon initial setup on the network or when the unit is required to re-range. This mode indicates that the NOC components that perform the automated cross-polarization pointing function are not operational.

IRU State Message Strings:



RxCode 0 IRUST_SUSPEND: The receiver is in USB suspend.

This should be a transient state at startup or after a suspend. A customer should never see this message. If they do, shutdown and restart the PC to clear this state and check TCP/IP settings if the condition persists.

RxCode 1 IRUST_POINT: The receiver is in pointing mode.

This status 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 dish.

RxCode 2 IRUST_RXMODE: The receiver is in factory or NOC mode.

This status is for testing purpose only and will not been seen by users.

RxCode 3 IRUST_NOLOCK: The receiver is not locked to a signal.

This status indicates that the IRU is unable to receive the signal from the NOC. This is also associated with a signal level less than 30. This occurs if there is a weather outage for the user, a complete NOC outage, a mis-pointed antenna, or if the LNB is not operating correctly (either due to the connection via cable to the IRU or an LNB failure). This is likely a pointing issue or a temporary NOC outage.

RxCode 4 IRUST_BADNET: The receiver is locked to the wrong network.

This status appears if the receiver locked to a signal, which does not match that which the user was assigned to at web-setup time. This is likely due to the user changing pointing to the wrong satellite or changing the tuning frequency to not match that which was provided during the commissioning process. If the user has been reassigned to a different transponder or satellite, then the user should use web-setup to get the proper configuration parameters.

RxCode 5 IRUST_OK: The receiver is operational.

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.

RxCode 6 IRUST_SATAGC: The receiver is not detecting any signal (check connections).

This indicates that the LNB to IRU connections are either faulty or the IRU itself is faulty. The cables and connectors should be checked.

RxCode 7 IRUST_NONET: The receiver is locked to a unknown network.

This status appears if the receiver locked to a signal that does not have DirecWay identification. This is likely to occur if part of the DirecWay NOC is not operational. It is also likely if the user is pointed to the incorrect satellite or a frequency other than that provided during the commissioning process. To ensure it is not a local issue, reset the IRU to see if this condition persists.

Other strings that appear on status dialog:
Idle (Not connected in version 4.0.1)

This is the normal status when a 1-way unit is not connected to the internet via a phone line. This is also the normal status for a 2-way unit configured to use terrestrial rather than satellite return channel when it is not connected to the internet via a phone line. It is also possible to be in this state if the return channel mode is set to "Use satellite as primary ... fall back to terrestrial..." and the satellite is not available

Connecting

This is the status during the time when a unit is dialing the phone line and connecting for internet access.

Connected via Satellite

This is the normal mode for a 2-way unit. A 2-way Unit is connected all of the time when it is properly operating (whether data is being transmitted or not).

Connected via Modem

This is the normal status once the phone line is connected.

Connected via Satellite - Modem connection to Internet Service Provider (ISP) is still active The connection to your Internet Service Provider (ISP) is no longer required. - Press the ''Disconnect'' button to disconnect your modem.

This set of messages appears when DIRECWAY is configured for satellite return channel as primary and modem as fallback and: The satellite return channel was considered non-operational some time in the past. The modem is connected to the internet as the backup to the satellite return channel. The satellite return channel is now considered operational. The modem is still connected to the internet even though the satellite return channel is now being used. The user should disconnect the phone line since it is not being used.

DIRECWAY needs to establish a connection to the Internet. Press the "Connect" button to establish the connection or "Cancel" to close this dialog.

This message indicates that access to the internet is needed because a user requested connection to a website that is not in the PC cache. This occurs on a 1-way system where auto-connect is not enabled.

Expand got feedback?

by grohgreg See Profile edited by PetDude See Profile
last modified: 2002-08-07 21:20:31