Re: Issues with ACCORD Reference Clock Driver - NTP

This is a discussion on Re: Issues with ACCORD Reference Clock Driver - NTP ; Hi Hal, The custom NMEA format has GPS time unlike standard NMEA which give UTC. And the baudrate cannot be changed to 4800, it only works at 9600. Things are not as simple as we think and we need to ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Re: Issues with ACCORD Reference Clock Driver

  1. Re: Issues with ACCORD Reference Clock Driver

    Hi Hal,
    The custom NMEA format has GPS time unlike standard NMEA which give
    UTC. And the baudrate cannot be changed to 4800, it only works at 9600.
    Things are not as simple as we think and we need to work to make things simple
    I am looking for people who can help me in doing this.

    The binary format is just an add on to NMEA and it need not be supported but
    is would be nice if it did as an extra feature. Thats all.

    Venu

  2. Re: Issues with ACCORD Reference Clock Driver

    venu gopal wrote:
    > Hi Hal,
    > The custom NMEA format has GPS time unlike standard NMEA which give
    > UTC. And the baudrate cannot be changed to 4800, it only works at 9600.
    > Things are not as simple as we think and we need to work to make things simple
    > I am looking for people who can help me in doing this.
    >
    > The binary format is just an add on to NMEA and it need not be supported but
    > is would be nice if it did as an extra feature. Thats all.
    >
    > Venu


    If I recall correctly, NMEA is only defined to work at 4800 so 9600 is
    outside the spec. That doesn't mean it cannot be supported but we have
    to be careful about the implications of that.

    Danny

+ Reply to Thread