Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
hardware:lcd_led_marquees [2022/02/08 01:53] – added note about supported filesystems atari | hardware:lcd_led_marquees [2022/10/04 08:22] – removal of broken scripts atari | ||
---|---|---|---|
Line 38: | Line 38: | ||
</ | </ | ||
- | This is the lower resolution LED panel that's more suited to pixel-art display than full-color images. It's easy to tell this one from the LCD panel as it has a USB port on the back, while the LCD panel does not. | + | {{: |
- | Installation is simple. Power on the Pixelcade panel, plug in its USB port into the Batocera machine, [[: | + | This is the lower resolution LED panel that's more suited to pixel-art display than full-color images. It's easy to tell this one from the LCD panel as it has a USB port on the back, while the LCD panel does not. This panel comes in two sizes, pictured above is the smaller size next to an Xbox One controller. |
+ | |||
+ | Installation is simple. Power on the Pixelcade panel and plug in its USB port into the Batocera machine: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Then [[: | ||
<code bash> | <code bash> | ||
Line 58: | Line 64: | ||
This is the higher resolution LCD panel that's suited to displaying full-color images. It supports Wi-Fi and sends its signals over the network instead of a USB cable. It is also possible to use an Ethernet connection in case a fully wired setup is preferred. | This is the higher resolution LCD panel that's suited to displaying full-color images. It supports Wi-Fi and sends its signals over the network instead of a USB cable. It is also possible to use an Ethernet connection in case a fully wired setup is preferred. | ||
- | Installation uses a different command from the LED panel, so be careful. Power on the Pixelcade panel, | + | Installation uses a different command from the LED panel, so be careful. Power on the Pixelcade panel, |
<code bash> | <code bash> | ||
Line 110: | Line 116: | ||
</ | </ | ||
- | ===== Using an x86_64 PC and an RPi4 ===== | + | If you wish to simply see the events that are being fired off by Pixelcade' |
- | It is possible to homebrew up a D.I.Y. marquee display using a spare Raspberry Pi (RPi 4 was tested, but should work on any of them) connected to a display. [[https://forum.batocera.org/d/7129-dynamic-marquee-for-pi4-working|Link to the original forum post explaining this.]] Essentially, | + | < |
+ | killall java | ||
+ | /userdata/system/pixelcade/jdk/ | ||
+ | </ | ||
- | Artwork needs to be sourced and placed in the appropriate '' | + | Now you'll get the following debug output: |
- | Place '' | + | {{: |
- | <file bash game.sh> | + | ===== Using the two HDMI outputs on a RPi4 ===== |
- | # | + | |
- | System=$1 #system name | + | |
- | Romname=${2%.*} #romname | + | |
- | rom=${Romname## | + | |
- | / | + | |
- | </ | + | |
- | Place '' | + | It is possible to use the two HDMI outputs on an RPi4, with one displaying Batocera and the other displaying the dynamic marquee. [[https://forum.batocera.org/d/7129-dynamic-marquee-for-pi4-working|Link to the original forum post explaining this.]] Essentially, |
- | <file bash system.sh> | + | <WRAP center round important> |
- | # | + | This has broken on **v34** and higher. Stay on **v33** or lower if you intend to use this. |
- | System=$1 #System name | + | </WRAP> |
- | / | + | |
- | </file> | + | |
- | Place '' | + | ===== Using two computers ===== |
- | <file bash marquee.sh> | + | [[https:// |
- | #!/bin/bash | + | |
- | case $1 in | + | This can be done using Batocera installed onto a device and another computer/Raspberry Pi connected to a separate display. So far, this has been tested successfully using Batocera installed on an x86_64 computer/Raspberry Pi with another Raspberry Pi acting as the marquee. |
- | Start) | + | |
- | Romname=$3 | + | |
- | Gamepath=$2 | + | |
- | marqueeimage=$Gamepath/images/ | + | |
- | if [ -f "/userdata/ | + | |
- | then | + | |
- | ffmpeg -i / | + | |
- | + | ||
- | fi | + | |
- | + | ||
- | if [ -f "/ | + | |
- | then | + | |
- | fbv / | + | |
- | elif [ -f " | + | |
- | then | + | |
- | fbv $marqueeimage -fer | + | |
- | else | + | |
- | fbv / | + | |
- | fi | + | |
- | + | ||
- | ;; | + | |
- | Gameselected) | + | |
- | System=$2 #system name | + | |
- | Romname=$3 #romname | + | |
- | + | ||
- | if [ -f "/ | + | |
- | then | + | |
- | fbv / | + | |
- | elif [ -f "/ | + | |
- | then | + | |
- | fbv "/ | + | |
- | else | + | |
- | fbv / | + | |
- | fi | + | |
- | + | ||
- | ;; | + | |
- | + | ||
- | Systemselected) | + | |
- | imagepath="/ | + | |
- | if [ -f " | + | |
- | then | + | |
- | fbv " | + | |
- | else | + | |
- | fbv / | + | |
- | fi | + | |
- | + | ||
- | ;; | + | |
- | + | ||
- | esac | + | |
- | </ | + | |
- | + | ||
- | Place '' | + | |
- | + | ||
- | <file bash script.sh> | + | |
- | # | + | |
- | + | ||
- | case $1 in | + | |
- | gameStart) | + | |
- | + | ||
- | gamepath=${5%/ | + | |
- | romname=${5## | + | |
- | / | + | |
- | ;; | + | |
- | + | ||
- | gameStop) | + | |
- | killall ffmpeg | + | |
- | ;; | + | |
- | esac | + | |
- | </ | + | |
===== Troubleshooting ===== | ===== Troubleshooting ===== | ||
Line 214: | Line 145: | ||
==== My Pixelcade LED/LCD panel isn't working! ==== | ==== My Pixelcade LED/LCD panel isn't working! ==== | ||
- | It could be that it's simply not plugged in correctly. Ensure that the USB cable on both ends is firmly secure in their ports. On the Batocera machine itself, it might be worth checking if it's functional on a different port (such as a USB 3.0 port if you were using a 2.0 port, or vice-versa). | + | Pixelcade takes a few more moments after ES has started before it "kicks in". |
+ | |||
+ | If it's still not working, it could be that it's simply not plugged in correctly. Ensure that the USB cable on both ends is firmly secure in their ports (or if using the LCD panel, that it's paired to the same Wi-Fi network as Batocera). On the Batocera machine itself, it might be worth checking if it's functional on a different port (such as a USB 3.0 port if you were using a 2.0 port, or vice-versa). | ||
If it's still not working, try out the following: | If it's still not working, try out the following: | ||
Line 226: | Line 159: | ||
~/ | ~/ | ||
</ | </ | ||
- | * If using the LED panel (not the LCD one), run '' | + | * If using the LED panel (not the LCD one), run '' |
- hardware/lcd_led_marquees.txt
- Last modified: 7 days ago
- by nadenislamarre