Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen der Seite angezeigt.

--- public:supercan_raspi:supercan_raspi_anleitung [2021/01/31 12:41] – [Installation] geier99
+++ public:supercan_raspi:supercan_raspi_anleitung [2023/08/06 18:27] (aktuell) – [Installation] geier99
@@ Zeile 5: / Zeile 5: @@
 ===== Installation =====
-  - Erst mal alle Schritte von [[https://github.com/jgressmann/supercan/blob/master/Linux/README.md|SuperCAN - Linux - Readme]] durchführen.
+  - Erst mal alle Schritte von [[https://github.com/jgressmann/supercan-linux/blob/main/README.md|SuperCAN - Linux - Readme]] durchführen.
   - Interface nun an den USB-Port anschließen und mal kontrollieren, ob es erkannt wurde und die USB Kommunikation in Ordnung ist:<code>pi@raspberrypi:~ $ lsusb -t
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
@@ Zeile 12: / Zeile 12: @@
         |__ Port 3: Dev 4, If 1, Class=Vendor Specific Class, Driver=supercan_usb, 12M
         |__ Port 3: Dev 4, If 2, Class=Application Specific Interface, Driver=, 12M
-</code> sollte nun die 2 CAN-FD Kanäle anzeigen. \\ bzw. sollte in dem Kernellog nun folgnedes auftauchen<code>[    4.032336] supercan_usb 1-1.3:1.0: device proto version 1, little endian, cmd buffer of 64 bytes
+</code> sollte nun die 2 CAN-FD Kanäle anzeigen. \\ bzw. sollte in dem Kernel log nun folgendes auftauchen<code>[ 1299.592718] usb 1-1.3: new full-speed USB device number 7 using dwc_otg
-[    4.040256] supercan_usb 1-1.3:1.0: device features perm=0010 conf=0743
+[ 1299.749691] usb 1-1.3: New USB device found, idVendor=1d50, idProduct=5035, bcdDevice= 3.00
-[    4.040285] supercan_usb 1-1.3:1.0: device D5035-01 SuperCAN ch0, serial 487a4a8a5339393338202020ff131426, firmware version 0.3.9
+[ 1299.749708] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
-[    4.053381] cdc_acm 1-1.1.2:1.0: ttyACM0: USB ACM device
+[ 1299.749718] usb 1-1.3: Product: D5035-01 SuperCAN
-[    4.055389] supercan_usb 1-1.3:1.0: device has CAN msg buffer of 512 bytes
+[ 1299.749727] usb 1-1.3: Manufacturer: 2guys
-[    4.055406] supercan_usb 1-1.3:1.0: device supports CAN-FD
+[ 1299.749737] usb 1-1.3: SerialNumber: 487a4a8a5339393338202020ff131426
-[    4.055415] supercan_usb 1-1.3:1.0: device supports monitoring mode
+[ 1299.757322] supercan_usb 1-1.3:1.0: device proto version 1, little endian, cmd buffer of 64 bytes
-[    4.055424] supercan_usb 1-1.3:1.0: device supports external loopback mode
+[ 1299.758928] supercan_usb 1-1.3:1.0: device features perm=0010 conf=0743
-[    4.055699] cdc_acm 1-1.1.2:1.2: ttyACM1: USB ACM device
+[ 1299.758952] supercan_usb 1-1.3:1.0: device D5035-01 SuperCAN ch0, serial 487a4a8a5339393338202020ff131426, firmware version 0.3.14
-[    4.056759] usbcore: registered new interface driver cdc_acm
+[ 1299.759298] supercan_usb 1-1.3:1.0: device has CAN msg buffer of 512 bytes
-[    4.056770] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
+[ 1299.759308] supercan_usb 1-1.3:1.0: device supports CAN-FD
-[    4.090041] supercan_usb 1-1.3:1.1: device proto version 1, little endian, cmd buffer of 64 bytes
+[ 1299.759317] supercan_usb 1-1.3:1.0: device supports monitoring mode
-[    4.091554] supercan_usb 1-1.3:1.1: device features perm=0010 conf=0743
+[ 1299.759326] supercan_usb 1-1.3:1.0: device supports external loopback mode
-[    4.091580] supercan_usb 1-1.3:1.1: device D5035-01 SuperCAN ch1, serial 487a4a8a5339393338202020ff131426, firmware version 0.3.9
+[ 1299.764817] supercan_usb 1-1.3:1.1: device proto version 1, little endian, cmd buffer of 64 bytes
-[    4.093164] supercan_usb 1-1.3:1.1: device has CAN msg buffer of 512 bytes
+[ 1299.766302] supercan_usb 1-1.3:1.1: device features perm=0010 conf=0743
-[    4.093180] supercan_usb 1-1.3:1.1: device supports CAN-FD
+[ 1299.766326] supercan_usb 1-1.3:1.1: device D5035-01 SuperCAN ch1, serial 487a4a8a5339393338202020ff131426, firmware version 0.3.14
-[    4.093189] supercan_usb 1-1.3:1.1: device supports monitoring mode
+[ 1299.767799] supercan_usb 1-1.3:1.1: device has CAN msg buffer of 512 bytes
-[    4.093198] supercan_usb 1-1.3:1.1: device supports external loopback mode
+[ 1299.767810] supercan_usb 1-1.3:1.1: device supports CAN-FD
-[    4.103866] usbcore: registered new interface driver supercan_usb
+[ 1299.767819] supercan_usb 1-1.3:1.1: device supports monitoring mode
-</code> Wenn das alles in Ornung ist, kann nun der Socket CAN-Treiber verwendet werden.
+[ 1299.767828] supercan_usb 1-1.3:1.1: device supports external loopback mode
+</code> Wenn das alles in Ordnung ist, kann nun der Socket CAN-Treiber verwendet werden.
   - SocketCAN Device einrichten (Hinweis: da in meinem Raspi das PiCAN-Duo Modul verbaut ist, wird hier in den Beispielen can2/can3 genommen):
     * Baudrate einstellen:<code>sudo ip link set can2 type can  bitrate 500000</code>
@@ Zeile 43: / Zeile 45: @@
           SuperCAN: tseg1 2..256 tseg2 2..128 sjw 1..128 brp 1..512 brp-inc 1
           SuperCAN: dtseg1 1..32 dtseg2 1..16 dsjw 1..16 dbrp 1..32 dbrp-inc 1
-          clock 80000000numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535</code>Jetzt könne die Standard Tools von den CAN-Utils verwendet werden, wie z.B. <code>candump can2
+          clock 80000000numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535</code>Jetzt könne die Standard-Tools von den CAN-Utils verwendet werden, wie z.B. <code>candump can2
 oder
-cansniffer -c t 0 can2</code>
+cansniffer -c -t 0 can2</code> ([[public:can-utils_tipps|Tipps zu den can-utils]])
      * Das Schließen des CAN Kanals geschieht mit <code>sudo ip link set down can2</code>