Howdy Raj,

Well over half a century ago when I was 13, I wanted to build an oscillator to practice morse code.? One of the men at my church was an EE and also a ham (he also had a really cute daughter my age that I was kind of sweet on...).? I dropped by his house one evening and asked him if he could help me build an osculator (not a misspelling, rather a mispronunciation of oscillator).? He told me if I wanted to practice code, he would help me build an oscillator but if I had in mind some sort of practice with Janice (his daughter) I had better take up some other hobby quickly.

Nelson??

On Tue, Mar 6, 2018 at 7:37 PM, Raj vu2zap <rajendrakumargg@...> wrote:

My English teacher Mr. Hobday RIP would have explained it as oscillating occulation!

He lived down the road and would drop in some evenings and explain English words
by breaking them down. I suspect he always came for a cuppa! I managed to pass!

Raj

At 07-03-18, you wrote:

>How far away from English does Ameriglish/Yankish really go?
>Their/There/They're is bad enough, but "osculation"??? Sorry, David, go back to middle school :( or at least use a dictionary once in a while ...
>
>Still, 73
>Dex, ZL2DEX

--

I always thought the Universe was a wonderfully strange place until I?studied Particle Physics - I now know the Universe is, in fact, profoundly odd in nature

So did you measure the crystal directly?
If so, your probe likely modified the frequency a bit.

My calculation of 24.9991375 may be wrong for a number of reasons:

It assumed that your two readings of the three clocks were made while?
tuning through 10.0mhz in 50hz steps.? But we have since seen that there
is a bug in the code such that it would not make the LSB to USB transition while?
tuning in 50hz steps.? So not clear exactly what was going on there.

It assumes your rig was either uncalibrated (and thus si5351_vco==875.0mhz)
and that your probe on the crystal is not disturbing the crystal frequency.
Or that you are doing an si5351_setfreq() to one of the clock outputs of 25.0mhz and measuring that.

Jerry


On Wed, Mar 7, 2018 at 09:59 pm, Michael Shreeve wrote:

24.99800 MHz clock

?

. . .

24.99800 MHz clock

On Wed, Mar 7, 2018 at 8:34 PM, Michael Shreeve <shreevester@...> wrote:

Jerry, I was just looking at it. on LSB 54.99645

? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? on USB 54.99645

Regardless of upper or lower, no change. Does that make more sense ? When I looked before setting it, I noticed it wasn't on 10.000 MHz so I made very sure this time. Now to measure the 25 clock.

On Wed, Mar 7, 2018 at 7:03 PM, Jerry Gaffke via Groups.Io <jgaffke@...> wrote:

So, in that first instance, the rig is tuned to?54.98977-(32.99388+11.99624) =?9.999650
In the second instance, it is tuned to?54.99647-(56.99305-11.99624) =?9.999660
Since it flipped, we can assume 10mhz is somewhere in the middle, let's assume 9.999655 mhz
I'm betting your 25mhz oscillator will measure to be around? 25.0 * 9.999655/10.0 =?24.9991375 mhz

This little exercise in looking at that transition makes apparent what I think is a bug in that code scrap,?
we need to deal with the case where one or the other frequency is exactly equal to 10.0 mhz.
So code in ubitx_20.ino at line 470 should be edited to read:

? ? if (prev_freq <= 10000000l && frequency > 10000000l)

? ? ? isUSB = true;

? ? if (prev_freq > 10000000l && frequency <= 10000000l)

? ? ? isUSB = false;

I think.

Jerry, KE7ER

On Wed, Mar 7, 2018 at 05:21 pm, Michael Shreeve wrote:

Hopeffuly you see this Jerry, its just for you. but anyone might find this usefull I hope.?

Frequencies on 10mhz lsb Clock 0 54.98977
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? clock 1 32.99388
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? clock 2 11.99624

Frequencies on 10 MHz USB Clock 0 54.99647
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? Clock 1 56.99305
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Clock 2 11.99624?
And as I said in the video, haven't measured the master 25.000 MHz clock. Soon that will happen.?

--

Michael Shreeve N6GRG

--

Michael Shreeve N6GRG

Yup, another minor bug in the code from? ?
Though neither of these bugs will be an issue for most users.

Just be aware that after going into the menu to flip between USB and LSB,
it won't take affect till after the next time the frequency is changed.

And be aware that very occasionally when tuning past 10mhz the USB/LSB flip
won't happen like it usually does.
So either tune through 10mhz again, spinning the encoder quickly this time,
or switch sidebands manually using the menu.?



The bug Michael found is in function menuSidebandToggle()? at line 155 in file??ubitx_menu.ino,?
where it currently reads:

? ? updateDisplay();

? ? menuOn = 0;

Need to add a line to update the frequency, since this function has toggled the the state of isUSB:?

? ? updateDisplay();
? ? setFrequency(frequency);

? ? menuOn = 0;

?

There are other cases of this same bug.
For example, on line 57 of that same file, in function menuVfoToggle()

? ? ? setFrequency(frequency);

? ? ? if (frequency >= 10000000l)

? ? ? ? isUSB = true;

? ? ? else

? ? ? ? isUSB = false;

? ? ? updateDisplay();

Notice that the call to setFrequency() is made before the variable isUSB is modified.
It should occur after the variable isUSB is modified.

None of this will be an issue for normal operation.
Not something I feel inclined to fix on my rig.

Jerry, KE7ER

On Wed, Mar 7, 2018 at 09:06 pm, Jerry Gaffke wrote:

You are awfully sparse with your words, and don't fully describe what you are doing or seeing.

I suspect what you are doing is setting the frequency to exactly 10.0 mhz.
Then you go into the menu and flip between LSB and USB, and are wondering why there is no change
in the measurement of clk1 with the frequency counter.
My guess is that the code does not update the Si5351 until the frequency changes.
Move the freq by 50hz using the encoder knob and clk1 should update.
But I would carry out this experiment at something other than 10.0 mhz,
as we have too much happening there already.

You may have found another little bug in the code.?
Or as some would say, a feature.

Jerry, KE7ER

Jerry, I was just looking at it. on LSB 54.99645

? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? on USB 54.99645

Regardless of upper or lower, no change. Does that make more sense ? When I looked before setting it, I noticed it wasn't on 10.000 MHz so I made very sure this time. Now to measure the 25 clock.

On Wed, Mar 7, 2018 at 7:03 PM, Jerry Gaffke via Groups.Io <jgaffke@...> wrote:

So, in that first instance, the rig is tuned to?54.98977-(32.99388+11.99624) =?9.999650
In the second instance, it is tuned to?54.99647-(56.99305-11.99624) =?9.999660
Since it flipped, we can assume 10mhz is somewhere in the middle, let's assume 9.999655 mhz
I'm betting your 25mhz oscillator will measure to be around? 25.0 * 9.999655/10.0 =?24.9991375 mhz

This little exercise in looking at that transition makes apparent what I think is a bug in that code scrap,?
we need to deal with the case where one or the other frequency is exactly equal to 10.0 mhz.
So code in ubitx_20.ino at line 470 should be edited to read:

? ? if (prev_freq <= 10000000l && frequency > 10000000l)

? ? ? isUSB = true;

? ? if (prev_freq > 10000000l && frequency <= 10000000l)

? ? ? isUSB = false;

I think.

Jerry, KE7ER

On Wed, Mar 7, 2018 at 05:21 pm, Michael Shreeve wrote:

Hopeffuly you see this Jerry, its just for you. but anyone might find this usefull I hope.?

Frequencies on 10mhz lsb Clock 0 54.98977
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? clock 1 32.99388
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? clock 2 11.99624

Frequencies on 10 MHz USB Clock 0 54.99647
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? Clock 1 56.99305
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Clock 2 11.99624?
And as I said in the video, haven't measured the master 25.000 MHz clock. Soon that will happen.?

--

Michael Shreeve N6GRG