This is the description of the MATLAB/Octave 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 MATLAB/Octave API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
Download (matlab_example_simple.m)
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 | function matlab_example_simple()
import com.tinkerforge.IPConnection;
import com.tinkerforge.BrickletGPS;
HOST = 'localhost';
PORT = 4223;
UID = 'XYZ'; % Change XYZ to the UID of your GPS Bricklet
ipcon = IPConnection(); % Create IP connection
gps = handle(BrickletGPS(UID, ipcon), 'CallbackProperties'); % Create device object
ipcon.connect(HOST, PORT); % Connect to brickd
% Don't use device before ipcon is connected
% Get current coordinates
coordinates = gps.getCoordinates();
fprintf('Latitude: %g °\n', coordinates.latitude/1000000.0);
fprintf('N/S: %s\n', coordinates.ns);
fprintf('Longitude: %g °\n', coordinates.longitude/1000000.0);
fprintf('E/W: %s\n', coordinates.ew);
input('Press key to exit\n', 's');
ipcon.disconnect();
end
|
Download (matlab_example_callback.m)
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 | function matlab_example_callback()
import com.tinkerforge.IPConnection;
import com.tinkerforge.BrickletGPS;
HOST = 'localhost';
PORT = 4223;
UID = 'XYZ'; % Change XYZ to the UID of your GPS Bricklet
ipcon = IPConnection(); % Create IP connection
gps = handle(BrickletGPS(UID, ipcon), 'CallbackProperties'); % Create device object
ipcon.connect(HOST, PORT); % Connect to brickd
% Don't use device before ipcon is connected
% Register coordinates callback to function cb_coordinates
set(gps, 'CoordinatesCallback', @(h, e) cb_coordinates(e));
% 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.setCoordinatesCallbackPeriod(1000);
input('Press key to exit\n', 's');
ipcon.disconnect();
end
% Callback function for coordinates callback
function cb_coordinates(e)
fprintf('Latitude: %g °\n', e.latitude/1000000.0);
fprintf('N/S: %s\n', e.ns);
fprintf('Longitude: %g °\n', e.longitude/1000000.0);
fprintf('E/W: %s\n', e.ew);
fprintf('\n');
end
|
Download (octave_example_simple.m)
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 | function octave_example_simple()
more off;
HOST = "localhost";
PORT = 4223;
UID = "XYZ"; % Change XYZ to the UID of your GPS Bricklet
ipcon = javaObject("com.tinkerforge.IPConnection"); % Create IP connection
gps = javaObject("com.tinkerforge.BrickletGPS", UID, ipcon); % Create device object
ipcon.connect(HOST, PORT); % Connect to brickd
% Don't use device before ipcon is connected
% Get current coordinates
coordinates = gps.getCoordinates();
fprintf("Latitude: %g °\n", java2int(coordinates.latitude)/1000000.0);
fprintf("N/S: %s\n", coordinates.ns);
fprintf("Longitude: %g °\n", java2int(coordinates.longitude)/1000000.0);
fprintf("E/W: %s\n", coordinates.ew);
input("Press key to exit\n", "s");
ipcon.disconnect();
end
function int = java2int(value)
if compare_versions(version(), "3.8", "<=")
int = value.intValue();
else
int = value;
end
end
|
Download (octave_example_callback.m)
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 40 41 | function octave_example_callback()
more off;
HOST = "localhost";
PORT = 4223;
UID = "XYZ"; % Change XYZ to the UID of your GPS Bricklet
ipcon = javaObject("com.tinkerforge.IPConnection"); % Create IP connection
gps = javaObject("com.tinkerforge.BrickletGPS", UID, ipcon); % Create device object
ipcon.connect(HOST, PORT); % Connect to brickd
% Don't use device before ipcon is connected
% Register coordinates callback to function cb_coordinates
gps.addCoordinatesCallback(@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.setCoordinatesCallbackPeriod(1000);
input("Press key to exit\n", "s");
ipcon.disconnect();
end
% Callback function for coordinates callback
function cb_coordinates(e)
fprintf("Latitude: %g °\n", java2int(e.latitude)/1000000.0);
fprintf("N/S: %s\n", e.ns);
fprintf("Longitude: %g °\n", java2int(e.longitude)/1000000.0);
fprintf("E/W: %s\n", e.ew);
fprintf("\n");
end
function int = java2int(value)
if compare_versions(version(), "3.8", "<=")
int = value.intValue();
else
int = value;
end
end
|
Generally, every method of the MATLAB bindings that returns a value can
throw a TimeoutException
. This exception gets thrown if the
device did not respond. If a cable based connection is used, it is
unlikely that this exception gets thrown (assuming nobody unplugs the
device). However, if a wireless connection is used, timeouts will occur
if the distance to the device gets too big.
Beside the TimeoutException
there is also a NotConnectedException
that
is thrown if a method needs to communicate with the device while the
IP Connection is not connected.
Since the MATLAB bindings are based on Java and Java does not support multiple return values and return by reference is not possible for primitive types, we use small classes that only consist of member variables. The member variables of the returned objects are described in the corresponding method descriptions.
The package for all Brick/Bricklet bindings and the IP Connection is
com.tinkerforge.*
All methods listed below are thread-safe.
BrickletGPS
(String uid, IPConnection ipcon)¶Parameters: |
|
---|---|
Returns: |
|
Creates an object with the unique device ID uid
.
In MATLAB:
import com.tinkerforge.BrickletGPS;
gps = BrickletGPS('YOUR_DEVICE_UID', ipcon);
In Octave:
gps = java_new("com.tinkerforge.BrickletGPS", "YOUR_DEVICE_UID", ipcon);
This object can then be used after the IP Connection is connected.
BrickletGPS.
getCoordinates
()¶Return Object: |
|
---|
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
getStatus()
.
BrickletGPS.
getStatus
()¶Return Object: |
|
---|
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, getCoordinates() , getAltitude() and getMotion() return invalid data |
2 | 2D Fix, only getCoordinates() and getMotion() return valid data |
3 | 3D Fix, getCoordinates() , getAltitude() and getMotion() return valid data |
There is also a blue LED on the Bricklet that indicates the fix status.
The following constants are available for this function:
For fix:
BrickletGPS.
getAltitude
()¶Return Object: |
|
---|
Returns the current altitude and corresponding geoidal separation.
This data is only valid if there is currently a fix as indicated by
getStatus()
.
BrickletGPS.
getMotion
()¶Return Object: |
|
---|
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
getStatus()
.
BrickletGPS.
getDateTime
()¶Return Object: |
|
---|
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.
BrickletGPS.
restart
(short restartType)¶Parameters: |
|
---|
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 restartType:
BrickletGPS.
getIdentity
()¶Return Object: |
|
---|
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.
BrickletGPS.
setCoordinatesCallbackPeriod
(long period)¶Parameters: |
|
---|
Sets the period with which the CoordinatesCallback
callback is triggered
periodically. A value of 0 turns the callback off.
The CoordinatesCallback
callback is only triggered if the coordinates changed
since the last triggering.
BrickletGPS.
getCoordinatesCallbackPeriod
()¶Returns: |
|
---|
Returns the period as set by setCoordinatesCallbackPeriod()
.
BrickletGPS.
setStatusCallbackPeriod
(long period)¶Parameters: |
|
---|
Sets the period with which the StatusCallback
callback is triggered
periodically. A value of 0 turns the callback off.
The StatusCallback
callback is only triggered if the status changed since the
last triggering.
BrickletGPS.
getStatusCallbackPeriod
()¶Returns: |
|
---|
Returns the period as set by setStatusCallbackPeriod()
.
BrickletGPS.
setAltitudeCallbackPeriod
(long period)¶Parameters: |
|
---|
Sets the period with which the AltitudeCallback
callback is triggered
periodically. A value of 0 turns the callback off.
The AltitudeCallback
callback is only triggered if the altitude changed since
the last triggering.
BrickletGPS.
getAltitudeCallbackPeriod
()¶Returns: |
|
---|
Returns the period as set by setAltitudeCallbackPeriod()
.
BrickletGPS.
setMotionCallbackPeriod
(long period)¶Parameters: |
|
---|
Sets the period with which the MotionCallback
callback is triggered
periodically. A value of 0 turns the callback off.
The MotionCallback
callback is only triggered if the motion changed since the
last triggering.
BrickletGPS.
getMotionCallbackPeriod
()¶Returns: |
|
---|
Returns the period as set by setMotionCallbackPeriod()
.
BrickletGPS.
setDateTimeCallbackPeriod
(long period)¶Parameters: |
|
---|
Sets the period with which the DateTimeCallback
callback is triggered
periodically. A value of 0 turns the callback off.
The DateTimeCallback
callback is only triggered if the date or time changed
since the last triggering.
BrickletGPS.
getDateTimeCallbackPeriod
()¶Returns: |
|
---|
Returns the period as set by setDateTimeCallbackPeriod()
.
Callbacks can be registered to receive time critical or recurring data from the device. The registration is done with "set" function of MATLAB. The parameters consist of the IP Connection object, the callback name and the callback function. For example, it looks like this in MATLAB:
function my_callback(e)
fprintf('Parameter: %s\n', e.param);
end
set(device, 'ExampleCallback', @(h, e) my_callback(e));
Due to a difference in the Octave Java support the "set" function cannot be used in Octave. The registration is done with "add*Callback" functions of the device object. It looks like this in Octave:
function my_callback(e)
fprintf("Parameter: %s\n", e.param);
end
device.addExampleCallback(@my_callback);
It is possible to add several callbacks and to remove them with the corresponding "remove*Callback" function.
The parameters of the callback are passed to the callback function as fields of
the structure e
, which is derived from the java.util.EventObject
class.
The available callback names with corresponding structure fields 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.
BrickletGPS.
CoordinatesCallback
¶Event Object: |
|
---|
This callback is triggered periodically with the period that is set by
setCoordinatesCallbackPeriod()
. The parameters are the same
as for getCoordinates()
.
The CoordinatesCallback
callback is only triggered if the coordinates changed
since the last triggering and if there is currently a fix as indicated by
getStatus()
.
In MATLAB the set()
function can be used to register a callback function
to this callback.
In Octave a callback function can be added to this callback using the
addCoordinatesCallback()
function. An added callback function can be removed with
the removeCoordinatesCallback()
function.
BrickletGPS.
StatusCallback
¶Event Object: |
|
---|
This callback is triggered periodically with the period that is set by
setStatusCallbackPeriod()
. The parameters are the same
as for getStatus()
.
The StatusCallback
callback is only triggered if the status changed since the
last triggering.
The following constants are available for this function:
For fix:
In MATLAB the set()
function can be used to register a callback function
to this callback.
In Octave a callback function can be added to this callback using the
addStatusCallback()
function. An added callback function can be removed with
the removeStatusCallback()
function.
BrickletGPS.
AltitudeCallback
¶Event Object: |
|
---|
This callback is triggered periodically with the period that is set by
setAltitudeCallbackPeriod()
. The parameters are the same
as for getAltitude()
.
The AltitudeCallback
callback is only triggered if the altitude changed since
the last triggering and if there is currently a fix as indicated by
getStatus()
.
In MATLAB the set()
function can be used to register a callback function
to this callback.
In Octave a callback function can be added to this callback using the
addAltitudeCallback()
function. An added callback function can be removed with
the removeAltitudeCallback()
function.
BrickletGPS.
MotionCallback
¶Event Object: |
|
---|
This callback is triggered periodically with the period that is set by
setMotionCallbackPeriod()
. The parameters are the same
as for getMotion()
.
The MotionCallback
callback is only triggered if the motion changed since the
last triggering and if there is currently a fix as indicated by
getStatus()
.
In MATLAB the set()
function can be used to register a callback function
to this callback.
In Octave a callback function can be added to this callback using the
addMotionCallback()
function. An added callback function can be removed with
the removeMotionCallback()
function.
BrickletGPS.
DateTimeCallback
¶Event Object: |
|
---|
This callback is triggered periodically with the period that is set by
setDateTimeCallbackPeriod()
. The parameters are the same
as for getDateTime()
.
The DateTimeCallback
callback is only triggered if the date or time changed
since the last triggering.
In MATLAB the set()
function can be used to register a callback function
to this callback.
In Octave a callback function can be added to this callback using the
addDateTimeCallback()
function. An added callback function can be removed with
the removeDateTimeCallback()
function.
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.
BrickletGPS.
getAPIVersion
()¶Return Object: |
|
---|
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.
BrickletGPS.
getResponseExpected
(byte functionId)¶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
setResponseExpected()
. 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 functionId:
BrickletGPS.
setResponseExpected
(byte functionId, boolean responseExpected)¶Parameters: |
|
---|
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 functionId:
BrickletGPS.
setResponseExpectedAll
(boolean responseExpected)¶Parameters: |
|
---|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
BrickletGPS.
DEVICE_IDENTIFIER
¶This constant is used to identify a GPS Bricklet.
The getIdentity()
function and the
IPConnection.EnumerateCallback
callback of the IP Connection have a deviceIdentifier
parameter to specify
the Brick's or Bricklet's type.
BrickletGPS.
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a GPS Bricklet.