LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

CCP DAQ list issue running with ECU Measurement and Calibration Toolkit 15.0

Hi, 

 

I'm using ECU MC to peform a CAN communication in CCP protocol with my product.

It works petty good when I initialize DAQ task in polling mode, but the acquisition time is too slow (4ms for one signal). Knowing that I have more then 200 signals to monitoring. So to reach my objective (10ms for all signals like X-NET), I must switch to DAQ list mode, the issue is in this mode, DAQ read returns only 0 without any errors. 

It has been severals weeks that I have been blocking by this issue, is someone have already encounted this issue? Get any solutions?

 

Cheng

Test bench development engineer

 

Download All
0 Kudos
Message 1 of 6
(3,358 Views)

Hello ChengXXu,

 

I advice you to use this simple architecture in attachment instead of yours. The error was not handle completely so maybe this time you will get an error coming back to you.

 

I advice you to make your code as simple as possible first: instead of trying to acquire 10 signals, just try 1. The error can originate from communication or the way you handle your datas and display them. 

 

Hope it will help.

 

Bye

 

0 Kudos
Message 2 of 6
(3,307 Views)

Maybe we should do the math.

  • 200 signals (wo/errors or checksum handling)
  • Read Doubles (64-bits)
  • 10ms total read time
  • 10ms / (200 * 64) = 7.8125 E-7
  • 1Mbaud max cannot handle 7.8125E-7
Help the Community (and future reviewers) by marking posts as follows:
If it helped - KUDOS
If it answers the issue - SOLUTION
0 Kudos
Message 3 of 6
(3,304 Views)

In fact, the baudrate was 1G bit/s.

Get 200 signals in 10ms with DAQ list method is surely possible. Just like CANalyzer did. 

0 Kudos
Message 4 of 6
(3,300 Views)

Hello Pierre Denis,

 

Thx for your response, unfortunately the situation doesn't be impoved, same behavior (still return "0" with out error). To me National Instrument has a different standard in CCP protocol from CANalyzer, therefore a database (a2l format) generated by others equipments wont supported NI materiel (to be confirmed with NI).

0 Kudos
Message 5 of 6
(3,290 Views)

Actually, it may be an issue with Vector CANTech.  I have been using the A2L format for years with the NI CCP protocol with only minor issues.  We have found that generally, it is something specific to the way that VC displays some things. 

Help the Community (and future reviewers) by marking posts as follows:
If it helped - KUDOS
If it answers the issue - SOLUTION
0 Kudos
Message 6 of 6
(3,284 Views)