What's the switch' part number? Where did you get it from? Maybe a little research can show how the switch LED is connected internally.
When you mentioned LED, is that the LED connected to the Contolblock or the LED on the switch?
If you power the RPi using the microUSB of the RPi itself you will loose the power switch and reset functions on the Powerblock. When the Powerblock is used as designed using its microUSB connector, power to the RPi is controlled by the Powerblock and routed to the Power and Ground pins of the GPIO connector. When the RPi is booted up the driver and control service of the Powerblock will initialy interrogate the status of the Powerblock board and intitiate the boot up process. If the microUSB on the RPi is used to as power source, all of this is bypassed and the RPi will power up as if the Powerblock does not exist.
The only way to use microUSB on th RPi together with the Powerblock is to isolate the RPi's micrUSB connections from the RPi itself (cut the traces from the RPi) and rewire them to the Powerblock's microUSB connector. Doing so is a mute, waste of time, potentially damaging to the RPi exercise.
@loonyboi Thanks! I wasn't sure if you meant to mirror the controls by ES' UI or at file system level by copying their config files. So if I understand you correctly, setting them up identically in ES does suffice.
I guessed as much, just me beeing a linux n00b. Thanks and sorry for wasting your time. Still, this could have been prevented with clearer instructions. It went fine with installing the software though, nice and easy to copy the commands, all clear there. Just small things like this one that you who know command line better maybe don’t realize that others don’t get.. Thanks again.
OK, this is probably my last post on this matter. It isn't solved, by any stretch of the imagination, but i do have a workaround!
I don't believe that the short has fried anything, the controlblock is still working exactly as advertised, but it DID scramble the outputs. All the outputs are still there, just in different places!
If it is possible to re-flash the firmware i think it would restore the normal operation, but that is just a hunch, and as it stands now i am not willing to take the risk.
Just in case someone out there ever has a similar problem i'm posting how i rewired the controlblock:
WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING!
THIS WON'T WORK ON YOUR SYSTEM, IT FIXED MY SYSTEM ONLY. I ONLY POST HERE TO SHOW WHAT THE SHORT DID TO MY CONTROLBLOCK!
In the end i rewired my project to match the new outputs of the scrambled Controlblock as follows:!
Hope that helps, if anyone else finds themself in a similar situation!
END WARNING! END WARNING! END WARNING! END WARNING! END WARNING! END WARNING! END WARNING! END WARNING!