ECU Calibration Tool Kit

[Colin hughes]

I have just started using this tool kit.

We used the open.vi to load the a2l file and it reads the characteristic OK and DAQ list, but seemed to miss the part that set up the bus and SetKey DLL.

We set this vier Property.Set but it does not seem to work when we try to read a value from the ECU.

The as2 file does not give a path to the SetKeys DLL's so how does it no where they are.

Using Vector, it seem that some of the property values like station ID are being used as the Message ID with no data.

I am using a version 1 CAN card that could be the problem but I was told that it should work with the serial number on the card. No ask as it is in the PC.

I have a new card on order but I suspect I will still have the same problems.

This a2l file works with other third party software that use the same a2l file and DLL's.

So I have two problems.

Not reading the CAN interface setup part of the a2l file and not logging in the the ECU on the first call as expected as the message ID (send or receive)) is not being used.

Ta

Colin

[Ian Colman]

Hi Colin,

Thanks for your post. Could i ask if you are using the ECU Measurement and Calibration Toolkit with LabVIEW or annother programing enviroment? Also when you encounter each of your two probems, do you revcieve an error message of any sort or does your program hang/crash? The more information you can provide regarding how you try to read the CAN Interface set-up and what happens when it fails the better really.

Best Regards,

Ian Colman
Applications Engineer
National Instruments UK & Ireland

[Colin hughes]

Hi Ian

Thanks for your reply, here is the answer I got from NI

>>I have looked into your issue regarding communication over the CAN bus and I think I can explain why you are running into problems. As it is, the ECU module is only compatable with version 2 >>hardware. This is because the ECU module uses the NI-CAN Channel API whereas your card will only support the Frame API. One solution to your issue is to use a newer CAN card that is >>version 2. There is still a way to use the card you have, but this will require a little more effort. The solution is based on frame to channel conversion and is explained in the two KnowledgeBase's >>linked below. Don't worry about the fact it talks about cRio hardware as the card you have behaves the same.

I looked at the monitor program this morning and it seems that no messages are bring put on the bus.

The ECU tranmits about ten messages which are being picked up OK from the CAN monitor program.

I have a new CAN version 2 card on order but as they are not in stock I have asked them to loan me a USB version for now so that I can get thngs going.

I hope it works as I think there could be issues with USB, Hope not

Ta

Colin

I

[Ian Colman]

Hi Colin,

Thanks for letting me know. Hopefully this will solve your problem but feel free to call Rich or post back here if you have any issues what so ever.

All the best,

Ian Colman

Applications Engineer

National Instruments UK & Ireland

[Colin hughes]

Hi Ian

Forgot, the test stand is  using Labview 7.1. we have an upgrade on order for 8.5 but I might hold fire on installing the upgrade (least impact).

We do have some problems loading the CAN setting from the a2l file , so I need a contact someone on the ECU Calibration Tool kit team so that I can send them the a2l file. (confidential)

They can fix that part of the program for future versions.

Currently in house we do not use a2l but old tb7 format (motorola), but we are hopping to force the ECU teams to produce a2l file for Delphi ECU (heavy duty).

If so I will sent one of them as well.  ReadNames.vi works OK so it is just the CAN cards setting  part., used SetProperty instead.

Thanks

Colin

[DirkW]

I doubt the device version is realy the reason here. The ECU MC TK and the NI-CAN Channel API should work with both Series 1 and 2.

If you need a Seed Key DLL to secure the access to the particular ECU, then you should have the DLL in the same place as his A2L File. The A2L File should reference this DLL and the driver calls this DLL to calculate the Key when you access the ECU.

If there is no reference within the A2L file i doubt you realy need a Seed Key DLL.

Could you explain again what you mean with the setting part?

DirkW

[Colin hughes]

The DLL info is in a2l file and the DLL's are in the same directory as the a2l file.

The settings part off the a2l file are the CAN communication.

Buardrate., Seedkey DLL's, send and receive message ID's intel or Motorola, ECU id and other info.

We set these using SetProperty as they did not read in from the a2l. although the setting we used came from the a2l file.

No CAN message appeared on the CAN bus when we tried to read back a characteristic the last time I tried although at one point the ECU id seemed to used as the CAN message Id.

Ta

Colin