This is the description of the Shell API bindings for the GPS Bricklet. General information and technical specifications for the GPS Bricklet are summarized in its hardware description.
An installation guide for the Shell API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
1 2 3 4 5 6 7 | #!/bin/sh
# Connects to localhost:4223 by default, use --host and --port to change this
uid=XYZ # Change XYZ to the UID of your GPS Bricklet
# Get current coordinates
tinkerforge call gps-bricklet $uid get-coordinates
|
Download (example-callback.sh)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 | #!/bin/sh
# Connects to localhost:4223 by default, use --host and --port to change this
uid=XYZ # Change XYZ to the UID of your GPS Bricklet
# Handle incoming coordinates callbacks
tinkerforge dispatch gps-bricklet $uid coordinates &
# Set period for coordinates callback to 1s (1000ms)
# Note: The coordinates callback is only called every second
# if the coordinates has changed since the last call!
tinkerforge call gps-bricklet $uid set-coordinates-callback-period 1000
echo "Press key to exit"; read dummy
kill -- -$$ # Stop callback dispatch in background
|
Possible exit codes for all tinkerforge
commands are:
argparse
module is missingThe common options of the call
and dispatch
commands are documented
here. The specific command structure is shown below.
call
gps-bricklet
[<option>..] <uid> <function> [<argument>..]¶Parameters: |
|
---|
The call
command is used to call a function of the GPS Bricklet. It can take several
options:
--help
shows help for the specific call
command and exits--list-functions
shows a list of known functions of the GPS Bricklet and exitsdispatch
gps-bricklet
[<option>..] <uid> <callback>¶Parameters: |
|
---|
The dispatch
command is used to dispatch a callback of the GPS Bricklet. It can
take several options:
--help
shows help for the specific dispatch
command and exits--list-callbacks
shows a list of known callbacks of the GPS Bricklet and exitsgps-bricklet
<uid> <function>
[<option>..] [<argument>..]¶Parameters: |
|
---|
The <function>
to be called can take different options depending of its
kind. All functions can take the following options:
--help
shows help for the specific function and exitsGetter functions can take the following options:
--execute <command>
shell command line to execute for each incoming
response (see section about output formatting
for details)Setter functions can take the following options:
--expect-response
requests response and waits for itThe --expect-response
option for setter functions allows to detect
timeouts and other error conditions calls of setters as well. The device will
then send a response for this purpose. If this option is not given for a
setter function then no response is sent and errors are silently ignored,
because they cannot be detected.
gps-bricklet
<uid> <callback>
[<option>..]¶Parameters: |
|
---|
The <callback>
to be dispatched can take several options:
--help
shows help for the specific callback and exits--execute <command>
shell command line to execute for each incoming
response (see section about output formatting
for details)gps-bricklet
<uid> get-coordinates
¶Output: |
|
---|
Returns the GPS coordinates. Latitude and longitude are given in the
DD.dddddd°
format, the value 57123468 means 57.123468°.
The parameter ns
and ew
are the cardinal directions for
latitude and longitude. Possible values for ns
and ew
are 'N', 'S', 'E'
and 'W' (north, south, east and west).
PDOP, HDOP and VDOP are the dilution of precision (DOP) values. They specify the additional multiplicative effect of GPS satellite geometry on GPS precision. See here for more information.
EPE is the "Estimated Position Error". This is not the absolute maximum error, it is the error with a specific confidence. See here for more information.
This data is only valid if there is currently a fix as indicated by
get-status
.
gps-bricklet
<uid> get-status
¶Output: |
|
---|
Returns the current fix status, the number of satellites that are in view and the number of satellites that are currently used.
Possible fix status values can be:
Value | Description |
---|---|
1 | No Fix, get-coordinates , get-altitude and get-motion return invalid data |
2 | 2D Fix, only get-coordinates and get-motion return valid data |
3 | 3D Fix, get-coordinates , get-altitude and get-motion return valid data |
There is also a blue LED on the Bricklet that indicates the fix status.
The following symbols are available for this function:
For fix:
gps-bricklet
<uid> get-altitude
¶Output: |
|
---|
Returns the current altitude and corresponding geoidal separation.
This data is only valid if there is currently a fix as indicated by
get-status
.
gps-bricklet
<uid> get-motion
¶Output: |
|
---|
Returns the current course and speed. A course of 0° means the Bricklet is traveling north bound and 90° means it is traveling east bound.
Please note that this only returns useful values if an actual movement is present.
This data is only valid if there is currently a fix as indicated by
get-status
.
gps-bricklet
<uid> get-date-time
¶Output: |
|
---|
Returns the current date and time. The date is
given in the format ddmmyy
and the time is given
in the format hhmmss.sss
. For example, 140713 means
14.07.13 as date and 195923568 means 19:59:23.568 as time.
gps-bricklet
<uid> restart
<restart-type>¶Parameters: |
|
---|---|
Output: |
|
Restarts the GPS Bricklet, the following restart types are available:
Value | Description |
---|---|
0 | Hot start (use all available data in the NV store) |
1 | Warm start (don't use ephemeris at restart) |
2 | Cold start (don't use time, position, almanacs and ephemeris at restart) |
3 | Factory reset (clear all system/user configurations at restart) |
The following symbols are available for this function:
For <restart-type>:
gps-bricklet
<uid> get-identity
¶Output: |
|
---|
Returns the UID, the UID where the Bricklet is connected to, the position, the hardware and firmware version as well as the device identifier.
The position can be 'a', 'b', 'c', 'd', 'e', 'f', 'g' or 'h' (Bricklet Port). A Bricklet connected to an Isolator Bricklet is always at position 'z'.
The device identifier numbers can be found here.
gps-bricklet
<uid> set-coordinates-callback-period
<period>¶Parameters: |
|
---|---|
Output: |
|
Sets the period with which the coordinates
callback is triggered
periodically. A value of 0 turns the callback off.
The coordinates
callback is only triggered if the coordinates changed
since the last triggering.
gps-bricklet
<uid> get-coordinates-callback-period
¶Output: |
|
---|
Returns the period as set by set-coordinates-callback-period
.
gps-bricklet
<uid> set-status-callback-period
<period>¶Parameters: |
|
---|---|
Output: |
|
Sets the period with which the status
callback is triggered
periodically. A value of 0 turns the callback off.
The status
callback is only triggered if the status changed since the
last triggering.
gps-bricklet
<uid> get-status-callback-period
¶Output: |
|
---|
Returns the period as set by set-status-callback-period
.
gps-bricklet
<uid> set-altitude-callback-period
<period>¶Parameters: |
|
---|---|
Output: |
|
Sets the period with which the altitude
callback is triggered
periodically. A value of 0 turns the callback off.
The altitude
callback is only triggered if the altitude changed since
the last triggering.
gps-bricklet
<uid> get-altitude-callback-period
¶Output: |
|
---|
Returns the period as set by set-altitude-callback-period
.
gps-bricklet
<uid> set-motion-callback-period
<period>¶Parameters: |
|
---|---|
Output: |
|
Sets the period with which the motion
callback is triggered
periodically. A value of 0 turns the callback off.
The motion
callback is only triggered if the motion changed since the
last triggering.
gps-bricklet
<uid> get-motion-callback-period
¶Output: |
|
---|
Returns the period as set by set-motion-callback-period
.
gps-bricklet
<uid> set-date-time-callback-period
<period>¶Parameters: |
|
---|---|
Output: |
|
Sets the period with which the date-time
callback is triggered
periodically. A value of 0 turns the callback off.
The date-time
callback is only triggered if the date or time changed
since the last triggering.
gps-bricklet
<uid> get-date-time-callback-period
¶Output: |
|
---|
Returns the period as set by set-date-time-callback-period
.
Callbacks can be used to receive time critical or recurring data from the device:
tinkerforge dispatch gps-bricklet <uid> example
The available callbacks are described below.
Note
Using callbacks for recurring events is always preferred compared to using getters. It will use less USB bandwidth and the latency will be a lot better, since there is no round trip time.
gps-bricklet
<uid> coordinates
¶Output: |
|
---|
This callback is triggered periodically with the period that is set by
set-coordinates-callback-period
. The parameters are the same
as for get-coordinates
.
The coordinates
callback is only triggered if the coordinates changed
since the last triggering and if there is currently a fix as indicated by
get-status
.
gps-bricklet
<uid> status
¶Output: |
|
---|
This callback is triggered periodically with the period that is set by
set-status-callback-period
. The parameters are the same
as for get-status
.
The status
callback is only triggered if the status changed since the
last triggering.
The following symbols are available for this function:
For fix:
gps-bricklet
<uid> altitude
¶Output: |
|
---|
This callback is triggered periodically with the period that is set by
set-altitude-callback-period
. The parameters are the same
as for get-altitude
.
The altitude
callback is only triggered if the altitude changed since
the last triggering and if there is currently a fix as indicated by
get-status
.
gps-bricklet
<uid> motion
¶Output: |
|
---|
This callback is triggered periodically with the period that is set by
set-motion-callback-period
. The parameters are the same
as for get-motion
.
The motion
callback is only triggered if the motion changed since the
last triggering and if there is currently a fix as indicated by
get-status
.
gps-bricklet
<uid> date-time
¶Output: |
|
---|
This callback is triggered periodically with the period that is set by
set-date-time-callback-period
. The parameters are the same
as for get-date-time
.
The date-time
callback is only triggered if the date or time changed
since the last triggering.