Send Motion-user mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. Re: moving motion to a newer machine (Barry Martin)
----------------------------------------------------------------------
Message: 1
Date: Mon, 8 Aug 2022 09:09:58 -0500
From: Barry Martin <[email protected]>
To: [email protected]
Subject: Re: [Motion-user] moving motion to a newer machine
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Hi Dave!
> I now have an R Pi 3B+ that I can substitute for the old machine and
> hope that might give me an upgraded frame rate. It presently has buster
> on it, 32-bit I think (uname -m says armv71). So:
AFAIK Buster is 32-bit. /uname -m/ gives the processor type; /cat
/etc/os-release/ gives some of the information you're asking about but
not all.? ...I'm not sure how to tell the bit option? (looks like we'll
both be learning!)
> Q1 Would putting a 64-bit version of the OS on the machine be
> worthwhile? And regardless, it it worth upgrading to a newer OS release?
I have three RPi 4B's here.? Two are running Bullseye and the third
Buster.? With this limited experience I have not found a difference
running Motion? on Buster vs. Bullseye. All three seem to be equal,
running at 15 fps and an image of 720 (1080 caused some dropouts: gray
sections, image shifts, etc.)? So from what I see here no difference
between Buster and Bullseye, though I would go with 'the latest and
greatest' just to make future updating easier. Instructions for
Bullseye: https://motion-project.github.io/motion_build.html
<https://motion-project.github.io/motion_build.html>
And the big question as to why one is running Buster: about ten days ago
the SD card apparently became corrupted and failed to boot: halted at
the 'super pixel'.? The backup card was Buster so swapped that in.
The other two RPi's I had had problems with.? Originally one Pi running
two USB cameras -- not a good idea: overloads the USB channel -- says so
if you can find the one sentence.? Over time fiddle-fiddle with various
updates and swaps and tests -- amazing how much 'abuse' the Pi will
take!!? Separated the cameras to their own Pi - problem solved.? (I also
had a pair of faulty USB extension cables - that didn't help
troubleshooting!)
Also very important to keep the Pi itself cool.? One Bullseye unit is in
a metal case with the heat sink 'prongs', the second in? a metal case
with a 30 mm cooling fan and stick-to-the-ICs heat sinks.? The unit with
the fan is a about eight degrees Celsius cooler.? (The two are next to
each other in a closet.)
The Buster unit had some 'fun' experimentations.? I thought the UPS HAT
had failed/malfunctioned on the original unit so swapped in a new RPI
4B, so new (more different as had been used elsewhere) with a different
UPS HAT.? I like this UPS HAT much better, but cases don't fit.? Using
an acrylic case 'kit' which protects the top and bottom (solder-side of
the RPi, component side of the HAT) but leaves the sides open.? Well, at
least good ventilation!? Found the thing was running super-hot as shut
down! Even with the heat sinks was running over 80?C!? Plugged in a
little 5v cooling fan, aimed at the Pi, by the time I walked to the
other end of the house and ssh'd in the temperate had dropped
significantly. It's currently reporting 40.4?.
> Q2 Is armhf the correct version for 32-bit and arm64 presumably for 64?
As I mentioned earlier in my ramblings I'd go with 64-bit Bullseye just
so future updates are easier; you're more current.
> It's been a long time since I installed it so I've forgotten most of
> the procedure. I have some notes and have access to
> https://motion-project.github.io/motion_build.html
That's what I had used.
> Q3 I've copied /etc/motion from the old machine. Is there anything else
> I need to keep/copy apart from those config files?
>
> I know the config files have changed a bit but I expect I can figure
> out how to transfer settings to the new installation.
I would install the current version of Motion - make sure to select the
right one!? There have been corrections and improvements compared to the
old versions and may as well take advantage of the hard work.? I found
it worked quite well 'out of the box' -- major tweak was the
resolution.? I did use my original configurations as a guide for the new
one.
Hope this helps, and apologies for the ramblings but hope they were
somewhat useful.
Barry
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 194, Issue 4
*******************************************
