PCAN UDS Message Flow Control and Tester present problem?

[Ken0711]

Good Morning,Wagner

I checked all participant, i found when i sent the UDS message with functional address ,it will send the 3E 80 with 0000H ,

and i checked my configuration and tried to compare with the Sample(06_client_all_request),it still send the 3E80 with 0000h

as shown my configuration

Code: Select all

           
            TPUDSStatus result;
            TPUDSMsg request = new TPUDSMsg();
            TPUDSMsg requestConfirmation = new TPUDSMsg();
            TPUDSMsg response = new TPUDSMsg();
            UInt32 ResponseTimeOut = 2000;
            uint Counter = 5;

            request.MSGTYPE = TPUDSMessageType.PUDS_MESSAGE_TYPE_REQUEST;
            request.NETADDRINFO.SA = (byte)TPUDSAddress.PUDS_ISO_15765_4_ADDR_TEST_EQUIPMENT;
            request.NETADDRINFO.TA = (byte)TPUDSAddress.PUDS_ISO_15765_4_ADDR_OBD_FUNCTIONAL;
            request.NETADDRINFO.TA_TYPE = TPUDSAddressingType.PUDS_ADDRESSING_FUNCTIONAL;
            request.NETADDRINFO.RA = 0x00;
            request.NETADDRINFO.PROTOCOL = TPUDSProtocol.PUDS_PROTOCOL_ISO_15765_2_11B;

so what's the problem ?

Thanks!

[K.Wagner]

Hello,

the PCAN-UDS API doesn't generate such a message for its own.

Are you sending UUDT messages from your app with PCAN-UDS? Are you additionally using PCAN-Basic in your app? It looks like a normal CAN message. Maybe you have code that is being triggered at the same time you send the functional request?

and i checked my configuration and tried to compare with the Sample(06_client_all_request),it still send the 3E80 with 0000h

Does the sample project generate the 0000h [3E 80] frame too? If not, then it is an additional hint that it is being generated from somewhere else.

[Ken0711]

Hello Wagner ,

I did't use the UUDT Message from my app with PCAN-UDS。

Actually ，when i Masked the Functional Address Message ,it was normally(no 3E 80 From 0000h)

i tried execute the sample(06) ,it also sent normally

the only difference is which i used the old pcan_uds version ,there haven't this configuration config.type = uds_msgtype.PUDS_MSGTYPE_USDT

Code: Select all

    public enum TPUDSMessageType : byte
    {
        /// <summary>
        /// UDS Request Message
        /// </summary>
        PUDS_MESSAGE_TYPE_REQUEST = 0x00,
        /// <summary>
        /// UDS Request/Response confirmation  Message
        /// </summary>
        PUDS_MESSAGE_TYPE_CONFIRM = 0x01,
        /// <summary>
        /// Incoming UDS Message
        /// </summary>
        PUDS_MESSAGE_TYPE_INDICATION = 0x02,
        /// <summary>
        /// UDS Message transmission started
        /// </summary>
        PUDS_MESSAGE_TYPE_INDICATION_TX = 0x03,
		/// <summary>
		/// Unacknowledge Unsegmented Data Transfert
		/// </summary>
		PUDS_MESSAGE_TYPE_CONFIRM_UUDT = 0x04,
    
    }

it is the reason which caused the problem?

thanks!

[K.Wagner]

Hello,

the only difference is which i used the old pcan_uds version

Sorry, but we do support only for the latest versions. Note that in every new version changes, bug fixes and enhancements are made, not only for PCAN-UDS but also for the underlying APIs PCAN-ISO-TP and PCAN-Basic. We cannot help on older versions as problems may arise, that are already fixed or are consequence of other bugs.

Please use the latest versions and try again. If the error persists, then we need a sample project for reproduction. If you cannot or you don't want to do so, then we cannot helpt you.

You find history of changes and download links of the libraries here:
PCAN-UDS: https://www.peak-system.com/PCAN-UDS-API.373.0.html
PCAN-ISO-TP: https://www.peak-system.com/PCAN-ISO-TP-API.372.0.html
PCAN-Basic: https://www.peak-system.com/PCAN-Basic.126.0.html

Thanks for your understanding.