Search Results for 'api'

I wrote a 32bit program using your API to communicate with the SA44B unit. I am now trying to write a 64bit application using your API to communicate with the BB60C. My problem is I am getting unresolved external error on ilink64 call. According to the documentation the linker is expecting .o or .a files, not a .lib. I was using the bb_api.lib in the x64 folder. In the 32bit application I had to convert sa_api.lib to sa_apiomf.lib using coff2omf converter. That same converter fails on the 64bit version of the library. Do you supply the library in a .a format (ELF) or is there a converter to convert from .lib to .a?

[Justin Crooks]

bbowar,

The algorithm is basically the same, but with the SA44B, software image and spur rejection is on by default, and this can cause inaccuracies if the signal changes rapidly. The BB60C defaults to using only hardware image and spur rejection, so it is immune from this added measurement error, and will be more accurate for dynamic, real-world signals.

Spike is now working with the new VMware update 8.1.1 !

Tested on a Macbook Pro (OS X El Capitan Version 10.11.4) with Windows 7 and Windows 10 and BB60C

[dept911]

Andrew,

Thanks for your rapid response. However, When I click on the following
File>Import>Limit Line Table

It opens a file window to open the .csv file for the limit lines. No apparent opportunity to clear limit lines.

..Harold

Hello
Can we use vsg25 api in Linux or Ubuntu environment?
we want to use VSG API our own Linux based QT Application.

Thanks
Saira

I was trying to build a C application using my Borland C++ compiler. Application compiles and links, but when I run the application I get the following error: Access violation at address 6D4E2152 in module ‘sa_api.dll’. Write of address of 00000064. This error occurs on the saOpenDeviceBySerialNumber() function call. Any idea of what the problem may be?

[jams90]

I get my TG44A to work on C# with the TG_API.dll

thanks!

[jams90]

Hi, i’ve read about the StandAlone API and downloaded it with the PDF file wich explains the functions but i can’t get the API to work on C#.

is it posible to use it on a C# forms project?

[Justin Crooks]

Lou,
The way spur reject works is by mixing the incoming RF using two unique combinations of local oscillator and sometimes a different IF frequency. The results are compared and a signal not present in both is rejected as probable spurious.

In essence, a signal that is present for the entire sweep (or, for large spans, the time it takes to sweep 21.4 MHz) will not be rejected or hidden. We show our internal clock noise, rather than hiding it and risking missing an actual signal.

If a signal is pulsed or rapidly frequency hopping, spur reject may reject the actual signal, which is why for these types of signals, spur reject mode must be disabled. To analyze these types of signals, the BB60C is strongly recommended, although if you know the frequency of the signal, the SA44B in real-time mode may work also.

[Andrew]

Hi Labbench1,

Yes I did. I have made a note to notify you when the API has been compiled on Linux and is on the website. I suspect early next week. I’ll make a point to do it on Monday or Tuesday.

Apologize for the wait.

Regards,
A.J.

[Andrew]

Hi Andrew,

The trigger values in the current API provide you with the full resolution pre-decimation. The BB60 has a sample rate of 80MS/s which we convert to a 40MS/s I/Q data stream with decimation 1. The triggers are referenced to the 80MS/s. So at a decimation of 1, you would need to divide a trigger value by 2 to have it reference a sample in a 40MS/s I/Q stream.

If you have a decimation of ‘n’, divide the trigger value by (n*2) to have it reference a sample in your data stream.

Alternatively, the trigger values range between 0 and 2^20 (1048576), so if your getting 8192 samples per acquisition, divide the trigger value by the ration of 2^20 / 8192 = 128.

The reason it is this way, is so that the triggers are still providing 12.5ns resolution for any I/Q data stream.

Regards,
A.J.

Hello.
I work with BB60 API IQ example with trigger functionality.
My buffer length is 8192 samples (625kHz samplerate with 300kHz bandwidth) but trigger array gives me values like 100000 and bigger.Is it wrong or this values are not indexes in data array.

I am following the instruction from this page https://signalhound.com/download/spike-api-for-armv7-a-linux/. But i still cannot run the example “full_span_peak_search”. This is my Signal Hound serial numbers : 30300391
OS : Rasbian Wheezy

How do i know my Signal Hound Firmware Version ? Should i upgrade it ? And How do i upgrade it ?

Thanks, and sorry for my bad english

Attachments:

You must be logged in to view attached files.

[Andrew]

Hello rmaso,

Someone else might be able to assist you further. I don’t have experience with Labview but I found this response earlier in this thread.

If you have installed the Signal Hound Spike application, look in this folder.
C:\Program Files\Signal Hound\Spike\api\sa_series\labview
This is a Labview example we distribute. Another forum member was able to verify this worked out of the box. If this example works for you, then maybe you can determine what is causing issues with your setup.

Regards,
A.J.

[Andrew]

Of course,

Since you are using the Atom CPUs, it would be good to characterize the behavior on Windows first. Our application uses the API under the hood, so you can get a good idea on how various features work. The API functions similarly on both Windows/Linux, so when I get it recompiled, porting should be easy, if you are able to start development on Windows. Shoot me an email at aj at signalhound dot com and I will email you when I get a new Linux version up. I can’t guarantee any time frame though, maybe in the next couple weeks.

Regards,
A.J.

[Anonymous]

I use 32bit spike API in Windwos 7.
Next bring the thread function code
After each call bbFetchRaw stack pointer decreases on 12 byte

while(!Active)
{
if(reconfigure)
{
bbAbort(DeviceID);
bbConfigureCenterSpan(DeviceID, Freq, Bandwidth);
bbConfigureIQ(DeviceID,64,Bandwidth)
bbInitiate(DeviceID, BB_STREAMING, BB_STREAM_IQ);
reconfigure = false;
}
bbFetchRaw(handle, &data[0], 0);
PostMessage();
}

[Andrew]

Hi John,

The main reason one might buy a BB60A now is due to price. We do not sell the BB60A anymore and have not since the BB60C was released.

The BB60C hardware design is drastically different than the BB60A, as you noted. The BB60C uses a direct RF path for frequencies below 20MHz. The HDSDR application requires an input I/Q data stream to operate on. We have not developed the direct RF to I/Q code necessary for HDSDR. This only affects 20MHz and below. Our API is available to users and we do provide the code for our device to interface HDSDR, so if you have programming experience, it would be possible to fill in the missing pieces to get the direct RF into HDSDR. This would require C++ and signal processing experience.

Regards,
A.J.

Hello
In bb_api.h BB_MIN_IQ_BW is disable. So …
How can I know IQ bandwidth lower limit for any sample rate ?

[Justin Crooks]

Have you tried closing the device and re-opening it? If you are using the Spike API, this will likely work. With the older API, I believe there is a SHAPI_CyclePort or similar that should accomplish the same thing.

Does anyone have a suggestion on how to restart a stuck DLL when using Labview? Problem I am having is when I lose connection to a SA124B, for example during a trace request. I cannot regain control of the analyzer through the DLL.
Second question. Is the serial protocol for the SA124 published anywhere then I could go direct to the USB port and reset the connection to the analyzer with out having to use the DLL.
Any suggestions would be appreciated.
Thanks.