Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

trace command hung #16

Open
d51r3verse opened this issue Nov 18, 2019 · 2 comments
Open

trace command hung #16

d51r3verse opened this issue Nov 18, 2019 · 2 comments

Comments

@d51r3verse
Copy link

d51r3verse commented Nov 18, 2019

qrp73/NanoVNA-Q#16
Same issue appeared latest(f6f948b) NanoVNA-H too.

I using "empty trace" command for identify current trace status and scale in my script.
But it will hung occasionally.
I found the only way to remove this issue, Manually reconfigure traces or simply disable unsued trace slot( trace x off ) before send "empty trace". Similar issues on marker too.

Another issue I found was...

  1. Set sweep range to full span 10e3 ~ 1.5e9 / calibrate off / Nothing connected CH0/CH1.
  2. trace all off -> marker 1...4 off -> pause (Blank screen / LED steady - For fast fetch)
  3. Python loop scan&data 0..1 -> Join&save s2p touchstone via scikit-rf
    Exported every data 0...1 and sp2 files was exactly same.

But data is different with sweep&trace 0..1 enabled.( +4 ~ +20 dB point appeared at CH0 logmag )
NanoVNA requires at least one activated trace for get valid data?

Always appreciate your contribution.

@hugen79
Copy link
Owner

hugen79 commented Nov 18, 2019

Do not use the "pause" command to pause the scan. You can use the "scan" command to pause the screen display and perform a single scan, then use the "data" command to get the data.

@d51r3verse
Copy link
Author

d51r3verse commented Nov 18, 2019

I issued single pause command at outside of the loop.
Inside the loop doing scan & data 0...1, Every iterated data array were different( data array only updates after scan command )

In device live mode( trace 0 logmag 0 enabled / live sweep ), pulled CH0 logmag can not up to -21 dB( As I expected ).
But, I can see plus level of CH0 logmag when I turned all off traces & markers( blank screen / manual scan via PC ).

hugen79 pushed a commit that referenced this issue Dec 26, 2019
いろいろとありがとうございます。やろうと思っていたアイテムなので助かります。

基本はOKなのでこのまま入れちゃいます。
一点、scaleがデフォルトだと合わないので、追加で少し考えたいです。
前からある箇所で、phaseが90単位だったり、Logが10単位だったりも気に入らないので、合わせて考えます。
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants