¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Nanovna-Users
  2. Topics

DiSlord v1.2.0 instability even though MS5351 clock-generator is selected (MS-3.6 HW version)

 

Hi guys.

My original NanoVNA-H genuine (sourced from Eleshop in EU) has been working flawlessly with delivered 1.1.01 synchronised DiSlord firmware. After upgrading to DiSlord version 1.2.0 and selecting Ms5351 clock generator in options give severe signal error in around 420M-440Mhz and 600M something. Even reverting to Si5351 setting and back again as well as resetting all settings and creating completely new calibrations does not solve it. Only remedy is to revert back to 1.1.01 DiSlord synchronised version but then I miss all the new trace formats and especially the ability to flip screen.

Anyone know if there will be a DiSlord synchronised 1.2.0 version with MS or SI selectable initial clock generator setting?

Thanks

C
 

Post your issue on his github or group.

On Wed, 24 Aug 2022 at 17:00, <cavokk@...> wrote:

Hi guys.

My original NanoVNA-H genuine (sourced from Eleshop in EU) has been
working flawlessly with delivered 1.1.01 synchronised DiSlord firmware.
After upgrading to DiSlord version 1.2.0 and selecting Ms5351 clock
generator in options give severe signal error in around 420M-440Mhz and
600M something. Even reverting to Si5351 setting and back again as well as
resetting all settings and creating completely new calibrations does not
solve it. Only remedy is to revert back to 1.1.01 DiSlord synchronised
version but then I miss all the new trace formats and especially the
ability to flip screen.

Anyone know if there will be a DiSlord synchronised 1.2.0 version with MS
or SI selectable initial clock generator setting?

Thanks

C
 

This is because DiSlord's firmware uses the 3rd harmonic at 600MHz, and the VCO frequency division factor is set to 6, which requires the VCO of the MS5351 to be locked at 1200MHz, but not every MS5351 can lock to 1200MHz well . I properly adjusted the MS5351's division settings and updated the firmware, I hope it works for you.
 

Hugen,

Is this a problem with the SI version chips?

Thanks,

Mike N2MS

On 08/31/2022 2:01 AM Hugen <hugen@...> wrote:


This is because DiSlord's firmware uses the 3rd harmonic at 600MHz, and the VCO frequency division factor is set to 6, which requires the VCO of the MS5351 to be locked at 1200MHz, but not every MS5351 can lock to 1200MHz well . I properly adjusted the MS5351's division settings and updated the firmware, I hope it works for you.
 

Ohhh - big thanks :D - will test during the weekend as I am loooong way from home at the moment. Thanks for the effort providing a fix ?

Cheers

C
 

So - I am happy to report that new 1.2.14 FW has solved the issue completely !

Thanks for the support :D

Cheers

C
John N0TA
 

I can't find 1.2.14 -- where is it?
- John
Alex Kindred N7AWK
 



Alex N7AWK

On Wed, Sep 7, 2022, 3:18 PM John N0TA <reillyjf@...> wrote:

I can't find 1.2.14 -- where is it?
 

Thanks Hugen for your info.

I think I'm missing something, it appears to me that there are two versions of each fw files an MS_xxxx and SI_xxxx, could you please guide me on which dfu file version I need for my H4 (SN:xxx71290)?

Thanks,
Ramon
 

On Fri, Sep 9, 2022 at 12:07 PM, Ramon S wrote:

I think I'm missing something, it appears to me that there are two versions of
each fw files an MS_xxxx and SI_xxxx, could you please guide me on which dfu
file version I need for my H4 (SN:xxx71290)?
On the NanoVNA-H and NanoVNA-H4, if MS5351M is used, the MS suffix is added to the version number on the label of the backshell, such as 3.6_MS or 4.3_MS.

Roger
 

Hi Roger,

Thanks for your reply.

The label of my back shell only says...HW Version 4.2, SN: SN:H$-xxx71290. I do not see nay mention of MS or SI. bought my unit from R&L Electronics in Sep '20. Could it be it does not contain any of these chips?
My first instinct was to try which H4 dsu file would load on it, but am concerned I might brick this very useful instrument...
 

The MS/SI tag only came into being after there were two types. Those with no tag, iirc, are the SI. (Actually, unless this latest .14 build changed something, the code in the SI and MS builds is identical, with the diff being which is preselected. You can, however, change the selection in tnne advanced menus.

On September 9, 2022 10:45:15 PM CDT, "Ramon S via groups.io" <ve7rvs@...> wrote:
Hi Roger,

Thanks for your reply.

The label of my back shell only says...HW Version 4.2, SN: SN:H$-xxx71290. I do not see nay mention of MS or SI. bought my unit from R&L Electronics in Sep '20. Could it be it does not contain any of these chips?
My first instinct was to try which H4 dsu file would load on it, but am concerned I might brick this very useful instrument...




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

It is practically impossible to brick these, even if you deleted the
bootloader there are programing headers on the board. It should
be explained in the community manual.

On Sat, 10 Sept 2022 at 05:45, Ramon S via groups.io <ve7rvs=
[email protected]> wrote:

Hi Roger,

Thanks for your reply.

The label of my back shell only says...HW Version 4.2, SN: SN:H$-xxx71290.
I do not see nay mention of MS or SI. bought my unit from R&L Electronics
in Sep '20. Could it be it does not contain any of these chips?
My first instinct was to try which H4 dsu file would load on it, but am
concerned I might brick this very useful instrument...
 

Tim and Dragan,

Thanks for your inputs. I have now updated my H4 with the SI dfu file.

1 - 14 of 14