Details
-
Bug
-
Resolution: Incomplete
-
P3: Somewhat important
-
None
-
5.9.6, 5.11.2
-
OS: Windows 10 Enterprise 2016 - 64 Bit
Qt: 5.11.2
PCANBasic.dll - from 20.11.2017 ( newest found at 10.10.2018 )
PCAN-miniPCIe FW-Version: 1.3.0
PCAN-miniPCIe Driver-Version: 4.1.4
PCAN-miniPCIe Hardware-Rev: 4
PCAN-miniPCIe Article Number: IPEH-003049
PCAN-USB FW-Version: 2.8
PCAN-USB Driver-Version: 4.1.4
PCAN-USB Article Number: IPEH-002021/002022OS: Windows 10 Enterprise 2016 - 64 Bit Qt: 5.11.2 PCANBasic.dll - from 20.11.2017 ( newest found at 10.10.2018 ) PCAN-miniPCIe FW-Version: 1.3.0 PCAN-miniPCIe Driver-Version: 4.1.4 PCAN-miniPCIe Hardware-Rev: 4 PCAN-miniPCIe Article Number: IPEH-003049 PCAN-USB FW-Version: 2.8 PCAN-USB Driver-Version: 4.1.4 PCAN-USB Article Number: IPEH-002021/002022
-
Windows
Description
Using the PCAN-miniPCIe Dual Channel Version and taking advantage of the QCanBusDevice. Connecting, sending and receiving works just fine.
There is a chance ( about 10% ) that when disconnecting the device and connecting again that the device is "dead".
Dead means: For an unspecified time ( always different ) of seconds to half a minute the device does not receive and send messages. This has been inspected by external sniffing on the CAN-BUS that shows that there are still messages beeing sent and received from and to other participants. This "dead" state is automatically left after some time and everything is working fine again.
It looks like the device is just disconnected, but the device.state() returns that it is in connectedState.
This problem does not occur when using the PCAN-USB interface.
As i cannot tell if this problem is Qt, Peak or anything else sided, sorry for the inconvenience if this is not a QTBug.