Search Results for 'api'

Hi.
We are using a SA44B as a backend in our educational radio telescope interferometer, operating at 1.4 GHz. The SA44B is controlled from a Linux PC, using CUSBSA API and we have found that the spectrum has a noise that has a sinusoid shape, with ~200 kHz between peaks. We first blamed our amplifiers but after testing with a noise generator, we found that it is the SA44 who produces this effect which can be also seen with a 50 ohm load at the input. Funny thing is that we don´t see this when using Spike. We have tried with different BW and FFT values but no change. Any hint on what to do to eliminate the noise? (image attached).
Regards
Juan

Attachments:

You must be logged in to view attached files.

I am trying to write some API software for the SA44B using LabView. I would like to automate reference level changes so that it can actively change during signal sweeping.

I currently have a loop that collects my sweep information. It outputs this info into a graph, and collects the maximum value. This maximum value is then used with case statements to determine if the reference level should be changed. I’m using the saConfigLevel function to change the reference level. I know the function works because I can set the reference level at the beginning of execution. However, when I use it inside the loop and case statements, it correctly updates the indicator used to see the current reference level, but fails to change the reference level for the device itself.

Any ideas are welcome.
Thanks

[Andrew]

Hello oogieoogieful,

Just to clarify, I though because you were using the SHAPISlowPlot.m file you would be using the and SA44/SA124. I am now under the impression that you have retrofitted it to call the BB60 API instead of the SA API. If you have done that and you have the latest version of the BB60 API then you should be able to simply use the 64-bit BB60 API with your code. We distribute both 32 and 64 bit API builds for then BB60 API. You can find it in typically at C:/ProgramFiles/SignalHound/Spike/api/x64

Regards,
A.J.

[oogieoogieful]

I am a new developer.

I do have the latest version of Spike installed (3.04 API BB) I have access to a BB series spectrum analyzer, not an SA series.

Here is the documentation I am now working from:

http://www.signalhound.eu/download/BB60-API-Manual.pdf

I’m not sure exactly how this error arises but I believe it is when Matlab creates a thunk file:

A thunk file is a compatibility layer to a 64-bit library generated by MATLAB. The name of the thunk file is BASENAME_thunk_COMPUTER.c where BASENAME is either the name of the shared library or, if specified, the mfilename prototype name. COMPUTER is the string returned by the computer function

I may have access to a 32-bit Matlab soon. Apparently, the 32-bit Matlab does not require a thunk file.

[Andrew]

Hello oogieoogieful,

Someone else might be able to help you get things working, but our experience is that we have not had a customer be able to utilize our supplied 32-bit Matlab example on a 64-bit version of Matlab. We do not have a version of 64-bit Matlab in our shop and so have been unable to attempt to work through the incompatibilities. It does appear that one would have to go through quite a bit of effort to call a 32-bit DLL from 64-bit Matlab.

If you are interested, we have fully updated our SA device APIs. There are now 32 and 64 bit versions of the API that get installed when you download the latest version of our Spike spectrum analyzer software. http://www.signalhound.com/Spike. We recommend all new developers target these new APIs. They come with documentation as well to get you going. We do not currently provide Matlab interfaces to them, but if you are adept at C/Matlab programming you should be able to find enough information to call our 64-bit DLL from Matlab. The new APIs do have a different interface than the old ones, so there will be a learning curve which may not be acceptable if you are already familiar with the older APIs.

Let me know if you have any follow up questions.

Regards,
A.J.

[Andrew]

Hello Kirbi,

Depending on which sa_api version you are running, real-time functionality has changed recently. You will want to check out the programming manual for your version to find a full C example in the appendix for setting up real-time mode. This should help you set up Labview.

Regards,
A.J.

Hi,
I am trying to run the SHAPISlowPlot.m in Matlab and I get an error for the loadlibrary() call. Attached is the error message.

Does anyone else have experience with this type of error?

After reading the MatlabInstructions.txt file I see that it assumes I am running 32-bit Matlab, I have 64-bit Matlab R2014a.

Also, when I type >>mex -setup
It appears that my MEX is configured to use Microsoft Visual C++ 2012 instead of Visual C++ 6.0 or 2008.

Could my environment be what is causing this error?

Thanks!

Attachments:

You must be logged in to view attached files.

[Lior]

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

[Justin Crooks]

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.

[bbowar]

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?

[Andrew]

Hello Shapes,

We provide a C# API for the BB60C. You can find the code in the bb_api folder. The BB60C API is very similar to the SA44/124 API so you will be able to easily retrofit it over to the SA124 api.

It is simply a wrapper to our C DLL, it does not include any sort of visual app.

Regards,
A.J.

Spike shows a peak measurement of for example +7dbm. The API function returns +3dbm with the amplifier settings the same.

thanks
jim

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.

[Justin Crooks]

If you are using it with the USB-SA44B, you can use the API found in the Spike folder.
If you are using it by itself, without the USB-SA44B, email support@signalhound.com for a standalone TG API. Keep in mind that the TG output power is only from -30 to -10 dBm.

[Andrew]

Hi Victor,

Thank you for your updates and patience. I looked into this a bit further, and I hope I have come up with a solution. Start with a fresh download of the firmware updater folder and install this driver from FTDI. Link below

https://signalhound.com/sigdownloads/Spike/CDM%20v2.12.00%20WHQL%20Certified.exe

The ftd2xx.dll/bb_api.dll you dropped in are likely 64-bit versions. The FTDI driver install will be necessary for using the TG44/TG124 and will install the 32 and 64-bit versions. I think this is the missing piece. The firmware updater is a 32-bit application and installing the FTDI drivers hopefully will install the last missing DLL.

Let me know if this works.

Regards,
A.J.

[Anonymous]

Hello Andrew,

I had those libraries installed. And reinstalling them didn’t solve the problem. Here are my steps:
1. Unpack updater to separate folder.
2. Updater can’t find ftd2xx.dll, so I copy it from Spike 3.0.7 folder.
3. Updater shows that error from screenshot.
4. I also replaced bb_api.dll with one from Spike with no luck.

Regards,
Victor

[Justin Crooks]

I think I answered this on Facebook last week. In essence, for the legacy API, yes. I recommend keeping FFTSize * AvgCount <= 65536, although up to 512*255 will work. The new Spike API has no such limitations.

[Andrew]

Hey Dan,

Here is the direct link to the archived ARM build.
https://signalhound.com/sigdownloads/SA44B/arm_sa44B_api.zip
Compiled on a beagleboard with GCC, Cortex A8 processor.

Regards,
A.J.

[Andrew]

Hello Feng,

Video triggering is not a function of the API. If you need video triggering you will need to check the amplitude of the I/Q samples against your trigger level as you acquire them.

Let me know if you have any other questions.

Regards,
A.J.

[tr_feng]

Hi Andrew,
I am using APIs，i can not set up video trigger in IQ streaming mode, what’s the usage in API?
Thanks!