Hi

I use Pronto 9600 on a network mode, To benefit the Fireball Interface.

Network Gear:

5x 3com access points- all on the same ssid configure to WEP64, on the same wireless channel (6)

1x linksys router

1x 3com giga switch

---
I got 2 main problems:

1. when the pronto isn't in use for more then 1 hour , it will lose communication with
the access point, the procees of reconnecting can take up to 1 minute.

2.When i roam to diffrent room, the pornto wont connect to a closer access point,
and will stay connected to the prev access point with the "poor connection quality".



I know i can write some scripts into my access points to drop connection with a low
rssi values, but will the pronto know to connect to an access point with a stronger
signal?

Thank you

Open the file in ProntoEdit Pro and select System Properties.
Select Wireless settings and look at the timeout setting - is it 1 hour ?
You can select from 15 minutes to 24 hours for the timeout.

Its 24hours,

and by the way, i got my access point to drop a "low signal" connection, but
the pronto wont reconnect to a diffrent access point, i had to force the pronto
to connect to other access point by reseting it.

Do you have a DHCP server? In this case can you verify the IP lease duration. Did you check for the existence of maybe a secondary DHCP server?
Have you tried giving a fixed IP address?

Finally got around to setting my RFX9400 and TSU9600 up in network mode and experiencing similar issues.

It will connect and then drop the connection, nothing is showing in the diagnostic screen.
Then take a minute or more to reconnect.

I am using a Netgear DG834G modem/ router that is set to give the same IP address to each device on the network.

The wireless meter keeps dropping, and all the equipment is withing one metre of each other.

Will get hold of a Linksys WAG54 and try that over the weekend.

Or make sure you have the latest firmware installed into the Linksys WAG54.

Does everyone have the latest firmware for their 9600 Pronto as well as the RFXxxxx extenders??? There are two recent releases; one of the extender and one for the Pronto.

At this point, no one has confirmed this setting but with all of the work/time I have into the Nevo SL wireless stuff, the best setting on the Nevo SL was "never turn off" and "never drop wifi." The 24hr setting in the Pronto extenders is supposed to equal this.

Dave

I have the TSU9600 set for 24 hour connection, the RFX9400 sits connected to the Netgear DG834G without a hiccup.

It is the TSU9600 that is going to sleep and loosing the connection, even if it does pick up a connection it is not stable.

Just reloaded the latest firmware and have set static IP addresses.

Will wait until later today when I get hold of a Linksys to play with over the weekend.

Edit:
Well, was not able to get a Linksys but did get hold of a Billion 7300G and after the TSU 9600 sat trying to connect to the Netgear DG834G for the last day (and failing) it fired up straight away and has so far been OK.

WOW... I hope not to disapoint you, but in my opinion; you might have set unrealistic expectation due to the sale hypes from Philips. In my experience, I will never consider the TSU9600 as a "Multi-room" control system. Instead, I see it as a "one room" solution. What you are pretending is only attainable by more robust communicating devices with a solid operating systems (eg Notebooks, and Tablets). To star; We do not even know the actual TSU9600 protocol; they discribe it as "Wi-Fi and that is all. There is no way to optimiced!

Not one knows (not even philips) if it is a 802.11b, 802.11g, let alone 802.11a. "Roaming" is only a condition of a more complex device and it must be expecified in the settings (no were is that stated on the remote). I have hope that Philips will develop the product to a more stable solution. But than again I have seen others of their "Sales Hypes" end up in dead ends; Just as any one who owns a Philips iPronto TSi6400.

avtech we do now the protocol used and Philips certainly knows it. It's 802.11g, for example in the manual it states that you should enable only "g" mode not turbo g. Also you should not allow any "non g" appliances in your network so it can be a clean normal 802.11g system for best operation. All this is stated in the manual.

Furthemore we also known that the actual TCP/IP protocol used is UDP based (as instead of a slower to connect TCP based) connection where they do their own verification. UDP is superior in terms of speed and simplicity. The penalty you get for those features is that you need to do your own verification and resending. Something the pronto does.

I believe the WiFi network described by ETK is setup incorrectly, and this will not help any WiFi device when roaming. Access Points should not be set to operate on the same channel if their coverage area is intended to overlap for roaming purposes. Instead use only channels 1, 6 and 11 to avoid conflict with each other. However the same SSID and encryption settings should be set for all of them.

Your reasoning might be considered good! But is not a valid one! You may deduct the use of 802.11g based on assumptions, but only if stated clearly in the spec, I would concur with you.

Keep in mind, 802.11b is compatible with 802.11g. Philips could mention 802.11g "Networks" as a reference to throw you off, and have the remote operating at 802.11b since is a low cost solution for them that are compatible with 802.11g. I will only believe it when I see it on "writing" in their specs like any other wi-fi device states it.

I have ask that questions to the "Philip's Pronto Team," all I got is the run around without any definite answer. Please, be my guess! Contact them and ask that question, and have them put it in writing. In any event they should come out clear and state the truth (there is no shame in it).

To make matters worse, I have experienced some network performance drop (read from 802.11g to 802.11b) after placing the TSU9600 on an 802.11g network, forcing all 802.11g devices to operate down to 802.11b speed.

By the way, I would consider the implementation of 802.11b/g in a remote as a very potential limitation; think about all the possible interference in the 2.4 GHz frequency; no wonder all the cordless phones are now operating more reliable in the 5.8 GHz. I would think, many times, before attempting to place one of these remotes in cities like Manhattan. At it is right now, I am hopping for the new 802.11n "Dual Band Draft" wireless routers. This might provided a liable solution to the networks performance drop with the TSU9600.


In my opinion, 802.11a would have been a better solution. 802.11a operates at 5.8 GHz. frequencies making the device less prone to interference from the many wi-fi networks and devices that operate at 2.4 GHz. I guess the only compromise is a smaller coverage area, but a strong, reliable and fast communication. Even better would have been if you could select the actual frequency based on the circumstances.

First of if you call it an assumption because it's "only" stated in the manual then a specification wont help you either. They might lie in that one too.

But it's quite funny how you can bash Philips on what wifi standard they have and that they don't specify it in any specification when you obviously haven't even bothered to check the actual specifications.
So go to [Link: pronto.philips.com] for the technical data then take your pick of specification under TSU9600.
Go to page 2 and on the left side the third headline called "Connectivity" on the very first row under that it clearly states "Built-in wireless technology: 802.11g".

Personally I really like that they used 802.11g so I can use my existing wifi routers and don't have to buy special equipment just to get the pronto signal to the next room.

I will apologise for not seen that into the spec before! I will take back my coment about Philips not stating in writting the communication protocol. I hope my point is clear: no shame in the thruth! And I like to thank Xetick for pointing the info out.

Point taken!


I hope you can address the second point: the Roaming issues for multi-room, "next room," aplication. Can you place the TSU9600 into multi-room operation reliable in 802.11g?

Hi people

After long testing, with diffrent access points, i can clearly said

as for this moment the philips pronto isnt supporting roaming, the remote will have to disconnect from AP in order to connect to
a new one.

I know philips is working on this issue, and im sure it will be solve soon.

I did send philips some feedback and will update, as soon as they will replay

As this thread is pointed out as the main thread regarding WiFi roaming, I'll share my idea here.
First of all the message by dvwebster made some sense to me, has anyone tried implementing such infrastructure? I mean using different channels cause that might get the pronto to reconnect quicker or anything?



Now, another idea I had in order to get the 9600 to reconnect quicker is just to make its antenna worse.
I'll explain - if I have three rooms that have good reception-overlap then I'll go from room to room and the pronto will stay connected to the older room but with low reception - it won't reconnect to the current room until reception totally dies, and that sometimes never happens cause it's hard to get the overlap to be that exact.
Now, if I open the sucker up and get some copper on/near the antenna or replace the RF cable from the XMTR to the antenna to a worse cable (IF there is one) then I'll get it's WiFi performance DOWN, which will force it to disconnect faster when moving between rooms, hence REconnecting faster too to the current room.

Any thoughts before I crack it open?
Don't suppose anyone has any pictures of its board or schematics right?