This whole subject was "up front" in the community for some time, but then died down. It is this that makes one wonder if it was solved, or not.
My problem is that the shutdown varies due to the personnel who are working that night (those flipping the switches). I don't have the luxury of knowing that at x:pm the gates are closed, then x+12 minutes later the power is turned off. Sometimes it is 30 minutes later, sometimes one member of the night's crew is closing the gate when the other is headed to the main power switch. This could mean as little as a minute or two after closing time.
I'll work on the timing and see what the shortest time I need before turning things off is.
Dave's thought of lessening the amount of writes to the card is good information. I do believe that is where all the corrupt files came from.
As far as using the EMMC, wasn't the overall SOP to move the files off of the EMMC and onto the flash drive presented a couple of years ago? I remember folks doing just that as a matter of course.
We are using Kulp K8-B units for these props. The information as to their reaction to power being turned off is most welcome.
Thanks everyone for your input.
Al
Hi Al. How is this for a wild idea: Create a small application that listens for a specific message on a specific port and executes a "shutdown now" command (I think FPP has this). Shutdown takes about 45 seconds. Then the shutdown procedure for the crew is: type "YourCommandName" into a pc/laptop. Wait for the command to finish, turn off power. Have the script broadcast the shutdown message to the FPPs and then have it delay for a minute before exiting. If you wanted to make it smart you could have it ping a list of FPPs waiting for them to stop responding and return when they all go silent.
You could just set up some Google smart plugs going to the controllers and set the timers to be on during a slightly wider time window than the controllers are on. They need wifi to set the timers, but not to honor them once they are set. And then the instructions to the volunteers is simple:. when the show stops running, turn the power off.
1pet2_9 wrote:I always set up a cron to do a polite shutdown several minutes before a power down. I did notice that is harder to do when running FPP, so maybe that is the root of some of...whatever problems people are facing. If it's intermittent bad sectors on your card, that is a known problem when you don't nice shutdown your Pi.
You can run scripts from fpp as part of your playlist thus you can add shutdown scripts to your playlist leadout and the pi/beaglebone will shutdown once your show is over. Thats I changed to doing it this past year. It works great as you can extend your show time and not have to worry about the pi/beaglebone shutting down.
Sorry, but Google Smart Plugs require electricity AND an Internet link. Good idea for an at home/house setup.
The trigger idea is being seriously looked at. The problem is some of our folks have to be shown what the keyboard on a laptop is. :spox:
Reaching back into my bag of "old" tricks, I came across a battery backup for RPi I tried many years ago. Literally, a battery unit connected directly to the RPi to keep it up when the power goes down (a mini-UPS). If power does not return within a specified amount of time, a script could be run to shutdown when it sees it is not receiving source power. The battery keeps it up long enough to shutdown properly, and then would turn itself off. Now to adapt this to a Kulp and Beagle setup.
