> > Have you tried running the daemon in debugging mode, per the driver29.html > > page? What does that say? We found that quite useful on the one occasion > > where we had any problem with our unit. > > I still get clk_noreply... :(
You should see the driver logging what it's doing though, which might help
narrow down where the problem is. (You might have to rebuild the daemon
with DEBUG turned on, if it isn't already.) As I said, we found this
pretty useful. refclock_palisade.c is the place to look to see what it all
means.
> I have been leant a Serial Port Analyser..
> HP4925A
>
> I can see the pulse per second coming into the unit, and I can see the
> data on the screen.
You should see the daemon toggling RTS, and you should see the clock
sending back its timestamp in response.
--
Dr George D M Ross, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh, Scotland, EH8 9AB
Mail: g...@inf.ed.ac.uk Voice: +44 131 650 5147 Fax: +44 131 650 6899
PGP: 1024D/AD758CC5 B91E D430 1E0D 5883 EF6A 426C B676 5C2B AD75 8CC5
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
pgpdcqj919H8t.pgp
Description: PGP signature
_______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
