The hit or miss on some codes may also be due to the faster IR timing. I found that adding a .1 delay before the code fixes it on those that have this problem. The other option is to hold down the button until the device responds.

This message was edited by onward on 03/29/04 18:35.

After 1 year of seeing people complain that their remote is too slow, now they are complaining it is too fast? How can Philips win? Stop being lazy and add your delay and if you needed your signal to repeat, such as fast forward or volume, then you have to hold down the button anyways. It's impossible to make a fool proof product that works with every 3rd party unit, ask Microsoft.

Before you guys attack and call Lowpro lazy and all...oops, too late. Those of us with the new "delay needed" problem are not too lazy to put in the delay - I already did (took all of 10 minutes to do), the problem is that now each press is a macro and will only execute once - so in order to scroll down a list with the cursor, we have to press and release, press and release, press and release, ... I agree that the new firmware is nice, but Philips solution to go ahead and add the delay to fix the problem doesn't seem right. Why is it that a quick press in the previous firmware worked just fine and now it doesn't? Did the previous' firmware IR delay problem somehow force a 250ms or longer burst - after some delay? I can live with this delay fix, but it just doesn't seem right. But please don't attack those of us that are trying to get things right. One day you too might get that special DVD player or Satellite receiver and have the same problem. ;-)

Just had a thought - is there any way that Philips could allow us to set the IR burst time? It could be a setting in the editor...it could be set to some default, but also be adjustable for different needs.

I've always thought they should allow us to set burst length. Many other companies do, such as, Elan for their VIA and Z-Pads, Lexicon allowed it for the outdated 700T, and I'm sure other companies allow you to alter the burst length. I'm no IR protocol expert (or novice even) but I wouldn't think it would be that difficult to add into the software.

When you merge a blank pcf with the older pcf the result pcf will have two "home" being the default the one in the blank pcf, so all the links and jumps to the old home page are broken.

Willy.

I tried the merge idea, but the battery icon still shows a dark backround on a light screen.

After installing new firmware and software for the TU-3000, SOFMY codes for a Draper Screen can still not be corretly learned. I tried all the JUJU that I know and still nothing. Any suggestions?
The codes worked just fine on the TU-2000.

How about pasting the hex from a CCF?

Willie,
I ran into the same situation. I simply copied everything from my old "home" to my new "home" and then made the old "home" invisible by clicking on "hide device." By copying the pages and devices from the old to the new, all of the jumps and links work fine.

Onward:
I think the secret is to create a new pcf and THEN merge your old pcf to the new one. I tried it the other way and had the old system page format appear.

Hope this helps,
Rick

Some of us support a fleet of Prontos.

Previously, adding a new device or updating the firmware was relatively straight forward. Many times I could ask a customer to bring their unit by and I'd do it at the counter, knowing that the unit would work fine at home.

Now, it seems like I'll have to go to the customer's home and fuss with things, probably having to check all or most of the pages and buttons again. (Eventually, of course, I'll have corrected most of my library of devices, but I'll have to do it again after a better solution is worked out for the 0.1 second delay that is sometimes required.)

I also have to face the issue that once I install the new editor, I'm forced to struggle through updating the firmware on any TSU3000 that I touch in the future. Furthermore, selling an additional or replacement unit to a customer suddenly becomes a problem because the new unit will respond differently than the old units.

Well some have asked me what is the big deal about having to insert a .1 second delay. Read below.

Before you guys attack and call Lowpro lazy and all...oops, too late. Those of us with the new "delay needed" problem are not too lazy to put in the delay - I already did (took all of 10 minutes to do), the problem is that now each press is a macro and will only execute once - so in order to scroll down a list with the cursor, we have to press and release, press and release, press and release, ... I agree that the new firmware is nice, but Philips solution to go ahead and add the delay to fix the problem doesn't seem right. Why is it that a quick press in the previous firmware worked just fine and now it doesn't? Did the previous' firmware IR delay problem somehow force a 250ms or longer burst - after some delay? I can live with this delay fix, but it just doesn't seem right. But please don't attack those of us that are trying to get things right. One day you too might get that special DVD player or Satellite receiver and have the same problem. ;-)

I also have a problem now with my codes not always working for other things. I don't have to hold the buttons down, but in my macros I am getting misses quite frequently where I never got them before. How can I be sure which codes I need to add the .1 second delay to and which ones I don't. There is no way to be sure. I am not looking forward to adding a .1 second delay to all the IR codes in my setup just to ensure the remote works like it did before this new firmware. I had no problems before with any code in my remote. My pronto is going back and I am picking up a new one with the older firmware, so I can just upgrade to the firmware that is one version before this latest one. I will just live with the vol/mute/channels being backlit on first key press until Phillips lets us control IR burst length and whether a hard button backlights first or not.

-Lowpro

I have just started using the new multi line label feature. However it doesn't seem to work quite how I expected. I have many rectangular channel buttons and it appears that the the second line of a label cannot display the same width of text as the first line.

For example:
Community
Channel

Becomes
Community
Chan...

It displays correctly in the editor but not on the remote. Is this the correct behaviour, or am I doing something wrong? I would hope that the second line would be capable of displaying up to the same width as the first line.

Teresa

I was thinking which could be a dangerous thing by the way. :-P

Anyway, would it be possible for the Pronto Team to add an option under the device properties RF tab in the editor where we could set the IR burst length. The options would be "Long" IR burst, like it was before this firmware update, and the other option would be "Short" IR burst, like it is now.

This would allow the end user to simply enter the IR burst length they need per device. If I could set the IR burst length back to what it was before this most recent firmware and editor update my issues in this regard would be resolved and I'd never have to look back. Having the option as an end user (when feasible) instead of globally changing something for everyone is a win win for all concerned.

If the Pronto Team would consider integrating such an option as I have described above in the next firmware and editor update that would be greatly appreciated.

Thanks,
Lowpro

This message was edited by Lowpro on 03/30/04 12:14.

Rick, that's exactly what I did. I created a new PCF, merged my existing with it. I got the new system page format. I removed all the other system items except date, clock and battery. Ran it in the emulator and the battery icon is dark against a white backround. I didn't bother to download it to the 3000 since the emulator usually displays it the same.

This message was edited by onward on 03/30/04 11:28.