There have been questions about what products can be used to control TCP/IQ wirelessly. Bruce has been kind enough to test two products and share the information. This information does not in anyway indicate an endorsement or a preference, just that they have been tested.
In order to use wireless Ethernet to control a TCP/IQ system, the computer (or Pocket PC device) must be separated from the TCP/IQ network using a router. This is especially true if Cobranet traffic is present on the TCP/IQ network, as the 100 Mbps audio traffic will swamp the much slower wireless node.
We have successfully tested the following router/access points with a small TCP/IQ system:
Linksys WRT54G w/firmware v1.30.7
D-Link DI-624 w/firmware v1.12
Both of these routers are part of the latest generation of router/access points that support the 802.11g wireless standard and have a 10/100 Mbps auto-sensing port on the WAN side of the router.
I will be preparing setup instructions for both of these routers.
Note: support for these routers require TCP/IQ firmware that has not yet been released as of October 15, 2003.
If you are interested, there were two issues that we needed to address:
1. First, due to the nature of the market for which these products were intended, both of these routers have built-in firewalls that cannot be disabled. This means that all traffic through the router must be initiated from the client side, which in TCP/IQ is the controller software (e.g. IQwic). The way we were doing the delivery of meter data was actually initiated from the component side. Consequently, components could be discovered and controlled, but they would display no meters. The same is true when accessing a system through our VPN. Currently, no meter data is being returned to computers accessing a system inside Crown through Checkpoint.
2. Both routers use a Network Address Table (NAT) to allow multiple computers on a private LAN to access the Internet through one public IP address. Consequently, the IP address appears differently to TCP/IQ devices connected to the WAN side of the router than it would normally, and we were not allowing for this. (The Linksys router actually has a setting to turn the NAT off, but the D-Link router does not.)
No replies to this topic