Re: ISO-TP_FORMAT_EXTENDED is not working
Posted: Wed 26. Jun 2024, 10:06
Hello,
Some parameters can be overriden at different levels: CAN_TX_DLC can be configured globally for the channel, for a mapping or for a specific message. Using source_mapping.can_tx_dlc=0 tells the API to use any value configured for the channel, by default CAN_TX_DLC is 8 as defined by ISO-15765-2.
As for config_physical.can_id = -1, it states to use the Network Addressing Information to retrieve the mapped can_id. In future release a constant will be used for clarity (PCANTP_CAN_ID_DEFINED_BY_NAI)
For your last question: PCAN-UDS automatically configures standardized mappings as stated in our documentation in "ยง4.3 UDS and ISO-TP Network Addressing Information".
Communication from 0xF1 to ECU 0x01 with Normal addressing is a standardized mapping that's why you don't have to register it.
Some parameters can be overriden at different levels: CAN_TX_DLC can be configured globally for the channel, for a mapping or for a specific message. Using source_mapping.can_tx_dlc=0 tells the API to use any value configured for the channel, by default CAN_TX_DLC is 8 as defined by ISO-15765-2.
As for config_physical.can_id = -1, it states to use the Network Addressing Information to retrieve the mapped can_id. In future release a constant will be used for clarity (PCANTP_CAN_ID_DEFINED_BY_NAI)
For your last question: PCAN-UDS automatically configures standardized mappings as stated in our documentation in "ยง4.3 UDS and ISO-TP Network Addressing Information".
Communication from 0xF1 to ECU 0x01 with Normal addressing is a standardized mapping that's why you don't have to register it.