The KE0FF GPS Disciplined Wall Clockjoeh/projects/GPSDWC.pdf · The KE0FF GPS Disciplined Wall...
Transcript of The KE0FF GPS Disciplined Wall Clockjoeh/projects/GPSDWC.pdf · The KE0FF GPS Disciplined Wall...
The KE0FF GPS Disciplined Wall ClockBy Joseph Haas, KEØFF
12/10/2019
A while back, I embarked on an endeavor to build a GPS disciplined reference oscillator for my fledgling home lab. It reached some degree of success which meant that I now have a GPS reference in my office that is on nearly all the time. My thoughts turned to what other uses I could find for the data produced by the GPS receiver. Needing a time-of-day clock for my office, this became a natural extension of the project.
First: This is Texas son, so it has to be BIG!
The simple requirements for this clock were that it keep accurate time with little to no operator intervention and that the display digits be LARGE. Oh, and I wanted LED’s so that there were no angle-of-view issues. I often work with reading glasses or no glasses in my lab, and it can be difficult tosee across the room, so I wanted large digits that I could discern without my normal eye wear handy. A quick search on Mouser’s web site revealed that they carried some 4” LED displays. The size was adequate, but at over $25 each, the cost was prohibitive. A broader internet search yielded a handful of sources that were at about ¼ the cost. That was more palatable, so I ordered 4 of them. I also got a small, 4 digit display from Mouser to allow software development to progress while waiting for the real displays.
Clock electronics with temporary 4-digit display
I could have used an NXP LED driver, the MC14489, for the digit segments, but these devices are expensive and somewhat limited in their ability to drive a large display. So, I decided to design an interface that used software to scan the LED segments with a PWM output to modulate the segments for brightness control. In truth, this offered two freedoms of control for brightness (the scan rate can also modulate the LED brightness) but the PWM would run at a much higher rate so as to reduce the interaction between the two sub-systems.
Half of a 1-of-8 MUX was used to address the digits, while an 8-bit GPIO (General Purpose I/O) port was used to drive the segments. Common-anode displays were used, meaning that the address signal was to drive a PFET to supply voltage to the anode, and an NFET was used for each of the segments.
© Joseph M. Haas, 12/10/2019, all rights reserved 1
The PWM brightness signal was applied to the MUX as a secondary enable for modulating the segment brightness.
Second: Seconds
The next ponder-able was the seconds “hand”. I had decided to use the Tiva TM4C123GH6PM “LaunchPad” development board which has an RGB LED that is driven by the MCU. I came up with an8-state sequence of brightness and color variation that operated on a 1-minute cycle. Innovative, but it lacked the presence I was looking for. With a bit of training, you could deduce the current second within a few seconds, but you had to focus on the RGB color and watch it for a few seconds. A quick glance wasn’t very fruitful.
I considered a ring of discrete LEDs. This had a number of drawbacks. One was the number required. To encircle the display (about 16” across) would require over 200 LEDs to satisfy my vision. Beyond that was the infrastructure needed to drive those many individual LEDs with brightness and color variations. The result would have been impressive, but cost and complexity were huge roadblocks.
Then I discovered the NeoPixel. These are small LED devices that feature a set of RGB LED’s (some newer versions feature a white LED as well) and a small microcontroller that accepts a serial, 2-wire, data input which is used to control the individual LEDs in a serial chain that, theoretically, could feature an unlimited number of LED’s (timing constraints coupled with the desired update rate inevitably become the limiting factors for the NeoPixel system). Circling the entire clock was still cost prohibitive,but a smaller ring could be managed, and with only a couple of GPIOs needed to drive them it was an easy compromise. A 16-segment ring device from Adafruit and done.
16-segment NeoPixel ring with machined PVC support
However, 16 is an unfortunate number for a time-keeping device. It is ever-so close to an even multiple of 60, but not nearly close enough to satisfy my OCD. After several stabs, I worked out that one could divide 60 by 8 with a 7.5 second cycle to allow for 8 cycles of 16 LED’s to exactly fill one minute (at 0.46875 sec/LED). The variation of color and circular progression would allow one to determine the
© Joseph M. Haas, 12/10/2019, all rights reserved 2
second relatively quickly (with some foreknowledge of the color order, of course). Not ideal, but workable. By this time, the auxiliary display was in the mix, so a seconds display would generally be available, making the “ring” more of an appendage of aesthetic value rather than a functional artifice.
The GPSDO
I needed the GPS data from the GPSDO . I also wanted to get power from the GPSDO to minimize the number of connections to the clock (ultimately, this morphed into UPS power, since I want to run the GPSDO off of a UPS at some point, so there are now two power inputs to the clock). I didn’t want to punch another hole in the GPSDO chassis, so I shoe-horned the signals into the pinout of the PC debug port (A DSUB-9 connector). An external “Y” cable split off the wall clock and debug PC port. Things were moving along well.
Software to drive the LED segments and integrate the GPS data into the algorithm progressed with relative ease. Before long, I had the beginnings of a clock. However, this is where the feature creep demons began to do their work. The first was innocent enough: a battery-backed real-time clock to act as a time reference proxy for the condition where GPS data was unavailable for some reason. The hardware was simple enough, as was the software.
The next add-on was the auxiliary display. This was to provide an avenue for some of the status data that was present in the GPS data stream. I chose to use the LEDU design from my mobile radio controller project. I had several PCBs available, and found that I could still get LEDs to fit the various sized displays that were used in that design. Of course, that design used the MC14489, so I still ended up using several of those devices. The software was an easy port since I already had a robust design for it using a Silicon Labs 8051 variant. Here, I skipped the dedicated processor, and provided the SPI interface directly from the Tiva processor.
Several “screens” were devised for the AUX DU to display internal clock data for the RTC and GPS. A push-button is used to cycle through the screens. A “title” banner is displayed for a second or so after each screen is engaged. This makes the whole process rather “self-documentary”. Two other switches are used to set and display clock settings for DST, time-zone, and an early GPS status loop which predates the addition of the AUX DU.
While it is not strictly possible to display all alphabetic characters on a 7-segment display, one can comeclose. By mixing upper and lower case characters, one can faithfully represent all but 6 alphabetic characters. The MC14489 is not quite flexible enough to allow this level of representation, but it is still able to represent all but 7. For the characters that can not be represented faithfully, some poetic license is invoked. “T” is represented by “7”, “V” and “W” are represented by “U” (lower case “u” is used for “U”), “K”, “X” are represented by “H” (lower case “h” is used for “H”), “Q” is represented by “9”, and “M” and “N” are both represented by “n”. This can result in some confusion for those not used to the substitutions. However, the relatively narrow data sets mean that the ambiguities that are suggested by these substitutions are generally resolved by the context of the display. Thus, “non” when presented as aday of the week can only be “mon” for Monday.
© Joseph M. Haas, 12/10/2019, all rights reserved 3
The large 7-segment display uses a slightly different segment map for alpha-characters as there is more flexibility to this interface since each segment is controllable in software. The “M” and “N” ambiguity is relieved by placing a “bar” above the “n” to represent “M”, and “T” is represented as a lower case version that is not entirely accurate (a backwards “L” with the center segment activated), but is more easily distinguished from the dual use of the digit “7” that must be employed with the MC14489 implementation.
Under the Hood
The electronics turned out to be rather simple. Most of the active circuits are shown on the second page of the schematic (see the schematic presented at the end of this document). The auxiliary display unit (AUX DU) uses a previously developed PCB (based on the MC14489 LED driver I.C.) with some modifications.
The software started out by counting milliseconds from midnight. This value was then processed to update the displays once a minute. However, the addition of the RTC chip changed this logic considerably. First off, the RTC maintained a reasonably good timebase that was factory trimmed and temperature stable. At the very least, it was much better than the references that are found on the Tiva LaunchPad board. The RTC also featured an output that could be configured at one of the reference divider taps. I chose the 1024 tap as this was very close to the original 1ms interrupt. This became the new reference for the clock logic. While this resulted in some duplication of effort in that the Tiva would run software that accomplished the clock task (already done inside the RTC chip) it would preserve the original logic and thus minimize software rework.
GPS data is provided from the GPSDO as the raw TSIP (a Trimble proprietary protocol) serial stream directly from the GPS receiver using RS-232 signaling. Rather than provide an RS-232 transceiver at the clock end, I used a simple transistor switch to accomplish the level translation. At the baud rate used(9600), this is not likely to be prone to data-integrity issues over the relatively short run (a few feet) between the GPSDO and the clock.
If GPS is connected and valid, the clock logic periodically (every 12 hours) compares the clock state with that of the GPS data. An error value is calculated, which is used to correct the RTC when the system is running open-loop (i.e., no GPS). The core of the clock actually keeps time in UTC, which (atthe time of this writing) is about 18 seconds ahead of GPS time, which is accounted for in the error calculation. Time-zone and DST features are applied when the display is updated.
The last flourish was a light sensor to allow the LEDs to be auto-dimmed. I’ve used LEDs in the past aslight sensors (an idea I must credit to Forrest M. Mims, III) but in this case, I purchased a purpose built sensor which was a photo-sensitive transistor operated as an emitter follower. The output of the sensor fed to an A/D input on the Tiva MCU, and software cleaned up the data to determine when to dim the LEDs. The dynamic range turned out to be fairly narrow, so I had to tweak the software a bit to get it right. I also had to tweak the sensor mounting to keep it from seeing the light from the LEDs themselves. The presence of the “smoked” lens further complicated this task. The feature was actually working quite well until the lens was attached. The reduction of transmitted light, and internal reflections conspired to increase the tweak-factor.
© Joseph M. Haas, 12/10/2019, all rights reserved 4
The Mechanics of the Electronics
The 4” displays finally arrived and I was forced to confront the question of how to mount them to a common substrate. A PCB was a natural choice, but as mentioned earlier, the area covered by the 4” digits was on the order of 16” by 6”. That is a lot of PCB (i.e., a lot of cost). Because of this, I discarded the idea of a PCB, and decided to use a metal plate with access cut-outs for the digit leads. But how to secure the digits?
The in-process back-plate for display support, an old HP salvage item
The devices featured a pair of voids between the segments. By inserting a parallelogram-shaped piece of material and securing with epoxy, holes for machine screws could be provided which would allow thedigits to be secured to the metal plate from behind. I secured the services of a couple of friends to 3D print the inserts and used 4-40 melt-nuts to provide a threaded receptacle for machine screws.
Back-side view of 4”, 7-segment display with mounting blocks installed
© Joseph M. Haas, 12/10/2019, all rights reserved 5
BOOMSKI, It’s a Clock!
I now had the skeleton of the clock with all of the necessary elements. My wife caught a glimpse of it and declared that it looked like a bomb clock. I tried to convince her that no one would make a bomb clock using 4” LEDs – no one outside of Hollywood, at least – but she was adamant. Fortunately, she didn’t call the FBI (well, I’m pretty sure she didn’t).
I generally go for the “industrial look”. The innards of a military naval vessel would be my perfect home decorating motif. With this in mind, I did want a certain aesthetic for the clock enclosure – wood being my preference in this case. I like having some of the electronics exposed under the front lens, but I want the enclosure to look, well, “nice”. While I am no stranger to woodwork, and am not half-bad at it, I wasn’t looking forward to the undertaking, even if it was to be relatively simple. So, I enlisted the help of another of my friends who had a real, live, woodworking shop. For the cost of lunch, he was happy to build to my specifications.
Early build stage of the clock internal frame (the central gap is for the not-yet installed colon section)
The result was, overall, what I was shooting for, which is an unfortunate rarity for my projects. While the software goes to great lengths to complicate the task, the clock works very well (another rarity) and now leaves me with no excuse for staying too late in my home office.
© Joseph M. Haas, 12/10/2019, all rights reserved 6
The finished clockThere is no AM/PM indicator...this is a 24hr clock, son!
The auxiliary display shows the date: Saturday, May 11, 2019.The seconds ring indicates 13 seconds, a slight mis-alignment
from the 12 seconds shown. The 8 cycle progression is:off, red, green, yellow, blue, pink, cyan, and white.
The main display colon dots blink in unison when GPS isactive, but alternate otherwise.
© Joseph M. Haas, 12/10/2019, all rights reserved 7
1 2 3 4 5 6
A
B
C
D
654321
D
C
B
A
Title
Number RevisionSize
Orcad C
Date: 12-May-2019 Sheet of File: C:\Users\User\Documents\1ffsys\10MHz GPS Slave\Wall Clock HW\GPSWallClock.ddbDrawn By:
Main sch page
SCH, CLOCK, WALL, GPSD
-1 2
ZONE REV DESCRIPTION DATE APPROVED
ALL - GPS Wall Clock - IR
REVISIONS
01/02/2019 ke0ff
MCUMCU.sch
DUDU.sch
a
b
c
d
e
f
g
h
a7
b6
c4
e2
ca11
f9
g10
h5
d3
ca28
DS1
Hr 10's
a
b
c
d
e
f
g
h
a7
b6
c4
e2
ca11
f9
g10
h5
d3
ca28
DS2
HR 1's
a
b
c
d
e
f
g
h
a7
b6
c4
e2
ca11
f9
g10
h5
d3
ca28
DS3
MIN 10's
a
b
c
d
e
f
g
h
a7
b6
c4
e2
ca11
f9
g10
h5
d3
ca28
DS4
MIN 1's
DS5
Colon1
DS6
Colon2
SW1TZone/DST
SW2STATUS
SW3DU-MODE
DI2
DO3
GND4
+5V1
M2
SECONDS HAND
NEO Pixel Ring (AdaFruit)
1
23
4
567
1
23
4
567
1
23
4
567
1
23
4
56
7
1
23
4
56
7
1
23
4
567
1
23
4
567
1
23
4
567
1
23
4
56
7
1
23
4
567
1
23
4
567
1
23
4
567
1
23
4
567
1
23
4
56
7
1
23
4
567
1
23
4
567
grnbrn
red
orgyel
blu
vio
gry
redbrn
grn
blkwht
blu
vio
gry
vio
blu
brn
red
org
yel
red
brn
blkwht
brn
red
org
yel
redbrn
blkwht
brn
red
org
yel
redbrn
blk
wht
To MCU P3 16p ribbon (color coded)
org
grn To MCU P?
To MCU P?
grn
4p SIP
7p Molex
vio
gry
wht
blk
grn
blu
6p 2mm
2p SIP
vio
gry
wht
blk
3p Molex
grn
blu
To light sensor, AUX DU
org
grn
3p SIP
To MCU P5
7p Molex
7p Molex
7p Molex
7p Molex
7p Molex
7p Molex 7p Molex
7p Molex
1 2 3 4 5 6
A
B
C
D
654321
D
C
B
A
Title
Number RevisionSize
Orcad C
Date: 12-May-2019 Sheet of File: C:\Users\User\Documents\1ffsys\10MHz GPS Slave\Wall Clock HW\GPSWallClock.ddbDrawn By:
Main PCB
SCH, CLOCK, WALL, GPSD
-2 2
+3V3J1-01
PB5J1-02
PB0J1-03
PB1J1-04
PE4J1-05
PE5J1-06
PB4J1-07
PA5J1-08
PA6J1-09
PA7J1-10
VBUSJ3-01
GNDJ3-02
PD0J3-03
PD1J3-04
PD2J3-05
PD3J3-06
PE1J3-07
PE2J3-08
PE3J3-09
PF1J3-10
GNDJ2-01
PB2J2-02
PE0J2-03
PF0J2-04
RSTJ2-05
PB7J2-06
PB6J2-07
PA4J2-08
PA3J2-09
PA2J2-10
PF2J4-01
PF3J4-02
PB3J4-03
PC4J4-04
PC5J4-05
PC6J4-06
PC7J4-07
PD6J4-08
PD7J4-09
PF4J4-10
dbUSB USB
SW1
SW2
RST
M1
TM4C123GH6PM_LP
A1
B2
C3
G16
G2A4
G2B5
Y015
Y114
Y213
Y312
Y411
Y510
Y69
Y77
U2
74HC238
1
32
Q9BSH-103
1
32
Q13
FDN-358P
R5
909
1
32
Q10BSH-103
1
32
Q14FDN-358P
R6
909
1
32
Q11BSH-103
1
32
Q15
FDN-358P
R7
909
1
32
Q12BSH-103
1
32
Q16FDN-358P
R8
909
CA1
CA2
CA3
CA4
1357
9111315
2468
10121416
P3
7SEG DU
+5V
VIN1
VOUT2
ON5
GND3
FB4
U1
LM2576HV-ADJP10094
D3SMBSR1010P10097
R19.31K
R23.01K
+ C3330uF
16V
+ C2
47uF63V
L1
330uHP10093
FB1
33uH
C10.1uF50V
2 1
D1
MRA4003P10031300V1A
12
3
P2
EXT PWR+12V
2 1
D2
MRA4003P10031300V
1A
1
35
7
9
2
46
8
10
P1
GPSDO
1
35
7
9
2
46
8
10
P4
AUX DU
1
23
4
567
P5
MISC I/O
GPSTXD
PC6PC7
PE5
digsel0digsel1
pwm7seg
E-DRVC-DRVCA1CA3
B-DRVF-DRV
PF4
D-DRVP-DRVCA2CA4
A-DRVG-DRV
NPXL_DO
+5V
ecca1ca3
bf
sw1
dpca2ca4
agnpxl_do
+5V
PF1
1
24
53
U474AHCT1G08
npxl_do
PD3PD2 PA5
PA2
csbcsa mosi
spck
+5V
+5V
PF0
PF3
sw2
sw3
R102.5K
R112.5K
C410uF
PE4 vsens
+5V+3.3V
PB5 fPB0 aPB1 bPE4 csb
PE5 pwm7segPB4 ePA5 mosiPA6 /rtcintPA7 /rtc_cs
PF3 sw3PB3 dPC4 gpstxd
PC6 digsel0
PC7 digsel1
PF4 sw1
PD2csa
PD3csb
PF1npxl_do
PA2spck
PB2c
PF0sw2
PB7p
PB6gPA4rtc_clkPA3miso
1
23
Q172N2222A
R20
10K
R2110K
+3.3V
PC4gpstxd
1
32
Q1BSH-103
R12
100
1
32
Q2BSH-103
R13
100
1
32
Q3
BSH-103
R14
100
1
32
Q4BSH-103
R15
100
PB0
PB1
PB2
PB3
A-DRV
B-DRV
C-DRV
D-DRV
SCL1
SDI2
SDO3
/CE4
IFS5
/TS6
CLKO7
Vss8
Vdd16
Vbat15
BBS14
/INT13
n/c12
n/c11
n/c10
n/c9
U3
PF2129T
BT1
BATTERYC70.1uF
C60.1uF
C510uF
+3.3V
R22
20K
+3.3V
PA2
PA5
PA3
PA7
PA4
PA6
spck
mosi
miso
rtc_cs
npxl_do
/rtx_int
USB COM/Debug
R9
100
R3 100
R4 100
TVS1
15V
+12V
+12V
P1 connects to a DB9
IDC via 0.05" ribboncable. This DB9 connectsto the GPSDO unit to bring in GPS TSIP dataand +12V power.
C8
0.01uF
C9
0.01uF
C40.01uF
TVS
R2510K
+3.3V
R2410K
+3.3V
R2310K
LIGHT SENSE
1
32
Q5BSH-103
R16
100
1
32
Q6BSH-103
R17
100
1
32
Q7
BSH-103
R18
100
1
32
Q8BSH-103
R19
100
PB4
PB5
PB6
PB7
E-DRV
F-DRV
G-DRV
P-DRV
1 2 3 4 5 6
A
B
C
D
654321
D
C
B
A
Title
Number RevisionSize
Orcad C
Date: 12-May-2019 Sheet of File: C:\Users\User\Documents\1ffsys\10MHz GPS Slave\Wall Clock HW\GPSWallClock.ddbDrawn By:
+5V_DU
CD100.1uF
CD90.1uF
CD70.1uF
CD50.1uF
CD20.1uF
CD80.1uF
CD60.1uF
CD40.1uF
CD10.1uF
+5V_DU
Bank19
Bank213
Bank315
Bank416
Bank517
Rx8
/CS10
SCK11
MOSI12
MISO18
VSS14
h19
g20
f1
e2
d4
c5
b6
a7
VDD3
UD10
MC14489
BANK_A1BANK_A2BANK_A3BANK_A4
BANK_A5
/CSABSCK_DUMOSI_DU
+5V_DU
A_aA_bA_c
A_dA_eA_fA_gA_h
RD7845
Bank19
Bank213
Bank315
Bank416
Bank517
Rx8
/CS10
SCK11
MOSI12
MISO18
VSS14
h19
g20
f1
e2
d4
c5
b6
a7
VDD3
UD11
MC14489
BANK_B1BANK_B2BANK_B3BANK_B4BANK_B5
/CSABSCK_DU
+5V_DU
B_aB_bB_cB_dB_e
B_fB_gB_h
RD8845
Bank19
Bank213
Bank315
Bank416
Bank517
Rx8
/CS10
SCK11
MOSI12
MISO18
VSS14
h19
g20
f1
e2
d4
c5
b6
a7
VDD3
UD13
MC14489
BANK_D1BANK_D2BANK_D3BANK_D4
BANK_D5
/CSDESCK_DUMOSI_DU
+5V_DU
D_aD_bD_c
D_dD_eD_fD_gD_h
RD11845
Bank19
Bank213
Bank315
Bank416
Bank517
Rx8
/CS10
SCK11
MOSI12
MISO18
VSS14
h19
g20
f1
e2
d4
c5
b6
a7
VDD3
UD14
MC14489
BANK_E1BANK_E2BANK_E3BANK_E4BANK_E5
/CSDESCK_DU
+5V_DU
E_aE_bE_cE_dE_e
E_fE_gE_h
RD12845
+5V_DU
/CSABp
/CSDEp
/CSAB
/CSDE
+5V_DU
+5V_DU
/SCK_DU
/MOSI_DU
SCK_DU
MOSI_DU
a
b
c
d
e
f
g
h
k
m
n
p
j
j15
k3
m2
n1
p4
cc1141617
18
a11
b10
c8
d6
e5
f12
g7
h9
cc213
DS1
HDSP-523E
a
b
c
d
e
f
g
h
a7
b6
c4
d2
e1
f9
g10
h5
cc13
cc28
DS2
HDSP-513A
a
b
c
d
e
f
g
h
a14
b13
c8
d7
e6
f1
g2
h9
cc14
cc212
DS7
SC03-12YWA
A_aA_b
A_cA_dA_eA_fA_g
B_aB_bB_cB_dB_e
B_fB_g
BANK_A1
BANK_A2BANK_A3BANK_A4
BANK_A5
BANK_B1 BANK_B2 BANK_B3
BANK_B4BANK_B5
A_aA_b
A_cA_dA_eA_fA_g
a
b
c
d
e
f
g
h
a7
b6
c4
d2
e1
f9
g10
h5
cc13
cc28
DS3
HDSP-513A
A_aA_b
A_cA_dA_eA_fA_gA_h
a
b
c
d
e
f
g
h
a7
b6
c4
d2
e1
f9
g10
h5
cc13
cc28
DS4
HDSP-513A
A_aA_bA_cA_dA_e
A_fA_g
a
b
c
d
e
f
g
h
a7
b6
c4
d2
e1
f9
g10
h5
cc13
cc28
DS5
HDSP-513A
a
b
c
d
e
f
g
h
a7
b6
c4
d2
e1
f9
g10
h5
cc13
cc28
DS6
HDSP-513A
B_aB_bB_cB_dB_e
B_fB_g
B_aB_b
B_cB_dB_eB_fB_g
a
b
c
d
e
f
g
h
a14
b13
c8
d7
e6
f1
g2
h9
cc14
cc212
DS8
SC03-12YWA
B_aB_b
B_cB_dB_eB_fB_g
a
b
c
d
e
f
g
h
a14
b13
c8
d7
e6
f1
g2
h9
cc14
cc212
DS9
SC03-12YWA
B_aB_b
B_cB_dB_eB_fB_g
Offset 1 GHz 100 MHz 10 MHz 1 MHz
100 KHz 10 KHz 1 KHz
1 Hz10 Hz100 Hz
A_a
A_bA_c
A_d
MAIN BAND FREQUENCY (red)
a
b
c
d
e
f
g
h
a14
b13
c8
d7
e6
f1
g2
h9
cc14
cc212
DS10
DNP
1 GHz
SUB BAND (yellow) FREQUENCY & S/RF METERS
BANK_D1BANK_D2
BANK_D3BANK_D4BANK_D5
C_aC_b
C_c
BANK_E1BANK_E2BANK_E3BANK_E4
BANK_E5
a
b
c
d
e
f
g
h
a14
b13
c8
d7
e6
f1
g2
h9
cc14
cc212
DS11
SC03-12YWA
100 MHz
D_aD_bD_cD_dD_e
D_fD_g
a
b
c
d
e
f
g
h
a14
b13
c8
d7
e6
f1
g2
h9
cc14
cc212
DS12
SC03-12YWA
10 MHz
D_aD_bD_cD_dD_e
D_fD_g
a
b
c
d
e
f
g
h
a14
b13
c8
d7
e6
f1
g2
h9
cc14
cc212
DS13
SC03-12YWA
1 MHz
D_aD_bD_cD_dD_e
D_fD_g
a
b
c
d
e
f
g
h
a14
b13
c8
d7
e6
f1
g2
h9
cc14
cc212
DS14
SC03-12YWA
100 KHz
D_aD_b
D_cD_dD_eD_fD_g
a
b
c
d
e
f
g
h
a14
b13
c8
d7
e6
f1
g2
h9
cc14
cc212
DS15
SC03-12YWA
10 KHz
a
b
c
d
e
f
g
h
a14
b13
c8
d7
e6
f1
g2
h9
cc14
cc212
DS16
SC03-12YWA
1 KHz
100 Hz 10 Hz 0.1 Hz
E_aE_b
E_cE_dE_eE_fE_g
MAIN BAND CTCSS (green)1 Hz
E_aE_bE_c
E_dE_eE_fE_g
E_aE_bE_c
E_dE_eE_fE_g
E_aE_bE_c
E_dE_eE_fE_g
Special Fn
a
b
c
d
e
f
g
h
a7
b6
c4
d2
e1
f9
g10
h5
cc13
cc28
DS17
ACSC02-41
a
b
c
d
e
f
g
h
a7
b6
c4
d2
e1
f9
g10
h5
cc13
cc28
DS18
ACSC02-41
a
b
c
d
e
f
g
h
a7
b6
c4
d2
e1
f9
g10
h5
cc13
cc28
DS19
ACSC02-41
a
b
c
d
e
f
g
h
a7
b6
c4
d2
e1
f9
g10
h5
cc13
cc28
DS20
ACSC02-41
M1
MTGD1
M1
MTGD2
M1
MTGD3
M1
MTGD4
12345
6789
10
JD1
DU I/O
A_h
D_aD_b
D_cD_dD_eD_fD_g
E_aE_bE_c
E_dE_eE_fE_gE_h
BANK_C1
LED23
SpFn
BANK_A1
123
456789
10
JX2
SPARE
1
24
53
UD574AHCT1G08
1
24
53
UD674AHCT1G08
1
24
53
UD774AHCT1G08
1
24
53
UD874AHCT1G08
Jumper added at assy
Jumper added at assy
1 1
-LEDU (mod'fd UX89DU)
JD1 is placed on solder side. The pinoutshown reflects this installation and isrelative to the solder side connector NOTthe PCB layout silkscreen.
+5V_DUGND
GND
+5V_DU
E_hE_hE_h
D_h
D_h
A_eA_p
A_g
A_f
DS1 is a 2 digit version with cut-jump
added to complete the 2nd digitconnection.
/CSABp
/CSDEp
/SCK_DU
/MOSI_DU
+5V_DU
GND
12
QD1
EAALST05RDMA0
OPTO_N
OPTO_P
Terminated to a flying-lead connector
SCH, CLOCK, WALL, GPSD
RDx1
100
RDx2
100
RDx3
100
CDx1100pF
CDx2100pF
CDx3100pF