02-08-2011 10:17 PM
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 firstname.lastname@example.org I can provide this to you when it's available.
03-28-2011 10:58 AM - edited 03-28-2011 11:00 AM
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.lvlibroject Window.vi >> NI_VS Workspace ExecutionAPI.lvlib:NI VeriStand - Connect to System.vi
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.lvlibpen 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???
03-28-2011 11:07 AM
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-simula
10-17-2011 03:22 AM
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.
01-21-2012 10:54 AM
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://decibel.ni.com/content/docs/DOC-19122
that will implement all the model running and fpga interfacing rt code for you.
01-23-2012 05:03 AM
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
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 1st 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
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,
01-23-2012 11:27 AM
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.
My questions/comments to you: