- This topic has 31 replies, 10 voices, and was last updated 7 years, 1 month ago by
.
-
Hi,
I’ve nearly the same configuration (7″ touch + jive lite + tsop4838@gpio + XBOX one remote clone) for both of my kids very stable and nearly indestructible.
At first I played around with some default key mappings like „KEY_RIGHT“ this worked – but the remote has a lot of more keys 😉
Since Jive Lite has no native IR/lirc support, I had to use irxevent:
1.) complete lircd.conf for all keys you wanted to use (for such a much-used remote like the XBOX one just download it somewhere ;-))
2.) take the whole needed mapping from IR-keys to the keyboard control of jive lite (reference: InputToActionMap.lua) in the lircrc config file
for example:# Remote: VolumeUp # Jivelite '+' begin remote = XBOX-ONE prog = irxevent button = VolumeUp config = Key plus jivelite endor for multiple keyboard action just double the block:
# Remote: big green button # jivelite at first stop playback 'C' begin remote = XBOX-ONE prog = irxevent button = XboxFancyButton config = Key shift-c jivelite end # Remote: big green button # jivelite second power off for display backlight 'q' begin remote = XBOX-ONE prog = irxevent button = XboxFancyButton config = Key q jivelite endInstead of
jiveliteyou may useCurrentWindowas target for the keyboard emulation and control even other applications with the mapped keys in the lircrc.3.) On startup you need a script which waits for the successfull start of lircd and jivelite to start finally irxevent e.g.
irxevent /etc/lirc/lircrcAlways check lircd for running correctly (e.g. via irw) – otherwise thee hardware.conf may be not correct…
Here is the script I start via crontab @reboot
#!/bin/bash # Nur ausführen, wenn jivelite im Autostart autostart=$(grep -a "jivelite=1" /opt/max2play/autostart.conf | wc -l) if [ $autostart -eq 0 ]; then echo "Jivelite nicht im Autostart - irxevent wird nicht gestartet!" exit 0 fi # Warten bis jivelite gestartet ist while [ -z "$(pidof jivelite)" ]; do sleep 1 done # Warten bis Lircd gestartet ist while [ -z "$(pidof lircd)" ]; do sleep 1 done if [ -z "$(pidof irxevent)" ]; then echo "Starte irxevent!" echo 'DISPLAY=:0 irxevent -d /etc/lirc/lircrc' else echo "Starte irxevent neu!" echo 'sudo kill “$(pidof irxevent)“' sleep 1 echo 'DISPLAY=:0 irxevent -d /etc/lirc/lircrc' fi exit 0Hi Heiner,
everything with my remote control works fine, if I wrote in the shell of the remote session this:
DISPLAY=:0 irxevent -d /home/pi/lircrc
but after a reboot of the Raspberry PI3, I have to do it every time again.
My Problem is, to do that string anywhere in the boot sequence.
I try it as a script whit crontab like follow:
#!/bin/bash
### BEGIN INIT INFO
# Provides: fb.sh
# Required-Start:
# Required-Stop:
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Starts & Stops fb.sh
# Description: Starts & Stops fb.sh
### END INIT INFO# Nur asuführen wenn jivelite im Autostart
autostart=$(grap -a „jivelite=1“ /opt/max2play/autostartconf | wc -l)
if [ $autostart -eq 0 ];
then
echo „Jivelite nicht im Autostart – irxevent wird nicht gestartet!“
exit 0
fi# Warten bis jivelite gestartet ist
while [ -z „$(pidof jivelite)“ ];
do
sleep 1
done# Warten bis Lircd gestartet ist
while [ -z „$(pidof lircd)“ ];
do
sleep 1
doneif [ -z „$(pidof irxevent)“ ];
then
echo „Starte irxevent!“
echo ‚DISPLAY=:0 irxevent -d /home/pi/lircrc‘
else
echo „Starte irxevent neu!“
echo ’sudo kill „$(pidofirxevent)“‚
sleep 1
echo’DISPLAY=:0 irxevent -d /home/pi/lircrc‘
fiexit 0
The script name is fb.sh and that is the crontab config:
@reboot /home/pi/fb.sh
I don’t know what is wrong in my script.
regards
CarstenHi Heiner,
yes the LIRC implementation is checked, but I modify the config.txt in /boot.
I change it to GPIO=17 and remove the GPIO OUT. I use a Hifiberry Digi+.
I told that everything works fine if I use this command in a shell:
DISPLAY=:0 irxevent -d /home/pi/lircrc, so my problem know is, that after a reboot of the raspbian OS,
i have todo it every time. I need help for a implementation of this command that it works after any reboot without my doing in the shell.
You must be logged in to reply to this topic.