Publisher Up Time issue

[CyberMerln]

Do not know if this a driver or flexcan issue so I am posing the question here.

In testing a Flexcan library and a new version of the FlexCan library we noticed that after about 1 hour or so the valid messages stop being received the by the subscriber.  With the new version if we reboot the publisher or subscriber it starts right up again receiving valid messages.  With the old version have to reboot the publisher.  We are using the GNSS message with dummy data as the test message.  Message goes out every 100ms?

The question is what has anyone tested Node uptimes or is there a test limit that we need to pass for the new library. Any suggestions would be helpful.

Respectfully

Mike

[Pavel Kirienko]

Sounds like a driver issue. Please collect a CAN dump and post it here for evaluation.

Pavel.

--
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 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/ceed091c-4fb0-454e-9080-2cd7d9ccbc81%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[CyberMerln]

What kind of CAN dump do you need?

[Pavel Kirienko]

Record what happens on the bus when this condition is reached:

> In testing a Flexcan library and a new version of the FlexCan library we noticed that after about 1 hour or so the valid messages stop being received the by the subscriber.

Pavel.

To view this discussion on the web visit https://groups.google.com/d/msgid/uavcan/f9f7457d-cb53-4b6e-a997-7d36446818e6%40googlegroups.com.

[CyberMerln]

Got it.  Reason why I ask is I can dump a lot of data and don't want to overload you with data :)

[CyberMerln]

Still working it - too much data overloading my usb port.  But that neither here or there. And still trying to isolate the problem at the same time.  Think there may be an issue with the current clock driver that was being implemented with the library I am using for UAVcan.  I think this may be causing problems.  Want to replace it with the one that you posted on GITHUB for the libuavcan-kinetis (uses the pit timers) but having some challenges implementing it.  I will post my questions on that on the GitHub issue tracker. Unless you want me to do that here.

Thanks

Mike

[Pavel Kirienko]

Sure, feel free to post your questions on Github. Note that the FlexCAN driver was contributed by David Sidrane, I did not write any of it.

Pavel.

To view this discussion on the web visit https://groups.google.com/d/msgid/uavcan/73ff9cf5-3649-48d1-b0e6-179d417c3128%40googlegroups.com.

[CyberMerln]

Thanks.  Mostly a question of implementation of the clock.  I realize that David S. wrote the driver and went to his GitHub page but he doesn't have a copy driver on his page.  So can't post over there.  The questions are real simple. :)