gpsd-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gpsd-users] NTP1 keeps going away.


From: stinga
Subject: Re: [gpsd-users] NTP1 keeps going away.
Date: Thu, 9 Nov 2017 22:02:49 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0

On 09/11/17 21:20, Gary E. Miller wrote:
Yo stinga!

On Thu, 9 Nov 2017 21:00:47 +0000
stinga <address@hidden> wrote:

Don't think it is this as the 5 was a coincidence I have seen more
pulses on occasions.
Which could be a flakey PPS signal.  Which is why you need to look
with an oscope.

Maybe just use a jumper to connect gnd ad 3.3V to the PPS pin and see is
ppstest sees it.

Using watch -n0.001 gpio readall I can see physical pin 18 changing, this is gpio5

address@hidden:~# gpio readall
 +-----+-----+---------+------+---+-Model B1-+---+------+---------+-----+-----+  | BCM | wPi |   Name  | Mode | V | Physical | V | Mode | Name    | wPi | BCM |
 +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
 |     |     |    3.3v |      |   |  1 || 2  |   |      | 5v      |     |     |  |   2 |   8 |   SDA.1 |   IN | 1 |  3 || 4  |   |      | 5v      |     |     |  |   3 |   9 |   SCL.1 |   IN | 1 |  5 || 6  |   |      | 0v      |     |     |  |   4 |   7 | GPIO. 7 |   IN | 1 |  7 || 8  | 1 | ALT0 | TxD     | 15  | 14  |  |     |     |      0v |      |   |  9 || 10 | 1 | ALT0 | RxD     | 16  | 15  |  |  17 |   0 | GPIO. 0 |   IN | 0 | 11 || 12 | 0 | IN   | GPIO. 1 | 1   | 18  |  |  27 |   2 | GPIO. 2 |   IN | 0 | 13 || 14 |   |      | 0v      |     |     |  |  22 |   3 | GPIO. 3 |   IN | 0 | 15 || 16 | 0 | IN   | GPIO. 4 | 4   | 23  |  |     |     |    3.3v |      |   | 17 || 18 | 1 | IN   | GPIO. 5 | 5   | 24  |  |  10 |  12 |    MOSI |   IN | 0 | 19 || 20 |   |      | 0v      |     |     |  |   9 |  13 |    MISO |   IN | 0 | 21 || 22 | 0 | IN   | GPIO. 6 | 6   | 25  |  |  11 |  14 |    SCLK |   IN | 0 | 23 || 24 | 1 | IN   | CE0     | 10  | 8   |  |     |     |      0v |      |   | 25 || 26 | 1 | IN   | CE1     | 11  | 7   |
 +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
 | BCM | wPi |   Name  | Mode | V | Physical | V | Mode | Name    | wPi | BCM |  +-----+-----+---------+------+---+-Model B1-+---+------+---------+-----+-----+

I assume
dtoverlay=pps-gpio,gpiopin=18
Relates to physical pin 18, I have had this working, it ran for a week with a hicup at one point but now refuses to work.
But since I have been changing things maybe I have mucked the pins up.

Yet
address@hidden:~# ppstest /dev/pps0
trying PPS source "/dev/pps0"
found PPS source "/dev/pps0"
ok, found 1 source(s), now start fetching data...
time_pps_fetch() error -1 (Connection timed out)
time_pps_fetch() error -1 (Connection timed out)

So the gpio pin is pulsing, the pi is detecting it, but maybe there is some disconnect to the kernel?

I think I am going to start again with the pi3 on a clean install.

--
'ooroo

Stinga...(:)-)
---------------------------------------------------
Email: address@hidden         o
You need only two tools.        o /////
A hammer and duct tape. If it    /@   `\  /) ~
doesn't move and it should use  >  (O)  X<  ~  Fish!!
the hammer. If it moves and      `\___/'  \) ~
shouldn't, use the tape.           \\\
---------------------------------------------------


reply via email to

[Prev in Thread] Current Thread [Next in Thread]