Max2Play Home 2016 (en) › Forums › General Questions on Hardware and Max2Play Versions › PowerFail, Corrupt SD, SD Protect not in HiFi Berry 2.46? & Stretch Incommicado › Reply To: PowerFail, Corrupt SD, SD Protect not in HiFi Berry 2.46? & Stretch Incommicado
Hi Heiner, and as always thanks for your quick response and support!
1. Which versions of m2p for the RPi have SD Protect as an add-on? The only ones I have found are for ODROID.
And, by the way, LMS in the HiFiBerry version is optional, so SD Protect should be available in that version, as well.
Ok, so here’s what I really think: SD Power Protection is a Requirement. (period). Without it the Max2Play RPi is like a car that whenever it’s turned off can’t be started again until a tow truck is called to haul it to a garage where it can be fixed and started again. How acceptable would that be?
If someone can’t fix LMS then do this: create a simple RPi voltage threshhold detector, a super-cheap little RPi plug in, either generate an interrupt or, better yet, a voltage out-of-tolerance flag so that, when the voltage is too low the M2P Executive can suspend normal operation until the voltage is back in tolerance. It’s that easy.
2. http://max2play/ Here’s my theory: When a new m2p rpi is ethernet cabled into a system that has another m2p rpi there is a problem using http://max2play/ in a browser, the browser connection can’t be made because the address can’t be resolved even through the existing m2p rpi has had it’s name changed to, eg, „Big Blue“. „Big Blue“ of the existing device is different than the new one’s „max2play“ yet the browser doesn’t think they’re different.
This is what I’ve observed, yesterday: Firefox goes to http://max2play.com (with Google Search enabled) in the URL field. Chrome keeps max2play/ in the URL field, and displays:
„This site can’t be reached
max2play’s server IP address could not be found.
Did you mean http://max2play.com/?
Search Google for max2play
„Big Blue“ is not responding correctly so that it’s address can be differentiated from the „max2play“ address? A little more work to fix.
I don’t think it’s acceptable to turn off every m2p device on a network just to add a new one, I never have.
Logging into the router to determine the IP addresses of every connected device including the new cable-connected m2p device, and using that in a browser URL field works always.
That’s my 0.02Euro,