-
Notifications
You must be signed in to change notification settings - Fork 270
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
Wrong units shown for admittance values #445
Comments
Actually, it looks like the calculation is not showing the admittance but the parallel impedance so either the calculation or the labeling of the value needs to change |
I believe the above pull request should fix the issue, can you check if it works for you? |
Saver show correct values in Om But NanoVNA Saver use different formula: |
Well, as the link to Wikipedia shows, admittance is defined as 1/Z and has the unit Siemens. If you change the calculation you get something different which is not what I, and apparently others, would expect when you label it admittance. The formula that NanoVNA Saver currently uses could be called something like parallel impedance model or so, but as long as it's called admittance by NanoVNA Saver it will cause confusion. My change in #446 switches the calculation of admittance to provide the result in Siemens. I'd suggest to either do it that way or to re-label the admittance field, as it's currently presented, in a way that avoids this confusion. |
While add admittance in NanoVNA firmware i add additional markers: Most question, need change sign for Xp? |
My first guess would be that you may have a j^2 in there that gives you the -1 factor. Quick check: for a capacitor I'd expect some negative value for X, and a positive value for B so that would also match the formula |
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. |
The marker data for admittance use ohms as a unit. This should be S (for Siemens) or mho or Ω-1 (-1 as a power)
.
The text was updated successfully, but these errors were encountered: