Search Results for 'api'

I have a BB60C. I found the Spike this software can import .csv file to set Limit-Line. But I can not found LabView vision API this function.
Anybody know how to used LabView to set Limit-Line.

Attachments:

You must be logged in to view attached files.

Dear all,

Recently, I wrote a C app on my 64 bit Linux PC (Ubuntu 16.04 LTS) , through the Linux API provided in the following page, it performs well.

https://signalhound.com/support/product-downloads/sa44b-sa124b-downloads/

However, when I port the same C source code to the Raspberry Pi 3 Model B (with Raspbian OS and g++ 4.9.2), the ARMv7 API provided in the same page cannot get the job done.

To identify this issue, I tried the example “sweep_and_iq_test” along side with the ARMv7 API, it seems like the same error is inevitable.

The output message from example code “sweep_and_iq_test” is following:

saOpenDevice No error
saConfigAcquisition No error
saConfigCenterSpan No error
saConfigLevel No error
saConfigSweepCoupling No error
saInitiate No error
pure virtual method called
terminate called without an active exception
Got Sweep 0
Got Sweep 0

Clearly, this happened when the function saGetSweep_32f(device, min, max) is called.

I think the issue: “pure virtual method called / terminate called without an active exception” can be identified as the thread join/detach problem.

Could you provide me any suggestion or support for this issue? Thanks a lot.

[Andrew]

Hello Yu Ching,

You are correct, there is no direct channel power measurement in the API. You will need to calculate it. The most typical way this is performed is by either integrating the frequency bins of a sweep (in power units) or averaging the power of an IQ waveform. LabVIEW might have these measurements available in the signal processing or related libraries.

I will attach the pseudo-code for the sweep method. This is pulled from Spike.

Let me know if you have further questions.

Regards,
Andrew

Attachments:

You must be logged in to view attached files.

I have a BB60C. I found the Spike this software can test channel power. But I can not found LabView vision API this function(channel power.).I alway ready use the API catch the signal by LabView
Anybody know how to used LabView to analyze (Channel power)?

I have recently gotten the following error when loading a program that uses the SA_API:
This application was unable to start correctly, (0xc000007b).
I don’t get this error on other computers. Spike works correctly on the same computer. One difference is that this computer runs Windows 10. Any thoughts?

Hello.

We are trying to use the TG44A with a small form computer. I was wondering if the API and drivers are compatible in any way with the Raspberry PI 3 boards or with the Intel NUC mini computers.

Thank you for your help.
Gabi Constantin.

[Andrew]

Hi Jared,

You are correct. These measurements are features of Spike and are not available through a public API.

The SA44 API consists only of low level data acquisition functions. You would need to use the API to retrieve IQ data from the receiver and then make your measurements on this data. Average power would be easy to calculate but carrier offset of a digitally modulated signal is non-trivial.

At this moment, there is not a way to retrieve these measurements programatically. We have talked about making Spike programmable via SCPI but there is no definite plans of this yet.

I apologize for the inconvenience.
If you have additional questions, please let me know.

Regards,
Andrew

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.