Functional Description
The usb2can hardware device is implemented through the can-utils terminal tool.
In practice, we use a unified interface like can0 more often to develop programs without using the descriptor /dev/ttyCH341USBx:
1.0 Convenient for customers to quickly receive and send tests.
2.0 Unified interface for secondary development.
3.0 EMUC is also configured like this: https://www.innodisk.com/en/products/embedded-peripheral/communication-canbus/emuc-b202-1
This zip is an example of the EMUC driver, which can finally be configured via the start.sh script for the can0 interface [below].
[EMUC_B202_SocketCAN_driver_v3.7_utility_v3.2_20230315_Ubuntu22.04-1.zip]
(https://github.com/WCHSoftGroup/ch341ser_linux/files/13631363/EMUC_B202_SocketCAN_driver_v3.7_utility_v3.2_20230315_Ubuntu22.04-1.zip)

sudo apt install can-utils -y
# Reading information on the can bus
candump can0
# Sending information to the can bus
cansend 123#DEADBEE
Functional Description
The
usb2canhardware device is implemented through thecan-utilsterminal tool.In practice, we use a unified interface like can0 more often to develop programs without using the descriptor /dev/ttyCH341USBx:
1.0 Convenient for customers to quickly receive and send tests.
2.0 Unified interface for secondary development.
3.0 EMUC is also configured like this: https://www.innodisk.com/en/products/embedded-peripheral/communication-canbus/emuc-b202-1
This zip is an example of the EMUC driver, which can finally be configured via the
start.shscript for the can0 interface [below].[EMUC_B202_SocketCAN_driver_v3.7_utility_v3.2_20230315_Ubuntu22.04-1.zip]
(https://github.com/WCHSoftGroup/ch341ser_linux/files/13631363/EMUC_B202_SocketCAN_driver_v3.7_utility_v3.2_20230315_Ubuntu22.04-1.zip)