John
Yes I did go through the code looking for the touch screen. Like you I
wanted to know how it was used. What magical stuff might it allow. Well
none. :-)
It does take at least 2 good decodes to display time as I recall.
Regards
Paul.
On Sun, Nov 15, 2020 at 3:06 AM John C. Westmoreland, P.E. <
Hello Time Nuts/Paul,
Yes - I know you have said that - the point was/is I wasn't sure there was
something in the code or not that could be calling some of the
touch screen functions - if you said you scrubbed that and I didn't
understand - thanks for doing that.
I was wondering - using the Storm
John I mentioned in an earlier post the touchscreen is not used and there
is nothing in the code that I see. I have no wires connected. Display is
stable.
On Fri, Nov 13, 2020 at 11:09 AM John C. Westmoreland, P.E. <
j...@westmorelandengineering.com> wrote:
> Hello Time Nuts,
>
> Paul, the wiring
Hello Time Nuts,
Paul, the wiring harness I made is longer than 6" - not by much - but I'll
shorten those and see if it clears it up.
I thought the same thing - maybe the display could be flaky - or maybe
strange things can happen too if in
the software the touch screen part is enabled but the wir
I kind of wonder if you don't have a flakey display. I did not add the
terminating R and everything has always worked fine on the display. After I
quit using the 3" jumper cables to the audio card and stacked the modules,
the audio worked correctly.
My display is on a set of 6" jumpers and has been
John:
I suggest you try Chris Howard's
https://github.com/chris-elfpen/Teensy4WWVBsdr
You might have to adjust the I/O pins for Teensy 4.1 vs 4.0
I am having no problems with the display once I put in the source
termination resistor.
Been running for multiple days, so far.
--- Graham
On Tue, Nov
Hello Time Nuts,
I've been running some tests - I just had the screen 'white-out' problem
happen again - I have a termination resistor on the SCK line (pin 13 on the
Teensy 4.1) -
so it appears this is related to the TFT screen updates - maybe a pixel
write going out of bounds. The Teensy is stil
Graham that is the alternate approach. The new suggested KD2BD vcTCXO works
very well. Its 10 MHz and readily available. But then the old divider
chains are needed. The KD2BD method works well if you have plenty of solder.
First mixer is 50 KHz LO. Result 10 KHz IF.
10 KHz IF gain
Second Mixer is a
Paul:
It might be easier to relegate that function to hardware.
A simple TC-VCO that drives the sampling clock for the ADC and is steerable
for frequency/phase lock from the CPU would allow you to build a
synchronous receiver without working about locking the CPU clocking system
to anything.
---
No time to experiment the last few days as the weather has been great and
have to get outside stuff done. That said trying to tease apart how to
create a lockable NCO in the teensy.
Its not clear to me that I can create a sine wave oscillator and drive that
out to a pin to see stability and adjustm
Hello Graham and Fellow Time Nuts,
I did what Paul had mentioned as well - and that appeared to clear up the
immediate screen issues but I will
insert a termination resistor as well as Graham has suggested.
I looked on the PJRC forum as well - and it appears there has been a lot of
discussion and
John W:
Regarding your Teensy WWVB receiver display issues.
The Teensy does not have a source termination resistor on the SPI clock.
Add a 50 Ohm resistor (value not critical, anything from 33 to 75 will
work) in series with the SPI Clock signal, as physically close to the
Teensy as practical.
Thi
gt; > >> >> >> > >
> > >> >> >> > > Has anyone been successful getting WWVB to decode using the
> > >> example
> > >> >> >> for
> > >> >> >> > > DCF77 and making the changes for W
t;
> >> >> >> > > Chris has his own approach - it's interesting - but on my
> setup
> >> at
> >> >> >> least
> >> >> >> > I
> >> >> >> > > haven't been successful with it
ybe it's my antenna - not
>> sure
>> >> >> just
>> >> >> > > yet.
>> >> >> > > Also - my screen eventually 'whites-out' after running that for
>> a
>> >> >> while -
>> >&
; But, with the DCF77 approach - it appears to identify bits OK -
> >> with
> >> >> the
> >> >> > > code having only minimal changes - so I'd like to go down that
> >> path.
> >> >> > >
> >> >> > >
- and not sure it's
> worth
> > >> > > anything other than looking at some of the data that's being
> dumped.
> > >> > > https://github.com/jwestmoreland/Teensy-DCF77
> > >> > >
> > >> > > For DC7FF - the AM is
#x27;s being
>> dumped.
>> >> > > https://github.com/jwestmoreland/Teensy-DCF77
>> >> > >
>> >> > > For DC7FF - the AM is just 0.2ms (1) and 0.1ms (0) with no AM at
>> the
>> >> > minute
>> >> > >
rk
> >> > the
> >> > > end of current minute/beginning of next minute.
> >> > >
> >> > > The DCF77 code seems to take some advantage of the signal
> level/timing
> >> > and
> >> > > the dimensions of the TFT di
x27;m looking at this wrong - I guess that isn't
>> > > a big deal until you try to deal with the marker timing for WWVB - of
>> > > course I could be looking at this wrong right now too.
>> > >
>> > > Maybe trying something like the Goertzel algor
ke KE9NS has done
> in
> > > his work with WWV is worth taking a look at too with
> > > this setup.
> > >
> > > 73's,
> > > John
> > > AJ6BC
> > >
> > >
> > >
> > >
> > >
> > > On Sun, Nov 1, 2020
gt; >
> >
> >
> > On Sun, Nov 1, 2020 at 10:50 AM Mike Feher wrote:
> >
> > > Too bad I am an old retired hardware engineer and know nothing about
> > these
> > > new SW controlled devices. Have Fun - Regards - Mike
> > >
> > > Mike B
On 11/2/20 6:59 PM, John C. Westmoreland, P.E. wrote:
Hello Time Nuts,
I have a question -
Has anyone been successful getting WWVB to decode using the example for
DCF77 and making the changes for WWVB?
Yes.
Maybe you mean other than me?
Chris
__
eher, N4FS
> > 89 Arnold Blvd.
> > Howell NJ 07731
> > 848-245-9115
> >
> > -Original Message-
> > From: time-nuts On Behalf Of paul
> swed
> > Sent: Sunday, November 1, 2020 12:48 PM
> > To: Discussion of precise time and frequency measuremen
: Discussion of precise time and frequency measurement <
> time-nuts@lists.febo.com>
> Subject: Re: [time-nuts] WWVB teensy BPSK early experiments
>
> John sent the link on the teensy wwvb AM receiver. It can easily be
> shifted to other frequencies. Using the work Frank dcf77 a
:48 PM
To: Discussion of precise time and frequency measurement
Subject: Re: [time-nuts] WWVB teensy BPSK early experiments
John sent the link on the teensy wwvb AM receiver. It can easily be shifted to
other frequencies. Using the work Frank dcf77 and then Chris wwvb did with the
PJRC audio
ace a 90
degree phase change or delay needs to occur.
Or as suggested a hilbert transform.
Regards
Paul
WB8TSL
On Sun, Nov 1, 2020 at 5:35 AM wrote:
> Thanks John.
>
> Ray,
> AB7HE
>
> Original Message ----
> Subject: Re: [time-nuts] WWVB teensy BPSK earl
Thanks John.
Ray,
AB7HE
Original Message
Subject: Re: [time-nuts] WWVB teensy BPSK early experiments
From: "John C. Westmoreland, P.E."
Date: Sat, October 31, 2020 9:06 pm
To: Discussion of precise time and frequency measurement
Ray,
https://github.com/ch
; Ray,
> AB7HE
>
> ---- Original Message ----
> Subject: Re: [time-nuts] WWVB teensy BPSK early experiments
> From: Bob kb8tq
> Date: Sat, October 31, 2020 11:42 am
> To: Discussion of precise time and frequency measurement
>
>
> Hi
>
> …..errr…
On 10/31/20 7:26 PM, Bob kb8tq wrote:
Hi
On Oct 31, 2020, at 9:45 PM, jimlux wrote:
On 10/31/20 4:46 PM, Bob kb8tq wrote:
Hi
Looking at the data sheet for the MCU, they really do want 24 MHz and that’s
about it. I suspect you would
do better to take your 10 MHz OCXO and run it into one of
Hi
> On Oct 31, 2020, at 9:45 PM, jimlux wrote:
>
> On 10/31/20 4:46 PM, Bob kb8tq wrote:
>> Hi
>> Looking at the data sheet for the MCU, they really do want 24 MHz and that’s
>> about it. I suspect you would
>> do better to take your 10 MHz OCXO and run it into one of the frequency
>> conve
Hi
The gizmo you want is a hot air rework tool. They are not all that expensive
( < $200 for a fancy one, quite a bit less for a simple one). They normally
come with a bunch of tips. That lets you “focus” the heat on the part you want
to pull.
One of an infinite number, randomly chosen:
https:/
On 10/31/20 5:42 PM, paul swed wrote:
Jim
Thanks for the details. I took a serious look at popping the xtal out and
am afraid its a bit beyond me since there are 4 pads that need to be
heated. I have worked on very small stuff under the microscope. But this
seems problematic. I sort of thought al
On 10/31/20 4:46 PM, Bob kb8tq wrote:
Hi
Looking at the data sheet for the MCU, they really do want 24 MHz and that’s
about it. I suspect you would
do better to take your 10 MHz OCXO and run it into one of the frequency
converter chips to get the 24.
Then feed that into the board. One more chi
Sorry Bob. I meant to address this question to Paul.
"Things already accomplished by Chris in the wwvb AM receiver"
Is there a link to the AM receiver? Curious as to what that looks like.
Ray,
AB7HE
Original Message
Subject: Re: [time-nuts] WWVB teensy BPSK early e
Bob,
"Things already accomplished by Chris in the wwvb AM receiver"
Is there a link to the AM receiver? Curious as to what that looks like.
Ray,
AB7HE
Original Message
Subject: Re: [time-nuts] WWVB teensy BPSK early experiments
From: Bob kb8tq
Date: Sat, October 3
Jim
Thanks for the details. I took a serious look at popping the xtal out and
am afraid its a bit beyond me since there are 4 pads that need to be
heated. I have worked on very small stuff under the microscope. But this
seems problematic. I sort of thought all the bits would get upset. No free
lunc
Hi
Looking at the data sheet for the MCU, they really do want 24 MHz and that’s
about it. I suspect you would
do better to take your 10 MHz OCXO and run it into one of the frequency
converter chips to get the 24.
Then feed that into the board. One more chip, but you now don’t have a bunch of
On 10/31/20 11:42 AM, Bob kb8tq wrote:
Hi
…..errr…..
Can you pull the clock oscillator off the Teensy board? (Yes, the soldering
iron would be involved).
Will the clock input to the MCU accept something like 10 MHz? If so solder
on a cable ….
At that point whatever the Teeny does is locked to
Good suggestions. The Teensy runs at some 580 MHz. I thought on the crystal
I had seen something like 166. These things are seriously small. But the
schematic shows its 24 MHz.
Inside the teensy is a PLL that creates the high speed system clock. So
thats potentially a good answer. Use something lik
Just a thought, Paul --
If the teensy can generate an output that is accurate but jittery, you
could use a simple PLL to lock a crystal to that with a time constant
that smooths out the jitter.
John
On 10/31/20 1:47 PM, paul swed wrote:
Hello to the group. Wanted to update the everyone
Hi
…..errr…..
Can you pull the clock oscillator off the Teensy board? (Yes, the soldering
iron would be involved).
Will the clock input to the MCU accept something like 10 MHz? If so solder
on a cable ….
At that point whatever the Teeny does is locked to the 10 MHz. If that comes
from one of
Hello to the group. Wanted to update the everyone thats interested in
what I have learned so far on the Teensy and audio codec. No complete
solution yet. Much of my experimentation and knowledge has come from Frank
and Chris, who built the complete wwvb AM time receiver. In addition
and important i
43 matches
Mail list logo
