Search Results for 'api'

I am currently developing a test fixture for calibration/testing of an RF module. Each module needs to know its RF power and carrier offset. My USB-SA44B can report these numbers when configured in modulation analysis mode. However, I don’t see any references to modulation analysis mode in the API. Does this mean that modulation analysis mode is a feature of Spike, and not the instrument per se?

[Andrew]

Hello g0s,

There are a few ways to load a custom waveform for the VSG. I know you don’t want to use the application we provide, but the easiest way is to use the UI to load the custom waveform file. There are example waveform files in the application directory at
C:\Program Files (x86)\Signal Hound\VSG25\arb_examples
You can also use the C programming interface we provide, the files for which are also provided in the application directory at
C:\Program Files (x86)\Signal Hound\VSG25\api
You will want to use the sgSetFrequencyAmplitude and sgSetCustomIQ functions to achieve this.

Waveforms can be created in excel or a number of other ways, common ways might be using a math library such as Matlab, etc.

Let us know if you have more specific questions.

Regards,
Andrew

[Justin Crooks]

The .csv file is generally for non-standard waveforms. Our API can be used to control the VSG without the GUI.
The CSV file can be used if you have less than 2048 I/Q samples you wish to send, either as a repeating burst, or a continuous loop.

[Andrew]

Hi Jason,

We currently don’t have an ARM build for the BB60C. It is unlikely we will any time soon, because we would have to find replacements for the signal processing libraries we use, which target x86/x64 specifically. The processing requirements are simply too high to re-implement the functionality in naive C code and have it run on ARM.

Although, we do have a BB60 Linux build for x64 and it does not require any modifications to the kernel to run. A standard Ubuntu (or similar) install will work fine. We used the libusb library for USB 3.0 with no issues.

It should be stated that our Windows APIs are the only APIs that receive full support. We do fix issues in our other APIs but it may take awhile compared to the Windows versions.

Regards,
Andrew

[joeqsmith]

What version of Labview are you using?

Do you have a specific question? You may want to upload your code that you are having problems with.

If you are just looking for a general idea how to do it, the SA example is where I started. API manual is good enough. I really have not seen too many problems that were not related to lack of sleep.

[Andrew]

Hello Mehran,

I apologize that you are having issues.
Lets wait another week or two and we will release some .vi’s and examples that should help you get going. This will be part of our API download SDK once released. Check back in a couple weeks.

In the meantime, someone on the forums may be willing to help you out with your Labview issues. The only tips I can provide is to look at our existing SA API example for Labview. Also check out the BB60 API C examples which show how to use the API.

Regards,
Andrew

Hi Guys

I thought I would finally ask this question. I’ve got the SA44B which I am using with a number of computers. For instance windows x64, windows x32, raspberry pi, linux i86 and my latest instalment is trying to get the SA44B APIs to work on an odriod xu4.

So I’ve managed to interface to the SA44B via the APIs for each operating system, but would like to understand the limitations (or where the limitations are) when working with the ARM devices.

There is definitely a drop in performance when switching from an i86 to an ARM environment. Where is the issue? Is it some memory management thing? Is it something to do with dropped samples?

I’m just trying to understand what ARM device I could use that would give similar performance to the i86 devices or is it a case of the APIs needing to be updated?

Any recommendations in helping me understand the ‘issues’ with the ARM environment?

An example of the discrepancies between the 2 architectures would be if I was looking at a DBV-T spectrum (in spike) on an i86 pc, it would be a nice flat amplitude response. Whereas, with the same settings, the ARM response would show significant peaks and troughs in the amplitude. Averaging fixes this but I’m after the better performance!

Many thanks

Regards
Jason

We have several SA44Bs. One now has no output. Using Spike in swept mode, the display is a solid color. In zero span mode, there is no line, data shows not a number. Using LabVIEW API, the device can open and return API ver, serial number, etc., but when retrieving zero span IQ data, the data is NaN. No error is returned. I hooked a cable from the Self test output to the input, and ran the Self Test in Spike, and it passed.

[Andrew]

Hello ykhaled,

We do not offer this type of plot in our software (CCDF plot). This is something we may offer in the future, but for now we don’t currently have plans for this.

The only work-around I see available is to utilize our programming API to make the measurement in your own application. This would require programming experience as well as the ability to make this calculation with the waveform data from the BB60C.

Let me know if you have additional questions.

Regards,
Andrew

[Andrew]

Hello mehran,

We are working on Labview vi’s right now for our products. These files should be available in the next couple of weeks. If you cannot wait for us to deliver this, then consider using the example vi project we distribute in the API download folder. The vi project can be found in the sa_series examples. The API for the SA44/SA124 is very similar to the BB60C API and you should be able to convert this project to the BB60C API in short time.

Regards,
Andrew

I have written some code which I compile using an Embarcadero compiler for a 64 bit target and have no issues. When I select to compile for a 32 bit target my compiler gives me the following error “Unrecognized _declspec modifier”
The line causing the error is in bb_api.h:
“BBDEPRACATED(“This function is deprecated…”)
Any idea what the could be the problem?

[joeqsmith]

Andrew, I swapped the board out for the second one. It too has been solid. Not a single glitch and I am using the hub and extension cable as well. The BB60C has been in use a fair amount. It seems the Dell’s USB ports may just not be as clean. I guess you could buy the same PC and see if you could replicate the problem. Maybe there would be a way to allow the BB60C to auto recover. Attached my latest video with Labview. Things are a little cleaner and I have a much better understanding how to use the API now.

https://www.youtube.com/watch?v=Mkec-Eyhg7c

[joeqsmith]

No problem. I’ve continued to work with the API using LabVIEW. The more I use it, I like it.

Morning,

Thanks for the great products you are producing!

I’m looking for a way to start Spike from a batch file that will either:

1) Allow me to set the parameters of the spectrum analyser from the command line OR
2) Allow me to start spike with a saved Preset

I’m able to do this using the APIs and a custom program, but in some instances I would like to use the latest Spike functionality.

I’m running a remote pc with an SA44b connected and using tightvnc to connect to it, hence the need to start spike with some predefined parameters.

Many thanks for your help.

Regards
Jason

[Andrew]

Hello magintd,

I can clarify. The bbr file is a flat recording of sweeps only (frequency domain ‘bins’). The IQ data is not recorded in this file. The sweeps are stored as min/max arrays. If the avg detector is enabled, min/max should equal the same values. I will attach a basic bbr parser so you can see the layout and how we parse the files in our software.

If you are looking to get IQ data, then we do have another recording feature in zero-span that records IQ data. If you are looking for the ultimate flexibility, you could grab IQ data directly from the device with our APIs.

Let me know if you have additional questions.

Regards,
A.J.

Attachments:

You must be logged in to view attached files.

[Andrew]

Hi Joe,

Did you get download the latest API files from the link I posted above? The bbFetchRaw function is deprecated and is not used in any of the examples I provide. The function that replaces it is the bbGetIQ function and has more flexibility.

That said, decimation is the only way to control the sample rate of the device. bbFetchRaw will always return the same amount of data per call. You do not need to call bbQueryStreamInfo more than once. bbGetIQ allows you to retrieve an arbitrary amount of samples per function call. bbFetchRaw guarantees no loss of samples assuming data retrieval keeps up with the sample rate of the device. The API will store about 3/4 of a second worth of data before data loss occurs.

This information and more can be found in the API manual at
https://signalhound.com/sigdownloads/BB60C/BB60-API-Manual.pdf

Regards,
A.J.

[Andrew]

Hi Joe,

Glad you found your problem with that function.

Regarding getting IQ data from the receiver, take a look in the examples folder. There will be an example of the minimal IQ acquisition setup. This should be a good starting point. If you don’t see the examples folder, get the latest API files from this download

https://signalhound.com/download/bbsa-application-programming-interface-for-windows-3264-bit/

Video triggering occurs in the Spike software. The implementation is simply looking for the transition across a certain amplitude. (for() loop through each IQ sample). Pattern triggering is much more involved and is performed in the Spike software as well.

Regards,
A.J.

[joeqsmith]

STUPID STUPID STUPID… pointer problems… Must have been too late in the day and I could not see it.

I am reading the API document and I am trying to understand what I need to do to get the BB60C into zero-span mode.

Basically, I am wanting to try and decode that 2FSK signal I mentioned earlier using Labview. I have it now working with your demodulator using the clipboard copy paste. I also have it working with the raw IQ data now with the file save under zero-span. Next step is just to pull the data directly from the BB60C.

Also, I did not see anything in the API for triggers. Does this mean that the triggers in Spike were all at a higher level?

I am attempting to use the latest API and for the most part, everything seems to work which is why I wonder if I found a bug.

I did notice that when I call the bbGetDeviceType, it always returns a 0. The device is open when I make the call. It does not return an error.

I assume the problem is between the keyboard and chair but I noticed the document mentions four possible types including BB_DEVICE_BB124
but the header only defines three.
// Device type
#define BB_DEVICE_NONE 0
#define BB_DEVICE_BB60A 1
#define BB_DEVICE_BB60C 2

Is this call functional?

Thanks

[Andrew]

Hello ssw,

Did you download the API files found at this link?
https://signalhound.com/download/bbsa-application-programming-interface-for-windows-3264-bit/

In this download folder you will find two examples, simple_sweep_1 and simple_sweep_2. They will show you how to open, configure, and acquire data from the SA44B. You will use the saConfigCenterSpan function to control the frequency range of a sweep, and you will use the saGetSweep functions to acquire one sweep at your desired configuration. The example files should be able to be compiled and ran.

Hopefully this is enough to get you started. Contact us at support@signalhound.com if you have additional questions.

Regards,
A.J.