<< Click to Display Table of Contents >> Manual > Device Connection Guide > PATLITE > Connection Procedure (Ethernet) > AirGrid WD-Z Type 2 |
About the connection example
Please see below for an example of connection settings for this driver.
Applicable models etc. |
explanation |
This is an example of connection settings with the WDR series.
|
Device List
The compatible devices are as follows (see here for how to view the device list).
device |
keyword |
explanation |
detail |
reading |
Writing |
Red Information |
RED |
Red lamp is on |
Off - 0 Lit - 1 Blink - 2 |
○ |
× |
Yellow Information |
YELLOW |
Yellow lamp is on |
○ |
× |
|
Green Information |
GREEN |
Green lamp is on |
○ |
× |
|
Blue Information |
BLUE |
Blue lamp is on |
○ |
× |
|
White Information |
WHITE |
White lamp status |
○ |
× |
|
Buzzer Information |
BUZZER |
Buzzer sound status |
Stop - 0 Consecutive - 1 Intermittent - 2 |
○ |
× |
MAC Address (WDT) |
MACADDR |
Shows the set MAC address |
Regardless of whether communication is in progress or interrupted, the value quality will be GOOD. |
○ |
× |
WDTMonitoring Information |
WDTMONITOR |
Communication status between WDR and WDT |
TRUE - Communicating FALSE - Communication lost |
○ |
× |
Communication Quality |
LQI |
Wireless communication path quality |
0 (lowest) to 255 (highest) |
○ |
× |
Transmission Mode |
TRANSMITMODE |
WDT transmission mode |
0 - Transmit on change mode 1 - Response Send Mode |
○ |
× |
Specify the WDT to be connected
When setting up communication with WDT, specify the MAC address of the WDT to connect to. Check the MAC address on the label on the WDT itself, or from the WDR side using the setting tool "WDS WIN01".
There are two ways to specify the MAC address: you can set it for each individual tag, or you can specify it collectively on a folder basis.
When specifying on a folder basis, specify the MAC address of the WDT to connect to in the WDT MAC address in the communication settings of the folder properties.
When using the MAC address of the folder communication settings, set the WDT MAC address in the communication settings of the tag properties to "0000000000000000" (16 zeros).
If you want to specify the MAC address of the WDT for each tag, specify the MAC address of the WDT to connect to in the WDT MAC address in the communication settings for the tag above.
Communication Mode
WDT has two modes: "change transmission mode" and "response transmission mode." Select the communication mode that best suits your situation.
Transmit on change mode
WDT sends signal lamp information immediately after the signal lamp status change occurs. Select this if you want to collect signal lamp information every time the signal lamp status changes.
Response Sending Mode
WDT sends signal lamp information after receiving a request for signal lamp information from the host PC. Select this if you want to periodically monitor and obtain the status of the signal lamp.
The transmission mode can be changed for each WDT using the setting tool "WDS-WIN01".
In the "transmission on change mode," if there are multiple signal lights and many transmitters whose signal light status changes frequently, the data communication load will be high, and issues such as data loss and frequent transmitter joining/leaving may occur.
In such cases, switch to "response transmission mode" and have the host side manage all the transmitters in order to request data, rather than having each transmitter send data individually. By sending and receiving data from transmitters in a group one at a time, the occurrence of data loss and communication failures can be reduced. However, in response transmission mode, data is obtained periodically regardless of changes in the transmitter, so the timing of value acquisition may be delayed depending on the number of connected devices. For details on communication modes, please refer to the device manufacturer's manual.
Time until communication is completed
The tag value will be updated after a certain time (up to 100 seconds) after the Server application is brought online.
This delay occurs because the entry sequence for the initial connection takes time.
If you want to check the communication status in the output log, check "Driver(Debug)" at the message source. For example, after going online, there will be a delay until the tag value is updated, so during that time you can check whether communication is normal. |