Mitsubishi Electric MELSEC iQ-R Series User manual

MELSEC iQ-R High Speed Data Logger Module
User's Manual (Application)
-RD81DL96
-SW1DNN-RDLUTL (High Speed Data Logger Module Tool)

1
SAFETY PRECAUTIONS
(Read these precautions before using this product.)
Before using this product, please read this manual and the relevant manuals carefully and pay full attention to safety to handle
the product correctly. If products are used in a different way from that specified by manufacturers, the protection function of
the products may not work properly.
The precautions given in this manual are concerned with this product only. For the safety precautions of the programmable
controller system, refer to the MELSEC iQ-R Module Configuration Manual.
In this manual, the safety precautions are classified into two levels: " WARNING" and " CAUTION".
Under some circumstances, failure to observe the precautions given under " CAUTION" may lead to serious
consequences.
Observe the precautions of both levels because they are important for personal and system safety.
Make sure that the end users read this manual and then keep the manual in a safe place for future reference.
WARNING Indicates that incorrect handling may cause hazardous conditions, resulting in
death or severe injury.
CAUTION Indicates that incorrect handling may cause hazardous conditions, resulting in
minor or moderate injury or property damage.

2
[Design Precautions]
WARNING
●Configure safety circuits external to the programmable controller to ensure that the entire system
operates safely even when a fault occurs in the external power supply or the programmable controller.
Failure to do so may result in an accident due to an incorrect output or malfunction.
(1) Emergency stop circuits, protection circuits, and protective interlock circuits for conflicting
operations (such as forward/reverse rotations or upper/lower limit positioning) must be configured
external to the programmable controller.
(2) When the programmable controller detects an abnormal condition, it stops the operation and all
outputs are:
• Turned off if the overcurrent or overvoltage protection of the power supply module is activated.
• Held or turned off according to the parameter setting if the self-diagnostic function of the CPU
module detects an error such as a watchdog timer error.
(3) All outputs may be turned on if an error occurs in a part, such as an I/O control part, where the
CPU module cannot detect any error. To ensure safety operation in such a case, provide a safety
mechanism or a fail-safe circuit external to the programmable controller. For a fail-safe circuit
example, refer to "General Safety Requirements" in the MELSEC iQ-R Module Configuration
Manual.
(4) Outputs may remain on or off due to a failure of a component such as a relay and transistor in an
output circuit. Configure an external circuit for monitoring output signals that could cause a
serious accident.
●In an output circuit, when a load current exceeding the rated current or an overcurrent caused by a
load short-circuit flows for a long time, it may cause smoke and fire. To prevent this, configure an
external safety circuit, such as a fuse.
●Configure a circuit so that the programmable controller is turned on first and then the external power
supply. If the external power supply is turned on first, an accident may occur due to an incorrect output
or malfunction.
●Configure a circuit so that the external power supply is turned off first and then the programmable
controller. If the programmable controller is turned off first, an accident may occur due to an incorrect
output or malfunction.
●For the operating status of each station after a communication failure, refer to manuals for the network
used. For the manuals, please consult your local Mitsubishi representative. Incorrect output or
malfunction due to a communication failure may result in an accident.
●When connecting an external device with a CPU module or intelligent function module to modify data
of a running programmable controller, configure an interlock circuit in the program to ensure that the
entire system will always operate safely. For other forms of control (such as program modification,
parameter change, forced output, or operating status change) of a running programmable controller,
read the relevant manuals carefully and ensure that the operation is safe before proceeding. Improper
operation may damage machines or cause accidents. When a Safety CPU is used, data cannot be
modified while the Safety CPU is in SAFETY MODE.
●Especially, when a remote programmable controller is controlled by an external device, immediate
action cannot be taken if a problem occurs in the programmable controller due to a communication
failure. To prevent this, configure an interlock circuit in the program, and determine corrective actions
to be taken between the external device and CPU module in case of a communication failure.

3
[Design Precautions]
[Design Precautions]
[Security Precautions]
WARNING
●Do not write any data to the "system area" and "write-protect area" of the buffer memory in the
module. Also, do not use any "use prohibited" signals as an output signal from the CPU module to
each module. Doing so may cause malfunction of the programmable controller system. For the
"system area", "write-protect area", and the "use prohibited" signals, refer to the user's manual for the
module used. For areas used for safety communications, they are protected from being written by
users, and thus safety communications failure caused by data writing does not occur.
●If a communication cable is disconnected, the network may be unstable, resulting in a communication
failure of multiple stations. Configure an interlock circuit in the program to ensure that the entire
system will always operate safely even if communications fail. Incorrect output or malfunction due to a
communication failure may result in an accident. When safety communications are used, an interlock
by the safety station interlock function protects the system from an incorrect output or malfunction.
CAUTION
●Do not install the control lines or communication cables together with the main circuit lines or power
cables. Doing so may result in malfunction due to electromagnetic interference. Keep a distance of
100mm or more between those cables.
●During control of an inductive load such as a lamp, heater, or solenoid valve, a large current
(approximately ten times greater than normal) may flow when the output is turned from OFF to ON.
Therefore, use a module that has a sufficient current rating.
●After the CPU module is powered ON or is reset, the time taken to enter the RUN status varies
depending on the system configuration, parameter settings, and/or program size. Design circuits so
that the entire system will always operate safely, regardless of the time.
●Do not power off the programmable controller or reset the CPU module while the settings are being
written. Doing so will make the data in the flash ROM and SD memory card undefined. The values
need to be set in the buffer memory and written to the flash ROM and SD memory card again. Doing
so also may cause malfunction or failure of the module.
●When changing the operating status of the CPU module from external devices (such as the remote
RUN/STOP functions), select "Do Not Open by Program" for "Opening Method" of "Module
Parameter". If "Open by Program" is selected, an execution of the remote STOP function causes the
communication line to close. Consequently, the CPU module cannot reopen the line, and external
devices cannot execute the remote RUN function.
WARNING
●To maintain the security (confidentiality, integrity, and availability) of the programmable controller and
the system against unauthorized access, denial-of-service (DoS) attacks, computer viruses, and other
cyberattacks from external devices via the network, take appropriate measures such as firewalls,
virtual private networks (VPNs), and antivirus solutions.

4
[Installation Precautions]
[Installation Precautions]
WARNING
●Shut off the external power supply (all phases) used in the system before mounting or removing the
module. Failure to do so may result in electric shock or cause the module to fail or malfunction.
CAUTION
●Use the programmable controller in an environment that meets the general specifications in the
MELSEC iQ-R Module Configuration Manual. Failure to do so may result in electric shock, fire,
malfunction, or damage to or deterioration of the product.
●To mount a module, place the concave part(s) located at the bottom onto the guide(s) of the base unit,
and push in the module until the hook(s) located at the top snaps into place. Incorrect interconnection
may cause malfunction, failure, or drop of the module.
●To mount a module with no module fixing hook, place the concave part(s) located at the bottom onto
the guide(s) of the base unit, push in the module, and fix it with screw(s). Incorrect interconnection
may cause malfunction, failure, or drop of the module.
●When using the programmable controller in an environment of frequent vibrations, fix the module with
a screw.
●Tighten the screws within the specified torque range. Undertightening can cause drop of the
component or wire, short circuit, or malfunction. Overtightening can damage the screw and/or module,
resulting in drop, short circuit, or malfunction. For the specified torque range, refer to the MELSEC iQ-
R Module Configuration Manual.
●When using an extension cable, connect it to the extension cable connector of the base unit securely.
Check the connection for looseness. Poor contact may cause malfunction.
●When using an SD memory card, fully insert it into the SD memory card slot. Check that it is inserted
completely. Poor contact may cause malfunction.
●Securely insert an extended SRAM cassette or a battery-less option cassette into the cassette
connector of the CPU module. After insertion, close the cassette cover and check that the cassette is
inserted completely. Poor contact may cause malfunction.
●Beware that the module could be very hot while power is on and immediately after power-off.
●Do not directly touch any conductive parts and electronic components of the module, SD memory
card, extended SRAM cassette, battery-less option cassette, or connector. Doing so can cause
malfunction or failure of the module.

5
[Wiring Precautions]
[Wiring Precautions]
WARNING
●Shut off the external power supply (all phases) used in the system before installation and wiring.
Failure to do so may result in electric shock or cause the module to fail or malfunction.
●After installation and wiring, attach a blank cover module (RG60) to each empty slot before powering
on the system for operation. Also, attach an extension connector protective cover*1 to each unused
extension cable connector as necessary. Directly touching any conductive parts of the connectors
while power is on may result in electric shock.
*1 For details, please consult your local Mitsubishi Electric representative.
CAUTION
●Individually ground the FG and LG terminals of the programmable controller with a ground resistance
of 100 ohms or less. Failure to do so may result in electric shock or malfunction.
●Use applicable solderless terminals and tighten them within the specified torque range. If any spade
solderless terminal is used, it may be disconnected when the terminal screw comes loose, resulting in
failure.
●Check the rated voltage and signal layout before wiring to the module, and connect the cables
correctly. Connecting a power supply with a different voltage rating or incorrect wiring may cause fire
or failure.
●Connectors for external devices must be crimped or pressed with the tool specified by the
manufacturer, or must be correctly soldered. Incomplete connections may cause short circuit, fire, or
malfunction.
●Securely connect the connector to the module. Poor contact may cause malfunction.
●Do not install the control lines or communication cables together with the main circuit lines or power
cables. Doing so may result in malfunction due to noise. Keep a distance of 100mm or more between
those cables.
●Place the cables in a duct or clamp them. If not, dangling cables may swing or inadvertently be pulled,
resulting in malfunction or damage to modules or cables. In addition, the weight of the cables may put
stress on modules in an environment of strong vibrations and shocks. Do not clamp the extension
cables with the jacket stripped. Doing so may change the characteristics of the cables, resulting in
malfunction.
●Check the interface type and correctly connect the cable. Incorrect wiring (connecting the cable to an
incorrect interface) may cause failure of the module and external device.
●Tighten the terminal screws or connector screws within the specified torque range. Undertightening
can cause drop of the screw, short circuit, fire, or malfunction. Overtightening can damage the screw
and/or module, resulting in drop, short circuit, fire, or malfunction.
●When disconnecting the cable from the module, do not pull the cable by the cable part. For the cable
with connector, hold the connector part of the cable. For the cable connected to the terminal block,
loosen the terminal screw. Pulling the cable connected to the module may result in malfunction or
damage to the module or cable.
●Prevent foreign matter such as dust or wire chips from entering the module. Such foreign matter can
cause a fire, failure, or malfunction.
●When a protective film is attached to the top of the module, remove it before system operation. If not,
inadequate heat dissipation of the module may cause a fire, failure, or malfunction.

6
[Wiring Precautions]
[Startup and Maintenance Precautions]
CAUTION
●Programmable controllers must be installed in control panels. Connect the main power supply to the
power supply module in the control panel through a relay terminal block. Wiring and replacement of a
power supply module must be performed by qualified maintenance personnel with knowledge of
protection against electric shock. For wiring, refer to the MELSEC iQ-R Module Configuration Manual.
●For Ethernet cables to be used in the system, select the ones that meet the specifications in the user's
manual for the module used. If not, normal data transmission is not guaranteed.
WARNING
●Do not touch any terminal while power is on. Doing so will cause electric shock or malfunction.
●Correctly connect the battery connector. Do not charge, disassemble, heat, short-circuit, solder, or
throw the battery into the fire. Also, do not expose it to liquid or strong shock. Doing so will cause the
battery to produce heat, explode, ignite, or leak, resulting in injury and fire.
●Shut off the external power supply (all phases) used in the system before cleaning the module or
retightening the terminal screws, connector screws, or module fixing screws. Failure to do so may
result in electric shock.

7
[Startup and Maintenance Precautions]
CAUTION
●When connecting an external device with a CPU module or intelligent function module to modify data
of a running programmable controller, configure an interlock circuit in the program to ensure that the
entire system will always operate safely. For other forms of control (such as program modification,
parameter change, forced output, or operating status change) of a running programmable controller,
read the relevant manuals carefully and ensure that the operation is safe before proceeding. Improper
operation may damage machines or cause accidents.
●Especially, when a remote programmable controller is controlled by an external device, immediate
action cannot be taken if a problem occurs in the programmable controller due to a communication
failure. To prevent this, configure an interlock circuit in the program, and determine corrective actions
to be taken between the external device and CPU module in case of a communication failure.
●Do not disassemble or modify the modules. Doing so may cause failure, malfunction, injury, or a fire.
●Use any radio communication device such as a cellular phone or PHS (Personal Handy-phone
System) more than 25cm away in all directions from the programmable controller. Failure to do so
may cause malfunction.
●Shut off the external power supply (all phases) used in the system before mounting or removing the
module. Failure to do so may cause the module to fail or malfunction.
●Tighten the screws within the specified torque range. Undertightening can cause drop of the
component or wire, short circuit, or malfunction. Overtightening can damage the screw and/or module,
resulting in drop, short circuit, or malfunction.
●After the first use of the product, do not perform each of the following operations more than 50 times
(IEC 61131-2/JIS B 3502 compliant).
Exceeding the limit may cause malfunction.
• Mounting/removing the module to/from the base unit
• Inserting/removing the extended SRAM cassette or battery-less option cassette to/from the
CPU module
• Mounting/removing the terminal block to/from the module
• Connecting/disconnecting the extension cable to/from the base unit
●After the first use of the product, do not insert/remove the SD memory card to/from the CPU module
more than 500 times. Exceeding the limit may cause malfunction.
●Do not touch the metal terminals on the back side of the SD memory card. Doing so may cause
malfunction or failure of the module.
●Do not touch the integrated circuits on the circuit board of an extended SRAM cassette or a battery-
less option cassette. Doing so may cause malfunction or failure of the module.
●Do not drop or apply shock to the battery to be installed in the module. Doing so may damage the
battery, causing the battery fluid to leak inside the battery. If the battery is dropped or any shock is
applied to it, dispose of it without using.
●Startup and maintenance of a control panel must be performed by qualified maintenance personnel
with knowledge of protection against electric shock. Lock the control panel so that only qualified
maintenance personnel can operate it.

8
[Startup and Maintenance Precautions]
[Operating Precautions]
[Disposal Precautions]
[Transportation Precautions]
CAUTION
●Before handling the module, touch a conducting object such as a grounded metal to discharge the
static electricity from the human body. Wearing a grounded antistatic wrist strap is recommended.
Failure to discharge the static electricity may cause the module to fail or malfunction.
●After unpacking, eliminate static electricity from the module to prevent electrostatic discharge from
affecting the module. If an electrostatically charged module comes in contact with a grounded metal
object, a sudden electrostatic discharge of the module may cause failure.
For details on how to eliminate static electricity from the module, refer to the following.
Antistatic Precautions Before Using MELSEC iQ-R Series Products (FA-A-0368)
●Use a clean and dry cloth to wipe off dirt on the module.
CAUTION
●When changing data and operating status, and modifying program of the running programmable
controller from an external device such as a personal computer connected to an intelligent function
module, read relevant manuals carefully and ensure the safety before operation. Incorrect change or
modification may cause system malfunction, damage to the machines, or accidents.
●Do not power off the programmable controller or reset the CPU module while the setting values in the
buffer memory are being written to the flash ROM in the module. Doing so will make the data in the
flash ROM and SD memory card undefined. The values need to be set in the buffer memory and
written to the flash ROM and SD memory card again. Doing so can cause malfunction or failure of the
module.
CAUTION
●When disposing of this product, treat it as industrial waste.
●When disposing of batteries, separate them from other wastes according to the local regulations. For
details on battery regulations in EU member states, refer to the MELSEC iQ-R Module Configuration
Manual.
CAUTION
●When transporting lithium batteries, follow the transportation regulations. For details on the regulated
models, refer to the MELSEC iQ-R Module Configuration Manual.
●The halogens (such as fluorine, chlorine, bromine, and iodine), which are contained in a fumigant
used for disinfection and pest control of wood packaging materials, may cause failure of the product.
Prevent the entry of fumigant residues into the product or consider other methods (such as heat
treatment) instead of fumigation. The disinfection and pest control measures must be applied to
unprocessed raw wood.

9
CONDITIONS OF USE FOR THE PRODUCT
(1) MELSEC programmable controller ("the PRODUCT") shall be used in conditions;
i) where any problem, fault or failure occurring in the PRODUCT, if any, shall not lead to any major or serious accident;
and
ii) where the backup and fail-safe function are systematically or automatically provided outside of the PRODUCT for the
case of any problem, fault or failure occurring in the PRODUCT.
(2) The PRODUCT has been designed and manufactured for the purpose of being used in general industries.
MITSUBISHI ELECTRIC SHALL HAVE NO RESPONSIBILITY OR LIABILITY (INCLUDING, BUT NOT LIMITED TO
ANY AND ALL RESPONSIBILITY OR LIABILITY BASED ON CONTRACT, WARRANTY, TORT, PRODUCT
LIABILITY) FOR ANY INJURY OR DEATH TO PERSONS OR LOSS OR DAMAGE TO PROPERTY CAUSED BY the
PRODUCT THAT ARE OPERATED OR USED IN APPLICATION NOT INTENDED OR EXCLUDED BY
INSTRUCTIONS, PRECAUTIONS, OR WARNING CONTAINED IN MITSUBISHI ELECTRIC USER'S, INSTRUCTION
AND/OR SAFETY MANUALS, TECHNICAL BULLETINS AND GUIDELINES FOR the PRODUCT.
("Prohibited Application")
Prohibited Applications include, but not limited to, the use of the PRODUCT in;
• Nuclear Power Plants and any other power plants operated by Power companies, and/or any other cases in which the
public could be affected if any problem or fault occurs in the PRODUCT.
• Railway companies or Public service purposes, and/or any other cases in which establishment of a special quality
assurance system is required by the Purchaser or End User.
• Aircraft or Aerospace, Medical applications, Train equipment, transport equipment such as Elevator and Escalator,
Incineration and Fuel devices, Vehicles, Manned transportation, Equipment for Recreation and Amusement, and
Safety devices, handling of Nuclear or Hazardous Materials or Chemicals, Mining and Drilling, and/or other
applications where there is a significant risk of injury to the public or property.
Notwithstanding the above restrictions, Mitsubishi Electric may in its sole discretion, authorize use of the PRODUCT in
one or more of the Prohibited Applications, provided that the usage of the PRODUCT is limited only for the specific
applications agreed to by Mitsubishi Electric and provided further that no special quality assurance or fail-safe,
redundant or other safety features which exceed the general specifications of the PRODUCTs are required. For details,
please contact the Mitsubishi Electric representative in your region.
(3) Mitsubishi Electric shall have no responsibility or liability for any problems involving programmable controller trouble and
system trouble caused by DoS attacks, unauthorized access, computer viruses, and other cyberattacks.

10
CONSIDERATIONS FOR USE
This section explains the following considerations.
Page 10 Considerations for network connection
Page 10 Considerations for performance/specifications
Page 11 Considerations for data logging, event logging, and report functions
Page 12 Considerations for other functions
Page 12 Considerations for accessing a high speed data logger module
Page 13 Considerations for security
Page 13 Considerations for using SD memory cards
Page 15 Considerations for using a redundant system
Page 15 Considerations for the recipe function
Considerations for network connection
■Mail server and FTP server connections
When immediately powering ON after powering OFF, connection to mail servers or FTP servers may fail.
Power the programmable controller OFF, wait several minutes then power it ON.
Considerations for performance/specifications
■Sequence scan time of the CPU module
When using the high speed data logger module, the CPU module sequence scan time may increase.
Design your system and programs keeping in mind this increase in sequence scan time of the CPU module.
■Network connection using Ethernet
• When connecting to Ethernet network, basically configure the communication route to the access target via Ethernet
(twisted pair) cables and hubs. Note that when accessing via wireless LAN (Wi-Fi) or router, an error such as timeout or
missing data occurs, and cannot be communicated properly depending on the status of the equipment (wireless LAN or
router) on the network or the access route.
• When the access to the high speed data logger module is overloaded, errors and missing data may occur. Creating logging
files, report files might take time, and communication with the module might not be possible. Reduce the load on the
Ethernet network which is connected to the high speed data logger module.
■Time handled on the high speed data logger module
Time handled on the high speed data logger module is the time on the CPU module.
For errors and the optimum timing for setting the time, refer to the following:
Page 90 Time Synchronization Function
MELSEC iQ-R High Speed Data Logger Module User's Manual (Startup)
■High speed sampling
The high speed sampling function is not supported by CPU modules on other stations via a network.

11
Considerations for data logging, event logging, and report functions
■Data logging, event logging, and report functions
• The data logging, event logging, and report functions are best effort functions. Since the processing time of a module varies
depending on the setting and the status of other devices, these functions may not perform at the set sampling interval. Run
the system by fully verifying the processing time of each function when constructing it. For processing time, refer to the
following:
(Page 344 Processing Time)
• If data logging function, event logging function, or report function are used, they affect the sequence scan time of the
access target CPU module. Run the system by verifying how the sequence scan time is affected when configuring the
system.
(Page 352 Influence on the sequence scan time)
• If exponential format is selected for the data output format with the data logging, event logging, or report setting, rounding
errors will occur in the range of the number of digits that exceed the number of digits set for the decimal part.
• If the result of the linear function transformation with the scaling function exceeds the maximum or minimum range of the
specified output format, the maximum or minimum value will be output in binary format. Therefore, when outputting in the
binary format, errors may occur in the output values.
• The file transfer/e-mail transmission via the file transfer function/e-mail function may take from a few seconds to tens of
seconds depending on the network line or transmission size. Target files may be deleted before file transfer/e-mail
transmission is completed depending on the settings. Review the file switching timing and the setting for the number of
saved files and lengthen the time until the file is deleted.
( Page 51 File switching timing)
• When a CSV file is opened with Excel, the date column format is displayed in the default setting of Excel. Set the cell
format as necessary.
• Since general sampling specified data and report current value data are sampled asynchronously with the sequence scan,
data separation may occur. If data separation must be prevented, set the number of device points sampled at one time to
less than the access units, or set the module to use high speed sampling.
■Data logging function
• When the number of device points to be sampled by the trigger logging function exceeds the access units and general
sampling is specified for the data sampling method, device values sampled in another sequence scan as the one where the
trigger occurred may be included in one data row. To avoid this, the number of device points that can be sampled at once
should be less than the access units or high speed sampling should be used. For the access units, refer to the following:
(MELSEC iQ-R High Speed Data Logger Module User's Manual (Startup))
• Immediately after switching the programmable controller system ON, if a trigger occurs before sampling the number of lines
of data before the trigger, the lines of the data before the trigger may be fewer than the specified number of lines.
• When triggers continuously occur with the trigger logging function, triggers may not be detected or the number of lines of
data specified before the trigger may not be output. For operation when triggers continuously occur, refer to the following:
(Page 29 Trigger logging function)
■Report function
• Immediately after switching the programmable controller system ON, if a creation trigger occurs when data does not exist in
the data logging file, an error occurs in the high speed data logger module. Configure and construct the system so that the
creation trigger occurs after data is saved in the data logging file.
• Report output takes time. Therefore, according to the data logging save setting, the data logging file including the data
when the creation trigger occurs, may be deleted before the report output is completed. In this situation, the specified
number of records worth of data is not output, and an error occurs in the high speed data logger module. Check the Point in
the following section when configuring and constructing the system.
(Page 74 Creation trigger function)
• When the creation triggers continuously occurred, they may not be detected. For operation when the creation trigger
continuously occurred, refer to the following:
(Page 74 Creation trigger function)

12
• When using Microsoft Excel 2010 (32-bit version), Microsoft Excel 2013 (32-bit version), Microsoft Excel 2016 (32-bit
version), Microsoft Excel 2019 (32-bit version/64-bit version), or Microsoft 365 (32-bit version/64-bit version), install Visual
Basic for Applications (abbreviated as VBA below). If VBA is not installed, the error message below will be displayed
when the "Layout setting" screen is started, and the layout settings cannot be configured.
"This workbook has lost its VBA Project, ActiveX Controls and any other programmability-related features."
• The saving format of a report file output by the report function is the xls format. Some of the functions added to Microsoft
Excel 2007 and later cannot be used.
• Microsoft Excel 2010 (64-bit version) is not supported.
• Microsoft Excel 2013 (64-bit version) is not supported.
• Microsoft Excel 2016 (64-bit version) is not supported.
Considerations for other functions
■Access target CPU setting
• When rewriting the settings in Configuration Tool, turning the power OFF and ON, or resetting a CPU module, a high speed
data logger module is prepared to communicate with an access target CPU module. Therefore, if a large number of access
target CPU modules are set, several minutes are required for this preparation.
• The following conditions may affect the general sampling, file transfer function, and e-mail function: a CPU module that
does not exist is set as an access target CPU module, or a high speed data logger module cannot communicate with the
access target CPU module temporarily because of the power interruption of access target CPU module or network failure.
Before using a high speed data logger module, make sure that the module can communicate with a CPU module set as an
access target.
■Time synchronization function
• If implementing the time synchronization with the CPU module, it will change the time of the high speed data logger
module. When the CPU module's time is changed, the high speed data logger module's time may be greatly changed.
• Since there is inaccuracy in the clock element of the CPU module and the high speed data logger module, the time may be
moved slightly forward or backward when the time is synchronized. Since changing the time of the high speed data logger
module affects the time stamp, as well as the following determination of the cycles and of the time: data logging, event
logging, and reports, configure the module to synchronize its time at the required minimum range.
Considerations for accessing a high speed data logger module
■Web browser operations and settings
• In the local area network (LAN) setting of the web browser, do not set a proxy server for the local address.
(MELSEC iQ-R High Speed Data Logger Module User's Manual (Startup))
■FTP server function
• Because of FTP client side application restrictions, if the user name or password is input incorrectly, end the FTP operation
and redo the FTP connection from the beginning. FTP may not operate correctly by reentering the correct user name or
password with the 'user' FTP command.
• The maximum number of simultaneous connections to the FTP server is 10. However, depending on the FTP client, it may
make multiple simultaneous connections, so an FTP client may not be able to login even if 10 clients are not connected. In
this situation, shutdown all the FTP clients, then restart and connect them.
• When transferring many files at once with FTP, a 426 error (data connection error) may occur. In this situation, split the files
into multiple parts then transfer them separately.
• When a web browser is used for FTP access, the user authentication screen may not be displayed due to the specification
of the web browser. In this case, enter the address of a high speed data logger module in the following format.
ftp://<user name>:<password>@<the address of a high speed data logger module or host name>/

13
• When a web browser is used for FTP access, data logging files, event logging files, report files, and recipe files may not be
opened directly due to the specification of the web browser. Make sure to open the files after saving them to a personal
computer.
• When a web browser is used for FTP access, due to the specification of the web browser, errors may not be displayed even
if the transfer failed when files are transferred to the SD memory card which does not have enough free space. Update the
display and check if the files are transferred normally.
• When a web browser is used for FTP access, a retry may be performed at user authentication failure due to the
specification of the web browser. Note that unintentional repeated entry of wrong passwords may lock the module.
• The following port numbers (communication protocol) are used for the FTP server function.
Port for transferring data: 20 (TCP/IP)
Port for controlling communications: 21 (TCP/IP)
■Replacement of an older version of a module
• When replacing an older version of a high speed data logger module, delete temporary internet files (caches) of a web
browser before accessing a newer version of the module.
■Connecting GX LogViewer
• The maximum number of connections for GX LogViewer to access the high speed data logger modules simultaneously is 2.
• The following port numbers (communication protocols) are used for the online function.
Connection via a hub: 49900, 49902 to 49906 (TCP/IP)
Direct connection: 49900 (UDP)
High speed data logger module search: 49901 (UDP)
■Connection with Configuration Tool
• Note that a module may be in an unintended status when operating it in multiple pieces of Configuration Tool at the same
time.
• The following port numbers (communication protocols) are used for the online function.
Connection via a hub: 49900, 49902 to 49906 (TCP/IP)
Direct connection: 49900 (UDP)
High speed data logger module search: 49901 (UDP)
Considerations for security
• Although the high speed data logger module supports basic authentication (account setting) using user names and
passwords, it does not completely protect the system from illegal access. Avoid accounts (user name, password) consisting
of simple alphanumeric characters only, and include some non-alphanumeric characters ($, &, ?) to create a complicated
user name and password.
Considerations for using SD memory cards
■SD memory card file/directory
• Do not create files (excluding module operating files and recipe files) or folders on the SD memory card with a personal
computer. If files or folders are created on the SD memory card with a personal computer, they may be deleted.
■SD memory card to be used
• Use SD memory cards manufactured by Mitsubishi Electric Corporation in the manual below. If any other SD memory cards
are used, a failure such as data corruption on the SD memory card or a system shutdown (module major error (error code:
2450H) occurs in the CPU module) may occur during an operation.
(MELSEC iQ-R High Speed Data Logger Module User's Manual (Startup))

14
■Turning the power OFF or resetting a CPU module
• When a CPU module is powered OFF or reset while writing data to an SD memory card, the processing to write data to the
SD memory card may not be completed. It may cause a loss of logging data during the processing, corruption of data in the
SD memory card that is being accessed, or occurrence of a file system error. The file is automatically recovered when the
high speed data logger module is powered ON again, but it will not succeed in some cases.
The operation, powering OFF or resetting the CPU module after stopping file access, should be considered. For the
important data, a periodic backup is recommended.
(MELSEC iQ-R High Speed Data Logger Module User's Manual (Startup))
■Removing or replacing an SD memory card
• Make sure to stop file access before ejecting or replacing the SD memory card.
(MELSEC iQ-R High Speed Data Logger Module User's Manual (Startup))
• Not following the procedure may cause a loss of logging data during processing, corruption of data in the SD memory card
that is being accessed, a file system error, or false recognition of the mounting status of the SD memory card.
(MELSEC iQ-R High Speed Data Logger Module User's Manual (Startup))
• If an error occurs on the SD memory card, refer to the following:
(Page 253 Troubleshooting on an SD memory card)
• High speed data logger module settings are saved to the SD memory card. Therefore, the high speed data logger module's
IP address returns to the initial status (192.168.3.3) when the SD memory card is not inserted in the module or when the
power is turned OFF to ON or the CPU module is reset, without the settings written to the SD memory card. When
necessary, read the current settings before ejecting the SD memory card and after replacing the card, promptly write those
settings to the new card.
■SD memory card capacity
• Access speed to the SD memory card is affected by the amount of saved files. In particular, access speed becomes
extremely slow when files are saved up to the capacity limit of the SD memory card. Use the SD memory card maintaining
10% or more free space on the card.
• A minimum size occupied by the files on the hard disk varies depending on the SD memory card capacity. Therefore, the
actual file size and the occupied file size on the hard disk may differ.
■SD memory card diagnostic time
• The high speed data logger module performs diagnostics (file recovery, etc.) of the inserted SD memory card contents at
the times listed below.
When powering OFF to ON or resetting the CPU module
When inserting an SD memory card while the power is ON
• The SD memory card diagnostic time takes longer when there are more files on the card. 100 files takes approximately 5
seconds, and 1000 files takes approximately 10 seconds.
• Saving many files on an SD memory card increases the following time. Delete unnecessary files.
Time until 'SD memory card status' (X1) rises
Time until a high speed data logger module starts processing ('Module READY' (X0) or 'Module operating status' (X5) rises)
■Formatting SD memory card
• Use the format function of Configuration Tool to format an SD memory card.
( Page 221 SD memory card diagnostics)
• Do not format an SD memory card using the format function of Windows.
• Do not reset the control CPU or turn the power OFF when formatting an SD memory card.
• High speed data logger module settings are saved to an SD memory card. Therefore, all settings are lost when formatting
the SD memory card. When necessary, read the current settings before formatting, and promptly write those settings after
formatting. The IP address of the high speed data logger module returns to the initial status (192.168.3.3) when turning the
power OFF to ON or when resetting the module without writing the settings to the SD memory card.

15
■SD memory card life (limit on writing)
• An SD memory card has a life (a limit on the number of times for writing data). For details, refer to the following:
(Page 420 SD Memory Card Life)
■RECIPE folder
• The maximum number of recipe files that can be stored in the RECIPE folder is 256. Storing large numbers of files in the
RECIPE folder causes a longer processing time for the following operations. Delete unnecessary files.
Displaying or operating the file browser
Displaying a file list of recipe execution operation
Recipe execution operation
• Do not store any files other than recipe files in the RECIPE folder.
■Write protect switch
• Make sure that the write protect switch of an SD memory card is in the unlocked position. When the write protect switch is
in the locked position, no files can be written to the SD memory card.
Considerations for using a redundant system
■Mountable base units
• A high speed data logger module must be mounted on an extension base unit*1 or a redundant extension base unit. It
cannot be mounted on the main base unit in a redundant system.
*1 Only the extension level 2 to 7 are available.
■Access target CPUs
• There are restrictions on accessible routes. For details, refer to the following:
(MELSEC iQ-R High Speed Data Logger Module User's Manual (Startup))
■Dedicated instructions
• When mounting a high speed data logger module to a process CPU (redundant mode), dedicated instructions cannot be
used. If a dedicated instruction is used, "Operation error (redundant function)" occurs in the process CPU (redundant
mode).
■Resetting a CPU module
• When mounting a high speed data logger module to a process CPU (redundant mode), reset CPU modules of both
systems for a function that requires resetting the CPU modules.
Considerations for the recipe function
■Recipe files
• For recipe file names, use the characters usable in file names and folder (directory) names only.
■Recipe execution operation
• Before performing the recipe execution operation, write the settings of a high speed data logger module in Configuration
Tool, then set the module operating status to "In operation". The module operating status can be checked in the "Module
Diagnostic" screen.
(Page 216 Module diagnostics)
• The recipe execution operation can be performed to the control CPU only. It cannot be performed to a CPU module on
another station.
• Do not power OFF or reset the CPU module during the recipe execution operation. The recipe file being edited may be
damaged. Power OFF or reset the CPU module after confirming the completion of the recipe execution operation.

16
INTRODUCTION
Thank you for purchasing the Mitsubishi Electric MELSEC iQ-R series programmable controllers.
This manual describes the functions, Configuration Tool, and troubleshooting to use the modules listed below.
Before using this product, please read this manual and the relevant manuals carefully and develop familiarity with the
functions and performance of the MELSEC iQ-R series programmable controller to handle the product correctly.
When applying the program examples provided in this manual to an actual system, ensure the applicability and confirm that it
will not cause system control problems.
Note that the menu names and operating procedures may differ depending on an operating system in use and its version.
When reading this manual, replace the names and procedures with the applicable ones as necessary.
Please make sure that the end users read this manual.
The program examples shown in this manual are the examples in which a high speed data logger module
(RD81DL96) is assigned to the input/output No. X/Y0 to X/Y1F unless otherwise specified. To use the
program examples shown in this manual, the input/output number assignment is required. For details on the
assignment of input/output number, refer to the following:
MELSEC iQ-R Module Configuration Manual
Relevant product
RD81DL96

17
CONTENTS
CONTENTS
SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
CONDITIONS OF USE FOR THE PRODUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
CONSIDERATIONS FOR USE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
RELEVANT MANUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
GENERIC TERMS AND ABBREVIATIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
CHAPTER 1 FUNCTION 23
1.1 Data Logging Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Target data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Sampling function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Continuous logging function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Trigger logging function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Trigger conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Period specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Scaling function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Save function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Data missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
1.2 Event Logging Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Sampling function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Period specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Scaling function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
E-mail notification function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Save function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
1.3 Report Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Target data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Creation trigger and current value data sampling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Period specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Scaling function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Save function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
1.4 Recipe Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Recipe file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Execution procedure of the recipe function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Operation at recipe execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
1.5 Security Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Access authentication function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
IP filter function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
1.6 Time Synchronization Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
1.7 Auto Logging Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
1.8 File Access Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
1.9 File Transfer Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
1.10 E-mail Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
1.11 Event History Registration Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
1.12 Free Space Adjustment Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

18
1.13 FTP Server Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
1.14 Self-diagnostic Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
1.15 Initialization Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
CHAPTER 2 HIGH SPEED DATA LOGGER MODULE CONFIGURATION TOOL 107
2.1 High Speed Data Logger Module Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Setting operations overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
2.2 Common Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Operations on wizard screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Data list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Device batch replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Data setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Importing global labels and common device comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
2.3 Project Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Creating a new project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Opening a project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Saving a project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Opening a Q-series high speed data logger module (QD81DL96) project . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Importing settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Exporting settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
2.4 Common Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Network setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Time synchronization setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Access target CPU setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
File transfer setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
E-mail setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Security setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Logging operation setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
SD memory card setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
2.5 Data Logging Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Data logging setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Logging type/file format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Sampling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Number of logging lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Unicode text output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Binary output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
CSV output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Finish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
2.6 Event Logging Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Event logging setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
File format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Sampling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Unicode text output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185