Need help setting up AUTOSAR E2E P02 protocol CRC channels with NI-VCOM

[Pianne]

Hi all,

I need to set up a CAN network to communicate with a 3rd party controller that uses Autosar E2E protocol counter and CRC channels.

I'm using the Custom Device included in 'NI Vehicle Communcitation Toolkit' on a Linux-RT PXI target with NI Veristand 2023.

I have some experience setting up CAN networks on XNET devices but never used the VCOM custom device or any Autosar E2E...
I read through the VCOM manual but it's not clear to me yet...

I (think I) managed to configure the counter channels ok but I'm struggling with the CRC channels:

With the controller in question, I was given the following information:
- CRC is following the "Autosar profile 1" sceme -- "E2E_P01_DATAID_BOTH"
- I was also given a unique "Data ID" for each message

The documentation states that VCOM supports Autosar E2E (that's why we bought it) but there is no mention of it in the 'AutoSignal Types' of the Restbus Simulation Configuration app.

I've found this document, describing the Autosar E2E:
https://www.autosar.org/fileadmin/standards/R20-11/FO/AUTOSAR_PRS_E2EProtocol.pdf

What I took from that is that "E2E_P01_DATAID_BOTH" seems to be a variation of the "J1850 CRC", so I selected "ChecksumUserJ1850" as Autosignal Type in the RBSConfig app. and set 'Initial Value' and 'FinalXORValue' both to '00', correct?

Now I need to figure out what to enter as 'CRCMask', 'UserBytesBefore' and 'UserBytesAfter' and where to enter the "Data ID".

Any help would be greatly appreciated.

-PJ.

[Pianne]

OK. I think I figured it out.

For anyone interested or facing the same, this is how I configured the CRC AutoChannels for AUTOSAR_E2E_Profile1 ("E2E_P01_DATAID_BOTH") in the RBS descriptor:

 - Autosignal Type: "J1850_USER"

 - CRCPolynom: [empty] --> Defined by J1850 as 0x1D

 - CRCMask: "127" --> [01111111] calculate over the first 7 bytes

 - Initial Value: "00" --> Defined by Autosar E2E_P01

 - FinalXORValue: "00" --> Defined by Autosar E2E_P01

 - UserBytesBefore: This is where you enter the unique Data ID for the message, as an array of bytes, starting from the LSB.
        Example: Data ID = 0x2468 (=d9029) --> LSB= 0x68 (=d104), MSB= 0x24 (=d36)

                        --> UserBytesBefore= "104,36" (To be entered in the RBSConfig tool as decimal numbers, separated by a comma)

 - UserBytesAfter: [empty] or "256"

[donbosco100]

How AUTOSAR E2E P02 configure in labview.

[ZYOng]

---

@donbosco100 wrote:

How AUTOSAR E2E P02 configure in labview.

---

The configuration for the AUTOSAR E2E is not done in LabVIEW but RBSConfig tool.

End-to-End Communication Protection: NI-VCOM supports additional checksum mechanisms. You can configure the checksum mechanisms using the RBSConfig tool. 

[donbosco100]

Thank you for your information XYOng,

           I have tried with the RBS config tool there is no clear info. Please share any help docs.

In Canoe we sending the below message with CRC and Counter.

How to configure in NI with RBS config tool and send to xnet.

OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	c0 00 00 00	PDU should be sent cyclacilly each 320ms
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	5e 01 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	1c 02 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	f6 03 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	25 04 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	83 05 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	e1 06 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	4f 07 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	24 08 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	fa 09 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	4c 0a 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	40 0b 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	ea 0c 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	28 0d 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	15 0e 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	3f 0f 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	c0 00 00 00	Here the sequence should re-start again…
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	5e 01 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	1c 02 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	f6 03 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	25 04 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	83 05 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	e1 06 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	4f 07 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	24 08 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	fa 09 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	4c 0a 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	40 0b 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	ea 0c 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	28 0d 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	15 0e 00 00
OTAMC_D_01_XIX_HCP5_CANFD01	16a95596x	4	3f 0f 00 00

[ZYOng]

See Using NI-VCOM Toolkit to Configure Rolling Counter for CAN Application

Select ChecksumUserJ1850 as the Auto Signal type.

[donbosco100]

Thank you for the info, You mentioned J1850 communication. How to configure CANFD.

[ZYOng]

CAN FD is defined in the DBC file.

[donbosco100]

How to RBL file load labview and use in logic.

Thanks

[ZYOng]

You should explore the shipping examples and documentation. All you need to get started are provided

<LabVIEW>\examples\NI-VCOM

C:\Users\Public\Documents\National Instruments\NI-VCOM