This is the description of the Perl API bindings for the GPS Bricklet 2.0. General information and technical specifications for the GPS Bricklet 2.0 are summarized in its hardware description.
An installation guide for the Perl 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 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 | #!/usr/bin/perl
use strict;
use Tinkerforge::IPConnection;
use Tinkerforge::BrickletGPSV2;
use constant HOST => 'localhost';
use constant PORT => 4223;
use constant UID => 'XYZ'; # Change XYZ to the UID of your GPS Bricklet 2.0
my $ipcon = Tinkerforge::IPConnection->new(); # Create IP connection
my $gps = Tinkerforge::BrickletGPSV2->new(&UID, $ipcon); # Create device object
$ipcon->connect(&HOST, &PORT); # Connect to brickd
# Don't use device before ipcon is connected
# Get current coordinates
my ($latitude, $ns, $longitude, $ew) = $gps->get_coordinates();
print "Latitude: " . $latitude/1000000.0 . " °\n";
print "N/S: $ns\n";
print "Longitude: " . $longitude/1000000.0 . " °\n";
print "E/W: $ew\n";
print "Press key to exit\n";
<STDIN>;
$ipcon->disconnect();
|
Download (example_callback.pl)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 | #!/usr/bin/perl
use strict;
use Tinkerforge::IPConnection;
use Tinkerforge::BrickletGPSV2;
use constant HOST => 'localhost';
use constant PORT => 4223;
use constant UID => 'XYZ'; # Change XYZ to the UID of your GPS Bricklet 2.0
# Callback subroutine for coordinates callback
sub cb_coordinates
{
my ($latitude, $ns, $longitude, $ew) = @_;
print "Latitude: " . $latitude/1000000.0 . " °\n";
print "N/S: $ns\n";
print "Longitude: " . $longitude/1000000.0 . " °\n";
print "E/W: $ew\n";
print "\n";
}
my $ipcon = Tinkerforge::IPConnection->new(); # Create IP connection
my $gps = Tinkerforge::BrickletGPSV2->new(&UID, $ipcon); # Create device object
$ipcon->connect(&HOST, &PORT); # Connect to brickd
# Don't use device before ipcon is connected
# Register coordinates callback to subroutine cb_coordinates
$gps->register_callback($gps->CALLBACK_COORDINATES, 'cb_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!
$gps->set_coordinates_callback_period(1000);
print "Press key to exit\n";
<STDIN>;
$ipcon->disconnect();
|
Generally, every subroutine of the Perl bindings can report an error as
Tinkerforge::Error
object via croak()
. The object has a
get_code()
and a get_message()
subroutine. There are different
error code:
All functions listed below are thread-safe.
BrickletGPSV2
->
new
($uid, $ipcon)¶Parameters: |
|
---|---|
Returns: |
|
Creates an object with the unique device ID $uid
:
$gps_v2 = BrickletGPSV2->new("YOUR_DEVICE_UID", $ipcon);
This object can then be used after the IP Connection is connected.
BrickletGPSV2
->
get_coordinates
()¶Return Array: |
|
---|
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).
This data is only valid if there is currently a fix as indicated by
get_status()
.
BrickletGPSV2
->
get_status
()¶Return Array: |
|
---|
Returns if a fix is currently available as well as the number of satellites that are in view.
There is also a green LED on the Bricklet that indicates the fix status.
BrickletGPSV2
->
get_altitude
()¶Return Array: |
|
---|
Returns the current altitude and corresponding geoidal separation.
This data is only valid if there is currently a fix as indicated by
get_status()
.
BrickletGPSV2
->
get_motion
()¶Return Array: |
|
---|
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()
.
BrickletGPSV2
->
get_date_time
()¶Return Array: |
|
---|
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.
BrickletGPSV2
->
get_satellite_system_status
($satellite_system)¶Parameters: |
|
---|---|
Return Array: |
|
Returns the
for a given satellite system. Currently GPS and GLONASS are supported, Galileo is not yet supported.
The GPS and GLONASS satellites have unique numbers and the satellite list gives the numbers of the satellites that are currently utilized. The number 0 is not a valid satellite number and can be ignored in the list.
The following constants are available for this function:
For $satellite_system:
For $fix:
BrickletGPSV2
->
get_satellite_status
($satellite_system, $satellite_number)¶Parameters: |
|
---|---|
Return Array: |
|
Returns the current elevation, azimuth and SNR for a given satellite and satellite system.
The satellite number here always goes from 1 to 32. For GLONASS it corresponds to the satellites 65-96.
Galileo is not yet supported.
The following constants are available for this function:
For $satellite_system:
BrickletGPSV2
->
restart
($restart_type)¶Parameters: |
|
---|---|
Returns: |
|
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 constants are available for this function:
For $restart_type:
BrickletGPSV2
->
set_fix_led_config
($config)¶Parameters: |
|
---|---|
Returns: |
|
Sets the fix LED configuration. By default the LED shows if the Bricklet got a GPS fix yet. If a fix is established the LED turns on. If there is no fix then the LED is turned off.
You can also turn the LED permanently on/off, show a heartbeat or let it blink in sync with the PPS (pulse per second) output of the GPS module.
If the Bricklet is in bootloader mode, the LED is off.
The following constants are available for this function:
For $config:
BrickletGPSV2
->
get_fix_led_config
()¶Returns: |
|
---|
Returns the configuration as set by set_fix_led_config()
The following constants are available for this function:
For $config:
BrickletGPSV2
->
set_sbas_config
($sbas_config)¶Parameters: |
|
---|---|
Returns: |
|
If SBAS is enabled, the position accuracy increases (if SBAS satellites are in view), but the update rate is limited to 5Hz. With SBAS disabled the update rate is increased to 10Hz.
The following constants are available for this function:
For $sbas_config:
New in version 2.0.2 (Plugin).
BrickletGPSV2
->
get_sbas_config
()¶Returns: |
|
---|
Returns the SBAS configuration as set by set_sbas_config()
The following constants are available for this function:
For $sbas_config:
New in version 2.0.2 (Plugin).
BrickletGPSV2
->
get_spitfp_error_count
()¶Return Array: |
|
---|
Returns the error count for the communication between Brick and Bricklet.
The errors are divided into
The errors counts are for errors that occur on the Bricklet side. All Bricks have a similar function that returns the errors on the Brick side.
BrickletGPSV2
->
set_status_led_config
($config)¶Parameters: |
|
---|---|
Returns: |
|
Sets the status LED configuration. By default the LED shows communication traffic between Brick and Bricklet, it flickers once for every 10 received data packets.
You can also turn the LED permanently on/off or show a heartbeat.
If the Bricklet is in bootloader mode, the LED is will show heartbeat by default.
The following constants are available for this function:
For $config:
BrickletGPSV2
->
get_status_led_config
()¶Returns: |
|
---|
Returns the configuration as set by set_status_led_config()
The following constants are available for this function:
For $config:
BrickletGPSV2
->
get_chip_temperature
()¶Returns: |
|
---|
Returns the temperature as measured inside the microcontroller. The value returned is not the ambient temperature!
The temperature is only proportional to the real temperature and it has bad accuracy. Practically it is only useful as an indicator for temperature changes.
BrickletGPSV2
->
reset
()¶Returns: |
|
---|
Calling this function will reset the Bricklet. All configurations will be lost.
After a reset you have to create new device objects, calling functions on the existing ones will result in undefined behavior!
BrickletGPSV2
->
get_identity
()¶Return Array: |
|
---|
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. There is also a constant for the device identifier of this Bricklet.
BrickletGPSV2
->
register_callback
($callback_id, $function)¶Parameters: |
|
---|---|
Returns: |
|
Registers the given $function
name with the given $callback_id
.
The available callback IDs with corresponding function signatures are listed below.
BrickletGPSV2
->
set_coordinates_callback_period
($period)¶Parameters: |
|
---|---|
Returns: |
|
Sets the period with which the CALLBACK_COORDINATES
callback is triggered
periodically. A value of 0 turns the callback off.
The CALLBACK_COORDINATES
callback is only triggered if the coordinates changed
since the last triggering.
BrickletGPSV2
->
get_coordinates_callback_period
()¶Returns: |
|
---|
Returns the period as set by set_coordinates_callback_period()
.
BrickletGPSV2
->
set_status_callback_period
($period)¶Parameters: |
|
---|---|
Returns: |
|
Sets the period with which the CALLBACK_STATUS
callback is triggered
periodically. A value of 0 turns the callback off.
The CALLBACK_STATUS
callback is only triggered if the status changed since the
last triggering.
BrickletGPSV2
->
get_status_callback_period
()¶Returns: |
|
---|
Returns the period as set by set_status_callback_period()
.
BrickletGPSV2
->
set_altitude_callback_period
($period)¶Parameters: |
|
---|---|
Returns: |
|
Sets the period with which the CALLBACK_ALTITUDE
callback is triggered
periodically. A value of 0 turns the callback off.
The CALLBACK_ALTITUDE
callback is only triggered if the altitude changed since the
last triggering.
BrickletGPSV2
->
get_altitude_callback_period
()¶Returns: |
|
---|
Returns the period as set by set_altitude_callback_period()
.
BrickletGPSV2
->
set_motion_callback_period
($period)¶Parameters: |
|
---|---|
Returns: |
|
Sets the period with which the CALLBACK_MOTION
callback is triggered
periodically. A value of 0 turns the callback off.
The CALLBACK_MOTION
callback is only triggered if the motion changed since the
last triggering.
BrickletGPSV2
->
get_motion_callback_period
()¶Returns: |
|
---|
Returns the period as set by set_motion_callback_period()
.
BrickletGPSV2
->
set_date_time_callback_period
($period)¶Parameters: |
|
---|---|
Returns: |
|
Sets the period with which the CALLBACK_DATE_TIME
callback is triggered
periodically. A value of 0 turns the callback off.
The CALLBACK_DATE_TIME
callback is only triggered if the date or time changed
since the last triggering.
BrickletGPSV2
->
get_date_time_callback_period
()¶Returns: |
|
---|
Returns the period as set by set_date_time_callback_period()
.
Callbacks can be registered to receive
time critical or recurring data from the device. The registration is done
with the register_callback()
function of
the device object. The first parameter is the callback ID and the second
parameter the callback function name:
sub my_callback
{
print "@_[0]";
}
$gps_v2->register_callback(BrickletGPSV2->CALLBACK_EXAMPLE, 'my_callback')
The callback function will be called from an internal thread of the
IP Connection. In contrast to many other programming languages, variables are
not automatically shared between threads in Perl. If you want to share a global
variable between a callback function and the rest for your program it has to be
marked as :shared
. See the documentation of the threads::shared Perl module for more details.
The available constants with inherent number and type of parameters 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.
BrickletGPSV2
->
CALLBACK_PULSE_PER_SECOND
¶Callback Parameters: |
|
---|
This callback is triggered precisely once per second, see PPS.
The precision of two subsequent pulses will be skewed because of the latency in the USB/RS485/Ethernet connection. But in the long run this will be very precise. For example a count of 3600 pulses will take exactly 1 hour.
BrickletGPSV2
->
CALLBACK_COORDINATES
¶Callback Parameters: |
|
---|
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 CALLBACK_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()
.
BrickletGPSV2
->
CALLBACK_STATUS
¶Callback Parameters: |
|
---|
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 CALLBACK_STATUS
callback is only triggered if the status changed since the
last triggering.
BrickletGPSV2
->
CALLBACK_ALTITUDE
¶Callback Parameters: |
|
---|
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 CALLBACK_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()
.
BrickletGPSV2
->
CALLBACK_MOTION
¶Callback Parameters: |
|
---|
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 CALLBACK_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()
.
BrickletGPSV2
->
CALLBACK_DATE_TIME
¶Callback Parameters: |
|
---|
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 CALLBACK_DATE_TIME
callback is only triggered if the date or time changed
since the last triggering.
Virtual functions don't communicate with the device itself, but operate only on the API bindings device object. They can be called without the corresponding IP Connection object being connected.
BrickletGPSV2
->
get_api_version
()¶Return Array: |
|
---|
Returns the version of the API definition implemented by this API bindings. This is neither the release version of this API bindings nor does it tell you anything about the represented Brick or Bricklet.
BrickletGPSV2
->
get_response_expected
($function_id)¶Parameters: |
|
---|---|
Returns: |
|
Returns the response expected flag for the function specified by the function ID parameter. It is true if the function is expected to send a response, false otherwise.
For getter functions this is enabled by default and cannot be disabled,
because those functions will always send a response. For callback configuration
functions it is enabled by default too, but can be disabled by
set_response_expected()
. For setter functions it is disabled by default
and can be enabled.
Enabling the response expected flag for a setter function allows to detect timeouts and other error conditions calls of this setter as well. The device will then send a response for this purpose. If this flag is disabled for a setter function then no response is sent and errors are silently ignored, because they cannot be detected.
The following constants are available for this function:
For $function_id:
BrickletGPSV2
->
set_response_expected
($function_id, $response_expected)¶Parameters: |
|
---|---|
Returns: |
|
Changes the response expected flag of the function specified by the function ID parameter. This flag can only be changed for setter (default value: false) and callback configuration functions (default value: true). For getter functions it is always enabled.
Enabling the response expected flag for a setter function allows to detect timeouts and other error conditions calls of this setter as well. The device will then send a response for this purpose. If this flag is disabled for a setter function then no response is sent and errors are silently ignored, because they cannot be detected.
The following constants are available for this function:
For $function_id:
BrickletGPSV2
->
set_response_expected_all
($response_expected)¶Parameters: |
|
---|---|
Returns: |
|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
Internal functions are used for maintenance tasks such as flashing a new firmware of changing the UID of a Bricklet. These task should be performed using Brick Viewer instead of using the internal functions directly.
BrickletGPSV2
->
set_bootloader_mode
($mode)¶Parameters: |
|
---|---|
Returns: |
|
Sets the bootloader mode and returns the status after the requested mode change was instigated.
You can change from bootloader mode to firmware mode and vice versa. A change from bootloader mode to firmware mode will only take place if the entry function, device identifier and CRC are present and correct.
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
The following constants are available for this function:
For $mode:
For $status:
BrickletGPSV2
->
get_bootloader_mode
()¶Returns: |
|
---|
Returns the current bootloader mode, see set_bootloader_mode()
.
The following constants are available for this function:
For $mode:
BrickletGPSV2
->
set_write_firmware_pointer
($pointer)¶Parameters: |
|
---|---|
Returns: |
|
Sets the firmware pointer for write_firmware()
. The pointer has
to be increased by chunks of size 64. The data is written to flash
every 4 chunks (which equals to one page of size 256).
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
BrickletGPSV2
->
write_firmware
(\@data)¶Parameters: |
|
---|---|
Returns: |
|
Writes 64 Bytes of firmware at the position as written by
set_write_firmware_pointer()
before. The firmware is written
to flash every 4 chunks.
You can only write firmware in bootloader mode.
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
BrickletGPSV2
->
write_uid
($uid)¶Parameters: |
|
---|---|
Returns: |
|
Writes a new UID into flash. If you want to set a new UID you have to decode the Base58 encoded UID string into an integer first.
We recommend that you use Brick Viewer to change the UID.
BrickletGPSV2
->
read_uid
()¶Returns: |
|
---|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
BrickletGPSV2
->
DEVICE_IDENTIFIER
¶This constant is used to identify a GPS Bricklet 2.0.
The get_identity()
function and the
IPConnection->CALLBACK_ENUMERATE
callback of the IP Connection have a device_identifier
parameter to specify
the Brick's or Bricklet's type.
BrickletGPSV2
->
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a GPS Bricklet 2.0.