- This topic has 5 replies, 3 voices, and was last updated 2 years, 1 month ago by
.
- Posts
I just received VSG60A and I was doing a step sweep between 110-130MHz to BB60C, it either caused the VSG60 to crash and Spike (BB60C) disconnected. There wasn’t any apparent pattern, examples:
1. While I set the start frequency in VSG60 and Spike got disconnected.
2. While I was using VSG60, it just crashed but Spike was running.
3. Sometime I was able to run the test, but VSG60 crashed or Spike disconnect when I was changing any of its parameter (RF Off).I previously was able run the similar test from AWG to BB60C and it worked without any issue.
1. Spike 3.5.16, F/W 8
2. VSG60 1.0.6, F/W 6 (No Error Log)Hello,
Is the crash specific to one certain VSG60 configuration? Can you operate the VSG60 in any transmit output? For example, does a simple CW output work? If the crash is associated with just the step sweep, it might simply be a bug with that specific configuration that we can investigate and fix. Let me know the full settings used when a crash occurs.
That being said, you might need to run the VSG60 on a separate PC to run them both simultaneously. Most PCs will have difficulty running two of our high speed USB 3.0 devices simultaneously due to the shared USB 3.0 bus. If you continue to see disconnections on the BB60C, you will need to either, use a different PC for each device, or you could try installing a USB 3.0 adapter card and plugging one of the devices into that card. The card will add another USB 3.0 bus, so putting one on the adapter card’s bus, and one on the PC’s bus can resolve this.
Here are two adapter cards customers have used in the past with success.
I look forward to your response.
AndrewCKWong,
I am able to reproduce this issue. The issue appears to affect the step sweep mode with certain configurations. I will need to fix this and issue a new release of the software.
I apologize for the inconvenience. I do not have a workaround at this time.
I will respond on this forum topic when I have released the new version.
Regards,
AndrewI’d like to add that in my case, the issue was Linux not allocating enough memory to USB devices.
As soon as I enabled the VSG60A while the BB60C was running, the application would either crash or disconnect one or both devices.
https://signalhound.com/sigdownloads/SDK/online_docs/vsg60_api/index.html contains instructions on how to solve:
sudo sh -c ‘echo 32 > /sys/module/usbcore/parameters/usbfs_memory_mb’Additionally, here’s how to make these new settings persist at boot:
Create a file: /etc/modprobe.d/signalhound_usb.confContaining:
# 16mb per signalhound device is needed, we set 3x that value here to have some head-room
options usbcore usbfs_memory_mb=48Next reboot, this will automatically be applied!
You must be logged in to reply to this topic.