View Full Version : Imon 15c2x0036 VFD/IR problems
fayelund
2009-03-05, 22:50
Hi i have got both lirc and lcdproc running. lirc creates both /dec/lirc0, /dec/lirc1, /dev/lcd0 and /dev/lcd1. The display works fine through lcdproc, and through xbmc.
The issue is that the RC wont work at all! I have tried irw, and it registers nothing.
i have also tried irrecord, but it fails with:
irrecord: could not get hardware features
irrecord: this device driver does not support the new LIRC interface
irrecord: make sure you use a current version of the driver
irrecord: could not init hardware (lircd running ? --> close it, check permissions)
Does anyone have a clue what to try next?
did you kill lircd before running irrecord ?
fayelund
2009-03-06, 09:33
did you kill lircd before running irrecord ?
Yes, did not help.
I did find a solution though, but cant try it for some hours yet. I will try to change
REMOTE_ARGS="$REMOTE_ARGS --output=/dev/lircd --listen"
to:
REMOTE_ARGS="$REMOTE_ARGS --output=/dev/lircd1 --listen"
and
TRANSMITTER_ARGS="$TRANSMITTER_ARGS --output=/dev/lircd1 --connect=localhost:8765 --pidfile=/var/run/lircd1.pid"
to:
TRANSMITTER_ARGS="$TRANSMITTER_ARGS --output=/dev/lircd --connect=localhost:8765 --pidfile=/var/run/lircd1.pid"
hopefully this will help....
(found this in the tread: http://codeka.com/forums/viewtopic.php?f=3&t=85)
rodercot
2009-03-06, 14:36
That solution will likely not hold on a reboot. your remotes /dev/lirc0 will become /dev/lirc1 device and vice versa.
What equipment are you using. I have an imon ffdc model with the ir and I use the ir in the case with the MCE 1029 remote and then the MCE dongle to transmit. I know the 0036 can be a bit of a pain but I am not sure as to why it is registering two lirc instances.
FYI irrecord needs to run like so
Sudo su
ps ax | grep lirc (to get the pid number)
kill XXXX (x = pid number from above)
irrecord --device=/dev/lirc(0 or 1) "output file"
This is a good resource to bookmark for more than one lirc device.
http://www.eggshellskull.com/lirc/blaster/index.php
Dave
fayelund
2009-03-06, 18:04
well solution did not work.
Have killed lirc, biut irrecord still gives the same error.
My equipment is a Chieftec HM-01 with built in iMon VFD and IR, im using the supplied Imon PAD RC.
After what ive read lirc registers to instances is becaus of the knobs on the case.
rodercot
2009-03-06, 21:14
OH Yes!!! The knobs, do you have the buttons as well. Do a serach for Ron Frazier and check out his site, he has good info on this stuff as well. You are going to need to setup udev rules or at least aliases for all your lirc devices.
in my /etc/modprobe.d/aliases I have set an alias for lirc_imon and lirc_mceusb forcing them to lirc0 and lirc1 and in your case maybe a lirc2 for a dongle if you have one as well.
Then in my /etc/rc.local file I created the device lirc0 and lirc1 listen rules and this works pretty much 99% of the time but I did not have to edit my init.d lirc start up script at all.
You can also search for the Thermaltake case and as well the silverstone LC models I believe use the 0036 device.
Dave
rodercot
2009-03-06, 21:17
well solution did not work.
Have killed lirc, biut irrecord still gives the same error.
My equipment is a Chieftec HM-01 with built in iMon VFD and IR, im using the supplied Imon PAD RC.
After what ive read lirc registers to instances is becaus of the knobs on the case.
Yes you are likely going to have to kill both pids one for lircd and for lircd1 sockets, I thought that killing lircd would actually stop the second one as well AND that could be the whole problem with irrecord, it is killing the second instance as well and thus not seeing anything on the ir input.
Dave
You could try is mode2 works.
First kill lircd, then run mode2 for each device in a separate window at the same time.
mode2 --device=/dev/lirc0 --raw
mode2 --device=/dev/lirc1 --raw
rodercot
2009-03-06, 21:24
You could try is mode2 works.
First kill lircd, then run mode2 for each device in a separate window at the same time.
mode2 --device=/dev/lirc0 --raw
mode2 --device=/dev/lirc1 --raw
Ronie,
I do not think he can do that because killing lircd will STOP lircd1 as well, will it not? Scratch that - yes you are right If in fact stopping lircd does kill lircd1 as well, you should be able to send to both device lirc0 and lirc1 as per your irrecord command line. Just try and see which one works. you could also try a -f in your irrecord command line to force raw.
Can you issue a ls -l /dev/lirc* after killing in the pid in SU mode and see if you still have a lirc0 and lirc1 device.
Dave
fayelund
2009-03-06, 22:25
Updated to ubuntu 9.04, now the mode2 commands produce output! finally going somwhere...
fayelund
2009-03-06, 22:42
well, lirc will still not recieve anything, but i think that is related to how i start lirc
rodercot
2009-03-06, 22:50
The ideal thing to do IS getting one device working perfectly and then setup the next device and so on, I am not sure of you can disconnect the knob/button part for the time being and just get the vfd and ir working first.
Dave
fayelund
2009-03-07, 14:06
well it seems like mode2 recieves sometimes, but sudenly it stops and everything seems dead again.
It's important to run mode2 for /dev/lirc0 and /dev/lirc1 at the same time, as explained in this (http://mythtvblog.blogspot.com/2008/04/getting-imon-0038-lcd-working-with-lirc.html) howto:
The iMON buffers up the inputs from each device separately, but maintains the sequence of events between the 2 buffers. If you only run the lirc1 device, everything will work fine until the iMON picks up an IR signal that it decides to put in the lirc0 buffer. When that happens, the lirc1 buffer will appear to have locked up and will not generate any more events. In reality, it's just maintaining the event sequence, and the next event is waiting to be removed from the lirc0 device. Until you do that, you will see no more events coming from the lirc1 device.
fayelund
2009-03-07, 18:58
It's important to run mode2 for /dev/lirc0 and /dev/lirc1 at the same time, as explained in this (http://mythtvblog.blogspot.com/2008/04/getting-imon-0038-lcd-working-with-lirc.html) howto:
Well that worked fine, thanks. I am still in the dark on making the RC talk to lirc though...
fayelund
2009-03-10, 07:43
well its up and running now, had to turn to ubuntu 8.10 and 32.bit. This worked like a charm (except for some minor problems with some of the buttons repeating earlier sent commands). Thanks for the help, have posted a problem for my new problem at codeka.com, since it is not related to xbmc at all, and probably a config or driver error.
alanwww1
2009-04-12, 21:23
well its up and running now, had to turn to ubuntu 8.10 and 32.bit. This worked like a charm (except for some minor problems with some of the buttons repeating earlier sent commands). Thanks for the help, have posted a problem for my new problem at codeka.com, since it is not related to xbmc at all, and probably a config or driver error.
How did you solve the problem ?
I still can not use the pad and the numbers on the remote.