Engine Simulation Custom Device Feedback

[StephenB]

See here:

http://www.ni.com/white-paper/11135/en#toc2

You probably installed LabVIEW after you installed NI VeriStand. Therefore the NI VeriStand installer never had the opportunity to detect LabVIEW and add its extensions. I suggest going to Control Panel -> Add/Remove Software -> NI Software -> NI VeriStand 2012 -> Modify.

Then in the screenshot shown at that link, make sure all the LabVIEW support is added

[jamesy]

Great built the model ok. Can you recommend a Model run rate ??

I'm guessing the model should run as fast as the information is streamimg in from the FPGA.

james

[StephenB]

Yeah just set the decimation to 1, therefore it runs every iteration as the main NIVS loop.

There will be a 1 tic delay as the data goes through the model unless you go to the controller page and change to low latency mode:

http://zone.ni.com/reference/en-XX/help/372846F-01/veristand/pcl_modes_models/

[jamesy]

When i import the model and then hit ok i get the following error:

james

[StephenB]

Odd.... haven't seen that before.

Did you follow the insturctions I placed on the front panel of the VI before compiling the model? Make sure you hit save after following those instructions.

Can you attach the model here?

[jamesy]

the second angles out box never goes white when i type 0.

[jamesy]

Stephen,

I restarted my PC and did a rebuild. Looks good.

I think i have to select "segment into scalar channels" otherwise i just get one inport and one outport.

I'm guessing now i can use mapping and do not need any calculated channels ??

James

[jamesy]

Hi Stephen,

After looking more closely at the veristand actuator angles i notice that they all reference cylinder 1. Unfortunately i have to scale each veristand actuator value by an additional offset given its delta from cylinder 1.

My ECU cylinder values reference TDC in that particular cylinder. This is much easier to understand.

So my conversion is:

cyl 1 +450 = cyl 2
cyl 1 +90  = cyl 3
cyl 1 +180 = cyl 4
cyl 1 +270 = cyl 5
cyl 1 +360 = cyl 6
cyl 1 +540 = cyl 7
cyl 1 +630 = cyl 8

if the angles goes greater than 720 then i must - 720.

Then i start the angle conversion as before to convert to +/- 360.

I could once again use calculated channels but then why use a model at all.

So I created the model attached. ( modifiying the one you created)

When i added the model into veristand i noticed that i had 24 model inputs and outputs per cylinder. ( i only set 4 per cylinder in labview ) I did set the default as instructed but the array was no longer greyed out. Perhaps it remembered the last time i set it to 24??

I also notice that with this model installed ( even though its not connected to anything) The veristand GUI is slower. I enter a value like 500 rpm in the workspace and it jumps to 0 then creeps up to 500. There is a delay from setting a value to seeing it on the HIL. Perhaps theres something major wrong with the model that slows Veristand??

My Graph of crank and cam in the workspace now looks like it has some delay.

James.

[StephenB]

yeah the arrays are enormous and there are 16 of them set to size of 24. Thats 384 items. I dont think you need that many. probably just 2 each? (start angle, end angle).

Right click each one and go to data operations -> empty array

Then set their size just like did before.

Or you could do this for just one of the arrays and copy it, instead of clicking on each

[StephenB]

James,

another approach that might be better, is to have the angles for each of your 8 cylinders right inside your FPGA. For example you could modify your APU loop to have 1 APU per cylinder so you have an angle value for each, then use those values as the angle references for the events.

The APU has an input for start angle. So just set that to the offset you need for each cylinder.

To make this exactly clear, I made a real quick screen capture:

http://screencast.com/t/pRRytI3J4K

Then you use the same model math for each angle since they are already cylinder correct coming from the FPGA.