AMX WebLinx Instruction Manual
  1. Manuals
  2. Brands
  3. AMX Manuals
  4. Software
  5. WebLinx
  6. Instruction manual
AMX WebLinx Instruction Manual

AMX WebLinx Instruction Manual

Administrator program
Hide thumbs
Table of Contents

Advertisement

Quick Links

instruction manual
WebLinx
Administrator Program
(Version 1.1 or higher)
So f twa re

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the WebLinx and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for AMX WebLinx

Summary of Contents for AMX WebLinx

  • Page 1 WebLinx Administrator Program (Version 1.1 or higher) So f twa re...
  • Page 2 The AMX Software is owned by AMX and is protected by United States copyright laws, patent laws, international treaty provisions, and/or state of Texas trade secret laws. Licensee may make copies of the AMX Software solely for backup or archival purposes. Licensee may not copy the written materials accompanying the AMX Software.

  • Page 3: Table Of Contents

    Getting PWS or IIS Web server programs ................14 Program Pages and Options ................... 14 Using the WebLinx Server and IDK................. 14 Starting the WebLinx Server and Administrator Program ..........15 Connecting to an AXB-NET/NetLinx Central Controller ..........15 Shutting Down the WebLinx Server ................16 Administrator Operations ..................17...
  • Page 4 Administering user accounts ....................21 Popup messages ........................22 Administration Page ......................22 Uploading files to the WebLinx Server PC ................22 Downloading files from the WebLinx Server PC ..............23 Sending touch panel (.TPD) files ................... 23 Sending Axcess/NetLinx (*.AXS) program files ..............24 Sending Infrared Library (IRL) files ..................
  • Page 5 Table of Contents Troubleshooting .....................43 WebLinx Administrator Program...
  • Page 6 Table of Contents WebLinx Administrator Program...

  • Page 7: Product Information

    NetLinx equipment. Once the Internet Protocol (IP) links are created between the WebLinx Server and Central Controllers, you can use the Administrator program to update remote system programs, touch panel files, and create Axcess/NetLinx program libraries, or backups to ensure remote systems are operating at optimal performance levels.

  • Page 8: Sample Product Application

    Product Information Sample Product Application FIG. 1 shows a PC remotely communicating with the WebLinx Server using IE and controlling an Axcess Central Controller system via the Internet, through an AXB-NET. Remote Communication/Control Configuration PC running Internet Explorer Communication AXB-NET Ethernet...

  • Page 9: Minimum System Requirements

    Static (fixed) or DHCP IP address (supplied by Internet Service Provider) Operating systems and Web servers The WebLinx Administrator program is compatible with any one of these operating systems: Microsoft Windows 98 with PWS (or equivalent) Microsoft Windows 2000 PRO with Windows 2000 server (IIS or equivalent) Microsoft Windows NT Workstation (4.0 or higher) with:...

  • Page 10: Installing Weblinx Administrator

    6. From the Directory Permissions dialog, ensure that Replace Permissions on Subdirectories is checked, and select OK. 7. If you have already attempted to run WebLinx Administrator prior to this, you may have to reboot to ensure permissions have been updated fully.

  • Page 11: Things To Know Before Starting

    Accessing WebLinx through firewalls It may be necessary for you to locate the WebLinx Server PC inside a firewall-protected network. Firewall programming is not easily accomplished, and should only be done by network-trained personnel to maintain the integrity of a secure network.
  • Page 12 Product Information WebLinx Administrator Program...

  • Page 13: Designing Weblinx Systems

    If using another OS, you must upgrade or change operating systems to work with WebLinx. The following table lists OS’s you can use along with the compatible Web Servers, and NIC configuration requirements to design a secure WebLinx system.
  • Page 14 IP addresses (one DHCP/static and one non-resolvable) to create a secure network and control configuration for the WebLinx system. If the described two IP address configuration is not used, the target PC and remote Central Controller systems are exposed to the outside world.

  • Page 15: Getting Connected

    Do not attempt these installation instructions unless you are experienced in both areas. For experienced persons, please read the manufacturer's instructions accompanying the NIC hardware, in addition to the instructions in this section to properly configure the WebLinx system. Windows 98 and dual NIC configuration If you are using the Windows 98 OS, you need to purchase and install two NICs configured for TCP/IP communication into the target PC.

  • Page 16: Windows Nt (Server/Workstation) And Single Nic Configuration

    When the boot-up is complete and the desktop is open, verify the new IP addresses are correct as described in these steps. You should record all the IP addresses in the WebLinx Configuration Log to prepare for setting up the system links in the WebLinx Configuration program.
  • Page 17 5. Click the Add button, under the IP Addresses field, to open the TCP/IP Address dialog box. Enter the non-resolvable IP address for the WebLinx Server. Then, tab and enter the IP address for the Subnet Mask (like 255.255.255.0). Click Add to save the second non-resolvable IP address.

  • Page 18: Windows 2000 (Server/Workstation) Nic Configuration

    The first AXB-NET IP address you use should be the non- resolvable IP address assigned to the WebLinx Server plus one. For example, if the non- resolvable IP address assigned to the WebLinx Server was 192.168.100.100, then the first AXB-NET device address should be 192.168.100.101.

  • Page 19: Target Pc Name And Ip Address

    2. Record the IP address information in the WebLinx Configuration Log. Getting AXB-NET IP configuration information The AXB-NET devices you plan to use to communicate with the WebLinx programs must have non-resolvable IP addresses that comply with the RFC-1918 specification for Address Allocation for Private Internets as described earlier in this manual.

  • Page 20: Getting Pws Or Iis Web Server Programs

    Using the WebLinx Server and IDK Before installing the WebLinx programs, you should have PWS or IIS installed on the target PC equipped with one or two NICs, and configured with the proper IP addresses. You also need to have the PC, NIC, and WebLinx Server address information you recorded in the WebLinx Configuration Log on hand to install these programs.

  • Page 21: Starting The Weblinx Server And Administrator Program

    4. Enter the non-resolvable IP address assigned to the AXB-NET device connected to the Central Controller. 5. Enter 1-255 in the Device field to assign an Axcess device number to the WebLinx Server or 1- 32,000 for a NetLinx system. This number should match the WLSERVER=<1-255> value used in the Axcess program installed in the Central Controller.

  • Page 22: Shutting Down The Weblinx Server

    About WebLinx page, launch WebLinx Administrator, and Shutdown the Server Shutdown. 11. A green WebLinx Server icon should start blinking in the desktop tray as shown in FIG. 4. A blinking green icon means the WebLinx Server is communicating with the AXB-NET/Central Controller system.

  • Page 23: Administrator Operations

    3. Click Log Out on the main page to log out of the program. Logging In/Out (Remote PC) 1. Launch IE and enter <PC Name or Web Server IP address >/WebLinx to open the Administrator program. 2. Click User Login and enter your name and password in the User Name field. After you perform the required operations, proceed to step 3 to log out.

  • Page 24: Select Server

    Refer to the Configuration Log table on page 12 if you don't know the IP address. The first time you connect to a WebLinx Server, you enter the IP address to establish the initial connection, and then set links to one or more AXB-NET/NetLinx Central Controller systems.

  • Page 25: Server Links

    Server Links The Server Links page lists detailed information about each system you can link to the WebLinx Server. You can edit and/or delete these links as required. There are also options on the page to add new system links, reset the server to update link information, and shut down the server.

  • Page 26: Listing, Editing, And Deleting Server Links

    3. Locate and click Delete on the target server link you want to delete. Then, click OK on the confirmation dialog box to delete the link. 4. Click Reset Server to update the WebLinx Server if you change the server link configuration. If not, click Back to Main.

  • Page 27: Preferences (Administrator Account Only)

    3. Click on the Security tab and give full control to the guest group. Security settings can only be set if you have OS Administrator privileges. 4. Click Back to Main. Ensure that the WebLinx directory (and all files/subdirectories) have sufficient permissions for the Guests group. Otherwise, you will not be allowed to create new users.

  • Page 28: Popup Messages

    Uploading files to the WebLinx Server PC You can upload touch panel (.TPD), Axcess (.AXS), and Infrared Library IRL files to the WebLinx Server's PC. When you upload files to the PC, they are placed in the ..\inetpub\wwwroot\WebLinx\admin\filecache folder. Then, you can send these files to specific Axcess equipment or to the Central Controller.

  • Page 29: Downloading Files From The Weblinx Server Pc

    3. Choose ALL in the Show Files drop-down menu to see a complete list of Axcess program, IRL, and touch panel files stored on the WebLinx Server's PC. Each file is listed by name along with its size, creation date, and last modification date.

  • Page 30: Sending Axcess/Netlinx (*.Axs) Program Files

    If no Axcess program files appear in the menu, you need to upload the file as described in the Uploading files to the WebLinx Server PC instructions. Keep in mind that Send Source applies to Axcess files the Axcess system only.

  • Page 31: Diagnostics

    Axcess Programming Language and product-specific instruction manuals on hand to send properly constructed Axcess commands to the system and/or its devices. You can also use the AMX Control Disc's Product Publications CD that contains a complete set of all Axcess product instruction manuals.

  • Page 32: Sending Channel Commands

    3. Enter the Send String command in the Send Strings field. All string send commands must have a single quote before and after the command. The program automatically places double quotes around the command line. Then, click Send to send the command to the target device. Then, click Back to Main. WebLinx Administrator Program...

  • Page 33: Sending Axcess Send Commands

    Click Slot to display the Axcess CardFrame's slot number (1 or 2) of the master processor controlling the Axcess bus. Single master processor controllers like the AXB-EM232 will report slot 1 is in control. 3. Click Back to Main. WebLinx Administrator Program...

  • Page 34: Setting The System Date And Time

    2. Click anywhere on the About page to close it. Help Option Click Help to launch the WebLinx Help program. If a File Download dialog box opens, click the Open this file from its current location option. Then, disable the Always ask before opening this type of file option.

  • Page 35: Weblinx Programming Commands

    WebLinx server control port The WebLinx Server monitors TCP/IP port number 10501 for control commands. This port is a fixed parameter for the WebLinx Server, and is stored in a configuration file for the WebLinx Server program. WebLinx Administrator Program...

  • Page 36: Command Functions

    WebLinx Programming Commands Command Functions Command functions are ASP script operations that the WebLinx Server processes and sends to the Central Controller's processor as operations to perform. Command Functions WLDecByteLevel Syntax: Decrements the byte level WLDecByteLevel (WLHost, WLPort, plpdev, plpport,...
  • Page 37 - Port on the device (16-bit integer) plpsys - System ID of the control network (16-bit integer) plplevel - Level on the device (16-bit integer) Return value wLevel Value - Level value returned from WebLinx Server (16-bit integer) WebLinx Administrator Program...
  • Page 38 WebLinx Server. Arguments: WLHost - WebLinx Server address (string) WLPort - WebLinx Server control port (10501) plpdev - Device number on the control network (16-bit integer) plpport - Port on the device (16-bit integer) plpsys - System ID of the control network (16-bit integer)
  • Page 39 Arguments: WebLinx Server. WLHost - WebLinx Server address (string) WLPort - WebLinx Server control port (10501) plpdev - Device number on the control network (16-bit integer) plpport - Port on the device (16-bit integer) plpsys - System ID of the control network (16-bit integer)
  • Page 40 WLHost - WebLinx Server address (string) WLPort - WebLinx Server control port (10501) plpdev - Device number on the control network (16-bit integer) plpport - Port on the device (16-bit integer)
  • Page 41 Value - Set the level value (16-bit integer) WLDeviceCommand These device-specific strings are internal WebLinx commands to a specific WebLinx device. These commands can optionally return the results back in a Sends strings to a specific CR/LF (carriage return/line feed) delimited strings.
  • Page 42 "GetAt Index") Arguments: WLHost - WebLinx Server address (string) WLPort - WebLinx Server control port (10501) plpdev - Device number on the control network (16-bit integer) plpport - Port on the device (16-bit integer) plpsys - System ID of the control network (16-bit integer)
  • Page 43 Arguments: WLHost - WebLinx Server address (string) WLPort - WebLinx Server control port (10501) plpdev - Device number on the control network (16-bit integer) plpport - Port on the device (16-bit integer) plpsys - System ID of the control network (16-bit integer)
  • Page 44 WebLinx host and port, and the destination Device, Port, and System as you would when using the IDK from an ASP script.

  • Page 45: Send_Commands For Ir/Serial/Data Ports

    WebLinx Programming Commands Send_Commands for IR/Serial/Data Ports The IR/Serial/Data Send_Commands listed in the following table generate control data for external device, and configure the IR/Serial/Data ports. Send_Commands for the IR/Serial/Data Ports CAROFF This command overrides active software settings. Disables carrier from...
  • Page 46 WebLinx Programming Commands Send_Commands for the IR/Serial/Data Ports (Cont.) CTON Syntax: Sets the IR pulse (single) "'CTON',<Time>" on time for each channel Variable: digit and IR functions. Time = 0-255 in tenths of a second. System default is 5 (.5 second). Time is stored in permanent memory.
  • Page 47 WebLinx Programming Commands Send_Commands for the IR/Serial/Data Ports (Cont.) PTON Syntax: Sets the IR power-on "’PTON’,<Time>" pulse time after a power- Variable: off pulse in increments of Time = 0 - 255; System default is 15 (1.5 seconds). Time is stored in permanent .10 seconds.
  • Page 48 WebLinx Programming Commands Send_Commands for the IR/Serial/Data Ports (Cont.) Syntax: Transmits the IR code in ’XCH [Channel]’ the format set with the Variable: XCHM mode command. Channel = 0 through 999 Mode 0 (default) Examples: SEND_COMMAND IR_1, 'XCH 3' Transmits the IR code as 3 enter...

  • Page 49: Troubleshooting

    Const.inc program. If they do match, make sure the WebLinx device number for the Central Con- troller and WebLinx Server link is not already assigned to another device on the bus. If it is, choose an unassigned device number and update the Axcess program and link settings.
  • Page 50 Problem Solution WebLinx Server No WebLinx Server icons appear on my The WebLinx Server is not running. Refer to desktop tray. the Getting Connected section on page 9 to start the WebLinx Server.The WebLinx Server is started but no system links are present.

This manual is also suitable for:

Weblinx 1.1

Table of Contents