Forum Replies Created
- Posts
PK,
The API would be the recommended way to automate with the VSG25. The VSG25 software and device does not support SCPI. SCPI automation is only supported on the VSG60 software.
The VSG25 API exposes most of the functionality of the user interface. It can be found in our SDK, linked below. See the user manual for programming examples.
https://signalhound.com/software/signal-hound-software-development-kit-sdk/
Let us know if you have follow up questions.
No it does not.
We have now released ARMv8 API builds for the BB60, SP145, and SM200/435 devices. This is API only, no Spike. The README in the documentation mentions the platform and compiler used for each build. None of the builds will support Windows+ARM.
RSartell,
Porting Spike is definitely something we have talked about, but there isn’t a timeline for this right now. The work done on the APIs would benefit a Spike port.
From your previous post, it seems Windows on ARM is your target platform? As you’ve noticed, all my ARM compiles are for Linux or Mac. If we ported Spike, Linux would likely be the first target OS.
Andrew
After long delay, we are happy to announce the availability of ARM (AArch64) support for the BB60 API. The API was compiled on the Nvidia Jetson AGX Orin platform. It’s expected to work on many ARMv8 Linux based systems.
Library files and README can be found in the SDK.
https://signalhound.com/software/signal-hound-software-development-kit-sdk/
Nome,
For many PCs, the use of a non y-cable will be sufficient to run the VSG60. It is becoming more rare for a PC to not supply the necessary 6W over a typical USB type-A port. You will typically only have issues when using ultra portable laptops such as the surface pro (for example).
A micro-B to type-C cable should work fine on most PCs with the VSG60. If that doesn’t work, consider something like the Anker 555 hub. This will connect to the PC via USB-C, and give you 2 USB type A ports to connect a y-cable to.
Our MATLAB examples are convenience classes that wrap and call the functions in the DLL. You can see everywhere we call a DLL function, the “calllib” function is used. It’s all just standard MATLAB code. As to which functions to call in the DLL, you would want to reference the VSG60 API (link below). What I recommend, is looking at the C++ examples in the SDK, creating your own example, then porting that to MATLAB. Writing your initial example in C++ is even better as you can prove functionality before the port.
https://signalhound.com/sigdownloads/SDK/online_docs/vsg60_api/index.html
Thanks for the feedback Alan. I’ll get this into our request log. I think these are reasonable requests.
Thank you for sharing!
This bug was resolved in a release of Spike today (4.0.8). https://signalhound.com/spike/
If you continue to have issues with this release, please contact us at support@signalhound.com
Thanks
mmark,
There are a couple scaling factors you might need to consider when FFT’ing the I/Q data from our API.
– If you are requesting 16-bit I/Q data from our API, and you want to measure dBm, then you will need to get the I/Q correction and apply it via the equations in our API manual. If you are requested 32-bit floating point data (recommended), then the data is already scaled.
– The FFT itself. I would recommend scaling the Fwd FFT by N. What additional scaling you need to apply is dependent on which FFT library you are using. Some use scaling by default, some dont.
– If you are using a window function, you want to normalize the window before windowing the data.
– Once you have the above resolved, the output of the FFT can be converted to dBm using the equation
10*log10(I^2 + Q^2)
The problem with the 2 script approach is that all the resources associated with the handle and device are in the working memory of the first script. The second script can’t access those.
A couple alternative solutions,
– Go to a 1 script approach where after the initialization occurs, the script goes into a waiting for user input loop, and responds to the requests for data, all within one script. This is the easiest solution.
– Change the first script to act more like a service, which stays open and communicates with other scripts/programs that request data. The first script is the only script that interfaces the device, and relays all data to the other script. This seems like a more complex approach unless you plan on being able to have several programs requesting data simultaneously.
It has been marked as spam. It got through our spam filters.
Hi Euan,
Good questions,
The marker “Set Freq” entry was designed as a one way control. It doesn’t show you the current marker frequency, but can be used to set the marker frequency. This is why you don’t see it ever update until you manually type something into the box. So things like moving the marker, or loading presets will not affect it.
As for why you don’t see the marker frequency report exactly what you set, is because the sweep bins do not always land on nice round frequencies. So when you set 1.83GHz, it will find the closest frequency point to your value. What frequencies bins the sweep lands on are hardware and configuration specific and are not predictable. RBW controls how close sweep bins are, so as long as your RBW is good for your application, using the set freq will always choose a sweep bin within your RBW, which would presumably be sufficient.
Let me know if you have follow up questions.
The SP145 would be the better choice for phase noise measurements due to it’s better absolute phase noise performance and higher frequency range.
The purpose of the preselector is to filter out of band energy. This is most commonly helpful when measuring over the air with an antenna, as communications signals such as broadcast radio, cellular, WLAN, are filtered, improving measurement performance such as dynamic range.
Phase noise measurements are commonly/ideally made directly connected to the DUT via coax, eliminating the presence of out of band energy unless generated by the DUT itself. You can always insert a filter if out of band energy was a problem for a particular measurement setup.
Yes, presets for these 2 devices should be compatible. Your client should be able to load your generated presets.
There is no road map or timeframes we are targeting. We are releasing updates as we can allocate engineering resources to them. I will be sure to reply to this thread when there are any updates to our ARM offerings.
Hi Jequin,
We have not yet built a LabView wrapper project for the SP145 API. It should be possible. One approach I could suggest now is to look at the SM LabView project and adapt it to the SP API. This may be difficult if you don’t have experience calling DLLs from LabView.
I don’t have a timeline on when we would have usable examples for the SP145 at this point.
If you attempt to build your own, and have any questions, please contact us at support@signalhound.com.
Thanks
I’m using this thread as the general update thread on our ARM progress since it has the most visibility and comments on our forum. We are very much interested in supporting the ARM architecture and have been slowly adding support since our last update.
In our SDK we now have API builds for both the SP145 and SM200/435 for both the Nvidia Jetson Orin AGX and MacOS (M4 CPU). These APIs support a subset of functionality, namely sweeps and I/Q streaming with decimations up to 4, which hopefully covers most use cases. 10GbE support for our SM devices is also not supported on the Mac build, just the USB variants for now.
We are continuing to develop capability on ARM to support a larger subset of our APIs and new APIs altogether, (I.E. the BB60 API).
We appreciate everyone’s feedback and patience.
Thanks Joe!
Pooja, we have also responded to your email. For this issue we will continue our support via email.
Regards