Is there a mechanism to receive all the messages that the underlying CAN Driver sees through UAVCAN, somewhat like a raw tap on the underlying CAN interface? Everything seems to be geared towards having a known structure to UAVCAN and not at being able to receive unknown structures. Would I have to insert some tap under the drivers with interfaces to UAVCAN?
--
You received this message because you are subscribed to the Google Groups "UAVCAN" group.
To unsubscribe from this group and stop receiving emails from it, send an email to uavcan+unsubscribe@googlegroups.com.
To post to this group, send email to uav...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/uavcan/a22bdb81-74b9-47cc-95ca-a8c713bd95f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
There's a good reason for that. You can't receive an unknown structure, by design, because the answer is right there: the structure is unknown. You can receive only known structures, so the solution for that is to instantiate a subscriber for every type you know.However, if you just want raw CAN frames, all of our open source libraries allow you to receive raw traffic from the bus directly in your application:
On Thu, Apr 5, 2018 at 1:22 AM, Erik Rainey <erik....@gmail.com> wrote:
Is there a mechanism to receive all the messages that the underlying CAN Driver sees through UAVCAN, somewhat like a raw tap on the underlying CAN interface? Everything seems to be geared towards having a known structure to UAVCAN and not at being able to receive unknown structures. Would I have to insert some tap under the drivers with interfaces to UAVCAN?
--
You received this message because you are subscribed to the Google Groups "UAVCAN" group.
To unsubscribe from this group and stop receiving emails from it, send an email to uavcan+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/uavcan/efb8eaa4-bd2b-4a02-9fe6-61a25a689e22%40googlegroups.com.