Page 1 of 1
Corrupting the Ack delimiter and CRC delimiter
Posted: Thu 26. Jul 2018, 07:12
by shraavann
Hello ,
I'm new to the usage of PCAN usb Pro , i want to corrupt the acknowledgement delimiters and CRC delimiters of a message that is being transmitted from the PCAN usb pro but i could not find any such options on the PCAN view tool or the API .
Is it possible to corrupt these fields for the transmitted message ?
Thanks
Re: Corrupting the Ack delimiter and CRC delimiter
Posted: Thu 26. Jul 2018, 09:38
by M.Maidhof
Hi,
with PCAN-View you can use the error generator tab to destroy/change a specific bit of a CAN message. You have to calculate the bitposition of the crc delimiter of your CAN message, and set the bitposition in the errorgenerator tab. Knowledge of the raw CAN protocol definitions are necessary to use that feature. Take care of the stuff bits in your calculation.
regards
Michael
Re: Corrupting the Ack delimiter and CRC delimiter
Posted: Thu 26. Jul 2018, 10:56
by shraavann
Hi Mike
I could destroy the required bit positions of a message that is received by the PCAN tool

.
I'm not able to destroy/corrupt the bit positions of a message that i want to transmit from the PCAN tool to another ECU .
I have uploaded a image where i could destroy a particular bit of a message which is being received by the PCAN.
Re: Corrupting the Ack delimiter and CRC delimiter
Posted: Thu 26. Jul 2018, 15:58
by M.Maidhof
Hi,
did you set the ID to your transmit message ID? Did you transmit this ID in the transmit list after setup the ID in the error generator tab?
regards
Michael
Re: Corrupting the Ack delimiter and CRC delimiter
Posted: Fri 27. Jul 2018, 06:00
by shraavann
Yes i did set a ID in the transmit list ,in this case the transmit message ID is 55h with cycle time of 1000 ms .
Re: Corrupting the Ack delimiter and CRC delimiter
Posted: Fri 27. Jul 2018, 08:36
by PEAK-Support
You ignore 50 Messages - with a Sheduler that use 1000ms, you have to wait 50 Seconds before the Device destroy the Frame. After that you destroy for over 50 Seconds every Message (52 Times - 1000ms).
Here a screen - 2 PCAN-USB - destroying 0x1c every 6th Frames

- Destroy_0x01c.JPG (150.7 KiB) Viewed 15341 times