Engine Simulation Toolkit Feedback

[StephenB]

Welcome to the Engine Simulation Toolkit feedback forum. Please use this discussion to ask questions, get support, or provide feedback.

[jarm.woo]

stephen, when i run the ni_lib_engine_simulation_toolkit_(est)-1.0.0.33, it popups the figure as shown below:

my labview version is 13.0.1f3 , is it the problem with this version of labview?

and I also want to know whether if a c MODUL like 9401,9263 or something like that supports this toolkit.

which R serial FPGA board is supported by this toolkit? all of them?

消息编辑者为：jarm.woo

[StephenB]

Hello,

you need VI package manager 2014 or later to install the package. Inside VI package manager go to help > check for updates.

the toolkit has only one specific IO requirement: The

-digital output used by "digital pattern generation" and "directional speed sensor simulation" must be high speed.

[timviola]

This looks great Stephen, I'm very excited to get started.

[StephenB]

Great! Thanks for posting

I just got back in town from a work trip so I haven't had a chance to read your email yet. I will get to it next week hopefully.

[jarm.woo]

stephen, why do i get the following dialog when i  want to open the RT driver vi?

do i miss installing somthing toolkit?

"The

-digital output used by "digital pattern generation" and "directional speed sensor simulation" must be high speed. " do you mean this function only supported by NI -940x except 947x in cRIO platform?

[StephenB]

Hello,

To directly answer your questions:

1. Yes you are missing the item linked the the "Open Source" section of NI Engine Simulation Toolkit for NI VeriStand
2. Any DIO module that can operate in a single cycle timed loop in the FPGA. For example the 9401 would work, but the 9403 would not.

I have a question for you: Why are you opening the source of the custom device? There is no reason to open the source if you do not plan to make changes to the features of the custom device... which would be  uncommon.

To simply use the Engine Simulation Toolkit, do not open the custom device code in LabVIEW. Instead follow these steps:

1. Download the zip file attached to the page with 'built' in the name (at this time named: Engine Simulation Toolkit NIVS 2013 v1.0.0 Built.zip)
2. Unzip the contents
3. Close NI VeriStand
4. Open the readme.rtf file and follow the instructions to install it
5. Open NI VeriStand
6. Open an existing or create a new project
7. Open the system definition
8. Right click custom devices and select National Instruments -> Engine Simulation Toolkit
9. Use the browse button to select a bitfile either you have built yourself or someone has provided for you. You can select the example bitfile included in the zip file if you want to explore the functionality of the custom device while you wait for your personal bitfile.

To create a bitfile:

1. Download the vip file attached to the page.
2. Install it with VI Package Manager 2014 or later
3. After installing, click 'examples' to navigate to the examples provided with the VI package
4. Open the examples to see how the FPGA IP is put together
5. Use the information from the example to create your own bitfile for your specific needs on your specific FPGA target

I really hope that helps. Have a great day!

[NFT]

Hi Stephen,

I saw the demo for this at NIWeek last week, and I'd love to test it out with some of our systems. Unfortunately, I'm having a problem with the configuration.

I'm trying to build a digital pattern that looks like this:

I think it can be done, but I'm having trouble working the add/remove pulse controls. I think the problem is that the selection mode in the list controls is set to "1 Item" instead of "0 or 1 Item", which means to add another item I need to leave the page, which results in Error 1149 for some reason. Then upon returning to the page, it looks like my configuration hasn't been correctly stored/loaded. I'd change it myself, but I'm unable to build the custom device since I appear to be missing some OpenG libraries that I don't believe I can install due to company policies.

[StephenB]

Hi NFT,

That's great that you saw it at NI week and are trying it out!

Thanks for the feedback. That page can be complicated to use. Sorry you're running into issues. I haven't seen error 1149 before, can you show me that error and exactly how to get it?

The reason you cannot add another tooth is because you need to move the cursor after adding the first tooth.

However, I just found an issue adding pulses in the -360 to 0 range... I'm looking into it now.

[NFT]

I just opened up the system definition file again and I'm no longer getting that error. I'm not exactly sure what initially happened to cause it, but I would get an error popup any time I was on the Digital Patterns page and selected a different item from the system tree.

Originally, I didn't understand what you meant by "move the cursor", but I think I might understand now. I'm still not sure I fully understand the interface, but I'm having a bit better luck now.