Function Files: File Name File Identifier File Description HSC

Chapter 3
Function Files
This chapter describes controller function files. The chapter is organized as

follows:
• Overview on page 67
• Real-Time Clock Function File on page 68
• Memory Module Information Function File on page 72
• Base Hardware Information Function File on page 74
• Communications Status File on page 75
• Ethernet Communications Status File on page 90
• Input/Output Status File on page 97
Overview Function Files are one of the three primary file structures within the MicroLogix
1400 controller (Program Files and Data Files are the others). Function Files
provide an efficient and logical interface to controller resources. Controller
resources are resident (permanent) features such as the Real-Time Clock and
High-Speed Counter. The features are available to the control program through
either instructions that are dedicated to a specific function file, or via standard
instructions such as MOV and ADD. The Function File types are:
File Name File Identifier File Description
High-Speed Counter HSC This file type is associated with the High-Speed Counter function. See Using the High-Speed Counter
and Programmable Limit Switch on page 107 for more information.
Extended Pulse Train Output PTOX This file type is associated with the Pulse Train Output Instruction. See Pulse Train Outputs (PTOX)
Function File on page 145 for more information.
Extended Pulse Width PWMX This file type is associated with the Pulse Width Modulation instruction. See Pulse Width Modulation
Modulation (PWMX) Function File on page 159 for more information.
Selectable Timed Interrupt STI This file type is associated with the Selectable Timed Interrupt function. See Using the Selectable
Timed Interrupt (STI) Function File on page 302 for more information.
Event Input Interrupt EII This file type is associated with the Event Input Interrupt instruction. See Using the Event Input
Interrupt (EII) Function File on page 306 for more information.
Real-Time Clock RTC This file type is associated with the Real-Time Clock (time of day) function. See Real-Time Clock
Memory Module Information MMI This file type contains information about the Memory Module. See Memory Module Information
Base Hardware Information BHI This file type contains information about the controller’s hardware. See Base Hardware Information
Function File on page 74 for the file structure.
Communications Status File CS0 This file type contains information about the Communications with the controller. See
for Channel 0 Communications Status File on page 75 for the file structure.
Communications Status File CS2
for Channel 2
Rockwell Automation Publication 1766-RM001I-EN-P - June 2019 67

Chapter 3 Function Files
File Name File Identifier File Description

I/O Status File IOS This file type contains information about the controller I/O. See Input/Output Status File on page 97
for the file structure.
Ethernet Status File for ES1 The file type contains information about the Ethernet Communications with the controller.
Channel 1
LCD Information File LCD This file type is associated with the LCD screen, keypads, and trimpot.
Real-Time Clock The real-time clock provides year, month, day of month, day of week, hour,
minute, and second information to the Real-Time Clock (RTC) Function File in
Function File the controller.
The Real-Time Clock parameters and their valid ranges are shown in the table
below.
Real-Time Clock Function File

Feature Address Data Format Range Type User Program Access
YR - RTC Year RTC:0.YR word 1998…2097 status read/write
MON - RTC Month RTC:0.MON word 1…12 status read/write
DAY - RTC Day of Month RTC:0.DAY word 1…31 status read/write
HR - RTC Hours RTC:0.HR word 0…23 (military time) status read/write
MIN - RTC Minutes RTC:0.MIN word 0…59 status read/write
SEC - RTC Seconds RTC:0.SEC word 0…59 status read/write
DOW - RTC Day of Week RTC:0.DOW word 0…6 (Sunday to Saturday) status read-only
DS - Disabled RTC:0/DS binary 0 or 1 status read-only
BL - RTC Battery Low RTC:0/BL binary 0 or 1 status read-only
Writing Data to the Real-Time Clock
The RTC settings may be changed by either the user program, a write MSG
instruction from another MicroLogix controller, or the programming software.
Use the Copy Word (CPW) instruction to adjust the RTC settings within the
ladder logic as follows:
IMPORTANT A Major fault (44h) is generated if any of the data being written to the
RTC function file is invalid. For example, setting the Seconds to 61 or
setting the Day of Month to 32.
68 Rockwell Automation Publication 1766-RM001I-EN-P - June 2019

Function Files Chapter 3
An example write MSG from another MicroLogix controller to synchronize their

RTCs is shown here:
The programming screen is shown below:
When valid data is sent to the real-time clock from the programming device or
another controller, the new values take effect immediately. In RSLogix 500/
RSLogix Micro, click Set Date & Time in the RTC Function File screen to set the
RTC time to the current time on your PC.
The real-time clock does not allow you to load or store invalid date or time data.
TIP Use the Disable Clock button in your programming device to disable the
real-time clock before storing a module. This decreases the drain on the
battery during storage.
Real-Time Clock Accuracy
The following table indicates the expected accuracy of the real-time clock for
various temperatures.

Real-Time Clock Accuracy at Various Temperatures

Ambient Temperature Accuracy(1)
0°C (+32°F) -13…-121 seconds/month
+25°C (+77°F) +54…-54 seconds/month
+40°C (+104°F) +29…-78 seconds/month
+55°C (+131°F) -43…-150 seconds/month
(1) These numbers are worst case values over a 31 day month.
RTC Battery Operation

The real-time clock uses the same replaceable battery that the controller uses. The
RTC Function File features a battery low indicator bit (RTC:0/BL), which
shows the status of the replacement battery. When the battery is low, the
indicator bit is set (1). This means that the battery wire connector could be
disconnected or if the battery is connected, the battery may be ready to fail in the
next two weeks. In the latter case, the replacement battery needs to be replaced
with a new one. When the battery low indicator bit is clear (0), the battery level is
acceptable.
ATTENTION: Operating with a low battery indication for more

than 14 days may result in invalid RTC data if power is removed
from the controller.
RTA - Real Time Clock Instruction Type: output

Adjust Instruction Execution Time for the RTA Instruction
Controller When Rung Is:
RTA
True False
Real Time Clock Adjust MicroLogix 1400 999.8510 µs 0.4090 µs
The RTA instruction is used to synchronize the controllers Real-Time Clock

(RTC) with an external source. The RTA instruction will adjust the RTC to the
nearest minute. The RTA instruction adjusts the RTC based on the value of the
RTC Seconds as described below.
IMPORTANT The RTA instruction will only change the RTC when the RTA
rung is evaluated true, after it was previously false
(false-to-true transition). The RTA instruction will have no
effect if the rung is always true or false.
RTA is set:
• If RTC Seconds are less than 30, then RTC Seconds is reset to 0.

• If RTC Seconds are greater than or equal to 30, then the RTC Minutes are
incremented by 1 and RTC Seconds are reset to 0.
The following conditions cause the RTA instruction to have no effect on the
RTC data:
• RTC is disabled
• An external (via communications) message to the RTC is in progress when
the RTA instruction is executed. (External communications to the RTC
takes precedence over the RTA instruction.)
To re-activate the RTA instruction, the RTA rung must become false, and then
true.
TIP There is only one internal storage bit allocated in the system for
this instruction. Do not use more than one RTA instruction in your
program.
TIP You can also use a MSG instruction to write RTC data from one
controller to another to synchronize time. To send (write) RTC
data, use RTC:0 as the source and the destination.

Memory Module The controller has a Memory Module Information (MMI) File which is updated
with data from the attached memory module. At power-up or on detection of a
Information Function File memory module being inserted, the catalog number, series, revision, and type are
identified and written to the MMI file in the user program. If a memory module
is not attached, zeros are written to the MMI file.
The memory module function file programming screen is shown below:
The parameters and their valid ranges are shown in the table below.
MMI Function File Parameters

Feature Address Data Format Type User
Program
Access
FT - Functionality Type MMI:0.FT word (INT) status read-only
MP - Module Present MMI:0/MP binary (bit) status read-only
WP - Write Protect MMI:0/WP binary (bit) control read-only
FO - Fault Override MMI:0/FO binary (bit) control read-only
LPC - Program Compare MMI:0/LPC binary (bit) control read-only
LE - Load On Error MMI:0/LE binary (bit) control read-only
LA - Load Always MMI:0/LA binary (bit) control read-only
MB - Mode Behavior MMI:0/MB binary (bit) control read-only
FT - Functionality Type
The LSB of this word identifies the type of module installed:

• 1 = Memory Module (MM1)
MP - Module Present
The MP (Module Present) bit can be used in the user program to determine
when a memory module is present on the controller. This bit is updated once per
scan, provided the memory module is first recognized by the controller. To be

recognized by the controller, the memory module must be installed prior to

power-up or when the controller is in a non-executing mode. If a memory module
is installed when the controller is in an executing mode, it is not recognized. If a
recognized memory module is removed during an executing mode, this bit is
cleared (0) at the end of the next ladder scan.
WP - Write Protect
When the WP (Write Protect) bit is set (1), the module is write-protected and
the user program and data within the memory module cannot be overwritten
IMPORTANT Once the WP bit is set (1), it cannot be cleared. Only set this bit if
you want the contents of the memory module to become
permanent.
FO - Fault Override
The FO (Fault Override) bit represents the status of the fault override setting of
the program stored in the memory module. It enables you to determine the value
of the FO bit without actually loading the program from the memory module.
IMPORTANT The memory module fault override selection in the Memory

Module Information (MMI) file does not determine the controller’s
operation. It merely displays the setting of the user program’s Fault
Override bit (S:1/8) in the memory module.
See Fault Override At Power-Up on page 536 for more information.
LPC - Load Program Compare
The LPC (Load Program Compare) bit shows the status of the load program
compare selection in the memory module’s user program status file. It enables you
to determine the value without actually loading the user program from the
memory module.
See Memory Module Program Compare on page 540 for more information.
LE - Load on Error
The LE (Load on Error) bit represents the status of the load on error setting in
the program stored in the memory module. It enables you to determine the value
of the selection without actually loading the user program from the memory
module.
See Load Memory Module On Error Or Default Program on page 537 for more
information.

LA - Load Always
The LA (Load Always) bit represents the status of the load always setting in the
program stored in the memory module. It enables you to determine the value of
the selection without actually loading the user program from the memory
module.
See Load Memory Module Always on page 537 for more information.
MB - Mode Behavior
The MB (Mode Behavior) bit represents the status of the mode behavior setting
in the program stored in the memory module. It enables you to determine the
value of the selection without actually loading the user program from the
memory module.
See Power-Up Mode Behavior on page 537 for more information.
Base Hardware Information The base hardware information (BHI) file is a read-only file that contains a
description of the MicroLogix 1400 Controller.
Function File
Base Hardware Information Function File (BHI)
Address Description
BHI:0.CN CN – Catalog Number
BHI:0.SRS SRS – Series
BHI:0.REV REV – Revision
BHI:0.FT FT – Functionality Type

Communications Status File The Communications Status (CS) File is a read-only file that contains
information on how the controller communication parameters are configured
and status information on communications activity.
The communications status file uses:
Communications Status File Size

Controller Number of Word Elements
MicroLogix 1400 71 1-word elements
There are three Communications Status Files for each communications port.
Communications Status File CS0 and CS2 correspond to Channel 0 and
Channel 2 on the controller. Ethernet Communications Status File ES
corresponds to Channel 1 on the controller.
TIP You can use the Communications Status File information as a

troubleshooting tool for communications issues.
The data file is structured as shown below:
Communications Status File

Word Description Applies to Controller Details
on Page
0…5 General Channel Status Block MicroLogix 1400 75
6…22 DLL Diagnostic Counters Block MicroLogix 1400 77
23…42 DLL Active Node Table Block MicroLogix 1400 89
words 43…70 when using DF1 Full-Duplex, DF1 Half-Duplex, DH-485, or ASCII:
43 End of List Category Identifier Code (always MicroLogix 1400 --
0)
43…70 Reserved • MicroLogix 1400 --
words 43…70 when using Modbus RTU Slave, Master or DF1 Half-Duplex Master:
43…69 Modbus Slave Diagnostic Counters Block • MicroLogix 1400 83
70 End of List Category Identifier Code (always • MicroLogix 1400 --
0)
The following tables show the details of each block in the Communications
Status File.
General Status Block of Communications Status File
General Channel Status Block

Word Bit Description
0 - Communications Channel General Status Information Category Identifier Code
1 - Length
2 - Format Code


3 - Communications Configuration Error Code
4 0 ICP – Incoming Command Pending Bit
This bit is set (1) when the controller determines that another device has
requested information from this controller. Once the request has been
satisfied, the bit is cleared (0).
1 MRP – Incoming Message Reply Pending Bit
This bit is set (1) when the controller determines that another device has
supplied the information requested by a MSG instruction executed by this
controller. When the appropriate MSG instruction is serviced (during
end-of-scan, SVC, or REF), this bit is cleared (0).
2 MCP – Outgoing Message Command Pending Bit
This bit is set (1) when the controller has one or more MSG instructions
enabled and in the communication queue. This bit is cleared (0) when the
queue is empty.
3 SSB – Selection Status Bit
This bit indicates that the controller is in the System Mode. It is always set.
4 CAB – Communications Active Bit
This bit is set (1) when at least one other device is on the DH-485 network. If
no other devices are on the network, this bit is cleared (0).
5…14 Reserved
15 Communications Toggle Push Button Communications Defaults Active. This bit
is set (1) whenever Channel 0 is in the default communications mode. The bit is
cleared (0) when Channel 0 is in user configured communications mode.
5 0…7 Node Address – This byte value contains the node address of your controller
on the network.
8…15 Baud Rate – This byte value contains the baud rate of the controller on the
network.

Diagnostic Counter Block of Communications Status File
With RSLogix 500/RSLogix Micro version 8.10.00 and later, formatted displays
of the diagnostic counters for each configured channel are available under
Channel Status. These displays include a Clear button that allows you to reset the
diagnostic counters while monitoring them online with the programming
software.
TIP Clicking the Clear button while online monitoring Channel Status of
any channel will reset the channel status diagnostic counters for all
three channels to zero.
Diagnostic Counter Blocks are shown for:

• DH-485 (on page 77)
• DF1 Full-Duplex (on page 79)
• DF1 Half-Duplex Slave (on page 80)
• DF1 Half-Duplex Master (on page 81)
• DF1 Radio Modem (on page 82)
• Modbus RTU Slave (on page 83)
• Modbus RTU Master (on page 84)
• ASCII (on page 86)
• DNP3 (on page 86 )
DH-485 Diagnostic Counters Block

6 - Diagnostic Counters Category Identifier Code (always 2)
7 - Length (always 30)
8 - Format Code (always 0)
9 - Total Message Packets Received
10 - Total Message Packets Sent
11 0…7 Message Packet Retries
8…15 Retry Limit Exceeded (Non-Delivery)
12 0…7 NAK – No Memories Sent
8…15 NAK – No Memories Received
13 0…7 Total Bad Message Packets Received
8…15 Reserved
14…22 - Reserved


DF1 Full-Duplex Diagnostic Counters Block

9 0 CTS
1 RTS
2 Reserved
3 Reserved
4…15 Reserved
12 - Undelivered Message Packets
13 - ENQuiry Packets Sent
14 - NAK Packets Received
15 - ENQuiry Packets Received
16 - Bad Message Packets Received and NAKed
17 - No Buffer Space and NAK’ed
18 - Duplicate Message Packets Received
19…22 - Reserved

DF1 Half-Duplex Slave Diagnostic Counters Block

9 0 CTS
1 RTS
2 Reserved
3 Reserved
4…15 Reserved
13 - Message Packets Retried
15 - Polls Received
16 - Bad Message Packets Received
17 - No Buffer Space
19…22 - Reserved

DF1 Half-Duplex Master Diagnostic Counters Block

9 0 CTS
1 RTS
2 Reserved
3 Reserved
4…15 Reserved
14 - Reserved
15 - Polls Sent
17 - No Buffer Space, Received Packet Dropped
19 - Last Normal Poll List Scan
20 - Max. Normal Poll List Scan
21 - Last Priority Poll List Scan
22 - Max. Priority Poll List Scan

DF1 Radio Modem Diagnostic Counters Block

9 0 CTS
1 RTS
2 Reserved
3 Reserved
4…15 Reserved
13…15 - Reserved
17 - No Buffer Space, Received Packet Dropped
19…22 - Reserved

Modbus RTU Slave Diagnostic Counters Block (Data Link Layer)

9 0 CTS
1 RTS
2 Reserved
3 Reserved
4…15 Reserved
11 - Total Message Packets Received for This Slave
13 - Link Layer Error Count
14 - Link Layer Error Code
15…22 - Reserved
Modbus RTU Slave Diagnostic Counters Block (Presentation Layer)

46 - Pre-Send Time Delay
47 0…7 Node Address
8…15 Reserved
48 - Inter-Character Timeout
49 - RTS Send Delay
50 - RTS Off Delay
51 0…7 Baud Rate
8 and 9 Parity
10…15 Reserved
55 - Presentation Layer Error Code
56 - Presentation Layer Error Count
57 - Execution Function Error Code
58 - Last Transmitted Exception Code
59 - Data File Number of Error Request
60 - Element Number of Error Request
61 - Function Code 1 Message Counter

Modbus RTU Slave Diagnostic Counters Block (Presentation Layer)

Modbus RTU Master Diagnostic Counters Block (Data Link Layer)

9 0 CTS
1 RTS
2 Reserved
3 Reserved
4…15 Reserved
11 - Reserved
15…22 - Reserved
Modbus RTU Master Diagnostic Counters Block (Presentation Layer)


Modbus RTU Master Diagnostic Counters Block (Presentation Layer)

55 - ERR 1: Illegal Function
56 - Last Device Reporting ERR 1
57 - ERR 2: Illegal Data Address
59 - ERR 3: Illegal Data Value
61 - ERR 4: Slave Device Failure
62 - ERR 5: Acknowledge
63 - ERR 6: Slave Device Busy
64 - ERR 7: Negative Acknowledgement
65 - ERR 8: Memory Parity Error
66 - Non-Standard Response
67 - Last Device Reporting ERR 4 to ERR 8 or Non-Standard Response
68 and 69 - Reserved (always 0)

ASCII Diagnostic Counters Block

6 - DLL Diagnostic Counters Category Identifier code (always 2)
9 0 CTS
1 RTS
2 Reserved
3 Reserved
4…15 Reserved
10 0 Software Handshaking Status
1…15 Reserved
11 - Echo Character Count
12 - Received Character Count
13…18 - Reserved
19 - Bad Character Count
20…22 - Reserved
DNP3 Slave Diagnostic Counters Block (Data Link Layer)

6 - DLL Diagnostic Counters Category Identifier code
(2)
7 - Length: 30 (15 words to follow including format code)
8 - Counters Format Code: 11 - DNP3 Slave

DNP3 Slave Diagnostic Counters Block (Data Link Layer)

9 15…4 Reserved Modem Control Line States - Always zero
3 Channel 0 - DCD
Channel 2 - DCD
2 Reserved Modem Control Line States - Always zero
1 RTS
0 CTS
10 0 Total Message Packets Sent
11 - Total Message Packets Received for this node
12 - Total Packets Observed
18 - Reserved - Always zero

DNP3 Slave Diagnostic Counters Block (Application Layer)

52 - PL Diagnostic Counters Category Identifier Code (6))
54 - Category Block Format Code - 2
55 - Application Layer Error Code
56 - Application Layer Error Count
57 - Function Code that caused the last error
58 - Last Transmitted IIN in the response
59 - Data File Number of Error Request
60 - Element Number of Error Request
61 - Received Confirm Function Code Counter
62 - Received Read Function Code Counter
63 - Received Write Function Code Counter
64 - Received Etc Function Code Counter
65 - Transmitted Solicited Response Function Code Counter
66 - Transmitted Unsolicited Response Function Code Counter
67 - Number of events to be reported
68 - Transport layer error code
69 - Transport layer error count

Active Node Table Block of Communications Status File
Active Node Table Block

Word Description
23 Active Node Table Category Identifier Code (always 3)
24 Length:
• always 4 for DH-485
• always 18 for DF1 Half-Duplex Master
• always 0 for DF1 Full-Duplex, DF1 Half-Duplex Slave, Modbus RTU Slave, Modbus RTU Master, ASCII, and DNP3 Slave
25 Format Code (always 0)
26 Number of Nodes:
• always 32 for DH-485
• always 255 for DF1 Half-Duplex Master
• always 0 for DF1 Full-Duplex, DF1 Half-Duplex Slave, Modbus RTU Slave, Modbus RTU Master, ASCII, and DNP3 Slave
27 Active Node Table (DH-485 and DF1 Half-Duplex Master) – Nodes 0…15
(CS0:27/1 is node 1, CS0:27/2 is node 2, and so on)
This is a bit-mapped register that displays the status of each node on the network. If a bit is set (1), the corresponding node is active on
the network. If a bit is clear (0), the corresponding node is inactive.
28 Active Node Table (DH-485 and DF1 Half-Duplex Master) – Nodes 16…31
29 Active Node Table (DF1 Half-Duplex Master) – Nodes 32…47
…
42 Active Node Table (DF1 Half-Duplex Master) – Nodes 240…255

If you are using RSLogix 500/RSLogix Micro version 8.10.00 or higher, you can
view the active node table by clicking on “Processor Status” and then selecting the
tab for the configured channel.

Ethernet Communications The Ethernet Communications Status (ES) File is a read-only file that contains
information on how the controller Ethernet communication parameters are
Status File configured and status information on Ethernet communications activity.
The Ethernet communications status file uses 178 1-word elements.
TIP You can use the Ethernet Communications Status File

information as a troubleshooting tool for Ethernet
communications issues.
The data file is structured as:
Communications Status File

Word Description Applies to Controller Details
on Page
0…119 General Channel Status Block MicroLogix 1400 75
120…176 DLL Diagnostic Counters Block MicroLogix 1400 77
177 End of List Category Identifier Code (always 0) MicroLogix 1400 89
The following tables show the details of each block in the Ethernet
Communications Status File.
General Status Block of Ethernet Communications Status File

0 - Communications Channel General Status Information Category Identifier Code (1)
1 - Length: 236
2 - Format Code
3 - Communications Configuration Error Code


4 0 ICP – Incoming Command Pending Bit
This bit is set (1) when the controller determines that another device has requested information from this controller. Once the
request has been satisfied, the bit is cleared (0).
1 MRP – Incoming Message Reply Pending Bit
This bit is set (1) when the controller determines that another device has supplied the information requested by a MSG
instruction executed by this controller. When the appropriate MSG instruction is serviced (during end-of-scan, SVC, or REF),
this bit is cleared (0).
2 MCP – Outgoing Message Command Pending Bit
This bit is set (1) when the controller has one or more MSG instructions enabled and in the communication queue. This bit is
cleared (0) when the queue is empty.
3...4 Reserved – Always zero
5 SNMP Server Status
This bit is set (1) when the SNMP server is enabled. The cleared bit (0) means that the SNMP server is disabled.
6 HTTP Server Status
This bit is set (1) when the internal web server is enabled. The cleared bit (0) means that the internal web server is disabled.
7 SMTP Client Status
This bit is set (1) when the SMTP client (for email) is enabled. The cleared bit (0) means that the SMTP client is disabled.
8…15 Reserved – Always zero
(Series A)
8…11 Reserved – Always zero
(Series B)
12 Modbus TCP Status
(Series B This bit is set (1) when the Modbus TCP Server/Client feature is enabled. The cleared bit (0) means that the Modbus TCP
Server/Client is disabled.
13 DNP3 over IP Status
(Series B This bit is set (1) when the DNP3 over IP feature is enabled. The cleared bit (0) means that the DNP3 over IP feature is
disabled.
14 Reserved – Always zero
(Series B
15 Disable Ethernet/IP Incoming Connection Status
(Series B This bit is set (1) when the Ethernet/IP Incoming connection is not allowed. The cleared bit (0) means that the Incoming
connection is allowed.


5 0 Ethernet Port Link Status
This bit is set (1) when the Ethernet link is active.
1 Ethernet Port Connection Speed
This bit is valid when the Auto Negotiation function is enabled.
This bit indicates the speed of the link layer driver operating at Ethernet port:
• 0: 10 Mbps
• 1: 100 Mbps
2 Reserved – Always zero
3 Duplex Mode
This bit is valid when the Auto Negotiation function is enabled.
This bit indicates the duplex mode of the Ethernet port:
• 0: Half Duplex
• 1: Full Duplex
4 Auto Negotiate Status
This bit is set (1) when the Auto Negotiation function is enabled.
5 Forced Speed Mode Status
This bit set (1) when the Auto Negotiation function is disabled and the Ethernet port speed is 100Mbps.
6 Forced Duplex Mode Status
This bit set (1) when the Auto Negotiation function is disabled and the Ethernet port’s duplex mode is Full Duplex.
7 Reserved - Always zero
8 BOOTP Valid Flag (Default: 0, False)
This bit is set (1) when the appropriate BOOTP response has been received. If BOOTP Enable Flag in Ethernet Port
Communications Configuration File is set (1, Yes) and this flag is cleared (0, False), then network-related information is
invalid.
9 DHCP Valid Flag (Default: 0, False)
This bit is set (1) when the appropriate DHCP response has been received. If DHCP Enable Flag in Ethernet Port
Communications Configuration File is set (1, Yes) and this flag is cleared (0, False), then network-related information is
invalid.
10 BOOTP Status Flag
This bit is set (1) if BOOTP is selected as configuration method.
11 DHCP Status Flag
This bit is set (1) if DHCP is selected as configuration method.


5 12 Advertise 100 MB Full Duplex Flag
This bit indicates advertisement status if Auto negotiate enabled:
• 0: 100 MB Full Duplex was not advertised during auto negotiation
• 1: 100 MB Full Duplex was advertised during auto negotiation
13 Advertise 100 MB Half Duplex Flag
• 0: 100 MB Half Duplex was not advertised during auto negotiation
• 1: 100 MB Half Duplex was advertised during auto negotiation
14 Advertise 10 MB Full Duplex Flag
• 0: 10 MB Full Duplex was not advertised during auto negotiation
• 1: 10 MB Full Duplex was advertised during auto negotiation
15 Configuration End Flag
This bit is set (1) when the Ethernet boot-up sequence is completed, including IP address, gateway address, subnet mask and
and so on.
6…8 - Ethernet Hardware Address (6-byte string)
A unique Ethernet hardware address assigned to this processor.
9…10 - IP Address (in network byte order)
Internet address that is specified for this processor.
11…12 - Subnet Mask (in network byte order)
Subnet mask that is specified for this processor
13…14 - Gateway Address (in network byte order)
Gateway address that is specified for this processor
15…16 - Broadcast Address (in network byte order)
NOT SUPPORTED AT THIS TIME. The Broadcast Address is used in sending multicast messages. A Broadcast Address of all
zeros indicates that no broadcast address was configured. In this case, the network code chooses a valid broadcast address
when needed for that current subnet.
17…18 - Primary Name Server(in network byte order)
Primary Name Server that is specified for this processor.
19…20 - Secondary Name Server(in network byte order)
Secondary Name Server that is specified for this processor.
21…52 - Default Domain Name
Default domain name that is specified for this processor.
53…84 - SNMP Contact
Contact string that is specified for this processor.
85…116 - SNMP Location
Location string that is specified for this processor.
117 - Message Connection Timeout
The amount of time (in ms) allowed for a MSG instruction to establish a connection with the destination node. The MSG
Connection Timeout has a range of 250 ms...65,500 ms.
118 - Message Reply Timeout
The amount of time (in ms) that the MicroLogix 1400 processor waits for a reply to a command that it has initiated via a MSG
instruction. The MSG Reply Timeout has a range of 250 ms...65,500 ms.
119 - Inactivity Timeout
The amount of time (in minutes) that a MSG connection may remain inactive before it is terminated. The Inactivity Timeout
has a 1 minute resolution and a range of 1...65,500 minutes.

Diagnostic Counter Block of Communications Status File
With RSLogix 500/RSLogix Micro version 8.10.00 and later, formatted displays
of the diagnostic counters for Ethernet communications channel are available
under Channel Status. These displays include a Clear button that allows you to
reset the diagnostic counters while monitoring them online with the
programming software.
Ethernet Diagnostic Counters Block

120 - DLL Diagnostic Counters Category Identifier Code (always 2)
122 - Counters Format Code: Ethernet (always 0)
123 Low word RMON Rx Octets
124 (RMON_R_OCTETS)
High word
125 Low word RMON Tx Octets
126 (RMON_T_OCTETS)
High word
127 Low word RMON Rx Packets
128 (RMON_R_PACKETS)
High word
129 Low word RMON Tx Packets
130 (RMON_T_PACKETS)
High word
131 Low word Frames Transmitted with Excessive Collisions
132 (IEEE_T_EXCOL)
High word
133 Low word Frames Received with CRC Error
134 (IEEE_R_CRC)
High word
135 Low word Frames Received with Alignment Error
136 (IEEE_R_ALIGN)
High word
137 Low word Count of frames not counted correctly
138 (RMON_T_DROP)
High word
139 Low word Receive FIFO Overflow Count
140 (IEEE_R_MACERR)
High word
141 Low word Frames transmitted with Tx FIFO Under-run
142 (IEEE_T_MACERR)
High word
143 Low word Frames Transmitted with Single Collision
144 (IEEE_T_1COL)
High word
145 Low word Frames Transmitted with Multiple Collisions
146 (IEEE_T_MCOL)
High word
147 Low word Frames Transmitted with Deferral Delay
148 (IEEE_T_DEF)
High word
149 Low word Frames Transmitted with Late Collisions
150 (IEEE_T_LCOL)
High word

Ethernet Diagnostic Counters Block

151 Low word Frames Transmitted with Carrier Sense Errors
152 (IEEE_T_CSERR)
High word
153 Low word RMON Tx Collision Count
154 (RMON_T_COL)
High word
Ethernet Diagnostic Counters Block (continued)

155 Low word Total Commands Sent
156
High word
157 Low word Total Commands Received
158
High word

Ethernet Diagnostic Counters Block (continued)

159 Low word Total Replies Sent
160
High word
161 Low word Total Replies Received
162
High word
163 Low word Total Replies Sent with Error
164
High word
165 Low word Total Replies Received with Error
166
High word
167 Low word Total Replies Timed Out
168
High word

The last Port tab will show the current states of Ethernet communications port
according to word 5 of Ethernet Communications Status File.
Input/Output Status File The input/output status (IOS) file is a read-only file in the controller that
contains information on the status of the embedded and local expansion I/O.
The data file is structured as:
Input/Output Status File
Word Description
0 Embedded Module Error Code – Always zero
1…4 Expansion Module Error Code – The word number corresponds to the module’s slot number. See the I/O module’s documentation for specific
information. (MicroLogix 1400)

Function Files: File Name File Identifier File Description HSC

Uploaded by

Copyright:

Available Formats

Function Files: File Name File Identifier File Description HSC

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Function Files: File Name File Identifier File Description HSC

Uploaded by

Copyright:

Available Formats

Chapter 3

This chapter describes controller function files. The chapter is organized as

Rockwell Automation Publication 1766-RM001I-EN-P - June 2019 67

File Name File Identifier File Description

Real-Time Clock Function File

Writing Data to the Real-Time Clock

68 Rockwell Automation Publication 1766-RM001I-EN-P - June 2019

An example write MSG from another MicroLogix controller to synchronize their

The programming screen is shown below:

Real-Time Clock Accuracy

Rockwell Automation Publication 1766-RM001I-EN-P - June 2019 69

Real-Time Clock Accuracy at Various Temperatures

RTC Battery Operation

ATTENTION: Operating with a low battery indication for more

RTA - Real Time Clock Instruction Type: output

The RTA instruction is used to synchronize the controllers Real-Time Clock

70 Rockwell Automation Publication 1766-RM001I-EN-P - June 2019

Rockwell Automation Publication 1766-RM001I-EN-P - June 2019 71

The memory module function file programming screen is shown below:

MMI Function File Parameters

The LSB of this word identifies the type of module installed:

72 Rockwell Automation Publication 1766-RM001I-EN-P - June 2019

recognized by the controller, the memory module must be installed prior to

IMPORTANT The memory module fault override selection in the Memory

See Fault Override At Power-Up on page 536 for more information.

LPC - Load Program Compare

Rockwell Automation Publication 1766-RM001I-EN-P - June 2019 73

See Power-Up Mode Behavior on page 537 for more information.

74 Rockwell Automation Publication 1766-RM001I-EN-P - June 2019

The communications status file uses:

Communications Status File Size

TIP You can use the Communications Status File information as a

The data file is structured as shown below:

Communications Status File

General Status Block of Communications Status File

General Channel Status Block

Rockwell Automation Publication 1766-RM001I-EN-P - June 2019 75

General Channel Status Block

76 Rockwell Automation Publication 1766-RM001I-EN-P - June 2019

Diagnostic Counter Block of Communications Status File

Diagnostic Counter Blocks are shown for:

DH-485 Diagnostic Counters Block

Rockwell Automation Publication 1766-RM001I-EN-P - June 2019 77

78 Rockwell Automation Publication 1766-RM001I-EN-P - June 2019

DF1 Full-Duplex Diagnostic Counters Block

Rockwell Automation Publication 1766-RM001I-EN-P - June 2019 79

DF1 Half-Duplex Slave Diagnostic Counters Block

80 Rockwell Automation Publication 1766-RM001I-EN-P - June 2019

DF1 Half-Duplex Master Diagnostic Counters Block

Rockwell Automation Publication 1766-RM001I-EN-P - June 2019 81

DF1 Radio Modem Diagnostic Counters Block

82 Rockwell Automation Publication 1766-RM001I-EN-P - June 2019

Modbus RTU Slave Diagnostic Counters Block (Data Link Layer)

Modbus RTU Slave Diagnostic Counters Block (Presentation Layer)

Rockwell Automation Publication 1766-RM001I-EN-P - June 2019 83

Modbus RTU Slave Diagnostic Counters Block (Presentation Layer)

Modbus RTU Master Diagnostic Counters Block (Data Link Layer)

Modbus RTU Master Diagnostic Counters Block (Presentation Layer)

84 Rockwell Automation Publication 1766-RM001I-EN-P - June 2019