Hello Carlos,

Thank you for emailing us as well. We will continue to work through your issues via email.

Regards,
Andrew

Hello JY,

You will need to calibration file for each SA44B you own. If you know the serial numbers for the devices I can help you get links to the calibration files.

Newer SA44B devices store the calibration file on the device itself. If you try running Spike with the other devices, it might automatically find the cal file from either the device or our server.

Regards,
Andrew

Hi Travis,

KB0NE is correct. There are no discussions for introducing other receivers into the Spike software.

Regards,
Andrew

Hello JY,

These instructions are for the Spike application.

Download the calibration file for your unit here
https://signalhound.com/custdata/P2054/D20540419.bin

Place this file into this directory path.
C:\ProgramData\SignalHound\cal_files

ProgramData is a hidden folder so you must “Show Hidden Files/Folders” in the Windows file browser menu. If the SignalHound/cal_files folder does not exist, then go ahead and create it. Once there, rerun Spike.

I believe for the 2.14 application simply place the .bin file in the same directory as the executable in the application directory.

Let me know if you run into any issues.

Regards,
Andrew

Hello setu_mohta,

There is currently no plans to offer a signal generator with these features.

Regards,
Andrew

Hello setu_mohta,

We do not have a CSV signal library other than the small number of examples we ship the unit with (~5 examples which indicate more of how to create the CSV files over providing various waveforms)

Regards,
Andrew

Hello Blackmore90,

Thank you for the reply.

The BB60C generally has had issues running consistently with Xeon processors which is why we only specify the i5/i7 processors in the minimum/recommended PC specs. Generally the issues stem from the USB drivers/support.

If you haven’t already, you can check the Supermicro page for your PC and see if there is any USB/chipset drivers specifically for your machine. I found this page which appears to be the motherboard for the server you linked. You can find a link to the drivers for this motherboard here. “Download the latest drivers and utilities” on the right hand side of the page. There is Intel USB/chipset drivers in the driver list. See if these resolve your issues.

https://www.supermicro.com/products/motherboard/Xeon/C600/X10DRU-X.cfm

I look forward to your response.

Regards,
Andrew

Hi Catalin,

There are situations (when using the SA44/124) in which the IF overload may not always be reported. Where as with the BB60C which relies on the ADC to tell us of IF overload, the SA overload warning is done by manually checking amplitude values. The ADC does not reliably clamp to the min/max ADC values so we cannot always depend on the large values being clamped properly by the ADC. Additionally, the signal can clamp before it reaches the ADC (in the RF section) and we cannot detect that situation either.

Also note, the Spike software when sweeping will warn you when the signal exceeds the reference level which is not the same as the IF overload warning. This extra warning is not present in zero-span mode.

Sample rates are low enough on the SA devices, you could insert a check on the IQ data to determine if it exceeds some known value (your reference level?).

Let me know if you have additional questions.

Regards,
Andrew

Hi Blackmore90,

Can you provide the PC make and model? I will see if I can determine what else can be done for your specific PC.

Regards,
Andrew

Hi hhonza,

Try disabling the video trigger when you are playing back the capture. This will allow you to scroll through the data. When you are playing the signal back and the video trigger is active, it attempts to find triggers in the capture and overrides your manual scrolling.

Once you are able to scroll through the data, try zooming in on the falling edge of that pulse to verify it is a smooth descent.

The trigger position control only affects the display of the IQ data. The pre-trigger setting on the IQ recording toolbar affects how much data before the trigger gets saved.

Let me know if you have additional questions.

Regards,
Andrew

(Yves has contacted us through email)

– Andrew

Hi John,

Sorry for the delay in response. The SA44B can sweep a larger range than its available RBW. The SA44B can be configured to sweep any range of frequencies within its 1Hz to 4.4GHz range. At a 200MHz span the minimum RBW available will be 6.5kHz.

As for antenna, I’m not familiar with the EMI/EMC antenna market. I would imagine it would depend on what you are attempting to achieve. Are you simply trying to find/characterize interference, an RF probe might be best in this case. If you need to simulate a real EMC test, you will likely need to recreate the test setup as close as possible with a calibrated antenna. I wish I could be more help. Maybe someone else on the board could help you out? You could create a separate topic. I know there have been several users on this board with EMC experience.

Regards,
Andrew

[Andrew]

Hello pmerana,

In the control panel in EMC precompliance, in the ‘trace’ section, you will find the export button which will export the entire sweep (all active sweep segments) to one file. It will export the frequency/amplitude pairs of each sweep segment in order. (Basically exactly as it is plotted). You will need to plot it on a logarithmic x axis to see it as it is shown in Spike. Is this adequate for your needs?

No updates for automatic QP measurements.

Regards,
Andrew

• This reply was modified 7 years, 10 months ago by Andrew.

Hi Blackmore90,

IQ streaming can be more USB throughput sensitive than standard swept analysis.

Here are some troubleshooting ideas.
1) Try a different USB 3.0 port. We have found that not all USB 3.0 ports are created equal.
2) Enable the high performance power option in the “Power Options” menu in the control panel.
3) Try updating your USB 3.0 driver. You can find instructions for Windows 7 machines on our website on the page http://www.signalhound.com/Spike in the FAQ section under the question “The Software Reports “Device not found” (BB60C)”. You will find two driver links. Install one and restart your PC and try again.

I look forward to your response.

Regards,
Andrew

Hello HHonza501,

There are no plans currently to allow the user to change sweep configurations during the recording. If users needed this kind of flexibility on the sweep recordings I would recommend using the API to retrieve sweeps from the device and storing them in a custom file format that suits the customers needs.

You are correct, as you scroll the recording it will move the sweeps into the waterfall. I can see how this wouldn’t be desired. I will make a note of this and potentially resolve this for future versions. Thank you for the feedback.

Let me know if you have additional questions or need clarification.

Regards,
Andrew

That is correct. There is no configurable DSP on the unit, other than the processing associated with individual measurements (sweep/real-time/IQ). The API will be very similar to our other devices.

Regards,
Andrew

Hi Testpoint,

More information on the SM200A here
https://signalhound.com/sm200a/

Let us know if you have follow up questions.

Regards,
Andrew

Hello Sinisa,

Currently there is no plan to restore the 3D waterfall.

Regards,
Andrew

Hello Bindinir,

The 3D spectrogram view was removed in a recent release. In that same release we added several new features to the 2D spectrogram, such as large sweep history and marker placement.

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

Regards,
Andrew

Hi Jay,

We have seen improvements when using a low latency or real-time kernel. Unfortunately there is no way to determine when this loss occurs. At one point we narrowed it down to a small circular buffer within the FTDI driver, (based on other similar complaints). Several years ago we tested an open source version of the FTDI driver and saw worse results.

Internally using a low latency kernel with a desktop PC (Intel i-series processor), we saw no loss occur over long periods of acquisition (using IQ data to detect data loss). Although, I have had customers report data loss even on low latency kernels with lower power processors.

It would require a moderate/large firmware/software redesign to fully resolve this issue for the Linux platform. We don’t have any plans for this at this time.

Regards,
Andrew

[Author]

Posts