Get decoding diagnostic request from decoding thread of can_bus_t
authorRomain Forlot <romain.forlot@iot.bzh>
Mon, 13 Mar 2017 13:58:22 +0000 (14:58 +0100)
committerRomain Forlot <romain.forlot@iot.bzh>
Thu, 16 Mar 2017 16:15:55 +0000 (17:15 +0100)
commitf0d7a6523955ee94a32ec4b62e2a207b23f62316
tree1856801bfd7f2718689888ccc488643dc99e436a
parentb606db2b74d5c92d33a126071062c9eb2a548beb
Get decoding diagnostic request from decoding thread of can_bus_t

Decoding divided in 2 subfunctions dedicated to decode either
pure CAN messages or diagnostic (obd2) message. About now,
a diagnostic request has a name then it will be pushed
on the event_queue as a SimpleMessage. Without name full
details of diagnostic response will be pushed as diagnostic
response. This behavior follows the one from OpenXC.

Change-Id: I255f3f6487fa9511ea47c74606014995a7b0f720
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
src/can/can-bus-dev.cpp
src/can/can-bus-dev.hpp
src/can/can-bus.cpp
src/can/can-bus.hpp
src/diagnostic/diagnostic-manager.cpp
src/diagnostic/diagnostic-manager.hpp
src/utils/openxc-utils.cpp
src/utils/openxc-utils.hpp