Device No.
Name
SD10297
Time setting function execution
time (Day of the week)
SD10298
Time setting function required
response time
SD10299
Time setting function (SNTP
client) execution
SD10320 to
Unlock failure count
SD10327
SD10338
MELSOFT connection TCP port
continuous unlock failure count
SD10339
FTP transmission port (TCP/IP)
continuous unlock failure count
SD10340
Direct connection with MELSOFT
continuous unlock failure count
SD10680
Open completion signal
SD10681
Open request signal
SD10682
Socket communications receive
status signal
SD10683
Initial status
SD10692
Predefined protocol ready
SD10710
Predefined protocol setting data
check area protocol number
SD10711
Predefined protocol setting data
check area setting type
APPX
160
Appendix 1 List of Special Device Applications and Assignments
Description
The day of the week which the time setting function is executed is stored in a binary code.
0: Sunday
1: Monday
2: Tuesday
3: Wednesday
4: Thursday
5: Friday
6: Saturday
When the communication fails, this device is not updated from the value stored previously.
A time required from sending the message to the SNTP server to receiving the response
and setting the time to the CPU module is stored.
0000H to FFFEH (Unit: ms)
If the value exceeds the above range, all the values are stored as FFFFH.
When the communication fails, this device is not updated from the value stored previously.
Executes the time setting function when b0 is turned on. (Only when the time setting
(SNTP client) is set to "Use" in the GX Works3.)
The function is not executed if b0 is turned on during execution of the time setting function.
Unlock failure counts are stored.
[SD10320] to [SD10327]: Connection No. 1 to No. 8
Unlock failure counts of the MELSOFT connection (via hub) are stored.
FTP transmission port (TCP/IP) continuous unlock failure count is stored.
Unlock failure counts of the MELSOFT connection (direct connection) are stored.
Open completion signal for each connection.
[b0] to [b7]: Connection No. 1 to No. 8
0: Closed or not open
1: Open completed
Open request signal for each connection.
[b0] to [b7]: Connection No. 1 to No. 8
0: No open request
1: Requesting open
Socket communication receive state signal for each connection.
[b0] to [b7]: Connection No. 1 to No. 8
0: Data not received
1: Data reception completed
Stores the status of the initial processing.
Initial normal completion status (b0)
0:
1: Initialization normal completion
Initial abnormal completion status (b1)
0:
1: Initialization abnormal completion
Stores the ready status of the protocol setting data.
0:
1: Ready
When a protocol setting data error is detected, stores the protocol number where the error
was detected.
Protocol is checked in order from smallest protocol number. The protocol number where
an error was detected first is stored.
0: No error
1 to 64: Protocol number
*1
65535: Cannot identify
0 is stored if an error is detected in the packet setting or element setting.
1 is stored if an error is detected in the protocol detailed setting. (Valid when protocol
number value is 1 to 128)
0: Packet setting or element setting
1: Protocol preferences
*1
65535: Cannot identify
R/W
R
R
R/W
R
R
R
R
R
R
R
R
R
R
R