By the way "1F334455#1122334455667788" doesn't look like a valid J1939 packet. But I barely know that particular protocol.
On Wed, May 20, 2020 at 4:15 PM William Hermans <yyrk...@gmail.com> wrote: > Without any code, or steps you've taken. No one can help, or say what's > going on. I will say this however. I wrote in a relatively short period of > time( with help! From multiple sources). Software that could communicate > over CANBUS that was able to decode information from a "TRACE" > inverter(XanBus) in real-time. This ran for weeks at a time, displaying the > information in a web interface. Proven 100% accurate. > > I would not say that using the CANBUS hardware interface on the beaglebone > is 100% rock solid, but it had been very reliable in my case. Once I knew > what I was doing. The only real problem we had was we were completely > off-grid, powered by solar. So when we switched from solar power, to the > genset. The quick power blip would sometimes put the beaglebone in a wonkey > state. However, creating, and using canbus traffic logs. I was able to keep > a working beaglebone powered via a laptop for months. > > Probably the first place to look is at the hardware you're using. But I'd > double check everything. > > On Wed, May 20, 2020 at 1:29 PM Andrey <klim....@gmail.com> wrote: > >> Guys, thanks for the answers! >> Unfortunately, I can't use can1, it is have no output on my Board. >> It is strange that after a bus crash, ifconfig shows the number of >> packets transmit 0 and received 3. >> If the tire falls after only three attempts to send, it is not normal and >> does not look like a system for cars that is designed to be reliable. >> >> debian@bone:~$ cansend can0 *1F334455#1122334455667788* >> [ 273.654439] can: raw protocol (rev 20170425) >> [ 273.670296] c_can_platform 481cc000.can can0: bus-off >> debian@bone:~$ sudo ifconfig >> can0: flags=129<UP,NOARP> mtu 16 >> unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 >> txqueuelen 10 (UNSPEC) >> RX packets *3* bytes 24 (24.0 B) >> RX errors 0 dropped 0 overruns 0 frame 0 >> TX packets 0 bytes 0 (0.0 B) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> device interrupt 47 >> ... >> >> This is more complicated than I thought. >> >> -- >> 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 beagleboard+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/1a0b4dcf-2f7e-46a1-8083-43336085c415%40googlegroups.com >> <https://groups.google.com/d/msgid/beagleboard/1a0b4dcf-2f7e-46a1-8083-43336085c415%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORrHPStJu8F7LwF-%2BjPqwBP4WMXdJGqYKGTAqAiKG_QbQQ%40mail.gmail.com.
