PEAK-System Forum

Hi,
many thanks for the clarifications and comment re-first frame. These certainly help me better understand the system implications from the CAN hardware perspective. Hardware errors, e.g. BUSHEAVY, in my case can be managed. They have not to date interfered with the desired inter-process ...

Hi,
I hope the attached image helps explain the intention? P.S. If this must have PCAN-USB hardware to operate that is not an issue from my perspective

Hi,
in following the regimen outlined, both using the Peak-System demonstration application and now my own code. A 'Self Receive' is operational with the configuration detailed.

So it seems it is not required to have external hardware.


The question therefore remains:
1) Why does opening and ...

Hi,
thanks for the reply.

I assesed the ACK to be contribtuory, following connection of the external CAN hardware.
Hence question 1.

The confounding point was use of a second instance of RP1210_Test.exe which at least permitted exchange from PCAN-View.

Where an applicaiton uses PCAN-Basic for ...

The problem described below occurs with software I have written.
However, the issue is detailed using RP1210_Test.exe to remove any concerns as to the code base, so as to assist with root cause investigation.

Description:
Issue: Messages not received or transmitted between RP1210_Test.exe and PCAN ...