开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育

Smith Chart acting up in calibration


 

On my H4, I recently started having a problem calibrating. During cal the smith chart is sweeping wildly displaying a lot of straight angled lines about the cursor. In the end the cal fails as evidence by measuring the cal standards.

This started after flashing firmware to H4 dislord 1.2.40 though I suppose it could be coincidental.

I opened it and checked for cracked solder joints but didnt see any. Then I flashed it a few more times, testing in between, and finally after 2-3 attempts it started behaving normally again.

Has anyone else seen this before? Maybe I had some setting botched?

Bryan, N0LUF


 

UPDATE: It seems this only happens when my stop freq is above 300mhz. Is this normal or is my understanding flawed. I may have never noticed this because I don't recall ever using it that high.

Bryan, n0luf


 

COULD IT BE?

There are three ranges noted on the back label. 50k-300MHz, 300MHz-900MHz, and 0.9GHz-1.5GHz.

If my stimulus start and stop crisses over one of these ranges then I see this happen.

So this may be a feature I never heard of instead of a bug or problem.

Maybe me talking to myself will help some poor bloak searching the threads someday. lol

Bryan N0LUF


 

Bryan,

What was your original firmware version? Have you tried re-flashing back to
that version? This would eliminate hardware concerns and focus solely on
firmware. I noticed there are 10 issues flagged on version 1.2.40 which
gives me pause. I also noticed that a new version number of 1.2.42 has been
assigned for a future update.

Tony AC9QY

On Sun, Feb 9, 2025 at 9:51?AM Bryan Curl via groups.io <bc3910=
[email protected]> wrote:

COULD IT BE?

There are three ranges noted on the back label. 50k-300MHz, 300MHz-900MHz,
and 0.9GHz
-1.5GHz.

If my stimulus start and stop crisses over one of these ranges then I see
this happen.

So this may be a feature I never heard of instead of a bug or problem.

Maybe me talking to myself will help some poor bloak searching the threads
someday. lol

Bryan N0LUF






 

I have lost your initial message, but if this is an -H4, isnthe MS/SI option ser correctly?

That can change when flashing.

On February 9, 2025 10:51:08 AM EST, "Bryan Curl via groups.io" <bc3910@...> wrote:
COULD IT BE?

There are three ranges noted on the back label. 50k-300MHz, 300MHz-900MHz, and 0.9GHz-1.5GHz.

If my stimulus start and stop crisses over one of these ranges then I see this happen.

So this may be a feature I never heard of instead of a bug or problem.

Maybe me talking to myself will help some poor bloak searching the threads someday. lol

Bryan N0LUF




--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


 

Hi Tony,
I thought I had the noted somewhere but cant seem to locate it.now. I should have backed it up. I wonder if my amazon history would yield the answer.

It seems to work fine if I dont cross one of those ranges in my stimulus setting.
Bryan


 

On Sun, Feb 9, 2025 at 09:13 AM, Tim Dawson wrote:


I have lost your initial message, but if this is an -H4, isnthe MS/SI option
ser correctly?

That can change when flashing.
Yes that setting is important. IF the OP bought his H4 a few years ago it is the SI version. I thought the label on the back indicated if it was an MS version It is easy enough to try both settings and see if one works better than the other.

The other issue is that some of the chips will not operate up to 300 MHz. You can change the upper limit by going into Config-Expert Settings and changing the limit under Threshold.

Roger


 

The label on the back does indicate if it’s using the MS5351. Someone (and
I can’t remember whom) mentioned that firmware 1.2.40 included support for
both the Si5351 and MS5351. After flashing, there is a setting in a menu
(can’t remember this either) to select the proper chip. If I can find that
menu setting, I’ll post it.

Tony AC9QY



On Sun, Feb 9, 2025 at 11:58?AM Roger Need via groups.io <sailtamarack=
[email protected]> wrote:

On Sun, Feb 9, 2025 at 09:13 AM, Tim Dawson wrote:


I have lost your initial message, but if this is an -H4, isnthe MS/SI
option
ser correctly?

That can change when flashing.
Yes that setting is important. IF the OP bought his H4 a few years ago it
is the SI version. I thought the label on the back indicated if it was an
MS version It is easy enough to try both settings and see if one works
better than the other.

The other issue is that some of the chips will not operate up to 300 MHz.
You can change the upper limit by going into Config-Expert Settings and
changing the limit under Threshold.

Roger






 

On my older firmware, the menu selection is config/expert setting
settings/more/mode. The mode setting toggles between Si5351 and MS5351.
This path may be different in 1.2.40.

Tony AC9QY

On Sun, Feb 9, 2025 at 12:18?PM Tony Scaminaci via groups.io <tonyscam=
[email protected]> wrote:

The label on the back does indicate if it’s using the MS5351. Someone (and
I can’t remember whom) mentioned that firmware 1.2.40 included support for
both the Si5351 and MS5351. After flashing, there is a setting in a menu
(can’t remember this either) to select the proper chip. If I can find that
menu setting, I’ll post it.

Tony AC9QY



On Sun, Feb 9, 2025 at 11:58?AM Roger Need via groups.io <sailtamarack=
[email protected]> wrote:

On Sun, Feb 9, 2025 at 09:13 AM, Tim Dawson wrote:


I have lost your initial message, but if this is an -H4, isnthe MS/SI
option
ser correctly?

That can change when flashing.
Yes that setting is important. IF the OP bought his H4 a few years ago
it
is the SI version. I thought the label on the back indicated if it was
an
MS version It is easy enough to try both settings and see if one works
better than the other.

The other issue is that some of the chips will not operate up to 300 MHz.
You can change the upper limit by going into Config-Expert Settings and
changing the limit under Threshold.

Roger










 

Roger,
Resolved: You nailed the issue. I thought for sure I was an SI type but sure enough the HW version is 4.3_MS. The flash changed it to SI.

The unit will now calibrate with a stimulus of 50khz to 1.5G with no issues.

Thanks for all the help guys.

Bryan, N0LUF


 

Just a crazy thought from someone with very little VNA experience .....
SMA connectors are known to have a quite limited number of insertion cycles.
Is it possible you have a connector that is no longer working reliably;y?


 

On Sun, Feb 9, 2025 at 10:34 AM, Bryan Curl wrote:


Roger,
Resolved: You nailed the issue. I thought for sure I was an SI type but sure
enough the HW version is 4.3_MS. The flash changed it to SI.
Bryan - The first one to suggest this was Tim Dawson so he gets the credit not me...

Roger


 

Thanks for the shout out, and glad that I could help!

- Tim

On February 9, 2025 2:41:19 PM EST, "Roger Need via groups.io" <sailtamarack@...> wrote:
On Sun, Feb 9, 2025 at 10:34 AM, Bryan Curl wrote:


Roger,
Resolved: You nailed the issue. I thought for sure I was an SI type but sure
enough the HW version is 4.3_MS. The flash changed it to SI.
Bryan - The first one to suggest this was Tim Dawson so he gets the credit not me...

Roger




--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


 

Absolutely....thanks Tim. Somehow I missed your post.

One thing Ill have to remember now is that a reset will revert it back to SI...even if I save the config.

Fred, Yes, the sma connectors are weak sauce. They are always my first suspect. My next one may have N type...but adapters may cost more than the nanovna. hi hi.


 

At one time there were specific binaries which set that flag (but otherwise identical) Not sure if they still exist or not, since it's so easy to set.

- Tim

On February 9, 2025 8:26:04 PM EST, "Bryan Curl via groups.io" <bc3910@...> wrote:
Absolutely....thanks Tim. Somehow I missed your post.

One thing Ill have to remember now is that a reset will revert it back to SI...even if I save the config.

Fred, Yes, the sma connectors are weak sauce. They are always my first suspect. My next one may have N type...but adapters may cost more than the nanovna. hi hi.




--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


 

As a followup on this, I see the chip specific files from Huygen, but not Dislord . . . . fwiw . . .

- Tim

On February 9, 2025 8:41:26 PM EST, Tim Dawson <tadawson@...> wrote:
At one time there were specific binaries which set that flag (but otherwise identical) Not sure if they still exist or not, since it's so easy to set.

- Tim

On February 9, 2025 8:26:04 PM EST, "Bryan Curl via groups.io" <bc3910@...> wrote:
Absolutely....thanks Tim. Somehow I missed your post.

One thing Ill have to remember now is that a reset will revert it back to SI...even if I save the config.

Fred, Yes, the sma connectors are weak sauce. They are always my first suspect. My next one may have N type...but adapters may cost more than the nanovna. hi hi.




--
Sent from my Android device with K-9 Mail. Please excuse my brevity.




--
Sent from my Android device with K-9 Mail. Please excuse my brevity.