Increment of pulse gens & measuring xtalk

[Dennis_Knutson]

It can be a benefit to the end user to simply recall a single file to do the setup instead of going through several pages to repeat a test. You would need a couple of extra controls. One that prompts the user to save the current settings and one that would prompt to user to select a file. You could save the settings in an ini file. Functions for reading/writing are on the File I/O>Configuration File VIs palette.

[jjlee]

I cannot figure out how to make a connectioin to two controls (that you mentioned) together.

The idea is to come up with a user prompt for "Recalling Config. File" (OK and CANCEL buttons) for loading instruments configuration files.

for OK selection, it will open up a window prompt for a file selection.

for CANCEL selection, it will ask a user to set up aggressor parameters in tab control.

Do I need to have long enough delay so that  this initial Q&A session occurs before the setup actually gets started(???)

Message Edited by jjlee on 10-12-2005 03:15 PM

[Dennis_Knutson]

What you've added won't work at all. What I would suggest is that you look at the shipping examples for the event structure and implement that. You could add Boolean controls called Load Config, Save Config, Run, and Stop. In the Load Config event, you would use a File Dialog function to get the name of the config file, load the settings for each instrument from the file, and write those values to local variables of your instrument parameters. In the Save Config event, you would read the current settings from the instrument controls, use a file dialog to get the name of the file, and then write them. In the Run event, you would basically put the code that you have now. Finally, the Stop event would stop the entire program.

Right now, you have no datalow with your pop-up dialog, the config file reads, and the execution of your instrument program so you can't predict what will happen when and in what order.

[jjlee]

Thanks for your help.

I have done something like this, but I am not sure this is the correct approach.

How can I do the save config event? Is this part of one event structure?

[Dennis_Knutson]

Well, you haven't added an event and your dialog and read/write of the config file is all wrong. What I had in mind was something like the attachment. I only did two tabs for two instruments and did not add the common settings or the settings for the 8648. To add the settings for the additional 8133's, all that you should have to do is expand the string array that defines the sections in the load and save events. To add the 8648 and common settings, you just need to add additional read/write functions in the appropriate events and pass them to the run event.

[jjlee]

Well, unfortunately, my LV base package does not the event structure that you mentioned. (It looks pretty nice though!)

Thank you!

[Dennis_Knutson]

Ugh. I don't know how anyone can get by with just the base package. Anyway, you can still do something similar with polling. This is the way it was done before the event structure and for base package users. I the attachment, I used a type of state machine. You certainly can use something simpler but I though you might want to look at another architecure.

[jjlee]

It looks much simpler with using 'Event Structure' than 'state machine.' (I am a newbie without too much LV programming experience)

Is there any known problem/issue with using Event structure in the base package?  Is it a good idea to upgrade to Full version?

[Dennis_Knutson]

If you have the base package, I think all that you can do is run an event program that was created with the full version. You can't edit the events. Remember that the event structure is kind of new (introduced with version 6.1) and an awful lot of programs have been written without it. While it does make a lot of things simpler, you should be able to write what you need for this application without it. I personally think the full version is more than worth the upgrade cost with all of the analysis tools but this is stuff that I use on a regular basis. You'll have to look at all of the additioanl features and decide for yourself.

[jjlee]

I am not sure how to group the parameters into a cluster like the 'pulse setting' so that I can simplify before making all parameters  flying over each event structure...(messy!)

For adding more aggressors, I have added more tabs and expanded on 'timeout' event. Is this correct way to do it?