Very helpful - thanks to Tom & Tom. This unit does not have VR modules - the power controller is one circuit board about 6" long, and it has been badly burnt.
Schematic solves identity of CAPSUL 0616 black box - this is the backlight driver for the LCD backlight HV supply. Although there are 5 connections to the front display board wheras the schematic suggests only 4. The "Start A+ Source" seems to +10V <200mA . "Run A+ Source" is also unregulated and no voltage specified, although since 1N914s are used, the current can't be much. I see "Start A+ Source", "Run A+ Source", and A+ sink labels, but no indication as to what goes in between. Maybe the only purpose is powering U1. OSC B+/RTN - isolated unregulated. Is this 24V? That seems unexpected because C27 is only rated at 25V. There seems to be +5V unreg major current. I'll have to figure out the current. Linear VRs are listed as 78XX and 79XX and 7905 (U6-8) - they are not populated in this unit. Someone already replaced CR15 in this unit with a much larger diode but it looks like CR14 was on fire at some point, as were R9, U1 and C1. They took out neighboring components when they went. Also, CR2 is definitely not a 1N4002 so that got replaced at some point with a larger part. Black soot on the topside, multiple carbonized components, and vaporized traces on the bottom suggest to me it is not worth the time to repair this thing. Remaining questions- 1) OSC voltage? Did Austron really use 25V caps for a 24V line? The oscillator is clearly labeled 15V but it has a separate LM350T VR. I would guess that 18V would be fine for it but I will check that with bench PS. Maybe the design voltage is 20V? 2) Can I modify the display board to use a standard DC backlight display power supply? 3) What is the purpose of the Start A+ Source and Run A+ Source? Do they have any use outside the power controller board? As a general design strategy, I don't get the purpose of the multiple over/under-voltage circuits, crowbars, and alarms. None of that stuff prevented this thing from going up in smoke. At 10:00 AM 7/6/2020, [email protected] wrote: >Send time-nuts mailing list submissions to > [email protected] > >To subscribe or unsubscribe via the World Wide Web, visit > http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com >or, via email, send a message with subject or body 'help' to > [email protected] > >You can reach the person managing the list at > [email protected] > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of time-nuts digest..." > > >Today's Topics: > > 1. Re: Raspberry Pi NTP server (Steve Platt) > 2. Re: Raspberry Pi NTP server (Tim Shoppa) > 3. HP-5372A and HP-5372A operation with no CRT display. > (Lester Veenstra) > 4. ESE ES-188 Master Clock : Repair (Gregory Beat) > 5. Re: HP-5372A and HP-5372A operation with no CRT display. > (Magnus Danielson) > 6. 5071A (Bill Notfaded) > 7. Re: 5071A (Bob kb8tq) > 8. Re: 5071A (Tom Van Baak) > 9. Austron 2110 schematics? (AC0XU (Jim)) > 10. Re: Austron 2110 schematics? (Tom Van Baak) > 11. Re: Austron 2110 schematics? (Tom Knox) > 12. Success replacing Oncore VP with Synergy SR-6Tf ? (Steve Jones) > 13. Re: HP-5372A and HP-5372A operation with no CRT display. > (Lester Veenstra) > 14. Re: HP-5372A and HP-5372A operation with no CRT display. > (Gary Woods) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Sun, 5 Jul 2020 15:53:00 +0100 >From: Steve Platt <[email protected]> >To: [email protected] >Subject: Re: [time-nuts] Raspberry Pi NTP server >Message-ID: <[email protected]> >Content-Type: text/plain; charset=utf-8; format=flowed > >On 03/07/2020 13:56, Andrew Hancock wrote: >> But here's the weird thing, it starts out okay, from what I can tell, and I >> get 377 for both GPSD and PPS >> >> remote refid st t when poll reach delay offset >> jitter >> ============================================================================== >> *127.127.28.0 .GPSD. 1 l 21 32 37 0.000 98.447 >> 89.508 >> o127.127.22.0 .PPS. 0 l 20 32 17 0.000 -63.468 >> 27.800 > >That's NOT ok, IMHO :-) > >I think the offset and jitter for the PPS server are far too high. >Here's what my Raspberry Pi2 looks like: > >> $ ntpq -p >> ???? remote?????????? refid????? st t when poll reach?? delay offset? >> jitter >> ============================================================================== >> *SHM(0)????????? .SHM.??????????? 0 l??? 7?? 16? 377??? 0.000 -90.737? >> 65.556 >> oPPS(0)????? ? ?? .PPS.????? ? ???? 0 l??? 5?? 16? 377 0.000??? >> 0.002?? 0.002 >> +ntp0... (other NTP servers omitted but 0ffset values were 1 or 2 ms) > >My setup sounds like your original, with a GPS Hat and PPS on a GPIO >line.? The huge difference between your remote servers and your PPS >signal suggest (as others have said) that the timing of your PPS signal >is wrong.? I think that is the cause of your problems. > >Steve > > > > >------------------------------ > >Message: 2 >Date: Sun, 5 Jul 2020 11:14:55 -0400 >From: Tim Shoppa <[email protected]> >To: Discussion of precise time and frequency measurement > <[email protected]> >Subject: Re: [time-nuts] Raspberry Pi NTP server >Message-ID: > <caj_qrvbqpqqg66yxt7ngwdwquzfoklqorptkadulyyr6xg4...@mail.gmail.com> >Content-Type: text/plain; charset="UTF-8" > >Andrew, outlier rejection in NTPD is not the most stable thing in the world. > >You have two local refclocks that are consistently 200ms off from the "rest >of the world" and this is 10 times larger than the round trip delay to the >rest of the world. > >But the local stratum 0 refclock poll interval is ten or twenty times more >frequent than the rest of the world so the local wrong clock gets to >trigger the algorithm ten times as often as the rest of the world. > >The outlier rejection NTPD algorithm goes absolutely bonkers in this case. >Which is good because you see it and fix the actual problem. > >Like David suggested, seeing the 200ms offset, this 200ms is a very common >default PPS pulse width so it almost certainly is triggering off the wrong >edge. > >Tim N3QE > >On Sun, Jul 5, 2020 at 7:50 AM Andrew Hancock < >[email protected]> wrote: > >> Thanks David >> >> I may try that list. >> >> It is odd, it works fine, and then craps out.... >> >> And then it's happy again... >> >> Andrew >> >> -----Original Message----- >> From: time-nuts <[email protected]> On Behalf Of David J >> Taylor via time-nuts >> Sent: 03 July 2020 18:34 >> To: [email protected] >> Cc: David J Taylor <[email protected]> >> Subject: Re: [time-nuts] Raspberry Pi NTP server >> >> A puzzle (so I hope) I'm in the correct place. >> >> I've built myself, many years ago an NTP server, on a RPi 1, which not >> sure if ever ran properly. >> >> It uses a u-blox6 board, connected to the Pi correctly, and PPS to GPIO, >> compiled NTP to include kernel PPS support. >> >> GPS 3D fix is fine, using an outside aerial, there are no issues here >> reported with cgps -s or gpsmon, but recently I've racked mounted all my >> PIs in a network rack. >> >> So I cannot use HaTs anymore, so I cobbled together a GPS ublox6 (same >> module) but using a FT232RL, and connected all the pins correctly, and DCD >> so I can get PPS. >> >> Cgps -s and gpsmon, reports all is well, pps registers correctly... >> >> But here's the weird thing, it starts out okay, from what I can tell, and >> I get 377 for both GPSD and PPS >> >> remote refid st t when poll reach delay offset >> jitter >> >> ============================================================================== >> *127.127.28.0 .GPSD. 1 l 21 32 37 0.000 98.447 >> 89.508 >> o127.127.22.0 .PPS. 0 l 20 32 17 0.000 -63.468 >> 27.800 >> uk.pool.ntp.org .POOL. 16 p - 1024 0 0.000 0.000 >> 0.004 >> +212.23.8.6 195.66.241.2 2 u 129 1024 1 13.266 198.007 >> 3.273 >> +212.23.10.129 85.199.214.99 2 u 134 1024 1 19.693 195.605 >> 3.282 >> +178.62.18.76 85.199.214.100 2 u 135 1024 1 13.804 195.465 >> 3.299 >> +185.120.34.123 85.199.214.98 2 u 130 1024 1 12.808 197.879 >> 3.304 >> +51.68.198.213 85.199.214.102 2 u 132 1024 1 13.534 197.377 >> 3.402 >> +95.215.175.2 178.79.160.57 3 u 131 1024 1 19.722 198.984 >> 3.244 >> >> And then later. >> >> remote refid st t when poll reach delay offset >> jitter >> >> ============================================================================== >> *127.127.28.0 .GPSD. 1 l 20 32 377 0.000 -38.512 >> 43.162 >> x127.127.22.0 .PPS. 0 l 19 32 377 0.000 -159.01 >> 0.949 >> uk.pool.ntp.org .POOL. 16 p - 1024 0 0.000 0.000 >> 0.004 >> +212.23.8.6 195.66.241.2 2 u 255 1024 1 13.615 142.618 >> 1.953 >> +212.23.10.129 85.199.214.99 2 u 261 1024 1 19.799 144.028 >> 3.384 >> +162.159.200.123 10.63.8.8 3 u 258 1024 1 18.501 141.995 >> 3.016 >> +185.53.93.157 81.187.26.174 2 u 258 1024 1 15.385 143.600 >> 3.045 >> -217.114.59.3 33.117.170.50 2 u 259 1024 1 19.927 143.014 >> 3.364 >> +109.74.192.97 85.199.214.99 2 u 255 1024 1 13.578 142.723 >> 1.864 >> >> Which does not look good, notice the x in front of PPS... >> >> And then sometimes.... It borks.. and drops out completely and * and x >> disappear, and all the +. >> >> Then go back to >> >> >> remote refid st t when poll reach delay offset >> jitter >> >> ============================================================================== >> *127.127.28.0 .GPSD. 1 l 27 64 3 0.000 34.096 >> 1.954 >> o127.127.22.0 .PPS. 0 l 26 32 3 0.000 -69.865 >> 14.194 >> uk.pool.ntp.org .POOL. 16 p - 1024 0 0.000 0.000 >> 0.002 >> 212.23.8.6 195.66.241.2 2 u 121 1024 1 13.316 200.644 >> 0.002 >> 212.23.10.129 85.199.214.99 2 u 118 1024 1 19.929 202.213 >> 0.002 >> 178.79.155.116 85.199.214.99 2 u 120 1024 1 13.391 201.057 >> 0.002 >> 185.121.25.242 85.199.214.99 2 u 121 1024 1 14.084 200.964 >> 0.002 >> 81.21.65.169 195.195.221.100 2 u 122 1024 1 17.587 200.121 >> 0.002 >> 178.62.6.8 68.166.61.255 2 u 122 1024 1 13.864 200.580 >> 0.002 >> >> >> I'm beginning to wonder my testing using Meinberg polling every 10 seconds >> is causing the Pi an issue! >> >> remote refid st t when poll reach delay offset >> jitter >> >> ============================================================================== >> *127.127.28.0 .GPSD. 1 l 13 64 377 0.000 144.454 >> 69.663 >> o127.127.22.0 .PPS. 0 l 12 32 377 0.000 59.311 >> 19.278 >> uk.pool.ntp.org .POOL. 16 p - 1024 0 0.000 0.000 >> 0.002 >> 212.23.8.6 195.66.241.2 2 u 491 1024 1 13.316 200.644 >> 0.002 >> 212.23.10.129 85.199.214.99 2 u 489 1024 1 19.929 202.213 >> 0.002 >> 178.79.155.116 85.199.214.99 2 u 491 1024 1 13.391 201.057 >> 0.002 >> 185.121.25.242 85.199.214.99 2 u 492 1024 1 14.084 200.964 >> 0.002 >> 81.21.65.169 195.195.221.100 2 u 493 1024 1 17.587 200.121 >> 0.002 >> 178.62.6.8 68.166.61.255 2 u 493 1024 1 13.864 200.580 >> 0.002 >> >> Stopped monitoring, see if it stops... >> >> Thanks for your comments >> ============================================== >> >> Andrew, >> >> Three thoughts: >> >> - any chance the DCD pulse is the wrong polarity? Triggering on the >> trailing an not the leading edge? Might give errors typically around 100 >> ms (the pulse width), but your errors seem to be more in the 250-300 ms >> range. >> >> - WNRO (week number roll over) issue? >> >> - unless you need stand-alone operation, try commenting out the type 28 >> driver. >> >> I'd suggest the NTP Questions list, but it is /very/ fussy in what e-mail >> provider it accepts. Only one of my four works! >> >> https://lists.ntp.org/listinfo/questions >> >> Cheers, >> David >> -- >> SatSignal Software - Quality software for you >> Web: https://www.satsignal.eu >> Email: [email protected] >> Twitter: @gm8arv >> >> >> _______________________________________________ >> time-nuts mailing list -- [email protected] >> To unsubscribe, go to >> http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com >> and follow the instructions there. >> >> _______________________________________________ >> time-nuts mailing list -- [email protected] >> To unsubscribe, go to >> http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com >> and follow the instructions there. >> > > >------------------------------ > >Message: 3 >Date: Sun, 5 Jul 2020 11:51:22 -0400 >From: "Lester Veenstra" <[email protected]> >To: "'Discussion of precise time and frequency measurement'" > <[email protected]> >Subject: [time-nuts] HP-5372A and HP-5372A operation with no CRT > display. >Message-ID: <00dc01d652e4$2225c4d0$66714e70$@com> >Content-Type: text/plain; charset="iso-8859-1" > >The repair bench is up and successful on repairing the A17 video driver >boards. This involved replacing bad caps. > >If anyone has a bad A17 board, particularly ones with obvious blown >(literally) caps, I would be happy to repair and bench test. > >No cost other than send it to me with a prepaid, pre printed USPS return >label. > >Lester B Veenstra? K1YCM M?YCM W8YCM 6Y6Y >[email protected] > >452 Stable Ln (HC84 RFD USPS Mail) >Keyser WV 26726 > >GPS: 39.336826 N? 78.982287 W (Google) >GPS: 39.33682 N? 78.9823741 W (GPSDO) > > >Telephones: >Home:?????????????????? ? +1-304-289-6057 >US cell??????????????????? +1-304-790-9192 >Jamaica cell:?????????? +1-876-456-8898 >? > > > > > >------------------------------ > >Message: 4 >Date: Sun, 5 Jul 2020 13:42:27 -0500 >From: Gregory Beat <[email protected]> >To: [email protected] >Subject: [time-nuts] ESE ES-188 Master Clock : Repair >Message-ID: <[email protected]> >Content-Type: text/plain; charset=utf-8 > >ESE ES-188 Master Clock : Repair > >Another ESE Master Clock bargain ($100) arrived this summer on the time-nuts >bench, from an eBay dumpster diver/flipper. The ES-188 NTP Referenced Master >Clock/Time Code Generator. >The clock?s internal TCXO is synchronized via the Internet (NTP). > >The ES-188 receives accurate time and date information from a user selected >NTP server and supplies this data to the user in the form of five (5) >different types of time code (SMPTE/EBU, IRIG-B, ASCII, TC89 and TC90) and a >front panel nine-digit display (.56? yellow LEDs). >This Master Clock is used at locations without ability to mount an external >GPS antenna, or facilities that desire an alternative time synchronization >method (not GPS based). >? >FIRST Step, Request the full ES-188 manual, with schematic and parts list, >from ESE Support - who delivers electronically (e-mail attachment). > >Initial bench assessment confirmed the eBay reseller could not differentiate >working, from non-working (Outrageous initial eBay asking price of >$300). >The 6 Volt, 1.3 Ah rechargeable battery and BR-2330 lithium coin cell were >dead (config not retained), as expected. > >The ES-188 has three (3) user access ports on rear panel: >RS-232(serial); USB; and Ethernet provide by Lantronix Xport (IPv4) model. > >The Ethernet port acquired an IP address (DHCP), but did not respond with IP >tools. >ESE provides PC software (Master Control Panel) for RS-232 and USB access from >a PC. >The RS-232 port (MAX233) was not responsive. >The USB port (FTDI FT232BM) was recognized by the PC (Drivers loaded by >Windows 10), BUT odd behavior was observed (worked sometimes). > >Time to open up the ES-188 rack case to visual inspect inside. >The Six (6) electrolytic capacitors in the power supply section were bulging. >An obvious failure of those smoothing capacitors, that provide DC to the >LM317, 7805, and +3.3 volt regulators. >This ES-188 was built ~2008, so the Meritek 85? electrolytics (3300 uFd, 4700 >uFd) used by ESE did not last 12 years. >? >SECOND Step, Order Parts and Install. > >Panasonic EEU-FK radial electrolytic capacitors (25V, 105?) were purchased >from Digi-Key for replacement, that matched the PC board lead spacing (7.50 >mm) and diameter. >The new Panasonic capacitors were shorter (height). > >Looking at the Schematic diagram, the ES-188 main processor is the >87C530QNL-188 (PLCC-52). >This Maxim processor sells for ~$50 (blank, no firmware in ROM). >https://www.mouser.com/datasheet/2/256/DS83C530-DS87C530-1511768.pdf >This microcontroller has multiple I/O lines and supports Intel >8051-instruction set (firmware). >There are three (3) ICs that connect to this processor for external user ports: > >74HCT04 : HEX Inverter, six independent inverter gates >74HCT08 : AND Gate, four independent 2-input AND gates >MAX233CPP : 5 Volt, RS-232 Driver/Receiver > >All three (3) of those chips were damaged, likely from nearby unstable DC >power or an ESD event. >** The surface mounted FTDI FT232BM (USB bridge IC) was NOT damaged. ** > >Replacing the six (6) bad electrolytic capacitors, three (3) bad ICs, and two >(2) new batteries for less than $20 (parts) restored the ES-188 to operation. >The ES-188 then successfully sent IRIG-B time codes to my remote clock display. >? >LAST Step, Configure Master Clock and Operate. > >I configured the ES-188 settings, via its Ethernet port (telnet), on a menu. > >Set the initial Master Clock, Date and Time. >Set the ESE-188 local network address (IPv4), Gateway, and DNS Server. > >For the NTP Primary Server, do not use the NIST or WWV time servers, Use your >local ISP. >For example, my local Comcast/Xfinity (IPv4) server: 73.15.134.22 >For the Secondary Server, select a reliable NTP server. >== > >greg, w9gb > > > > >------------------------------ > >Message: 5 >Date: Sun, 5 Jul 2020 21:32:39 +0200 >From: Magnus Danielson <[email protected]> >To: [email protected] >Subject: Re: [time-nuts] HP-5372A and HP-5372A operation with no CRT > display. >Message-ID: <[email protected]> >Content-Type: text/plain; charset=utf-8 > >Hi Lester, > >Good to hear your progress. > >So, I gather that you managed to successfully repair it, and it was a >capacitor issue that I also had experienced. > >Which caps did fail for you? I think I recall a 50 uF bipolar cap. > >Cheers, >Magnus > >On 2020-07-05 17:51, Lester Veenstra via time-nuts wrote: >> The repair bench is up and successful on repairing the A17 video driver >> boards. This involved replacing bad caps. >> >> If anyone has a bad A17 board, particularly ones with obvious blown >> (literally) caps, I would be happy to repair and bench test. >> >> No cost other than send it to me with a prepaid, pre printed USPS return >> label. >> >> Lester B Veenstra? K1YCM M?YCM W8YCM 6Y6Y >> [email protected] >> >> 452 Stable Ln (HC84 RFD USPS Mail) >> Keyser WV 26726 >> >> GPS: 39.336826 N? 78.982287 W (Google) >> GPS: 39.33682 N? 78.9823741 W (GPSDO) >> >> >> Telephones: >> Home:?????????????????? ? +1-304-289-6057 >> US cell??????????????????? +1-304-790-9192 >> Jamaica cell:?????????? +1-876-456-8898 >> ? >> >> >> >> _______________________________________________ >> time-nuts mailing list -- [email protected] >> To unsubscribe, go to >> http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com >> and follow the instructions there. > > > > >------------------------------ > >Message: 6 >Date: Sun, 5 Jul 2020 11:50:25 -0700 >From: Bill Notfaded <[email protected]> >To: Discussion of precise time and frequency measurement > <[email protected]> >Subject: [time-nuts] 5071A >Message-ID: > <CADToqn0gso=jf35wyan1ffphnb1wh0+prijvvrbnzsy1xoq...@mail.gmail.com> >Content-Type: text/plain; charset="UTF-8" > >If the power is cycled on one of these will it always go into attention >mode yellow until cleared? Or will it go green continuous operation all in >it's own? If one of these has been on the shelf a while is it common for >one even with a good tube to report attention yellow for a while until tube >pumps down and eventually will the yellow clear on it's own? > >Bill > > >------------------------------ > >Message: 7 >Date: Sun, 5 Jul 2020 16:12:06 -0400 >From: Bob kb8tq <[email protected]> >To: Discussion of precise time and frequency measurement > <[email protected]> >Subject: Re: [time-nuts] 5071A >Message-ID: <[email protected]> >Content-Type: text/plain; charset=utf-8 > >Hi > >My recollection is that if power is cycled, it drops out of ?continuous >operation >mode?. There *might* even be BBC footage documenting this ? :) > >Simply put, all of these devices ( 5071 and the other HP atomic standards I >have seen) *only* go into continuous operation when you push a button. Anything >odd that comes along takes them out of this mode. It?s just a flip flop so you >can?t read a lot into it being off. Power line voltage ?out of spec? is one >way >to nuke it (at least on some HP?s ). > >Bob > >> On Jul 5, 2020, at 2:50 PM, Bill Notfaded <[email protected]> wrote: >> >> If the power is cycled on one of these will it always go into attention >> mode yellow until cleared? Or will it go green continuous operation all in >> it's own? If one of these has been on the shelf a while is it common for >> one even with a good tube to report attention yellow for a while until tube >> pumps down and eventually will the yellow clear on it's own? >> >> Bill >> _______________________________________________ >> time-nuts mailing list -- [email protected] >> To unsubscribe, go to >> http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com >> and follow the instructions there. > > > > >------------------------------ > >Message: 8 >Date: Sun, 5 Jul 2020 13:24:14 -0700 >From: Tom Van Baak <[email protected]> >To: [email protected] >Subject: Re: [time-nuts] 5071A >Message-ID: <[email protected]> >Content-Type: text/plain; charset=utf-8; format=flowed > >Bill, > >A 5071A will never go solid-green "continuous operation" on its own. >That solid-green state is set manually from the blinking-green state, by >design. > >This prevents you from seeing green, having a short power failure >overnight, and then you come back in the morning and see green and you >think all is well. The 5061A and 5065A have a similar fail safe. > >The yellow LED means attention, as in something's wrong and it did not >warm up or lock. The internal diagnostics are pretty good so if it gives >up there's a good reason. The error code is available on the front panel >LCD or via SCPI over the RS232 port. Depending on the diagnostic log or >the text of fatal error it's pretty clear when there's no hope. In the >case of leaky tube or ion pump failure there's nothing wrong with trying >again and again and again and again until you give up hope. > >On the other hand if all goes well during warm-up and lock is achieved, >yellow goes out on its own and you get blinking-green. It's up to you >then to manually set it to solid-green. > >/tvb > > >On 7/5/2020 11:50 AM, Bill Notfaded wrote: >> If the power is cycled on one of these will it always go into attention >> mode yellow until cleared? Or will it go green continuous operation all in >> it's own? If one of these has been on the shelf a while is it common for >> one even with a good tube to report attention yellow for a while until tube >> pumps down and eventually will the yellow clear on it's own? >> >> Bill >> > > > > >------------------------------ > >Message: 9 >Date: Sun, 05 Jul 2020 14:34:08 -0600 >From: "AC0XU (Jim)" <[email protected]> >To: [email protected] >Subject: [time-nuts] Austron 2110 schematics? >Message-ID: <[email protected]> >Content-Type: text/plain; charset="us-ascii" > >Time Nuts- > >I have an Austron 2110 with a severely toasted power controller board. >Probably not repairable. I plan to build a substitute with a more modern >design. > >Does anyway have schematics? I noticed correspondence between Magnus >Danielson and Harald Hauglin some years ago. Did the manula or schematics ever >get posted? > >Thanks in advance- >Jim > > > > >------------------------------ > >Message: 10 >Date: Sun, 5 Jul 2020 14:33:13 -0700 >From: Tom Van Baak <[email protected]> >To: [email protected] >Subject: Re: [time-nuts] Austron 2110 schematics? >Message-ID: <[email protected]> >Content-Type: text/plain; charset=utf-8; format=flowed > >Jim, > >For the power supply see: http://leapsecond.com/museum/au2110b/ps.htm > >Let me know if you need more pages from the manual. > >For sample LCD readings see: http://leapsecond.com/museum/au2110b/lcd.htm > >/tvb > > >On 7/5/2020 1:34 PM, AC0XU (Jim) wrote: >> Time Nuts- >> >> I have an Austron 2110 with a severely toasted power controller board. >> Probably not repairable. I plan to build a substitute with a more modern >> design. >> >> Does anyway have schematics? I noticed correspondence between Magnus >> Danielson and Harald Hauglin some years ago. Did the manula or schematics >> ever get posted? >> >> Thanks in advance- >> Jim >> >> >> _______________________________________________ >> time-nuts mailing list -- [email protected] >> To unsubscribe, go to >> http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com >> and follow the instructions there. >> > > > > >------------------------------ > >Message: 11 >Date: Sun, 5 Jul 2020 21:46:38 +0000 >From: Tom Knox <[email protected]> >To: Discussion of precise time and frequency measurement > <[email protected]> >Subject: Re: [time-nuts] Austron 2110 schematics? >Message-ID: > > <cy4pr04mb0472c776507d751c9c6dbcf6df...@cy4pr04mb0472.namprd04.prod.outlook.com> > >Content-Type: text/plain; charset="iso-8859-1" > >Hi Jim; >These are encapsulated blocks two 48>5 and one 48>24 - I know the 24 is made >by Victor. Pretty easy to replace. >I up-dated my 2110 with a high contrast LED backlite display. Easy to do when >you have it apart. >Cheers; > >Tom Knox > >SR Test and Measurement Engineer > >Ascent Concepts and Technology > >4475 Whitney Place > >Boulder Colorado 80305 > >303-554-0307 > >[email protected] > >"Peace is not the absence of violence, but the presence of Justice" Both MLK >and Albert Einstein > >________________________________ >From: time-nuts <[email protected]> on behalf of Tom Van Baak ><[email protected]> >Sent: Sunday, July 5, 2020 3:33 PM >To: [email protected] <[email protected]> >Subject: Re: [time-nuts] Austron 2110 schematics? > >Jim, > >For the power supply see: http://leapsecond.com/museum/au2110b/ps.htm > >Let me know if you need more pages from the manual. > >For sample LCD readings see: http://leapsecond.com/museum/au2110b/lcd.htm > >/tvb > > >On 7/5/2020 1:34 PM, AC0XU (Jim) wrote: >> Time Nuts- >> >> I have an Austron 2110 with a severely toasted power controller board. >> Probably not repairable. I plan to build a substitute with a more modern >> design. >> >> Does anyway have schematics? I noticed correspondence between Magnus >> Danielson and Harald Hauglin some years ago. Did the manula or schematics >> ever get posted? >> >> Thanks in advance- >> Jim >> >> >> _______________________________________________ >> time-nuts mailing list -- [email protected] >> To unsubscribe, go to >> http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com >> and follow the instructions there. >> > > >_______________________________________________ >time-nuts mailing list -- [email protected] >To unsubscribe, go to >http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com >and follow the instructions there. > > >------------------------------ > >Message: 12 >Date: Sun, 5 Jul 2020 14:59:46 -0700 >From: Steve Jones <[email protected]> >To: [email protected] >Subject: [time-nuts] Success replacing Oncore VP with Synergy SR-6Tf ? >Message-ID: <[email protected]> >Content-Type: text/plain; charset=utf-8; format=flowed > >Greetings, > >I've found various posts in the list archive since about 2012 suggesting >that one could drop a Synergy SSR-6Tf in to replace an Oncore VP board, >or about planning to do so (and others about replacing an M12* with an >SSR-6Tr[u]). But if anybody has simply posted, "I dropped in an SSR-6Tf >and it worked" then I missed it. I wrote to Synergy's contact address >shortly before the (US) holiday, but it could be a while before they >respond... > >So, can anybody say "Yes, I replaced a VP with an SSR-6Tf and it Just >Worked?" > >FWIW my specific use case is a Spectracom NetClock/GPS 1U rackmount w/ >display, and the serial number on the GPS receiver board inside maps to >an Oncore VP per a document about WNRO &c on the Synergy site. > >Thanks in advance, >--Steve. > >Steve Jones >Berkeley, California > >"The amount of beauty required launch 1 ship = 1 Millihelen" > > > > > >------------------------------ > >Message: 13 >Date: Mon, 6 Jul 2020 10:42:48 -0400 >From: "Lester Veenstra" <[email protected]> >To: "'Discussion of precise time and frequency measurement'" > <[email protected]> >Subject: Re: [time-nuts] HP-5372A and HP-5372A operation with no CRT > display. >Message-ID: <01d301d653a3$b87be3f0$2973abd0$@com> >Content-Type: text/plain; charset="utf-8" > >Magnus: > The suspects were not hard to locate, leaking black goo. I did measure the > actual values of most of the larger electrolytics on the A17, for future > reference. On two boards, C414, 3300 mfd 35 vdc had to be replaced with new > 3300 mfd 50 vdc units. One board had a good C414 with only in place a 4.7 > mfd component. Replaced this also with 3300 mfd 50 vdc. > >One board also needed C406, 450 mfd 50V replaced. > >Now all three boards,on bench, with just 12Vdv applied produce a nice raster , >intensity controllable with variable 0-5 vdc on video input. > >Waiting on some female pins to arrive to make up a jumper cable from the >mother board to an external A17/CRT for final test before reassembling the >system. > >Certainly not as exciting as bring Cesium Beam standards back to life, but I >do like to keep the old boat anchors glowing, even if they only have a single >vacuum tube. HI . > >Lester B Veenstra K1YCM M?YCM W8YCM 6Y6Y >[email protected] > > >-----Original Message----- >From: time-nuts [mailto:[email protected]] On Behalf Of Magnus >Danielson >Sent: Sunday, July 05, 2020 3:33 PM >To: [email protected] >Subject: Re: [time-nuts] HP-5372A and HP-5372A operation with no CRT display. > >Hi Lester, > >Good to hear your progress. > >So, I gather that you managed to successfully repair it, and it was a >capacitor issue that I also had experienced. > >Which caps did fail for you? I think I recall a 50 uF bipolar cap. > >Cheers, >Magnus > > > > >------------------------------ > >Message: 14 >Date: Mon, 06 Jul 2020 11:09:14 -0400 >From: Gary Woods <[email protected]> >To: Discussion of precise time and frequency measurement > <[email protected]> >Subject: Re: [time-nuts] HP-5372A and HP-5372A operation with no CRT > display. >Message-ID: <[email protected]> >Content-Type: text/plain; charset=us-ascii > >On Mon, 6 Jul 2020 10:42:48 -0400, you wrote: > >>Certainly not as exciting as bring Cesium Beam standards back to life, but I >>do like to keep the old boat anchors glowing, even if they only have a single >>vacuum tube. HI . > >As the instructor at an RCA seminar said, "I like those glass NPN >devices with the light inside so you can tell they're on." >-- >Gary Woods O- K2AHC Public keys at home.earthlink.net/~garygarlic, or get >0x1D64A93D via keyserver >fingerprint = E2 6F 50 93 7B C7 F3 CA 1F 8B 3C C0 B0 28 68 > >-- >This email has been checked for viruses by Avast antivirus software. >https://www.avast.com/antivirus > > > > >------------------------------ > >Subject: Digest Footer > >_______________________________________________ >time-nuts mailing list >[email protected] >http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com > > >------------------------------ > >End of time-nuts Digest, Vol 192, Issue 10 >****************************************** _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com and follow the instructions there.
