ControlBlock Installed - But Doesn't shut down PI
I've also tried as others have stated - Installing the drivers directly from Retro-Pie setup, With no luck - after enabling the driver and rebooting - I will have a pulsing LED
My next step is to flash my SD card - reinstall a clean install of Retropie 4.5.1 and try to install the drivers directly from there.
I don't believe the controlblock is faulty - I believe it's an issue with the driver which is beyond my understanding.
Thank you for your help - Look forward to your feedback.
final update on my end :
Tested by flashing 4.5.1 retropie to SD card ->Booted PIE -> Installed driver from retro pie setup -> driver -> control block.
It installed and I enabled the driver and rebooted. After system came up - Led was still pulsing - I went to configure the joystick "4 game pads detected" so the Controlblock player 1 + 2 were detected ( my ps4 controller and USB keyboard were plugged in) But Icould not configure the buttons. (This is probably because i did not disconnect the wires from the controlblock prior to installing the driver)
Hope we find a solution!
Ok, I can reproduce the issue. arcade controls via ControlBlock are working, but the power button does not work as expected. Something must have slipped through with the latest driver update. I will fix that today and give you an update here.
Sorry for that!
Thank you! This is FANTASTIC NEWS! I thought I was going crazy.
I'm happy we were able to reproduce the issue so that if anyone else is affected they can find the solution in this thread and save themselves the time troubleshooting!
Thank you for your help, I look forward to the fix.
I tracked down the cause to the Raspberry Pi driver side - and not the ControlBlock firmware. That is for sure and good news. I will now work on a fix for the driver. Plan to release it sometime this evening.
By any chance do you know if the driver was broken for all versions of Retropie? Do you think the new driver will fix it for future and past releases as well?
Looking forward to the update.
I have just released the updated driver at Github.
The driver is the same for all RetroPie versions.
it would be great if you could give feedback here if that solves the issues on your side.
@petrockblog thanks Petrock.
I will test this within the hour and report back.
@petrockblog Good News! It's working now. The LED went solid right after the quick install method. Power Switch confirmed working!
Glad to hear that!
k0zmir last edited by k0zmir
ok, hope things are working for you now.
Thanks PetrockBlog! I just installed the Control Block on a Raspberry Pi 4 but due to the cooler I had to use dumont connectors - turns out i had 2 wires crossed - which solved my issue.
One question I do have now though... On my RP3 i got a message when i hit my shutdown button that shutdown script had been initiated and it was shutting own. It was a quick screen of terminal text.
On the RP4 though - The system just shuts down and there is no text regarding the shutdown script. Can you confirm on the RP4 this is correct? Or is there a way i can check to ensure the controlblock is running the shutdown script and i'm not just cutting power?
Glad to hear that!
The PowerBlock only cuts the power if it observes the corresponding signal.
You should be able to see log entries of the PowerBlock in the log file
I had a look at the system log and here are the first few lines of when i started the shutdown.
May 17 22:38:30 retropie systemd: Stopped target Sound Card.
May 17 22:38:30 retropie systemd: Stopping Session c1 of user pi.
May 17 22:38:30 retropie systemd: Stopped target Multi-User System.
May 17 22:38:30 retropie systemd: rpi-eeprom-update.service: Succeeded.
May 17 22:38:30 retropie systemd: Stopped Check for Raspberry Pi EEPROM updates.
Does that look right to you? Or what should i be looking for?
Sorry, I confused it with the PowerBlock.
The logs of the ControlBlock should be in in the file
2020-05-19 03:30:50.802 DEBUG  [Logger::logMessage@18] Starting ControlBlock driver.
2020-05-19 03:30:50.811 DEBUG  [Logger::logMessage@18] Created configuration. isEnabled: true, address: 0, pad type: arcade, power switch: true, only one gamepad: false
2020-05-19 03:30:50.812 DEBUG  [Logger::logMessage@18] Created configuration. isEnabled: false, address: 2, pad type: arcade, power switch: false, only one gamepad: false
2020-05-19 03:30:50.838 DEBUG  [Logger::logMessage@18] Enabled power signal.
2020-05-19 03:30:50.838 DEBUG  [Logger::logMessage@18] Created PowerSwitch. doShutdown: 1
2020-05-19 03:30:50.838 DEBUG  [Logger::logMessage@18] Starting gamepad polling ...
Looks like it's calling the Shutdown in the second last line!
Have you heard about any undervoltage warnings when using the control block with a Raspberry Pi 4?
Ever since I switched it over to my Rp 4 i've been getting under voltage warnings. I'm using the same canakit power supply i used on my Rp3 through the control block. The only USB device i have plugged in as a logitech wireless keyboard dongle.
Answered my own question. I'm using a Canakit 5v - 2.5amp Mirco-Usb raspberry 3 charger.
Because the PI4 requires 5.v at 3 amp my Canakit Micro Usb is underpowering it via the Micro Usb power on the RP4.
To rectify this I ordered the "Argon ONE Raspberry Pi UL Listed Power Supply 5.25 Volts 3 Amps" off amazon.
I'm certain this will resolve my under voltage issues.