LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Increment of pulse gens & measuring xtalk

Yeah, that's fine. You'll also need to add addtional items in the string arrays for the load and save events. These create the different section names for each instrument. Also, I don't know if you noticed but the example I sent that uses the state machine instead of events has local variables to update the front panel controls after doing a load. You should look at that example and add it to this one.

To group controls into a cluster, you just have to add a cluster control on the front panel, select the controlsyou want, and drag them into the cluster.

Message 31 of 39
(977 Views)
Expanding string arrays for load and save events just showed empty slots....how is this done correctly?
0 Kudos
Message 32 of 39
(967 Views)
The array elements are empty because they haven't been defined. Just type in a new value.
0 Kudos
Message 33 of 39
(965 Views)

Could you please explain more on the "local variables to update the front panel controls after loading event?" I am vague on how to understand your statement.Thanks

0 Kudos
Message 34 of 39
(961 Views)
Look at the example I posted that doesn't use events. In the "Load" case, on the right side of the diagram is a case statement. Inside the case statement are local variables for each of the front panel controls. The data that is read from the file is used to write to the local variables. This is what actually will update the values of the front panel controls. When you add additional front panel controls, you will have to add additional cases and in each case, add the correct local variable. Say you've added VISA Resource 3, Enable/Disable 3, and Pulse Setting 3. Go to case 1 of the case statement and right click and select Duplicate Case. This will create case 2. If you left click on one of the local variables in the new case, you'll get a list of all controls and indicators. Change the VISA Resource 2 to VISA Resource 3, Enable/Disable 2 to Enable/Disable 3, etc. Creating local variables in the first place is very simple. All you have to do is right click on a control or indicator on either the front panel or diagram and select Create>Local Variable.
Message 35 of 39
(959 Views)
Thanks alot!
I think I need to put 8648 controls in load event and passing cluster from no event....
Am I thinking to the right direction?
 
Plz see the attached.
 
0 Kudos
Message 36 of 39
(953 Views)
Yes, I think you've got the right idea. I didn't do all of the controls that you originally had because I just wanted to give you the basic idea and it would have taken too much of my time to do the whole thing. And, by having you do some of the work, you get to better understand what's going on and in the process, improve your skills and that's a good thingSmiley Happy.
Message 37 of 39
(955 Views)

I have added 8648 controls in the "run" event...I wonder if there may be any conflict with the current set up....8648 will need to get set first so that 8133s can be triggered/configured with appropriate setting(s)..please see the modified VI for your comment/recommendation...

 

Thanx

0 Kudos
Message 38 of 39
(943 Views)

It is quite a daunting task to output; 1) crosstalk graph, 2) save measurement data in txt & xls files.... I did download the tds8000 driver and looked at a few example VIs, but do not have a clue where to begin...

I think I need to set the scope before start measuring

Could you provide some guidance how I should approach?

0 Kudos
Message 39 of 39
(926 Views)