some question about PassThru and CANFD
some question about PassThru and CANFD
Can I use the PassThru API to enable the canfd transmission function of PCAN-USB FD?
- PEAK-Support
- Sales & Support
- Posts: 1646
- Joined: Fri 10. Sep 2010, 19:34
Re: some question about PassThru and CANFD
The FD Version of PassThru is not officially finished . So we have no final release for it.
(no ISO norm ready – no Release ready)
But we have buil, based on the GM Extension GMW177753, a PassThru Version that also Support CAN-FD.
Please contact our support if you are interested in a pre-release version of this API
(no ISO norm ready – no Release ready)
But we have buil, based on the GM Extension GMW177753, a PassThru Version that also Support CAN-FD.
Please contact our support if you are interested in a pre-release version of this API
--------------------------------
PEAK-System Technik
Technical Support Team
support[at]peak-system.com
-------------------------------
PEAK-System Technik
Technical Support Team
support[at]peak-system.com
-------------------------------
Re: some question about PassThru and CANFD
So now I want to use the canfd transmission function of pcan-usbfd, am I only use the Can basic api?
Last edited by M.Gerber on Tue 23. Oct 2018, 08:21, edited 1 time in total.
Reason: Removed full quote of preceding post
Reason: Removed full quote of preceding post
Re: some question about PassThru and CANFD
Hello,
PCAN-Basic: Supports CAN and CAN-FD protocols
PCAN-ISO-TP: Supports ISO-15765-2, a.k.a. ISO-TP, and uses CAN and CAN-FD as transport protocol.
PCAN-UDS: Supports ISO-15765-3/ISO-14229, a.k.a. UDS, and uses CAN as transport protocol.
PCAN-OBDII: Supports ISO-15765-4, a.k.a. OBDII, and uses CAN as transport protocol.
PCAN-PassThru: Suppors CAN, ISO-15765-2, and ISO-15765-4, and uses CAN as transport protocol.
PCAN-PassThru (GMW177753)-BETA: Supports CAN, ISO-15765-2, ISO-15765-4, using CAN as transport protocol; and the proprietary protocol GMW-177753 (ISO-15765-2, ISO-14229) using CAN-FD as transport protocol.
PCAN-Basic: Supports CAN and CAN-FD protocols
PCAN-ISO-TP: Supports ISO-15765-2, a.k.a. ISO-TP, and uses CAN and CAN-FD as transport protocol.
PCAN-UDS: Supports ISO-15765-3/ISO-14229, a.k.a. UDS, and uses CAN as transport protocol.
PCAN-OBDII: Supports ISO-15765-4, a.k.a. OBDII, and uses CAN as transport protocol.
PCAN-PassThru: Suppors CAN, ISO-15765-2, and ISO-15765-4, and uses CAN as transport protocol.
PCAN-PassThru (GMW177753)-BETA: Supports CAN, ISO-15765-2, ISO-15765-4, using CAN as transport protocol; and the proprietary protocol GMW-177753 (ISO-15765-2, ISO-14229) using CAN-FD as transport protocol.
Best regards,
Keneth
Keneth
Re: some question about PassThru and CANFD
Thank you very much for your reply. I've got the DLL file, but where do I go to get the header file corresponding to the passthru API?
Last edited by M.Gerber on Tue 23. Oct 2018, 08:21, edited 1 time in total.
Reason: Removed full quote of preceding post
Reason: Removed full quote of preceding post
Re: some question about PassThru and CANFD
Hello,
The PCAN-PassThru Api is actually thought to be used with applications that already implements J2534, so no header file is shipped. If you want to write your own J2534, you should acquire the documentation from SAE-J2534.
If you want to test the BETA-Version, that supports CAN-FD, you will need the GM documentation, GMW17753
Within the PDF shipped with PCAN-PassThru you find examples of use for each function API, with remarks on PEAK related data.
The PCAN-PassThru Api is actually thought to be used with applications that already implements J2534, so no header file is shipped. If you want to write your own J2534, you should acquire the documentation from SAE-J2534.
If you want to test the BETA-Version, that supports CAN-FD, you will need the GM documentation, GMW17753
Within the PDF shipped with PCAN-PassThru you find examples of use for each function API, with remarks on PEAK related data.
Best regards,
Keneth
Keneth
Re: some question about PassThru and CANFD
Hi,
PassThruIoctl always returns the error of "A PCAN Channel has not been initialized yet or the initialization process" when using passthru API to initialize canfd (ISO15765_FD_PS). However, if the option J1962_PINS is set, it will not retrun error, but I don't think I need to set this option. Is there any solution, or can you give a sample code to initialize canfd (ISO15765_FD_PS)?
Here is my code.
PassThruIoctl always returns the error of "A PCAN Channel has not been initialized yet or the initialization process" when using passthru API to initialize canfd (ISO15765_FD_PS). However, if the option J1962_PINS is set, it will not retrun error, but I don't think I need to set this option. Is there any solution, or can you give a sample code to initialize canfd (ISO15765_FD_PS)?
Here is my code.
Code: Select all
void CfgFDDevice15765(SCONFIG * CfgItem, SCONFIG_LIST & Input, unsigned int BS_15765, unsigned int STMIN_15765)
{
CfgItem[0].Parameter = BS_TX;
CfgItem[0].Value = BS_15765;
//CfgItem[0].Value = 0xffff;
CfgItem[1].Parameter = STMIN_TX;
CfgItem[1].Value = STMIN_15765;
//CfgItem[1].Value = 0xffff;
CfgItem[2].Parameter = ISO15765_BS;
CfgItem[2].Value = 0;
CfgItem[3].Parameter = ISO15765_STMIN;
CfgItem[3].Value = 0;
//CfgItem[4].Parameter = J1962_PINS ;
//CfgItem[4].Value = PIN6_14;
Input.NumOfParams = 4;
Input.ConfigPtr = &(CfgItem[0]);
}
Re: some question about PassThru and CANFD
Hello,
do you have initialized the channel already with PassThruOpen before calling the IOCTL? Regarding the Pin, this is the only supported one:
do you have initialized the channel already with PassThruOpen before calling the IOCTL? Regarding the Pin, this is the only supported one:
Best regards,
Keneth
Keneth
Re: some question about PassThru and CANFD
Hey, thank you for your reply. When I sent the can message, I encountered this problem:“Bus error: an error counter reached the 'heavy'/'warning' limit”. Can you tell me what caused it?
Re: some question about PassThru and CANFD
Hi,
possible reasons:
- wrong CAN cable
- no second active CAN node on your network
- no termination resistors in your CAN cables
- wrong baudrate
regards
Michael
possible reasons:
- wrong CAN cable
- no second active CAN node on your network
- no termination resistors in your CAN cables
- wrong baudrate
regards
Michael