USB IR receives OK but does not transmit

[terry]

I recently received the Hybrid USB IR with an LED and a PLUG.

I installed it following the instructions on the support page and it works well with MythTV and LIRC on [Mandriva2008].

The only problem i have is that the plug-in IR transmitter is not changing the channel on my Hughes DirecTV SAT Director's Pack [HBH-SA] receiver as did the serial blaster i just swapped out.

I have a Hughes DirecTV remote [HRMC-15] and I used the Hughes_HRMC-8 for the lircd.conf found on the lirc/remotes package and it works well.

I am able to navigate within MythTV and used all the functions of the remote.

I tried IRRECORD using my HRMC-15 remote but it would only record in RAW format.

The lirc: Version: 0.8.2-5.iguana rpm

The driver: Version: 0.95-1.iguana rpm

Output from igclient to list the sending channels --get-channels which gives me [get channels: success: channels=0x00]

Output from igclient to list version number gives me [get version: success: version=0x0102]

Output from igclient to get carrier gives me [get carrier: success: carrier=38000Hz]

My lircd.conf file is attached.

Any help is greatly appreciated.

[terry]

lircd.conf

[jdunn]

Please take a look at the device through a digital camera (or cell phone camera) while you try and send signals. Those cameras can see into the infrared and you should see the LED light up as a white light. Also, run igclient --get-features and post the output. It should be a number, and shouldn't be 0. If it is 0 then I know what the problem is and will have a fix for it posted this weekend.

[terry]

Replying to jdunn:

Please take a look at the device through a digital camera (or cell phone camera) while you try and send signals. Those cameras can see into the infrared and you should see the LED light up as a white light. Also, run igclient --get-features and post the output. It should be a number, and shouldn't be 0. If it is 0 then I know what the problem is and will have a fix for it posted this weekend.

I don't have access to a digital camera at the moment but the plug in transmitter is sending signals. I have an RCA RF extender cone that beams signals to another room. The cone lights up with each digit of the channel I am trying to change to. I use the attached chang.sh file to change the channels on the command line. If I change the sleep parameter in this file, i can see that the pulses increase or decrease. This is the same file I am currently using for the serial blaster. I tried a different plug in transmitter and both are sending pulses of light to the RCA cone extender. I know the RCA cone extender is functioning because I can change channel when I use the remote to change channels pointing at the cone.

Output from igclient to get features gives me [get features: success: features=0x2]

Hope this helps.

[terry]

Replying to terry:

Replying to jdunn:

Please take a look at the device through a digital camera (or cell phone camera) while you try and send signals. Those cameras can see into the infrared and you should see the LED light up as a white light. Also, run igclient --get-features and post the output. It should be a number, and shouldn't be 0. If it is 0 then I know what the problem is and will have a fix for it posted this weekend.

I don't have access to a digital camera at the moment but the plug in transmitter is sending signals. I have an RCA RF extender cone that beams signals to another room. The cone lights up with each digit of the channel I am trying to change to. I use the attached chang.sh file to change the channels on the command line. If I change the sleep parameter in this file, i can see that the pulses increase or decrease. This is the same file I am currently using for the serial blaster. I tried a different plug in transmitter and both are sending pulses of light to the RCA cone extender. I know the RCA cone extender is functioning because I can change channel when I use the remote to change channels pointing at the cone.

Output from igclient to get features gives me [get features: success: features=0x2]

Hope this helps.

Update: If i move the cone next to the built-in LED on the device...there aren't any pulses of light being directed to the cone when i use the chang.sh from command line but the cone receives the pulses of light when i move it back next to the plugin transmitter LED.

[terry]

Replying to terry:

Update: If i move the cone next to the built-in LED on the device...there aren't any pulses of light being directed to the cone when i use the chang.sh from command line but the cone receives the pulses of light when i move it back next to the plugin transmitter LED.

[terry]

Replying to terry:

Replying to terry:

Replying to jdunn:

Please take a look at the device through a digital camera (or cell phone camera) while you try and send signals. Those cameras can see into the infrared and you should see the LED light up as a white light. Also, run igclient --get-features and post the output. It should be a number, and shouldn't be 0. If it is 0 then I know what the problem is and will have a fix for it posted this weekend.

I don't have access to a digital camera at the moment but the plug in transmitter is sending signals. I have an RCA RF extender cone that beams signals to another room. The cone lights up with each digit of the channel I am trying to change to. I use the attached chang.sh file to change the channels on the command line. If I change the sleep parameter in this file, i can see that the pulses increase or decrease. This is the same file I am currently using for the serial blaster. I tried a different plug in transmitter and both are sending pulses of light to the RCA cone extender. I know the RCA cone extender is functioning because I can change channel when I use the remote to change channels pointing at the cone.

Output from igclient to get features gives me [get features: success: features=0x2]

Hope this helps.

I used a digital camera and can see the white light coming from the led...

[jdunn]

We're going through and doing some ticket cleanups and came across this one. Before I close this, is this still a problem, can you try upgrading to the latest driver and firmware?