Confidential
USERS MANUAL
82(158)
Document number
Revision
1/198 17-4/FCP 101 3045 Uen
D
Parameter
Description
00000001
Notification when the service has been lost. i.e. Going from either AMPS or
Digital service to NO SERVICE.
00000002
Notification when service is changed. Three conditions apply:
•
Going from no service to service (either Digital or AMPS)
•
Going from Digital to AMPS service
•
Going from AMPS to Digital service
Note: Changing SID and remaining on the same service type will NOT trigger
the Ring Indicator.
00000004
Notification of an incoming voice call
00000008
Notification of an incoming data call
00000010
Notification of an incoming SMS message
00000020
Notification of an incoming voice mail indication
00000040
Notification that the RTC cycle has completed
00000080
Notification of an Antenna failure (refer to AT*EAFF)
00000100
Notification of an Antenna Diagnostic State change (refer to AT*EANTLIM)
00000200
Notification that the duration for holding the module awake has expired
4.9.4
AT*EWAKE (Query Wakeup Event)
Description
Syntax
Possible responses
Reads the wakeup event
AT*EWAKE?
*EWAKESET: <bit mask>
OK
This command queries the origin of the wakeup. All events that took place from the time the module is
powered on until the AT*EWAKE command is issued are OR’ed in the bit mask.
The reason(s) for wakeup is cleared when the AT*EWAKE command is issued or when the module is powered
off. In addition, if the RI pin is still set asserted at the time of execution of this command the pin is de-asserted.
It is recommended that the application poll the module immediately upon starting up to determine the event
that triggered the Ring Indicator. Some events are dependent upon external resources (for example, the
network) and may terminate if not handled immediately. For example, if an incoming voice call is not handled
in a timely manner, the network will reroute the call to voicemail.
It is recommended that the host application issue AT*EWAKE immediately before powering down if the
intention is to leave the CM52 powered on. This resets the wakeup reason, and no “old” events are indicated
when in fact they did not happen during the time the host application was powered down. This is necessary
because the wakeup reason can be set, and the RI pin asserted during normal execution when the host
application is powered on.
Refer to AT*EWAKESET for a description of the bit mask parameter.
Note:
Due to the multitasked nature of the software, the Ring Indicator and the unsolicited messages
are not tied to the same task; therefore, it is possible that notification of an event from the RI is not
matched exactly to the notification of the event through an unsolicited message.