Would Signal Hound be willing to build a 32-bit Linux API for a one time engineering fee? We may be interested depending on the one time fee.

Andrew,

I updated the USB 3.0 drivers and it is working now.

Thanks!

I think I figured it out. I noticed the Video Processor units used by Spike was Power and I was using Log in my setup. I changed the Video Processor units in my setup to Power and now the measurements for both CW and 20MHZ noise signal match to within 0.1db.

If I use the 80.0e6 instead of 486111.111, my channel power matches Spike for a CW type signal, but not a 20MHZ White Noise signal. Below are the values from Spike and my computed channel power using both values.
Spike My ChPwr (486) My ChPwr (80.0e6)
CW Signal -51.62 -52.7 -51.6
20MHZ White Noise -51.5 -55.0 -53.9

I found the Embarcadero C++ compiler had a utility called “mkep” to convert a .dll file to a .a file. Now when I link the .a file, there are no unresolved external errors.

We just took delivery of a BB60C unit and I would like to make the same channel power measurement that I am doing with the SA44B. Is the algorithm for computing noise bandwidth of the BB60C different than the SA44B?

AJ,

Thanks for the noise bandwidth information. I now get the same channel power reading as SPIKE.

bbowar

Thanks! The vi in the labview folder runs fine.

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?

[Author]

Posts