Moxa AWK-6222-EU-T [16/101] Communication testing

AWK-6222 User’s Manual Getting Started

2-4

NOTE

After you click Submit to apply changes, the web page will refresh, and then the string

“(Updated)” and a blinking reminder will be displayed on the upper-right corner of the page, as

illustrated below.

To make the changes effective, click Restart and then Save and Restart after you change the

settings. About 30 seconds are needed for the AWK-6222 to complete its restart process.

Step 5: Select the operation mode

By default, the AWK-6222’s operation mode is set to Wireless redundancy. You can change the

setting in Wireless Settings Æ Operation mode if you would like to use the Wireless bridge or

AP-Client mode instead. Detailed information about configuring the AWK-6222’s operation mode

can be found in Chapter 3.

Step 6: Test communications.

We will describe two test methods to make sure the network connection is established. Please refer

to the following section for more details.

Communication Testing

After installation, you can run a sample test to make sure the AWK-6222 and wireless connection

are functioning normally. The following sections explain two testing methods. Use the first

method if you are using only one AWK-6222 device, and use the second method if you are using

two or more AWK-6222s.

Testing one AWK-6222 with AP-Client Operation Mode

If you are only using one AWK-6222, you will need a second notebook computer equipped with a

WLAN card. Configure the WLAN card to connect to the AWK-6222 (NOTE: the default SSID is

MOXA_1), and change the IP address of the second notebook (B) so that it is on the same subnet

as the first notebook (A), which is connected to the AWK-6222.

After configuring the WLAN card, establish a wireless connection with the AWK-6222 and open a

DOS window on Notebook B. At the prompt, type

ping <IP address of notebook A>

and then press Enter (see the figure below). A “Reply from IP address …” response means the

communication was successful. A “Request timed out.” response means the communication failed.

In this case, recheck the configuration to make sure the connections are correct.