This is the description of the Modbus protocol for the GPS Bricklet 2.0. General information and technical specifications for the GPS Bricklet 2.0 are summarized in its hardware description.
A general description of the Modbus protocol structure can be found here.
BrickletGPSV2.
get_coordinates
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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_low_level
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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 meanings are defined for the elements of this function:
For satellite_system:
For fix:
BrickletGPSV2.
get_satellite_status
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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 meanings are defined for the elements of this function:
For satellite_system:
BrickletGPSV2.
restart
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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 meanings are defined for the elements of this function:
For restart_type:
BrickletGPSV2.
set_fix_led_config
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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 meanings are defined for the elements of this function:
For config:
BrickletGPSV2.
get_fix_led_config
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the configuration as set by set_fix_led_config
The following meanings are defined for the elements of this function:
For config:
BrickletGPSV2.
set_sbas_config
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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.
New in version 2.0.2 (Plugin).
The following meanings are defined for the elements of this function:
For sbas_config:
BrickletGPSV2.
get_sbas_config
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the SBAS configuration as set by set_sbas_config
New in version 2.0.2 (Plugin).
The following meanings are defined for the elements of this function:
For sbas_config:
BrickletGPSV2.
get_spitfp_error_count
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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 meanings are defined for the elements of this function:
For config:
BrickletGPSV2.
get_status_led_config
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the configuration as set by set_status_led_config
The following meanings are defined for the elements of this function:
For config:
BrickletGPSV2.
get_chip_temperature
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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.
BrickletGPSV2.
set_coordinates_callback_period
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the period as set by set_coordinates_callback_period
.
BrickletGPSV2.
set_status_callback_period
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the period as set by set_status_callback_period
.
BrickletGPSV2.
set_altitude_callback_period
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the period as set by set_altitude_callback_period
.
BrickletGPSV2.
set_motion_callback_period
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the period as set by set_motion_callback_period
.
BrickletGPSV2.
set_date_time_callback_period
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the period as set by set_date_time_callback_period
.
BrickletGPSV2.
CALLBACK_PULSE_PER_SECOND
¶Function ID: |
|
---|---|
Response: |
|
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
¶Function ID: |
|
---|---|
Response: |
|
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
¶Function ID: |
|
---|---|
Response: |
|
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
¶Function ID: |
|
---|---|
Response: |
|
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
¶Function ID: |
|
---|---|
Response: |
|
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
¶Function ID: |
|
---|---|
Response: |
|
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.
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
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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 meanings are defined for the elements of this function:
For mode:
For status:
BrickletGPSV2.
get_bootloader_mode
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the current bootloader mode, see set_bootloader_mode
.
The following meanings are defined for the elements of this function:
For mode:
BrickletGPSV2.
set_write_firmware_pointer
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.