can't send zero (number 0) to DCT700

[medisoft]

Hi! I want to report that I have a problem sending the number 0 to a motorola DCT700. I can send all other numbers, and other codes, but the 0 I can't.

I can receive all the codes from the DCT700 remote control.

[jdunn]

Could you please attach a copy of the LIRC configuration file that you are using? Since you can receive the code and can send related ones it is most likely that the code is recorded incorrectly and not a problem with the device or driver.

[medisoft]

Lirc DCT700

[medisoft]

The DCT700 file is the one that i generated with irrecord, the dctxxxx is the dct2000 file, that also works receiving almost all codes from my dct700 remote control.

[jdunn]

Well, I don't believe this is a problem with the iguanaworks device or driver. I suspect the problem is the recorded signal, but I'm not sure what's causing it. In general RAW_CODES are less likely to send correctly since noise is added during recording and transmission. However, the space encoded version should work. I tried to run my own decoder on the raw codes and failed to decipher them.

Looking at the space encoded file the only thing that stands out to me is the 0 line:

         0                        0x000000000000FFFF

Even though the other numeric codes contain FF a value of all 1s seems if not unlikely, then at least slightly surprising. Good luck, and I'm going to leave this ticket open for a couple weeks in case you have anything else or add or if anything else occurs to me.

[medisoft]

mmm, i tested with a prerecorded and to my own recorded.... is there a way to "loopback" to see with the same iguanair device to receive the same that is sending?

[medisoft]

Can you see this:  http://ubuntuforums.org/showthread.php?t=712773

there someone commented about this same issue... it seems to be a lirc bug, can you confirm that?

[medisoft]

does your device have hardware carrier? of i need to enable software carrier?

[jdunn]

The devices cannot both send and receive at the same time due to hardware limitations (150 byte buffer to store sent and received codes that cannot be shared, along with timings that have to be precise during transmission while reception causes unpredictable interrupts).

I took a look at the webpage, and since the guy who solved it never said what was really different between the mythbuntu compiled one and his own I can't tell what changed. I would guess that the "with transmitter" serial driver option was not selected. The other thing you should note is that that person could not successfully send ANY signals. Since other signals work for you there is something specific to the "0". The only thing that occurs to me is that you may want to try varying the carrier frequency around 38kHz, but I don't have a ton of hope that it will work.... on the only slightly kidding side have you thought about having it change to a channel without a 0 and then hitting chan-? Crappy yes, but depending on your setup it might work.

I've only seen hardware/software carrier applied to serial devices where there is a kernel driver twiddling data lines at 38kHz in order to generate the carrier (software) or where there is a timer chip and the driver only turns the device on or off (hardware). For our USB devices the carrier is generated onboard so it's a hardware carrier and has no other option.

[bluey]

We haven't seen any feedback on this ticket in 3 months. Please respond with an update or we will close the ticket.

Thank you,

Ben