+- Forum (http://forum.xbian.org)
+-- Forum: Hardware (/forum-7.html)
+--- Forum: Remotes and CEC support (/forum-26.html)
+--- Thread: USB Infrared Toy v2 from dangurous prototypes (/thread-2776.html)
Pages: 1 2
RE: USB Infrared Toy v2 from dangurous prototypes - kasteleman - 25th Feb, 2015 12:49 AM
(24th Feb, 2015 11:43 PM)CurlyMo Wrote:(24th Feb, 2015 11:26 PM)kasteleman Wrote:Then don't quote old posts(24th Feb, 2015 10:37 PM)CurlyMo Wrote: You didn't install the latest deb.Yes i did!
I you have a working setup, i will add your files to the package so all users can use the IRToy from then on.
Have added irtoy.conf in /etc/lirc/hardware with the following content:
# /etc/lirc/hardware/irtoy.conf
#
# Arguments which will be used when launching lircd
LIRCD_ARGS="--listen=8765"
#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD=false
#Don't start irexec, even if a good config file seems to exist.
#START_IREXEC=true
#Try to load appropriate kernel modules
#LOAD_MODULES=true
# Run "lircd --driver=help" for a list of supported drivers.
DRIVER="usb_irtoy"
# usually /dev/lirc0 is the correct setting for systems using udev
DEVICE="/dev/ttyMCA0"
#MODULES=""
# Default configuration files for your hardware if any
#LIRCD_CONF=""
#LIRCMD_CONF=""
added --listen=8765 so my domoticasystem can use the irtoy over the network!
Configfiles for the remotes follow....
Also added a case to the hardware.conf file:
*"Prototypes"*)
. /etc/lirc/hardware/irtoy.conf
;;
The only thing i'm wondering about is the following in that file:
. /etc/lirc/hardware/custom.conf
if [ -z $LIRCD_ARGS ] && [ -z $LOAD_MODULES ] && [ -z $DRIVER ] && [ -z $DEVICE ] && [ -z $MODULES ] && [ -z $LIRCD_CONF ] && [ -z $LIRCMD_CONF ]; then
case "$DMESG" in
*"lirc_rpi"*)
Why do you use the custom.conf and then after "then" the case for "$DMESG"?
I thought you first catch the case for DMESG and if case match use specific conf file.
If no case match, then you use custom.conf. Specific reason for that, or do i misunderstand the syntax?
RE: USB Infrared Toy v2 from dangurous prototypes - CurlyMo - 25th Feb, 2015 01:03 AM
Can you post this info on github. That's were the developers read normally.
RE: USB Infrared Toy v2 from dangurous prototypes - kasteleman - 25th Feb, 2015 01:06 AM
(25th Feb, 2015 01:03 AM)CurlyMo Wrote: Can you post this info on github. That's were the developers read normally.
XBian github and my question about hardware.conf?
RE: USB Infrared Toy v2 from dangurous prototypes - CurlyMo - 25th Feb, 2015 01:33 AM
Post that as well on the XBian github.
RE: USB Infrared Toy v2 from dangurous prototypes - kasteleman - 26th Feb, 2015 05:51 PM
(25th Feb, 2015 01:33 AM)CurlyMo Wrote: Post that as well on the XBian github.
issue reported on github
Almost forgot:
Config of Yamaha rav333 remote:
begin remote
name rav333
bits 32
flags SPACE_ENC|CONST_LENGTH
eps 30
aeps 100
header 8933 4466
one 554 1652
zero 554 558
ptrail 555
repeat 8934 2241
gap 106793
toggle_bit_mask 0x0
begin codes
sleep 0x5EA10CF3
power 0x7E8154AB
hdmi1 0x5EA1E21C
hdmi2 0x5EA152AC
hdmi3 0x5EA1B24C
hdmi4 0x5EA10AF4
av1 0x5EA1CA34
av2 0x5EA16A94
av3 0x5EA19A64
av4 0x5EA13AC4
av5 0x5EA1FA04
audio1 0x5EA1A658
audio2 0x5EA116E8
v-aux 0x5EA1AA55
tuner 0x5EA16897
fm 0xFE801AE4
am 0xFE80AA54
memory 0xFE80E618
presetup 0xFE80DA24
presetdown 0xFE807A84
tunigup 0xFE808678
tuningdown 0xFE8026D8
movie 0x5EA111EE
music 0x5EA1916E
stereo 0x5EA129D6
surdecode 0x5EA1B14E
straight 0x5EA16A95
info 0x5EA1E41A
volumeup 0x5EA158A7
volumedown 0x5EA1D827
mute 0x5EA138C7
end codes
end remote
RE: USB Infrared Toy v2 from dangurous prototypes - packetgeek - 8th Mar, 2015 12:06 PM
Did they ever get around the USB IRToy's crashing problem? I've been able to get it to work for short periods of time but the IRToy likes to drop out after a few minutes of idle time. Just to head off the suggestion, I did try changing the timeout on the USB port. It didn't prevent the crash.
After a few weeks of attempting various work-arounds, I ended up tossing the IRToy into the junk box, with a slight hope that Dangerous Prototypes would fix the firmware.
- Tim