page 3 – 6
AM-55 / Sep 2015
A M - 5 5 G U I
The AM-55 and Internet Security Concerns
The AM‑55 does not act as a “web device” or “web server,” nor does it support
open ports to the Internet. Therefore there is no worry that someone could “hack” into
the AM‑55 and use it as a pathway to the rest of the network to which it is connected.
About DHCP and the AM-55
The AM‑55 does not utilize DHCP – Dynamic Host Configuration Protocol (or
automatically assigned network addressing) – and needs to be assigned a “STATIC”
network‑unique IP address. Most DHCP servers assign addresses starting at the bottom
of the group 192.168.0.xxx. Therefore choosing an address high in that group, say
192.168.0.200, as a static IP address will likely keep it out of the way of the busiest
DHCP addressing.
However, it’s always wise to check with your network administrator to determine
what static IP addresses may be open and usable for the AM‑55. Sometimes the local
network warrants the “Subnet” and “Gateway” values to be vastly different, but our
suggested starting values for the Subnet and for the Gateway usually suffice for all but
the most complex situations.
The AM-55 Network Protocols and Ports Used
The AM‑55 uses both TCP and UDP protocols to communicate with the remote GUI.
TCP is used from the GUI to the AM‑55 because its high reliability ensures that all control
changes sent to the AM‑55 will be received with 100% accuracy. The UDP protocol is
used by AM‑55 to send and update metering and other real time data back to the GUI.
The TCP protocol uses port 55905. The UDP Protocol uses a port in the range between
60000 and 60010. It tries 60000 first and if it is busy it tries 60001 next. This process
repeats if necessary until an idle UDP port is found. Note that AM‑55 requires these
ports to be open through any firewalls for successful connectivity.
For information on configuring the Network settings on the AM‑55, please see page
2‑9 of this manual.
