Your Universal Remote Control Center
RemoteCentral.com
Philips Pronto NG Family Forum - View Post
Previous section Next section Up level
Up level
The following page was printed from RemoteCentral.com:

Login:
Pass:
 
 

Topic:
IR Duration
This thread has 11 replies. Displaying all posts.
Post 1 made on Monday April 18, 2005 at 21:59
shotzes
Long Time Member
Joined:
Posts:
April 2005
42
On the TSU 3000, what is the "default" time for duration on a given button. If i wanted to make the duration longer, clicking on minimum, starts at .01 seconds. Is that longer than default or shorter?
Help?
Post 2 made on Monday April 18, 2005 at 22:11
Peter Dewildt
Loyal Member
Joined:
Posts:
July 2001
6,307
I think it has previously been stated that an IR Code in a macro has the repeat part transmitted 5 times.

For an IR Code that is not in a macro, it is transmitted as long as the button is pushed, but I don't know if there is a minimum time or not.
Peter
Pronto 1000 (retired), Pronto TSU7000, RFX6000 (retired)
Pronto 2xTSU9600, RFX9400
OP | Post 3 made on Monday April 18, 2005 at 22:23
shotzes
Long Time Member
Joined:
Posts:
April 2005
42
sorry peter, that didn't help me because i don't really know anything about the way it all works. The problem i'm having is that on my pioneer products i noticed i have to hold the bottons down longer than any other brands. I saw the "new" duration button and thought i could fix my problem.
Post 4 made on Tuesday April 19, 2005 at 01:18
Peter Dewildt
Loyal Member
Joined:
Posts:
July 2001
6,307
tTy it and see what happens.
Peter
Pronto 1000 (retired), Pronto TSU7000, RFX6000 (retired)
Pronto 2xTSU9600, RFX9400
Post 5 made on Tuesday April 19, 2005 at 01:57
sddroog
Long Time Member
Joined:
Posts:
February 2003
46
On 04/18/05 22:23 ET, shotzes said...
The problem i'm having is that on my pioneer products
i noticed i have to hold the bottons down longer
than any other brands. I saw the "new" duration
button and thought i could fix my problem.

I had that to on my Pioneer CD and MD player with the previous firmware. I solved that by adding a 0.1 delay to every button. Now with the new firmware I removed all those delays again and to my surprise it worked, without specifying a duration (I just left it at default)
Post 6 made on Tuesday April 19, 2005 at 02:11
Daniel Tonks
Wrangler of Remotes
Joined:
Posts:
October 1998
28,782
They might have put the default back at whatever it was for the first Pronto (which worked perfectly until they started fiddling with the RC5000, and continued fiddling with the Pronto NG).
OP | Post 7 made on Tuesday April 19, 2005 at 02:26
shotzes
Long Time Member
Joined:
Posts:
April 2005
42
I updated my firmware and it all works beautifully! Thanks.

This message was edited by shotzes on 04/19/05 02:43 ET.
Post 8 made on Tuesday April 19, 2005 at 08:44
johnsfine
IR Expert
Joined:
Posts:
September 2002
5,159
On 04/18/05 21:59 ET, shotzes said...
On the TSU 3000, what is the "default" time for
duration on a given button. If i wanted to make
the duration longer, clicking on minimum, starts
at .01 seconds. Is that longer than default or
shorter?

I expect the default is much longer than .01 seconds.

Most IR signals have a repeat pattern around .1 seconds long. So a duration less than .1 seconds probably wouldn't get you beyond the minimum possible duration for the signal.

I assume the Pronto still obeys the repeat pattern. For example a protocol with a simple .09 second repeat pattern would permit a .09, .18, .27, .36, etc. duration. It wouldn't permit an arbitrary duration. I assume that if you ask for .25 in such a protocol, you'd get .27

My rough understanding of the old firmware is:

1) If the IR signal is the only action on a button, then the duration depends on how long you press the button. The only minimum (for a really short press) is the one-time part of the signal.

2) If the IR signal is one of two or more actions (including when you just add a tiny delay as the other action), it has a fixed (in the firmware) duration that has changed from version to version, which in at least one early version was too long for many devices and in all versions has been too short for many devices (no one duration is good enough for the range of devices).

How does the new firmware act? If I understand the earlier posts in this thread correctly, the new one has a default duration that is longer than the fixed duration described in (2) above.
Can you reduce that on a device basis for devices that were problems when (2) was longer?
Can you reduce it on an individual signal basis?
I assume you can increase it on an individual signal basis (since most of the complaints leading to creation of the feature were specific commands needing very long duration).
I assume it is the fixed duration when a signal is one of multiple actions. Is it also a minimum duration when the signal is the only action? (Duration is the longer of that minimum or the actual press)?
Post 9 made on Tuesday April 19, 2005 at 13:07
CV27
Long Time Member
Joined:
Posts:
November 2004
146
John,

My rough understanding of the old firmware is:...

Your post could be an answer to one of my (many) questions in a separate thread ([Link: remotecentral.com]) :

I have a button, let's call it M1, containing 2 links:
- the first link is to a button (B1) containing an X10 IR command (code) to an IR543
- the second is a link to a button (B2) containing the Pause IR code for that JVC

Even a short tap on M1 consistantly works, the thing pauses. But if I press B2, then I need to press and hold for the Pause to occur. I would have anticipated the opposite

Although I'm using the new firmware, if I tie in your 'understanding of durations' with the JVC weirdness of the one burst pair for a single press, could that not explain why M1 works more reliably than B2?
Post 10 made on Tuesday April 19, 2005 at 17:36
Peter Dewildt
Loyal Member
Joined:
Posts:
July 2001
6,307
John, it is labelled "Minimum Duration" in the editor, and it is stored with the IR Code. It applies whether or not it is a single action or one of multiple actions (i.e. a macro).
Peter
Pronto 1000 (retired), Pronto TSU7000, RFX6000 (retired)
Pronto 2xTSU9600, RFX9400
Post 11 made on Tuesday April 19, 2005 at 20:03
johnsfine
IR Expert
Joined:
Posts:
September 2002
5,159
On 04/19/05 13:07 ET, CV27 said...
could that not explain why M1 works more
reliably than B2?

Yes, that explains it.

The default duration used in sequences when there is more than one action must be a good duration for that particular signal. It must be longer than the minimum duration used for single action keys.

I guess that means that the new minimum duration feature can only increase the duration vs. the previous firmware version.
Post 12 made on Thursday April 21, 2005 at 20:20
joeyd27
Long Time Member
Joined:
Posts:
March 2004
40
This new IR duration is great.
I have mostly all Sony equipment and had to add the .1 sec delay to all the codes. Now I did away with the delay and set the minimum duration to .1 and now it works great.
Also on my Motorola Cable Box I set the minimum duration to .01 and now it is faster reacting. If I want channel 150, I can now type in 150 faster than I could before without having it miss a number. Definitely a noticable difference.


Jump to


Protected Feature Before you can reply to a message...
You must first register for a Remote Central user account - it's fast and free! Or, if you already have an account, please login now.

Please read the following: Unsolicited commercial advertisements are absolutely not permitted on this forum. Other private buy & sell messages should be posted to our Marketplace. For information on how to advertise your service or product click here. Remote Central reserves the right to remove or modify any post that is deemed inappropriate.

Hosting Services by ipHouse