Thank Brent, However I was more curious about the bring up of the hardware on the BBB. IS there cape file I have not noticed yet ? If so I can probably figure it out on my own.
On Thu, Sep 11, 2014 at 4:52 PM, Brent <[email protected]> wrote: > Well, I'm not reading a guide, but I'll share a few links that helped me > get started. I have a Qt application and I use the SocketCAN to read/write > CAN messages. This will work with J1939 as well. > > https://www.kernel.org/doc/Documentation/networking/can.txt > http://en.wikipedia.org/wiki/SocketCAN > http://www.can-cia.org/fileadmin/cia/files/icc/13/kleine-budde.pdf > > On Thursday, September 11, 2014 7:44:50 PM UTC-4, William Hermans wrote: >> >> Brent, what guide are you reading for CAN ? I've never used CAN >> personally, and am curious . . . >> >> On Thu, Sep 11, 2014 at 2:25 PM, Brent Sink <[email protected]> wrote: >> >>> Adding restart-ms did the trick! Thanks so much, I never knew that was >>> even there. >>> >>> On Wed, Sep 10, 2014 at 8:37 PM, Devan Lai <[email protected]> wrote: >>> >>>> You can configure the controller to automatically recover from bus-off >>>> conditions by setting the "restart-ms" option. >>>> >>>> The python-can documentation has some useful notes on socket-can and >>>> bus-off conditions: >>>> >>>> http://python-can.readthedocs.org/en/latest/socketcan.html#can-errors >>>> >>>> >>>> On Wednesday, September 10, 2014 9:39:21 AM UTC-7, Brent wrote: >>>>> >>>>> I have noticed that if I short CAN_H and CAN_L together, or if there >>>>> is noise on the bus, the BeagleBone will stop sending and receiving CAN >>>>> messages. When this happens, if I execute "ifconfig can0 down" and >>>>> "ifconfig can0 up", things start working again. Is there a way to detect >>>>> this automatically and recover? I'm using SocketCAN, but haven't found >>>>> anything that would tell me when I get a bus off or bus heavy. >>>>> >>>> -- >>>> For more options, visit http://beagleboard.org/discuss >>>> --- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "BeagleBoard" group. >>>> To unsubscribe from this topic, visit https://groups.google.com/d/ >>>> topic/beagleboard/SdvoxYkgagc/unsubscribe. >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> >>> -- >>> -brent >>> >>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "BeagleBoard" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
