Labview drivers for SA44

Hello all,
I wrote some VIs around the SH api, to support both 32 and 64 bit versions of LabView. I hope you will find them useful. It was tested with SA44 on windows 8 64 bit.

Attachments:

You must be logged in to view attached files.

Excellent!!! I will try it out later today. Thank you for sharing this.

Hi,
Would you be willing save this project reverted to 2012 Lab View?

Unfortunately I am unable to update at this time.

Thanks.
John

After unzipping, I had to create a sub-folder, “data”, and move shlv.ini into the folder. After that, it looked pretty good. Nice work!

KBONE, you can also download an evaluation copy of the latest LabView, save as a previous version (e.g. LV 2012), and then fix whatever errors creep in.

“KBONE, you can also download an evaluation copy of the latest LabView, save as a previous version (e.g. LV 2012), and then fix whatever errors creep in.”

And the download is about a bazillion megabytes and I am on a limited data plan. It would be nice if Lior would just make a reverted copy for those of us who don’t have unlimited data.

The .INI file is used in case your installed path is different than the default, or when using 32 bit Labview in a 64 bit system. Attached is the driver for LV2009. It is not tested, since I can’t access LV2009 anymore.

Attachments:

You must be logged in to view attached files.

I just took delivery of 3 USB-SA44B signal hounds. I loaded the Spike software and that works fine. I downloaded the LV2013 zip file to try and control the unit using Labview. When I run the test app, I get an error code 13 from the saGetSerialNumberList (Call Library Function Node). I am running 32 bit version of Windows 7 and 32 bit version of Labview 2013. The path where it is looking is \x86\sa_api.dll. I noticed when I double click on the saGetSerialNumberList block, it shows a path to the dll in \x64\sa_api.dll. I tried changing the path there to x86 but I still get error code 13. Any ideas on what else to try?

Bbowar, you can also look at the simple, less functional Labview example in your C:\Program Files\Signal Hound\Spike\api\sa_series\labview folder. It doesn’t have all of the functionality of Lior’s program, but it might be easier to get running if you are experiencing difficulties.

Thanks! The vi in the labview folder runs fine.

It seems that LV uses the static DLL reference 1st, then the path input.
Attached is an updated driver which corrects this issue. It was tested on a 64bit target.

Attachments:

You must be logged in to view attached files.

Hello,,i have tried to unzip the file ,but when i run tes app2.vi ,,,it says that .INI file is error ? what should i do to run the lab view properly so that it can fetch the data ?
thx
ps : i am currently developing project to Plot Antenna Radiation Pattern that can get data acquisition automatically through lab view

See few posts above, you need to place the .ini file in the \data directory.

I have added the .INI in to C:\Users\LENOVO\Downloads\Signal-hound-LV2013\data
but when i run the tes app2.vi it shows this error ?

thanks Lior

Attachments:

You must be logged in to view attached files.

You need an internet connection for downloading the calibration files.

Yes sir, i do have downloaded the cal file,and run the setup.cal
but,yet it doesn’t still solve this,,,i have checked the firewall setting and allow the app..but yet it doesn’t solve it anyway..

any help would be highly appreciated sir. *i am currently a student

thanks Lior,

Attachments:

You must be logged in to view attached files.

Hello Lior,,

My problem has solved, but from your labview file, is that possible to change the mode operation —> Real Time or i need to adjust the labview function again ?

Thanks Lior,

Attachments:

You must be logged in to view attached files.

You can change it to real time, I have not tested it. I implemented only the functions I needed. Make sure your software can handle such data, a 250KHz sweep once every 32mSec.

I have changed it to real time but it says “Invalid parameter error ”
How do i fixed this ?

thanks in advanced ,lior

Check your span and RBW settings. There are limits in RT mode. Also, check the API manual for more information.

[Author]

Posts