Terry, I have used both (first) an NWTS and later also MichaelB's timelink reciever to drive my NixieChron. I did buy the Microchip processor upgrade from Michael for the Nixiechron with the last firmware. The process is very simple as described above by Nick. At one point I was looking at getting a Chinese manufacturer to make up a bunch of 6" P/S2 minidin to 3.5mm cables for exactly this. Like many things, I got sidetracked.
I do recall there was one NWTS setting that wasn't obvious, potentially the baud rate 4800 not 9600. I honestly can't recall. On the P/S2 port, Pin 1 is GND, Pin 2 is +5v and Pin 5 is RXD Effectively I'm using the master Mod-Six GPS reciever and transmitter to send time to my Mod-Sixes and to the Nixiechron. https://groups.google.com/g/neonixie-l/c/vcNOdSB3nYM/m/3AmeUTtCAQAJ On Tuesday, 27 July 2021 at 9:16:23 am UTC+10 Terry S wrote: > Guys, I also need help with this, as I have a Nixichron and I'm moving to > a location where I will not have a good GPS signal (metal roofed house with > large overhangs!) > > Can someone help me out with an explanation of what I need to do? Rather > purchase a solution than home brew. > > Thanks, Terry > > On Thursday, July 22, 2021 at 11:04:33 AM UTC-5 Jeff Walton wrote: > >> The NWTS also checks for latency of the response from the NTP and if the >> response time is outside of an acceptable range, it does not update. Later >> firmware is more forgiving, according to the original developer, and the >> accessibility of multiple pools beginning with 2.20 firmware resolved sync >> issues for me. >> >> Early NWTS firmware also did not have the ability to tweak the time. >> That is a useful feature to synchronize clocks from different designers. >> It's useful if you have clocks near each other and they differ by a second >> or two. >> >> >> Jeff >> >> -------- Original message -------- >> From: 'Nick' via neonixie-l <neoni...@googlegroups.com> >> Date: 7/22/21 3:26 AM (GMT-06:00) >> To: neonixie-l <neoni...@googlegroups.com> >> Subject: Re: [neonixie-l] Re: Using a NWTS on a NixiSat to replace a >> Haicom 204III puck... >> >> I had considered re-flashing to 2.21 as I bought this unit in 2017 and >> never used it until now (never even built it), so the firmware is "old". >> >> Having said that, it works just fine for me. I don't need the >> multi-multi-pool NTP server stuff - by using pool.net.org or one of its >> regional sub-domains you already have multiple servers available and those >> lists are shuffled every hour, so for domestic use it's more than adequate. >> >> Nick >> >> On Wednesday, 21 July 2021 at 23:55:24 UTC+1 Jeff Walton wrote: >> >>> The latest NWTS software is version 2.21 (yes, this is later than 2.5) >>> >>> Version 2.21-20190701SF >>> <https://www.dropbox.com/s/dv1qvzdfwy43xf6/nwts2.21-20190701SF.zip?dl=0> >>> >>> >>> >>> Luis Ramos is maintaining the NWTS and I believe that he has an OEM >>> customer that is using the NWTS module in their product. Luis did the >>> latest codes for the NWTS and it now supports multiple NTP pools – if the >>> NWTS does not get a valid answer from the first time source, it will now go >>> to another time source for the NTP solution. It is a nice feature to have >>> if the NTP source is busy or non-responsive. The multiple NTP sources >>> begins with firmware 2.20 and 2.21 >>> >>> >>> >>> The NWTS is still available through >>> https://www.tindie.com/stores/mazevedo/ >>> >>> >>> >>> Jeff >>> >>> >>> >>> >>> >>> *From:* 'Nick' via neonixie-l >>> *Sent:* Wednesday, July 21, 2021 2:36 PM >>> *To:* neonixie-l <neoni...@googlegroups.com> >>> *Subject:* Re: [neonixie-l] Re: Using a NWTS on a NixiSat to replace a >>> Haicom 204III puck... >>> >>> >>> >>> Indeed - NWYTS: 2.5, NixiSat: 110210 >>> >>> Couple of things - who is maintaining/selling NWTS now and who has the >>> source code etc. for the NixiSat? >>> >>> >>> >>> Both are estate items, regrettably, and both are important! >>> >>> On Wednesday, 21 July 2021 at 18:34:48 UTC+1 MichaelB wrote: >>> >>> Ahhh you're right, Jeff. That's probably what he was referring to. Good >>> catch! >>> >>> On Wednesday, July 21, 2021 at 10:29:38 AM UTC-7 Jeff Walton wrote: >>> >>> 2.5 is probably the NWTS firmware version. The NWTS is a very nice >>> solution and is very configurable. >>> >>> >>> >>> Jeff >>> >>> >>> >>> >>> >>> *From:* neoni...@googlegroups.com *On Behalf Of *MichaelB >>> *Sent:* Wednesday, July 21, 2021 11:52 AM >>> *To:* neonixie-l <neoni...@googlegroups.com> >>> *Subject:* [neonixie-l] Re: Using a NWTS on a NixiSat to replace a >>> Haicom 204III puck... >>> >>> >>> >>> Nope, you gt the latest. I was confused a bit when you said you were >>> "running 2.5 firmware". Maybe Jeff referred to this version like that at >>> one time? Didn't know that if he did. Carry on Garth >>> >>> On Wednesday, July 21, 2021 at 9:41:52 AM UTC-7 Nick wrote: >>> >>> ! I have the latest (last) firmware if you ever want a copy >>> >>> >>> >>> I'm running 110210 - is yours later than that? >>> >>> >>> >>> Thanks >>> >>> >>> >>> Nick >>> >>> On Wednesday, 21 July 2021 at 14:15:54 UTC+1 MichaelB wrote: >>> >>> That'll do the trick! I have the latest (last) firmware if you ever want >>> a copy. >>> >>> On Wednesday, July 21, 2021 at 5:58:16 AM UTC-7 Nick wrote: >>> >>> Thanks to all who replied but I decided to stop being pathetic and to do >>> it myself! >>> >>> >>> >>> Basically, after the upgrades to the Haicom 204III GPS puck, the NixiSat >>> is talking to the puck using RS232, 4800 baud, 8 bits, no parity and is >>> expecting to just receive a $GPRMC sentence once a second. >>> >>> >>> >>> So, just set the NWTS to send just send $GPRMC messages at 4800 baud >>> using RS232 signalling (JP1,JP2 off, JP3 linked) - 5V power (about 80mA >>> needed) from the NixiSat is on pins 1 & 2 of the 6-pin mini-DIN connector >>> and RXD is on pin 5. Basically there's now a little black box behind the >>> clock and that's it. >>> >>> >>> >>> Works a treat. I have to say the NTWS is a very nice solution for those >>> needing GPS accuracy in an area where there's no satellite visibility for >>> GPS. I'm running the 2.5 firmware which is quite old but it works for me >>> just fine. >>> >>> >>> >>> Nick >>> >>> On Tuesday, 20 July 2021 at 22:35:18 UTC+1 MichaelB wrote: >>> >>> Hey Thanks Greg. >>> >>> >>> >>> Hi Nick, ping me and I can tell you how I do it so that you can use the >>> clock either NWTS or GPS governed and easily swap them. The one I sent >>> Dalibor is done this way. >>> >>> >>> >>> You've already done the hard part by converting the clock away from the >>> older Axiom/Oncore 1PPS GPSs. And I assume converted that BNC connector to >>> either a mini DIN or 1/8" TRS? >>> >>> >>> >>> On Tuesday, July 20, 2021 at 1:54:44 PM UTC-7 Greg P wrote: >>> >>> Nick, >>> >>> >>> >>> Takes some modification to the PCB and added components. Michael Barile >>> (Bad Nixie) is the master at these conversions. Well worth it to have him >>> do it for you, he has many satisfied customers. >>> >>> On Tuesday, July 20, 2021 at 9:05:29 AM UTC-4 Nick wrote: >>> >>> Has anyone done this? >>> >>> >>> >>> I have an original Jeff Thomas NixiSat with the later firmware and the >>> HaiCom 204III puck that I added a few years ago - see >>> https://groups.google.com/g/neonixie-l/c/evzX0noEGXg/m/4ygtcNnhj3wJ >>> >>> >>> >>> The current site of the clock has no GPS visibility, so I want to >>> replace the puck with an NWTS - I just happened to have an unused one lying >>> around... >>> >>> >>> Thanks >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "neonixie-l" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to neonixie-l+...@googlegroups.com. >>> To view this discussion on the web, visit >>> https://groups.google.com/d/msgid/neonixie-l/1150b615-fe6e-431f-a064-e91acf3f82b2n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/neonixie-l/1150b615-fe6e-431f-a064-e91acf3f82b2n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "neonixie-l" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to neonixie-l+...@googlegroups.com. >>> >>> To view this discussion on the web, visit >>> https://groups.google.com/d/msgid/neonixie-l/0cc0efce-5497-4dc5-9beb-a8bde18e4b2dn%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/neonixie-l/0cc0efce-5497-4dc5-9beb-a8bde18e4b2dn%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "neonixie-l" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to neonixie-l+...@googlegroups.com. >> To view this discussion on the web, visit >> https://groups.google.com/d/msgid/neonixie-l/0556996c-5422-42f7-b009-754d50cae7dan%40googlegroups.com >> >> <https://groups.google.com/d/msgid/neonixie-l/0556996c-5422-42f7-b009-754d50cae7dan%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "neonixie-l" group. To unsubscribe from this group and stop receiving emails from it, send an email to neonixie-l+unsubscr...@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/neonixie-l/5b2e0652-d13f-49f4-abcf-5f629f6ded4fn%40googlegroups.com.
