A program could just as well circumvent the issue of there potentially being left-over messages in the TX queue from a previous application by first calling CAN_Unitialize and only then calling CAN_Initialize, right? Or do you see any problems with that approach?
EDIT: Never mind ... stupid idea ...
Search found 4 matches
- Fri 28. Apr 2017, 09:25
- Forum: PCAN-Basic
- Topic: Receive queue non-empty if previous CAN_Uninitialize missing
- Replies: 3
- Views: 7210
- Mon 13. Feb 2017, 14:35
- Forum: PCAN-View
- Topic: Losing messages
- Replies: 4
- Views: 9187
Re: Losing messages
Well, more than a year later I can report that the problem never did return. I have no idea what exactly did cause the issue, but whatever it was, the driver update seems to have helped. 

- Thu 3. Sep 2015, 16:08
- Forum: PCAN-View
- Topic: Losing messages
- Replies: 4
- Views: 9187
Re: Losing messages
Thanks for your response! I've updated the drivers, and suddenly the previously missing messages are getting through! :o I'm hoping that it stays that way and that it's not just some weird timing issue that I've somehow covered up by rebooting the system or something silly like that.
About the code ...
About the code ...
- Thu 3. Sep 2015, 14:13
- Forum: PCAN-View
- Topic: Losing messages
- Replies: 4
- Views: 9187
Losing messages
Hi,
First off, my problem isn't purely a PCAN-View issue, so I apologize in advance if this isn't the correct sub forum. Anyway, I'm using the Peak PCAN-USB adapter (firmware version: 2.8, driver versiom: 3.8.2) and PCAN-View version 4.0.28.419 on Windows 7.
I have a C++ application that uses ...
First off, my problem isn't purely a PCAN-View issue, so I apologize in advance if this isn't the correct sub forum. Anyway, I'm using the Peak PCAN-USB adapter (firmware version: 2.8, driver versiom: 3.8.2) and PCAN-View version 4.0.28.419 on Windows 7.
I have a C++ application that uses ...