Engine Simulation Toolkit Feedback

[tasso_bot]

Hi,

Is available also an example of FPGA source code?

From the link: https://github.com/NIVeriStandAdd-Ons/Engine-Simulation-Toolkit-Custom-Device, i have found only the custom device source code.

thanks,

Marco

[ikc]

Hi Marco,

You can find an example project in "C:\Program Files (x86)\National Instruments\LabVIEW 2015\examples\NI\Engine Simulation Toolkit (EST)\Example\"

JL

[Fefo]

Hi all,

I've managed to have the EST running with a few APUs and analog generations but I'm having some issues with the directional speed sensor generation. What I've done is to create a custom bitfile which has no digital pattern generations but has a few speed sensors.

Now, I think I understand that directional speed sensors require digital patterns (although they don't seem to be connected in the bitfile) but I still have some questions:

1. Do I really need digital patterns to run speed sensors?
2. If so, do I only need the 'load input' of the digital pattern or do I also need the streaming loop?
3. Can I have multiple pattern generators with the same loaded pattern but with different APUs? Or do I need one loading loop for each generation loop?

Is there some sort of user manual for the EST?

Thank you all and thanks for the good job

[cbacchiani]

Hi all, I'm Fefo's colleague.

So far we decided to settle with using a digital pattern instead of the speed sensor, so to avoid that problem.

Now the thing is we're trying to set up multiple digital patterns (4), each with its own APU, but we can only manage to get the output of the first. I attach an example with 2 channels, of which only the first works.

My first hyphothesis was about wrong labeling of the blocks, but I can't find the mistake.

Another possibility is the fact that the outputs are managed in separate loops, but since I'm using an R module that shouldn't be an issue.

I basically copy-pasted the first block, is there something I should change or rename?

---

Update: It seems that connecting both digital patterns to a single APU gets them working. The issue is we need the patterns to be independent on each other, therefore we need several independent APUs.

Is there any way to get it to work?

---

Update #2: Looking inside the signals that the Custom Device engine sends to the FPGA, I've noticed that the Settings.Enable boolean field is always equal to FALSE. We're looking inside the engine code why is that.

[Yusuke.T]

Hi, is there the version of NI VeriStand 2016?

I know there is a source code on Github but "File Formats.lvlibp" is missing.

I have the file on

"C:\Users\Public\Documents\National Instruments\NI VeriStand 2015\Custom Devices\Engine Simulation Toolkit"

but LabVIEW said that the version compatibility of the file is incorrect, it is developed on LabVIEW 2015.

Best Regards,

[cbacchiani]

It seems we have found a bug which was preventing us from using multiple APUs. Basically if the signal generation of each APU is defined within the APU's page in the custom device settings, it won't work. What you have to do in order to have all signals working is to define all generations within the first APU page, because the FPGA will link all of them to the proper APU anyways.

[Jiri_K]

First build classes at https://github.com/NIVeriStandAdd-Ons/Engine-Simulation-Toolkit-Custom-Device/tree/master/Source/Fil...

And than main project....

[Yusuke.T]

Hi Jiri, thank you so much!!

Best,

[cbacchiani]

I think I have stumbled over a bug in the analog replay function. If I set an FPGA memory size of 8192 (half of the default) for the samples, and I accordingly set that value in the custom device page, I noticed that the output streaming frequency is double than what is supposed to be.

Also, this happens only if I use the crank angle as reference, whereas I get the right frequency using cycle angle as reference. This is likely due to the block in the attached image, where the register read block points to the cycle angle even though the 'CycleAngle' boolean is false.

[Yusuke.T]

If you want to build this add-on under LabVIEW Japanese environment, Analog Replay may return error "-2563" or other TDMS storage error. It's caused by localization problem.

To fix it, please look at

Engine Simulation Toolkit Custom Device (EST).lvproj --> EST System Explorer.lvlib --> Page helpers --> Analog Replay --> File Load Dialog.vi

In the case structure I attached, Get Channel Groups.vi is incorrectly coded ("File" isn't correct. "ファイル" in Japanese should be). Please fix those of string.