Effects of recent works and activities with CAN buses. I sat down and wrote soft to work with CAN BUS, it is supposed to work as an analyzer, recorder / player, bomber etc.
The assumption to achieve maximum functionality with relatively cheap hardware.
As STM32F103 hardware with any USB-Bridge (it is suitable for non-clogged buses), or STM32F042 with native USB, I wrote the firmware for both of these devices.
PC software written in C # still under development. Support for CAN1000, 500, 250, 125, 100 kbps bus speeds so far. Frames 11 and 29 bit, hardware control from MCU.
Coloring of changing CAN data seen in PassThru Scope. Monitor and tracer seen from the Peak analyzer software (it's a Mercedes in ? analyzers), other ideas and functionalities seen in others, including hobbyists from the east. The photos show prototypes from BluePill and with a purchased module for F042. In the video, a preview of how it works on F042 with native STM USB.
Software frame filtration.
I added the double buffering extension and now it no longer flashes like it does in the video.
To do: hardware filtration on the CAN controller of the processor. Adding goodies to broadcasting custom frames and a bomber.
[movie: c8118cf661] https://filmy.elektroda.pl/78_1637505465.mp4 [/ movie: c8118cf661]
Cool? Ranking DIY
in general, most of the simple things are going to be socket can from linux, it works on probably all possible CAN interfaces. But the strength of every analyzer is the software, I have pcan and vector. I like pcan-exploler to simulate a vector for coarse analysis. It's time to lean more and more over CAN FD and LIN because more and more of it.
and its name is BUSMASTER and I would recommend the author to make a dong for it, at a reasonable price there would be people willing.