Manuel Reimer manuel.nulldev...@nurfuerspam.de wrote:
On 10/06/2013 12:17 AM, Rob wrote:
That is why I suspect that it cannot run 50 baud.
What happens when you try stty 50 /dev/tty...?
[root@alarm dev]# stty 50 /dev/ttyAPP0
[root@alarm dev]# stty /dev/ttyAPP0
speed 50 baud; line = 0;
On 08/10/13 01:15, Brian Inglis wrote:
Normally with speeds below 300 (150, 110, 75, 50) bps both interfaces
need to be configured to use two stop bits to avoid framing errors. Many
USB converters (and probably other serial interfaces) nowadays, lack
support for low speeds, and possibly also
Rob van der Putten r...@sput.nl wrote:
Using 8 bits + parity prevents framing errors but introduces parity
errors instead;
-+ +---+---+---+---+---+---+---+---+---+-
| S | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | P | S
+---+---+---+---+---+---+---+---+---+---+
Hello,
I wanto to keep the system clock of my embedded Linux board (Olinuxino
Maxi, based on iMX233) up to date using the DCF77 signal.
To do so, I wired the receiver to the RX line of the UART port and
symlinked it to /dev/refclock-1.
The receiver works well and delivers a good signal. I
Manuel Reimer manuel.nulldev...@nurfuerspam.de wrote:
Hello,
I wanto to keep the system clock of my embedded Linux board (Olinuxino
Maxi, based on iMX233) up to date using the DCF77 signal.
To do so, I wired the receiver to the RX line of the UART port and
symlinked it to /dev/refclock-1.
On 10/05/2013 03:46 PM, Rob wrote:
I use:
server 127.127.8.0 mode 6
It works fine for me.
I tried that and I still get the same errors. Then I rewired my receiver
to send out *noninverted* signals. Now I get:
Oct 05 17:21:58 alarm ntpd[1075]: parse: convert_rawdcf: parity check
FAILED for
Manuel Reimer manuel.nulldev...@nurfuerspam.de wrote:
On 10/05/2013 03:46 PM, Rob wrote:
I use:
server 127.127.8.0 mode 6
It works fine for me.
I tried that and I still get the same errors. Then I rewired my receiver
to send out *noninverted* signals. Now I get:
Oct 05 17:21:58 alarm
On 10/05/2013 05:55 PM, Rob wrote:
Can the serial port run at 50 baud? This is a requirement for this
method of dcf parsing. Maybe the length of the divider register is
insufficient to go that low.
Maybe. I could ask the vendor about that.
The interesting thing is, that the error message
