Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.os.linux.misc > #78549 > unrolled thread

More on wifi range - Pi PICO W Oil level sensor

Started byThe Natural Philosopher <tnp@invalid.invalid>
First post2025-12-09 10:47 +0000
Last post2025-12-24 22:53 +0000
Articles 20 on this page of 99 — 13 participants

Back to article view | Back to comp.os.linux.misc


Contents

  More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-09 10:47 +0000
    Re: More on wifi range - Pi PICO W Oil level sensor Andy Burns <usenet@andyburns.uk> - 2025-12-09 11:57 +0000
      Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-09 14:07 +0000
        Re: More on wifi range - Pi PICO W Oil level sensor Rich <rich@example.invalid> - 2025-12-09 19:14 +0000
          Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-09 19:17 +0000
      Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-09 21:19 -0500
        Re: More on wifi range - Pi PICO W Oil level sensor Andy Burns <usenet@andyburns.uk> - 2025-12-10 05:18 +0000
          Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-10 00:27 -0500
            Re: More on wifi range - Pi PICO W Oil level sensor Andy Burns <usenet@andyburns.uk> - 2025-12-10 05:38 +0000
              Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-10 02:13 -0500
                Re: More on wifi range - Pi PICO W Oil level sensor Andy Burns <usenet@andyburns.uk> - 2025-12-10 08:12 +0000
                Re: More on wifi range - Pi PICO W Oil level sensor Andy Burns <usenet@andyburns.uk> - 2025-12-10 08:15 +0000
                  Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-10 03:56 -0500
                    Re: More on wifi range - Pi PICO W Oil level sensor Andy Burns <usenet@andyburns.uk> - 2025-12-10 09:14 +0000
                      Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-10 09:59 +0000
                      Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-10 05:02 -0500
                        Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-10 10:24 +0000
                          Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-10 05:53 -0500
                            Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-10 11:45 +0000
                          Re: More on wifi range - Pi PICO W Oil level sensor "Carlos E.R." <robin_listas@es.invalid> - 2025-12-11 22:06 +0100
                            Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-12 10:26 +0000
                              Re: More on wifi range - Pi PICO W Oil level sensor Andy Burns <usenet@andyburns.uk> - 2025-12-12 10:39 +0000
                                Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-12 11:14 +0000
                                  Re: More on wifi range - Pi PICO W Oil level sensor Andy Burns <usenet@andyburns.uk> - 2025-12-12 11:41 +0000
                                    Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-12 12:10 +0000
                                    Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-13 01:19 -0500
                              Re: More on wifi range - Pi PICO W Oil level sensor "Carlos E.R." <robin_listas@es.invalid> - 2025-12-12 12:19 +0100
                                Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-12 12:10 +0000
                                Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-12 23:42 -0500
                                  Re: More on wifi range - Pi PICO W Oil level sensor "Carlos E.R." <robin_listas@es.invalid> - 2025-12-13 13:30 +0100
                            Re: More on wifi range - Pi PICO W Oil level sensor Fritz Wuehler <fritz@spamexpire-202512.rodent.frell.theremailer.net> - 2025-12-14 19:23 +0100
                              Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-15 01:55 -0500
                                Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-15 17:49 +0000
                                  Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-16 01:50 -0500
                                    Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-16 10:43 +0000
                                      Re: More on wifi range - Pi PICO W Oil level sensor rbowman <bowman@montana.com> - 2025-12-16 20:40 +0000
                                        Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-17 01:05 +0000
                                          Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-17 01:55 -0500
                                            Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-17 10:31 +0000
                                              Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-17 06:25 -0500
                                                Re: More on wifi range - Pi PICO W Oil level sensor "Carlos E.R." <robin_listas@es.invalid> - 2025-12-18 19:00 +0100
                                                  Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-19 00:55 -0500
                                                    Re: More on wifi range - Pi PICO W Oil level sensor "Carlos E.R." <robin_listas@es.invalid> - 2025-12-19 15:16 +0100
                                                      Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-20 03:26 -0500
                                                        Re: More on wifi range - Pi PICO W Oil level sensor "Carlos E.R." <robin_listas@es.invalid> - 2025-12-20 13:00 +0100
                                      Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-17 00:20 -0500
                                      Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-17 01:01 -0500
                                Re: More on wifi range - Pi PICO W Oil level sensor rbowman <bowman@montana.com> - 2025-12-15 23:45 +0000
                                Re: More on wifi range - Pi PICO W Oil level sensor "Carlos E.R." <robin_listas@es.invalid> - 2025-12-16 23:31 +0100
                                  Re: More on wifi range - Pi PICO W Oil level sensor Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-12-16 16:35 -0800
                                    Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-17 01:38 -0500
                                  Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-17 01:20 -0500
                                    Re: More on wifi range - Pi PICO W Oil level sensor rbowman <bowman@montana.com> - 2025-12-17 07:58 +0000
                                      Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-17 03:24 -0500
                                Re: More on wifi range - Pi PICO W Oil level sensor "Carlos E.R." <robin_listas@es.invalid> - 2025-12-17 20:39 +0100
                              Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-15 17:46 +0000
                        Re: More on wifi range - Pi PICO W Oil level sensor "Carlos E.R." <robin_listas@es.invalid> - 2025-12-11 22:03 +0100
                  Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-10 09:57 +0000
            Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-10 09:55 +0000
              Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-10 05:36 -0500
                Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-10 11:33 +0000
        Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-10 09:47 +0000
          Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-10 05:29 -0500
            Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-10 11:29 +0000
            Re: More on wifi range - Pi PICO W Oil level sensor Daniel James <daniel@me.invalid> - 2025-12-10 13:01 +0000
              Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-10 13:05 +0000
                Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-10 23:19 -0500
              Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-10 23:12 -0500
                Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-11 08:48 +0000
                  Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-11 04:19 -0500
                  Cable chasing (Was: More on wifi range - Pi PICO W Oil level sensor) Daniel James <daniel@me.invalid> - 2025-12-11 10:15 +0000
                Inside out (Was: More on wifi range - Pi PICO W Oil level sensor) Daniel James <daniel@me.invalid> - 2025-12-11 10:23 +0000
                  Re: Inside out (Was: More on wifi range - Pi PICO W Oil level sensor) Lars Poulsen <lars@beagle-ears.com> - 2025-12-11 18:16 +0000
                    Re: Inside out (Was: More on wifi range - Pi PICO W Oil level sensor) John R Walliker <jrwalliker@gmail.com> - 2025-12-11 18:28 +0000
                      Re: Inside out (Was: More on wifi range - Pi PICO W Oil level sensor) "Carlos E.R." <robin_listas@es.invalid> - 2025-12-11 21:59 +0100
                        Re: Inside out (Was: More on wifi range - Pi PICO W Oil level sensor) The Natural Philosopher <tnp@invalid.invalid> - 2025-12-12 11:21 +0000
                          Re: Inside out (Was: More on wifi range - Pi PICO W Oil level sensor) "Carlos E.R." <robin_listas@es.invalid> - 2025-12-13 13:45 +0100
    Re: More on wifi range - Pi PICO W Oil level sensor "Carlos E.R." <robin_listas@es.invalid> - 2025-12-11 22:18 +0100
      Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-12 10:41 +0000
        Re: More on wifi range - Pi PICO W Oil level sensor "Carlos E.R." <robin_listas@es.invalid> - 2025-12-13 13:57 +0100
      Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-12 11:28 +0000
        Re: More on wifi range - Pi PICO W Oil level sensor "Carlos E.R." <robin_listas@es.invalid> - 2025-12-13 13:56 +0100
          Re: More on wifi range - Pi PICO W Oil level sensor John R Walliker <jrwalliker@gmail.com> - 2025-12-14 19:22 +0000
      Re: More on wifi range - Pi PICO W Oil level sensor mm0fmf <none@invalid.com> - 2025-12-24 07:58 +0000
        Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-24 12:16 +0000
          Re: More on wifi range - Pi PICO W Oil level sensor John R Walliker <jrwalliker@gmail.com> - 2025-12-24 14:04 +0000
            Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-24 14:23 +0000
              Re: More on wifi range - Pi PICO W Oil level sensor "Kerr-Mudd, John" <admin@127.0.0.1> - 2025-12-24 17:00 +0000
                Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-24 20:07 +0000
                  Re: More on wifi range - Pi PICO W Oil level sensor mm0fmf <none@invalid.com> - 2025-12-24 23:17 +0000
                    Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-25 03:23 +0000
                      Re: More on wifi range - Pi PICO W Oil level sensor rbowman <bowman@montana.com> - 2025-12-25 07:32 +0000
                  Re: More on wifi range - Pi PICO W Oil level sensor c186282 <c186282@nnada.net> - 2025-12-24 21:16 -0500
              Re: More on wifi range - Pi PICO W Oil level sensor "Carlos E.R." <robin_listas@es.invalid> - 2025-12-27 21:51 +0100
                Re: More on wifi range - Pi PICO W Oil level sensor The Natural Philosopher <tnp@invalid.invalid> - 2025-12-27 23:31 +0000
                  Re: More on wifi range - Pi PICO W Oil level sensor rbowman <bowman@montana.com> - 2025-12-27 23:58 +0000
            Re: More on wifi range - Pi PICO W Oil level sensor Lars Poulsen <lars@beagle-ears.com> - 2025-12-24 23:01 +0000
          Re: More on wifi range - Pi PICO W Oil level sensor rbowman <bowman@montana.com> - 2025-12-25 02:29 +0000
        Re: More on wifi range - Pi PICO W Oil level sensor Lars Poulsen <lars@beagle-ears.com> - 2025-12-24 22:53 +0000

Page 2 of 5 — ← Prev page 1 [2] 3 4 5  Next page →


#78892

FromThe Natural Philosopher <tnp@invalid.invalid>
Date2025-12-12 10:26 +0000
Message-ID<10hgqju$2r3rh$1@dont-email.me>
In reply to#78834
On 11/12/2025 21:06, Carlos E.R. wrote:
> On 2025-12-10 11:24, The Natural Philosopher wrote:
>> On 10/12/2025 10:02, c186282 wrote:
>>> On 12/10/25 04:14, Andy Burns wrote:
>>>> c186282 wrote:
>>>>
>>>>>    I think it was you ... said how a cam would
>>>>>    more or less drop out when the Big Red Truck
>>>>>    was there.
>>>> No, maybe TNP said his oil level monitor would drop out?
>>>
>>>    Posting traffic has considerably increased of late,
>>>    partly my "fault" ... but COSLM was kind of dying
>>>    and that would have been tragic. Forgive the sort
>>>    of off-topic stuff, but it DOES keep minds alive -
>>>    you can't ALWAYS think about Linux without kind
>>>    of seizing up :-)
>>>
>> I stated for te record and for the interest of others doing outside 
>> wifi coupled IOT shit that rain wind and possibly cars made a difference.
>>
>> Someone else remarked that so did fire trucks.
>>
>> The downside of the new oil monitor is that is is so accurate - to 
>> within a litre it seems - that I can visibly see how much a shower or 
>> washing the dishes costs me, and a cold night is very expensive. :-)
>> LOL.
>>
>> Now off to write the software that will look at it for me and warn me 
>> of things by email.
>> So I can get on with the next project.
> 
> You mentioned thieves stealing fuel. You can also monitor for that. You 
> would need a fuel flow meter on the fuel line, or a sensor telling when 
> the furnace is working. Compare with the tank level decreasing rapidly.
> 

The problem is that the sensor I built on the tank has no power except 
batteries: So it only wakes up occasionally and draws nanoamps in between.
I have completed the warning software that looks for low oil levels, 
loss of communication, a failing battery and unexpected changes in oil 
level, BUT it cannot do that in real time as the unit is only powered up 
for a minute or so every couple of hours.

Depending on how long the batteries last I may increase the frequency of 
operation. But it can never be 'real time'



-- 
If you tell a lie big enough and keep repeating it, people will 
eventually come to believe it. The lie can be maintained only for such 
time as the State can shield the people from the political, economic 
and/or military consequences of the lie. It thus becomes vitally 
important for the State to use all of its powers to repress dissent, for 
the truth is the mortal enemy of the lie, and thus by extension, the 
truth is the greatest enemy of the State.

Joseph Goebbels



[toc] | [prev] | [next] | [standalone]


#78895

FromAndy Burns <usenet@andyburns.uk>
Date2025-12-12 10:39 +0000
Message-ID<mq29n8Fkbm0U1@mid.individual.net>
In reply to#78892
The Natural Philosopher wrote:

> the sensor I built on the tank has no power except batteries: So it only 
> wakes up occasionally and draws nanoamps in between.
> I have completed the warning software that looks for low oil levels, 
> loss of communication, a failing battery and unexpected changes in oil 
> level, BUT it cannot do that in real time as the unit is only powered up 
> for a minute or so every couple of hours.
> 
> Depending on how long the batteries last I may increase the frequency of 
> operation.


Worth trying to send the data as UDP rather than TCP? if it fits in a 
single packet,the receiver doesn't have to track the position within a 
stream ...

[toc] | [prev] | [next] | [standalone]


#78903

FromThe Natural Philosopher <tnp@invalid.invalid>
Date2025-12-12 11:14 +0000
Message-ID<10hgtem$2r3rh$8@dont-email.me>
In reply to#78895
On 12/12/2025 10:39, Andy Burns wrote:
> The Natural Philosopher wrote:
> 
>> the sensor I built on the tank has no power except batteries: So it 
>> only wakes up occasionally and draws nanoamps in between.
>> I have completed the warning software that looks for low oil levels, 
>> loss of communication, a failing battery and unexpected changes in oil 
>> level, BUT it cannot do that in real time as the unit is only powered 
>> up for a minute or so every couple of hours.
>>
>> Depending on how long the batteries last I may increase the frequency 
>> of operation.
> 
> 
> Worth trying to send the data as UDP rather than TCP? if it fits in a 
> single packet,the receiver doesn't have to track the position within a 
> stream ...
> 
> 
Well the daemon runs under xinetd...for sheer laziness. I guess I could 
make it UDP.

But I don't know what problem that would solve.

-- 
Microsoft : the best reason to go to Linux that ever existed.

[toc] | [prev] | [next] | [standalone]


#78913

FromAndy Burns <usenet@andyburns.uk>
Date2025-12-12 11:41 +0000
Message-ID<mq2dc2FktbjU2@mid.individual.net>
In reply to#78903
The Natural Philosopher wrote:

> Well the daemon runs under xinetd...for sheer laziness. I guess I could 
> make it UDP.
> 
> But I don't know what problem that would solve.

The data would arrive if a single packet got through the fog, whereas 
with tcp at least dour packets on sequence need to make it (or get 
retried) with UDP you could afford to spray each packet half a dozen 
times and if one of them makes it, you're good ...


[toc] | [prev] | [next] | [standalone]


#78920

FromThe Natural Philosopher <tnp@invalid.invalid>
Date2025-12-12 12:10 +0000
Message-ID<10hh0oj$2r3rh$25@dont-email.me>
In reply to#78913
On 12/12/2025 11:41, Andy Burns wrote:
> The Natural Philosopher wrote:
> 
>> Well the daemon runs under xinetd...for sheer laziness. I guess I 
>> could make it UDP.
>>
>> But I don't know what problem that would solve.
> 
> The data would arrive if a single packet got through the fog, whereas 
> with tcp at least dour packets on sequence need to make it (or get 
> retried) with UDP you could afford to spray each packet half a dozen 
> times and if one of them makes it, you're good ...
> 
> 
> 
Oh, ok...

-- 
“The ultimate result of shielding men from the effects of folly is to 
fill the world with fools.”

Herbert Spencer

[toc] | [prev] | [next] | [standalone]


#78966

Fromc186282 <c186282@nnada.net>
Date2025-12-13 01:19 -0500
Message-ID<Gp2cnVMsbIP3mKD0nZ2dnZfqn_ednZ2d@giganews.com>
In reply to#78913
On 12/12/25 06:41, Andy Burns wrote:
> The Natural Philosopher wrote:
> 
>> Well the daemon runs under xinetd...for sheer laziness. I guess I 
>> could make it UDP.
>>
>> But I don't know what problem that would solve.
> 
> The data would arrive if a single packet got through the fog, whereas 
> with tcp at least dour packets on sequence need to make it (or get 
> retried) with UDP you could afford to spray each packet half a dozen 
> times and if one of them makes it, you're good ...

   I once made a bi-directional client/server setup,
   first Python, then 'C'. One variant was TCP, the
   other UDP. Probably could have used a config file
   or defs ... but I never got to it.

   On a clean LAN, both worked perfectly. However
   with some outdoor devices (Pi2 + wifi dongle as
   best I recall) both approaches had issues kind
   of similar to what you described.

   TCP, while "error resistant", was often VERY iffy.
   UDP - well - easier/smaller to send. You could
   scan each packet for obvious errors and, if a
   fail, could ask for it again or just let the
   pgm work around to sending that data again.

   For almost all modern apps, TCP is best by far.
   However iffy situations CAN still exist, so
   UDP you add some IQ to MIGHT be better.

   As I've said elsewhere, wifi can sometimes be
   black magic. Weird RF shadows and multipaths
   can be anywhere and it's very hard to tell
   what's perfect placement.

   Hmm ... apparently CANbus can be sent over
   wifi - but you lose some error-checking so
   there's no gain. There are various dongles
   for lower-freq data transmission too, but
   never got around to trying them. Fidelity
   might be worth losing some speed.

[toc] | [prev] | [next] | [standalone]


#78907

From"Carlos E.R." <robin_listas@es.invalid>
Date2025-12-12 12:19 +0100
Message-ID<7bat0mxbob.ln2@Telcontar.valinor>
In reply to#78892
On 2025-12-12 11:26, The Natural Philosopher wrote:
> On 11/12/2025 21:06, Carlos E.R. wrote:
>> On 2025-12-10 11:24, The Natural Philosopher wrote:
>>> On 10/12/2025 10:02, c186282 wrote:
>>>> On 12/10/25 04:14, Andy Burns wrote:
>>>>> c186282 wrote:


>>> Now off to write the software that will look at it for me and warn me 
>>> of things by email.
>>> So I can get on with the next project.
>>
>> You mentioned thieves stealing fuel. You can also monitor for that. 
>> You would need a fuel flow meter on the fuel line, or a sensor telling 
>> when the furnace is working. Compare with the tank level decreasing 
>> rapidly.
>>
> 
> The problem is that the sensor I built on the tank has no power except 
> batteries: So it only wakes up occasionally and draws nanoamps in between.
> I have completed the warning software that looks for low oil levels, 
> loss of communication, a failing battery and unexpected changes in oil 
> level, BUT it cannot do that in real time as the unit is only powered up 
> for a minute or so every couple of hours.
> 
> Depending on how long the batteries last I may increase the frequency of 
> operation. But it can never be 'real time'

Ah.

What about a small solar panel and rechargeable batteries?

-- 
Cheers, Carlos.
ES🇪🇸, EU🇪🇺;

[toc] | [prev] | [next] | [standalone]


#78919

FromThe Natural Philosopher <tnp@invalid.invalid>
Date2025-12-12 12:10 +0000
Message-ID<10hh0mr$2r3rh$24@dont-email.me>
In reply to#78907
On 12/12/2025 11:19, Carlos E.R. wrote:
> On 2025-12-12 11:26, The Natural Philosopher wrote:
>> On 11/12/2025 21:06, Carlos E.R. wrote:
>>> On 2025-12-10 11:24, The Natural Philosopher wrote:
>>>> On 10/12/2025 10:02, c186282 wrote:
>>>>> On 12/10/25 04:14, Andy Burns wrote:
>>>>>> c186282 wrote:
> 
> 
>>>> Now off to write the software that will look at it for me and warn 
>>>> me of things by email.
>>>> So I can get on with the next project.
>>>
>>> You mentioned thieves stealing fuel. You can also monitor for that. 
>>> You would need a fuel flow meter on the fuel line, or a sensor 
>>> telling when the furnace is working. Compare with the tank level 
>>> decreasing rapidly.
>>>
>>
>> The problem is that the sensor I built on the tank has no power except 
>> batteries: So it only wakes up occasionally and draws nanoamps in 
>> between.
>> I have completed the warning software that looks for low oil levels, 
>> loss of communication, a failing battery and unexpected changes in oil 
>> level, BUT it cannot do that in real time as the unit is only powered 
>> up for a minute or so every couple of hours.
>>
>> Depending on how long the batteries last I may increase the frequency 
>> of operation. But it can never be 'real time'
> 
> Ah.
> 
> What about a small solar panel and rechargeable batteries?
> 

Yes. That is in the 'lemme think about that' pile...
Not that there is much sun here..

At this time of year.

And where the tank it is likely to get overgrown or shat on by birds



-- 
“The ultimate result of shielding men from the effects of folly is to 
fill the world with fools.”

Herbert Spencer

[toc] | [prev] | [next] | [standalone]


#78961

Fromc186282 <c186282@nnada.net>
Date2025-12-12 23:42 -0500
Message-ID<Gp2cnVEsbIMuc6H0nZ2dnZfqn_ednZ2d@giganews.com>
In reply to#78907
On 12/12/25 06:19, Carlos E.R. wrote:
> On 2025-12-12 11:26, The Natural Philosopher wrote:
>> On 11/12/2025 21:06, Carlos E.R. wrote:
>>> On 2025-12-10 11:24, The Natural Philosopher wrote:
>>>> On 10/12/2025 10:02, c186282 wrote:
>>>>> On 12/10/25 04:14, Andy Burns wrote:
>>>>>> c186282 wrote:
> 
> 
>>>> Now off to write the software that will look at it for me and warn 
>>>> me of things by email.
>>>> So I can get on with the next project.
>>>
>>> You mentioned thieves stealing fuel. You can also monitor for that. 
>>> You would need a fuel flow meter on the fuel line, or a sensor 
>>> telling when the furnace is working. Compare with the tank level 
>>> decreasing rapidly.
>>>
>>
>> The problem is that the sensor I built on the tank has no power except 
>> batteries: So it only wakes up occasionally and draws nanoamps in 
>> between.
>> I have completed the warning software that looks for low oil levels, 
>> loss of communication, a failing battery and unexpected changes in oil 
>> level, BUT it cannot do that in real time as the unit is only powered 
>> up for a minute or so every couple of hours.
>>
>> Depending on how long the batteries last I may increase the frequency 
>> of operation. But it can never be 'real time'
> 
> Ah.
> 
> What about a small solar panel and rechargeable batteries?


   Seeed sells the "LiPo Rider Plus". After checking
   several brands of 'solar charge controllers' these
   were the ones I chose to power my field projects.
   Most of the others did NOT cap the voltage very
   well, or at all, so the sun comes out bright and you
   might send 6+ into your 3.1v device.

   Combined with a 3 to 5 watt panel they'll keep even
   intermittent non-nano-power projects going.

   Beware the quality of the batteries though ... got
   some no-names, about 50x50x10mm square, that were
   generally good - but one DID explode on me, inside
   the office building, when I barely touched it. Had
   not been charged for months either. Oh well, nothing
   to do but watch the big crimson flame .......

   Fire control IS a priority with lithiums.

[toc] | [prev] | [next] | [standalone]


#78990

From"Carlos E.R." <robin_listas@es.invalid>
Date2025-12-13 13:30 +0100
Message-ID<es201mxcdp.ln2@Telcontar.valinor>
In reply to#78961
On 2025-12-13 05:42, c186282 wrote:
> On 12/12/25 06:19, Carlos E.R. wrote:
>> On 2025-12-12 11:26, The Natural Philosopher wrote:
>>> On 11/12/2025 21:06, Carlos E.R. wrote:
>>>> On 2025-12-10 11:24, The Natural Philosopher wrote:
>>>>> On 10/12/2025 10:02, c186282 wrote:
>>>>>> On 12/10/25 04:14, Andy Burns wrote:


>> What about a small solar panel and rechargeable batteries?
> 
> 
>    Seeed sells the "LiPo Rider Plus". After checking
>    several brands of 'solar charge controllers' these
>    were the ones I chose to power my field projects.
>    Most of the others did NOT cap the voltage very
>    well, or at all, so the sun comes out bright and you
>    might send 6+ into your 3.1v device.
> 
>    Combined with a 3 to 5 watt panel they'll keep even
>    intermittent non-nano-power projects going.
> 
>    Beware the quality of the batteries though ... got
>    some no-names, about 50x50x10mm square, that were
>    generally good - but one DID explode on me, inside
>    the office building, when I barely touched it. Had
>    not been charged for months either. Oh well, nothing
>    to do but watch the big crimson flame .......
> 
>    Fire control IS a priority with lithiums.
> 

Huh. That's not good when the thing is intended to be near a oil tank.

-- 
Cheers, Carlos.
ES🇪🇸, EU🇪🇺;

[toc] | [prev] | [next] | [standalone]


#79087

FromFritz Wuehler <fritz@spamexpire-202512.rodent.frell.theremailer.net>
Date2025-12-14 19:23 +0100
Message-ID<4795ac3fd5ad1428f38c093b2b1543ca@msgid.frell.theremailer.net>
In reply to#78834
The Natural Philosopher <...@invalid.invalid> [TNP]:
TNP> Depending on how long the batteries last I may increase the
TNP> frequency of operation.  But it can never be 'real time'

Have you considered using a couple of old 12V car/motorcycle batteries
(one at a time) instead?

[toc] | [prev] | [next] | [standalone]


#79138

Fromc186282 <c186282@nnada.net>
Date2025-12-15 01:55 -0500
Message-ID<ZB6cnXUwSuxwLaL0nZ2dnZfqnPadnZ2d@giganews.com>
In reply to#79087
On 12/14/25 13:23, Fritz Wuehler wrote:
> The Natural Philosopher <...@invalid.invalid> [TNP]:
> TNP> Depending on how long the batteries last I may increase the
> TNP> frequency of operation.  But it can never be 'real time'
> 
> Have you considered using a couple of old 12V car/motorcycle batteries
> (one at a time) instead?

   Those are BIG (and heavy and need special recharge).
   At least they don't detonate like Li-Ion batts.

   Had a weather station that used up batteries too fast.
   Wanted to convert it to solar charge with a small lead
   battery - 6v. Well, first you needed a 9-12v solar
   panel, easy enough, but then a converter to get that
   into the range a dedicated lead/acid charger could
   cope with AND the charger could NOT cause the circuit
   to see any more than 6v regardless of sun levels.
   Turned into a MESS.

   Solution ... 9v little solar, a resistor bridge to
   drop to about 6.5v and a 10w zener to suck up any
   over-voltage across the device power leads. The batt
   just got a small harmless 'trickle charge' which was
   enough to deal. Less tech = MORE in this case.

   IF the poster has made something with "nano-power"
   parts (easily had but most are meant to be used
   with automated assembly machinery/methods) then
   even a couple of non-recharable lithium batts
   ought to be OK.

   THESE days, looks like you can just send a Gerber
   file or equiv to a board-making outfit and they
   will produce even one-off assemblies for a
   (semi) affordable price. The humans do nothing,
   the machine does all the work. Doesn't care WHAT
   or how many.

   In his app, does he even NEED "real time" ?
   "Close Enough" may be Good Enough perhaps.

   Again, we tend to get hung up on the decimal
   places even when "ball park" is adequate for
   the particular need.

[toc] | [prev] | [next] | [standalone]


#79162

FromThe Natural Philosopher <tnp@invalid.invalid>
Date2025-12-15 17:49 +0000
Message-ID<10hphmm$22juh$3@dont-email.me>
In reply to#79138
On 15/12/2025 06:55, c186282 wrote:
> In his app, does he even NEED "real time" ?
>    "Close Enough" may be Good Enough perhaps.

No,m I get a report every two hours

I did design my own PCBs

I have a nano timer that reboots the board every 2 hours and then the pi 
shuts itself off again.




-- 
"A point of view can be a dangerous luxury when substituted for insight 
and understanding".

Marshall McLuhan

[toc] | [prev] | [next] | [standalone]


#79265

Fromc186282 <c186282@nnada.net>
Date2025-12-16 01:50 -0500
Message-ID<NWednR3tSZOpnNz0nZ2dnZfqnPadnZ2d@giganews.com>
In reply to#79162
On 12/15/25 12:49, The Natural Philosopher wrote:
> On 15/12/2025 06:55, c186282 wrote:
>> In his app, does he even NEED "real time" ?
>>    "Close Enough" may be Good Enough perhaps.
> 
> No,m I get a report every two hours

   So seven milliseconds is CRITICAL obviously  :-)

> I did design my own PCBs

   I've done a number from scratch ... photo-masks,
   evil chemicals, the whole bit.

   SOME use XYZ mini-routers to literally machine-out
   copper from boards. Ugly, but DOES work for many
   applications.

> I have a nano timer that reboots the board every 2 hours and then the pi 
> shuts itself off again.

   I have a few PIs that just use crontab to
   reboot once/twice/thrice a day. Working on
   cleaning up the app that clutters/slows
   them down. Found some of the problems.

   Now STARTING a Pi from scratch a few times
   a day, THEN you need an external timer device.

   Microcontrollers, most have low-power libraries
   that 99.99% shut 'em down until there's an interrupt,
   perhaps from a time chip. PIs however - they're
   natural power hogs ... NOT good for battery/solar
   operation.

   I used a lot of Ard 2560s for solar field devices.
   They have low-power libs and reduce to seriously
   low current draw. DID slice the traces out of
   the cheapo time chip on the board and used
   "ChronoDots" instead. Interrupt, and it all
   comes back to life.

   Oh, where an oSillyScope is a good thing ... had
   an odd issue where the board would reset for no
   obvious reason. Turned out I'd attached the time
   chip to a current-limited line ALSO shared by an
   external device. The device didn't use much power
   EXCEPT for maybe a sub-millisecond when it powered
   up. Probably caps charging. FOUND that deadly
   voltage dip with a scope, little else would have.
   Had kept looking for a software problem, but ...

[toc] | [prev] | [next] | [standalone]


#79276

FromThe Natural Philosopher <tnp@invalid.invalid>
Date2025-12-16 10:43 +0000
Message-ID<10hrd3p$2i9gm$7@dont-email.me>
In reply to#79265
On 16/12/2025 06:50, c186282 wrote:
> On 12/15/25 12:49, The Natural Philosopher wrote:
>> On 15/12/2025 06:55, c186282 wrote:
>>> In his app, does he even NEED "real time" ?
>>>    "Close Enough" may be Good Enough perhaps.
>>
>> No,m I get a report every two hours
> 
>    So seven milliseconds is CRITICAL obviously  :-)
> 
LOL


>> I did design my own PCBs
> 
>    I've done a number from scratch ... photo-masks,
>    evil chemicals, the whole bit.
> 
It was cheaper to send the files to china than buy the kit..

https://dirtypcbs.com

Back in about 10 days at silly prices.

>    SOME use XYZ mini-routers to literally machine-out
>    copper from boards. Ugly, but DOES work for many
>    applications.
> 
Ah. Mr Usagi.

Some use 3D printers to deposit low melting point solder as well

We use what we have to hand. I use cCorel draw. There is an online 
facility that turns that into the right format for PCB manufaturers.

>> I have a nano timer that reboots the board every 2 hours and then the 
>> pi shuts itself off again.
> 
>    I have a few PIs that just use crontab to
>    reboot once/twice/thrice a day. Working on
>    cleaning up the app that clutters/slows
>    them down. Found some of the problems.
> 
Yes. That reminds me, I need to put the watchdog in some of my daemons too
But in the case of the oil sensor clienbt this is physical 'shut off all 
power and stay down for two hours' Draws about 50nA in that period


>    Now STARTING a Pi from scratch a few times
>    a day, THEN you need an external timer device.
> 
>    Microcontrollers, most have low-power libraries
>    that 99.99% shut 'em down until there's an interrupt,
>    perhaps from a time chip. PIs however - they're
>    natural power hogs ... NOT good for battery/solar
>    operation.
> 
Looked at all that. Not good enough. I was going to build a CMOS timer 
then I stumbled across the TP1550 chip.

liitle 'breakout' boards were dirt cheap


>    I used a lot of Ard 2560s for solar field devices.
>    They have low-power libs and reduce to seriously
>    low current draw. DID slice the traces out of
>    the cheapo time chip on the board and used
>    "ChronoDots" instead. Interrupt, and it all
>    comes back to life.
> 
>    Oh, where an oSillyScope is a good thing ... had
>    an odd issue where the board would reset for no
>    obvious reason. Turned out I'd attached the time
>    chip to a current-limited line ALSO shared by an
>    external device. The device didn't use much power
>    EXCEPT for maybe a sub-millisecond when it powered
>    up. Probably caps charging. FOUND that deadly
>    voltage dip with a scope, little else would have.
>    Had kept looking for a software problem, but ...
> 
I used my sillyscope to see why the *!%$£ things was oscillating under 
power.

turned out to need serious capacitance on the output to stop the wrong 
sort of feedback triggering it


-- 
"And if the blind lead the blind, both shall fall into the ditch".

Gospel of St. Mathew 15:14

[toc] | [prev] | [next] | [standalone]


#79312

Fromrbowman <bowman@montana.com>
Date2025-12-16 20:40 +0000
Message-ID<mqduehFiccvU9@mid.individual.net>
In reply to#79276
On Tue, 16 Dec 2025 10:43:05 +0000, The Natural Philosopher wrote:

> On 16/12/2025 06:50, c186282 wrote:
>> On 12/15/25 12:49, The Natural Philosopher wrote:
>>> On 15/12/2025 06:55, c186282 wrote:
>>>> In his app, does he even NEED "real time" ?
>>>>    "Close Enough" may be Good Enough perhaps.
>>>
>>> No,m I get a report every two hours
>> 
>>    So seven milliseconds is CRITICAL obviously
>> 
> LOL
> 
> 
>>> I did design my own PCBs
>> 
>>    I've done a number from scratch ... photo-masks,
>>    evil chemicals, the whole bit.
>> 
> It was cheaper to send the files to china than buy the kit..

I wish I had that option back in the '70s. Doing the art work, creating 
the silk screens, etching, and drilling was a pain in the ass. Fortunately 
I hired an older woman who knew more about the etching part than I did and 
a lesbian who was happy to stand in front of a Bridgeport punching holes. 
I got funny looks from the management since it was an all male shop except 
for the front office but they weren't DEI hires. They were the best 
candidates for the positions. 

[toc] | [prev] | [next] | [standalone]


#79334

FromThe Natural Philosopher <tnp@invalid.invalid>
Date2025-12-17 01:05 +0000
Message-ID<10hsvk3$35lln$4@dont-email.me>
In reply to#79312
On 16/12/2025 20:40, rbowman wrote:
> On Tue, 16 Dec 2025 10:43:05 +0000, The Natural Philosopher wrote:
> 
>> On 16/12/2025 06:50, c186282 wrote:
>>> On 12/15/25 12:49, The Natural Philosopher wrote:
>>>> On 15/12/2025 06:55, c186282 wrote:
>>>>> In his app, does he even NEED "real time" ?
>>>>>     "Close Enough" may be Good Enough perhaps.
>>>>
>>>> No,m I get a report every two hours
>>>
>>>     So seven milliseconds is CRITICAL obviously
>>>
>> LOL
>>
>>
>>>> I did design my own PCBs
>>>
>>>     I've done a number from scratch ... photo-masks,
>>>     evil chemicals, the whole bit.
>>>
>> It was cheaper to send the files to china than buy the kit..
> 
> I wish I had that option back in the '70s. Doing the art work, creating
> the silk screens, etching, and drilling was a pain in the ass. Fortunately
> I hired an older woman who knew more about the etching part than I did and
> a lesbian who was happy to stand in front of a Bridgeport punching holes.
> I got funny looks from the management since it was an all male shop except
> for the front office but they weren't DEI hires. They were the best
> candidates for the positions.

Back in the 1970s I worked for companies that could pay the rates for 
commercial prototypes.

But I built it all on pegboard first.

-- 
For in reason, all government without the consent of the governed is the 
very definition of slavery.

Jonathan Swift

[toc] | [prev] | [next] | [standalone]


#79358

Fromc186282 <c186282@nnada.net>
Date2025-12-17 01:55 -0500
Message-ID<W1Odnb_bludDzt_0nZ2dnZfqn_ednZ2d@giganews.com>
In reply to#79334
On 12/16/25 20:05, The Natural Philosopher wrote:
> On 16/12/2025 20:40, rbowman wrote:
>> On Tue, 16 Dec 2025 10:43:05 +0000, The Natural Philosopher wrote:
>>
>>> On 16/12/2025 06:50, c186282 wrote:
>>>> On 12/15/25 12:49, The Natural Philosopher wrote:
>>>>> On 15/12/2025 06:55, c186282 wrote:
>>>>>> In his app, does he even NEED "real time" ?
>>>>>>     "Close Enough" may be Good Enough perhaps.
>>>>>
>>>>> No,m I get a report every two hours
>>>>
>>>>     So seven milliseconds is CRITICAL obviously
>>>>
>>> LOL
>>>
>>>
>>>>> I did design my own PCBs
>>>>
>>>>     I've done a number from scratch ... photo-masks,
>>>>     evil chemicals, the whole bit.
>>>>
>>> It was cheaper to send the files to china than buy the kit..
>>
>> I wish I had that option back in the '70s. Doing the art work, creating
>> the silk screens, etching, and drilling was a pain in the ass. 
>> Fortunately
>> I hired an older woman who knew more about the etching part than I did 
>> and
>> a lesbian who was happy to stand in front of a Bridgeport punching holes.
>> I got funny looks from the management since it was an all male shop 
>> except
>> for the front office but they weren't DEI hires. They were the best
>> candidates for the positions.
> 
> Back in the 1970s I worked for companies that could pay the rates for 
> commercial prototypes.
> 
> But I built it all on pegboard first.

   Mostly good ... but if it's higher-frequency circuits
   you can't properly proto on such a board. You need a
   REAL board to see if there are HF/RF cross-over and
   capacitance problems and such. Sometimes just slight
   repositioning of the traces can have large effects.

   Oh, wifi, had a remote PI on my network. Performance
   had become horrible since I got a new router+wifi.
   Moved it exactly FOUR INCHES plus a slight rotation
   the other day and the data rate went up 5X  :-)

   Black magic !

   Hmm ... may re-enable 2.4ghz on the router. The
   lower-freq signal seems to be kinder and gentler
   relative to device positioning. Yea, 2.4 is
   'slower' ... but if you can barely get a 5ghz
   signal then that's even MORE slow !

   PIs ... found an article, THINK it was about P4s,
   with instructions on how to put a REAL antenna
   on the things. Turns out they can have a VERY
   long range (maybe illegal in some places) with
   a spliced-in proper antenna.

   Now USA, with the recent demolition of over-fat
   federal agencies, NOBODY to look for your signal !
   MAYbe if you're 'commercial', but Joe Average will
   have to be ignored.

   DISadvantage of really long range - you become
   noticed/attractive to possibly malicious neighbors.
   They can let something like 'hydra' run for a
   week and find yer PW by brute force if they want.

[toc] | [prev] | [next] | [standalone]


#79369

FromThe Natural Philosopher <tnp@invalid.invalid>
Date2025-12-17 10:31 +0000
Message-ID<10hu0ps$3dela$2@dont-email.me>
In reply to#79358
On 17/12/2025 06:55, c186282 wrote:
> On 12/16/25 20:05, The Natural Philosopher wrote:
>> On 16/12/2025 20:40, rbowman wrote:
>>> On Tue, 16 Dec 2025 10:43:05 +0000, The Natural Philosopher wrote:
>>>
>>>> On 16/12/2025 06:50, c186282 wrote:
>>>>> On 12/15/25 12:49, The Natural Philosopher wrote:
>>>>>> On 15/12/2025 06:55, c186282 wrote:
>>>>>>> In his app, does he even NEED "real time" ?
>>>>>>>     "Close Enough" may be Good Enough perhaps.
>>>>>>
>>>>>> No,m I get a report every two hours
>>>>>
>>>>>     So seven milliseconds is CRITICAL obviously
>>>>>
>>>> LOL
>>>>
>>>>
>>>>>> I did design my own PCBs
>>>>>
>>>>>     I've done a number from scratch ... photo-masks,
>>>>>     evil chemicals, the whole bit.
>>>>>
>>>> It was cheaper to send the files to china than buy the kit..
>>>
>>> I wish I had that option back in the '70s. Doing the art work, creating
>>> the silk screens, etching, and drilling was a pain in the ass. 
>>> Fortunately
>>> I hired an older woman who knew more about the etching part than I 
>>> did and
>>> a lesbian who was happy to stand in front of a Bridgeport punching 
>>> holes.
>>> I got funny looks from the management since it was an all male shop 
>>> except
>>> for the front office but they weren't DEI hires. They were the best
>>> candidates for the positions.
>>
>> Back in the 1970s I worked for companies that could pay the rates for 
>> commercial prototypes.
>>
>> But I built it all on pegboard first.
> 
>    Mostly good ... but if it's higher-frequency circuits
>    you can't properly proto on such a board. You need a
>    REAL board to see if there are HF/RF cross-over and
>    capacitance problems and such. Sometimes just slight
>    repositioning of the traces can have large effects.
> 
>    Oh, wifi, had a remote PI on my network. Performance
>    had become horrible since I got a new router+wifi.
>    Moved it exactly FOUR INCHES plus a slight rotation
>    the other day and the data rate went up 5X  :-)
> 
>    Black magic !
> 
Yes. The RF board got to revision 13...
...

>    DISadvantage of really long range - you become
>    noticed/attractive to possibly malicious neighbors.
>    They can let something like 'hydra' run for a
>    week and find yer PW by brute force if they want.
> 

Nearest neighbour is outside wifi range. 250 metres or more.

-- 
For in reason, all government without the consent of the governed is the 
very definition of slavery.

Jonathan Swift

[toc] | [prev] | [next] | [standalone]


#79370

Fromc186282 <c186282@nnada.net>
Date2025-12-17 06:25 -0500
Message-ID<cZidnTxI1rOGDt_0nZ2dnZfqnPWdnZ2d@giganews.com>
In reply to#79369
On 12/17/25 05:31, The Natural Philosopher wrote:
> On 17/12/2025 06:55, c186282 wrote:
>> On 12/16/25 20:05, The Natural Philosopher wrote:
>>> On 16/12/2025 20:40, rbowman wrote:
>>>> On Tue, 16 Dec 2025 10:43:05 +0000, The Natural Philosopher wrote:
>>>>
>>>>> On 16/12/2025 06:50, c186282 wrote:
>>>>>> On 12/15/25 12:49, The Natural Philosopher wrote:
>>>>>>> On 15/12/2025 06:55, c186282 wrote:
>>>>>>>> In his app, does he even NEED "real time" ?
>>>>>>>>     "Close Enough" may be Good Enough perhaps.
>>>>>>>
>>>>>>> No,m I get a report every two hours
>>>>>>
>>>>>>     So seven milliseconds is CRITICAL obviously
>>>>>>
>>>>> LOL
>>>>>
>>>>>
>>>>>>> I did design my own PCBs
>>>>>>
>>>>>>     I've done a number from scratch ... photo-masks,
>>>>>>     evil chemicals, the whole bit.
>>>>>>
>>>>> It was cheaper to send the files to china than buy the kit..
>>>>
>>>> I wish I had that option back in the '70s. Doing the art work, creating
>>>> the silk screens, etching, and drilling was a pain in the ass. 
>>>> Fortunately
>>>> I hired an older woman who knew more about the etching part than I 
>>>> did and
>>>> a lesbian who was happy to stand in front of a Bridgeport punching 
>>>> holes.
>>>> I got funny looks from the management since it was an all male shop 
>>>> except
>>>> for the front office but they weren't DEI hires. They were the best
>>>> candidates for the positions.
>>>
>>> Back in the 1970s I worked for companies that could pay the rates for 
>>> commercial prototypes.
>>>
>>> But I built it all on pegboard first.
>>
>>    Mostly good ... but if it's higher-frequency circuits
>>    you can't properly proto on such a board. You need a
>>    REAL board to see if there are HF/RF cross-over and
>>    capacitance problems and such. Sometimes just slight
>>    repositioning of the traces can have large effects.
>>
>>    Oh, wifi, had a remote PI on my network. Performance
>>    had become horrible since I got a new router+wifi.
>>    Moved it exactly FOUR INCHES plus a slight rotation
>>    the other day and the data rate went up 5X  :-)
>>
>>    Black magic !
>>
> Yes. The RF board got to revision 13...
> ...


   Well, this was a Pi4 ....

   Anyway, NO other revisions ... just MOVED the thing
   a TINY distance and got VASTLY better performance.
   Just shows how iffy 5ghz wifi can be.


>>    DISadvantage of really long range - you become
>>    noticed/attractive to possibly malicious neighbors.
>>    They can let something like 'hydra' run for a
>>    week and find yer PW by brute force if they want.
>>
> 
> Nearest neighbour is outside wifi range. 250 metres or more.

   Lucky !

   I have more nearby.

   At least ONE might be an asshole. I think they
   injected a load of NAZI bullshit into my old
   printer - only stopped because all the paper
   was used up. Getting into a printer directly
   like that is not dead newbie skills.

[toc] | [prev] | [next] | [standalone]


Page 2 of 5 — ← Prev page 1 [2] 3 4 5  Next page →

Back to top | Article view | comp.os.linux.misc


csiph-web