In message ,
Dave Liquorice  writes
>On Tue, 6 Aug 2019 20:17:42 +0100, Adrian wrote:
>
>> I've tried unplugging the gauge, but I still get the problem, suggesting
>> GPIO rather than the gauge itself.  Stopping and restarting the software
>> appeared to help for a couple of days, but it has started again.
>> Rebooting doesn't work either.   The Python3 code below is started at
>> boot up, and can be run with nohup.  Any suggestions on where to start
>> looking ?
>
>Had any thunderstorms recently? Suspect a hardware problem, damaged
>GPIO input, or the built in pull up/down resitors fried. A floating
>input can produce a stream of false transitions. Either try another
>GPIO for the guage or fit a 10 k or so pull up/down resistor as
>required.
>

Thanks for the reply.

No thunderstorms that I'm aware of (we've been very lucky weather wise).

With the PI powered off, I put a meter on the connections this morning,
and the resistance across the two pins was off the scale, I was starting
to suspect a short circuit as it seemed to think that the "switch" was
always closed.

I'll look at adding in a 10K resistor and see if that makes any
difference.

Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

--- SoupGate-Win32 v1.05