mervin2014Participantmervin2014 April 15, 2015 at 1:46 pm
I’ve been using my SA124B Option 2 and TG124A for a while, I usually use it for S21 measurements. I had upgraded to the latest version of Spike. The problem wasn’t resolved even upgrading to the latest version.
When I use my SA in operation other than Scalar network analysis, it works fine but when I am doing S21 measurements, most of the time it will disconnect after a minute or two in the scalar network analysis. I can reconnect using the spike interface but it is quite annoying since I always need to setup everything when that occurs. It will take a while for the issue to occur when the TG and SA are connected to the DUT. But as soon as I remove the SA or TG, to measure another DUT, almost all the time the issue will occur.
Please advice if there any steps that needed to take to solve this issue.
AndrewModeratorAndrew April 15, 2015 at 4:04 pm
Can you please email email@example.com to begin the support process.
Please send information regarding your setup such as the current configuration of the software, such as frequency range, and the tracking generator control values you are setting when seeing this issue. Also please describe what you mean by “remove the SA/TG” and what kind of error messages you are seeing on screen. Also please share your PC information with us, most importantly, the Operating system, whether you are 32/64 bit and the CPU model number. Any other information you can think of that is unique to your setup or measurement process is helpful so we can try to duplicate the issue or determine its source.
mervin2014Participantmervin2014 April 19, 2015 at 5:28 pm
Thank you Andrew for a very quick reply. I’m sorry that I did not reply sooner, quite busy at work. I downloaded spike version 3.0.7 and so far I did not have the issue of SA and TG disconnected in the middle of the measurement. Thanks a lot guys.
Ones again thank you for the latest spike version.
AndrewModeratorAndrew April 20, 2015 at 8:31 am
Thanks for updating us on your situation. I am glad a newer release seems to have resolved your issues.
You must be logged in to reply to this topic.