waveshareUSB to CAN Adapter Model A, STM32 Chip Solution, Multiple Working Modes, Multi-System Compatible

No direct C# code example or serial port library / DLL was provided with the product.The adapter uses the CH340 USB to Virtual serial port low level driver.A serial driver / api has to be written / purchased / integrated to use the product with your C# application.After requesting an example from Waveshare, I received a mixed English / Chinese set of code that was far too bloated, when all I needed was a simple C# App and serial API DLL.I had limited success writing a pure C# driver for this adapter that was efficient and reliable over the standard SerialPort Class. A lower level Win32 driver is needed to handle high speed serial port processing reliably and efficiently, which a USB to CAN interface will require, especially for 250k and above CAN rates. The device supports 2M baud for the serial side as a default, which supports what I have stated.I was not able to get consistent or reliable received data and the adapter required significant delay between transmitted packets for them to be sent successfully (no packet sent or corrupted data). This was confirmed by Waveshare.Perhaps, if someone has had success with this product, they will provide details on how that was achieved.Update 4/6/2024I applied a Win32 Serial Port API with very thin Data Received Event code (just loads serial data into a buffer and exits) and was able to generate more consistent results for received data, but found that I had to drop down to 1228800 baud to keep bytes from being dropped by the serial interface. I just ran a few tests receiving 2.5M bytes of data without missing bytes, so perhaps that was part of the issue.I've not gone back to test transmitted data again but based on Waveshare's support feedback, I don't expect this is going to improve much.

This isn’t great. Buy yourself something that supports socketcan instead.

This thing is totally useless as long as it works only with it's own application. Anyway, even with application, it still doesn't work. I monitored with a Komodo analyzer and get only errors. Follow the instructions, it doesn't do anything.

If you are interested in this device, reading the below technical summary should not be a problem for you.You can do basic logging and injection of CAN 2.0 A and B frames with this device.It uses CH340 as USB-to-Serial bridge. It works, and it is the same bridge as used by most cloned Arduinos, but it is know n to have reliability issues that will likely manifest themself at high baud rates or high data volumes. I wish they used CP2102 or FTDI bridge instead.The manufacturer claims they use STM32 microcontroller as main CPU. This is a new version of the device that encloses the board into a non-removable (and quite nice looking) case, so I cannot validate that. The case is definitely an improvement over the old version.According to car hacker enthusiasts, you must use vendor-supplied USB-CAN application that is not very convenient or write your own software to handle CAN frames.

I like how it designed, but it doesn't work. Do not waste your time and money.

I have not been able to use the software of this to it's full usefulness yet, but the hardware of this stick looks really nice. It uses easy to operate screw terminals on the outside and just plugs straight into your computer with USB on the other. The status indicator LEDs are helpful for debugging, I appreciate the labeling of the outputs on the printing, and the on/off switch is also a nice addition.

Was not able to get this to install with Windows and Linux to capture CAN Bus traffic.

When I bought this device I always intended to make my own driver code. I only used the software once before writing my own because I wanted more programmatic control. The hardware its self is very solid. The driver code I made is a little weird because of how it sets up the device. I will buy these again, just ditch the software.