MobileRead Forums - View Single Post - NickelMenu: An integrated launcher for Kobo eReaders

javl · 06-27-2021, 06:06 PM

Currently how this works is I have a Raspberry Pi Pico hooked up to the serial port on the Clara. Pressing the button closes the circuit between the port's VCC and the Pico, starting the Pico (so it doesn't use any power until you press the button). On boot the Pico sends out a single serial signal. A script checks the serial port and triggers a fake tap on the screen when it detects this signal.

Maybe I should explore my second option: when you plug in your USB cable it gets detected even when in this idle state, right? So I was thinking of hooking up a switch to a small USB powerbank and hooking my script into this power detection. I'm just not sure these short bursts of power (like a second every time you press the button) won't damage anything. Also, the USB plug seems to be a fragile point (but I could solder to the PCB instead).

Edit: ahh I see, the 500 is a 500ms delay. I was just looking for '500' in the docs. Didn't occur to me it was one of the regular arguments, sorry.

06-27-2021, 06:06 PM	#540
javl Junior Member Posts: 5 Karma: 10 Join Date: Sep 2016 Device: Kobo Touch 2.0	Currently how this works is I have a Raspberry Pi Pico hooked up to the serial port on the Clara. Pressing the button closes the circuit between the port's VCC and the Pico, starting the Pico (so it doesn't use any power until you press the button). On boot the Pico sends out a single serial signal. A script checks the serial port and triggers a fake tap on the screen when it detects this signal. Maybe I should explore my second option: when you plug in your USB cable it gets detected even when in this idle state, right? So I was thinking of hooking up a switch to a small USB powerbank and hooking my script into this power detection. I'm just not sure these short bursts of power (like a second every time you press the button) won't damage anything. Also, the USB plug seems to be a fragile point (but I could solder to the PCB instead). Edit: ahh I see, the 500 is a 500ms delay. I was just looking for '500' in the docs. Didn't occur to me it was one of the regular arguments, sorry. Last edited by javl; 06-27-2021 at 06:11 PM.