Menu
▾
▴
lirc-list
|
From: hari j. <ha...@gm...> - 2009-12-08 12:39:52
|
Hi
I am trying to get lirc irblaster to send signals using an irblaster I
bought online .
Since I had a new remote I first used a irreceiver to record signals and
created a lircd.conf
I then connected the irblaster. When I send a signal to the port. I get a
connection refused.
The messages and my lircd.conf are given below
I am quite confused , as my dmesg says it detected a receiver even though
its the transmitter that is plugged in.
Also I am assuming my /etc/init.d/lirc starts everything and loads
lirc_serial
I am running 64 bit ubuntu and lirc 0.8.3
I am attaching various outputs below
I dont know what I am doing , but I am hoping someone can point me in the
right direction
hari
#########
/dev
###########
The permissions on my node are
~$ ls -al /dev/lirc*
crw-rw-rw- 1 root root 61, 0 2009-12-08 07:03 /dev/lirc0
##########
error messages
###########
$ irsend -d /dev/lirc0 SEND_ONCE THOMSON_DCI1011COM 1
irsend: could not connect to socket
irsend: Permission denied
$ sudo irsend -d /dev/lirc0 SEND_ONCE THOMSON_DCI1011COM 1
irsend: could not connect to socket
irsend: Connection refused
############################
dmesg
after I load the modprobe lirc_serial
##############################
239.368233] lirc_dev: IR Remote Control driver registered, major 61
[ 239.368608] lirc_serial: no version for "lirc_unregister_plugin" found:
kernel tainted.
[ 239.867259] lirc_serial: auto-detected active low receiver
[ 239.867263] lirc_dev: lirc_register_plugin: sample_rate: 0
############
My /etc/ lircd.conf
############
more /etc/lircd.conf
# Please make this file available to others
# by sending it to <li...@ba...>
#
# this config file was automatically generated
# using lirc-0.8.3pre1(default) on Mon Dec 7 23:17:40 2009
#
# contributed by
#
# brand: THOMSON_DCI1011COM
# model no. of remote control:
# devices being controlled by this remote:
#
begin remote
name THOMSON_DCI1011COM
flags RAW_CODES|CONST_LENGTH
eps 30
aeps 100
ptrail 0
repeat 0 0
gap 119285
begin raw_codes
name 1
388 714 327 1600 328 635
310 2727 308 1207 296 1219
300 1078 267 2629 267 12900
270 830 268 2631 267 695
268 695 267 697 264 833
268 694 269 693 265
name 2
381 718 348 1581 329 634
322 2713 326 1191 297 1219
299 1076 297 2600 297 12873
298 801 304 2454 297 666
293 671 299 663 293 947
290 671 298 662 263
name 3
381 716 352 1578 326 637
333 2702 331 1185 295 1219
299 1078 294 2604 297 12872
298 802 303 2320 299 661
295 668 301 662 292 1085
301 663 294 665 293
name 4
384 718 360 1568 326 637
329 2708 302 1213 301 1215
297 1079 304 2592 294 12877
304 794 294 2190 294 668
302 659 295 668 268 1248
264 698 285 677 263
name 5
377 723 351 1579 332 631
323 2712 298 1218 326 1190
300 1075 299 2599 301 12869
302 796 297 2048 297 665
296 667 298 665 293 1361
290 674 296 662 292
name 6
378 722 353 1577 330 630
324 2712 323 1195 323 1191
331 1046 322 2576 326 12843
324 776 298 1908 322 640
291 671 300 663 292 1500
301 661 296 664 295
name 7
385 711 379 1551 374 589
356 2682 358 1156 352 1164
354 1023 349 2547 351 12818
347 752 351 1716 327 639
317 643 349 615 319 1611
322 641 320 638 322
name 8
387 713 355 1575 326 636
333 2703 306 1210 295 1219
302 1075 295 2601 299 12871
299 802 301 1629 292 668
300 663 295 668 301 1769
264 697 296 666 282
name 9
381 718 361 1568 324 639
331 2706 327 1187 322 1193
299 1080 301 2595 292 12878
294 804 294 1499 303 660
294 669 296 665 296 1911
294 669 289 672 296
name 0
398 701 376 1555 353 607
346 2691 349 1165 347 1170
346 1030 329 2567 320 12851
325 775 344 2691 324 637
324 640 320 641 324 639
318 645 324 639 315
name INFO
432 664 379 1549 376 587
378 2657 376 1140 376 1141
373 1002 382 2513 376 12798
404 693 380 1550 374 589
378 583 384 856 380 1412
376 587 381 578 374
name POWER
385 714 363 1568 326 636
331 2707 328 1185 324 1193
298 1079 304 2592 293 12879
298 801 292 670 299 665
293 668 301 663 292 2742
294 670 299 662 292
end raw_codes
end remote
#################
lsmod
##################
~$ lsmod | grep lirc
lirc_serial 17704 0
lirc_dev 18376 1 lirc_serial
|
|
From: <li...@ba...> - 2009-12-08 22:34:09
|
Hi! hari jayaram "ha...@gm..." wrote: [...] > I then connected the irblaster. When I send a signal to the port. I get a > connection refused. > The messages and my lircd.conf are given below > > I am quite confused , as my dmesg says it detected a receiver even though > its the transmitter that is plugged in. > Also I am assuming my /etc/init.d/lirc starts everything and loads > lirc_serial > > I am running 64 bit ubuntu and lirc 0.8.3 > I am attaching various outputs below > > I dont know what I am doing , but I am hoping someone can point me in the > right direction > > hari [...] > The permissions on my node are > > ~$ ls -al /dev/lirc* > crw-rw-rw- 1 root root 61, 0 2009-12-08 07:03 /dev/lirc0 You should have a /dev/lircd here. Since 0.8.6 this is located in /var/run/lirc/lircd. Looks like lircd is not running. [...] > $ irsend -d /dev/lirc0 SEND_ONCE THOMSON_DCI1011COM 1 > irsend: could not connect to socket > irsend: Permission denied irsend needs to communicate with lircd using the /dev/lircd socket. lircd will access /dev/lirc0. Christoph |
|
From: hari j. <ha...@gm...> - 2009-12-09 00:03:41
|
Hi Chris and everone. My ubuntu init script was not starting lird . But I could manually start it as root. After that there was no /dev/lircd1 only /dev/lirc0 and /dev/lircd SO as of now things are still stuck with irsend saying thde device only can receive. Also some background which I did not go into: I was trying to get a new contoller for a DTA using a blaster, there was however no conf file for the appropriate remote available on the net after much googling. So I decided to make a frequency info conf file myself. I bought a receiver and recompiled lirc to work with the receiver and made the new conf file for the comcast THOMSON_DCI1011COm DTA After that I did not recompile lirc . I am assuming the same lirc_serial module now controlls the now re-plugged back in irblaster as well. So basically I dont know why /dev/lircd1 is not being created and why the init script is not starting lircd automatically. I am having to manually start it. And now irsend reports that the device only supports receiving. How do I flip it back to knowing that there is a sender connected. I know the blaster works because If I do a cat >dev/ttyS0 and type some-stuff the Blaster LED glows a nice constant bright red. So what steps should I know take? Also once I get this set up I will have the conf file for the newly released Comcast cable Thomson DCI1011COm which I will email you to add to the distribution. Thanks Hari On Tue, Dec 8, 2009 at 4:37 PM, Christoph Bartelmus <li...@ba...>wrote: > Hi! > > hari jayaram "ha...@gm..." wrote: > [...] > > I then connected the irblaster. When I send a signal to the port. I get a > > connection refused. > > The messages and my lircd.conf are given below > > > > I am quite confused , as my dmesg says it detected a receiver even though > > its the transmitter that is plugged in. > > Also I am assuming my /etc/init.d/lirc starts everything and loads > > lirc_serial > > > > I am running 64 bit ubuntu and lirc 0.8.3 > > I am attaching various outputs below > > > > I dont know what I am doing , but I am hoping someone can point me in the > > right direction > > > > hari > [...] > > The permissions on my node are > > > > ~$ ls -al /dev/lirc* > > crw-rw-rw- 1 root root 61, 0 2009-12-08 07:03 /dev/lirc0 > > You should have a /dev/lircd here. > Since 0.8.6 this is located in /var/run/lirc/lircd. > Looks like lircd is not running. > > [...] > > $ irsend -d /dev/lirc0 SEND_ONCE THOMSON_DCI1011COM 1 > > irsend: could not connect to socket > > irsend: Permission denied > > irsend needs to communicate with lircd using the /dev/lircd socket. > lircd will access /dev/lirc0. > > Christoph > > > ------------------------------------------------------------------------------ > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > |
|
From: hari j. <ha...@gm...> - 2009-12-09 03:26:10
|
Sorry I know this problem has been reported before . But I dont know what I need to do to get around it. I am getting a device not supporting sending error I did make sure that lird was running I now have a /dev/lircd , but irsend fails as shown below I know the transmitter works fine because I can cat /dev/ttyS0 and see the LED glow red What do I need to do to get irsend to work. Thanks for your help Hari ########### irsend ########### $ irsend SEND_ONCE REMOTE_NAME 1 irsend: command failed: SEND_ONCE REMOTE_NAME 1 irsend: hardware does not support sending ########## my devices ########### $ ls -ltr /dev/lir* srw-rw-rw- 1 root root 0 2009-12-08 10:12 /dev/lircd crw-r--r-- 1 root root 61, 0 2009-12-08 10:30 /dev/lirc crw-rw-rw- 1 root root 61, 0 2009-12-08 20:37 /dev/lirc0 ########## dmesg for lirc_serial ########## [ 546.813078] lirc_dev: IR Remote Control driver registered, major 61 [ 546.813899] lirc_serial: no version for "lirc_unregister_plugin" found: kernel tainted. [ 547.312184] lirc_serial: auto-detected active low receiver [ 547.312188] lirc_dev: lirc_register_plugin: sample_rate: 0 [ 7551.230534] lirc_dev: IR Remote Control driver registered, major 61 [ 7551.727639] lirc_serial: auto-detected active low receiver [ 7551.727643] lirc_dev: lirc_register_plugin: sample_rate: 0 [ 7586.689775] lirc_dev: IR Remote Control driver registered, major 61 [ 7587.187711] lirc_serial: auto-detected active low receiver [ 7587.187716] lirc_dev: lirc_register_plugin: sample_rate: 0 [ 9319.632423] lirc_dev: IR Remote Control driver registered, major 61 [45040.916522] lirc_serial: auto-detected active low receiver [45040.916527] lirc_dev: lirc_register_plugin: sample_rate: 0 [45088.125303] lirc_dev: IR Remote Control driver registered, major 61 [45088.623256] lirc_serial: auto-detected active low receiver [45088.623262] lirc_dev: lirc_register_plugin: sample_rate: 0 On Tue, Dec 8, 2009 at 7:03 PM, hari jayaram <ha...@gm...> wrote: > Hi Chris and everone. > My ubuntu init script was not starting lird . But I could manually start it > as root. > After that there was no /dev/lircd1 only /dev/lirc0 and /dev/lircd > > SO as of now things are still stuck with irsend saying thde device only can > receive. > > Also some background which I did not go into: > I was trying to get a new contoller for a DTA using a blaster, there was > however no conf file for the appropriate remote available on the net after > much googling. > So I decided to make a frequency info conf file myself. > I bought a receiver and recompiled lirc to work with the receiver and made > the new conf file for the comcast THOMSON_DCI1011COm DTA > > After that I did not recompile lirc . I am assuming the same lirc_serial > module now controlls the now re-plugged back in irblaster as well. > > So basically I dont know why /dev/lircd1 is not being created and why the > init script is not starting lircd automatically. I am having to manually > start it. > And now irsend reports that the device only supports receiving. > > How do I flip it back to knowing that there is a sender connected. > > I know the blaster works because If I do a cat >dev/ttyS0 and type > some-stuff the Blaster LED glows a nice constant bright red. > > So what steps should I know take? > Also once I get this set up I will have the conf file for the newly > released Comcast cable Thomson DCI1011COm which I will email you to add to > the distribution. > > Thanks > Hari > > > On Tue, Dec 8, 2009 at 4:37 PM, Christoph Bartelmus <li...@ba...>wrote: > >> Hi! >> >> hari jayaram "ha...@gm..." wrote: >> [...] >> > I then connected the irblaster. When I send a signal to the port. I get >> a >> > connection refused. >> > The messages and my lircd.conf are given below >> > >> > I am quite confused , as my dmesg says it detected a receiver even >> though >> > its the transmitter that is plugged in. >> > Also I am assuming my /etc/init.d/lirc starts everything and loads >> > lirc_serial >> > >> > I am running 64 bit ubuntu and lirc 0.8.3 >> > I am attaching various outputs below >> > >> > I dont know what I am doing , but I am hoping someone can point me in >> the >> > right direction >> > >> > hari >> [...] >> > The permissions on my node are >> > >> > ~$ ls -al /dev/lirc* >> > crw-rw-rw- 1 root root 61, 0 2009-12-08 07:03 /dev/lirc0 >> >> You should have a /dev/lircd here. >> Since 0.8.6 this is located in /var/run/lirc/lircd. >> Looks like lircd is not running. >> >> [...] >> > $ irsend -d /dev/lirc0 SEND_ONCE THOMSON_DCI1011COM 1 >> > irsend: could not connect to socket >> > irsend: Permission denied >> >> irsend needs to communicate with lircd using the /dev/lircd socket. >> lircd will access /dev/lirc0. >> >> Christoph >> >> >> ------------------------------------------------------------------------------ >> Return on Information: >> Google Enterprise Search pays you back >> Get the facts. >> http://p.sf.net/sfu/google-dev2dev >> > > |
|
From: Nick M. <kno...@gm...> - 2009-12-09 09:03:56
|
2009/12/9 hari jayaram <ha...@gm...>:
> Sorry I know this problem has been reported before . But I dont know what I
> need to do to get around it.
> I am getting a device not supporting sending error
>
> I did make sure that lird was running
> I now have a /dev/lircd , but irsend fails as shown below
> I know the transmitter works fine because I can cat /dev/ttyS0 and see the
> LED glow red
>
> What do I need to do to get irsend to work.
Try the following entries in your modprobe configuration. You will
need to adjust the irq and io entries to match your system:
alias char-major-61 lirc_serial
options lirc_serial irq=4 io=0x3f8 type=0 softcarrier=1 txsense=0
install lirc_serial \
setserial /dev/ttyS0 uart none; /sbin/modprobe --ignore-install lirc_serial
The second line is split over 2 lines for the sake of posting this
message, but you should place it all on one line in your modprobe
entry.
This has been known to correct the "hardware does not support sending"
problem for some MythTV users.
Cheers,
Nick
--
Nick Morrott
MythTV Official wiki: http://mythtv.org/wiki/
MythTV users list archive: http://www.gossamer-threads.com/lists/mythtv/users
"An investment in knowledge always pays the best interest." - Benjamin Franklin
|
|
From: <li...@ba...> - 2009-12-09 17:01:18
|
Hi! hari jayaram "ha...@gm..." wrote: > Sorry I know this problem has been reported before . But I dont know what I > need to do to get around it. > I am getting a device not supporting sending error > > I did make sure that lird was running > I now have a /dev/lircd , but irsend fails as shown below > I know the transmitter works fine because I can cat /dev/ttyS0 and see the > LED glow red > > What do I need to do to get irsend to work. When you compile lirc you need to make sure that lirc_serial is compiled with transmitter support. Make sure that configure is called with the --with-transmitter switch. When you use setup.sh, make sure the "With transmitter diode" checkbox in the "Driver specific Options" is set. Christoph |
|
From: hari j. <ha...@gm...> - 2009-12-09 17:15:06
|
Thanks Christoph , Nick and eveyone else for your help. I can finally irsend with the DCI1011COM remote conf file I updated to a ubuntu ppa build from Jeremy Yoder , that put the version at 0.8.6 Also this time the package manager actually did ask me if I had a transmitter installed . And now irsend works . But I have another problem. Any channel change event works 1 our of 5 times. I tried to put the LED right next to the receiver and at a few different locations . At all of these the event gets registered one out of a few times and the right thing happens Accordingly I can see the events picked up and stopped. But the DTA box does not respond everytime Any ieas on how to make sure the blaster works everytime? the syslog has : Dec 9 12:02:21 hj-ubuntu41 lircd-0.8.6[6921]: accepted new client on /var/run/lirc/lircd Dec 9 12:02:21 hj-ubuntu41 lircd-0.8.6[6921]: removed client Thanks again for your help Hari On Wed, Dec 9, 2009 at 12:00 PM, Christoph Bartelmus <li...@ba...>wrote: > Hi! > > hari jayaram "ha...@gm..." wrote: > > > Sorry I know this problem has been reported before . But I dont know what > I > > need to do to get around it. > > I am getting a device not supporting sending error > > > > I did make sure that lird was running > > I now have a /dev/lircd , but irsend fails as shown below > > I know the transmitter works fine because I can cat /dev/ttyS0 and see > the > > LED glow red > > > > What do I need to do to get irsend to work. > > When you compile lirc you need to make sure that lirc_serial is compiled > with transmitter support. > Make sure that configure is called with the --with-transmitter switch. > When you use setup.sh, make sure the "With transmitter diode" checkbox in > the "Driver specific Options" is set. > > Christoph > > > ------------------------------------------------------------------------------ > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > |
|
From: <li...@ba...> - 2009-12-09 17:47:37
Attachments:
XMP
|
Hi! try the attached config file instead yours. Christoph hari jayaram "ha...@gm..." wrote: > Thanks Christoph , Nick and eveyone else for your help. > I can finally irsend with the DCI1011COM remote conf file > > I updated to a ubuntu ppa build from Jeremy Yoder , that put the version at > 0.8.6 > Also this time the package manager actually did ask me if I had a > transmitter installed . > > And now irsend works . But I have another problem. > > Any channel change event works 1 our of 5 times. I tried to put the LED > right next to the receiver and at a few different locations . > At all of these the event gets registered one out of a few times and the > right thing happens > > Accordingly I can see the events picked up and stopped. But the DTA box does > not respond everytime > Any ieas on how to make sure the blaster works everytime? > > the syslog has : > Dec 9 12:02:21 hj-ubuntu41 lircd-0.8.6[6921]: accepted new client on > /var/run/lirc/lircd > Dec 9 12:02:21 hj-ubuntu41 lircd-0.8.6[6921]: removed client > > Thanks again for your help > Hari > > On Wed, Dec 9, 2009 at 12:00 PM, Christoph Bartelmus > <li...@ba...>wrote: >> Hi! >> >> hari jayaram "ha...@gm..." wrote: >> >>> Sorry I know this problem has been reported before . But I dont know what >> I >>> need to do to get around it. >>> I am getting a device not supporting sending error >>> >>> I did make sure that lird was running >>> I now have a /dev/lircd , but irsend fails as shown below >>> I know the transmitter works fine because I can cat /dev/ttyS0 and see >> the >>> LED glow red >>> >>> What do I need to do to get irsend to work. >> >> When you compile lirc you need to make sure that lirc_serial is compiled >> with transmitter support. >> Make sure that configure is called with the --with-transmitter switch. >> When you use setup.sh, make sure the "With transmitter diode" checkbox in >> the "Driver specific Options" is set. >> >> Christoph >> >> >> --------------------------------------------------------------------------- >> --- Return on Information: >> Google Enterprise Search pays you back >> Get the facts. >> http://p.sf.net/sfu/google-dev2dev >> |
|
From: hari j. <ha...@gm...> - 2009-12-09 18:37:48
|
Hi Christoph, That file i,.e XMP.txt worked perfectly. Just curious whats different between that and the file I had which I recorded using irrecord?. Also you could also name that file for the Thomson DCI1011COM DTA which comcast cable in the U.S recently started using to replace the PACE DC050 DTAs it was using as part of its digital cable transition. Thanks for all your help...Now to come up with a channel change script to have myth control the DTA box. ALso On an unrelated note I am planning to compile lirc from scratch so that can track trunk , I may be emailing the newsgroup as I stuggle with that. Thanks Hari On Wed, Dec 9, 2009 at 12:46 PM, Christoph Bartelmus <li...@ba...>wrote: > Hi! > > try the attached config file instead yours. > > Christoph > > hari jayaram "ha...@gm..." wrote: > > > Thanks Christoph , Nick and eveyone else for your help. > > I can finally irsend with the DCI1011COM remote conf file > > > > I updated to a ubuntu ppa build from Jeremy Yoder , that put the version > at > > 0.8.6 > > Also this time the package manager actually did ask me if I had a > > transmitter installed . > > > > And now irsend works . But I have another problem. > > > > Any channel change event works 1 our of 5 times. I tried to put the LED > > right next to the receiver and at a few different locations . > > At all of these the event gets registered one out of a few times and the > > right thing happens > > > > Accordingly I can see the events picked up and stopped. But the DTA box > does > > not respond everytime > > Any ieas on how to make sure the blaster works everytime? > > > > the syslog has : > > Dec 9 12:02:21 hj-ubuntu41 lircd-0.8.6[6921]: accepted new client on > > /var/run/lirc/lircd > > Dec 9 12:02:21 hj-ubuntu41 lircd-0.8.6[6921]: removed client > > > > Thanks again for your help > > Hari > > > > On Wed, Dec 9, 2009 at 12:00 PM, Christoph Bartelmus > > <li...@ba...>wrote: > > >> Hi! > >> > >> hari jayaram "ha...@gm..." wrote: > >> > >>> Sorry I know this problem has been reported before . But I dont know > what > >> I > >>> need to do to get around it. > >>> I am getting a device not supporting sending error > >>> > >>> I did make sure that lird was running > >>> I now have a /dev/lircd , but irsend fails as shown below > >>> I know the transmitter works fine because I can cat /dev/ttyS0 and see > >> the > >>> LED glow red > >>> > >>> What do I need to do to get irsend to work. > >> > >> When you compile lirc you need to make sure that lirc_serial is compiled > >> with transmitter support. > >> Make sure that configure is called with the --with-transmitter switch. > >> When you use setup.sh, make sure the "With transmitter diode" checkbox > in > >> the "Driver specific Options" is set. > >> > >> Christoph > >> > >> > >> > --------------------------------------------------------------------------- > >> --- Return on Information: > >> Google Enterprise Search pays you back > >> Get the facts. > >> http://p.sf.net/sfu/google-dev2dev > >> > > > begin remote > > name XMP > bits 32 > flags XMP > eps 20 > aeps 300 > > one 0 137 > zero 250 710 > ptrail 250 > pre_data_bits 32 > pre_data 0x170F443E > pre 250 12921 > gap 81698 > toggle_bit_mask 0x0 > > begin codes > 1 0x1e000100 > 2 0x1d000200 > 3 0x1c000300 > 4 0x1b000400 > 5 0x1a000500 > 6 0x19000600 > 7 0x18000700 > 8 0x17000800 > 9 0x16000900 > 0 0x17000000 > INFO 0x17002600 > POWER 0x10000f00 > end codes > > end remote > > > > > ------------------------------------------------------------------------------ > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X