Engine Simulation Toolkit Feedback

[User002]

Nicopsa,

I developed the O2 sensor simulation.  What kind of sensor are you looking to simulate?  Depending on what it is, there is a custom device that does that (with some FPGA code).  We were considering rolling it into the engine sim cusom device, but for now it's separate.  It can be found here: https://github.com/NIVeriStandAdd-Ons/UEGO-Custom-Device

This_is_my_alias_,

What are the errors you get now when you try to deploy?

Thanks,

Andrew

[Joel-P]

Hello ikc,

Yes, those steps are correct to use the Engine Simulation Toolkit and Custom Device.

One thing that I want to explain, the Crank Angle is a numeric value that tells you what degree the simulated engine is at. The Connector0/DI0 is a digital line that will output a pulse each time the simulated engine reaches specific points based on the profile in the Custom Device. I want to make it clear that the output of Connector0/DIO0 is not a numeric value, and that it is a digital pulse train that simulates a Hall Effect Crank Sensor Waveform.

This_is_my_alias_

The Add Digital Pattern button is greyed out when the custom device does not see any more Digital Pattern Generations on the compiled bitfile. It is specifically looking for the Type Def controls that are used for the Digital Pattern Generation VI's, and these controls Must be named "load input.[Any Name]", "settings.[Any Name]", and "input.[Any Name]" where you can substitute anything for [Any Name].

I would recommend that you look at the Everything.vi which is included in the Engine Simulation Toolkit Examples.lvproj which is located here: C:\Program Files (x86)\National Instruments\LabVIEW 2015\examples\NI\Engine Simulation Toolkit (EST)

I would double check that you recompiled your bitfile after making the changes to the FPGA VI, and then that you pressed the Reload Bitfile button in the custom device.

As a quick test, you could add another Engine Simulation Toolkit Custom Device to your System Definition, and then point that to a compiled bitfile from the Everything VI. This should allow you to add up to 4 Digital Pattern Generators.

Best Regards,

Joel

[Nicopsa]

Hi HandyAndy,

Thanks for your answer, we are using an LSU Wide band sensor, from Bosh. I took a look on your LabVIEW model, I think it could match with my request. However, I would like to get more information about it. Should I send you a private message ? (my questions don't have any bond with the EST discussion)

[User002]

Nicopsa,

Send me a private message.  The UEGO sensor sim is in interesting state right now, so I want to find out more so we can support you in the way that makes sense.

Thanks,

Andrew

[HervéM]

Hello,

I try to use the directional speed sensor from your toolkit Engine Simulation.

I want a 60-teeth-signal with two mossing teeth; teeth must be 50µs impulssion for the forward. That's why I use paremeter in inclose picture.

In the bitfile, I have only change the digital output to an analog output. You can see the code in inclose picture.

With a speed request of 1000RPM, I have the signal in the last inclose picture.

The signal doesn't have any 50µs impulsion and no missing tooth.

Can you tell me what is going on with my signal ?

Best regard,

Hervé

[User002]

Hi HerveM,

I see you are using an analog output for the digital signal.  The digital I/O ports can run much faster (which is why they run in a Timed Loop rather than a regular while loop) and the code in that block runs with that assumption.  Since it expects to be executing faster, it isn't running well.

Can you use a digital line, and turn that into a Timed Loop rather than a while loop?  Perhaps use some signal conditioning to adjust the voltage levels?  That is typically better because the analog lines can't meet most current requirements for these applications.

If you need to use the analog line, it might be better to use the Analog Replay feature instead, since that code was made to run in a regular while loop.

Thanks,

Andrew

[Nicopsa]

Hello,

We are working on the knock simulation sensor and we would like to know which are the good values to make it work fine. Currently, we always get a knock default when we try some values.

Could you help us ?

[HervéM]

Hi Handy,

Thank you for this information, it's work fine with a digital output and a coditioner.

Regard,

Hervé

[Joel-P]

Hello Nicopsa,

I am a little confused about what you are seeing. Are you having trouble entering values in the system definition, or are you always getting a knock output on the analog line?

If you are having trouble modifying the values in the system definition, could you explain which values you are trying to write to?

Once you add a Knock Sensor you also have to add a cylinder to that Knock Sensor, then you can configure the Trigger angle, probability, and amplitude for that cylinder under the Knock Sensor.

Best Regards,

Joel

[Holt]

I'm using the EST to simulate a V10 engine in 2014.  I noticed there is a weird artifact that appears when you add the 10th injection capture.  It must have something to do with the custom device parsing the FPGA controls and having both "capture.Event Inj 1.Event 1" and "capture.Event Inj 10.Event 10" causes some confusion.  Here is a pic of the artifact.