LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Agilent 89601A labview drivers

Hi Doug,
Not quite sure what you meant by upload didn't stick, because it seems like I can download the files.  In any case, here they are zipped.

Yi Y.
Applications Engineer
National Instruments
http://www.ni.com/support
0 Kudos
Message 21 of 39
(2,921 Views)

Thanks Yi.  Sparky's written a driver for the 89601 software.  He tried to upload it to the Instrument Driver Network, but it hasn't shown up there yet.

 

Doug

0 Kudos
Message 22 of 39
(2,911 Views)
Oops, I mistake. We'll wait for Doug.

Yi Y.
Applications Engineer
National Instruments
http://www.ni.com/support
0 Kudos
Message 23 of 39
(2,905 Views)
here's what I got.

I found it easier to configure the 89600 software, save this configuration and recall it.  If you look in this config file it is huge, every possibile parameter is saved and pushed back into the app when recalled.  This insures that every test has the same base configuration any time it is run.  There are way to many parameters to bother creating graphical interface controlers for.

As you cann see in the junk yard programs, what I do is setup the MXA/89600 to record a chunck of data given some timing signal as the start of time (or your known test pattern).  This avoids needing to create a searcher in labview, to find the start of the test patter, and also adjust the record overlap.  Thats somehting that gets nasty, you might want to talk with Agilent feild engineer about what it is and how to figure out what to set it to.  They explained it to me but that only let me realize i didn't want to mess with it if I could aviod it.  I put a note about this field in the main vi tree:
About using overlap in the search function of the 89600 [recorded] buffer:
Say your packet is 720 ms (data is conitguous though not bursty), and the maxium
capture of the analyzer is 853.33333ms
And you tirggered the record right at the begining of your buffer, then to be sure you
don't search through previous portions of your 720ms packet you set your search to:
(853.33333-720)/853.33333 = 15.625% overlap, the 89600 will search right form the
end of your first packet and find the next one.

If you don't have time 0 at the begining of the record, each time you step to the next chunk of buffer you might not get enough new data (based on the overlap) to dump the specified packet length.  The 89600 does wierd things when the overlap didn't let in enough data from the recording (bogus demoded bits) even though it is a recording and there is data there (the sliding window is really a separate buffer duped from the recorded data based on overlap and search length).  This is all so you can capture a contigous data signal.

Enough of that feel free to post questions about this when it comes up.

Message Edited by Sparky on 09-10-2007 02:33 PM

Message Edited by Sparky on 09-10-2007 02:37 PM

Message Edited by Sparky on 09-10-2007 02:37 PM

0 Kudos
Message 24 of 39
(2,897 Views)

THANKS SPARKY!!  Just what I was looking for.  If I make any additions/changes, I'll post them.

 

Doug

0 Kudos
Message 25 of 39
(2,882 Views)

calibration code for agilent 89600

Use ESG signal generater & Power meter

such as E4438C and E4418A+E4412A

 

scv_lhc@hotmail.com

Beijing Orient Institude of Measurement & Test

 

0 Kudos
Message 26 of 39
(2,524 Views)

I am trying to create a 802.11n test suite with the 89600 software. When I run the open application software it runs without error but the application does not open. The same thing happens when I run the hello_world vi that install with the agilent software. Can someone confirm that the automation open will actually open the 89600 software. If this works for you can you tell me the active x class that the reference points to. I would appreciate any help.

 

Terrill

0 Kudos
Message 27 of 39
(2,190 Views)

If you are running on an XSA series spectrum analyzer you must have the Launch XSA software up, and it must be idle (as in the spectrum analyzer should not be running).  The SA will take SCPI commands but I'm not sure if there is one to turn it off so that the launch application is in control.  If you call to the 89601A with out the Launch application up it will run bit in simulated hardware,  the LSA serves the hardware deck to the system (and network you can hijack the hardware with the 89601A on any other pc).

 

One thing to check is if the function that opens a session with the 89601A has application visible set to true.  I thought one could run it as 'not visible' and save on some CPU load but it doesn't work properly (no data comes back from other function calls that are looking for things like dmeod bits).  If you check the task manager while your program is running and see the VSA.... Running its probably running in 'not visible' mode.

 

So short answer is yes LV can invoke the 89601A software.  Takes a long time to run though (checks license, checks hardware, loads add on modules).

0 Kudos
Message 28 of 39
(2,168 Views)

I attached the latest open and close vi's I use in the previous post.  You can get away with not closing the visa session, but in one test run where I have to check several test patterns, the core tx tester vi was not closing the visa session while always calling the open, and that causes the MXA/Windows to blue screen of death crash.  So close the session.  I have another vi to actually close the 89600 but as eluded to before that requires it to run through its startup procedure of counting all the electrons in the sun.

0 Kudos
Message 29 of 39
(2,162 Views)

put. Thank you for your input. I found my problem just now. I do not have a license on my office pc and was selecting demo when the license request came up. I activated the 14 day trial licnese and now everything works. Thanks again.

 

Terrill

0 Kudos
Message 30 of 39
(2,157 Views)