-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
door_status not coming through #263
Comments
Thanks for the help finding this bug, Zac. I think it's fixed now. There were two problems:
|
I'll close this bug for now, but let me know when you have time to give it a test (in |
- Fix recursive call to decodeSignal in tire and door decoders. - Add functional tests for testing full decode signal stack. See #263.
Cool, thanks for catching the pipeline issue! In the updated door examples, it looks like the values would be sent every time there's a CAN message. Here's my suggestion:
|
Thanks, just added that too. |
Looks like
shared_handlers
has changed with v6.X of vi-firmware and our previous implementation ofdoor_status
signals is no longer working.I've modified the
doorStatusDecoder(...)
such that it is now returns anopenxc_DynamicField
. I will create an issue branch fromnext
and get this working. Below are the changes I made toshared_handlers
.Right now, I'm getting an issue where the call to
publishVehicleMessage(...)
is causing the VI to hang and stall.The
door_status
signals are mapped in the following format:The idea is that the
door_status
event-based signals are only sent when something changes (i.e. when a door opens or closes.)Any thoughts why
publishVehicleMessage
crashes? Commenting out that line fixes the crash, but then I don't get any JSON output, of course.The text was updated successfully, but these errors were encountered: