
| Troubleshooting | |
| ||
Troubleshooting Information (Cont.) |
| |
|
|
|
Symptom | Solution |
|
|
|
|
Panel doesn’t respond to my | • The protective cover makes calibration difficult because the user |
|
touches | can’t calibrate on specific crosshairs when the sheet is pressing on |
|
| the whole LCD. |
|
| • Verify that the protective laminate coating on the LCD has been |
|
| removed before beginning any calibration process. |
|
|
|
|
The left border of the graphics has | • On some units at some resolutions, wavy lines may appear across |
|
a crawling, dashed line. | the entire screen. This has been seen on middle resolutions and is |
|
| referred to as the "Mid Range Fallout" problem. |
|
| • This is due to the graphics controller settings in the firmware. |
|
| • Update to the latest v2.XX.XX firmware. Visit the www.amx.com > |
|
| Tech Center > Downloadable Files > Firmware Files > Modero |
|
| panels, and then download the KIT file to your computer. |
|
|
|
|
NetLinx Studio only detects one of | Each Master is give a Device Address of 00000. |
|
my connected Masters. | • Only one Master can be assigned to a particular System number. |
|
| When working with multiple Masters, open different instances of |
|
| NetLinx Studio and assign each Master its own System value. |
|
| • Example: a site has an |
|
| work with both units. The ME260/64 can be assigned System #1 and |
|
| the |
|
| sessions of NetLinx Studio 2. |
|
|
|
|
I can’t seem to connect to a | • From the Settings > Master Comm Settings > Communication |
|
NetLinx Master using NetLinx | Settings > Settings (for TCP/IP), uncheck the "Automatically Ping |
|
Studio 2. | the Master Controller to ensure availability" box. |
|
| • 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 |
|
| incorrect. If you decide NOT to ping for availability and the controller |
|
| is |
|
| try for |
|
| Note: When trying to connect to a master controller that is behind a |
|
| firewall, unchecking this option may be required. Most firewalls will not |
|
| allow ping requests to pass through for security reasons. |
|
|
|
|
I have more that one Modero panel | Multiple NetLinx Compatible devices (such as Modero panels) can be |
|
connected to my System Master | associated for use with a single Master. Each Modero panel comes |
|
and only one shows up. | with a defaulted Device Number value of 10001. When using multiple |
|
| panels, it can become very easy to overlook the need to assign |
|
| different Device Number values to each panel. |
|
| • Press and hold the grey Front Setup Access button for 3 seconds to |
|
| open the Setup page. |
|
| • Press the Protected Setup button (located on the |
|
| panel page), enter 1988 into the |
|
| and press Done when finished. |
|
| • Enter a Device Number value for the panel into the Device Number |
|
| Keypad. The default is 10001 and the range is from 1 - 32000. |
|
|
|
|
133 | |
|
|