Page 1 of 1
Cannot XCP intialize after app. abnormal end
Posted: Fri 2. Aug 2019, 03:42
by bukkun
Hellow.
I found XCP_initalizeCanCannel() return 0x500 after my application has abnormal stop or kill by windows task-manager.
Once logout windows-account, recover XCP_initalizeCanCannel() to normal return.
Could let me how to recover XCP_initalizeCanCannel() without logout windows-account?
Re: Cannot XCP intialize after app. abnormal end
Posted: Fri 2. Aug 2019, 08:53
by K.Wagner
Hello,
This problem is described in the topic
CAN_initialize failing after 'Stop Debugging' in VS 2015
When you finish debugging without closing the connection, or any other abnormal termination, the underlying PCAN-Basic connection remains active. This is actually caught and removed from the device driver, though after some updates of Visual Studio and Windows this worked not more accurately. The problem was introduced with Windows 10, Version 1803. Older Windows versions and the newest don't have this problem.
Re: Cannot XCP intialize after app. abnormal end
Posted: Wed 21. Aug 2019, 09:52
by bukkun
Thank you for your information and advice.
However we can not update to windows10 1903 series freely in my company.
I found that reboot the "Deivice setup manager" services and can re-open CAN-USB on my PC.
Best Regards,
Re: Cannot XCP intialize after app. abnormal end
Posted: Wed 21. Aug 2019, 10:18
by K.Wagner
Hello,
with the last version of our
PeakCpl, Windows Control Panel Applet, there is now the possibility to reset abandoned PCAN-Basic connections (transport layer of XCP). You will see a PCANBasic tab if there are active PCAN-Basic connections. In this way you will don't need to reboot or install updates.