![]() ![]() I wonder if there is a way to enable Wake-on-LAN for the embedded NIC. Only good thing, it really cuts the mains to the 5V wallet. The solution in the link above is bad as not real Wake-on-LAN, requires additional 12V supply and is nearly as expensive as the Pi itself. I can add the chip is still powered as the activity LED still blinks so the link is maintained and enough supply remains to trigger a reboot by sending a pulse to GLOBAL_EN or equiv GPIO. When enabling from latest Raspbian, I get the following error: sudo ethtool -s eth0 wol gĬannot set new wake-on-lan settings: Unknown error 524 Querying the embedded BCM54213PE NIC with ethtool reports d which means disabled which means supported. I'd like to understand how I could wake a Pi after shutdown/halt/power-off. Martin Held started following RF Hacking Hack Chat.I ask here although there is a good thread because I don't want a facebooq or googre account.lion mclionhead has updated the log for Auto tracking camera.lion mclionhead has updated the log for 3D printed truck.Colin Maykish has added a new log for Flounder Z180 SBC.Colin Maykish has updated the project titled Flounder Z180 SBC.Colin Maykish liked The Lo-Fi Guide to the Orchestra.pelrun on Lithium-Ion Battery Circuitry Is Simple.Joshua on TRX-Duo Is A Red Pitaya Clone For Software Defined Radio.Rick C on A Raspberry Pi Phone For The Modern Era.Chris Arena on Amateur Rocket Aims For The Kármán Line, One Launch At A Time.Jerry on Amateur Rocket Aims For The Kármán Line, One Launch At A Time.Nick on Should’ve Used A 555 - Or 276 Of Them.Rick C on Surface Mount Soldering Practice For Budding Electrical Engineers.John7 on Hackaday Links: October 9, 2022.This Week In Security: PHP Attack Defused, Scoreboard Manipulation, And Tillitis 1 Comment Posted in computer hacks, Microcontrollers Tagged ESP32, featherwing, museum, Uninterruptible Power Supply, ups Post navigation ![]() And while you’re here, make sure to check out our coverage of other UPS solutions, like this supercap UPS. How would you have tackled this problem? Sound off in the comments below. Working within the constraints of reality means that the less obvious fix often ends up being the right one. There are undoubtedly a variety of alternative solutions that appear ‘better’ on paper, but these may gloss over the potential costs and disruption to a multi-acre museum. This unit is powered by a non-UPS backed power outlet, meaning that it only sends the WOL signal in the morning when mains power is restored via the circuit breaker. To get around this, an ESP32 Featherwing and a little bit if CircuitPython code sends out WOL (wake-on-LAN) signals over Ethernet automatically on power up. While many computers can be enabled to boot on power loss, the UPS and safe shutdown scripts meant that this wasn’t an option. This script then relays the shutdown signal from the UPS to every other computer in the museum, before shutting itself down for the evening. To get around this, the Windows task scheduling service was setup to be triggered by the UPS shutdown signal, which itself then triggered a custom Python script. However, each 300 watt UPS unit is very capable of powering multiple computers, the only limitation is the shutdown signal and the single USB connection. These are off-the-shelf consumer grade units, and were never intended to safely shut down more than one computer at a time. ![]() This in itself solves nothing – while the UPS can trigger a safe shutdown via USB, this signal could only be received by a single PC. Without drastically changing the one-touch end-of-day procedure, the only way to properly shutdown the hundreds of computers embedded in the museum exhibits involved using several UPS units, keeping the PCs briefly powered on after the mains power was cut. Tasked with finding a solution, mixed off-the-shelf UPS (uninterruptible power supply) hardware, a Featherwing and some Python to give the museum’s computer-run exhibits a fighting chance. However, financial concerns ruled out commercial computer management solutions, and manually shutting down each exhibit at the end of the day is not practical. Computers tend to get cranky when improperly shutdown, and there’s an non-zero risk of data loss. Flicking a circuit breaker to power cycle hundreds of desktop computers inside interactive museum exhibits is hardly ideal. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |