On December 30, 2009 at 07:31, markrubin said...
even with 2 way ethernet this happens if the system is set for 2 way communication
On my T4's/ XP8's you can see the wireless light on the T4 go out when the remote goes to sleep: it takes a few seconds after wake up to re-establish the wireless connection: no commands are executed during that time
The point of zigbee was suppose to resolve this problem. The reason they decided to use zigbee instead of wifi is because when the wireless connection is lost your device needs to reestablish the link. Has to do a bunch of crap that supposedly you don't need to do with zigbee. I don't know if maybe zigbee does have this limitation and RTI wasn't aware or if it is RTI's implementation of zigbee. Does C4 have this same issue? They aren't doing anything crazy with 2way on their remotes but they do have it. They could be hiding the fact that they do this. With RTI it would be more apparent in that 1-2 seconds.
If it is a zigbee issue I'd be interested to see if buetooth 3 would be implemented in remotes in the future. The biggest limitation and it is a big one would be range. But using bluetooth to establish a link and then use wifi for transferring sounds like the best of both worlds.
It looks like bluetooth can actually go up to 300ft. but it has to be a class1 device which is specified as mostly industrial.
