Raven and PinPoint CDMA User Guide Version 1.12
AirLink Communications, Inc. Page 37 March 24, 2004
RAP commands on port 17335 and not TAIP commands on port 21000. To accept
TAIP commands, *PPGPSR would have to be set to F0.
7.4 RAP Poll Command The RAP poll command can be issued by the local client (i.e. PPP/SLIP peer) to force
a new local report to be transmitted in response. If a RAP poll command is not from
the IP of the PPP/SLIP peer (i.e. IP in S110), the poll will be performed normally (i.e.
the response will go to the server at *PPIP).
7.5 TAIP Emulation The TAIP emulation functionality allows the PinPoint product to operate in a limited
manner with clients which only understand the Trimble ASCII Interface Protocol
(TAIP). TAIP emulation is enabled by setting the GPS report type to F0 (e.g.
AT*PPGPSR=F0 or AT*PPLATSR=F0). Once TAIP emulation is entered, the
PinPoint will listen for TAIP messages on port 21000 and will no longer
handle/generate RAP messages.
The automatic reports will be sent to the server configured with the *PPIP and
*PPPORT AT commands. This behavior is different than standard TAIP since TAIP
will instead simply report to the last client to request automatic reports.
The TAIP emulation will accept the following TAIP message types:
SRM – allows the client to set reporting mode configuration. The report mode
configuration is not stored in non-volatile memory and such should be reset upon a
unit reset. This behavior emulates that specified in TAIP spec.
QRM – reports the reporting mode configuration (returns an RRM message)
SID – allows the client to set the TAIP ID (AT*PPTAIPID can also be used to set
the TAIP ID). The TAIP ID, when set with a SID message, will be written to non-
volatile memory.
QID – reports the TAIP ID (returns an RID message).
DPV – configures automatic reporting of PV (Position/Velocity) reports based on
distance traveled and a maximum time. The delta distance value specified in the
message is converted to hundreds of meters and stored as *PPDIST. The maximum
time interval is stored as *PPTIME and the minimum time is stored as
*PPMINTIME. The epoch value is ignored.
FPV – configures periodic reporting of PV (Position/Velocity) reports. The time
interval from the message is stored at *PPTIME. Currently the epoch value is
ignored.
QPV – responds with a PV (Position/Velocity) report.
The TAIP emulation will generate the following reports corresponding to the
appropriate event (either a query for it, echoed due to a set, or due to an automatic
reporting event):
RRM – reports the reporting mode configuration.
RID – reports the TAIP ID.
RPV – Position/Velocity report.