How to configure the Mini-VCI J2534 cable on 64bit Linux as a capture device? #802
Replies: 1 comment
-
Closing as converted into #806 for which an explanation was provided. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've got ElementaryOS 7.1 (which is like Ubuntu 22.04LTS). I have a Toyota where one of the CAN networks is available on pins 6 and 14, as is typical. And I have a cheap J2534 OBD2 "Mini-VCI" cable.
TLDR, I am unable to read CAN packets using SavvyCAN on Linux. And, I'm unsure whether:
When plugging my USB device into the computer, I have the following output from
journalctl -f
:Jun 22 18:27:07 dougux kernel: usb 4-4: new full-speed USB device number 118 using ohci-pci
Jun 22 18:27:07 dougux kernel: usb 4-4: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
Jun 22 18:27:07 dougux kernel: usb 4-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jun 22 18:27:07 dougux kernel: usb 4-4: Product: M-VCI
Jun 22 18:27:07 dougux kernel: usb 4-4: Manufacturer: HX
Jun 22 18:27:07 dougux kernel: usb 4-4: SerialNumber: A695SEMP
Jun 22 18:27:07 dougux kernel: ftdi_sio 4-4:1.0: FTDI USB Serial Device converter detected
Jun 22 18:27:07 dougux kernel: usb 4-4: Detected FT232R
Jun 22 18:27:07 dougux kernel: usb 4-4: FTDI USB Serial Device converter now attached to ttyUSB0
Jun 22 18:27:07 dougux mtp-probe[21900]: checking bus 4, device 118: "/sys/devices/pci0000:00/0000:00:06.0/usb4/4-4"
Jun 22 18:27:07 dougux mtp-probe[21900]: bus: 4, device: 118 was not an MTP device
Jun 22 18:27:07 dougux mtp-probe[21910]: checking bus 4, device 118: "/sys/devices/pci0000:00/0000:00:06.0/usb4/4-4"
Jun 22 18:27:07 dougux mtp-probe[21910]: bus: 4, device: 118 was not an MTP device
Jun 22 18:27:08 dougux io.elementary.s[11770]: g_bytes_compare: assertion 'bytes1 != NULL' failed
Jun 22 18:27:10 dougux ModemManager[400]: [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:06.0/usb4/4-4': not supported by any plugin
Now I'm having a variety of problems getting SavvyCAN to run and detect the CAN interface.
I saw the related #327 , and I gather from that discussion that QtSerial may be the correct way to pull CAN frames off of my passthrough cable.
I am just poking around and I'm uncertain what the requirements really are. Do I need to have a
/dev/can0
device up for this to work?Perhaps someone who has successfully built and installed this can narrow down my paths of indirection a little bit?
Beta Was this translation helpful? Give feedback.
All reactions