A PCAN-UDS flash operation that stalls during service 0x36 can result from PCAN-USB firmware rather than the C# application or bus termination. In the documented case, the failing older adapter reported firmware 2.8; PEAK-System identified that firmware as lacking properties required by UDS and directed the user to support for an update.
Identify the failure pattern
The application uses PCAN-UDS.dll from C# to flash a device. The operation succeeds with newer PCAN-USB and PCAN-PRO hardware but fails with an older PCAN-USB adapter, even though only one adapter is connected and the CAN network is terminated.
| Evidence | Engineering significance |
|---|---|
Failure occurs while using UDS service 0x36
|
The transfer stops before UDSApi.Write completes all frames. |
| Newer PCAN-USB and PCAN-PRO devices work | Compare adapter firmware before changing the application protocol sequence. |
| Older PCAN-USB behavior differs between machines | Do not assume nominally identical computers have the same adapter firmware or installed API components. |
| PCAN-Basic reports repeated receive failures | The log confirms a persistent communication failure but does not define the meanings of the status values. |
Interpret the PCAN-Basic log without overdiagnosing it
Channel 0x51 repeatedly reports statuses 0x80000008, 0x80010000, 0x80000010, and 0x80000002. ISO-TP also ignores frames with CAN ID 0x001, message type 0x80, DLC 4, and data 00 00 00 04 00 00 00 00. The evidence does not provide authoritative definitions for those status values, so use them as correlation markers rather than assigning unsupported causes.
There is also a version discrepancy to resolve: the application description lists PCAN-Basic 4.3.4.246, while the captured log header reports the 64-bit API as 4.3.2.246. Confirm which DLL the failing process actually loads. This discrepancy is worth correcting, but the evidence identifies adapter firmware 2.8 as the established cause in this case.
Use firmware as the primary decision point
PEAK-System states that UDS requires device properties that may be absent on an old adapter. For the reported device, firmware 2.8 is the decisive finding.
| Firmware result | Decision |
|---|---|
2.8 |
Treat the adapter firmware as the confirmed blocker and request an update through PEAK-System support. |
| Any other version | The supplied evidence does not establish the cause. Preserve the PCAN-Basic and PCAN-View logs and continue diagnosis without assuming the same firmware defect. |
Check and correct the affected adapter
- Connect the older PCAN-USB adapter and open PCAN-View.
- Read the firmware version in the PCAN-USB pane. Record the adapter identity and firmware so results are not confused when testing multiple units.
- If the pane reports firmware
2.8, contact PEAK-System support and request assistance updating the adapter firmware. Do not infer an update procedure or target firmware version from the available evidence. - Confirm that the C# process uses the intended 64-bit libraries. The reported application set was PCAN-Basic
4.3.4.246, PCAN ISO-TP2.2.1.121, and PCAN-UDS1.3.3.50; compare this with the API version recorded in the new log. - Repeat the same service
0x36flash operation with the updated adapter while keeping the application, target device, connection, and termination unchanged.
Verify the resolution
Verification requires more than opening the CAN channel. Confirm that UDSApi.Write finishes sending the complete service 0x36 transfer and that the flash workflow advances beyond the previous stopping point. Capture a fresh PCAN-Basic log and compare it with the failing run: the repeated channel 0x51 read-failure sequence should no longer coincide with the transfer stopping.
If the operation still fails after PEAK-System completes the firmware update, preserve the firmware reading, loaded DLL versions, and both logs. The supplied evidence does not support assigning a second root cause from the status codes alone.
FAQ
Why does PCAN-UDS service 0x36 stop writing on an old PCAN-USB?
Check the adapter firmware in the PCAN-USB pane of PCAN-View. Firmware 2.8 was identified as lacking properties required by UDS and requires assistance from PEAK-System support to update.
Do PCAN-Basic statuses 0x80000008 and 0x80010000 prove a CAN wiring fault?
No. The log shows these statuses during the failure, but the evidence does not define them or establish wiring as their cause. Use the firmware result and controlled retest as the decision path.
How do I verify that the PCAN-USB firmware update fixed UDSApi.Write?
Repeat the same service 0x36 flash operation and confirm that UDSApi.Write completes all frames and advances beyond the former stopping point. Save a new PCAN-Basic log and verify the failure sequence no longer interrupts the transfer.
