Knowledgebase: Fleet Broadband
Alarms - Warnings - Events - Cause codes
Posted by Ove C. Nielsen on 16 February 2011 02:19 PM

Cause codes from network. (Call log / Diagnostic report)

Cause No. 1 "unassigned (unallocated) number" (UMTS specific cause values for call control)

This cause indicates that the destination requested by the mobile station cannot be reached because, although the number is in a valid format, it is not currently assigned (allocated).

Cause value = 2 IMSI unknown in HLR (Causes related to MS identification)

This cause is sent to the MS if the MS is not known (registered) in the HLR. This cause code does not affect operation of the GPRS service, although is may be used by a GMM procedure.

Cause value = 3 Illegal MS (Causes related to MS identification) This cause is sent to the MS when the network refuses service to the MS either because an identity of the MS is not acceptable to the network or because the MS does not pass the authentication check, i.e. the SRES received from the MS is different from that generated by the network. When used by an MM procedure, except the authentication procedure, this cause does not affect operation of the GPRS service.

Cause No. 3 "no route to destination" (UMTS specific cause values for call control) This cause indicates that the called user cannot be reached because the network through which the call has been routed does not serve the destination desired.

Cause value = 4 IMSI unknown in VLR (Causes related to MS identification) This cause is sent to the MS when the given IMSI is not known at the VLR.

Cause value = 5 IMEI not accepted (Causes related to MS identification) This cause is sent to the MS if the network does not accept emergency call establishment using an IMEI.

Cause value = 6 Illegal ME (Causes related to MS identification) This cause is sent to the MS if the ME used is not acceptable to the network, e.g. blacklisted. When used by an MM procedure, this cause does not affect operation of the GPRS service.

Cause No. 6 "channel unacceptable" (UMTS specific cause values for call control) This cause indicates the channel most recently identified is not acceptable to the sending entity for use in this call.

Cause value = 7 GPRS services not allowed (Additional cause codes for GMM) This cause is sent to the MS if it requests an IMSI attach for GPRS services, but is not allowed to operate GPRS services.

Cause value = 8 GPRS services and non-GPRS services not allowed (Additional cause codes for GMM) This cause is sent to the MS if it requests a combined IMSI attach for GPRS and non-GPRS services, but is not allowed to operate either of them.

Cause No. 8 "operator determined barring" (GPRS specific cause values for session management) This cause indicates that the MS has tried to access a service that the MS's network operator or service provider is not prepared to allow.

Cause value = 9 MS identity cannot be derived by the network (Additional cause codes for GMM) This cause is sent to the MS when the network cannot derive the MS's identity from the P-TMSI in case of inter-SGSN routing area update.

Cause value = 10 Implicitly detached (Additional cause codes for GMM) This cause is sent to the MS either if the network has implicitly detached the MS, e.g. some while after the Mobile reachable timer has expired, or if the GMM context data related to the subscription dose not exist in the SGSN e.g. because of a SGSN restart.

Cause value = 11 PLMN not allowed (Cause related to subscription options) This cause is sent to the MS if it requests location updating in a PLMN where the MS, by subscription or due to operator determined barring is not allowed to operate.

Cause value = 12 Location Area not allowed (Cause related to subscription options) This cause is sent to the MS if it requests location updating in a location area where the MS, by subscription, is not allowed to operate.

Cause value = 13 Roaming not allowed in this location area (Cause related to subscription options) This cause is sent to an MS which requests location updating in a location area of a PLMN which offers roaming to that MS in that Location Area, by subscription.

Cause value = 14 GPRS services not allowed in this PLMN (Additional cause codes for GMM) This cause is sent to the MS which requests GPRS service in a PLMN which does not offer roaming for GPRS services to that MS.

Cause value = 15 No Suitable Cells In Location Area (Cause related to subscription options) This cause is sent to the MS if it requests location updating in a location area where the MS, by subscription, is not allowed to operate, but when it should find another allowed location area in the same PLMN.

NOTE: Cause #15 and cause #12 differ in the fact that cause #12 does not trigger the MS to search for another allowed location area on the same PLMN.

Cause No.16 "normal call clearing" (UMTS specific cause values for call control) This cause indicates that the call is being cleared because one of the users involved in the call has requested that the call be cleared. Under normal situations, the source of this cause is not the network.

Cause value = 16 MSC temporarily not reachable” (Additional cause codes for GMM) This cause is sent to the MS if it requests a combined GPRS attach or routing are updating in a PLMN where the MSC is temporarily not reachable via the GPRS part of the GSM network.

Cause value = 17 “Network failure” (Causes related to PLMN specific network failures and congestion / Authentication Failures) This cause is sent to the MS if the MSC cannot service an MS generated request because of PLMN failures, e.g. problems in MAP.

Cause No.17 "user busy" (UMTS specific cause values for call control) This cause is used when the called user has indicated the inability to accept another call. It is noted that the user equipment is compatible with the call.

Cause No. 18 "no user responding" (UMTS specific cause values for call control) This cause is used when a user does not respond to a call establishment message with either an alerting or connect indication within the prescribed period of time allocated (defined by the expiry of either timer T303 or T310).

Cause No. 19 "user alerting, no answer" (UMTS specific cause values for call control) This cause is used when a user has provided an alerting indication but has not provided a connect indication within a prescribed period of time.

Cause value = 20 “MAC failure” (Causes related to PLMN specific network failures and congestion/Authentication Failures) This cause is sent to the network if the SIM detects that the MAC in the authentication request message is not fresh (see 3GPP TS 33.102).

Cause value = 21 “Synch failure” (Causes related to PLMN specific network failures and congestion/Authentication Failures) This cause is sent to the network if the SIM detects that the SQN in the authentication request message is out of range (see 3GPP TS 33.102).

Cause No. 21 "call rejected" (UMTS specific cause values for call control) This cause indicates that the equipment sending this cause does not wish to accept this call, although it could have accepted the call because the equipment sending this cause is neither busy nor incompatible.

Cause No. 22 "number changed" (UMTS specific cause values for call control) This cause is returned to a calling mobile station when the called party number indicated by the calling mobile station is no longer assigned. The new called party number may optionally be included in the diagnostic field. If a network does not support this capability, cause No. 1 "unassigned (unallocated) number" shall be used.

Cause value = 22 “Congestion”(Causes related to PLMN specific network failures and congestion/Authentication Failures) This cause is sent if the service request cannot be actioned because of congestion (e.g. no channel, facility busy/congested etc.).

Cause value = 23 “GSM authentication unacceptable”(Causes related to PLMN specific network failures and congestion/Authentication Failures) This cause is sent to the network in UMTS if the MS supports the UMTS authentication algorithm and there is no Authentication Parameter AUTN IE present in the AUTHENTICATION REQUEST message.

Cause No. 25 "pre-emption" (UMTS specific cause values for call control) This cause is returned to the network when a mobile station clears an active call which is being pre-empted by another call with higher precedence.

Cause value = 25 “LLC or SNDCP failure (GSM only)” (GPRS specific cause values for session management) This cause code is used by the MS indicate that a PDP context is deactivated because of a LLC or SNDCP failure (e.g. if the SM receives a SNSM-STATUS.request message with cause "DM received " or " invalid XID response ", see 3GPP TS 44.065 [78])

Cause value = 26 “Insufficient  resources(GPRS specific cause values for session management) This cause code is used by the MS or by the network to indicate that a PDP context activation request, secondary PDP context activation request or PDP context modification request cannot be accepted due to insufficient resources.

Cause No. 26 "non-selected user clearing" (UMTS specific cause values for call control)

Cause No. 27 "destination out of order" (UMTS specific cause values for call control) This cause indicates that the destination indicated by the mobile station cannot be reached because the interface to the destination is not functioning correctly. The term "not functioning correctly" indicates that a signalling message was unable to be delivered to the remote user; e.g., a physical layer or data link layer failure at the remote user, user equipment off-line, etc.

Cause value = 27 “Unknown or missing access point name” (GPRS specific cause values for session management) This cause code is used by the network to indicate that the requested service was rejected by the external packet data network because the access point name was not included although required or if the access point name could not be resolved.

Cause No. 28 "invalid number format (incomplete number)" (UMTS specific cause values for call control) This cause indicates that the called user cannot be reached because the called party number is not a valid format or is not complete.

Cause value = 28 “Unknown PDP address or PDP type” (GPRS specific cause values for session management) This cause code is used by the network to indicate that the requested service was rejected by the external packet data network because the PDP address or type could not be recognised.

Cause No. 29 "facility rejected" (UMTS specific cause values for call control) This cause is returned when a facility requested by user can not be provided by the network.

Cause value = 29 “User authentication failed” (GPRS specific cause values for session management) This cause code is used by the network to indicate that the requested service was rejected by the external packet data network due to a failed user authentication.

Cause No. 30 "response to STATUS ENQUIRY" (UMTS specific cause values for call control) This cause is included in STATUS messages if the message is sent in response to a STATUS ENQUIRY message. See also subclause 5.5.3.

Cause value = 30 “Activation rejected by GGSN” (GPRS specific cause values for session management) This cause code is used by the network to indicate that the requested service was rejected by the GGSN.

Cause No. 31 "normal, unspecified" (UMTS specific cause values for call control) This cause is used to report a normal event only when no other cause in the normal class applies.

Cause value = 31 “Activation rejected, unspecified” (GPRS specific cause values for session management) This cause code is used by the network to indicate that the requested service was rejected due to unspecified reasons.

Cause value = 32 “Service option not supported” (GPRS specific cause values for session management) This cause code is used by the network when the MS requests a service which is not supported by the PLMN.

Cause value = 33 ”Requested service option not subscribed”(GPRS specific cause values for session management) This cause is sent when the MS requests a service option for which it has no subscription.

Cause No. 34 "no circuit/channel available" (Resource unavailable class) This cause indicates that there is no appropriate circuit/channel presently available to handle the call.

Cause value = 34 “Service option temporarily out of order” (Causes related to nature of request) This cause is sent when the MSC cannot service the request because of temporary outage of one or more functions required for supporting the service.

Cause value = 35 “NSAPI already used” (GPRS specific cause values for session management) This cause code may be used by a network to indicate that the NSAPI requested by the MS in the PDP context activation request is already used by another active PDP context of this MS. Never to be sent, but can be received from a R97/R98 network at PDP context activation

Cause value = 36 “Regular PDP context deactivation” (GPRS specific cause values for session management) This cause code is used to indicate a regular MS or network initiated PDP context deactivation.

Cause value = 37 “QoS not accepted” (GPRS specific cause values for session management) This cause code is used by the MS if the new QoS cannot be accepted that were indicated by the network in the PDP Context Modification procedure.

Cause No. 38 "network out of order" (Resource unavailable class)

This cause indicates that the network is not functioning correctly and that the condition is likely to last a relatively long period of time; e.g., immediately re-attempting the call is not likely to be successful.

Cause value = 38 Call cannot be identified (Causes related to nature of request)

This cause is sent when the network cannot identify the call associated with a call re-establishment request.

Cause value = 38 Network failure  (GPRS specific cause values for session management)

This cause code is used by the network to indicate that the PDP context deactivation is caused by an error situation in the network.

Cause value = 39 Reactivation requested (GPRS specific cause values for session management)

This cause code is used by the network to request a PDP context reactivation after a GGSN restart.

Cause value = 40 No PDP context activated (Additional cause codes for GMM)

This cause is sent to the MS if the MS requests an establishment of the radio access bearers for all active PDP contexts by sending a SERVICE REQUEST message indicating "data" to the network, but the SGSN does not have any active PDP context(s).

Cause value = 40 Feature not supported (GPRS specific cause values for session management) 

This cause code is used by the MS to indicate that the PDP context activation initiated by the network is not supported by the MS.

Cause No. 41 "temporary failure" (Resource unavailable class)

This cause indicates that the network is not functioning correctly and that the condition is not likely to last a long period of time; e.g., the mobile station may wish to try another call attempt almost immediately.

Cause value = 41 semantic error in the TFT operation. (GPRS specific cause values for session management)

This cause code is used by the network to indicate that the there is a semantic error in the TFT operation included in a secondary PDP context activation request or an MS-initiated PDP context modification.

Cause No. 42 "switching equipment congestion" (Resource unavailable class)

This cause indicates that the switching equipment generating this cause is experiencing a period of high traffic.

Cause value = 42 syntactical error in the TFT operation. (GPRS specific cause values for session management)

This cause code is used by the network to indicate that there is a syntactical error in the TFT operation included in a secondary PDP context activation request or an MS-initiated PDP context modification.

Cause No. 43 "access information discarded" (Resource unavailable class)

This cause indicates that the network could not deliver access information to the remote user as requested; i.e., a user-to-user information, low layer compatibility, high layer compatibility, or sub-address as indicated in the diagnostic. It is noted that the particular type of access information discarded is optionally included in the diagnostic.

Cause value = 43 unknown PDP context (GPRS specific cause values for session management)

This cause code is used by the network to indicate that the PDP context identified by the Linked TI IE the secondary PDP context activation request is not active.

Cause No. 44 "requested circuit/channel not available" (Resource unavailable class)

This cause is returned when the circuit or channel indicated by the requesting entity cannot be provided by the other side of the interface.

Cause value = 44 semantic errors in packet filter(s) (GPRS specific cause values for session management)

This cause code is used by the network to indicate that there is one or more semantic errors in packet filter(s) of the TFT included in a secondary PDP context activation request or an MS-initiated PDP context modification.

Cause value = 45 syntactical error in packet filter(s) (GPRS specific cause values for session management)

This cause code is used by the network to indicate that there is one or more syntactical errors in packet filter(s) of the TFT included in a secondary PDP context activation request or an MS-initiated PDP context modification.

Cause value = 46 PDP context without TFT already activated (GPRS specific cause values for session management)

This cause code is used by the network to indicate that the network has already activated a PDP context without TFT.

Cause No. 47 "resource unavailable, unspecified" (Resource unavailable class)

This cause is used to report a resource unavailable event only when no other cause in the resource unavailable class applies.

Cause No. 49 "quality of service unavailable" (Service or option not available class)

This cause indicates to the mobile station that the requested quality of service, as defined in ITU-T Recommendation X.213, cannot be provided.

Cause No. 50 "Requested facility not subscribed" (Service or option not available class)

This cause indicates that the requested supplementary service could not be provided by the network because the user has no completed the necessary administrative arrangements with its supporting networks.

Cause No. 55 "Incoming calls barred within the CUG" (Service or option not available class)

This cause indicates that although the called party is a member of the CUG for the incoming CUG call, incoming calls are not allowed within this CUG.

Cause No. 57 "bearer capability not authorized" (Service or option not available class)

This cause indicates that the mobile station has requested a bearer capability which is implemented by the equipment which generated this cause but the mobile station is not authorized to use.

Cause No. 58 "bearer capability not presently available" (Service or option not available class)

This cause indicates that the mobile station has requested a bearer capability which is implemented by the equipment which generated this cause but which is not available at this time.

Cause No. 63 "service or option not available, unspecified" (Service or option not available class)

This cause is used to report a service or option not available event only when no other cause in the service or option not available class applies.

Cause No. 68 "ACM equal to or greater than ACMmax" (Service or option not available class)

This cause is used by the mobile to indicate that call clearing is due to ACM being greater than or equal to ACMmax.

Cause No. 65 "bearer service not implemented" (Service or option not implemented class)

This cause indicates that the equipment sending this cause does not support the bearer capability requested.

Cause No. 69 "Requested facility not implemented" (Service or option not implemented class)

This cause indicates that the equipment sending this cause does not support the requested supplementary service.

Cause No. 70 "only restricted digital information bearer capability is available" (Service or option not implemented class)

This cause indicates that one equipment has requested an unrestricted bearer service, but that the equipment sending this cause only supports the restricted version of the requested bearer capability.

Cause No. 79 "service or option not implemented, unspecified" (Service or option not implemented class)

This cause is used to report a service or option not implemented event only when no other cause in the service or option not implemented class applies.

Cause No. 81 "invalid transaction identifier value" (Service or option not implemented class)

This cause indicates that the equipment sending this cause has received a message with a transaction identifier which is not currently in use on the MS-network interface.

Cause No. 87 "user not member of CUG" (Service or option not implemented class)

This cause indicates that the called user for the incoming CUG call is not a member of the specified CUG.

Cause No. 88 "incompatible destination" (Service or option not implemented class)

This cause indicates that the equipment sending this cause has received a request to establish a call which has low layer compatibility, high layer compatibility, or other compatibility attributes (e.g., data rate) which cannot be accommodated.

Cause No. 91 "invalid transit network selection" (Service or option not implemented class)

Cause No. 95 "semantically incorrect message" (Causes related to invalid messages)

This cause is used to report receipt of a message with semantically incorrect contents (see subclause 8.8).

Cause No. 96 "invalid mandatory information" (Causes related to invalid messages)

This cause indicates that the equipment sending this cause has received a message with a non-semantical mandatory IE error (see subclause 8.5).

Cause No. 96 "invalid mandatory information" (Causes related to invalid messages)

Cause No. 97 "message type non-existent or not implemented" (Causes related to invalid messages)

This cause indicates that the equipment sending this cause has received a message with a message type it does not recognize either because this is a message not defined, or defined but not implemented by the equipment sending this cause.

Cause No. 97 "message type non-existent or not implemented" (Causes related to invalid messages)

This cause indicates that the equipment sending this cause has received a message with a message type it does not recognize either because this is a message not defined, or defined but not implemented by the equipment sending this cause.

Cause No. 98 "message type not compatible with protocol state" (Causes related to invalid messages)

This cause indicates that the equipment sending this cause has received a message not compatible with the protocol state (subclause 8.4).

Cause No. 98 "message type not compatible with protocol state" (Causes related to invalid messages)

This cause indicates that the equipment sending this cause has received a message not compatible with the protocol state.

Cause No. 99 "information element non-existent or not implemented" (Causes related to invalid messages)

This cause indicates that the equipment sending this cause has received a message which includes information elements not recognized because the information element identifier is not defined or it is defined but not implemented by the equipment sending the cause. However, the information element is not required to be present in the message in order for the equipment sending the cause to process the message.

Cause No. 100 "conditional IE error" (Causes related to invalid messages)

This cause indicates that the equipment sending this cause has received a message with conditional IE errors (see subclause 8.7.2).

Cause No. 101 "message not compatible with protocol state" (Causes related to invalid messages)

This cause indicates that a message has been received which is incompatible with the protocol state or that a STATUS message has been received indicating an incompatible call state.

Cause No. 102 "recovery on timer expiry"

This cause indicates that a procedure has been initiated by the expiry of a timer in association with 3GPP TS 24.008 error handling procedures.

Cause No. 111 "protocol error, unspecified" (Causes related to invalid messages)

This cause is used to report a protocol error event only when no other cause in the protocol error class applies.

Cause No. 127 "interworking, unspecified"

This cause indicates that there has been interworking with a network which does not provide causes for actions it takes; thus, the precise cause for a message which is being sent cannot be ascertained

Events in event log – event list .

ATB=S500A/E727/E352

09001 EV_ATB_AZIMUTH_MOTOR_SHORTED_TO_SUPPLY "Antenna - Azimuth motor connection shorted to supply"

09002 EV_ATB_AZIMUTH_MOTOR_SHORTED_TO_GROUND "Antenna - Azimuth motor connection shorted to ground"

09003 EV_ATB_AZIMUTH_MOTOR_VOLTAGE "Antenna - Azimuth motor - Insufficient voltage or load current"

09004 EV_ATB_ELEVATION_MOTOR_SHORTED_TO_SUPPLY "Antenna - Elevation motor connection shorted to supply"

09005 EV_ATB_ELEVATION_MOTOR_SHORTED_TO_GROUND "Antenna - Elevation motor connection shorted to ground"

09006 EV_ATB_ELEVATION_MOTOR_VOLTAGE "Antenna - Elevation motor - Insufficient voltage or load current"

Explorer 727/325:

The motor fault detection is done by monitoring the fault detection pins of the motor drivers. For the motor drivers to change fault

state, they are required to pass their home microstep position. The elevation motor fault is available via the FAILURE_REQ command

after ten seconds of presence and removed three seconds after it has gone. The azimuth motor fault detection is carried out

during the antenna initialisation and self-test procedures only. The fault is available via the FAILURE_REQ command when the

antenna has left the INIT_ST state and will be present until the antenna has been reset or a self-test is carried out.

Fault 0x01: Motor connections shorted to the supply voltage.

Fault 0x02: Motor connections shorted to ground.

Fault 0x03: Undervoltage lockout, overvoltage lockout, overtemperature, low load current or shorted load.

Recommended action:

It is recommended to make the faulty antenna axis turn at least two degrees, to ensure the motor drivers have passed their home

microstep postion. If the fault is still present it should be verified if the faulty axis is able to move, e.g. by running a self-test. If the

faulty axis does not move, service should be requested.

NB: A low load current fault (Fault type 0x03) may appear if the motor velocity is too high. E.g. when the antenna is exposed to

extreme movements.

09007 EV_ATB_CROSS_ELEVATION_MOTOR_SHORTED_TO_SUPPLY "Antenna - Cross-elevation motor connection shorted to supply"

09008 EV_ATB_CROSS_ELEVATION_MOTOR_SHORTED_TO_GROUND "Antenna - Cross-elevation motor connection shorted to ground"

09009 EV_ATB_CROSS_ELEVATION_MOTOR_VOLTAGE "Antenna - Cross-elevation motor - Insufficient voltage or load current"

S500 - TT3052A:

The motor fault detection is done by monitoring the fault detection pins of the motor drivers. For the motor drivers to change fault

state, they are required to pass their home microstep position. The elevation and cross-elevation motor faults are available via the

FAILURE_REQ command after ten seconds of presence and removed three seconds after they have gone. The azimuth motor fault

detection is carried out during the antenna initialisation and self-test procedures only. The fault is available via the FAILURE_REQ

command when the antenna has left the INIT_ST state and will be present until the antenna has been reset or a self-test is carried out.

Fault 0x01: Motor connections shorted to the supply voltage.

Fault 0x02: Motor connections shorted to ground.

Fault 0x03: Undervoltage lockout, overvoltage lockout, overtemperature, low load current or shorted load.

Recommended action:

It is recommended to make the faulty antenna axis turn at least two degrees, to ensure the motor drivers have passed their home

microstep postion. If the fault is still present it should be verified if the faulty axis is able to move, e.g. by running a self-test. If the

faulty axis does not move, service should be requested.

NB: A low load current fault (Fault type 0x03) may appear if the motor velocity is too high. E.g. when the antenna is exposed to

extreme movements.

0900A EV_ATB_EEPROM_WRITE_ERR "Antenna - Write verification fault in EEPROM"

EEPROM fault

The EEPROM write verification fault is detected by monitoring the number of consecutive write verification faults. This fault may be

caused by a defective EEPROM or if the EEPROM communication fails. The consequence of this fault is that the antenna is unable

to save the last known frequency and elevation after entering track state. If the EEPROM is defective, data may be lost or inaccessible.

Recommended action:

If this fault occurs it is recommended to try updating the frequency, wait ten seconds after the antenna has entered track state and

check if the fault has disappeared. If the fault is still present, power cycling the ATB may remove the fault.

0900C EV_ATB_TEMP_TOO_LOW "Antenna - temperature too low"

0900D EV_ATB_TEMP_TOO_HIGH  "Antenna - temperature too high"

Temperature sensor faults

The temperature in the sensor area is monitored to ensure stable sensor readings. A temperature too high or too low may affect the

performance of the antenna.

Recommended action:

If the temperature is too high it is recommended to turn off the antenna and let it cool. If the temperature is too low, the antenna

should be left turned on.

0900E EV_ATB_INCLINOMETER_ERR "Antenna - Inclinometer reading fault"

Elevation inclinometer fault

The elevation inclinometer is tested during a self-test. A false alarm may occur if the antenna is not kept steady during the self-test.

The consequence of a fault may be degradation of the tracking performance.

Recommended action:

If this fault occurs, it should be ensured that the antenna is kept steady. When this condition is met, the self-test may be repeated. If

the fault is still present, service should be requested.

Elevation rate sensor fault

The elevation rate sensor is tested by monitoring the sensor reading during a sinusoidal movement around the elevation axis. A false

alarm may occur if the antenna is not kept steady during the self-test. The consequence of a rate sensor fault may be degradation of

the tracking performance.

Recommended action:

If this fault occurs, it should be ensured that the antenna is kept steady. When this condition is met, the self-test may be repeated. If

the fault is still present, service should be requested.

0900F EV_ATB_RF_SYNT_PLL  "Antenna - PLL repeatedly looses lock"

RF synthesizer fault

The RF synthesizer fault is detected if the PLL repeatedly loses the lock. The fault may occur because of extreme changes in temperature,

or if the RF synthesizer is defective. If this fault occurs, the satellite link is most likely lost.

Recommended action:

If this fault occurs, it should be ensured that the temperature conditions are stable, not too high or too low. When these conditions are

met, it is recommended to power cycle the ATB and request service if this does not remove the fault.

09010 EV_ATB_LNA_LOW_RSSI "Antenna - Low RSSI level"

LNA fault

The LNA is tested by monitoring the RSSI level. The low RSSI level fault is only detectable during a self-test. The detection of this

fault is not unambiguous and in low noise environments a false alarm may occur. If this fault occurs, the antenna is most likely unable

to acquire a signal.

Recommended action:

It is recommended to check the RSSI level and ensure that the antenna is able to locate a satellite. If not, service should be requested

09011 EV_ATB_MICRO_TEMP_TOO_LOW "Antenna - Microcontroller temperature too low"

09012 EV_ATB_MICRO_TEMP_TOO_HIGH "Antenna - Microcontroller temperature too high"

Microcontroller faults

The temperature of the microcontroller is monitored to protect the electronics from too high temperatures, and to decide when to

enter low temperature mode. If the temperature is too high, the electronics may be damaged. In cases where the temperature drops

below -30°C, the antenna will enter a low temperature mode, where the azimuth and elevation motor velocities are reduced by 40%,

during seek states.

Recommended action:

It is recommended to turn off the antenna to prevent the electronics from damage, if fault type 0x02

09013 EV_ATB_HEATER_FAULT "Antenna - Heater fault"

Heater fault

The heater is tested during the self-test by either turning it on or off at the beginning of the test, depending on the pre-test state. The

consequence of this fault may be degraded tracking performance, because of inaccurate sensor readings.

Recommended action:

If this fault occurs, it is recommended to wait a few minutes, to ensure that the ATB temperature is stable, and then restart the selftest

procedure. If the fault is still present and the antenna is used in a very cold environment, service should be requested.

09014 EV_ATB_HPA_TURNED_OFF "Antenna - HPA is turned off"

HPA off

If the HPA off signal is high, the ATB changes state to the initialisation state and remains there, until the HPA off signal is low.

Recommended action:

To remove this fault, the HPA should be turned on. If this does not remove the fault, it is recommended to check the wire between the HPA and the ATB.

09015 EV_ATB_NOT_ALIVE "Communication with antenna lost"

09016 EV_ATB_CALIBRATION_SWITCH_FAULT "Antenna calibration switch fault"

The calibration of the elevation angle is carried out, using a calibration switch. The functionality of this switch is verified during the self-test and antenna initialisation procedure. If the switch is defective, the antenna will calibrate against the mechanical limit of motion, i.e. the antenna panel will beat against the side section of the antenna. The calibration procedure will last slightly longer and be more audible, but the antenna will function.

09017 EV_ATB_FLASH_DATA_INTEGRITY_FAULT "Antenna flash memory corrupted"

Flash data integrity fault

The integrity of the microcontroller flash memory is checked during the antenna initialisation procedure, using a CRC32 checksum.

If the microcontroller flash memory is corrupted, the antenna functionality may be more or less affected. The antenna will continue

its operation if possible.

Recommended action:

If the antenna operation is affected by a data corruption it is recommended to reset the antenna and check if the fault disappears. If

the fault is still present, it is recommended to try uploading new software to the ATB and eventually request service, if this does not

remove the fault.

Sailor 250/150:

09112 EV_ACM_CM_TEMPERATURE "Temperature above limit"

09113 EV_ACM_CM_VOLTAGE  "ACM Voltage out of range"

09114 EV_ACM_CM_BDU_COMM "Terminal/ACM link error"

0911E EV_ACM_CM_IMU_RANGE "IMU sensor range check failed"

All sensors inputs, including sensor voltage and temperature are filtered through an outlier removal routine that keeps track of the mean and variance of each sensor, over 1 min . If invalid or statistically unexpected values are detected - outside 3 sigma, an error is reported.

If the temperature is above 90deg or below 30 deg Celsius, an alarm is reported and written to flash.

Inertial Measurement Unit

The IMU consist of three gyros, three accelerometers and a temperature sensor. An ADC is used to measure their outputs.

The CPU – ADC interface is a SPI bus running at 6 MHz. All sensors are sampled 384 times per second.

One channel of the ADC is used for measuring the ACM supply voltage

An IMU data set contains the following information:

1 us time stamp (32 bit).

Three accelerometer readings (3x16 bit).

Three gyros readings (3x16 bit).

ACM supply voltage (16 bit).

Temperature reading (16 bit).

0911F EV_ACM_CM_GPS_VALID "GPS communication failed"

When the GPS enters normal operation, two categories of data from the GPS exist:

Subscribed velocity data, received 4 times pr. Second.

Polled data (position, status, time and info), updated once pr 10s

The GPS activity is monitored in 2s intervals. The subscribed data rate must not be less than 7 messages/2s and the polled data stream is allowed to loose 2 messages/60s.

09120 EV_ACM_CM_GPS_RANGE "GPS data range check failed"

Check (x,y,z) velocity messages for: legal range, accuracy and sample interval (=250ms).

Ensure that calculated acceleration accuracy is inside legal range (<=5g).

09121 EV_ACM_CM_KALMAN  "Kalman covariance too high"

09122 EV_ACM_CM_ANT_POINTING "Pointing error too high"

If the difference between the kalman filter/tracking receiver angles and the desired target angle gets above a certain threshold, a pointing CM is issued.

09123 EV_ACM_CM_ANT_MOTOR_SLIP_A "Minor Motor A slip (HALL sensor) test failed"

09124 EV_ACM_CM_ANT_MOTOR_SLIP_B "Minor Motor B slip (HALL sensor) test failed"

09125 EV_ACM_CM_ANT_MOTOR_ZERO_RECAL "Major Motor slip (HALL sensor) test failed"

Antenna angle (azimuth or elevation) was detected outside upper or lower limits, recalibration automatically restarted.

09126 EV_ACM_CM_MDM_VOLTAGE "MDM Voltage out of range"

09127 EV_ACM_CM_KALMAN_REINIT "Kalman reinit test failed"

0912A EV_ACM_CM_MOTOR_STOPPED "Motor stopped"

 ACM/ATB POST

[0602:10] Passed Production data

Prod data check

Check the integrity of BSD data (prod + calibration info)

[0602:11] Passed xDM eeprom + tx gain

XDM eeprom or tx-gain 

This test covers generic eeprom data and antenna type specific data.

If the framing (i.e. crc, len or version) or one of the 5x Tx gains is zero this test shall fail.

[0602:12] Passed Antenna type test

Antenna type test

Check the antenna type defined used the I2C eeprom located on the cable between the ACM and the MDM or SDM.

If the antenna type not is programmed or the value is outside expected range the test will fail.

[0602:13] Passed Antenna calibration

Antenna calibration (2 axis) (250/150)

Go to zero from both directions using each motor and monitor the two HALL sensors. Find optimum zero by simple interpolation.

[0602:14] Passed Sensor sanity check

Sensor sanity check

Read a value from all sensors (accelerometers and gyros), if one of the values is outside the normal operation threshold, read 10 samples, and verify that all are valid, if not, the test shall fail.

Activate Sensor Test

This test is carried out during POST and has the info-severity (see chapter 3). Since the severity is under the reporting threshold, the result will always be unknown by for the BDU. The service person can only inspect the result on the acm.

Activate the pin for each sensor and qualify each output measured on A/D converter. If one of the values is outside 3 sigma(TBD) of the expected value, read 10 samples, and verify that all are valid, if not, the test shall fail.

[0602:16] Passed GPS alive

GPS Alive 

Check that communication between ACM- and GPS board during initialisation.

The init phase is split up into:

Configuration phase where the GPS module is configured to the ACM application by a number of UBX-CFG-messages.

Validation phase where the HW version is read as a last check before the POST verdict is reported.

HPA:

0921E EV_HPA_CM_VOLTAGE "HPA input voltage outside range"

0921F EV_HPA_CM_LOG_INTERVAL "HPA log interval exceeded"

09220 EV_HPA_CM_TEMP_RANGE "HPA temperature above critical limit"

09221 EV_HPA_CM_TXRX_GAIN_RANGE "Antenna module gain outside range"

09223 EV_HPA_CM_UNEXPECTED_VOLTAGE "HPA input voltage not what terminal expected"

ADU POST

[0601:10] Passed Production data

[0601:12] Passed Antenna interface

[0601:13] Passed GPS board detection

[0601:14] Passed FPGA test

Sailor 500B-C:

09628 EV_ATM_CM_TEMPERATURE "Temperature above limit"

The temperature is measured every 10 sec and compared against the temperature levels defined below. If the temperature is rising a check against the upper hysteresis level is made, and the opposite for a falling temperature. If a level is crossed, the appropriate action is taken.

If the temperature reaches too high (in upwards direction), an temperature event is issued. If the temperature reaches critically high or too low, an event is issued saying the motors are stopped.

09629 EV_ATM_CM_VOLTAGE "ATM Voltage out of range"

The supply voltage (28 V) is verified each 2.5 ms.

To prevent alarms from toggling when the voltage is close to the low limit, a hysteresis of 0.75 V is applied around the limit.

Minimum required voltage: 19.25 V ± 0.75 V.

0962A EV_ATM_CM_BDU_COMM "Terminal/ATM link error"

0962B EV_ATM_CM_MSU_RANGE "MSU sensor range check failed"

Outlier checks are performed on all MSU sensor data. If invalid or unexpected values are detected an event is reported.

Motion Sensor Unit (MSU)

The Motion Sensor Unit consists of the elevation and cross-elevation tilt sensors. Each tilt sensor consists of one gyro and two accelerometers, which provide analogue output. These outputs and a gyro reference voltage are sampled using an ADC. The seven values are sampled as a data set at regular time intervals.

0962C EV_ATM_CM_ATR_MISS  "ATR data block missed"

0962D EV_ATM_CM_GPS_VALID "GPS communication failed"

GPS Data Range Check

Check GPS data for any jumps or values that are outside legal range.

GPS Data Missing

Validate that the required GPS information is received periodically from the BDU.

0962F EV_ATM_CM_ANT_POINTING_ELE "Elevation pointing error too high"

09630 EV_ATM_CM_ANT_POINTING_XELE "Cross Elevation pointing error too high"

09631 EV_ATM_CM_ANT_POINTING_AZI "Azimuth pointing error too high"

If the difference between the kalman filter/tracking receiver angles and the desired target angle gets above a certain threshold, a pointing CM is issued.

09632 EV_ATM_CM_ANT_MOTOR_SLIP_ELE "Elevation motor slipped"

09633 EV_ATM_CM_ANT_MOTOR_SLIP_XELE "Cross Elevation motor slipped"

09634 EV_ATM_CM_ANT_MOTOR_SLIP_AZI "Azimuth motor slipped"

If the expected antenna angle (as seen from motor control) falls outside what is physically possible, motor slip is assumed.

This causes motor control to boost motor current and lower acceleration until the platform is stabilized again, and the motor slip state is called off again. This only applies on elevation and cross elevation axes.

09635 EV_ATM_CM_PLL_LOCK "ATM PLL out of lock"

09636 EV_ATM_CM_MOTOR_STOPPED "Motor stopped"

ACM/ATB POST

[0602:10] Passed Production data

Production Data Check

Check the integrity of the “production data” located in ATM FLASH.

[0602:11] Passed xDM eeprom + tx gain

XDM Data Check

Check the integrity of the “XDM data” located in ATR EEPROM.

[0602:12] Passed Antenna type test

Antenna Type Check

Check the antenna type (stored in XDM data).

If the antenna type is not one of those supported by this software the test shall fail.

[0602:13] Passed Antenna calibration

Antenna Calibration (2 Axis)

Verify that within a limited time, both the elevation and cross elevation axes can stabilize around the current desired angle, i.e. that the cross elevation axis is horizontal, and the elevation axis is at the correct elevation.

[0602:14] Passed Sensor sanity check

Sensor Sanity Check

This test is carried out during POST and has the info severity (see chapter 4). Since the severity is under the reporting threshold, the result will always be unknown by the BDU. The service person can only inspect the result on the ACM.
Read a value from all sensors (accelerometers and gyros), if one of the values is outside the normal operation threshold, read 10 samples, and verify that all are valid, if not, the test shall fail.

[0602:16] Passed GPS alive

[0603] Not tested - GPS POST

Test summary: 0 failed of 40 test

Alarms displayed in Explorer 300-500-700.

100-1: Post IMEI - IMEI number not programmed - ttlib_sysconf - System data damaged - Important system data is damaged. - Do not use the terminal. 

100-2: Post MAC Ethernet - MAC address is not programmed - ttlib_sysconf - System data damaged - Important system data is damaged. Do not use the terminal.  

100-3: Post UT class UT class is not programmed ttlib_sysconf - System data damaged - Important system data is damaged - Do not use the terminal.  

100-4: Post serial number - Serial number is not programmed - ttlib_sysconf - System data damaged - Important system data is damaged - Do not use the terminal. 

100-5: Post device type - Device type is not programmed - System data damaged - Important system data is damaged -Do not use the terminal. 

100-6: Post PCB ID - The PCB is not valid - ttlib_sysconf - System data damaged - Important system data is damaged - Do not use the terminal. 

200-1: Post battery interface - Interface to battery is defective – batmon - Battery error - Error during communication with the battery - The terminal can only be used with external power supply

210-1: Post USIM - TDA8007 register - Chip fails POST test – usim - SIM module error - The SIM interface cannot be used. 

210-2: Post USIM - TDA8007 file read - Chip fails POST test – usim - SIM module error - The SIM interface cannot be used. 

220-1: Post USB DW - Chip fails POST test - USB module error - The USB connection cannot be used.

230-1: Post I2C - Core temperature - Interface to Core temperature sensor is not working – temperature - Temperature sensor FATAL - The system is in danger of overheating - Do not use the terminal.

240-1: Post I2C - Display temperature - Interface to display temperature sensor is not working – temperature - Temperature sensor error – Automatic adjustment of the display contrast does not work.

250-1: Post Bluetooth - HCICTRL alive - Bluetooth module does not respond to alive – Bluetooth - Bluetooth module error - Bluetooth cannot be used.

250-2: Post Bluetooth - HCICTRL type - Undefined Bluetooth module – Bluetooth - Bluetooth module error - Bluetooth cannot be used. 

260-1: Post SATDSP RX - The RX DSP failed to initialize – dspif - System error - The terminal cannot communicate on the satellite network.

260-2: Post SATDSP TX - The TX DSP failed to initialize - dspif - System error - The terminal cannot communicate on the satellite network. 

260-3: Post Watchdog - The interface to the watchdog does not work - devs_watchdog - System error - Internal system error.

260-4: Post RX DSP IQ offset - RX DSP IQ calibration is out of range - dspif - System error - Internal system error - Do not use the terminal.

260-5: Post TX DSP VCOBANK - TX DSP VCOBANK calibration is out of range – dspif - System error - Internal system error - Do not use the terminal.

270-1: Post VOCDSP - The VOC DSP failed to initialize: - dspif - Voice module error - Voice services cannot be used.

280-1: Post Stenic - Chip fails POST test - devs_eth - Ethernet module error - Ethernet cannot be used.

280-2: Post REALTEK - Chip fails POST test - devs_eth - Ethernet module error - Ethernet cannot be used.

280-3: Post REALTEK EEPROM - Chip fails POST test - devs_eth - Ethernet module error - Ethernet cannot be used.

290-1: Post PSU - The interface to the power supply does not work – PSU - Power supply error - Power on/off, charging and LED control are out of function.

300-1: Post GPS - Chip fails POST test – gps - GPS module error - The GPS module is out of function - The terminal cannot obtain a valid GPS position.

310-1: Post CONX WLAN - Chip fails POST test - pro module - WLAN module error - WLAN cannot be used. 

320: Antenna failure - Antenna failure - The EXPLORER 700 is not able to detect the antenna - Make sure the antenna is properly connected to the tranceiver.

330: ISDN failure - ISDN failure - The ISDN interface on the EXPLORER 700 cannot be used.

340-1: POST 2-wire - Chip fails POST test - 2-wire module - 2-wire failure - 2-wire cannot be used.

 

Alarms defined for CM (continuous monitoring) 

1000: Temperature low – temperature - Temperature too low - Low ambient temperature is causing the performance of the terminal to be degraded or halted. Move the terminal to a warmer location.

1100: Temperature high – temperature - Data rate reduction due to high temperature - High ambient temperature is causing the performance of the terminal to be degraded or halted - Move the terminal to a cooler location. 

1200: Battery low - batmon - Battery level low The battery is running out of power - Charge the battery or replace it with a new one.

1300: No GPS fix – gps - No GPS fix - The GPS receiver has not yet achieved a position fix - If GPS fix cannot be achieved, try moving the terminal to a

position with clear sight. 

1400: Satellite signal lost - iai2 - Satellite signal lost - There is no longer signal from the satellite - Check the line of sight to the satellite and try re-pointing. 

1500: Missing USIM - usim - SIM card Missing - No SIM card is detected in the slot - Insert SIM card, or try removing the SIM card and reinserting it. 

1600: Limited service (SOS only) - umts-reg - SOS calls only - The SIM card is not accepted by the network - Only emergency calls are allowed - Enter the PIN code and wait for network approval.

1700: Register CS failed - umts-reg - Registration for voice failed - The terminal has not yet been allowed to register for voice services (Circuit Switched).

1800: Register PS failed - umts-reg - Registration for data failed - The terminal has not yet been allowed register for data services (Packet Switched).

1900: Battery temperature too low for charging – batmon - Temperature too low for charging - The temperature is too low for the battery charger to operate - If charging is needed, move the terminal to a warmer location. 

2000: Satellite signal weak - iai2 - Satellite signal weak - The signal from the satellite is weak - Check the line of sight to the satellite - If possible, try re-pointing. 

2100: Ciphering off - iai2-al - Ciphering off - The network has turned ciphering off - Do not transmit data that requires ciphering. 

2200: Connection for Ethernet failed – eth - Ethernet Connection failed - Ethernet connection could not be created.

2300: External antenna failure – antenna - External antenna failure - The terminal is not able to detect the external antenna type. 

1: Check 

2: Intern relay fail 

3: External relay fail 

4: No TX DSP response 

5: Invalid TX response 

6: Invalid GPIO state 

7: Invalid sample frequency 

8: Invalid sample time 

9: Invalid number of samples

 

2400: Invalid battery -  batmon - Invalid battery - The terminal is not able to detect the battery type.

2500: Errorlog buffer full – errlog - Errorlog full Internal system error - Send diagnostic report to your distributor. Clear errorlog 

2600: Antenna failure – antenna - Antenna failure - The terminal is not able to detect the state of antenna relay - Do not use the terminal.

2800: Bluetooth Device Database Full – Bluetooth - Bluetooth Device Database Full - No room left for Bluetooth devices - Unpair a paired device of your choice.

2810: Bluetooth overload blocks power save – Bluetooth - Bluetooth overload blocks pow - Too many Bluetooth devices in sleep - Unpair a device - preferrably the least used.   The alarm will take some time to disappear. If the alarm does not disappear, unpair another device. 

2900: Network failed authentication - umts-mm/gmm - Network failed authentication - Network failed authentication - Restart terminal.   

1: CS domain 

2:PS domain 

3000:Antenna burst loss - Antenna burst loss - The antenna failed to transmit- If the problem persists, contact your distributor. 

3100: Antenna cable loss calibration failed - Antenna cable loss calibration failed - The antenna cable loss cannot be determined. The cable may be broken or too long.

3200: AVR failure - AVR failure - Communication with an external AVR processor is not working - If the problem is recurrent, the EXPLORER 527 should be returned for repair.

3300: Antenna link down - Antenna link down - There is no connection with the antenna. The reason may be one of the following:

1. the cable is not connected properly or the cable is defective.

2. A processor in the antenna is faulty 

3. Check the cable and the connectors. Replace the cable if necessary.

4. Contact your supplier for repair of the antenna 

3400: HPA heat alarm - HPA heat alarm - The HPA in the antenna is overheated - Transmission from the antenna is not possible - Switch off the system until the HPA has cooled down. Then restart the system. 

3500: 2-wire calibration failure - 2-wire module - 2-wire calibration failure - 2-wire calibration failed, because 

1: common mode balance error. Check wires 

2: hook is off. Put hook on 

3: wires are shorted or shorted to ground. Check wires 

3600: 2-wire operational failure - 2-wire module - 2-wire operational failure - 2-wire operational failure 

1: Ground-shorted. Check wires 

2: Power overload. Wait a while, until interface is ready again 

3: Temperature overload. Wait a while, until interface is ready again 

3700: Calibration value - Calibration values are lost default values are used - Return terminal incl. antenna when possible 

3800: Software uploading - Wait a while, while SW is uploading. 

5000: Invalid image - The downloaded image is invalid download a valid image



LaunchPad


AT_ITSGLUSER=1 CME ERROR 3

During the Inmarsat lauchPad initialization the following message is displayed "error processing request AT_ITSGLUSER=1 CME ERROR 3 

Web interface is OK.

Terminal setup for multiple User Groups (more entries in the ‘Network Classification Table’)  

Delete all filters except the ‘default group’ 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

(368 vote(s))
This article was helpful
This article was not helpful

Comments (0)
Help Desk Software by Kayako Fusion