<![CDATA[How to detect if a QCanBusDevice has been physically disconnected?]]>I'm using QCanBusDevice to interface with a Peak Can-Usb adapter.

How can I tell if the device has been removed, i.e. the usb adapter has been physically disconnected from my computer? I looked at all methods QCanBusDevice offers, but none of them tell me if the device is still physically connected.

  • QCanBusDevice::state() remains in the ConnectedState (this is probably the most counterintuitive)
  • QCanBusDevice::hasBusStatus() remains true
  • neither QCanBusDevice::error() nor QCanBusDevice::errorString() report an error
  • QCanBusDevice::errorOccured() is not emitted

It seems like the QCanBusDevice doesnt notice at all that adapter is no longer there.
The only thing that seems to change (and what I'm using right now) is the QCanBusDevice::deviceInfo(), which goes blank when you remove the adapter. Still, this seems rather hacky, so I'm wondering if I'm doing something unintended or if this feature is simply not implemented in QCanBusDevice (or PeakCanBackend to be specific)

]]>https://forum.qt.io/topic/165182/how-to-detect-if-a-qcanbusdevice-has-been-physically-disconnectedRSS for NodeSat, 07 Nov 2026 05:02:35 GMTFri, 16 Oct 2026 14:04:29 GMT60<![CDATA[Reply to How to detect if a QCanBusDevice has been physically disconnected? on Wed, 21 Oct 2026 09:00:38 GMT]]>@aha_1980 Thanks for taking care of this!

I think a method like deviceState() or deviceType() would be appropriate and offer more flexibility for the different CAN plugins. I wouldn't change QCanBusDevice::state() or busStatus(), they have a different meaning.

I have noticed that the Peak USB devices actually fall back to a virtual CAN interface the moment you disconnect the usb device (the virtual interface is called "PCANLight_USB_16" in PCAN-View). This might explain why no errors are reported and the QCanBusDevice remains connected - the virtual interface is still working. This automatic fallback seems to be an intended feature of the peak driver.

Ideally there'd be a DeviceType enum with values like Virtual and Physical to represent what kind of device it currently is. But this switching behaviour seems pretty specific to peak devices, so perhaps somebody has an idea for a more general approach.
Ideally-ideally this change would also be emitted as a signal :)

]]>https://forum.qt.io/post/840552https://forum.qt.io/post/840552Wed, 21 Oct 2026 09:00:38 GMT<![CDATA[Reply to How to detect if a QCanBusDevice has been physically disconnected? on Fri, 16 Oct 2026 16:47:52 GMT]]>I've added a task for that: https://qt-project.atlassian.net/browse/QTBUG-151640

]]>https://forum.qt.io/post/840522https://forum.qt.io/post/840522Fri, 16 Oct 2026 16:47:52 GMT<![CDATA[Reply to How to detect if a QCanBusDevice has been physically disconnected? on Fri, 16 Oct 2026 14:49:37 GMT]]>Hi @__mk__ ,

there is indeed no dedicated API for that problem currently.

What comes closest is QCanBusDevice::busStatus(), but that will currently (most likely) return CanBusStatus::Unknown as there is no special enum for that case.

But I'll take your post as feature request and see if I can add something. I'm not completely sure if that fits into busStatus() or if a separated deviceStatus() would be better. I'm open for suggestions.

Note: QCanBusDevice::hasBusStatus() just tells you if the device supports the function busStatus(), it is not the actual busStatus().

Regards

]]>https://forum.qt.io/post/840521https://forum.qt.io/post/840521Fri, 16 Oct 2026 14:49:37 GMT