Re: [chrony-users] Using radio time signal for syncronization
Thank you Miroslav. I haven’t tried the alsa-oss package yet. Admittedly I much prefer using Chrony over ntpd :) I will let you know if and when I have a good application. It may take a long while! Sviatoslav On Wed, Jan 8, 2025 at 03:21, Miroslav Lichvar <[mlich...@redhat.com](mailto:On Wed, Jan 8, 2025 at 03:21, Miroslav Lichvar < wrote: > On Tue, Jan 07, 2025 at 02:49:52PM +, Sviatoslav Feshchenko wrote: >> I might take Miroslav's suggestion and port the ntpd audio code. >> This would be a hobby project, so I am not looking for the easiest >> porting solution. I would also want the code to last and be relevant >> for the longest amount of time possible, so I would probably write >> directly for ALSA rather than pipewire, to minimize the risk of >> obsolescence. I wouldn't use the SOCK wrapper ntp-refclock in this >> case either, and instead write a standalone application (somewhat >> along the lines of gpsd), which would provide the SOCK connection. >> What are your thoughts on this approach? > > That sounds like a lot of work, but of course it's your time :). I'd > just submit a patch adding support for alsa to the ntp project. > Looking at the ./libntp/audio.c file, it shouldn't be that difficult. > > alsa provides an alsa-oss package providing some OSS compatibility. > You could start ntpd/ntp-refclock with the aoss utility. Have you > tried that? > >> If I am ever successful and >> it works well, would Miroslav be willing to include a blurb about >> the existence of this application in chrony documentation for >> chrony.conf SOCK driver, which currently only mentions gpsd as one >> application that supports the SOCK protocol? > > I'd certainly add it to the "Useful links" page on the chrony website. > > -- > Miroslav Lichvar > > -- > To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org > with "unsubscribe" in the subject. > For help email chrony-users-requ...@chrony.tuxfamily.org > with "help" in the subject. > Trouble? Email listmas...@chrony.tuxfamily.org.
Re: [chrony-users] Using radio time signal for syncronization
On Tue, Jan 07, 2025 at 02:49:52PM +, Sviatoslav Feshchenko wrote: > I might take Miroslav's suggestion and port the ntpd audio code. > This would be a hobby project, so I am not looking for the easiest > porting solution. I would also want the code to last and be relevant > for the longest amount of time possible, so I would probably write > directly for ALSA rather than pipewire, to minimize the risk of > obsolescence. I wouldn't use the SOCK wrapper ntp-refclock in this > case either, and instead write a standalone application (somewhat > along the lines of gpsd), which would provide the SOCK connection. > What are your thoughts on this approach? That sounds like a lot of work, but of course it's your time :). I'd just submit a patch adding support for alsa to the ntp project. Looking at the ./libntp/audio.c file, it shouldn't be that difficult. alsa provides an alsa-oss package providing some OSS compatibility. You could start ntpd/ntp-refclock with the aoss utility. Have you tried that? > If I am ever successful and > it works well, would Miroslav be willing to include a blurb about > the existence of this application in chrony documentation for > chrony.conf SOCK driver, which currently only mentions gpsd as one > application that supports the SOCK protocol? I'd certainly add it to the "Useful links" page on the chrony website. -- Miroslav Lichvar -- To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-users-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
Re: [chrony-users] Using radio time signal for syncronization
Thank you Miroslav (and Gerd) for your responses. Unfortunately we don't have DCF77 in North America, so that's not an option. I might take Miroslav's suggestion and port the ntpd audio code. This would be a hobby project, so I am not looking for the easiest porting solution. I would also want the code to last and be relevant for the longest amount of time possible, so I would probably write directly for ALSA rather than pipewire, to minimize the risk of obsolescence. I wouldn't use the SOCK wrapper ntp-refclock in this case either, and instead write a standalone application (somewhat along the lines of gpsd), which would provide the SOCK connection. What are your thoughts on this approach? If I am ever successful and it works well, would Miroslav be willing to include a blurb about the existence of this application in chrony documentation for chrony.conf SOCK driver, which currently only mentions gpsd as one application that supports the SOCK protocol? Many thanks! Sviatoslav On Tuesday, January 7th, 2025 at 4:33 AM, Miroslav Lichvar wrote: > On Sun, Jan 05, 2025 at 01:22:08AM +, Sviatoslav Feshchenko wrote: > > > Is there either a software implementation that would allow chrony to > > synchronize to these time signals, or is there a device that can be > > purchased or built with certain chips, that would produce 1PPS output and > > NMEA sentences for example that can then be interpreted by GPSD and chrony? > > > I'm not aware of any. We have DCF77 here, which is supported by the > ntpd parse driver reading the signal from a serial port. > > I guess the easiest solution would be to port the ntpd audio code to alsa or > pipewire and then use the SOCK wrapper ntp-refclock to feed chrony. > > -- > Miroslav Lichvar > > > -- > To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org > with "unsubscribe" in the subject. > For help email chrony-users-requ...@chrony.tuxfamily.org > with "help" in the subject. > Trouble? Email listmas...@chrony.tuxfamily.org. -- To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-users-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
Re: [chrony-users] Using radio time signal for syncronization
hI ! im using gude dcf77 usb clocks with dcfshm to have them in range og gps clocks i use refclock SHM 0 offset 0.423 in config file br gerd Am 07.01.25 um 10:33 schrieb Miroslav Lichvar: On Sun, Jan 05, 2025 at 01:22:08AM +, Sviatoslav Feshchenko wrote: Is there either a software implementation that would allow chrony to synchronize to these time signals, or is there a device that can be purchased or built with certain chips, that would produce 1PPS output and NMEA sentences for example that can then be interpreted by GPSD and chrony? I'm not aware of any. We have DCF77 here, which is supported by the ntpd parse driver reading the signal from a serial port. I guess the easiest solution would be to port the ntpd audio code to alsa or pipewire and then use the SOCK wrapper ntp-refclock to feed chrony. -- To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-users-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
Re: [chrony-users] Using radio time signal for syncronization
On Sun, Jan 05, 2025 at 01:22:08AM +, Sviatoslav Feshchenko wrote: > Is there either a software implementation that would allow chrony to > synchronize to these time signals, or is there a device that can be purchased > or built with certain chips, that would produce 1PPS output and NMEA > sentences for example that can then be interpreted by GPSD and chrony? I'm not aware of any. We have DCF77 here, which is supported by the ntpd parse driver reading the signal from a serial port. I guess the easiest solution would be to port the ntpd audio code to alsa or pipewire and then use the SOCK wrapper ntp-refclock to feed chrony. -- Miroslav Lichvar -- To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-users-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.