This forum covers PCAN-Linux and Linux development issues concerning our products
-
DeeFive
- Posts: 4
- Joined: Mon 27. May 2024, 10:12
Post
by DeeFive » Mon 3. Jun 2024, 11:10
Hello,
after an update to kernel 6.5.0-35 I realized that it does not seem to be possible to use SocketCAN's
one-shot interface option anymore. Trying to configure the interface that way yields:
Code: Select all
root@mdahst3:~ # ip link set can0 type can bitrate 250000 one-shot on
RTNETLINK answers: Operation not supported
root@mdahst3:~ # uname -a
Linux mdahst3 6.5.0-35-generic #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May 7 09:00:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
root@mdahst3:~ #
Has one-shot support been dropped? Would be a pity, as I am using it regularly for simulation purposes.
Best regards,
Michael
-
M.Maidhof
- Support

- Posts: 1701
- Joined: Wed 22. Sep 2010, 14:00
Post
by M.Maidhof » Mon 3. Jun 2024, 11:40
Hi,
which PCAN hardware do you use? Which firmware is used on that PCAN hardware?
regards
Michael
-
DeeFive
- Posts: 4
- Joined: Mon 27. May 2024, 10:12
Post
by DeeFive » Mon 3. Jun 2024, 11:58
Hi Michael,
thanks for looking into this. It is a PEAK-USB dongle, I am using plenty of them. I am not exactly sure about the firmware version, but `lsusb` shows:
Code: Select all
root@mdahst3:~ # lsusb -v -s 001:008
Bus 001 Device 008: ID 0c72:000c PEAK System PCAN-USB
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 16
idVendor 0x0c72 PEAK System
idProduct 0x000c PCAN-USB
bcdDevice 1c.00
iManufacturer 0
iProduct 3 VER1:PEAK
VER2:02.8.01
DAT :06.05.2004
TIME:09:35:37
...
...
Best regards,
Michael
-
M.Maidhof
- Support

- Posts: 1701
- Joined: Wed 22. Sep 2010, 14:00
Post
by M.Maidhof » Mon 3. Jun 2024, 12:11
Hi,
this is an older PCAN-USB with an older firmware from 2004, which don't support one-shot. Please update to latest firmware version 5.x using PEAK-Flash for Windows to fix your issue, or use a PCAN-USB with a higher firmware version when you have several available.
regards
Michael
-
DeeFive
- Posts: 4
- Joined: Mon 27. May 2024, 10:12
Post
by DeeFive » Mon 3. Jun 2024, 12:13
Hi Michael,
just solved it. Wondering about the seemingly pre-historic date code from lsusb output, I realized that the dongle was not the one that I was normally using. It had a red strain relief instead of a grey one. I now tried a different one which identified its F/W version as 8.3.0 in dmesg output. I can confirm that everything works as expected with this one now, one-shot option included. Obviously, an adapter from a different batch somehow made it to our lab.
Many thanks,
Michael
-
DeeFive
- Posts: 4
- Joined: Mon 27. May 2024, 10:12
Post
by DeeFive » Mon 3. Jun 2024, 12:14
Ah, so it can be updated? Great - will give it a try! Many thanks!