FreeMASTER中的主题 FreeMASTER 1.3.13.1 using Kvaser PCICAN card + canlib32.dll version 8.45.724 - can't open the port.

FreeMASTER 1.3.13.1 using Kvaser PCICAN card + canlib32.dll version 8.45.724 - can't open the port.

maqi7362_slpt — Wed, 18 Sep 2024 17:46:30 GMT

Need to work on FreeMASTER on CAN

use FreeMASTER Version 1.3.13.1

using Kvaser PCICAN card with canlib32.dll version 8.45.724.

CANKING is running and see self-generated traffic on both CAN channels after connecting both ports with RS232 + 120 Ohm.

under FreeMaster option window, when I test the connection, it said can't open the port.

I am using the latest PCICAN driver from Kvaser. And also knowing that FreeMaster was released around 2011.

What is the best way to solve this dilemma.

Thanks

Joe

Re: FreeMASTER 1.3.13.1 using Kvaser PCICAN card + canlib32.dll version 8.45.724 - can't open the po

MichalH — Thu, 19 Sep 2024 06:27:52 GMT

Hello,

is there any reason you are still at the version 1? There is a version 3.2.3 now available at www.nxp.com/freemaster

Well, the Kvaser CAN support is probably still based on the old library version, but at least you can try it. We are using Kvaser USB interfaces quite frequently. It is using the same drivers and it works as expected.

Regards,
Michal

Re: FreeMASTER 1.3.13.1 using Kvaser PCICAN card + canlib32.dll version 8.45.724 - can't open the po

maqi7362_slpt — Thu, 19 Sep 2024 19:00:55 GMT

I am indeed on 3.2.3 . GUI's help window gives me FreeMASTER 1.3.13.1.

My machine does not allow me install older version after canlib32.dll version 8.45.724 is installed.

I will try another machine.

BTW, can you share your Kvaser canlib.dll version? No release from 2001 to 2017. I don't know I shall try version before 2001 or right on 2017.

Thanks

Joe

Re: FreeMASTER 1.3.13.1 using Kvaser PCICAN card + canlib32.dll version 8.45.724 - can't open the po

maqi7362_slpt — Thu, 19 Sep 2024 20:52:12 GMT

Hi, Michal,

After some hassle with IT and uninstall, I got the port opened using Kvaser 2001 canlib.dll.... and in test mode, I can access the CAN port.

Now, I need some help to complete the test on CAN:

during Freemaster test mode, I use 0x7aa message is sending "7a, C0, 40"

can you tell me what reply message is, via 0x7ab,.. I am trying to use CANKING function to manaully reply test message. However, I could not find information on how to reply this test message on protocol V4 pdf. Can you help me where to get get this information? Thanks. Joe.

Re: FreeMASTER 1.3.13.1 using Kvaser PCICAN card + canlib32.dll version 8.45.724 - can't open the po

MichalH — Mon, 23 Sep 2024 07:44:13 GMT

Hello,

the format of the protocol messages is outlined in a whitepaper "serial_protocol_v4.pdf" included in the FreeMASTER driver installation (get a MCU SDK installation package for a target MCU, such as FRDM-MCXN947).

To your question: Both command and response can be transmitted on the same CAN frame ID (0x7aa by default). There is a direction M2S bit in the header byte of each frame which enables to use just a single ID.

The frame you have seen: "7A C0 40" is a board detection using legacy protocol. The legacy devices would reply with a detection response. New protocol-v4 devices will reply with error message "32 82 87" (error 82).

In protocol V4, FreeMASTER may use a CAN ping command "7B C0 00 ED" and shall receive a success message "32 00 00". FreeMASTER may then continue with protocol parameters probing (MTU detection) "67 20 05 00 4D 54 55 00" + "D1 8B" and gets a replay such as "27 40 06 4D 54 55 00 F0" + "92 01 70".

This section of the whitepaper specifies the control byte of CAN frames carrying the standard serial protocol payload:

Regards,
Michal

Re: FreeMASTER 1.3.13.1 using Kvaser PCICAN card + canlib32.dll version 8.45.724 - can't open the po

maqi7362_slpt — Thu, 03 Oct 2024 19:32:46 GMT

Michal,

GUI replied with 7B C0 00 ED, after I responded with your "32 82 87" message from "Slave" side (Kvaser single message send utility).

I think I am confident enough to move to the next step using target board and V4 protocol now.

Thanks

Joe