topic 回复： Automotive Engine Simulation Library for HIL in Components

Automotive Engine Simulation Library for HIL

DarylE — Wed, 23 Jul 2025 18:44:55 GMT

Please provide feedback, comments, and questions on the
Automotive Engine Simulation (AES) Library for HIL,

HIL Automotive Engine Simulation Reference Example,

and NI VeriStand Add-on - Automotive Engine Simulation

in this thread

Message Edited by Daryl E on 11-03-2009 02:24 PM

Re: Automotive Engine Simulation Library for HIL

andrepereira — Fri, 15 Jan 2010 16:33:19 GMT

Hi, I'm starting to work with the AES Add-on for Veristand and I need to modify the custom device in order to use a different R Series model, the PXI-7851R. I've downloaded the reference example and I have compiled the FPGA VI to the new target. Now, I need some help on how to integrate this modification to the custom device with no problems.

Any help is appreciated

Andre Pereira

Field Sales

NI-Brazil

Re: Automotive Engine Simulation Library for HIL

griffindore — Fri, 15 Jan 2010 18:39:54 GMT

Hi Andre,

The custom device was created with the idea that others may wish to extend it to use a variety of different FPGAs. As you open the source code for the Engine Simulation Custom Device, you'll find a Contros Virtual Folder under the Engine Simulation Custom Device.lvlib. Within this folder, you'll find a TypeDef for FPGA Target.ctl.

This TypeDef is an Enum that allows you to select which FPGA target you wish to run the custom device on. The first step will be to add an additional item to this Enum for your FPGA Target (i.e. 7851R). At this point, you'll be able to select the new FPGA target on the Main Page of the custom device (Engine Simulation Main Page.vi).

If you then open the Engine Simulation RT Driver VI.v, you'll see that the FPGA calls are all wrapped up in SubVIs (Set FPGA Config, Run FPGA, Set FPGA Crank Cam Throttle, Set FPGA Outputs, Get FPGA Inputs, and Close FPGA). In Set FPGA Config.vi you'll find that a case structure will execute the Open FPGA VI depending on which FPGA was selected in the FPGA Target enum. At that point, the reference is written to a cluster that contains an FPGA reference for every FPGA Target type that was included in the FPGA Target enum.

In order to adapt the custom device to your 7851,

You will have to add a case in Set FPGA Config.vi for the 7851. I suggest duplicating one of the pre-existing cases.
Then you can configure the Open FPGA Reference to use the bitfile created for your 7851. I suggest binding it to a TypeDef.
1. Note that there's a bug in #179896 LabVIEW 2009 that will cause the TypeDef created by the Open FPGA Reference to be empty and unusable. In order to work-around this issue, point the Open FPGA Reference node to an already-existing .ctl that has a control on its front panel. It's important that a control already exist within the .ctl file.
Then you will need to modify the FPGA Ref Cluster.ctl TypeDef to include the TypeDef for the 7851 Reference.
Within the Set FPGA Config.vi's case for the 7851, make sure you connect the FPGA Reference to the new reference for the 7851 within the FPGA Ref Cluster.
Modify the Run FPGA, Set FPGA Crank Cam Throttle, Set FPGA Outputs, Get FPGA Inputs, and Close FPGA VIs to add cases for the 7851.

Figure: Set FPGA Config.vi

Regards,

Re: Automotive Engine Simulation Library for HIL

griffindore — Fri, 15 Jan 2010 18:41:31 GMT

I forgot to add one last final step:

You must then build the Configuration and Engine Build Spefications found in the project.

Re: Automotive Engine Simulation Library for HIL

zazamee — Thu, 29 Jul 2010 07:38:50 GMT

I'm from PTTPLC. Could you give us any idea to simulate crank and cam in variable reluctance form ?

Or do you have any plan to develop them to your libraries ? Our engine have 36-2 crank and n+1 cam

(4 piston then 5 cam) as in attached. Thank you.

Shinapat Rhienprayoon

PTTPLC

shinapat.r@pttplc.com

Re: Automotive Engine Simulation Library for HIL

griffindore — Tue, 10 Aug 2010 16:55:52 GMT

Hi Shinapat,

I do have plans to develop variable reluctance simulation for crank. Unfortunately I do not have anything currently ready.

I can certainly help with some ideas though. This solution isn't flexible in a general use case which is the reason why I haven't implemented it yet, but you could create look-up tables (LUT 1D) from those waveforms captured in your screenshot and then cycle through the look-up tables according to the crank angle (0-360) for crank simulation and adjusted crank angle (0-720) for cam simulation.

I'd like to do something similar to the above suggestion, except just have one waveform that I cycle through for each tooth. This is much more complex because I'd have to keep track of where my teeth are in relation to the crank angle and then correspond the tooth to a waveform instead of corresponding the entire crank or cam to a waveform.

My understanding is that most people typically only care about the 0V crossing between peak and valley so you could also rig up the current implementation of Hall-Effect sensor simulation to output between a positive and negative voltage. A VR Sensor also crosses 0V at the middle of a tooth, so the Hall-Effect output would also need to be phase shifted to account for this difference. Of course this won't provide the nice sinusoidal looking output, but it ultimately depends on what the ECU is actually checking.

If you'd like to discuss this in more detail, feel free to email me at mike.lyons@ni.com.

Regards,

Re: Automotive Engine Simulation Library for HIL

marty102 — Tue, 21 Sep 2010 10:15:02 GMT

I have a litte Problem with the behaviour of the example.

I used it as it is, but removed everything but the cam/crk generation.

As soon I press the start button it is deployed and visually running, but at the output of the 9401 nothing happens.

Then I press stop, and start it again ... nice, it is running an generating a nice crk/cam Signal.

When I disconnect it from the power line, it is redeployed and again needs 2 times to start it up,

from then its working without any problem until the next power off/on.

Why this strange behaviour?

I added a 2sec delay to the fpga to give the cam-fifo a little mit more time to fill, but sadly this didn`t help.

Thanks a lot

Regards

Martin

Re: Automotive Engine Simulation Library for HIL

griffindore — Mon, 01 Nov 2010 16:36:54 GMT

Hi Martin,

I apologize for the delayed reply. It's possible that you're needing to re-deploy twice after the power cycle because the FPGA is not having its reference closed properly. I would recommend properly stopping the application and restarting it without a power on/off to see if you still get the same behavior. I did not experience anything like this in my testing. This sounds like an issue with LabVIEW FPGA/Real-Time and not specific to the reference example code so I would recommend contacting your local support resource.

I would strongly recommend against the 2 sec delay you added to the cam FIFO loop. This could cause problematic behavior since the crank will be running for those 2 seconds. The code was designed to prime the FIFO before running the FPGA. Also the FIFO will be in the read state until it receives all the expected cam angles.

Regards,

Re: Automotive Engine Simulation Library for HIL

griffindore — Mon, 01 Nov 2010 16:38:15 GMT

This is a notification that the device connections for the NI 9474 module for both the reference example and the NI VeriStand custom device were incorrect. Pin 4 is actually populated with Cam4Out and pins 5-7 are populated with 12VPWMOut1-3.

Regards,

回复： Automotive Engine Simulation Library for HIL

molezhou — Wed, 09 Feb 2011 02:43:04 GMT

Excuse me, I've just downloaded the custom device lib of Automotive Engine simulation. I found it should support Veristand 2009 and I wonder whether it is still compatible in Veristand 2010 or is there any methed that we might use the lib in Veristand 2010?

回复： Automotive Engine Simulation Library for HIL

griffindore — Wed, 09 Feb 2011 04:17:29 GMT

The version posted is for NI VeriStand 2009. Each version of NI VeriStand is bound to the corresponding version of LabVIEW. Therefore, if you'd like to upgrade it to VeriStand 2010, you can open the source code in LabVIEW 2010 and rebuild the source distributions. NI VeriStand 2010 will mutate the XML. When opening the source code, you will notice that the FPGA references that are bound to type defs use absolute paths so those will need to be updated.

You're in luck because the custom device was very recently upgraded to NI VeriStand 2010 and is currently available at ftp://ftp.ni.com/outgoing/Engine Simulation.zip. This file will only be available on the FTP for a very short time (few days). I will not be posting it online because I am currently working on a new paradigm for the Engine Simulation Custom Device for NI VeriStand 2010 and beyond. I am hoping to provide a beta version of the new custom device to interested customers within the next week or two. If you email me at mike.lyons@ni.com I can provide this to you when it's available.

Regads,

回复： Automotive Engine Simulation Library for HIL

Elvio — Mon, 28 Mar 2011 16:00:33 GMT

Hi everybody,

I'm working with Engine Simulation Cutom Device but I'm using 2010 version of Veristand so I've done the rebuild for source code. It seems to work but when I try deployng the project to my PXI System this error appears:

Error 1003 occurred at Project Window.lvlib:Project Window.vi >> NI_VS Workspace ExecutionAPI.lvlib:NI VeriStand - Connect to System.vi

Possible reason(s):

LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Select File>>Open to open the VI and then verify that you are able to run it.

=========================

NI VeriStand: Open VI Reference in NI VeriStand Engine.lvlib:Open Custom Device Driver VI Reference.vi->NI VeriStand Engine.lvlib:Launch Asynchronous Custom Device.vi->NI VeriStand Engine.lvlib:VeriStand Engine State Machine.vi->NI VeriStand Engine.lvlib:VeriStand Engine.vi->NI VeriStand Engine.lvlib:VeriStand Engine Wrapper (RT).vi<APPEND>

VI Path: c:\ni-rt\VeriStand\Custom Devices\Engine Simulation\Engine Simulation Engine.llb\Engine Simulation RT Driver VI.vi

Error 1003 occurred at Project Window.lvlib:Project Window.vi >> NI_VS Workspace ExecutionAPI.lvlib:NI VeriStand - Connect to System.vi
Possible reason(s):
LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Select File>>Open to open the VI and then verify that you are able to run it.=========================NI VeriStand: Open VI Reference in NI VeriStand Engine.lvlib:Open Custom Device Driver VI Reference.vi->NI VeriStand Engine.lvlib:Launch Asynchronous Custom Device.vi->NI VeriStand Engine.lvlib:VeriStand Engine State Machine.vi->NI VeriStand Engine.lvlib:VeriStand Engine.vi->NI VeriStand Engine.lvlib:VeriStand Engine Wrapper (RT).vi<APPEND>VI Path: c:\ni-rt\VeriStand\Custom Devices\Engine Simulation\Engine Simulation Engine.llb\Engine Simulation RT Driver VI.vi

So I opened the indicated library Engine Simulation Engine.llb and I've found this error in the VI Set FPGA Config.vi which is inside the VI indicated as broken Engine Simulation RT Driver VI.vi.

Maybe the problem is about the VI refernce path but it seems to me it's correct.

Can anybody help me???

回复： Automotive Engine Simulation Library for HIL

griffindore — Mon, 28 Mar 2011 16:07:08 GMT

I would expect the problem to be caused by the TypeDefs corresponding to the FPGA References. LabVIEW has some weird pathing problems with that, and I think they are saved as absolute paths. You can update it in the Open FPGA Reference.

I strongly recommend against using the old version of the Engine Simulation Custom Device with NI VeriStand 2010 or newer. You can find a completely revamped and new custom device for Engine Simulation at http://decibel.ni.com/content/groups/engine-simulation-2010-beta. You'll need to request to join the group before getting access to the new custom device.

Regards,

回复： Automotive Engine Simulation Library for HIL

Elvio — Mon, 28 Mar 2011 16:35:50 GMT

Thank you.

Request done.

Re: Automotive Engine Simulation Library for HIL

aksgoel — Mon, 17 Oct 2011 08:22:05 GMT

Hi,

I am trying to use an engine model built in MATLAB along with the AES library for interfacing to build an EMS HIL system. I have tried to use simulink interface toolkit to establish the connection. However I am aiming at running the engine model on the RT controller of PXI.

I am unable to integrate the SIT generated code to my AES library in a way to run both on the same RT controller. Has any one tried this. Or any one knows how to connect the MATLAB model to the AES library in a better way.

Re: Automotive Engine Simulation Library for HIL

StephenB — Wed, 23 Jul 2025 18:45:44 GMT

aksgoel

that is possible and one of the primary goals of this library. However it takes a lot of programming and experience to accomplish this.

instead, I recommend using NI VeriStand with the engine simulation custom device. https://forums.ni.com/t5/NI-VeriStand-Add-Ons-Documents/NI-VeriStand-Add-on-Engine-Simulation-Custom-Device/ta-p/3511370

that will implement all the model running and fpga interfacing rt code for you.

Re: Automotive Engine Simulation Library for HIL

Gaurav_Singla — Mon, 23 Jan 2012 10:26:15 GMT

Hi Stephen,

Re: Automotive Engine Simulation Library for HIL

Gaurav_Singla — Mon, 23 Jan 2012 11:03:22 GMT

Hi Stephen,

I'm Gaurav. I and Vijay have taken over the work started by Akshay Goel. We deployed the Custom Device of Engine Simulation library you had given us and we are able to view the Injecor and ignition start angles in veristand GUI, but we are not able to understand

what is the reference for these angles – is it power TDC or exhaust TDC and whether it is before or after TDC and whether the rotation is clockwise or anticlockwise. For eg , we gave the following inputs-

We entered the injector start angle in our controller to be 378 deg before power TDC.So it generates the injector pulses accordingly, but the output which we are

getting in veristand is 500 deg and 140 deg( it keeps switching between

these values).

We would like to know what is the reference for these angles

1.Before or After Power TDC.

2.Before or After Exhaust TDC.

Does the Crank wheel rotate clockwise or Anti-clockwise?

Following are the inputs to Custom Device GUI

no of teeth :36

no of missing teeth: 2

Pos of missing teeth after TDC : 225( The crank sensor in our engine is situated in such a way that, it detects Power TDC of 1^st cylinder 135 degrees after it detects the missing teeth when the crank is rotating in anticlockwise direction. Therefore the offset for the next Missing Pulse after TDC when it is rotating in the same direction is 225 degrees.).

Also in the labview model it expects 2 values

a.Nteeth.crank.Missingteeth.Offset

b.Nteeth.crank.TDC.Offset

but through veristand we are entering only the offset between missing teeth and

TDC. Will it calculate both these values with the one value we enter in the GUI.

Thanks and regards,

Gaurav

Re: Automotive Engine Simulation Library for HIL

StephenB — Mon, 23 Jan 2012 17:27:01 GMT

Hi Gaurav,

Glad to hear you have been making progress and you can see data inside NI VeriStand. I'll try to answer you questions here, but if I don't answer them clearly... please let me know so we can be sure to resolve this as much as possible.

Angle reference "is it power TDC or exhaust TDC"

The simulation doesn't make a distinction between "power" and "exhaust". It simply simulates the waveforms and captures event inputs... if the waveform is supposed to be "power" or "exhaust" in your application is up to you.

Angle reference "whether it is before or after TDC"

The angles are in reference to angle 0 of the crank/cam... and this custom device considers angle 0 as TDC. So if the pulse is seen from angle 212 to angle 215 your start angle is 212, end angle is 215 and angle duration is 3.

Angle reference "whether the rotation is clockwise or anticlockwise"

The angle simulation starts at 0 and increases to 720 or 360 before rolling over back to 0. The angle simulation is done by the Angle Processing Unit (APU) and the 0-360 degree value is output with the name "APU.Cycle Angle" and the 0-720 value is output with the name "APU.Crank Angle". Wether this is clockwise or anticlockwise is up to you in your application. Just define the teeth with whatever your perspective is. (General note, the 0-720 and 0-360 values are named crank and cam just because that is the general use case.... but you can use these values however you want)

My questions/comments to you:

Check the waveforms with an oscilliscope and make sure they are OK. I've seen issues before where a pull up/down resistor was needed depending on the NI IO used and the ECU.
Check the injector signals with an oscilliscope and make sure they aren't noisy. If they are noisy... use the "# of cycles to filter" input on the event subVI in your FPGA code. The units are "cycles" of the FPGA loop... which goes at 40 MHz so this will be a large value if you want to enable filtering.
I assume you are using the Fully Custom Teeth with the 0-720 degree signal (Default name: Cam) as the reference for your ECUs injectors? I say this because you state your controller is setup to inject at 378 degrees before power TDC. Are you sure this is wired correctly?

Re: Automotive Engine Simulation Library for HIL

StephenB — Mon, 23 Jan 2012 17:42:54 GMT

Correction, I had my nouns backward:

"APU.Cycle Angle" is 0 - 720
"APU.Crank Angle" is 0 - 360