Search Results for 'api'

[Andrew]

Hello rtcjss,

I personally have never used CVI but I have seen these types of issues before. You are seeing this because our API is not 100% C compatible. It is going to complain about missing typedefs on the enums and structs and maybe a few other things. I think if you addressed this, the CVI compiler would be able to parse our header file without errors. This is just a guess though. Without CVI, I cannot test this.

Regards,
A.J.

I try to write an application for the SA124B with LabWindows/CVI under Win7. I use the sa_api.h, sa_api.lib and sa_api.dll files. (x64)
Unfortunately the compilation its not success.
I receive many errors for the sa_api.h.
Does anyone know the problem ?
The sa_api.h File is suitable to work with CVI ? or need to make changes ?
I look for help!

Attachments:

You must be logged in to view attached files.

[Justin Crooks]

Dear G. Grasso,
These legacy APIs are no longer supported. I have had reports that the 64-bit API, when paired with a low latency kernel, works reasonably well.
Your best bet is Windows (x86/x64) which is our tried and true OS. If you must use Linux, try either the x64, or 32-bit ARM (Raspberry Pi 2-like processors).
We’ll remove the 32-bit link from our website to avoid this problem in the future.

[Andrew]

Hi Everyone,

Today we are releasing version 3.1.0 of the Spike software. With this comes EMC pre-compliance measurements and features for the BB60A/C users, frequency difference meter utility, temporary time base adjustment utility, ability to hide control panels, and we moved the API files out of the installer into their own separate download. Check out the change log on http://www.signalhound.com/Spike for more details.
Also keep an eye out for the next update where we will be attempting to resolve many of the text scaling issues for high DPI displays.

Regards,
A.J.

Hello,

I downloaded the Linux 32-bit Linux API files from the support section of your website and tried to compile the provided test program on a 32bit linux machine.
The compilation process halts with the following errors:
/usr/bin/ld: i386:x86-64 architecture of input file `libSHLAPI.a(main.o)’ is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file `libSHLAPI.a(myFFT.o)’ is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file `libSHLAPI.a(MeasRcvr.o)’ is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file `libSHLAPI.a(USBInterface.o)’ is incompatible with i386 output

Which means that the libSHLAPI.a was compiled on 64bit architecture machine, as confirmed by the following command:

objdump libSHLAPI.a -a
In archive libSHLAPI.a:

MeasRcvr.o: file format elf64-x86-64
rw-r–r– 0/0 5440 Jul 18 21:43 2011 MeasRcvr.o

USBInterface.o: file format elf64-x86-64
rw-r–r– 0/0 24392 Jul 18 21:43 2011 USBInterface.o

main.o: file format elf64-x86-64
rw-r–r– 0/0 42048 Jul 18 21:43 2011 main.o

myFFT.o: file format elf64-x86-64
rw-r–r– 0/0 15048 Jul 18 21:43 2011 myFFT.o

Please provide a download link for the 32bit version of the library.

Thank you

[Andrew]

Hi bbowar,

We distribute a linux build of the BB60 API on the BB60 downloads page. Usually it is a few versions behind the main distribution.
You will find it near the top of the list on this page
https://signalhound.com/support/downloads/bb60c-bb60a-downloads/

Regards,
A.J.

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.