Does anyone know if Lady Heather needs to send data to the Thunderbolt when monitoring performance? She must send commands to do surveys, save results, and change operations, but is there data sent to the Tbolt after configuration is complete and she is just showing graphs of operating conditions. I would like to use gpsd to provide time information from the Tbolt to ntpd on one of my servers but I would also like to be able to monitor Tbolt operations with Lady Heather. I am planning to make a splitter for the rs-232 from the Tbolt, connecting TD and RD to the server running ntps and TD only from the Tbolt to a machine running LH. Will this work? Is this the best procatice for doing this? I suppose another answer would be to modify gpsd to do the same work that LH does or arrange for gpsd to pass info packets on to a Linux process doing the same sort of monitoring tha LH does, but this seems to be re-inverting the LH wheel. Thanks for any thoughts, Tim N2LTQ

I imagine one could hack gpsd to accept and relay commands and

And perhaps the same thing could be done to Lady Heather itself,

I suppose it is even possible to have Heather just have a

Naturally some thought about conflicts between commands from the

On Sat, Oct 17, 2009 at 09:44:12PM -0400, Tim Cwik wrote: > > I would like to use gpsd to provide time information from the Tbolt to > ntpd on one of my servers but I would also like to be able to monitor > Tbolt operations with Lady Heather. I am planning to make a splitter for > the rs-232 from the Tbolt, connecting TD and RD to the server running > ntps and TD only from the Tbolt to a machine running LH. Will this work? > Is this the best procatice for doing this? > > I suppose another answer would be to modify gpsd to do the same work > that LH does or arrange for gpsd to pass info packets on to a Linux > process doing the same sort of monitoring tha LH does, but this seems to > be re-inverting the LH wheel. I imagine one could hack gpsd to accept and relay commands and responses from another program (Heather) to a Tbolt out a second serial port (or the virtual equivalent perhaps). And perhaps the same thing could be done to Lady Heather itself, which in certain senses might make more sense for this situation - as Lady Heather is highly tbolt specific and it might be easier to use logic in it to sort out the non-Heather commands and responses and pass them on without getting confused about what it was seeing and doing. Not clear what the ideal path to gpsd might be ... I think of some sort of socket interface rather than a second physical COM port. I suppose it is even possible to have Heather just have a gpsd/ntp mode where it sets up the Tbolt to generate the right stuff and keep spitting it out and gpsd could merely be a passive listener tied as you suggest with a simple Y cable. Depends I guess on how general one wants to be and what gpsd features one might want to use. Naturally some thought about conflicts between commands from the two sources and what the presumed state of the Tbolt is moment by moment is needed... > > Thanks for any thoughts, > > Tim N2LTQ > > > > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. -- Dave Emery N1PRE/AE, die@dieconsulting.com DIE Consulting, Weston, Mass 02493 "An empty zombie mind with a forlorn barely readable weatherbeaten 'For Rent' sign still vainly flapping outside on the weed encrusted pole - in celebration of what could have been, but wasn't and is not to be now either."