tiny-pilot / tinypilot

Use your Raspberry Pi as a browser-based KVM.
https://tinypilotkvm.com
MIT License
3.05k stars 255 forks source link

Add support for power/reset from DIY-IPMI #80

Open Fmstrat opened 4 years ago

Fmstrat commented 4 years ago

Leverage the reboot/power button functionality from https://github.com/Fmstrat/diy-ipmi

Relay board: https://www.amazon.com/dp/B0057OC5WK GPIO cables: https://www.amazon.com/gp/product/B01BV2A54G Wiring diagram: https://raw.githubusercontent.com/Fmstrat/diy-ipmi/master/Resources/Diagram.png

Tsaukpaetra commented 3 years ago

IMO relays for that are way overkill, they're sense lines (I think 5v falling-edge trigger?), so you should be able to use optocouplers to achieve this effect. 🤔

wesleyscaldwell commented 3 years ago

----- copying my comments from 803 -----

I think ATX pin is the better option. But that being said, maybe you can sell an add on relay module that connects to the pi.

Because for more permanent locations it's worth it to hook up the ATX pins, but for ad-hoc support locations a simple relay outlet might be easier.

db39 commented 1 year ago

A user on the forum is also interested in this functionality.

DeviousFusion commented 1 year ago

Would really appreciate if this was integrated in TinyPilot. While external ON/OFF switches are a good option, I think its best to use ATX pins. LED status will be helpful to know the system state.

binooetomo commented 11 months ago

My proposal for this feature is :

  1. TinyPilot send broadcast message via RS232.
    Message format is only 2 char, i.e: address,command
    where : A. 'address' is : A-Z B. 'Command': A=Power Off, B= Power On, C=Reboot, 'Status'

So if tinypylot say 'AC', it means : If You Node A, reboot your self.

  1. At the managed node, user must have some kind of micro controller (arduino?) that interpret this message and do the job (if the address is it's address).

  2. Network: a. TX pin from TinyPilot connected to RX pin of micro controller on all managed node, and b. RX pin from TinyPilot connected to TX pin of micro controller on all managed node.

Note:

  1. Set the baud rate as low as posible ... message is very short no need for extensive speed, and we got stability
  2. With this scenario, user can also extend the range directly or just make a simple additional device to make it talk different protocol (ie: RS485) All we ask is just TinyPilot 'say something' via it's RS232.