Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
locapack
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
RMESS
bossche-public
locapack
Commits
5f794207
Commit
5f794207
authored
4 years ago
by
Adrien van den Bossche
Browse files
Options
Downloads
Patches
Plain Diff
Update README.md
parent
8faeb2b2
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+14
-8
14 additions, 8 deletions
README.md
with
14 additions
and
8 deletions
README.md
+
14
−
8
View file @
5f794207
...
...
@@ -30,8 +30,14 @@ A Json description of the messages is also available.
Implementation status:
-
Arduino: encode/decode header, encode/decode universal GNSS packets ; example sketch with GPS receiver.
-
Node-RED: decode header, decode universal GNSS packets
-
Arduino
-
encode/decode header,
-
encode/decode universal GNSS packets (type 1) with example/test sketch,
-
encode/decode locally referenced packets (type 2) with example/test sketch,
-
example sketch with GPS receiver.
-
Node-RED
-
decode header,
-
decode universal GNSS packets
### Arduino
...
...
@@ -127,9 +133,9 @@ The `device_id_size` indicates the number of Bytes of the `device_id` field. A l
The
`packet_type`
indicates the structure of the payload. These types of packet have been described:
*
`type
0
`
: Universal GNSS localisation
*
`type
1
`
: Locally referenced localisation
*
`type
2
`
: Inter-node proximity
*
`type
1
`
: Universal GNSS localisation
*
`type
2
`
: Locally referenced localisation
*
`type
3
`
: Inter-node proximity
The
`movement_id_presence_flag`
must be set to 1 if the
`movement_id`
field is present in the packet.
...
...
@@ -137,7 +143,7 @@ The `timestamp_presence_flag` must be set to 1 if the `timestamp` field is prese
### Payload structure by packet type
#### Type
0
: Universal GNSS localisation
#### Type
1
: Universal GNSS localisation
Transport of GNSS coordinates. Altitude and DOP are optionnal.
...
...
@@ -165,7 +171,7 @@ The `altitude_presence_flag` must be set to 1 if the `altitude` field is present
The
`dop_presence_flag`
must be set to 1 if the
`dop`
field is present in the packet.
#### Type
1
: Locally referenced localisation
#### Type
2
: Locally referenced localisation
Transport of locally referenced 2D or 3D localisation. The "repère" is identified by an UID.
...
...
@@ -197,7 +203,7 @@ The `dop_presence_flag` must be set to 1 if the `dop` field is present in the pa
The
`frameofref_id_presence_flag`
must be set to 1 if the
`frameofref_id`
field is present in the packet.
#### Type
2
: Inter-node proximity
#### Type
3
: Inter-node proximity
Transport of raw distances (rangings) between pairs of nodes. The ranging technology can be specified.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment