Looping back received messages

[mike_green]

Looking for a way to loop back received CAN messages -- so that any message received from the connected device would be sent back to that device.
This would allow to perform an automated (rather than manual) testing of both Tx and Rx functionality of the CAN interface on the device under test.
Is there such a function in PCAN-View? If not, is there another PEAK System application or HW that could support this? Thanks.

[PEAK-Support]

to get e real, physical feedback (Message is ACK on the BUS from all other nodes) , simply use a 2nd CAN Interface.
With the PCAN-Explorer 6 you could trace all connected channels in one trace file and so see exactly the sending time and the real ACK time on the Bus.

[mike_green]

Thanks for the reply, but that is not what I'm after. I have one CAN port on my device, and I want to test its Tx and Rx functionality.
A manual test would look like this: I would send a CAN message out with preconfigured 8 bytes of data and would see it arriving at the RECEIVE window of PCAN-View.
I would then create a new message in PCAN-View with the same 8 bytes of data and send it out from PCAN back to my device (it would appear in the TRANSMIT window of PCAN-View).
In my device I would verify that the sent data is identical to the received one.
I am looking to automate this process: to configure the PCAN adaptor in such a way that every time it receives a CAN message from the connected device, it would create and send out a message with the same data as in the received message.
This way there is no need for a human operator to execute this procedure - my device would send a message, receive back a message, and verify that the data is the same.
My question is - is there such an app or an API for PCAN that would allow me to configure the PCAN in the way described above.

[PEAK-Support]

You could not "configure" a CAN Interface..you could use the functionality and build that what you need in Software.

You also mix up the confirmation of sending (ACK) your own Message and a automatically sended CAN Frame in your properitarry Format as a ECHO - these are 2 differnet things.

When you need a real physical ACK confirmation you could use:

a) as i wrote, use a second CAN-PC Interface
b) add a "Echo" node on the Network that send you the Message after receiving (ACK) back to the CAN Bus (and so to your incomming queue)

and you need to code your own Software - the PCAN-View is a simply CAN Viewer, if you need to script, use the PCAN-API or PCAN-Explorer.

A software "only" solution for a "self - receive" is with the PCAN-Basic API not possible. Our professional API (PCAN-Developer ) offer this feature with all newer CAN Interfaces. But this API is for CAN Analyzer / Low Level Tool developers.

But if you want a Tool that recieve a CAN Frame - and send out exact the same, you need to write your own application for that
(but keep in mind --> sending same ID from differnet nodes is a bad solution - and normally a "no go" )

[mike_green]

I haven't mentioned an ACK or an ECHO in my post. And the confirmation I mentioned is of getting a completely different message from the other device on the bus (PCAN in this case) that would contain the same data bytes.
Not sure where the confusion comes from and why it is so difficult to understand what I am talking about...
You are saying that there is a PCAN-API that would allow me to do this - then this is the answer I was looking for. Thanks.

[PEAK-Support]

You have to express yourself clearly - your description is misleading because there are different approaches - a simple example would have done the request with the first answer.
I don't understand their undertone either .. we can also talk in German..

MSG from CAN Node on BUS ---> received by CAN USB --> send out Echo from API (with same ID --> still a bad solution.-..)

that is possible - some lines of code with the free PCAN-Basic API

- Topic locked -