Hi,
I came across this older thread (https://forum.peak-system.com/viewtopic.php?t=3445&sid=366236ac1650d496d7bbf8eb8f9c7c6d) about RX/TX error counters and the mainline peak_usb driver, and have a related question on a PCAN-USB FD X6, kernel 6.12.47 using the newest proprietary driver Version 9.2 ...
Search found 12 matches
- Thu 6. Aug 2026, 17:34
- Forum: PCAN-USB X6
- Topic: TX/RX error counter (data[6]/data[7]) not incrementing and CAN_ERR_CNT never set
- Replies: 1
- Views: 974
- Thu 6. Aug 2026, 09:25
- Forum: PCAN-USB X6
- Topic: No way to detect self-received (echoed) frames under hardware loopback
- Replies: 6
- Views: 924
Re: No way to detect self-received (echoed) frames under hardware loopback
Hi,
thank you very much for the detailed description, that information definitely helped. Regarding the out-of-tree driver, I replied on the original post.
Best regards
Lukas
thank you very much for the detailed description, that information definitely helped. Regarding the out-of-tree driver, I replied on the original post.
Best regards
Lukas
- Thu 6. Aug 2026, 09:21
- Forum: PCAN-USB X6
- Topic: When will proprietary driver improvements (TX batching, extra ctrlmodes) land in the mainline in-kernel driver?
- Replies: 3
- Views: 608
Re: When will proprietary driver improvements (TX batching, extra ctrlmodes) land in the mainline in-kernel driver?
Hi,
thank you for the offer regarding the out-of-tree driver, we appreciate it. However, we're likely going to move to an updated kernel version in the near future for other reasons. If this is still relevant, I'll get in touch as soon as I have more concrete information on this topic. For now I ...
thank you for the offer regarding the out-of-tree driver, we appreciate it. However, we're likely going to move to an updated kernel version in the near future for other reasons. If this is still relevant, I'll get in touch as soon as I have more concrete information on this topic. For now I ...
- Wed 5. Aug 2026, 12:15
- Forum: PCAN-USB X6
- Topic: No way to detect self-received (echoed) frames under hardware loopback
- Replies: 6
- Views: 924
Re: No way to detect self-received (echoed) frames under hardware loopback
Hi,
thank you for the clarification!
I found the following information on the official SocketCAN Documentation (https://docs.kernel.org/networking/can.html):
MSG_CONFIRM:
set when the frame was sent via the socket it is received on. This flag can be interpreted as a ‘transmission confirmation ...
thank you for the clarification!
I found the following information on the official SocketCAN Documentation (https://docs.kernel.org/networking/can.html):
MSG_CONFIRM:
set when the frame was sent via the socket it is received on. This flag can be interpreted as a ‘transmission confirmation ...
- Tue 4. Aug 2026, 16:20
- Forum: PCAN-USB X6
- Topic: Disabling one interface causes a 100ms+ TX pause on unrelated interfaces
- Replies: 2
- Views: 812
Re: Disabling one interface causes a 100ms+ TX pause on unrelated interfaces
Hi,
Thanks for looking into this! Good news, the root cause has been tracked down, so no need to send the email.
It comes down to how the Linux kernel's rtnl_lock works: it's a single, global lock shared across all network interfaces, not just the one being reconfigured. This is a known kernel ...
Thanks for looking into this! Good news, the root cause has been tracked down, so no need to send the email.
It comes down to how the Linux kernel's rtnl_lock works: it's a single, global lock shared across all network interfaces, not just the one being reconfigured. This is a known kernel ...
- Mon 3. Aug 2026, 16:40
- Forum: PCAN-USB X6
- Topic: No way to detect self-received (echoed) frames under hardware loopback
- Replies: 6
- Views: 924
Re: No way to detect self-received (echoed) frames under hardware loopback
Hi,
Thanks for the clarification. Just to make sure I understand correctly: MSG_CONFIRM itself is a general SocketCAN feature, but it only works if the driver implements the frame-echo mechanism on its side. So what you're describing isn't a limitation of the SocketCAN API, it's that your netdev ...
Thanks for the clarification. Just to make sure I understand correctly: MSG_CONFIRM itself is a general SocketCAN feature, but it only works if the driver implements the frame-echo mechanism on its side. So what you're describing isn't a limitation of the SocketCAN API, it's that your netdev ...
- Thu 30. Jul 2026, 15:27
- Forum: PCAN-USB X6
- Topic: Disabling one interface causes a 100ms+ TX pause on unrelated interfaces
- Replies: 2
- Views: 812
Disabling one interface causes a 100ms+ TX pause on unrelated interfaces
Hello,
Versions: Linux kernel 6.12.47, PEAK proprietary Linux driver 9.2.0, PCAN-USB X6 FD firmware 3.5.1 (6-channel PCAN-USB X6, 3 physical USB units, 2 channels each)
Using SocketCAN :D bringing an interface down during operation can take several milliseconds by itself, which is expected ...
Versions: Linux kernel 6.12.47, PEAK proprietary Linux driver 9.2.0, PCAN-USB X6 FD firmware 3.5.1 (6-channel PCAN-USB X6, 3 physical USB units, 2 channels each)
Using SocketCAN :D bringing an interface down during operation can take several milliseconds by itself, which is expected ...
- Thu 30. Jul 2026, 15:20
- Forum: PCAN-USB X6
- Topic: When will proprietary driver improvements (TX batching, extra ctrlmodes) land in the mainline in-kernel driver?
- Replies: 3
- Views: 608
When will proprietary driver improvements (TX batching, extra ctrlmodes) land in the mainline in-kernel driver?
Hello,
Versions: Linux kernel 6.12.47 (mainline peak_usb in-kernel driver), PCAN-USB X6 FD firmware 3.5.1
The maximum achievable bus load with the mainline in-kernel peak_usb driver (SocketCAN :D ) is significantly lower than with the proprietary driver. As far as I can tell, this is because the ...
Versions: Linux kernel 6.12.47 (mainline peak_usb in-kernel driver), PCAN-USB X6 FD firmware 3.5.1
The maximum achievable bus load with the mainline in-kernel peak_usb driver (SocketCAN :D ) is significantly lower than with the proprietary driver. As far as I can tell, this is because the ...
- Thu 30. Jul 2026, 15:16
- Forum: PCAN-USB X6
- Topic: No way to detect self-received (echoed) frames under hardware loopback
- Replies: 6
- Views: 924
No way to detect self-received (echoed) frames under hardware loopback
Hello,
Versions: Linux kernel 6.12.47, PEAK proprietary Linux driver 9.2.0, PCAN-USB X6 FD firmware 3.5.1
With the proprietary driver (using SocketCAN :D ) it's possible to enable genuine hardware loopback (CAN_CTRLMODE_LOOPBACK). Under Linux's software loopback (SocketCAN's default kernel-side ...
Versions: Linux kernel 6.12.47, PEAK proprietary Linux driver 9.2.0, PCAN-USB X6 FD firmware 3.5.1
With the proprietary driver (using SocketCAN :D ) it's possible to enable genuine hardware loopback (CAN_CTRLMODE_LOOPBACK). Under Linux's software loopback (SocketCAN's default kernel-side ...
- Thu 30. Jul 2026, 15:11
- Forum: PCAN-USB X6
- Topic: Hardware timestamp is 0 for the first self-received frames at high data rate (HW loopback)
- Replies: 1
- Views: 523
Hardware timestamp is 0 for the first self-received frames at high data rate (HW loopback)
Hello,
Versions: Linux kernel 6.12.47; PEAK proprietary Linux driver 9.2.0; PCAN-USB X6 FD firmware 3.5.1
Using the proprietary driver (SocketCAN :D ) , I enabled CAN_CTRLMODE_LOOPBACK (hardware loopback) so that self-received/echoed frames get a genuine hardware timestamp instead of the software ...
Versions: Linux kernel 6.12.47; PEAK proprietary Linux driver 9.2.0; PCAN-USB X6 FD firmware 3.5.1
Using the proprietary driver (SocketCAN :D ) , I enabled CAN_CTRLMODE_LOOPBACK (hardware loopback) so that self-received/echoed frames get a genuine hardware timestamp instead of the software ...