AMX Modero NXD-700Vi Operation/Reference Manual page 230

G4 touch panels 7” modero widescreen video touch panels with full duplex intercom
Hide thumbs Also See for Modero NXD-700Vi:
Table of Contents

Advertisement

Symptom
My WEP doesn't seem to be
working.
NetLinx Studio only detects one of
my connected Masters.
I can't seem to connect to a
NetLinx Master using my NetLinx
Studio 2.x application.
Solution
• WEP will not work unless the same default key is set on both the
panel and the Access Point.
• For example: if you had your access point set to default key 4 (which
was 01:02:03:04:05) you must also set the Modero's panel key 4 to
01:02:03:04:05.
Each Master is give a Device Address of 00000.
• Only one Master can be assigned to a particular System number. If
you want to work with multiple Masters, open different instances of
NetLinx Studio and assign each Master its own System value.
• Example: a site has an NXC-ME260/64 and an NI-4000. In order to
work with both units. The ME260/64 can be assigned System #1 and
the NI-4000 can then be assigned System #2 using two open
sessions of NetLinx Studio 2.
• From the Settings > Master Comm Settings > Communication
Settings > Settings (for TCP/IP), uncheck the "Automatically Ping
the Master Controller to ensure availability".
• The pinging is to determine if the Master is available, and to reply
with a connection failure instantly if it is not. Without using the ping
feature, you will still attempt to make a connection, but a failure will
take longer to be recognized. Some firewalls and networks do not
allow pinging, though, and the ping will then always result in a failure.
• When connecting to a NetLinx Master controller via TCP/IP, the
program will first try to ping the controller before attempting a
connection. Pinging a device is relatively fast and will determine if the
device is off-line, or if the TCP/IP address that was entered was
incorrect. If you decide NOT to ping for availability and the controller
is off-line, or you have an incorrect TCP/IP address, the program will
try for 30-45 seconds to establish a connection.
Note: If you are trying to connect to a master controller that is behind a
firewall, you may have to uncheck this option. Most firewalls will not
allow ping requests to pass through for security reasons.

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents