XCP and CCP Master Add-On for NI VeriStand feedback.

[Lucabeer]

Hi!

We have made another test... which probably clarifies things a bit.

Instead of deploying the addon on the real-time platform PXI-8110, we have tried running it on our Windows 7 PC. As a matter of fact, our previous successful experiments with Labview (with ECU Measurement and Calibration toolkit) and DAQ lists were ALWAYS done on the PC instead of making them run on the dedicated hardware.

So, the problem now seems to be only related to the PXI-8110...

(BTW, polling does not seem to work either...)

[JWilson98]

The Windows vs. real-time piece of information is valuable.  A common issue is the real-time compliance of a seedkey DLL for the associated A2L file.  A helpful tool is the RT DLL Checker which can be found here:

http://digital.ni.com/public.nsf/allkb/0BF52E6FAC0BF9C286256EDB00015230

Your DLL has to pass this test in order to run on a real-time system since any Windows dependancies obviously will not work.

[Lucabeer]

Yes, we already thought of that! But our ECU does not need a seed key DLL for communication...

[Lucabeer]

To further clarify the situation, we have made two recordings of CCP activity with a CAN analyzer...

In the first one (CAN0) you can see what happens if we run the Add-On on the Windows PC... and everything runs smooth.

In the second one (CAN1) we are running the Add-On on the PXI target: you can clearly see that CCP messages stop immediately, as if the DAQ list was not started. Please note that there are no error replies by the ECU...

[StephenB]

Can you tell me the value of the status channels of the custom device? There may be an error indicated that would help us debug.

Thanks,

[Lucabeer]

Mmmm, where exactly should I get that info?

Has it something to do with the XNET Bus Monitor? (Which, by the way, doesn't seem to start: a dialog windows pops up and disappears immediately)

[StephenB]

The custom device has several channels under a folder called status. What are their values when you're running?

[StephenB]

If you don't see the status channels, then you're running an older version of the custom device. The version posted is #13. The status channels were added in #12

[Lucabeer]

Ok, we have used version 13, and the status channel constantly jumps from a value of 0 to -301058...

[StephenB]

You should be able to FTP into the RT target and find an error log at:
ftp://<ip>/ni-rt/NIVeriStand2010/Custom Devices/XCP and CCP Master

Can you attach that error log?

That error indicates "A timeout occurred waiting for a response from the ECU." Perhaps you're bus is flooded with too much traffic? How many characteristics and measurements do you have added to your system definition? What read rate have you selected for each? Are you using a DAQ list? If so, what rate is that?

I don't recommend adding a whole lot of items to the system definition. You should only add the ones you need within the NI VeriStand engine (aka, passing data to/from a model). Any other items you want to read/write you can do without them actually being in the system definition by using the API or the workspace controls provided by the add on. See this section of the devzone for an explanation.

Also, I'm about to post a v14 of the custom device that has many changes to the engine of the custom device. If we can't figure it out with v13, we should try v14 since there are so many changes.