Author Topic: MS MCE Blaster transmit on an MD problems  (Read 3357 times)

jondecker76

  • Alumni
  • wants to work for LinuxMCE
  • *
  • Posts: 763
    • View Profile
Re: MS MCE Blaster transmit on an MD problems
« Reply #15 on: August 20, 2008, 03:14:57 pm »
Another thing to mention is that USBUIRT has its own code base, so bugs could bedifferent between a USBUIRT and some other IR transceiver. Though, of course, they also have some shared code. Do you have a USBUIRT available to compare to?

rodercot

  • Guest
Re: MS MCE Blaster transmit on an MD problems
« Reply #16 on: August 20, 2008, 03:21:34 pm »
 Jon,
 
Yes I have a USBUirt on the hybrid which workd just fine for changing channels etc.. The only issue I have there is the MCE remote on the USBUirt will not control my volume on the Denon AVR-988 (rs232) rcvr. But the gyration remote controls it fine from Ambience controls. As in my other post this causes a problem only when I am watching something from another source IE VCR, DVD player etc where LMCE has to switch an input on the TV. Thus when I hit the ambience buttons to control volume it needs to switch back to the LMCE video input to control the volume and then when I am done adjusting the voleum it switches back to what I was watching, this takes about 1 minute to complete give or take, it would be nice to just have the MCE work properly.

 Colin - I am not sure I have applied the transmit fix on the core for the USBUirt device and it works. I did not know or realize that it needed to be done on a MCEusb_2 device as well per Media Director. Is this in fact the case.

 Dave

rodercot

  • Guest
Re: MS MCE Blaster transmit on an MD problems
« Reply #17 on: August 20, 2008, 03:39:09 pm »
Here is some data logging from the core.hybrid with the USBUirt attached. Note all those mute commands were actually a couple of Volume Up or Down commands from the MCE remote in that room. The Avr and Aquos are GSD devices.

 
Code: [Select]
Received Message from 28 (USB UIRT 0038 / Living Room/Family Room) to 10 (Media Plug-in / Living Room/Family Room), type 1 id 97 Command:Mute, retry none, parameters: <0x83ac8b90>
08 08/20/08 9:25:57.618 Received Message from 28 (USB UIRT 0038 / Living Room/Family Room) to 19 (The core/hybrid / Living Room/Family Room), type 1 id 97 Command:Mute, retry none, parameters: <0xa84fcb90>
08 08/20/08 9:25:57.618   Parameter 41(StreamID): 1002 <0xa84fcb90>
08 08/20/08 9:25:57.618 Forwarding 97 Command:Mute up pipe to 161 (AVR-988 (RS-232)) <0xb6c00b90>
05 08/20/08 9:25:57.618 The target device 19 (routed to 19) has not registered. <0xb6c00b90>
08 08/20/08 9:26:12.919 Received Message from 28 (USB UIRT 0038 / Living Room/Family Room) to 10 (Media Plug-in / Living Room/Family Room), type 1 id 97 Command:Mute, retry none, parameters: <0x83ac8b90>
08 08/20/08 9:26:12.920 Received Message from 28 (USB UIRT 0038 / Living Room/Family Room) to 19 (The core/hybrid / Living Room/Family Room), type 1 id 97 Command:Mute, retry none, parameters: <0xa84fcb90>
08 08/20/08 9:26:12.920   Parameter 41(StreamID): 1002 <0xa84fcb90>
08 08/20/08 9:26:12.920 Forwarding 97 Command:Mute up pipe to 161 (AVR-988 (RS-232)) <0xb6c00b90>
05 08/20/08 9:26:12.920 The target device 19 (routed to 19) has not registered. <0xb6c00b90>
08 08/20/08 9:26:13.883 Received Message from 28 (USB UIRT 0038 / Living Room/Family Room) to 10 (Media Plug-in / Living Room/Family Room), type 1 id 97 Command:Mute, retry none, parameters: <0x83ac8b90>
08 08/20/08 9:26:13.884 Received Message from 28 (USB UIRT 0038 / Living Room/Family Room) to 19 (The core/hybrid / Living Room/Family Room), type 1 id 97 Command:Mute, retry none, parameters: <0xa84fcb90>
08 08/20/08 9:26:13.884   Parameter 41(StreamID): 1002 <0xa84fcb90>
08 08/20/08 9:26:13.884 Forwarding 97 Command:Mute up pipe to 161 (AVR-988 (RS-232)) <0xb6c00b90>
05 08/20/08 9:26:13.884 The target device 19 (routed to 19) has not registered. <0xb6c00b90>
08 08/20/08 9:26:19.255 Received Message from 28 (USB UIRT 0038 / Living Room/Family Room) to 20 (OnScreen Orbiter / Living Room/Family Room), type 1 id 194 Command:Toggle Power, retry none, parameters: <0x83ac8b90>
08 08/20/08 9:26:19.256 Received Message from 20 (OnScreen Orbiter / Living Room/Family Room) to 10 (Media Plug-in / Living Room/Family Room), type 1 id 44 Command:MH Stop Media, retry none, parameters: <0x6a0f0b90>
08 08/20/08 9:26:19.256   Parameter 2(PK_Device): 0 <0x6a0f0b90>
08 08/20/08 9:26:19.256   Parameter 29(PK_MediaType): 0 <0x6a0f0b90>
08 08/20/08 9:26:19.256   Parameter 44(PK_DeviceTemplate): 0 <0x6a0f0b90>
08 08/20/08 9:26:19.256   Parameter 45(PK_EntertainArea): 1 <0x6a0f0b90>
08 08/20/08 9:26:19.256   Parameter 254(Bypass Event): 0 <0x6a0f0b90>

 Dave

rodercot

  • Guest
Re: MS MCE Blaster transmit on an MD problems
« Reply #18 on: August 20, 2008, 04:01:56 pm »
Jon,

 I have dwnlded the required files as per your threads. I am using my windows machine. I placed them in a folder php in the LMCE home directory. Can you give me the command to copy this to the right directories on the core from a command line please. I think my brain is in overload right now and cannot remember it at all. so cd/home/php/. Is this what I should be doing.

 cp /home/php/addModel.lang.php /var/www/pluto-admin/languages/en/addModel.lang.php

 Once copied do we need to set permissions on these files at all and finally is it still a force reload on the hybrid to activate the changes.

 Thanks

 Dave
« Last Edit: August 20, 2008, 04:22:53 pm by rodercot »

rodercot

  • Guest
Re: MS MCE Blaster transmit on an MD problems
« Reply #19 on: August 21, 2008, 01:30:50 pm »
Seth,

 Did you have any luck on your testing? I tried the FTDI fix on the MD for the heck of it and no difference. I know it is for the usbuirt but what the hey!!! It is easy to rebuild the MD.  I also just applied the fixes regarding delays etc from the link Jon supplied and no difference at all. I thought this may help the volume problem in the living room on the core but no luck either. It is so frustrating to watch the device send a code from the UI - advanced - Ir codes, but yet the device will not function under normal use. I see the differences of course in the code but still it is Frustrating.

 Does lirc in LMCE not use the LIRC conventions. IE hardware.conf etc... I also notice there is a new mceusb2 updated driver for the newer Vista remote.

 Here is a look at my hardware config from the md in question.

 
Code: [Select]
root@moon63:/etc/lirc# cat hardware.conf
# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="None "

# Arguments which will be used when launching lircd
LIRCD_ARGS=""

#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD=false

#Try to load appropriate kernel modules
LOAD_MODULES=true

# Run "lircd --driver=help" for a list of supported drivers.
DRIVER=""
# If DEVICE is set to /dev/lirc and devfs is in use /dev/lirc/0 will be
# automatically used instead
DEVICE=""
MODULES=""

# Default configuration files for your hardware if any
LIRCD_CONF=""
LIRCMD_CONF=""
root@moon63:/etc/lirc#


 Dave

 
« Last Edit: August 21, 2008, 03:56:49 pm by rodercot »

rodercot

  • Guest
Re: MS MCE Blaster transmit on an MD problems
« Reply #20 on: August 22, 2008, 01:29:50 pm »
 Am I the only having issues on an MD with this... I have reviewed the Lirc Site and barring updating the lirc files .8.3 or updating the driver I am lost. In everything I see on lirc they say a proper lircd.conf is important and I look at my three lircd files one from the core and two from the Md's and they all look like the one I have posted. It looks like we have lirc_mceusb2 ver 1.29 installed and the current is 1.47.

 I found a couple more things to check on the system which would make me believe all is setup right hardware wise. So I am assuming it is routing issue of the commands through DCE and or a config file elsewhere, anyhow I am lost at this point, but with owning three of these and a UsbUirt I really am not that prepared to spend another 80$ to get another USBUirt for this system. The MceUsb2 is supposed to work in 710Rc2.

 
Code: [Select]
Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.
root@moon63:~# ls -l /dev/lirc*
crw-rw---- 1 root root 61, 0 Aug 21 11:37 /dev/lirc0
srw-rw-rw- 1 root root     0 Aug 21 12:00 /dev/lircd


Code: [Select]
root@moon63:~# lsmod
Module                  Size  Used by
ide_cd                 32672  0
ide_generic             2176  0 [permanent]
rfcomm                 42136  2
l2cap                  26240  11 rfcomm
nfsd                  220912  13
exportfs                7040  1 nfsd
ppdev                  10244  0
parport_pc             37412  0
lp                     12580  0
parport                37448  3 ppdev,parport_pc,lp
autofs4                23044  1
cpufreq_stats           7232  0
cpufreq_powersave       2688  0
cpufreq_conservative     8072  0
cpufreq_userspace       5280  0
cpufreq_ondemand        9612  0
freq_table              5792  2 cpufreq_stats,cpufreq_ondemand
ac                      6148  0
dock                   10656  0
sbs                    19592  0
button                  8976  0
video                  18060  0
container               5504  0
battery                11012  0
ipv6                  273892  16
nls_cp437               6784  1
cifs                  237428  1
snd_hda_intel         375448  3
snd_pcm_oss            51488  0
snd_mixer_oss          18432  1 snd_pcm_oss
snd_pcm                86148  2 snd_hda_intel,snd_pcm_oss
snd_page_alloc         12168  2 snd_hda_intel,snd_pcm
snd_hwdep              10884  1 snd_hda_intel
snd_seq_dummy           4868  0
snd_seq_oss            35712  0
snd_seq_midi           10656  0
snd_rawmidi            27296  1 snd_seq_midi
snd_seq_midi_event      8576  2 snd_seq_oss,snd_seq_midi
snd_seq                58448  6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer              25988  2 snd_pcm,snd_seq
snd_seq_device          9612  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
lirc_mceusb2           14980  1
lirc_dev               16116  1 lirc_mceusb2
snd                    67012  19 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_hwdep,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq_midi_event,snd_seq,snd_timer,snd_seq_device
hci_usb                18332  3
bluetooth              57060  9 rfcomm,l2cap,hci_usb
serio_raw               8068  0
psmouse                39952  0
i2c_nforce2             7040  0
k8temp                  6656  0
pcspkr                  4224  0
shpchp                 34580  0
soundcore               8800  1 snd
nvidia               7825536  46
agpgart                35016  1 nvidia
pci_hotplug            32704  1 shpchp
i2c_core               26112  2 i2c_nforce2,nvidia
evdev                  11136  2
af_packet              24840  0
nfs                   245868  1
lockd                  67592  3 nfsd,nfs
sunrpc                172412  10 nfsd,nfs,lockd
sg                     36764  0
sr_mod                 17828  0
cdrom                  37536  2 ide_cd,sr_mod
ata_generic             8452  0
amd74xx                15260  0 [permanent]
ide_core              116804  3 ide_cd,ide_generic,amd74xx
forcedeth              51592  0
ehci_hcd               36492  0
sata_nv                20612  0
libata                125168  2 ata_generic,sata_nv
scsi_mod              147084  3 sg,sr_mod,libata
ohci_hcd               22916  0
usbcore               138632  5 lirc_mceusb2,hci_usb,ehci_hcd,ohci_hcd
raid10                 26496  0
raid456               128016  0
xor                    16904  1 raid456
raid1                  25984  0
raid0                   9728  0
multipath               9984  0
linear                  7552  0
md_mod                 82324  7 raid10,raid456,raid1,raid0,multipath,linear
thermal                14344  0
processor              32072  1 thermal
fan                     5764  0
capability              5896  0
commoncap               8320  1 capability
fuse                   47124  3
root@moon63:~#

 Here is some dmesg code from the md as well.


Code: [Select]
   21.116000] usbcore: registered new interface driver hci_usb
[   21.292000] lirc_dev: IR Remote Control driver registered, at major 61
[   21.328000] lirc_mceusb2: no version for "lirc_get_pdata" found: kernel tainted.
[   21.328000]
[   21.328000] lirc_mceusb2: Philips eHome USB IR Transciever and Microsoft MCE 2005 Remote Control driver for LIRC $Revision: 1.33 $
[   21.328000] lirc_mceusb2: Daniel Melander <lirc@rajidae.se>, Martin Blatter <martin_a_blatter@yahoo.com>
[   21.532000] usb 1-2: reset full speed USB device using ohci_hcd and address 4
[   21.736000] lirc_dev: lirc_register_plugin: sample_rate: 0
[   21.744000] lirc_mceusb2[4]: Philips eHome Infrared Transceiver on usb1:4
[   21.744000] usbcore: registered new interface driver lirc_mceusb2

 Dave
« Last Edit: August 22, 2008, 06:14:45 pm by rodercot »

rodercot

  • Guest
Re: MS MCE Blaster transmit on an MD problems
« Reply #21 on: August 23, 2008, 01:33:28 pm »
Here is a copy of the Lirc_DCE log from the MD. I have tried everything I can think of to fix this. I even tried re-compiling Lirc on the MD with the latest mce_usb2 driver. I rebuilt the MD completely from scratch. Deleting the original image and starting a new.

 Something I noted not sure if it matters but if you look at the Device Template for the USBUirt - It is controlled via USbUirt 0038 Infrared Devices and then if you look at the Lirc Embedded Transport device template is controlled via Category Lirc Drivers.

 In webadmin - wizard - devices - A/V devices I notice a 0 or 35 in the FK capture card port for most devices - what setting is this.

 
Code: [Select]
== ATTEMPT FRESH START ==
1       08/22/08 16:13:40       /usr/pluto/bin/Spawn_Device.sh 206 (spawning-device)    ^[[1;00m23849 Dev: 206; Already Running list: 196,197,198,199,201,202,200,203,204,^[[1;00m
== FRESH START ==
1       08/22/08 16:13:40       /usr/pluto/bin/Spawn_Device.sh 206 (spawning-device)    ^[[1;00mdevice: 206 ip: dcerouter cmd_line: LIRC_DCE^[[1;00m
0       08/22/08 16:13:40       206 (spawning-device)   ^[[1;00mEntering 206^[[1;00m
========== NEW LOG SECTION ==========
1       08/22/08 16:13:40       206 (spawning-device)   ^[[1;00mStarting... 1^[[1;00m
1       08/22/08 16:13:40       206 (spawning-device)   ^[[1;00mFound /usr/pluto/bin/LIRC_DCE^[[1;00m
05      08/22/08 16:13:40.330           ^[[33;1mConnection for client socket reported NEED RELOAD IP=192.168.80.2 MAC=00:18:F3:E2:5A:A2, device 206 last error 2^[[0m <0x2aadd219b910>
05      08/22/08 16:13:40.331           ^[[33;1mThe router must be reloaded before this device is fully functional^[[0m <0x2aadd219b910>
05      08/22/08 16:13:40.332           ^[[33;1mvoid ClientSocket::Disconnect() on this socket: 0x63eed0 (m_Socket: 5)^[[0m <0x2aadd219b910>
05      08/22/08 16:13:40.339           ^[[33;1mConnection for client socket reported NEED RELOAD IP=192.168.80.2 MAC=00:18:F3:E2:5A:A2, device 206 last error 2^[[0m <0x2aadd219b910>
01      08/22/08 16:13:40.449           ^[[31;1mThere are no remote controls -- LIRC will be dormant^[[0m <0x2aadd219b910>
05      08/22/08 16:15:50.793           ^[[33;1mGot a reload command from 0 ^[[0m <0x41001950>
05      08/22/08 16:15:51.062           ^[[33;1mvoid ClientSocket::Disconnect() on this socket: 0x638720 (m_Socket: 6)^[[0m <0x2aadd219b910>
Return code: 2
2       08/22/08 16:15:51       206 (spawning-device)   ^[[1;33mDevice requests restart... count=1/50 dev=206^[[1;00m
Fri Aug 22 16:15:51 EDT 2008 Restart
========== NEW LOG SECTION ==========
1       08/22/08 16:15:59       206 (spawning-device)   ^[[1;00mStarting... 1^[[1;00m
1       08/22/08 16:15:59       206 (spawning-device)   ^[[1;00mFound /usr/pluto/bin/LIRC_DCE^[[1;00m
05      08/22/08 16:16:01.091           ^[[33;1mCreating Leeching Thread for 1 remotes^[[0m <0x2afa4231e910>
05      08/22/08 16:16:01.092           ^[[33;1mCreating child 207^[[0m <0x2afa4231e910>
05      08/22/08 16:16:01.092           ^[[33;1mNote: Device manager has attached a device of type 1911 that this has no custom event handler for.  It will not fire events.^[[0m <0x2afa4231e910>
05      08/22/08 16:16:01.092           ^[[33;1mNote: Device manager has attached a device of type 1911 that this has no custom handler for.  This is normal for IR.^[[0m <0x2afa4231e910>
05      08/22/08 16:16:01.092           ^[[33;1mCreating child 211^[[0m <0x2afa4231e910>
05      08/22/08 16:16:01.092           ^[[33;1mNote: Device manager has attached a device of type 1940 that this has no custom event handler for.  It will not fire events.^[[0m <0x2afa4231e910>
05      08/22/08 16:16:01.092           ^[[33;1mNote: Device manager has attached a device of type 1940 that this has no custom handler for.  This is normal for IR.^[[0m <0x2afa4231e910>
05      08/22/08 16:16:01.092           ^[[33;1mCreating child 212^[[0m <0x2afa4231e910>
05      08/22/08 16:16:01.092           ^[[33;1mNote: Device manager has attached a device of type 1942 that this has no custom event handler for.  It will not fire events.^[[0m <0x2afa4231e910>
05      08/22/08 16:16:01.092           ^[[33;1mNote: Device manager has attached a device of type 1942 that this has no custom handler for.  This is normal for IR.^[[0m <0x2afa4231e910>
05      08/22/08 16:32:55.745           ^[[33;1mGot a reload command from 0 ^[[0m <0x41802950>
05      08/22/08 16:32:56.005           ^[[33;1mvoid ClientSocket::Disconnect() on this socket: 0x638720 (m_Socket: 6)^[[0m <0x2afa4231e910>
Return code: 2
2       08/22/08 16:32:56       206 (spawning-device)   ^[[1;33mDevice requests restart... count=1/50 dev=206^[[1;00m
Fri Aug 22 16:32:56 EDT 2008 Restart
========== NEW LOG SECTION ==========
1       08/22/08 16:33:04       206 (spawning-device)   ^[[1;00mStarting... 1^[[1;00m
1       08/22/08 16:33:05       206 (spawning-device)   ^[[1;00mFound /usr/pluto/bin/LIRC_DCE^[[1;00m
05      08/22/08 16:33:05.572           ^[[33;1mCreating Leeching Thread for 1 remotes^[[0m <0x2b75e72f7910>
05      08/22/08 16:33:05.573           ^[[33;1mCreating child 207^[[0m <0x2b75e72f7910>
05      08/22/08 16:33:05.573           ^[[33;1mNote: Device manager has attached a device of type 1911 that this has no custom event handler for.  It will not fire events.^[[0m <0x2b75e72f7910>
05      08/22/08 16:33:05.573           ^[[33;1mNote: Device manager has attached a device of type 1911 that this has no custom handler for.  This is normal for IR.^[[0m <0x2b75e72f7910>
05      08/22/08 16:33:05.573           ^[[33;1mCreating child 211^[[0m <0x2b75e72f7910>
05      08/22/08 16:33:05.573           ^[[33;1mNote: Device manager has attached a device of type 1940 that this has no custom event handler for.  It will not fire events.^[[0m <0x2b75e72f7910>
05      08/22/08 16:33:05.574           ^[[33;1mNote: Device manager has attached a device of type 1940 that this has no custom handler for.  This is normal for IR.^[[0m <0x2b75e72f7910>
05      08/22/08 16:33:05.574           ^[[33;1mCreating child 212^[[0m <0x2b75e72f7910>
05      08/22/08 16:33:05.574           ^[[33;1mNote: Device manager has attached a device of type 1942 that this has no custom event handler for.  It will not fire events.^[[0m <0x2b75e72f7910>
05      08/22/08 16:33:05.574           ^[[33;1mNote: Device manager has attached a device of type 1942 that this has no custom handler for.  This is normal for IR.^[[0m <0x2b75e72f7910>
05      08/22/08 16:52:05.377           ^[[33;1mLost connection with lircd^[[0m <0x40800950>
Return code: 255
3       08/22/08 16:52:05       206 (spawning-device)   ^[[1;31mDevice died... count=1/50 dev=206^[[1;00m
Fri Aug 22 16:52:05 EDT 2008 died
== ATTEMPT FRESH START ==
1       08/22/08 16:57:29       /usr/pluto/bin/Spawn_Device.sh 206 (spawning-device)    ^[[1;00m13045 Dev: 206; Already Running list: 196,197,198,199,202,204,200,^[[1;00m
== FRESH START ==
1       08/22/08 16:57:29       /usr/pluto/bin/Spawn_Device.sh 206 (spawning-device)    ^[[1;00mdevice: 206 ip: dcerouter cmd_line: LIRC_DCE^[[1;00m
0       08/22/08 16:57:29       206 (spawning-device)   ^[[1;00mEntering 206^[[1;00m
========== NEW LOG SECTION ==========
1       08/22/08 16:57:29       206 (spawning-device)   ^[[1;00mStarting... 1^[[1;00m
1       08/22/08 16:57:29       206 (spawning-device)   ^[[1;00mFound /usr/pluto/bin/LIRC_DCE^[[1;00m
05      08/22/08 16:57:30.173           ^[[33;1mCreating Leeching Thread for 1 remotes^[[0m <0x2aff8c94e910>
05      08/22/08 16:57:30.175           ^[[33;1mCreating child 207^[[0m <0x2aff8c94e910>
05      08/22/08 16:57:30.175           ^[[33;1mNote: Device manager has attached a device of type 1911 that this has no custom event handler for.  It will not fire events.^[[0m <0x2aff8c94e910>
05      08/22/08 16:57:30.175           ^[[33;1mNote: Device manager has attached a device of type 1911 that this has no custom handler for.  This is normal for IR.^[[0m <0x2aff8c94e910>
05      08/22/08 16:57:30.175           ^[[33;1mCreating child 211^[[0m <0x2aff8c94e910>
05      08/22/08 16:57:30.175           ^[[33;1mNote: Device manager has attached a device of type 1940 that this has no custom event handler for.  It will not fire events.^[[0m <0x2aff8c94e910>
05      08/22/08 16:57:30.175           ^[[33;1mNote: Device manager has attached a device of type 1940 that this has no custom handler for.  This is normal for IR.^[[0m <0x2aff8c94e910>
05      08/22/08 16:57:30.175           ^[[33;1mCreating child 212^[[0m <0x2aff8c94e910>
05      08/22/08 16:57:30.175           ^[[33;1mNote: Device manager has attached a device of type 1942 that this has no custom event handler for.  It will not fire events.^[[0m <0x2aff8c94e910>


 206 = Mceusb
 207 = Lirc Embedded Transport - Device
 1911 = Lirc Embedded Transport - Device Template
 211 = KC3235 TV on MD
 1940 = KC3225 Device Template
 212 = TV/Live Tv for kc3225
 1942 = Device Template for Live/TV kc3225

 rgds,

 Dave

rodercot

  • Guest
Re: MS MCE Blaster transmit on an MD problems
« Reply #22 on: August 23, 2008, 08:07:05 pm »
Could someone please pull up Device Template 1911 (Lirc Embedded Transmit) anc compare with mine.

 Can you tell me how the device is controlled (via device or via category)

 If you click on edit after controlled via Lirc Drivers - Is route to parent and create child devices automatically - are they check or unchecked.
 
 What is listed as your comm method.  ARe any of your device commands that are added currently have the box checked.

 I ordered another USBuirt yesterday @$@%@%@$R% another 60+$ by the time it gets in my hands. I cannot believe that no-one else is using one of these to transmit and not having problems with it. Thanks colin, seth an Jon AS USUAL.  This is just BS. IS the Device supported Or NOT. I have three of this now collecting dust in a corner - BALLS. It works in every version of linux with all 1.30 mce_USB2 driver and newer, why not with LMCE.

 Thanks,

 Dave

slampt

  • Veteran
  • ***
  • Posts: 102
    • View Profile
Re: MS MCE Blaster transmit on an MD problems
« Reply #23 on: August 24, 2008, 11:56:24 am »
Hey Dave,

I was also having this problem and there is a post of mine floating around.  I then got myself a USBUIRT and had the same problem as you described originally.
So basically with the MCE and the USBUIRT i get this problem, however both my test boxes needed to be used rather urgently for something else so I have had time to look into this.  Once work decides to pay me I will be going down and buying some more kit so I can start playing again. :P

Cheers.


rodercot

  • Guest
Re: MS MCE Blaster transmit on an MD problems
« Reply #24 on: August 26, 2008, 01:43:15 pm »
Well Upon deleting that MD completely and rebuilding it, I cannot even get Lirc embedded transmit to send a command to the device from Webadmin and have it work. It would really help if someone would compare their Lirc Device Template with mine, As I did try changing a couple things in there but had wrote all the settings down before I changed em.

  ??? ??? ???

 Dave