When an application transmits CAN data through PCANBasic.dll but PCAN-Explorer does not display the messages, connect PCAN-Explorer to the network created during PCAN-Basic initialization. The confirmed network name in this case is PCANLight_USB_16.
Root Cause
Successful transmission does not ensure that PCAN-Explorer is attached to the same network. The PCAN-Basic application creates PCANLight_USB_16 during initialization, so PCAN-Explorer cannot select that network until the application has initialized it.
Connection Procedure
- Start the application that initializes PCANBasic.dll.
- Wait for initialization to create the
PCANLight_USB_16network. - Open PCAN-Explorer and connect it to
PCANLight_USB_16. - Transmit a CAN message from the PCAN-Basic application.
Verification and Python Scope
Verify that PCAN-Explorer is connected specifically to PCANLight_USB_16, then confirm that transmitted messages appear in its receive view. If the network is absent, confirm that the PCAN-Basic application started first and completed initialization.
The evidence confirms the PCAN-Basic network-selection fix but does not establish whether a CANAPI2.py interface exists. Do not treat migration to CANAPI2.dll as necessary for message visibility; first verify the PCAN-Basic initialization and PCAN-Explorer connection sequence.
FAQ
Why does PCAN-Explorer not show messages sent with PCANBasic.dll?
PCAN-Explorer may be connected to a different network. Connect it to PCANLight_USB_16, which the PCAN-Basic API creates during initialization in this case.
Why is PCANLight_USB_16 missing in PCAN-Explorer?
Start the PCAN-Basic application first. The network becomes available only after the application initializes the PCAN-Basic API.
Do I need CANAPI2.dll to monitor transmitted CAN messages?
No migration is required for the confirmed issue. Initialize PCANBasic.dll first, then attach PCAN-Explorer to PCANLight_USB_16; the evidence does not establish the availability of CANAPI2.py.