python/its-vehicle: new client #114
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ymorin-orange
force-pushed
the
yem/its-vehicle
branch
2 times, most recently
from
c07acba
to
d5772ab
Compare
ymorin-orange
force-pushed
the
yem/its-vehicle
branch
from
d5772ab
to
9a61bce
Compare
|
@Hugues360 I accidentally left a little debug message, so I removed it and repushed; sorry or the mess... |
tigroo
added
enhancement
Hugues360
reviewed
May 3, 2024
Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
... and crudely instanciate it from main() while waiting for a better loop management... All fields in a GNSS report are optional but the timestamp the report was generated at (although a report with only the timestamp would be very useless), as gspd explicitly states that all fields are optional. Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
Not all GNSS devices trigger gpsd to emit GST or ATT messages, but when they do, there are interesting data in there that we want to make available for enhanced reporting (esp. the acceleration, the error ellipse...). Even when those messages are emitted, there is still no guarantee that any of the fields be present at all, as gpsd explicitly documents that all fields are optional, so be prepared for that. Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
... which is responsible for:
- gathering GNSS reports,
- assembling proper ITS messages (depending on what kind of client it
is),
- sending those messages to the MQTT broker(s),
- subscribing to the area of interest based on the current location,
- mirroring those messages to the local borker (if any),
- logging and tracking timestamps for MQTT messages that are sent and
received.
(most of that to come in followup commits).
Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
We currently only properly cleanup upon receiving a Ctrl-C (SIGINT), but process managers, like systemd et al., usually send SIGTERM to tell a process to terminate properly. Catch that signal, in addition to SIGINT, so that we have a chance to cleanup and drop all our connections cleanly. Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
…pth) Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
ymorin-orange
force-pushed
the
yem/its-vehicle
branch
from
9a61bce
to
f773dd6
Compare
Hugues360
approved these changes
May 3, 2024
Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
... unless we're mirroring self from the main broker. Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
... except our own, unless instructed so. Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
The tracker is responsible for tracking events, like when a message is sent, received, etc... For now, does nothing except hand out an ID. Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
Upon creation of a message, associate an ID to that message (for now, we do nothing with that ID, as the schemas do not define one). Track the emission and reception of messages. For now, we do nothing to actually track, but the infra is there. Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
ymorin-orange
force-pushed
the
yem/its-vehicle
branch
from
f773dd6
to
b2705ae
Compare
|
Ok, test passed with succes with a relevant gps log (with old version and new version to check that the its-client no longer fails) |
Hugues360
approved these changes
May 15, 2024
|
@tigroo I've (re)added you as a reviewer so that you can approve the PR if you |
tigroo
approved these changes
May 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes:
How to test:
$ pip3 install python/its-{quadkeys,vehicle}/home/login/.local/bin).its-vehicle.cfg(set the properproject and suffix):
gpsd.persistence$ mosquitto_pub -h HOST -p PORT -u USER -P PASS \ -t 'PROJECT/outQueue/SUFFIX/x/x/x/x/x' \ -m '{"source_uuid": "something", "where": "here and there"}'TERMsignalExpected results:
inQueue;generation_delta_time:{ "type": "cam", "origin": "self", "version": "1.1.3", "source_uuid": "test-me", "timestamp": 1713258140393, "message": { "protocol_version": 1, "station_id": 7603010, "generation_delta_time": 56031, "basic_container": { "station_type": 5, "reference_position": { "latitude": 436259333, "longitude": 14851333, "altitude": 0 }, "confidence": { "position_confidence_ellipse": { "semi_major_confidence": 10, "semi_minor_confidence": 50, "semi_major_orientation": 1 }, "altitude": 1 } }, "high_frequency_container": { "heading": 2289, "speed": 998, "longitudinal_acceleration": 161, "drive_direction": 0, "vehicle_length": 40, "vehicle_width": 20, "confidence": { "heading": 2, "speed": 3, "vehicle_length": 0 } } } }gpsd.persistenceduration, and are no longer emitted afterwards;inQueue,outQueue, andinterQueue); the MQTT client to the local broker is reporting CAM messages at 0.5Hz, onoutQueue;