If you are starting and stopping sessions asynchronously:
XNET Stop will stop a session first, and then try and stop the interface if it is not being used by another session. If you are starting and stopping sessions asynchronously, different processes could cause the firmware to behave unexpectedly or enter a bad state. Once the firmware is in a bad state, the system API will not be able to communicate with it and will re-assign the interface of a default name of "CAN-1" which will cause further internal errors.
Thank you for your feedback.
You changed your response to Not Helpful
You changed your response to Helpful
Collaborate with other users in our discussion forums
A valid service agreement may be required, and support options vary by country.