On April 12, 2010 at 15:52, Vitaliy Borodovsky said...
Can you help me with 2 questions:
1) Some of codes I have do not have frequency at all. Documentation says that it must send "1" without pulsing at all, just instant enabled infrared lamp.
But device uses Pronto Hex format. Do you know any way how to say in Pronto Hex that there is no carrier and we must enable lamp for the whole duration of On pair?
Use 0100 instead of 0000 for the first hex value. That means unmodulated. You still use the second hex value which encodes the cycle length of the modulation because even when unmodulated all the durations are expressed in units of the cycle length. But are you using an actual Pronto or are you using some other device that can import Pronto Hex? Most other universal remotes and IR transmit systems that can import Pronto Hex don't understand the unmodulated codes.
2) All codes I have contain "duty" cycles for the carrier. And they are not 50%
Does devices really decode them? Is it possible to explain to Prontohex that I have duty cycle 30%? If not how I can send these codes using pronto hex?
No consumer IR receiver can detect, decode or care about the duty cycle of a modulated IR signal. A duty cycle around 30% is typical because it gives only slightly less range than a duty cycle of 50% while giving significantly better battery life and/or allowing use of a power level that would burn out the transmitting IR LED if used at 50%.
The Pronto's modulation duty cycle, LED power levels, battery life, etc. are all internal design details of the Pronto itself. They are not programmable for individual protocols nor is there any reason they need to be. (you may as a result get worse battery life than on a remote custom designed for one protocol, but that's what rechargeable batteries are for).
