Understood. I guess you can connect the fan directly to other GPIO pins. Then the fan is always on, and you don't need a script.
Posts by Da Flex
-
-
Damn, what now?
Throw the Argon One case into the trash. It's the source of several issues on this forum (use the search function for evidence).
-
Da Flex that's not an appropriate comment/rebuke because XR819 is an Allwinner own-brand WiFi chip found on some older Allwinner boards. The specific device/OEM is irrelevant due to the not-supported state of the chip.
It's relevant for users, who don't know, which chips they have inside of their devices. Many of them only know the device name.
-
sghenkks Be more precise next time. You didn't mentioned your device, and you didn't mentioned the manufacturer of the WiFi chip.
-
Closed, because this thread is pointless.
-
How do I enable drivers in the kernel configuration?
This is not the Linux support forum. Figure it out elsewhere (Google, ChatGPT etc.).
-
Try the default skin.
-
Do I need to remove the other files such as keyboard.xml and the gpio info from the config.txt?
Yes, no need.
-
Nah. You only need the RPi Tools add-on, because it contains the Python GPIO library.
- Create the Python script inside of your /storage folder (e.g. /storage/scripts/gpio-reboot.py).
- Make it executable: chmod +x /storage/scripts/gpio-reboot.py
- Create /storage/.config/autostart.sh.
- Write the Python call into autostart.sh.: python /storage/scripts/gpio-reboot.py &
Then the script will run on every boot sequence.
-
Run this Python script from autostart.sh:
Python
Display More#!/usr/bin/python # This script was authored by AndrewH7 and belongs to him. # (www.instructables.com/member/AndrewH7) # You have permission to modify and use this script only for your own personal usage. # You do not have permission to redistribute this script as your own work. # Use this script at your own risk. import sys sys.path.append('/storage/.kodi/addons/virtual.rpi-tools/lib') import RPi.GPIO as GPIO import os # Replace YOUR_CHOSEN_GPIO_NUMBER_HERE with the GPIO pin number you wish to use. # Make sure you know which rapsberry pi revision you are using first. # The line should look something like this e.g. "gpio_number = 7". button_gpio_number = 3 # Use BCM pin numbering (i.e. the GPIO number, not pin number). # WARNING: this will change between Pi versions. # Check yours first and adjust accordingly. GPIO.setmode(GPIO.BCM) # It's very important the pin is an input to avoid short-circuits. # The pull-up resistor means the pin is high by default. GPIO.setup(button_gpio_number, GPIO.IN, pull_up_down = GPIO.PUD_UP) # Use falling edge detection to see if pin is pulled low to avoid repeated polling. # Send command to system to reboot. try: GPIO.wait_for_edge(button_gpio_number, GPIO.FALLING) os.system("shutdown -r now") except: pass # Revert all GPIO pins to their normal states (i.e. input = safe). GPIO.cleanup() -
Thank you for your reply.. So if i am reading it right EXT4 is fully supported my LibreELCE naively and kodi as no issues reading and writing to it?
Yes, EXT4 was made for Linux, and LibreELEC is Linux.
-
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
SSD1306 is part of the Luma.OLED API:
PostRE: OLEDproc Add-on
I think the issue for ssd1322 is solved.
I added a new parameter and oled starts to work.
1322 required mode = '1' as per
https://luma-oled.readthedocs.io/en/latest/api-documentation.html
luma.oled.device.greyscale.greyscale_device
I will come back to your last version for testing.livsJuly 31, 2022 at 12:27 AM Import your SSD1306 driver into your Python script:
Raspberry Pi: OLED-Display 128x64 mit Python ansteuern (I2C) - indiBit.deDieser Beitrag zeigt die Grundlagen, wie man ein Display am Raspberry Pi mit Python steuern kann. Im konkreten Fall wird ein 0,96 Zoll großes OLED-Display mit…indibit.de -
I can give you pirate "stuff" so you can pirate it yourself, if interested.
Declined.
Legal samples are here: https://kodi.wiki/view/Samples
-
Thread
OLEDproc Add-on
I just finished one little project. The work took me several weeks, but I believe it was worth it.
There are many OLED graphic displays on the market that are cheaper and look better than traditional (character) LCD displays.
I was sorry that so far these displays could not be used as a display for the Kodi multimedia center.
That is why I set myself the task of remedying this shortcoming. I am presenting the result of my work to you today.
The core of the solution is a new add-on called OLEDproc.…
LuRuApril 25, 2022 at 5:02 PM -
LE's RPi2 software is optimized to run on RPi2 and RPi3.
Could the hardware be the problem with the videos?
- Find a video from the Kodi sample library, that runs "stop-and-go" on your hardware: https://kodi.wiki/view/Samples
Use that sample to create and publish a log:
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link
-
Thread
Send text to kodi
I am running latest stable version of LibreElec, sending text to Kodi does not work from the web interface or by using Kore remote.
I have also tried running this command:
curl -v -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","method":"Input.SendText","params":{"text":"<text to send>","done":false},"id":1}' http://<host>:<port>/jsonrpc
it says it sent ok, but nothing is displayed?tb404October 29, 2019 at 8:53 PM