If you want to discuss the features of the new TSU 7000 please use the thread entitled TSU 7000 Questions and Answers.

This thread is about the actual beta testing program and how it was conducted.

In mid-September four of us from Remote Central were approached to become beta testers for the new 7000 (also known as the 980 for the international model).

We were given access to a beta testing web site and initially provided with a beta release of Pronto Pro Edit NG (PPENG). There were two bulletin boards - a Bug board and a general Discussion Board. There were also other beta testers mostly custom installers.

The first phase was to give PPENG a real try out - which is what we did.

Over the entire course of the beta testing program 211 threads were posted on the Bug Board - mostly by the four of us. This does not mean that there were 211 bugs - far from it. Many of the entries were suggestions, duplicate entries, very minor cosmetic bugs etc. We scoured Remote Central and found every reported 3000 bug to check to see if they still occurred with the 7000. Some did and were reported.

I would say that all up there were about a dozen significant bug reports. And I'm very pleased to say that they have been fixed. If there are any significant bugs remaining, we didn't find them. There are probably still some minor bugs outstanding but Philips knows abut them. Many suggestions were made which may end up appearing in future versions.

After a couple of weeks testing the software, we received our 7000 (even me in Australia), along with the first updated version of PPENG. It was great to see that many of the reported bugs were fixed. This is where the fun started - working on our own PCFs, migrating from old CCFs, learning codes, downloading, updating, tweaking etc., put up with bugs in PPENG (most of which were eventually fixed).

Then we were informed that some hardware bugs had been discovered which meant replacing a chip in the 7000. The new firmware would not be compatible with the original 7000, so we were sent new final production models of the 7000.

I also managed to get hold of an RF Extender. I just turned it on and it worked first time.

So what does that mean for the 7000?

This is the most thoroughly tested remote that Philips has produced. Even though we encountered problems (which should now all be fixed), we all found both the hardware and the software quite reliable. If you are concerned about the problems with the 3000 – don’t be, they are gone.

I am very proud to have been part of the beta testing program. And I believe that the work that we have put into the 7000 has paid off. This is a fantastic remote and the software and firmware is now most reliable.

The 7000 itself is absolutely fantastic. The color is so brilliant. The graphics that come with the gallery are fantastic and it is so easy to produce a professional looking PCF using the supplied graphics.

If you can afford one, I strongly recommend you buy one.

My 1000 stopped being used weeks ago, and is now well and truly retired. The 7000 rules!

[In case you are wondering – I have to declare a pecuniary interest, we all got to keep the 7000]

And for 3000 owners, Philips is currently working on a new release that will incorporate bug fixes discovered in the beta testing that are applicable to the 3000.

Peter
Very informative...Thanks

I am wondering if that (bug fixes) means to the software or to the remote itself?

Both software and firmware - yes.

I have no idea if the hardware changes for the 7000 also apply to the 3000. If so, then it may be possible that newly built 3000s will get the changes. Probably depends on how far away the 4000 is.

Well Peter,

You upped me once again. I could not have said it better.

The 4 individuals that Peter refers to are:

Peter, Andrea, Archer, and myself. I've had a remote since October 17 and Software since September 17. You can rest assured that we have all put the software and hardware through its paces.

I was probably the lone man out as I use WIN98SE. The release notes with the software package detail issues with WIN98SE. If you have a large CCF with lots of images, you may slow loading or out-of-memory conditions that are ALL attributed to the design of WIN98SE and not to Philips software.

If you hop over to the iPronto forum and are wondering if you will have the same problems with the 7000 that are being reported there, be assured that you will NOT.

If you are questioning a purchase of a 7000 because of the bugs reported on the 3000, DON'T.

Peter could not have said it better, this remote has been the most thoroughly tested prior to release of any Philips remote to date. I myself have logged over 100 hours on the software, particularly in the RC9200 migration and user interface areas.

If you can afford it, and can invest the time in converting existing graphics to transparent PNGs where required, it is the best $999.95 USD that you will ever spend.

Even with an RF extender the cost is still lower than the MSRP of the RC9200.

I must admit that I love the larger screen size on the RC9200.

However, I hate the contrast bars on the RC9200. I already have a version of SuperNudelist that will generate panels of 240x253 such that they can be migrated easily from a 9200 CCF. If you are interested in more info on SuperNudelist, please see the 'So You Want SuperNudelist for the 3000' thread in this forum.

Lyndel and I have spent a lot of time on the 7000. I'd be quite close to 100 hours as well, and that is not counting the time I spent migrating and the redesigning my CCF to the 7000.

Lyndel was really strong on the User Interface of PPENG and migration issues. I concentrated on previously reported bugs, upload/download/learning, stress testing.

Together we exchanged very many emails tracking down bugs before and after we posted them. Lyndel showed amazing patience in his detective work.

Together we've been working on new utilities for the PCF format. Lyndel is doing SNL, and I'm doing PCF Explorer (which is almost ready for release).

My RC9200 is retired. I love the TSU7000!

Let me also assure everyone that the beta test process was a success. A *LOT* of things were caught by Peter and Lyndel. They were so thorough, they even pointed out "bugs" in the online documentation and manual!

How is the battery life on this TSU7000?

Found the answer to the battery life question...

-Hinke

This message was edited by Hinke on 11/27/03 09:08.

Thankx guys ................
Now I KNOW I`m going to get one !!

Hi;

Thanks to all the beta testers. The role sounds fun to many of us but the dedication/committment to the process sounds time consuming. The kept 7000 can't adequately re-imburse a tester for all the hours they invest. "Labor of love." and "Enthralled with the get go.", I would guess.

Thanks again.

Now I am also thinking about getting a 7000.

Dave O

Your welcome,and thanks the nice response. Beta testing can be lots of fun, but it can also be lots of work, trying to reproduce a bug that pops up only after a series of events, regression testing and such.

We reported many bugs and many suggestions for enhancements for the 7000. I think we will see many of these suggestions being implimented in future updates.

The 7000 seems to be a stable remote but we are still going to find users that will have problems from bugs we didn't uncover, not knowing how to use the software, an occasional faulty remote, and etc.

If you get a 7000 I believe you will enjoy it. The color display is really great. My wife wouldn't be able to use our Home Theatre without the use of our Pronto

Dave

I'm sure your efforts were appreciated, but I have to disagree that Philips "listens". So far as I can see, TSU3000 buyers have essentially been abandoned by Philips as they moved all efforts to the TSU7000. The latest PENG update is feeble, with no new features and many bugs left unresolved.

Philips simply don't get it -- the TSU3000/TSU7000 should be a PLATFORM, not a DEVICE. If they really want the thing to be a success, they should release specs on the file formats etc and let the community as a whole address the poor firmware/PENG issues.

My son is playing today with Lego Mindstorms robots. As a toy, this is very successful because Lego released an SDK and supported 3rd party efforts, so now you can get Java kits and C-language kits for the device, and there is a thriving community supporting and promoting the device. Lego benefits (increased sales), the users benefit (more choice). Anyone spot the difference between this model and Philips brain-dead one?

-Tim

Interesting message Tim. I am in the computer industry and Solution Development Kits (SDK's) are indeed the standard. However, they do not seem to be the standard in consumer electronics yet, including the Philips remote. We have all been trying to help Philips move up to the US standard of SDK's, 3rd party delevlopment, etc., and they are listening but possibly somewhat hesitant, based upon country differences.

I agree there is a large market potential for companies who develop products based upon these unwritten standards and who recognize the potential market. It is possible that Philips still needs a little push in this direction.

They have shown a lot of fortitude with their recent TSU7000 beta program, which is a big move for them. It appears they are going in the right direction. Hopefully if it is fast enough for the US marketplace, remains to be seen.

Dave D'Arche
http://ProntoGuide.com

Peter... if you're still here, did you ever complete PCF Explorer? I searched RemoteCentral (and Google) for it but didn't see it anywhere (looked in PCF downloads first). I've been off the grid (or RC) for a few years, but just started re-fiddling with my TSU3500 configuration, and was interesting in doing some manipulation of the XML.

Thanks,
Jeff