-SW1DNN-DLUTL-E (High Speed Data Logger Module Tool)
SAFETY PRECAUTIONS
CAUTION
Indicates that incorrect handling may cause hazardous conditions,
resulting in death or severe injury.
Indicates that incorrect handling may cause hazardous conditions,
resulting in medium or slight personal injury or physical damage.
WARNING
(Always read these precautions before using this equipment)
Before using this product, please read this manual and the relevant manuals introduced in this manual
carefully and pay full attention to safety to handle the product correctly.
Note that these precautions apply only to this product. For the safety precautions of the programmable
controller system, please read the User's Manual for the CPU module used.
In this manual, the safety instructions are ranked as 'WARNING' and 'CAUTION'.
Note that the CAUTION level may lead to a serious consequence according to the circumstances.
Always follow the instructions of both levels because they are important to personal safety.
Please save this manual to make it accessible when required and always forward it to the end user.
[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.
For the operating status of each station after a communication failure, refer to relevant manuals for
the network. Erroneous outputs and malfunctions may lead to accidents. Not doing so can cause an
accident due to false output or malfunction.
To maintain the safety of the programmable controller system against unauthorized access from
external devices via the network, take appropriate measures. To maintain the safety against
unauthorized access via the Internet, take measures such as installing a firewall.
A - 1
[Design precautions]
WARNING
When changing data of the running programmable controller from a peripheral connected to the
CPU module or from a personal computer connected to an intelligent function module or special
function module, configure an interlock circuit in the sequence program to ensure that the entire
system will always operate safely. For program modification and operating status change, read
relevant manuals carefully and ensure the safety before operation.
Especially in the above mentioned control operations that are performed from an external device to a
remote programmable controller, any problems on the programmable controller side may not be
dealt with promptly due to abnormal data communication. To prevent this, configure an interlock
circuit in the sequence program, and determine corrective actions to be taken between the external
device and CPU module in case of a communication failure.
Do not write any data in the "system area" of the buffer memory in the intelligent function module.
Also, do not use any "use prohibited" signals as an output signal from the programmable controller
CPU to the intelligent function module.
Doing so may cause malfunction of the programmable controller system.
CAUTION
Do not bundle the control wires and the communication cables with the main circuit and the power
wires, and do not install them close to each other. They should be installed at least 100 mm (3.94 in.)
away from each other. Failure to do so may generate noise that may cause malfunctions.
During registering each setting, do not power OFF the mounted module or reset the programmable
controller CPU.
Otherwise, data in the CompactFlash card will be undefined. Therefore, resetting and re-registering
data are required.
This may also cause a module failure or malfunctions.
A - 2
[Installation precautions]
CAUTION
Use the programmable controller in an environment that meets the general specifications in the
user's manual for the CPU module used. Using the programmable controller in any other operating
environments may cause electric shocks, fires or malfunctions, or may damage or degrade the
module.
While pressing the installation lever located at the bottom of module, insert the module fixing tab into
the fixing hole in the base unit until it stops. Then, securely mount the module with the fixing hole as
a supporting point.
If the module is not installed properly, it may cause the module to malfunction, fail or fall off.
Secure the module with screws especially when it is used in an environment where constant
vibrations may occur.
Be sure to tighten the screws using the specified torque. If the screws loose, it may cause the
module to short-circuit, malfunction or fall off. If the screws are tightened excessively, it may damage
the screws and cause the module to short-circuit, malfunction or fall off.
Before mounting/dismounting the module, be sure to shut off all phases of external power supply
used by the system.
Failure to do so may cause product damage.
Do not directly touch any conductive part or electronic component of the module.
This may cause the module to malfunction or fail.
Push the CompactFlash card into the CompactFlash card slot and install it securely.
After installing the CompactFlash card, check that it is inserted securely.
Failure to do so may cause malfunctions due to poor contact.
A - 3
[Wiring precautions]
CAUTION
Connectors for external connection must be crimped or pressed with the tool specified by the
manufacturer, or must be correctly soldered.
If the connection is incomplete, it may cause the module to short circuit, catch fire, or malfunction.
Install connectors securely to modules.
Make sure to place the communication and power cables to be connected to the module in a duct or
fasten them using a clamp. If the cables are not placed in a duct or fastened with a clamp, their
positions may be unstable or moved, and they may be pulled inadvertently.
This may damage the module and the cables or cause the module to malfunction because of faulty
cable connections.
When disconnecting the communication and power cables from the module, do not pull the cables
by hand.
When disconnecting a cable with a connector, hold the connector to the module by hand and pull it
out to remove the cable.
When disconnecting a cable connected to a terminal block, loosen the screws on the terminal block
first before removing the cable. If a cable is pulled while being connected to the module, it may
cause the module to malfunction or damage the module and the cable.
Be careful not to let any foreign matter such as wire chips get inside the module. They may cause
fire, as well as breakdowns and malfunctions of the module.
A protective sheet is pasted on the upper part of the module in order to prevent foreign matter such
as wire chips to get inside the module while wiring.
Do not remove this protective sheet during wiring work.
However, be sure to remove the protective sheet before operating the module to allow heat radiation
during operation.
A - 4
[Startup and maintenance precautions]
WARNING
Do not touch any terminal during power distribution.
Doing so may cause malfunctions.
Always switch OFF the external supply power used by the system in all phases before cleaning or
retightening terminal screws.
Failure to do so may cause a failure or malfunction of the module.
If the screws loose, it may cause the module to short-circuit, malfunction or fall off.
If the screws are tightened excessively, it may damage the screws and cause the module to shortcircuit, malfunction or fall off.
CAUTION
Do not disassemble or transform the module.
Doing so may cause a failure, malfunctions, personal injuries, and/or a fire.
Before mounting/dismounting the module, be sure to shut off all phases of external power supply
used by the system.
Failure to do so may cause product damage.
Do not install/remove the module to/from the base unit more than 50 times after the first use of the
product. (IEC 61131-2 compliant)
Failure to do so may cause malfunction.
Before handling a module, touch a grounded metal object to discharge the static electricity from your
body.
Failure to do so may cause a failure or malfunction of the module.
[Operating precautions]
WARNING
Ensure safety before controlling a running programmable controller (e.g. data modification).
Do not write any data in the "system area" of the buffer memory in the intelligent function module.
Also, do not use any "use prohibited" signals as an output signal from the programmable controller
CPU to the intelligent function module.
Doing so may cause malfunction of the programmable controller system.
[Disposal precautions]
CAUTION
Dispose of this product as an industrial waste.
A - 5
CONDITIONS OF USE FOR THE PRODUCT
(1) Mitsubishi 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 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'S USER, 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 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 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
representative in your region.
A - 6
REVISIONS
Correction
Addition
Correction
*The manual number is given on the bottom left of the back cover.
Print date*Manual numberRevision
Jun., 2009SH-080818ENG-AFirst edition
Jun., 2009SH-080818ENG-B
Oct., 2009SH-080818ENG-C
Section 2.2
Section 3.4.2, Section 11.4.9, Appendix 8
HOW TO USE THIS MANUAL, Section 1.1, Section 2.1.3, Section 2.1.4,
Section 2.5, Section 3.1.1, Section 3.4, Section 3.8, Section 4.2.3, Section 4.5,
Section 7.5.2, Section 9.1, Section 11.2.4, Section 11.2.6, Section 11.2.7,
Section 11.2.9, Section 11.3.4, Section 11.4 to 11.4.8, Section 11.5.1,
Section 11.5.4, Section 11.5.8 to 11.5.12, Section 11.5.15, Section 11.6.1,
Section 11.6.4, Section 11.6.6 to 11.6.8, Section 11.6.10, Section 11.6.13,
Section 11.7.1, Section 11.7.3 to 11.7.7, Section 12.3, Section 13.1 to 13.1.9,
Section 14.3.4, Section 14.10.2, Section 14.10.3, Section 15.5, Section 15.6,
Section 17.1.1, Section 17.1.2, Section 17.2, Section 17.3.2 to 17.3.5,
Section 17.3.8, Section 17.3.9, Appendix 4.1, Appendix 5
Section 3.4.2 to 3.4.15 changed to Section 3.4.3 to 3.4.16
Appendix 8 changed to Appendix 9
A - 7
Print date*Manual numberRevision
Addition
Correction
Deletion
Correction
Addition
Correction
Correction
CONDITIONS OF USE FOR THE PRODUCT, RELATED MANUALS
Section 3.4.9, Section 3.8, Section 7.2.1, Section 7.2.2, Section 10.5,
Section 10.6, Section 11.2.10, Section 11.3.4, Section 11.3.5, Section 11.7.5,
Section 13.1.10, Chapter 14, Section 15.6, Section 17.3.10, Appendix 10
PRECAUTIONS FOR USE, INTRODUCTION, HOW TO USE THIS MANUAL,
GENERIC TERMS AND ABBREVIATIONS,
DEFINITIONS AND DESCRIPTIONS OF TERMS, Section 1.1, Section 1.3,
Section 2.1.1, Section 2.2, Section 2.3, Section 2.4, Section 2.5, Section 3.1,
Section 3.2, Section 3.3.1, Section 3.3.2, Section 3.4, Section 3.4.12,
Section 3.4.14, Section 3.4.16, Section 3.5, Section 4.2.1, Section 4.2.2,
Section 4.5, Chapter 5, Section 5.1, Section 5.2.1 to 5.2.3, Section 5.4,
Section 5.4.1 to 5.4.3, Chapter 6, Section 7.2, Section 7.5.4, Section 8.2,
Section 8.4.4, Section 9.2, Section 9.5.3, Section 10.3, Section 11.2,
Section 3.4.9 to 3.4.16 changed to Section 3.4.10 to 3.4.17,
Section 3.8 changed to 3.9,
Section 5.2 to 5.3 changed to Section 5.1 to 5.2,
Section 11.3.4 changed to Section 11.3.6,
Section 11.7.5 to 11.7.8 changed to Section 11.7.6 to 11.7.9,
Section 15.6 changed to Section 15.7
PRECAUTIONS FOR USE, Section 10.5, Section 16.3, Section 18.3.8
Japanese Manual Version SH-080801-U
This manual confers no industrial rights or any rights of any other kind, nor does it confer any patent licenses.
Mitsubishi Electric Corporation cannot be held responsible for any problems involving industrial property rights which may
occur as a result of using the contents noted in this manual.
This section explains the precautions in the order listed below.
Network connection precautions
Performance/specification precautions
Data logging, event logging, and report functions precautions
Other function precautions
Precautions when accessing the high speed data logger module
Security precautions
CompactFlash card precautions
Precautions when using a redundant system
Recipe function precautions
Precautions when using Logging File Conversion Tool
(1) Mail server and FTP server connections
When immediately turning the power ON after turning the power OFF, connections to
mail servers or FTP servers may fail.
Turn the programmable controller OFF, wait several minutes then turn it ON.
(1) Programmable controller CPU sequence scan time
When using the high speed data logger module, the programmable controller CPU
sequence scan time may increase. Design your system and programs keeping in
mind this increase in sequence scan time.
CHAPTER 17 PROCESSING TIME
(2) 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 (Wi-Fi) or router) on the network or the access
route.
(3) Time handled on the high speed data logger module
Two types of times handled on the high speed data logger module are available.
Programmable controller CPU time
Time obtained by the SNTP server function
For errors and the timing of setting the time, refer to the following sections.
The high speed data sampling function is not compatible with other stations' CPUs
routing the network.
A - 11
(1) Data logging, event logging, and report functions
Data logging, event logging, and report functions precautions
(a) The data logging, event logging, and report functions of the high speed data
logger module are the best effort functions.
Since module processing time changes according to the settings and status of
other devices, it may not operate with the set data sampling interval. Run the
system by fully verifying the processing time of each function when constructing it.
For processing time, refer to the following chapter.
CHAPTER 17 PROCESSING TIME
(b) If data logging, event logging, or report functions are used, they have an affect on
the sequence scan time of the access target CPU. Run the system by fully
verifying the affect to the sequence scan time when constructing it. For the affect
to the sequence scan time, refer to the following section.
Section 17.3 Effect on Sequence Scanning Time
(c) 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.
(d) 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 is output in binary format. Therefore, when outputting in the binary
format, errors may occur in the output values.
(e) E-mail transmissions/file transfers via the saved file transfer function may take a
few seconds to tens of seconds depending on the network line/transmission size.
Target files may be deleted before e-mail transmission/file transfer completes
depending on the settings.
Review the file switching timing and the number of files saved setting and
lengthen the time until the file is deleted.
(f) When CSV files are opened with Excel, the date column's format is displayed in
Excel's default setting. Set the cell format as necessary.
(g) Since general data 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 data
sampling.
®
(h) When CSV files are opened with Microsoft
displayed depending on the number of the data setting or number of file switching
lines.
In this case, open the CSV files with Microsoft
Excel® 2003, all the data may not be
®
Excel® 2007 or later, or text editor.
A - 12
(2) Data logging function
(a) Immediately after switching the programmable controller system ON, if a trigger
occurs before sampling the number of lines of data before the trigger, the data
before the trigger may be a few lines less than the specified amount.
(b) When triggers continuously occur with the trigger logging function, triggers may
be discarded 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
section.
Section 7.3.2 Trigger logging
(3) Report function
(a) 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 are saved in the data logging file.
(b) 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 outputting the report has completed. In this situation, the data for
the specified number of records are not output, and an error occurs in the high
speed data logger module. Verify the points listed in the following section when
configuring and creating the system.
Section 9.3 Creation Trigger
(c) When creation triggers continuously occur, they may be discarded. For operation
when the creation trigger continuously occurs, refer to the following section.
Section 9.3 Creation Trigger
If VBA is not installed, the error message below is 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."
(e) The save format of the report file output by the report function is the xls format. A
®
portion of the functions added from Microsoft
(f) One of the following operating systems is required with installing Microsoft
®
Excel
2010 (32-bit version).
• Windows
• Windows Vista
• Windows
Note that Microsoft
®
XP Service Pack 3
®
Service Pack 1 or later
®
7 or later
®
Excel® 2010 (64-bit version) is not supported.
Excel® 2007 and later cannot be used.
®
(g) The following operating system is required with installing Microsoft
(32-bit version).
®
• Windows
Note that Microsoft
7 or later
®
Excel® 2013 (64-bit version) is not supported.
®
Excel® 2013
A - 13
(1) Access target CPU setting ( Section 11.4.3)
Other function precautions
(a) When rewriting the Configuration Tool settings, power OFF to ON, or resetting the
CPU module, the high speed logger module prepares to communicate with the
access target CPU. Therefore, if a large number of access target CPUs are set,
several minutes are required for this preparation.
(b) The following conditions may affect the general sampling, FTP transfer function,
and e-mail function: when the CPU which does not exist in the access target CPU
is set, or the high speed data logger cannot communicate with the access target
CPU temporary because of the power interruption of access target CPU or
network failure.
Use high speed data logger modules with the status that can communicate with
the CPU set as access target CPU.
( Section 3.4.8 General data sampling delay time area (address: 800 to 805)
Appendix 8.2 Processing time of FTP transfer function and e-mail function)
(2) Time synchronization function ( Section 10.1)
(a) If implementing synchronization with the programmable controller CPU or SNTP
server time, the high speed data logger module's time is changed. When the
programmable controller CPU's time is changed or when restored after
communicating with the SNTP server fails, the high speed data logger module's
time may be greatly changed.
(b) Since there is inaccuracy in the clock element in the programmable controller
CPU and high speed data logger module, the time may be moved slightly forward
or backward when the time is synchronized.
Since changing the high speed logger unit's time affects the data logging, event
logging, and report cycles, the determination of time, and the time stamp,
configure the module to synchronize its time as little as possible.
A - 14
(1) Web browser operations, settings
Precautions when accessing the high speed data logger module
In the local area network (LAN) setting of the Web browser, do not set a proxy server
for the local address. ( Section 5.3.1)
(2) FTP server function
(a) 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.
(b) 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.
(c) If transferring many files at once with FTP, a 426 (Data connection error) may
occur.
In this situation, split the files up over multiple transfers and retransfer them.
(d) When using Internet Explorer as an FTP client, the user authentication screen
may not be displayed because of the Internet Explorer specification.
To enable the high speed data logger module's access authentication function,
enter the address in the following format.
ftp://<user name>:<password>@<high speed data logger module's address or
hostname>/
(e) When using Internet Explorer as an FTP client, data logging files, event logging
files, report files, and recipe files may not be opened directly because of the
Internet Explorer specification. Open those files after saving them to a personal
computer.
(f) When using Internet Explorer as an FTP client, because of the Internet Explorer
specification, errors may not be displayed even if the transfer failed when files are
transferred to the CompactFlash card which does not have enough free space.
Update the display and check if the files are transferred normally.
(3) Replacing old version module with new one
When a high speed data logger module is replaced, make sure to delete the
temporary Internet files of Web browser (cache) before accessing the high speed data
logger module. ( Section 10.3 POINT)
(4) Connecting GX LogViewer
The maximum number of connections for GX LogViewer to access high speed data
logger modules simultaneously is 2.
A - 15
Although the high speed data logger module supports basic authentication (account
Security precautions
CompactFlash card precautions
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.
(1) CompactFlash card file/directory names
(a) Do not create files*1 or folders on the CompactFlash card with a personal
computer.
If files or folders are created on the CompactFlash card with a personal computer,
they may be deleted.
*1: Excluding module operating files and recipe files
(b) Do not store files with file name containing unusable characters to CompactFlash
card.
For usable characters in file names, refer to the following section.
Appendix 4.2 Characters usable in file names, folder (directory) names
(2) CompactFlash card to be used
Use CompactFlash cards listed in Section 2.3.
Section 2.3 Connection System Equipment
If any other CompactFlash cards are used, a failure such as a data corruption on a
CompactFlash card or a system shutdown (SP.UNIT DOWN occurs in the
programmable controller CPU) may occur during an operation.
(3) When turning OFF or resetting programmable controller CPU
When a programmable controller CPU is turned OFF or reset while writing data to a
CompactFlash card, the processing to write data to a CompactFlash card may not be
completed. It may cause a loss of logging data during the processing, corruption of
data in the CompactFlash card that is being accessed, or occurrence of a file system
error. The file is automatically repaired when the high speed data logger module is
turned ON again, but it will not succeed in some cases.
The operation, turning OFF or resetting the high speed data logger module after
stopping file access, should be considered. For the important data, create backups by
performing a backup operation such as saving data to other media.
Section 16.6 (1) Stopping file access
A - 16
(4) When ejecting or replacing the CompactFlash card
(a) Be sure to stop file access before ejecting or replacing the CompactFlash card.
Section 16.5 Operations for Ejecting and Reinserting CompactFlash Card
(b) Not following the procedure shown in Section 16.5 may cause a loss of logging
data during processing, corruption of data on the CompactFlash card while
accessing, or a file system error.
(c) If an error occurs on the CompactFlash card, refer to the following section.
Section 18.3.8 Troubleshooting related to data management, CompactFlash
cards
(d) High speed data logger module settings are saved to the CompactFlash card.
Therefore, the high speed logger module's IP address returns to the initial status
(192.168.3.3) without a CompactFlash card inserted in the module or when
turning the power OFF/ON or resetting the programmable controller CPU without
the settings written to the CompactFlash card. When necessary, read the current
settings before ejecting the CompactFlash card and after replacing the card,
promptly write those settings to the new card.
(5) CompactFlash card capacity
(a) Access speed to the CompactFlash card is affected by the amount of saved files.
In particular, access speed becomes extremely slow when saving files up to the
capacity limit of the CompactFlash card.
Use the CompactFlash card maintaining 10% or more free space on the card.
(b) A minimum size of the occupied file on the hard disk varies depending on the
CompactFlash card capacity. Therefore, the actual file size and the occupied file
size on the hard disk may differ.
(6) CompactFlash card diagnostic time
(a) The high speed data logger module performs a diagnostics (file recovery, etc.) of
the inserted CompactFlash card contents at the times listed below.
When power OFF to ON, resetting the CPU module
Inserting a CompactFlash card when powered ON
(b) The CompactFlash card diagnostic time takes longer when there are more files on
the card.
100 files takes approximately 5 seconds, 1000 files takes approximately 10
seconds.
(c) When many files are saved on the CompactFlash card, the following operations
require longer time. Delete unnecessary files.
CompactFlash card status (X1) startup time
Time before the high speed data logger module can start processing
(Module READY (X0) and module operating status (X5) startup time)
A - 17
(7) CompactFlash card format
Precautions when using a redundant system
(a)
To format a CompactFlash card, use the high speed data logger module format function.
Section 13.1.6 CompactFlash card diagnostics
®
(b) Do not format a CompactFlash card using the Windows
(c) Do not reset the control CPU or turn the power OFF when formatting a
CompactFlash card.
(d) High speed data logger module settings are saved to the CompactFlash card.
Therefore, all settings are lost when formatting a card. When necessary, read the
current settings before formatting and promptly write those settings after
formatting. The high speed logger module's IP address returns to the initial status
(192.168.3.3) when turning the power OFF/ON or resetting the programmable
controller CPU without writing the settings to the CompactFlash card.
format function.
(8) CompactFlash card life duration (a limit for writing data)
The CompactFlash card has a life duration (a limit for writing data).
For details, refer to the following section.
Section 16.7 CompactFlash Card Life Duration
(9) About RECIPE folder
(a) A maximum number of recipe files that can be stored in the RECIPE folder is 256.
Storing large number of files in the RECIPE folder causes a longer processing
time for following operations. Delete unnecessary files.
Displaying or operating the file browser
Displaying a file list of recipe execution operation
Recipe execution operation
(b) Do not store files other than recipe files in the RECIPE folder.
(1) Mountable base unit
When using the high speed data logger module in a redundant system, be sure to
mount the module to the extension base unit for CPU/redundant power supply.
The high speed data logger module cannot be mounted to the main base unit in a
redundant system.
(2) "Access target CPU setting"
(a) When the high speed data logger module is mounted to the Redundant CPU, it
can only access the own station CPU. It cannot access CPUs of other stations.
(b) When the high speed data logger module is mounted to a unit other than the
Redundant CPU, it cannot access the Redundant CPU of other stations.
(3) Dedicated instructions
When the high speed data logger module is mounted to the Redundant CPU, the
dedicated instructions cannot be used. If any of those instructions are used, an
"OPERATION ERROR" occurs in the Redundant CPU.
A - 18
(1) Recipe files
Recipe function precautions
Precautions when using Logging File Conversion Tool
(a) When a recipe file to which 253 or more records are set is opened in Microsoft®
®
2003, the entire file cannot be displayed. Edit the data using Microsoft®
Excel
®
Excel
2007 or later, text editor or recipe editor.
(b) For recipe file names, use the characters usable in file names and folder
(directory) names only. ( Appendix 4.2)
(2) Recipe execution operation
(a) Before performing the recipe execution operation, write the high speed data
logger module settings using the Configuration Tool, and set the module operating
status to "In operation".
The module operating status can be checked on the <<Module diagnostics>> tab
of the "Diagnostics" screen.
Section 13.1.1 Module diagnostics
(b) The recipe execution operation is performed to an own station CPU only. It cannot
be performed to other stations' CPUs.
(c) Do not power OFF or reset the programmable controller CPU during the recipe
execution operation. The recipe file being edited may be damaged.
Power OFF or reset the programmable controller CPU after confirming the
completion of the recipe execution operation.
(1) Logging files that can be converted
The Logging File Conversion Tool can convert only binary format logging files created
by high speed data logger module to CSV format logging files.
Other binary files cannot be converted.
(2) Conversion processing of float type
When the binary output format is [Float (single precision)] or [Float (double
precision)], the following error may occur between CSV file data values that are
created in the Conversion Tool and the high speed data logger module.
• Float (single precision):
Significant figures of 7th and later digits (the last digit for 7 significant figures)
• Float (double precision):
Significant figures of 15th and later digits (the last digit for less than 15 significant
figures)
A - 19
Remark
INTRODUCTION
Thank you for purchasing the Mitsubishi MELSEC-Q series/MELSEC-L series general purpose
programmable controllers.
Before using the product, please read this manual and the relevant manuals carefully and develop familiarity
with the functions and performance of the programmable controller to handle the product correctly.
RELATED MANUALS
The manuals related to this product are shown below.
Refer to the following tables when ordering required manuals.
(1) CPU module user's manual
Manual name
<Manual number, Model code>
QCPU User's Manual
(Hardware Design, Maintenance and Inspection)
<SH-080483ENG, 13JR73>
Qn(H)/QnPH/QnPRHCPU User's Manual
(Function Explanation, Program Fundamentals)
<SH-080808ENG, 13JZ28>
QnUCPU User's Manual
(Function Explanation, Program Fundamentals)
<SH-080807ENG, 13JZ27>
MELSEC-L CPU Module User's Manual
(Function Explanation, Program Fundamentals)
<SH-080889ENG, 13JZ35>
C Controller Module User's Manual
(Hardware Design, Function Explanation)
<SH-080766ENG, 13JZ17>
Specifications of the hardware (CPU modules, power supply modules, base units,
batteries, and memory cards), system maintenance and inspection, and
troubleshooting.
Explains the programming methods, devices, and functions of Qn(H)/QnPH/
QnPRHCPU module.
Explains the programming methods, devices, and functions of QnUCPU module.
Explains the programming methods, devices, and functions of LCPU module.
Explains the programming methods, and functions of C controller module.
Description
(2) Operating manual
Manual name
<Manual number, Model code>
GX LogViewer Version 1 Operating Manual
<SH-080915ENG, 13JU68>
GX Works2 Version 1 Operating Manual
(Common)
<SH-080779ENG, 13JU63>
GX Developer Version 8 Operating Manual
Manuals in printed form are sold separately for single purchase. Order a manual
by quoting the manual number (model code) listed in the table above.
Description
Explains the system configuration, functions, and operating methods of GX
LogViewer.
Explains the system configuration of GX Works2 and the functions common to
Simple project and Structured project such as parameter setting, operation method
for the online function.
Explains the methods for programming, printing, monitoring, and debugging in GX
Developer.
Description
Explains the details of instructions used in programming.
A - 20
CONTENTS
SAFETY PRECAUTIONS ................................................................................................................................. A - 1
CONDITIONS OF USE FOR THE PRODUCT..................................................................................................A - 6
REVISIONS....................................................................................................................................................... A - 7
PRECAUTIONS FOR USE ............................................................................................................................ A - 11
INTRODUCTION............................................................................................................................................. A - 20
RELATED MANUALS .....................................................................................................................................A - 20
CONTENTS .................................................................................................................................................... A - 21
COMPLIANCE WITH THE EMC AND LOW VOLTAGE DIRECTIVES.......................................................... A - 29
HOW TO USE THIS MANUAL....................................................................................................................... A - 30
GENERIC TERMS AND ABBREVIATIONS................................................................................................... A - 32
DEFINITIONS AND DESCRIPTIONS OF TERMS ........................................................................................ A - 34
PACKING LIST .............................................................................................................................................. A - 35
3.2Accessible Routes and Devices ...................................................................................................... 3 - 7
3.3I/O Signals for the Programmable Controller CPU ........................................................................ 3 - 18
A - 21
3.3.1I/O signal list ........................................................................................................................... 3 - 18
3.3.2I/O signal details ..................................................................................................................... 3 - 20
Appendix 10Setting information CSV File Format .................................................................................App - 22
Appendix 11FTP Transfer Directory Configuration................................................................................App - 64
Appendix 12Sampling Processes of High Speed Data Logger Module ................................................App - 66
Appendix 12.1 Data changes between data sampling processes .....................................................App - 66
Appendix 12.2 Detecting data condition establishment.....................................................................App - 66
INDEX Index - 1 to Index - 2
WARRANTY
A - 28
COMPLIANCE WITH THE EMC AND LOW VOLTAGE DIRECTIVES
To configure a system meeting the requirements of the EMC and Low Voltage Directives
when incorporating the Mitsubishi programmable controller (EMC and Low Voltage
Directives compliant) into other machinery or equipment, refer to Chapter 4 "EMC AND
LOW VOLTAGE DIRECTIVES" in the "Safety Guidelines" included with the CPU module
or the base unit used.
The CE mark, indicating compliance with the EMC and Low Voltage Directives, is printed
on the rating plate of the programmable controller.
For the compliance of this product with the EMC and Low Voltage Directives, refer to
Section 4.1.3 "Cables" in Chapter 4 "EMC AND LOW VOLTAGE DIRECTIVES" of the
"Safety Guidelines" included with the CPU module or the base unit used.
A - 29
POINT
Remark
Displaying a chapter title
Index on the right of a page
clears the chapter of the page.
Displaying a section title
The section in which the open page
is included is clear.
Displaying a reference
Reference in this manual and
reference manual are shown
with .
Describes the operating procedure of
the function.
Describes the operating screen when
using the function.
Describes the screen displayed when
using the function.
Setting screen
Operating procedure
Screen display
*
HOW TO USE THIS MANUAL
The above is different from the actual page as it is provided for explanation only.
In addition, this manual provides the following explanations.
Explains matters to be made particularly aware of, functions or other information
related to the description on that page.
A - 30
Provides references related to the description on that page and convenient
information.
Additionally, lists, like the one below, which explain operation methods indicate that any of
the operations can be performed.
(Example)
Operation method
• [Event] [Event Properties]
• Right click on the event list and select [Event Properties].
The following table shows the definitions and descriptions of the terms used in this
manual.
No. NotationDescriptionExample
-
[ ]Menu name on menu bar[Project]
Toolbar icon
<< >>Tab name on screen<<Module diagnostics>>
" "Item name on screen"Stop"
Button on screen
Keyboard key
Ctrl
A - 31
GENERIC TERMS AND ABBREVIATIONS
Unless otherwise specified, this manual uses the following generic terms and
abbreviations to explain the QD81DL96 high speed data logger module and high speed
data logger module tool (SW1DNN-DLUTL-E).
Generic term/
abbreviation
High speed data logger
module
High speed data logger
module tool
Configuration Tool
Conversion Tool
GX LogViewerAbbreviation for GX LogViewer Version 1 (SW1DNN-VIEWER-E).
GX Works2Abbreviation for GX Works2 Version 1 (SWnDNC-GXW2-E).
GX Developer
Programming toolGeneric term for GX Works2 and GX Developer.
Basic model QCPUGeneric term for Q00J, Q00, and Q01.
High Performance model
QCPU
Process CPUGeneric term for Q02PH, Q06PH, Q12PH, and Q25PH.
Redundant CPUGeneric term for Q12PRH and Q25PRH.
Universal model QCPU
QnUDE(H)CPU
High-speed Universal
model QCPU
QCPU(Q mode)
LCPUGeneric term for L02S, L02S-P, L02, L02-P, L06, L06-P, L26, L26-P, L26-BT, and L26-PBT.
C Controller moduleGeneric term for Q12DCCPU-V, Q24DHCCPU-V and Q24DHCCPU-LS.
Built-in Ethernet port QCPU Generic term for QnUDE(H)CPU and High-speed Universal model QCPU.
Ethernet Built-in CPUGeneric term for Built-in Ethernet port QCPU and LCPU.
Q series-compatible C24Generic term for QJ71C24, QJ71C24-R2, QJ71C24N, QJ71C24N-R2, and QJ71C24N-R4
Q series-compatible E71Generic term for QJ71E71, QJ71E71-B2, QJ71E71-B5, and QJ71E71-100.
Ethernet moduleGeneric term for Q series-compatible E71 and QJ71E71-100.
Ethernet communications
CC-Link IE ControlAbbreviation for CC-Link IE Controller Network.
CC-Link IE FieldAbbreviation for CC-Link IE Field Network.
CC-Link IEGeneric term for CC-Link IE Controller Network and CC-Link IE Field Network.
MELSECNET/HAbbreviation for MELSECNET/H network system.
CC-LinkAbbreviation for Control & Communication Link.
Windows® XP
MELSEC-Q Series-compatible QD81DL96 high speed data logger module
Generic term for the high speed data logger module Configuration Tool (model: SW1DNN-DLUTL).
Abbreviation for the high speed data logger module Configuration Tool.
This tool configures and maintains the high speed data logger module.
The Configuration Tool is built-in to the high speed data logger module.
The Configuration Tool is included with the high speed data logger module tool.
Abbreviation for the Logging File Conversion Tool.
This tool converts binary format logging files to CSV format logging files.
The Conversion Tool is included with the high speed data logger module tool.
Generic product name for model names SWnD5C-GPPW-E, SWnD5C-GPPW-EA,
SWnD5C-GPPW-EV, and SWnD5C-GPPW-EVA. (n = Version 0 or later.)
- A designates a multiple-license product; -V designates a version upgraded product.
Generic term for Q02, Q02H, Q06H, Q12H, and Q25H.
Generic term for Q00UJ, Q00U, Q01U, Q02U, Q03UD, Q03UDE, Q03UDV, Q04UDH, Q04UDEH,
Q04UDV, Q06UDH, Q06UDEH, Q06UDV, Q10UDH, Q10UDEH, Q13UDH, Q13UDEH, Q13UDV,
Q20UDH, Q20UDEH, Q26UDH, Q26UDEH, Q26UDV, Q50UDEH, and Q100UDEH.
Generic term for Q03UDE, Q04UDEH, Q06UDEH, Q10UDEH, Q13UDEH, Q20UDEH, Q26UDEH,
Q50UDEH, and Q100UDEH.
Generic term for Q03UDV, Q04UDV, Q06UDV, Q13UDV, and Q26UDV.
Generic term for Basic model QCPU, High Performance model QCPU, Process CPU, Redundant CPU,
and Universal model QCPU.
Abbreviation for performing communications with a programmable controller CPU using an Ethernet
module or built-in Ethernet port CPU.
Generic term for Microsoft
Home Edition Operating System.
®
Windows® XP Professional Operating System and Microsoft® Windows® XP
Description
A - 32
Generic term/
abbreviation
Description
Generic term for Microsoft® Windows Vista® Home Basic Operating System,
®
Windows Vista® Home Premium Operating System,
®
Windows Vista® Business Operating System,
®
Windows Vista® Ultimate Operating System,
®
Windows Vista® Enterprise Operating System.
®
®
7 Home Premium Operating System,
®
7 Professional Operating System,
®
7 Ultimate Operating System,
®
7 Enterprise Operating System.
®
8 Pro Operating System,
®
8 Enterprise Operating System.
®
8.1 Pro Operating System,
®
8.1 Enterprise Operating System.
®
10 Pro Operating System,
®
10 Education Operating System,
®
10 Enterprise Operating System.
7 Starter Operating System,
®
8 Operating System,
®
8.1 Operating System,
®
10 Home Operating System,
Windows Vista
Windows® 7
Windows® 8
Windows® 8.1
Windows® 10
®
Microsoft
Microsoft
and Microsoft
Generic term for Microsoft Windows
Microsoft Windows
Microsoft Windows
Microsoft Windows
and Microsoft Windows
Generic term for Microsoft Windows
Microsoft Windows
and Microsoft Windows
Generic term for Microsoft Windows
Microsoft Windows
and Microsoft Windows
Generic term for Microsoft Windows
Microsoft Windows
Microsoft Windows
and Microsoft Windows
Microsoft
Windows® 8 or laterGeneric term for Windows® 8, Windows® 8.1, and Windows® 10
Windows® 7 or laterGeneric term for Windows® 7, Windows® 8, Windows® 8.1, and Windows® 10
Windows Vista® or laterGeneric term for Windows Vista®, Windows® 7, Windows® 8, Windows® 8.1, and Windows® 10
®
Excel
Microsoft® Excel® 2007 or
later
Internet Explorer
Personal computer
Generic term for Microsoft® Excel® 2003, Microsoft® Excel® 2007, Microsoft® Excel® 2010 (32-bit
®
version), and Microsoft
Excel® 2013 (32-bit version).
Generic term for Microsoft® Excel® 2007, Microsoft® Excel® 2010 (32-bitversion), and Microsoft® Excel®
2013 (32-bit version).
®
Generic term for Microsoft
®
Explorer
Internet Explorer
8.0, Windows® Internet Explorer® 9.0, Windows® Internet Explorer® 10.0, and Windows®
®
11.0.
Generic term for personal computer on which Windows
Internet Explorer 6.0, Windows® Internet Explorer® 7.0, Windows® Internet
®
operates.
A - 33
DEFINITIONS AND DESCRIPTIONS OF TERMS
The following table shows the definitions and descriptions of the terms used in this
manual.
Ter mDescription
Account
Device
SNTP
Time zone
Daylight saving time (summer
time)
URL
CompactFlash card
Direct connection
Connection via a hub
Host nameThe name of a computer connected to the network which is easy for people to understand.
Web browserAbbreviation for the software used to view web pages.
Data loggingThe function to log programmable controller CPU device values at the specified data sampling interval.
Event logging
Auto logging
Data logging file
Event logging file
Logging fileThe general term for the data logging file and event logging file.
CSV file
Binary fileA binary format file that is output from the high speed data logger module.
SMTP-Auth
POP before SMTP
Realtime trend
Best effort functionsThe concept of deriving maximum performance depending on the state at that time.
Designates the right to use the high speed data logger module or the ID necessary when using the
module.
The types of memory data in the programmable controller CPU.
There are devices handled in units of bits and in units of words.
Abbreviation for Simple Network Time Protocol.
A protocol for synchronizing a personal computer's time via a TCP/IP network, the simple version of
NTP. Since the SNTP protocol is included in NTP, the high speed data logger module can also
synchronize time via NTP.
The standard time zones for each region of the world.
Each nation uses the time difference (within ±12 hours) from the time at the Greenwich Observatory in
England (GMT) as the standard time. Regions using the same time difference are called a time zone.
The standard time for Japan is 9 hours ahead of GMT.
Depending on the country, they may also use daylight saving time in summer.
A system where clocks are set ahead for a specified period during summer.
Abbreviation for Uniform Resource Locator.
Notation method for indicating the location of information resources (documents, graphics, etc.) on the
Internet.
A storage card regulated by the 'CF+ and CompactFlash Specification' issued by the CompactFlash
Association. The memory card required for operating the high speed data logger module.
A connection method using an Ethernet cable to connect the high speed data logger module and a
personal computer on a 1:1 basis. They can be easily connected without knowing the IP address.
A method of connecting the high speed data logger module and a personal computer to a local area
network. The high speed data logger module's IP address must be specified when connecting. Multiple
high speed data logger modules can be accessed from a personal computer over a network.
The function to monitor sampled device values from the programmable controller CPU and log events
that occur.
A function to automatically start logging when a CompactFlash card with the auto logging settings
written to it in advance is inserted in a running high speed data logger module.
The file where the data sampled by the high speed data logger module are saved in the format
specified with the Configuration Tool.
The file where the events sampled by the high speed data logger module are saved in the format
specified with the Configuration Tool.
A CSV format file used for high speed data logger module and high speed data logger module tool.
(A text file in which data are organized by separating it with commas (",").)
One type of authorization method specified when sending e-mail.
The user's account and password are authenticated between the SMTP server and user, and this
method only sends e-mail if authenticated.
One type of authorization method specified when sending e-mail.
By accessing the specified POP3 server in advance before sending an e-mail, this method grants
permission to use the SMTP server.
The current data sampled by high speed data logger module is displayed with the trend graph function.
The data is always updated, and the display history from when the monitor is started to the present can
be checked.
A - 34
PACKING LIST
The following table shows the product included to the QD81DL96 high speed data logger
module.
Mount the module
and simply configure
it to reliably sample
data!!
Can save data to
the CompactFlash
card in the optimal
file format!!
OVERVIEW
CHAPTER 1OVERVIEW
This manual explains the specifications procedures up to operation, functions, and
troubleshooting of the high speed data logger module.
When applying the example programs introduced in this manual to an actual system,
make sure to examine the applicability and confirm that it will not cause system control
problems.
By easily configuring the high speed data logger module, it can save sampled
programmable controller device data in the optimal file format to a CompactFlash card
(sold separately, required) inserted in the module.
1.1 Features
This section explains the features of the high speed data logger module.
1
2
3
OVERVIEW
SYSTEM
CONFIGURATION
(1) Programmable controller device data can be easily logged without a
personal computer
The high speed data logger module can log programmable controller devices without
using a personal computer.
This can reduce costs, as well as provide peace of mind since you won't worry about
personal computer down-time or connection cables disconnecting.
By easily configuring the module, sampled data can be saved in the optimal file format
to a CompactFlash card.
SETTINGS AND
HIGH SPEED DATA
4
PROCEDURES UP TO
5
LOGGER MODULE
6
7
DATA LOGGING
8
SPECIFICATIONS
OPERATION
TOOL STARTUP
FUNCTION LIST
FUNCTION
Binary format logging files can be converted to CSV format logging files using the
Conversion Tool.
1.1 Features
1 - 1
EVENT LOGGING
FUNCTION
1
POINT
OVERVIEW
(2) Control data changes can be logged without misses ( Section 7.3.1)
The high speed data logger module can perform data logging per scan/in millisecond
intervals.
Since the module is logging changes in the specified control data without misses, it
demonstrates its effectiveness in determining the cause of problems when they occur.
Since it can also perform high speed logging, you can perform high-precision
equipment analysis.
(100ms interval data sampling)
Upper limit
Lower limit
Upper limit
Lower limit
(1) In order to perform logging per scan/in millisecond intervals, a programmable
(2) The data logging, event logging, and report functions of the high speed data
100ms
Capture fine
(1ms interval high speed data sampling by
the high speed data logger)
Over upper limit
1ms
controller CPU which supports the high speed data sampling function is
required.
Section 2.2 Applicable Systems
logger module are the best effort functions.
Since module processing time changes according to the settings and status
of other devices, it may not operate with the set data sampling interval. Run
the system by fully verifying the processing time of each function when
constructing it.
For processing time, refer to the following chapter.
Chapter 17 PROCESSING TIME
(3) Accelerate problem analysis when problems occur (trigger logging
function) ( Section 7.3.2)
With data status/change triggers, the high speed data logger module can save the
data before and after the trigger.
Since only the data before and after trouble occurs can be saved, you can quickly
identify the data which is the cause of the problem and save file space.
By setting an Excel file template, such as layouts, graphs, and calculation formulas, in
advance, the high speed data logger module can save data in list format or report
SETTINGS AND
PROCEDURES UP TO
OPERATION
5
format to the inserted CompactFlash card.
Blank daily report template
Transfer the template file to
the high speed data logger
module with the
Configuration Tool.
Based on the template file,
insert specified device
values at the specified
timing and additionally save
as a daily report file.
HIGH SPEED DATA
LOGGER MODULE
TOOL STARTUP
6
FUNCTION LIST
7
Daily report file (Excel)
1.1 Features
DATA LOGGING
FUNCTION
8
EVENT LOGGING
FUNCTION
1 - 3
1
EthernetEthernet
MELSECNET/HMELSECNET/H
Date/time
Occurred/Restored
Event name
08/01/28 14:25:23
08/01/28 16:24:05
08/01/28 16:34:54
08/01/28 17:45:02
Occurred
Occurred
Occurred
Occurred
Intrusion detector
Temperature exceeded
Process time exceeded
Process B warning
Internet
Mail server
Event occurs
Intrusion detection
switch is ON!
(bit ON/OFF condition)
E-mails can be sent
when events occur as
necessary.
Temperature exceeded!
(compare to numerical
value condition)
Process A is slow!
(Execution time
condition)
Process B should always
turn ON as device D B
C A, but turned ON as
device D A B C!
(Execution order
condition)
...
...
...
...
...
...
.
.
.
.
.
.
OVERVIEW
(5) Equipment error detection and failure prediction are possible (event
logging function) ( Chapter 8)
By setting monitoring target data and monitoring conditions, the high speed data
logger module can log changes (events) for those conditions. This can be utilized for
equipment error detection and failure prediction.
Not only data values can be set as monitoring conditions, the variation time and order
of changes for each data can also be set.
A detected event occurrence can be notified with an e-mail.
1 - 4
1.1 Features
1
OVERVIEW
High speed
data logger
module
(6) Accessible over the network hierarchy
The high speed data logger module can access programmable controller CPUs
hierarchically connected with networks such as CC-Link IE, MELSECNET/H, CCLink, and Ethernet, and perform data logging.
A single high speed data logger module can access up to a maximum of 64 programmable
controller CPUs.
1
2
3
4
OVERVIEW
SYSTEM
CONFIGURATION
SPECIFICATIONS
Can access and log
programmable
controller CPUs
crossing over the
network hierarchies!
SETTINGS AND
PROCEDURES UP TO
OPERATION
5
HIGH SPEED DATA
LOGGER MODULE
TOOL STARTUP
6
FUNCTION LIST
7
1.1 Features
DATA LOGGING
FUNCTION
8
EVENT LOGGING
FUNCTION
1 - 5
1
High speed data logger module
Built-in
Ethernet port QCPU
LCPUC Controller module
Does not require
adding a network
module
Logging file
Ethernet
OVERVIEW
For Ethernet connections, since the high speed data logger module can access other
station's programmable controller CPUs using its Ethernet port, it
s not necessary to add a network module to the module mounting station.
If the access target station is also a built-in Ethernet port CPU or C Controller module, it's
not necessary to add a network unit to the access target station.
This function can reduce costs.
1 - 6
1.1 Features
1
O
n
l
i
n
e
s
t
a
r
t
u
p
Factory
Configuration Tool
Start the high speed data logger
module's built-in Configuration Tool
online and emergency data can be
added on-site.
OVERVIEW
(7) Logging is possible with simple configuration
Logging settings can be easily configured with wizard format settings.
Since the Configuration Tool is built-in to the high speed data logger module, settings
can be easily changed on-site by simply connecting a personal computer.
Wizard format settings
1
2
3
4
OVERVIEW
SYSTEM
CONFIGURATION
SPECIFICATIONS
Setting data are easily changed on-site
Configuration complete!!
SETTINGS AND
PROCEDURES UP TO
OPERATION
5
HIGH SPEED DATA
LOGGER MODULE
TOOL STARTUP
6
FUNCTION LIST
7
1.1 Features
DATA LOGGING
FUNCTION
8
EVENT LOGGING
FUNCTION
1 - 7
1
Import
Programming toolHigh speed data logger module
Configuration Tool
DevicesDevice comments
Global labels
Temperature
Raw materials
Date
Y0
M0
D0
DevicesDevice comments
Global labels
Temperature
Raw materials
Date
Y0
M0
D0
OVERVIEW
(8) Created data can be utilized as programming assets
(a) Utilize project data of programming tool ( Section 11.2.10)
Global labels and device comments created in the programming tool can be
imported to the Configuration Tool.
Imported global labels are synchronized with the changes of global labels in the
import source, and they can be updated easily.
Since global labels and device comments that can be imported are specified from
the list displayed on the screen, input errors and work hours can be reduced.
(b) Utilize existing project data in Configuration Tool ( Section 11.3.4)
Settings of existing project data in the Configuration Tool can be specified and
imported.
This function reduces the setting work hours.
(c) Utilize tabular format data
A list of large-volume data created using Excel can be copied and pasted to the
data list of Configuration Tool.
Create large-volume data on Excel.Large-volume data are pasted as they are.
Copy
Paste
1 - 8
1.1 Features
1
File server
Logging
file
Logging
file
T
r
a
n
s
f
e
r
Logging files can be moved to a file
server, making it possible to log
without worrying about exceeding
available space!
CompactFlash
card
OfficeOn-site
Logging automatically starts
only by inserting the card.
Completes when LED is OFF.
Ship
Data sampling
Return shipment
OVERVIEW
(9) Large-volume logging files can be saved
Since the high speed data logger module can use high-capacity CompactFlash cards
up to a maximum of 8 GB, logging over long periods is possible.
Since the logging files saved on the CompactFlash card can also be transferred to a
server, logging which exceeds the capacity of the CompactFlash card is possible.
In addition, using the function which automatically deletes old files saved on the
CompactFlash card according to the specified number of files or free capacity, logging
can be continued without replacement of the CompactFlash card.
Even when the network is disconnected, logging files can be resent automatically.
1
2
3
4
OVERVIEW
SYSTEM
CONFIGURATION
SPECIFICATIONS
(10)Simple data sampling instructions for troubleshooting
( Section 10.2)
Logging can be automatically started simply by installing a CompactFlash card.
By only sending a CompactFlash card with the settings stored on it to the site and
having a worker insert it in the high speed data logger module, the module can
sample the necessary data.
(11)Time synchronization using SNTP ( Section 10.1)
The time between a high speed data logger module and a programmable controller
CPU can be set through communication with an SNTP server computer.
This enables synchronizing the time for the entire system.
(12) Displaying data and events matched to application
Using GX LogViewer, sampled data can be displayed as graphs and occurred/
restored events can be displayed in a list.
( GX LogViewer Version 1 Operating Manual)
1 - 10
1.1 Features
1
XX manufacturing batch process
XX manufacturing plant
(1) Preparation
(2) Agitation/cooling
(3) Addition
(4) Agitation
(5) Extraction
Logging file of
the preparation
phase
Logging file of
the agitation/cooling
phase
Logging file of
the agitation
phase
Logging file of
the addition
phase
Stock solution A tank Stock solution B tank Additive tank
(1) Preparation(3) Addition
(2)(4)
Agitation
(5) Extraction
(2) Cooling
Cooling
device
To the bottling process
Mixing pot
The report can be created in
batch units by collecting logging
data of each phase when
the batch process is completed!
The information and date can
be added to the report file name,
making it easier to recognize to
which batch the report corresponds!
BATCH_C0172_090410_1330_00000001.XLS
Switch a file and save logging data
when each phase is completed
OVERVIEW
(13)Data can be managed on a batch (lot) basis
By designating the programmable controller data which indicate the end of batches
(lots) as the file switching timing, files can be created in units of batches (lots).
In addition, attaching the batch (lot) number to the file name of the logging and report
makes the batch-based (lot-based) data management easier.
1
2
3
OVERVIEW
SYSTEM
CONFIGURATION
SPECIFICATIONS
4
SETTINGS AND
PROCEDURES UP TO
OPERATION
5
HIGH SPEED DATA
LOGGER MODULE
TOOL STARTUP
6
FUNCTION LIST
7
1.1 Features
DATA LOGGING
FUNCTION
8
EVENT LOGGING
FUNCTION
1 - 11
1
Recipe file
Product AProduct BProduct C
Example: Changing combination ratio of raw material at the specified time
Change
manufacturing data
Change
manufacturing data
Raw material B
1.6
Raw material A
2.4
Raw material C
1
Raw material B
1
Raw material A
2.4
Raw material C
1
Raw material B
1
Raw material A
3
Raw material C
1.2
Transfer (write) manufacturing data
Transfer (read) manufacturing data
Change manufacturing data at the specified time.
OVERVIEW
(14) Manufacturing data (device values) stored in programmable controller
CPU can be changed
(Recipe function: Chapter 15)
Device values can be transferred (read) from the recipe files (created in the
Configuration Tool and stored) stored in the CompactFlash card to the programmable
controller CPU at the specified time.
Furthermore, adjusted manufacturing data can be transferred (written) to recipe files
and utilized.
Transferring (reading/writing) manufacturing data can be executed from ladder
program using the dedicated instructions or from the Configuration Tool.
1 - 12
1.1 Features
1
CSV format
Event conditions
Match
Event
Event logging
Data logging
Current value data
Data
Data logging files
Report file
CompactFlash card
CSV format
Binary format
Event logging files
Binary format
or
or
Report creation
Programmable
controller CPU
High speed data
logger module
Sample device
values from
the
programmable
controller
CPU
The high speed data logger module logs (records/saves) device data sampled from a
programmable controller CPU as files on a CompactFlash card.
Files which can be created are data logging files, event logging files, and report files.
In the data logging file, all the sampled data in the specified period can be saved. In this
way, sampled data can be analyzed in depth. ( Chapter 7)
In the event logging file, only the specified data correspond to the event condition can be
saved. In this way, only necessary data can be identified. ( Chapter 8)
In the report file, data can be saved as an Excel file. In this way, by only configuring the
settings in advance, a report with desired graphs and layouts can be created
automatically. ( Chapter 9)
The overview up to creating a file is shown in the figure below.
1
2
3
4
OVERVIEW
SYSTEM
CONFIGURATION
SPECIFICATIONS
SETTINGS AND
HIGH SPEED DATA
PROCEDURES UP TO
5
LOGGER MODULE
6
7
DATA LOGGING
8
OPERATION
TOOL STARTUP
FUNCTION LIST
FUNCTION
1.2 Processing Overview
EVENT LOGGING
FUNCTION
1 - 13
1
OVERVIEW
1.3 High Speed Data Logger Module Software Configuration
The high speed data logger module software configuration is shown in the table below.
ItemDescriptionReference
High speed data logger
module tool
High speed data logger
module Configuration
Tool
Logging File
Conversion Tool
This software is for installing 'high speed data logger module Configuration Tool' and
'Logging File Conversion Tool'.
This software configures and maintains the high speed data logger module.
There is an online startup method and offline startup method (startup from the start menu)
to start the tool.
This software converts binary format logging files to CSV format logging files.
There is an offline startup method (startup from the start menu) to start the tool.
For the method for starting the high speed data logger module Configuration Tool and the
Logging File Conversion Tool, refer to the following chapter.
Chapter 5 HIGH SPEED DATA LOGGER MODULE TOOL STARTUP
Chapter 5
Chapter 11
Chapter 14
1 - 14
1.3 High Speed Data Logger Module Software Configuration
2
SYSTEM CONFIGURATION
CHAPTER 2SYSTEM CONFIGURATION
This chapter explains the system configuration of the high speed data logger module.
2.1 System Configuration
2.1.1 Overall system configuration
1
OVERVIEW
2
This section explains the overall system configuration when using the high speed data
logger module.
FTP server
QCPU
*1
High speed data
logger module
CC-Link IE MELSECNET/10(H),
Ethernet, CC-Link, C24
SNTP server
*2
Settings
Display
(Sold separately, required)
CF
Mail server
*3
Configuration Tool
GX LogViewer
Configuration/
display personal
computer
*1
SYSTEM
CONFIGURATION
3
SPECIFICATIONS
4
SETTINGS AND
PROCEDURES UP TO
OPERATION
5
HIGH SPEED DATA
LOGGER MODULE
TOOL STARTUP
6
Access target CPU : QCPU, LCPU, C Controller module
*1: Required when externally saving logged files.
*2: Required when synchronizing the high speed data logger module and programmable controller
CPU time to a standard time.
*3: Required when sending e-mail.
2.1 System Configuration
2.1.1 Overall system configuration
2 - 1
FUNCTION LIST
7
DATA LOGGING
FUNCTION
8
EVENT LOGGING
FUNCTION
2
Configuration personal computer
Twisted pair cable
(crossing cable)
Ethernet
High speed data logger module
SYSTEM CONFIGURATION
2.1.2 System configuration when performing initial setup, maintenance, and
inspection
Connect a high speed data logger module and a personal computer directly to perform an
initial setup, maintenance, and inspection. For the direct connection, refer to Section 2.1.3
(2) and Section 2.1.4.
2 - 2
2.1 System Configuration
2.1.2 System configuration when performing initial setup, maintenance, and inspection
2
POINT
r
SYSTEM CONFIGURATION
2.1.3 System configuration during operation
This section explains the system configuration when operating the high speed data logger
module.
(1) For a connection via a hub
In this method, the high speed data logger module and a personal computer are
connected through a local area network via a hub.
The high speed data logger module's IP address must be specified when connecting
via a hub.
High speed data logger module
Ethernet
Twisted pair cable
1
2
3
OVERVIEW
SYSTEM
CONFIGURATION
Hub
Twisted pair cable
Server personal compute
Configuration/display
personal computer
The high speed data logger module can be only connected over a LAN
connection.
The module cannot be connected via Internet.
(2) For a direct connection
In this method, the high speed data logger module and a configuration/display
personal computer are directly connected on a 1:1 basis through an Ethernet cable
(crossing cable) without a hub.
The high speed data logger module's IP address does not need to be specified to
perform communication when directly connecting. (The broadcast is used to perform
communication.)
SPECIFICATIONS
4
SETTINGS AND
PROCEDURES UP TO
OPERATION
5
HIGH SPEED DATA
LOGGER MODULE
TOOL STARTUP
6
FUNCTION LIST
7
High speed data logger module
Twisted pair cable
(crossing cable)
Ethernet
Configuration/display
personal computer
2.1 System Configuration
2.1.3 System configuration during operation
2 - 3
DATA LOGGING
FUNCTION
8
EVENT LOGGING
FUNCTION
2
Remark
High speed data logger module
Configuration/display
personal computer
Ethernet
Hub
SYSTEM CONFIGURATION
2.1.4 Precautions when directly connecting
This section explains precautions when directly connecting a configuration/display
personal computer to the high speed data logger module.
(1) Connecting to a LAN line
Do not connect to a LAN line and communicate over a direct connection.
By communicating over a direct connection, a load is placed on the line and it can
affect the communication of other devices.
(2) Connections which are not direct connections
Direct connection setup cannot be performed in a configuration where a single high
speed data logger module and a single configuration/display personal computer are
connected to a hub as shown in the following figure.
(3) Conditions where communication cannot be accomplished with a direct
connection
If the conditions below match, communications cannot be performed with a direct
connection.
If communications cannot be performed, review the high speed data logger module or
configuration/display personal computer settings.
(a) For each bit of the high speed data logger module's IP address, the bits
corresponding to the configuration/display personal computer's subnet mask 0
portion are all ON or OFF
Example)
High speed data logger module IP address: 64. 64.255.255
Configuration/display personal computer IP address : 64. 64.1.1
Configuration/display personal computer subnet mask: 255.255.0.0
(b) For each bit of the high speed data logger module's IP address, the bits that
correspond to the host address of each class for the configuration/display
personal computer's IP address are all ON or OFF
Example)
High speed data logger module IP address: 64. 64.255.255
Configuration/display personal computer IP address : 192.168.0.1
Configuration/display personal computer subnet mask: 255.255.0.0
(c) The high speed data logger module's IP address is obtained automatically by DHCP
2 - 4
• The IP address of each class is listed below.
Class A: 0.x.x.x to 127.x.x.x, Class B: 128.x.x.x to 191.x.x.x
Class C: 192.x.x.x to 223.x.x.x
• The host address of each class is the 0 portion below.
Class A: 255.0.0.0, Class B: 255.255.0.0
Class C: 255.255.255.0
2.1 System Configuration
2.1.4 Precautions when directly connecting
2
SYSTEM CONFIGURATION
(4) Other precautions
(a) When the Windows firewall is ON
Disable the Windows firewall.
(b) When multiple IP addresses are enabled at the same time
Direct connection setup cannot be performed in a configuration where multiple IP
addresses are enabled at the same time as shown below.
• IP addresses are assigned to each of multiple Ethernet ports (network
devices) of a configuration/display personal computer.
• Aside from the Ethernet port of a configuration/display personal computer, a
wireless LAN setting is enabled.
• Multiple IP addresses are assigned to a single Ethernet port of a
configuration/display personal computer.
1
2
3
4
OVERVIEW
SYSTEM
CONFIGURATION
SPECIFICATIONS
SETTINGS AND
HIGH SPEED DATA
PROCEDURES UP TO
5
LOGGER MODULE
6
7
DATA LOGGING
8
OPERATION
TOOL STARTUP
FUNCTION LIST
FUNCTION
2.1 System Configuration
2.1.4 Precautions when directly connecting
2 - 5
EVENT LOGGING
FUNCTION
2
SYSTEM CONFIGURATION
2.2 Applicable Systems
(1) Mountable modules, mountable base units, and number of mountable
modules
(a) When mounted to a CPU module
The following table shows mountable CPU modules and base units applicable to
the high speed data logger module and the number of mountable modules.
Depending on the combination with other mounted modules or the number of
mounted modules, power supply capacity may be insufficient.
When mounting modules, always take the power supply capacity into
consideration.
If the power supply capacity is insufficient, review the combination of mounted
modules.
Applicable when using a
programmable controller CPU
with a serial number whose first
five digits are '11012' or higher.
*4
*3
*4
Mountable base units
Main base
unit
Extension base
: Mountable, : Not mountable
*1: Can be mounted to any I/O slot of a mountable base unit.
*2: Can be mounted to the base unit with High performance model QCPU function version B or later only.
*
3: Applicable when using Q12DCCPU-V with a serial number whose first five digits are '12042' or
*4: The number of intelligent function module in which the high speed data sampling can be performed
for one control CPU is one.
*5:
Applicable when using QJ81DL96 with a serial number whose first five digits are '14122' or
Number of
mountable
modules
1 mountable
module for 1
control CPU
higher.
higher.
OVERVIEW
2
SYSTEM
CONFIGURATION
3
SPECIFICATIONS
4
SETTINGS AND
PROCEDURES UP TO
OPERATION
5
HIGH SPEED DATA
LOGGER MODULE
TOOL STARTUP
6
FUNCTION LIST
7
2.2 Applicable Systems
DATA LOGGING
FUNCTION
8
EVENT LOGGING
FUNCTION
2 - 7
2
Remark
SYSTEM CONFIGURATION
(b) When mounting to a MELSECNET/H remote I/O station
The high speed data logger module cannot be mounted to a MELSECNET/H
remote I/O station.
Mount the high speed data logger module to a master station.
(2) Support for multiple CPU systems
(a) The high speed data logger module supports multiple CPU systems.
(b) The high speed data logger module can only perform high speed data sampling
for the CPU controlling it.
When using the high speed data logger module in a multiple CPU system, refer to
the following manual.
QCPU User's Manual (Multiple CPU System)
2 - 8
2.2 Applicable Systems
2
POINT
POINT
SYSTEM CONFIGURATION
2.3 Connection System Equipment
This section explains the equipment that can be connected to the high speed data logger
module.
(1) CompactFlash card (sold separately, required)
The high speed data logger module requires one CompactFlash card.
Use one of the following CompactFlash cards manufactured by Mitsubishi.
If a CompactFlash card other than the following is used, a failure such as a data
corruption on a CompactFlash card or a system shutdown (SP.UNIT DOWN occurs in
the programmable controller CPU) may occur during an operation.
CompactFlash cards have a life span measured by writes.
For details about CompactFlash cards, refer to the following chapter.
Chapter 16 CompactFlash CARD
For precautions when wiring twisted pair cables, refer to the following section.
Section 4.4.2 Wiring precautions
SETTINGS AND
PROCEDURES UP TO
OPERATION
5
HIGH SPEED DATA
LOGGER MODULE
TOOL STARTUP
6
FUNCTION LIST
7
2.3 Connection System Equipment
DATA LOGGING
FUNCTION
8
EVENT LOGGING
FUNCTION
2 - 9
2
SYSTEM CONFIGURATION
2.4 Operating Environment
(1) Operating environment for configuration personal computer
ItemDescription
ComputerPersonal computer on which the following software operates
CPU
Required
memory
Free hard disk space512MB or more
DisplayResolution 1024x768 pixels or higher
Operating system
(English version)
Excel (English version)
*1*2*3*4*5
*9, *10
Web browser (English version)
InterfaceEthernet port
Refer to the following section.
(2) in this section Performance requirements for personal computer and operating system
Microsoft® Windows®XP Professional Operating System SP 2 or later
Microsoft® Windows®XP Home Edition Operating System SP 2 or later
Microsoft® Windows Vista® Home Basic Operating System
Microsoft® Windows Vista® Home Premium Operating System
Microsoft® Windows Vista® Business Operating System
Microsoft® Windows Vista® Ultimate Operating System
Microsoft® Windows Vista® Enterprise Operating System
Microsoft® Windows® 7 Starter Operating System
Microsoft® Windows® 7 Home Premium Operating System
Microsoft® Windows® 7 Professional Operating System
Microsoft® Windows® 7 Ultimate Operating System
Microsoft® Windows® 7 Enterprise Operating System
Microsoft® Windows® 8 Operating System
*8
Microsoft® Windows® 8 Pro Operating System
Microsoft® Windows® 8 Enterprise Operating System
Microsoft® Windows® 8.1 Operating System
Microsoft® Windows® 8.1 Pro Operating System
Microsoft® Windows® 8.1 Enterprise Operating System
Microsoft® Windows® 10 Home Operating System
Microsoft® Windows® 10 Pro Operating System
Microsoft® Windows® 10 Education Operating System
Microsoft® Windows® 10 Enterprise Operating System
Microsoft® Excel® 2003
*11
Microsoft® Excel® 2007
®
Microsoft
Excel® 2010 (32-bit version)
Microsoft® Excel® 2013 (32-bit version)
*12
*13
Microsoft® Internet Explorer 6.0
®
Internet Explorer® 7.0
®
Internet Explorer® 8.0
®
Internet Explorer® 9.0
®
Internet Explorer® 10.0
®
Internet Explorer® 11.0
*14
Windows
Windows
Windows
Windows
Windows
*6
*6
*7
*7
*7
*7
*7
*7
*7
*7
*7
*7
*8
*8
*8
*8
*8
*8
*8
*8
*8
2 - 10
2.4 Operating Environment
2
SYSTEM CONFIGURATION
*1: "64-bit Windows® XP Professional" and "64-bit Windows Vista®" cannot be used.
*2: When the following functions are used, this product may not run properly.
• Starting applications in Windows
• Fast user switching
• Remote desktop
• Windows XP Mode
• Windows Touch or Touch
• Modern UI
• Client Hyper-V
• Virtual desktop
• Tablet mode
• Windows
*3: Cannot be used if the user is logged in with Guest authority.
*4: If the Windows firewall setting is enabled, the 'Find High Speed Data Logger Module function' and
'Direct connection function' may not operate correctly.
Disable the Windows firewall setting.
*5: In the following case, the screen of this product may not work properly.
• The size of the text and/or other items on the screen is changed to a non-default value.
*6: One of the following applications is required to be installed.
• .NET Framework 2.0 English Language Pack
• .NET Framework 3.5 English Language Pack
•GX Works2
*7: Cannot be used if the user is logged on with parental controls enabled.
*8: For Windows
• ".NET Framework 3.5 (includes .NET 2.0 and 3.0)" needs to be enabled in "Turn Windows
features on or off" on the Control Panel.
• Select "Don't do anything (turn off Windows SmartScreen)" on the Control Panel.
*9: Required when using the report function.
*10: The save format of the report file output with the report function is the xls format.
A portion of the functions added from Microsoft
*11: Microsoft
under the Windows
*12: For Excel
Windows
*13: For Excel
*14: Required when using the online startup function.
®
sleep or hibernate
®
8 or later ;
®
Office 2003 Service Pack 3 or later is required when using Microsoft® Excel® 2003
®
®
XP Service Pack 3, Windows Vista® Service Pack 1 or later, or Windows® 7 or later
®
®
2010 (32-bit version), one of the following operating environment is required:
2013 (32-bit version), Windows® 7 or later is required.
®
compatibility mode
7 operating system.
®
Excel® 2007 or later cannot be used.
1
OVERVIEW
2
SYSTEM
CONFIGURATION
3
SPECIFICATIONS
4
SETTINGS AND
PROCEDURES UP TO
OPERATION
5
2.4 Operating Environment
HIGH SPEED DATA
LOGGER MODULE
TOOL STARTUP
6
FUNCTION LIST
7
DATA LOGGING
FUNCTION
8
EVENT LOGGING
FUNCTION
2 - 11
2
SYSTEM CONFIGURATION
(2) Performance requirements for personal computer and operating system
Operating system
Windows®XP Professional
Windows®XP Home Edition
Windows Vista® Ultimate
Windows Vista® Business
Windows Vista® Home Premium
Windows Vista® Home Basic
Windows Vista® Enterprise
Windows® 7 Starter
Windows® 7 Home Premium
Windows® 7 Professional
Windows® 7 Ultimate
Windows® 7 Enterprise
Windows® 8
Windows® 8 Pro
Windows® 8 Enterprise
Windows® 8.1
Windows® 8.1 Pro
Windows® 8.1 Enterprise
Windows® 10 Home
Windows® 10 Pro
Windows® 10 Education
Windows® 10 Enterprise
Personal computer performance requirements
CPURequired memory
®
CoreTM 2 Duo 2GHz
Intel
or higher is recommended
32-bit version :1BG or more
64-bit version :2BG or more
1GB or more
2 - 12
2.4 Operating Environment
2
Remark
11011
MAC ADD.
Serial number
(first 5 digits)
Lists compliant standard
symbols.
Serial number
SYSTEM CONFIGURATION
2.5 How to Check the Function Version, Serial Number
This section explains the method for checking the function version and serial number of
the high speed data logger module.
(1) Checking 'SERIAL on the rating plate' on the side of the high speed data
logger module
(2) Checking on the front of the module
The serial number is indicated on the serial number display on the front of the module
(at the bottom).
1
2
3
4
OVERVIEW
SYSTEM
CONFIGURATION
SPECIFICATIONS
Serial number has been labeled on to the front of the module since March 2009.
Note that, however, this labeling may not apply to some of modules manufactured
around the time of modification.
SETTINGS AND
HIGH SPEED DATA
PROCEDURES UP TO
5
LOGGER MODULE
6
7
DATA LOGGING
8
OPERATION
TOOL STARTUP
FUNCTION LIST
FUNCTION
2.5 How to Check the Function Version, Serial Number
2 - 13
EVENT LOGGING
FUNCTION
2
Operating procedure
Screen display
Operating procedure
Screen display
SYSTEM CONFIGURATION
(3) Checking with GX Developer
The function version and serial number can be checked with "Product Information
List" or "Module's Detailed Information" in GX Developer.
The following explains the method for checking them with "Product Information List".
For "Module Detail Information", refer to the following section.
Section 18.1.3 System monitor
Click [Diagnostics] [System monitor] button.
The [Product Information List] screen is displayed.
(4) Checking with GX Works2
The function version and serial number can be checked with "Product Information
List" or "Module's Detailed Information" in GX Works2.
The following explains the method for checking them with "Product Information List".
Click [Diagnostics] [System Monitor] button.
The [Product Information List] screen is displayed.
2 - 14
2.5 How to Check the Function Version, Serial Number
2
POINT
Operating procedure
Screen display
SYSTEM CONFIGURATION
(1) The serial number displayed in Programming tool or Setting's product
information may be different from the one on the rating plate.
• The serial number on the rating plate indicates the management
information of the product.
• The serial number displayed in Programming tool or Setting's product
information indicates the function information of the product.
The function information of the product is updated when functions are
added.
(2) The "Product No." column is displayed only when the CPU module is a
Universal model QCPU.
(5) Checking with the Configuration Tool
The product information can be checked with "Product information" in the
Configuration Tool.
2.5 How to Check the Function Version, Serial Number
DATA LOGGING
FUNCTION
8
EVENT LOGGING
FUNCTION
2 - 15
2
SYSTEM CONFIGURATION
2.6 System Configuration Precautions
This section describes the system configuration precautions.
2.6.1 Precautions when using Redundant CPUs
The following describes precautions when using Redundant CPUs.
(1) Mountable base unit
When using the high speed data logger module in a redundant system, be sure to
mount the module to the extension base unit for CPU/redundant power supply.
The high speed data logger module cannot be mounted to the main base unit in a
redundant system.
(2) "Access target CPU setting"
• When the high speed data logger module is mounted to the Redundant CPU, it
can only access the own station CPU.
It cannot access CPUs of other stations.
• The high speed data logger module cannot access Redundant CPUs of other
stations.
2.6.2 Precautions when using C Controller modules
The following describes precautions when using C Controller modules.
(1) "Access target CPU setting"
• When the high speed data logger module is mounted to the C Controller module,
it can only access the own station CPU.
It cannot access CPUs of other stations.
• When the control CPU of the access target network module is a C Controller
module, only the control CPU of the network module can be accessed.
(2) Network communication route
• When the network module is mounted to the C Controller module, the network
module cannot be used as a relay station.
2 - 16
2.6 System Configuration Precautions
2.6.1 Precautions when using Redundant CPUs
2
SYSTEM CONFIGURATION
1
2.6.3 Precautions for using multiple CPU system
The following describes the precautions for using the multiple CPU system.
(1) Access to each CPU module at start-up of multiple CPU system
In the system in which a high speed data logger module is mounted in the multiple
CPU system, an error may occur when accessing other CPU from the high speed
data logger module or accessing the other station via a network module controlled by
other CPU from the high speed data logger module due to the difference of start-up
time of each CPU module. In this case, clear the error in the high speed data logger
module after starting up other CPU.
Section 18.1.2
The start-up of other CPUs can be checked with the special relays, SM220 to SM223.
For the special relays, refer to the user's manual for the CPU module used.
2.6.4 Precautions for using hubs
The following describes the precautions for using the hub.
(1) IEEE802.3x flow control in full-duplex communication
The high speed data logger module does not support the IEEE802.3x flow control.
Therefore, when the load of an Ethernet line is high in the connection with the hub
supporting IEEE802.3x, the data to be sent to the module may be lost.
If the above mentioned phenomenon occurs, add the hubs and reduce the load on the
Ethernet line applied on single hub.
OVERVIEW
2
SYSTEM
CONFIGURATION
3
SPECIFICATIONS
4
SETTINGS AND
PROCEDURES UP TO
OPERATION
5
2.6 System Configuration Precautions
2.6.3 Precautions for using multiple CPU system
2 - 17
HIGH SPEED DATA
LOGGER MODULE
6
7
DATA LOGGING
8
EVENT LOGGING
TOOL STARTUP
FUNCTION LIST
FUNCTION
FUNCTION
2
SYSTEM CONFIGURATION
2.7 Software Packages
The following software packages can be used for the High speed data logger module.
GX Works2Version 1.44W or later
GX DeveloperVersion 8.90U or later
GX LogViewerVersion 1.00A or later
SoftwareVersion
2 - 18
2.7 Software Packages
3
SPECIFICATIONS
CHAPTER 3SPECIFICATIONS
This chapter explains the specifications of the high speed data logger module.
For the general specifications of the high speed data logger module, refer to the following
manual.
QCPU User's Manual (Hardware Design, Maintenance and Inspection)
3.1 Performance Specifications
This section explains the performance specifications of the high speed data logger
module.
(1) Transmission and interface specifications
ItemSpecifications
Interface
Communication methodFull-duplex/half-duplex
Flow control
Ethernet
CompactFlash card
Number of occupied I/O points32 points/slot (I/O assignment: Intelli. 32 points)
Data transmission rate10Mbps100Mbps
Transmission methodBase band
No. of cascaded stages
Max. segment length
Supported function
Supply power voltage3.3 V±5%
Supply power capacityMaximum 150mA
Card sizeTYPE I card
Number of installable cards1 card
*1
*3
*1: The high speed data logger module distinguishes 10BASE-T from 100BASE-TX according to the
external device.
For connection to a hub without an auto-negotiation function, set the hub to half-duplex
communications mode.
*2: This item indicates the number of connectable stages for a repeater hub.
For the number of connectable stages for a switching hub, check with the manufacturer of the
switching hub to be used.
*3: Distance between a hub and node.
*4: For programmable controller CPU, everyday (once in 24 hours); for SNTP server, re-obtains the
time at the user specified interval.
*5: The internal current consumption with a CompactFlash card inserted to the module.
10BASE-T100BASE-TX
• Full-duplex: None (Does not support to the IEEE802.3x)
• Half-duplex: Back pressure congestion control
*2
Maximum 4 stagesMaximum 2 stages
100m
Auto-negotiation function supported (automatically distinguishes 10BASE-T /
100BASE-TX)
• Obtained from a programmable controller CPU (in multiple CPU system, CPU No.1)
or SNTP server
• Time accuracy after obtaining the time is a daily variation of ±9.504 seconds
Section 10.1 Time Synchronization Function
*5
0.50A
1
OVERVIEW
2
SYSTEM
CONFIGURATION
3
SPECIFICATIONS
4
SETTINGS AND
PROCEDURES UP TO
OPERATION
5
HIGH SPEED DATA
LOGGER MODULE
TOOL STARTUP
6
*4
FUNCTION LIST
7
DATA LOGGING
FUNCTION
8
3.1 Performance Specifications
EVENT LOGGING
FUNCTION
3 - 1
3
Data sampling
SPECIFICATIONS
(2) Function specifications
(a) Data sampling performance specifications
ItemSpecifications
Number of access target CPUsMaximum of 64 CPUs
• Sequence scan time synchronization
Data sampling interval
Point)
(
Amount of sampled
*2*3*4
data
*1
Data type
Data output format (CSV file)
Scaling
*5
*7
*1: The specification for target data sampling with the data logging function, event logging function, and
*2: The number of device points available for 1 piece of data depends on the data type.
*3: The total number of data logging, event logging, and report data.
*4: The amount of sampled data per single setting is as follows only when the creation trigger and
*5: The data type when reading data from the programmable controller CPU's device memory.
*6: The format when outputting data to a CSV file with data logging or event logging.
*7: A function to perform data scaling and offset calculations.
High speed data sampling
General data sampling
High speed data sampling
General data sampling
*6
report function.
• Data logging : logging target data, trigger condition data, period condition data,
file switching condition data, saved file name data, e-mail transmission data
• Event logging: monitoring data, period condition data, file switching condition data,
saved file name data, e-mail transmission data
• Report: current value data, creation trigger condition data, period condition data,
saved file name data, e-mail transmission data
current value data are not synchronized with the report setting.
Amount of data (per single setting): maximum of 65535, number of device points (per single
setting): maximum of 65535.
However, note that, number of device points per setting of data excluding current value data is as
follows.
High speed data sampling: maximum of 256, General data sampling: maximum of 4096
Binary files are output in the binary format.
Reports are output in Excel cell format.
• 1 to 32767 milliseconds (for trigger logging)
• 3 to 32767 milliseconds (for continuous logging)
• 0.1 to 0.9 seconds, 1 to 32767 seconds
• Time interval specification (specify hour/minute/second)
Overall amount of data: maximum of 8192 (per setting: 256)
•
•
Overall number of device points: maximum of 8192 (per setting: 256)
•
Overall amount of data: maximum of 16384 (per setting: 256)
•
Overall number of device points: maximum of 262144 (per setting: 4096)
•Bit
• Word (signed)
• Double word (signed)
• Word (unsigned)
• Double word (unsigned)
• Float (single precision)
• Float (double precision)
•16 bit BCD
•32 bit BCD
• String: 1 to 8192 characters
• Raw: 1 to 8192 bytes
•Bit
• Decimal format: 0 to 14 digits after the decimal point
• Exponential format: 0 to 14 digits after the decimal point
• Hexadecimal format
•String
•Raw
Basic arithmetic operations: calculations combining (*, /) and (+, -)
3 - 2
3.1 Performance Specifications
3
POINT
Data logging
SPECIFICATIONS
The data logging, event logging, and report functions of the high speed data
logger module are the best effort functions.
Since module processing time changes according to the settings and status of
other devices, it may not operate with the set data sampling interval.
Run the system by fully verifying the processing time of each function when
constructing it.
For processing time, refer to the following chapter.
Chapter 17 PROCESSING TIME
(b) Data logging performance specifications
ItemSpecifications
Number of settings
Logging type
File format
Period
Trigger conditions
Trigger logging
Number of logging
*5
lines
File switching timing
Number of save files1 to 65535
Maximum of 64 settings
• Continuous logging
• Trigger logging
• CSV file (extension: .CSV)
• Binary file (extension: .BIN)
Specify applicable period or exclusion period.
• Data condition: bit ON/OFF, compare data to constant value, compare data to data
• Date range: specify start and/or end month/day
• Time range: specify start and/or end hour/minute/second
• Day of week/week condition: specify days of the week and/or weeks
AND or OR combination of the above: up to 8 conditions
• Condition
• Condition execution count: 3 conditions
• Condition execution order (order and/or time conditions): up to 4 conditions
• Before trigger occurs: 0 to 65534 lines
• After trigger occurs: 1 to 65535 lines
The sum of lines of before and after trigger occurrence is up to 65535 lines.
• Number of lines (number of records) specification: 100 to 100000 lines
• File size specification: 10 to 16384 kilobytes
• Condition specification
• Trigger logging unit
*2
*3
*4
• Comparison: bit ON/OFF, compare data to constant value, compare data to data
• Time of day specification: specify month/day/hour/minute/second
• At module startup
AND or OR combination of the above: up to 8 conditions
*4
• Comparison: bit ON/OFF, compare data to constant value, compare data to data
• At the time of change of value
• Fixed cycle: 1 to 86400 seconds
• Time interval specification: specify hour/minute/second
• Time of day specification: specify month/day/hour/minute/second
• At module startup
AND or OR combination of the above: up to 8 conditions
*4
*4
*6
*4
(Continued on the next page)
1
OVERVIEW
2
SYSTEM
CONFIGURATION
3
SPECIFICATIONS
4
SETTINGS AND
PROCEDURES UP TO
OPERATION
5
HIGH SPEED DATA
LOGGER MODULE
TOOL STARTUP
6
FUNCTION LIST
7
3.1 Performance Specifications
DATA LOGGING
FUNCTION
8
EVENT LOGGING
FUNCTION
3 - 3
3
Event logging
SPECIFICATIONS
*2: Up to 64 settings can be configured for data logging, event logging, and report function combined.
Of these, up to 32 settings can be configured for data logging, event logging, and report function
when high speed data sampling is specified.
*3: By using the report function, data can be re-output in the Excel file format.
*4: When high speed data sampling is specified, period, trigger conditions, and file switching condition
combined up to 5 conditions.
When general data sampling is specified, period, trigger conditions, and file switching condition
combined up to 10 conditions.
*5: The number of logging lines setting is affected by the amount of memory (trigger buffer) where
sampled data are temporarily saved. Since the amount of trigger buffer has an upper limit, there
may be situations where the listed number of logging lines cannot be set.
Section 11.5.12 (3) Trigger buffer usage amount
*6: When using a high speed data logger module with a serial number whose first five digits are '14041'
or lower, the range of records is from 100 to 65535.
(c) Event logging performance specifications
ItemSpecifications
Number of settings
Number of eventsMaximum of 64 events per single event logging setting
File format
Event conditions
Period
File switching timing
Number of save files1 to 65535
*1: Up to 64 settings can be configured for data logging, event logging, and report function combined.
Of these, up to 32 settings can be configured for data logging, event logging, and report function
when high speed data sampling is specified.
*2: When high speed data sampling is specified, period and file switching condition combined up to 5
conditions.
When general data sampling is specified, period and file switching condition combined up to 10
conditions.
*3: When using a high speed data logger module with a serial number whose first five digits are '14041'
or lower, the range of records is from 100 to 65535.
Maximum of 64 settings
• CSV file (extension: .CSV)
• Binary file (extension: .BIN)
• Condition
• Comparison: bit ON/OFF, compare data to constant value, compare data to data
• At the time of change of value
AND or OR combination of the above: up to 4 conditions
• Condition execution count: 3 conditions
• Condition execution order (order and/or time conditions): up to 4 conditions
Specify applicable period or exclusion period.
• Data condition: bit ON/OFF, compare data to constant value, compare data to data
• Date range: specify start and/or end month/day
• Time range: specify start and/or end hour/minute/second
• Day of week/week condition: specify days of the week and/or weeks
AND or OR combination of the above: up to 8 conditions
• Number of lines (number of records) specification: 100 to 100000 lines
• File size specification: 10 to 16384 kilobytes
• Condition
• Comparison: bit ON/OFF, compare data to constant value, compare data to data
• At the time of change of value
• Fixed cycle: 1 to 86400 seconds
• Time interval specification: specify hour/minute/second
• Time of day specification: specify month/day/hour/minute/second
• At module startup
AND or OR combination of the above: up to 8 conditions
*1
(From the previous page)
*2
*3
*2
3 - 4
3.1 Performance Specifications
3
Report
SPECIFICATIONS
(d) Report function performance specifications
ItemSpecifications
Number of settings
File formatExcel format (extension: .xls)
Output data type
Amount of output data64 layouts per single report setting, 65535 cells in total
Creation trigger conditions
Period
Layout file sizeMaximum of 10MB (total of all report settings)
Number of save files1 to 65535
*1: Up to 64 settings can be configured for data logging, event logging, and report function combined.
Of these, up to 32 settings can be configured for data logging, event logging, and report function
when high speed data sampling is specified.
*2: Only binary format data logging can be output to report function.
*3: When high speed data sampling is specified, period and creation trigger conditions combined up to
5 conditions.
When general data sampling is specified, period and creation trigger conditions combined up to 10
conditions.
Maximum of 64 settings
• Data inside data logging file
• Current value data
• Creation time
• Condition
• Comparison: bit ON/OFF, compare data to constant value, compare data to data
• At the time of change of value
• Fixed cycle: 1 to 86400 seconds
• Time interval specification: specify hour/minute/second
• Time of day specification: specify month/day/hour/minute/second
• At module startup
• At the time of the data logging file is switched
AND or OR combination of the above: up to 8 conditions
• Condition execution count: 3 conditions
• Condition execution order (order and/or time conditions): up to 4 conditions
Specify applicable period or exclusion period.
• Data condition: bit ON/OFF, compare data to constant value, compare data to data
• Date range: specify start and/or end month/day
• Time range: specify start and/or end hour/minute/second
• Day of week/week condition: specify days of the week and/or weeks
AND or OR combination of the above: up to 8 conditions
*1
*2
1
OVERVIEW
2
SYSTEM
CONFIGURATION
3
*3
*3
*3
SPECIFICATIONS
4
*3
SETTINGS AND
PROCEDURES UP TO
OPERATION
5
HIGH SPEED DATA
LOGGER MODULE
TOOL STARTUP
6
3.1 Performance Specifications
FUNCTION LIST
7
DATA LOGGING
FUNCTION
8
EVENT LOGGING
FUNCTION
3 - 5
3
E-mail
FTP server
FTP client
Recipe
SPECIFICATIONS
(e) Other performance specifications
ItemSpecifications
Application
Subject
Body
Attachment
Attachment formatMIME format
MIME version1.0
Communications with mail
server
Target addressMaximum of 16 groups
Operability verified e-mail client software
Application
*1
*3
Operability verified FTP client software
Session count
ApplicationTransfer saved files
Operability verified FTP server software
Number of dataMaximum of 256 data
Saved file (CSV, binary, or Excel file)
Maximum of 512KB
Port no. 25, 587, other (1 to 65535)
Authentication
method
FTP client software. For details of supported FTP commands, refer to Appendix 9.
from FTP client software.
FTP client software may use multiple connections per single access session.
A function to access a personal computer's FTP server software from the high speed data logger module (FTP client).
• No authentication
• SMTP-AUTH (PLAIN, LOGIN, CRAM-MD5)
• POP before SMTP
•Microsoft
•Microsoft
Read and delete saved files
Write, read, and delete recipe files
•Microsoft
• Windows
• Windows
• Windows
• Windows
• Windows
10
Microsoft
•Bit
• Word [signed]
• Double word [signed]
• Word [unsigned]
• Double word [unsigned]
• FLOAT [single precision]
• FLOAT [double precision]
• 16bit BCD
• 32bit BCD
CSV file (extension: .csv)
Maximum of 256 files
®
Outlook® Express 6.0
®
Windows® Mail 6.0
®
Internet Explorer® 6.0
®
Internet Explorer® 7.0
®
Internet Explorer® 8.0
®
Internet Explorer® 9.0
®
Internet Explorer® 10.0
®
Internet Explorer® 11.0
®
Internet Information Services
3 - 6
3.1 Performance Specifications
3
SPECIFICATIONS
3.2 Accessible Routes and Devices
This section explains accessible routes and devices.
*1: Applicable when using QJ81DL96 with a serial number whose first five digits are '14122' or higher.
*2: Only the own station can be accessed. ( Section 2.6.1 Precautions when using Redundant
*3: Applicable when using a Q12DCCPU-V with a serial number whose first five digits are ‘12042’ or
This section explains single network accessible routes.
For CC-Link IE, MELSECNET/10(H), Ethernet
High speed
data logger module
Network module
Network 2-7
Request
source
Network 1
Relay
station
Network communication route
Relay
station
The following shows the CPU modules that can be accessed on the network
communication routes.
........ The control CPU of the high speed data logger module and
the network module must be set to QCPU (Q mode).
............ The control CPU of the network module must be set to
QCPU (Q mode).
..For accessible programmable controller CPUs, refer to the
following table.
Access target CPU (Programmable controller series)
Network communication route
CC-Link IE Control, MELSECNET/10(H)
CC-Link IE Field
Ethernet (via own Ethernet module)
Ethernet (via the high speed data logger module's built-in
Ethernet port)
*13
*1: The control CPU of the access target network module must be set to QCPU (Q mode).
*2: When the control CPU of the access target network module is a C Controller module, only the
control CPU of the network module can be accessed.
*3: Cannot be accessed when the last network route (Network 8) is a CC-Link IE Field or an Ethernet.
*4: Use Universal model QCPU with a serial number whose first five digits are '12012' or higher.
*5: Cannot be accessed when the access target CPU is Q12DCCPU-V.
*6: When accessing a programmable controller CPU via Ethernet, use an Ethernet module.
The Ethernet port of a built-in Ethernet port programmable controller CPU cannot be used
*7: For the network number and station number, set them to the parameter setting of the Q series-
compatible E71 on the access target CPU side.
Also, set 'Station No. <-> IP information' in the parameter settings of the Q series-compatible E71.
For 'Station No. <-> IP information system', specify the IP address computation system, Table
exchange system, or both.
Example of accessible
module configuration
*6
High Speed
Data Logger
module
Ethernet
module
Programmable
controller CPU
(Q mode)
Ethernet
module
QCPU
*1
*4
*7*8
*9*10
Example of inaccessible
module configuration
High Speed
Data Logger
module
LCPU
: Accessible : Inaccessible
Ethernet
module
Network 8
*10
Access target
C Controller
module
Programmable
controller CPU
(Built-in Ethernet port)
CPU
*3
*5
*11*12
.
*2
3 - 8
Ethernet Ethernet
3.2 Accessible Routes and Devices
3
C24 multi-drop
CC-Link
High speed
data logger module
Request
source
Network module
Network
communication
route
Access target CPU
Request source
Access target CPU
SPECIFICATIONS
*8: The Ethernet port of a built-in Ethernet port QCPU cannot be accessed.
*9: The Ethernet port of a built-in Ethernet port QCPU and an Ethernet module can be accessed.
*10: UDP (MELSOFT Connection) must be added to the open setting of a built-in Ethernet port for the
access target CPU.
*11: For Q24DHCCPU-V, the system Ethernet port (S CH1) can be accessed.
*12: For Q12DCCPU-V, setting to allow MELSOFT Connection in the open setting of the built-in
Ethernet port is required.
*13: The Ethernet mounted station, built-in Ethernet CPU, or C controller module can be accessed.
The access via a relay station cannot be performed.
For CC-Link, C24
The following shows the CPU modules that can be accessed on the network
communication routes.
........ The control CPU of the high speed data logger module and
the network module must be set to QCPU (Q mode).
.. For accessible programmable controller CPUs, refer to the
following table.
Access target CPU (Programmable controller series)
Network communication route
CC-Link
C24
*1: The control CPU of the access target network module must be set to QCPU (Q mode).
*2: When the control CPU of the access target network module is a C Controller module, only the
control CPU of the network module can be accessed.
QCPU
(Q mode)
*1
LCPU
: Accessible : Inaccessible
C Controller
*2
module
1
OVERVIEW
2
SYSTEM
CONFIGURATION
3
SPECIFICATIONS
4
SETTINGS AND
PROCEDURES UP TO
OPERATION
5
HIGH SPEED DATA
LOGGER MODULE
TOOL STARTUP
6
3.2 Accessible Routes and Devices
FUNCTION LIST
7
DATA LOGGING
FUNCTION
8
EVENT LOGGING
FUNCTION
3 - 9
3
Network 8Network 1
Network 2-7
C24 multi-drop
CC-Link
High speed
data logger module
Network communication route
Co-existence
network
communication
route
Relay
station
Relay
station
Relay
station
Access target
CPU
Network module
Request
source
Request source
Relay station
Access target CPU
SPECIFICATIONS
(b) Co-existence network
This section explains co-existence network accessible routes.
For CC-Link IE , MELSECNET/10(H), Ethernet
The following shows the CPU modules that can be accessed on the network
communication routes and co-existence network communication routes.
........ The control CPU of the high speed data logger module and
the network module must be set to QCPU (Q mode).
............ The control CPU of the network module must be set to
QCPU (Q mode).
..For accessible programmable controller CPUs, refer to the
following table.
CC-Link IE, MELSECNET/10(H)
Ethernet (via own Ethernet module)
Network communication route
*4
*1: The control CPU of the access target network module must be set to QCPU (Q mode).
*2: When the control CPU of the access target network module is a C Controller module, only the
control CPU of the network module can be accessed.
*3: Cannot be accessed when the last network route (Network 8) is a CC-Link IE Field or an Ethernet.
*4: When accessing a programmable controller CPU via Ethernet, use an Ethernet module.
The Ethernet port of a built-in Ethernet port programmable controller CPU cannot be used.
Example of accessible
module configuration
*5: For the network number and station number, set them to the parameter setting of the Q series-
compatible E71 on the access target CPU side.
Also, set 'Station No. <-> IP information' in the parameter settings of the Q series-compatible E71.
For 'Station No. <-> IP information system', specify the IP address computation system, Table
exchange system, or both.
High Speed
Data Logger
module
Co-existence
network
communication
route
CC-Link
C24
CC-Link
C24
Programmable
Ethernet
module
controller CPU
Ethernet Ethernet
Access target CPU (Programmable controller series)
QCPU
(Q mode)
Ethernet
module
*1
*5
*5
Example of inaccessible
module configuration
High Speed
Data Logger
module
LCPU
: Accessible : Inaccessible
Programmable
Ethernet
module
controller CPU
(Built-in Ethernet port)
C Controller
*2
module
*3
3 - 10
3.2 Accessible Routes and Devices
3
Network 8Network 1
Network 2-7
C24 multi-drop
CC-Link
High speed data
logger module
Network
communication
route
Co-existence network communication route
Relay
station
Relay
station
Relay
station
Access target
CPU
Request
source
Network module
Request source
Relay station
Access target CPU
SPECIFICATIONS
1
For CC-Link, C24
OVERVIEW
2
Network communication route
CC-Link, C24
The following shows the CPU modules that can be accessed on the network
communication routes and co-existence network communication routes.
........ The control CPU of the high speed data logger module and
the network module must be set to QCPU (Q mode).
............ The control CPU of the network module must be set to
QCPU (Q mode).
.. For accessible programmable controller CPUs, refer to the
following table.
Co-existence
network
communication
route
CC-Link IE
Control
CC-Link IE Field
MELSECNET/
10(H)
Ethernet
*1: The control CPU of the access target network module must be set to QCPU (Q mode).
*2: When the control CPU of the access target network module is a C Controller module, only the
control CPU of the network module can be accessed.
*3: Cannot be accessed when the last network route (Network 8) is a CC-Link IE Field or an Ethernet.
*4: Use Universal model QCPU with a serial number whose first five digits are '12012' or higher.
Example of accessible
module configuration
High Speed
Data Logger
module
Ethernet
module
*6
Programmable
controller CPU
Access target CPU (Programmable controller series)
QCPU
(Q mode)
Ethernet
module
*1
*4
*7
Example of inaccessible
module configuration
High Speed
Data Logger
module
LCPU
: Accessible : Inaccessible
Ethernet
module
C Controller
module
Programmable
controller CPU
(Built-in Ethernet port)
*2
*3
*5
SYSTEM
CONFIGURATION
3
SPECIFICATIONS
4
SETTINGS AND
PROCEDURES UP TO
OPERATION
5
HIGH SPEED DATA
LOGGER MODULE
TOOL STARTUP
6
FUNCTION LIST
7
Ethernet Ethernet
*5: Cannot be accessed when the access target CPU is Q12DCCPU-V.
*6: When accessing a programmable controller CPU via Ethernet, use an Ethernet module.
The Ethernet port of a built-in Ethernet port programmable controller CPU cannot be used.
*7: For the network number and station number, set them to the parameter setting of the Q series-
compatible E71 on the access target CPU side.
Also, set 'Station No. <-> IP information' in the parameter settings of the Q series-compatible E71.
For 'Station No. <-> IP information system', specify the IP address computation system, Table
exchange system, or both.
3.2 Accessible Routes and Devices
3 - 11
DATA LOGGING
FUNCTION
8
EVENT LOGGING
FUNCTION
3
SPECIFICATIONS
(3) Accessible devices
For details of each device, refer to the following manuals.
QnUCPU User's Manual (Function Explanation, Program Fundamentals)
MELSEC-L CPU Module User's Manual (Function Explanation, Program Fundamentals)
(a) QCPU (Q mode)
Function input (FX)
Function output (FY)
Function register (FD)
Special relay (SM)
Special register (SD)
Input relay (X)
Output relay (Y)
Internal relay (M)
Latch relay (L)
Annunciator (F)
Edge relay (V)
Link relay (B)
Data register (D)
Link register (W)
Extended internal relay (M)
Extended data register (D)
Extended link register (W)
Timer
Counter
Retentive timer
Link special relay (SB)
Link special register (SW)
Step relay (S)
Direct input (DX)
Direct output (DY)
Index register(Z)
File register
Link direct
device
Intelligent function module device (Un\G)
Cyclic transmission area deviceCPU shared memory (U3En\G)
*2
Device*1 (device name)
*2
QCPU general
data sampling
Contact (TS)
Coil (TC)
Current value (T/TN)
Contact (CS)
Coil (CC)
Current value (C/CN)
Contact (SS)
Coil (SC)
Current value (ST/SN)
(R)
(ZR)
Link input (Jn\X)
Link output (Jn\Y)
Link relay (Jn\B)
Link special relay (Jn\SB)
Link register (Jn\W)
Link special register (Jn\SW)
*3
*3
: Accessible : Inaccessible
QCPU high speed
data sampling
*4
*4
3 - 12
3.2 Accessible Routes and Devices
3
SPECIFICATIONS
*1: The local devices of the Q series programmable controller CPUs and file registers for individual
programs cannot be accessed by specifying the program name.
Do not use local devices and file registers for individual programs since they may not be read/
written correctly.
*2: M and L devices are in the same region, regardless of the parameter device setting.
*3: When using Q00JCPU, Q00UJCPU, access is not possible.
*4: When accessed outside the range of the file register (ZR) region, the sampled value is -1 (FFFF
H).
1
2
3
4
SYSTEM
OVERVIEW
CONFIGURATION
SPECIFICATIONS
SETTINGS AND
HIGH SPEED DATA
PROCEDURES UP TO
5
LOGGER MODULE
6
7
DATA LOGGING
8
OPERATION
TOOL STARTUP
FUNCTION LIST
FUNCTION
3.2 Accessible Routes and Devices
EVENT LOGGING
FUNCTION
3 - 13
3
SPECIFICATIONS
(b) LCPU
Function input (FX)
Function output (FY)
Function register (FD)
Special relay (SM)
Special register (SD)
Input relay (X)
Output relay (Y)
Internal relay (M)
Latch relay (L)
Annunciator (F)
Edge relay (V)
Link relay (B)
Data register (D)
Link register (W)
Extended internal relay (M)
Extended data register (D)
Extended link register (W)
Timer
Counter
Retentive timer
Link special relay (SB)
Link special register (SW)
Step relay (S)
Direct input (DX)
Direct output (DY)
Index register(Z)
File register
Link direct
device
Intelligent function module device (Un\G)
Device*1 (device name)
*2
*2
Contact (TS)
Coil (TC)
Current value (T/TN)
Contact (CS)
Coil (CC)
Current value (C/CN)
Contact (SS)
Coil (SC)
Current value (ST/SN)
(R)
(ZR)
Link input (Jn\X)
Link output (Jn\Y)
Link relay (Jn\B)
Link special relay (Jn\SB)
Link register (Jn\W)
Link special register (Jn\SW)
LCPU general data
sampling
3 - 14
: Accessible : Inaccessible
*1: The local devices of the L series programmable controller CPUs and file registers for individual
programs cannot be accessed by specifying the program name.
Do not use local devices and file registers for individual programs since they may not be read/
written correctly.
*2: M and L devices are in the same region, regardless of the parameter device setting.
3.2 Accessible Routes and Devices
3
SPECIFICATIONS
(c) C Controller module
Function input (FX)
Function output (FY)
Function register (FD)
Special relay (SM)
Special register (SD)
Input relay (X)
Output relay (Y)
Internal relay (M)
Latch relay (L)
Annunciator (F)
Edge relay (V)
Link relay (B)
Data register (D)
Link register (W)
Extended internal relay (M)
Extended data register (D)
Extended link register (W)
Timer
Counter
Retentive timer
Link special relay (SB)
Link special register (SW)
Step relay (S)
Direct input (DX)
Direct output (DY)
Index register(Z)
File register
Link direct
device
Intelligent function module device (Un\G)
Cyclic transmission area deviceCPU shared memory (U3En\G)
*1:
For Q12DCCPU-V, only modules with a serial number whose first five digits are '12042' or higher are
accessible.
*2:
For Q12DCCPU-V, specify "Use device function" on C Controller module.
*3: For Q12DCCPU-V, use Q12DCCPU-V (Extended mode).
Device*1 (device name)
Contact (TS)
Coil (TC)
Current value (T/TN)
Contact (CS)
Coil (CC)
Current value (C/CN)
Contact (SS)
Coil (SC)
Current value (ST/SN)
(R)
(ZR)
Link input (Jn\X)
Link output (Jn\Y)
Link relay (Jn\B)
Link special relay (Jn\SB)
Link register (Jn\W)
Link special register (Jn\SW)
C Controller module
general data sampling
*1*2
*1*2
*1
*1
*1*2
*3
*1*2
*3
*1*2
*1*2
*1
*1
*1
*1
*1
*1
*1
*1
: Accessible : Inaccessible
SETTINGS AND
HIGH SPEED DATA
1
2
SYSTEM
3
4
PROCEDURES UP TO
5
LOGGER MODULE
6
7
DATA LOGGING
8
OVERVIEW
CONFIGURATION
SPECIFICATIONS
OPERATION
TOOL STARTUP
FUNCTION LIST
FUNCTION
3.2 Accessible Routes and Devices
EVENT LOGGING
FUNCTION
3 - 15
3
POINT
SPECIFICATIONS
(4) Device bit specification/digit specification
Special relay (SM)-
Special register (SD)-
Input relay (X)-
Output relay (Y)-
Internal relay (M)-
Latch relay (L)-
Annunciator (F)-
Edge relay (V)-
Link relay (B)-
Data register (D)-
Link register (W)-
Timer
Counter
Retentive timer
Link special relay (SB)-
Link special register (SW)-
Index register (Z)-
Contact (TS)-
Coil (TC)-
Current value (T/TN)-
Contact (CS)-
Coil (CC)-
Current value (C/CN)-
Contact (SS)-
Coil (SC)-
Current value (ST/SN)-
(R)-
(ZR)-
Link input (Jn\X)-
Link output (Jn\Y)-
Link relay (Jn\B)-
Link special relay (Jn\SB)-
Link register (Jn\W)-
Link special register (Jn\SW)-
3 - 16
: Specifiable : Not specifiable (CPU restriction) : Not specifiable (device type restriction)
(1) When using the high speed data sampling function, bit specified/digit
specified devices cannot be used.
(2) Bit specified/digit specified devices cannot be used in current value data for
reports.
(3) When using the recipe function, bit specified/digit specified devices cannot be
used.
3.2 Accessible Routes and Devices
3
SPECIFICATIONS
(5) Access units
The following table explains the number of device points (access units) that can be
accessed in a single process when sampling a programmable controller CPU's device
values.
When the access units are lower than the number of sampled device points, the
module sampled the device values in the same sequence scan.
When the access units exceed the number of sampled device points, device values
are sampled over multiple sequence scans, so there is a possibility of data separation
(the mixture of the current device value and the old device value) occurrence.
If data separation must be prevented, set the number of devices sampled at one time
to less than the access units, or set the module to use high speed data sampling.
1
2
3
OVERVIEW
SYSTEM
CONFIGURATION
CPU typeHigh speed data samplingGeneral data sampling
*1: Current value data when "Synchronize create trigger and current value data" is not checked.
When checked, refer to the access units for the specified data sampling method (high speed or
general data sampling).
*2: The high speed data sampling function can be used only when using a programmable controller
with a serial number whose first five digits are '11012' or higher.
Samples all device values
in the same sequence
scan.
Cannot be set.
Report current value
*1
data
96 points960 points
32 points240 points
SETTINGS AND
HIGH SPEED DATA
4
PROCEDURES UP TO
5
LOGGER MODULE
6
7
DATA LOGGING
8
SPECIFICATIONS
OPERATION
TOOL STARTUP
FUNCTION LIST
FUNCTION
3.2 Accessible Routes and Devices
EVENT LOGGING
FUNCTION
3 - 17
3
SPECIFICATIONS
3.3 I/O Signals for the Programmable Controller CPU
3.3.1 I/O signal list
The following table shows the list of high speed data logger module I/O signals for the
programmable controller CPU.
The I/O signal allocation is shown for when the high speed data logger module is mounted
on the 0 slot of the main base unit.
If the high speed data logger module is mounted on a slot other than slot 0, use by
substituting the I/O signals of the slot on which the module is mounted.
Device X indicates an input signal from the high speed data logger module to the
programmable controller CPU and device Y indicates an output signal from the
programmable controller CPU to the high speed data logger module.
Signal direction High speed data logger module programmable
controller CPU
Device No.Signal nameDevice No.Signal name
X0
X1
X2
X3Use prohibitedY3
X4
X5
X6
X7Y7
X8Y8
X9Y9
XAYA
XB
XC
XDYD
XEYE
XFYF
X10
Module READY
ON: Module prepared OFF: CompactFlash card status
ON: Inserted OFF: Not inserted
File access status
ON: Stopped OFF: Running
Network connection status
ON: Connected OFF: Not connected
Module operating status
ON: Running OFF: Stopped
Use prohibited
SNTP time synchronization timing
ON: Synchronizing complete OFF: -
Use prohibited
ERR. LED status
ON: Illuminated, flashing OFF: Off
Signal direction Programmable controller CPU high speed data
logger module
Y0
Use prohibited
Y1
Y2
Y4
Y5
Y6
YB
YC
Y10
File access stop request
ON: Stop request OFF: Clear file access stop request
ON: Clear stop request OFF: -
Use prohibited
Programmable controller CPU time synchronization
request
ON: Synchronization request OFF: -
Use prohibited
Error clear request
ON: Error clear request OFF: -
(Continued on the next page)
3 - 18
3.3 I/O Signals for the Programmable Controller CPU
3.3.1 I/O signal list
3
POINT
Signal direction High speed data logger module programmable
Device No.Signal nameDevice No.Signal name
SPECIFICATIONS
Signal direction Programmable controller CPU high speed data
controller CPU
X11Use prohibitedY11
X12
X13
X14
X15Use prohibitedY15
X16
X17
X18
X19
X1A
X1B
X1C
X1D
X1E
X1F
Data logging error
ON: Error OFF: Normal
Event logging error
ON: Error OFF: Normal
Report creation error
ON: Error OFF: Normal
Access target CPU error
ON: Error OFF: Normal
E-mail transmission error
ON: Error OFF: Normal
FTP transfer error
ON: Error OFF: Normal
Other error
ON: Error OFF: Normal
High speed data sampling failure
ON: Occurred OFF: No occurrence
Processing overload occurrence
ON: Occurred OFF: No occurrence
Trigger reoccurrence
ON: Occurred OFF: No occurrence
Creation trigger reoccurrence
ON: Occurred OFF: No occurrence
General data sampling delay occurrence
ON: Occurred OFF: No occurrence
Watchdog timer error
ON: Error OFF: Normal
Y12
Y13
Y14
Y16
Y17
Y18
Y19
Y1A
Y1B
Y1C
Y1D
Y1E
Y1F
(From the previous page)
logger module
Use prohibited
1
OVERVIEW
2
SYSTEM
CONFIGURATION
3
SPECIFICATIONS
4
SETTINGS AND
PROCEDURES UP TO
OPERATION
5
For I/O signals for the programmable controller CPU, do not output (ON) a 'Use
prohibited' signal.
Doing so may cause the programmable controller system to malfunction.
3.3 I/O Signals for the Programmable Controller CPU
3.3.1 I/O signal list
3 - 19
HIGH SPEED DATA
LOGGER MODULE
6
7
DATA LOGGING
8
EVENT LOGGING
TOOL STARTUP
FUNCTION LIST
FUNCTION
FUNCTION
3
SPECIFICATIONS
3.3.2 I/O signal details
Device
No.
X0Module READY
CompactFlash card
X1
status
Signal nameDescription
This section explains details about the I/O signals for the high speed data logger module.
(1) Input signal details
Turns ON when the high speed data logger module becomes ready after the programmable
controller is powered ON from OFF, or the programmable controller CPU is reset.
(1) Turns ON when the CompactFlash card is inserted and the file access status (X2) is OFF.
(2) Turns OFF when the CompactFlash card is not inserted or the file access status (X2) is ON.
(1) Turns ON while file access is stopped.
(a) The following operations are available while file access is stopped.
(b) While file access is stopped, the module has the following status.
• Reading from or writing to the CompactFlash card is stopped.
• Module operating status is stopped.
(2) Turns OFF during file access operation.
X2File access status
X4Network connection status
File access stop request (Y2)
Clear file access stop request (Y3)
File access status (X2)
Module operating status (X5)
CompactFlash card status (X1)
Turns ON when the high speed data logger module becomes ready after the programmable
controller is powered ON from OFF, or the programmable controller CPU is reset.
(Operating)
Replace CompactFlash card
Power OFF programmable controller
(Stopped)
(Operating)
Restart module
operation or
update settings
(Continued on the next page)
3 - 20
3.3 I/O Signals for the Programmable Controller CPU
3.3.2 I/O signal details
3
Time synchronization
with SNTP server
Time synchronization
with SNTP server
Time synchronization
Time synchronization result
(Buffer memory
address: 101-107)
Time synchronization
setting status
(Buffer memory address: 100)
SNTP time synchronization
timing (XB)
Time data
set
Time data
set
(First time)
(Initial
value 0)
(Initial
value 0)
(Initial
value OFF)
1 second
1 second
Device
No.
X5Module operating status
SPECIFICATIONS
Signal nameDescription
(From the previous page)
Turns ON while the data logging function, event logging function, and report function are
(1)
operating.
(2)
Turns OFF while the data logging function, event logging function, and report function are
stopped.
(3) Stop status in the following situations
(a) When module operation is stopped with the Configuration Tool.
(b) When settings are not written to the high speed data logger module.
(c) When a module stop error occurs.
(d) When the file access status has stopped (X2 is ON).
(4) Data logging, event logging, and report logging function operating status are restored with
the follow procedures.
(a) When module operation is stopped with the Configuration Tool
Restart module operation with the Configuration Tool.
Section 13.1.1 Module diagnostics
(b) When settings are not written to the high speed data logger module
1. Write settings to the high speed data logger module with the Configuration Tool.
Section 12.3 Writing Data
2. Update the settings.
Section 13.1.1 Module diagnostics
(c) When a module stop error occurs
1. Clear the error with the Configuration Tool ( Section 13.1.1 Module
diagnostics) or error clear request (Y10).
2. Update the settings with the Configuration Tool.
Section 13.1.1 Module diagnostics
(d) When the file access status has stopped (X2 is ON)
1. Turn clear file access stop request (Y3) ON.
File access status is operating (X2 is OFF).
2. Restart module operation or update the settings with the Configuration Tool.
Section 13.1.1 Module diagnostics
(1) When "Synchronize with SNTP" is selected in "Time synchronization setting", turns ON after
the time synchronization succeeds and the time is stored in the buffer memory.
(2) While XB is ON, the time data can be read from the time synchronization result (buffer
memory address: 101-107).
(3) Turns OFF 1 second after XB turns ON.
*1
*1
*1
1
OVERVIEW
2
SYSTEM
CONFIGURATION
3
SPECIFICATIONS
4
SETTINGS AND
PROCEDURES UP TO
OPERATION
5
HIGH SPEED DATA
LOGGER MODULE
TOOL STARTUP
6
XB
SNTP time synchronization
timing
*1: The operating status can also be restored by power OFF to ON or by resetting the CPU module.
3.3 I/O Signals for the Programmable Controller CPU
3.3.2 I/O signal details
(Continued on the next page)
3 - 21
FUNCTION LIST
7
DATA LOGGING
FUNCTION
8
EVENT LOGGING
FUNCTION
3
Device
No.
X10ERR. LED status
X12Data logging error
X13Event logging error
X14Report creation error
X16Access target CPU error
X17E-mail transmission error
X18FTP transfer error
X19Other errors
X1A
X1B
X1CTrigger reoccurrence
X1DCreation trigger reoccurrence
X1E
X1FWatchdog timer errorTurns ON when a watchdog timer error occurs.
SPECIFICATIONS
Signal nameDescription
High speed data sampling
failure
Processing overload
occurrence
General data sampling delay
occurrence
(1) Turns ON while the ERR. LED is ON (during a module continuation error) or flashing (during
a module stop error).
(2) ERR. LED is turned OFF by turning ON error clear request (Y10) when ERR. LED is ON.
(However, this is not possible while ERR. LED is flashing.)
(3) While ERR. LED is ON or flashing (when X10 is ON), X12 to X14, X16 to X19 (one or many)
turn ON.
(1) Turns ON when an error regarding data logging occurs.
(2) When this device is ON, the error code is stored in the data logging status area
( Section 3.4.11).
(3) Turns OFF when the error clear request (Y10) is turned ON.
(1) Turns ON when an error regarding event logging occurs.
(2) When this device is ON, the error code is stored in the event logging status area
( Section 3.4.12).
(3) Turns OFF when the error clear request (Y10) is turned ON.
(1) Turns ON when an error regarding reports occurs.
(2) When this device is ON, the error code is stored in the report creation status area
( Section 3.4.13).
(3) Turns OFF when the error clear request (Y10) is turned ON.
(1) Turns ON when a communication error occurs with the access target CPU.
(2) When this device is ON, the error code is stored in the access target CPU setting status
area ( Section 3.4.10).
(3) Turns OFF when the error clear request (Y10) is turned ON.
(1) Turns ON when an error regarding e-mail transmission occurs.
(2) When this device is ON, the error code is stored in the e-mail transmission status area
( Section 3.4.14).
(3) Turns OFF when the error clear request (Y10) is turned ON.
(1) Turns ON when an error regarding FTP transfers occurs.
(2) When this device is ON, the error code is stored in the FTP client status (PUT) area
( Section 3.4.16).
(3) Turns OFF when the error clear request (Y10) is turned ON.
(1) Turns ON when an error not corresponding to X12 to X14 or X16 to X18 occurs.
(2) When this device is ON, the error code is stored in the error log area ( Section 3.4.7).
(3) Turns OFF when the error clear request (Y10) is turned ON. (Only in case of a module
continuation error)
(1) Turns ON when a high speed data sampling failure occurs in data logging, event logging, or
report function. ( Chapter 17 PROCESSING TIME)
(2) Turns OFF by updating the settings.
(1) Turns ON when processing overload occurs in data logging, event logging, or report
function. ( Chapter 17 PROCESSING TIME)
(2) Turns OFF by updating the settings.
(1) Turns ON when the creation trigger reoccurs with data logging.
( Chapter 17 PROCESSING TIME)
(2) Turns OFF by updating the settings.
(1) Turns ON when the creation trigger reoccurs with report function.
( Chapter 17 PROCESSING TIME)
(2) Turns OFF by updating the settings.
(1) Turns ON when a general data sampling delay has occurred in data logging, event logging,
or report function. ( Chapter 17 PROCESSING TIME)
(2) Turns OFF by either of the following.
• When the settings are updated
• When a value greater than the general data sampling delay time (maximum) is set in the
allowed general data sampling delay time in the buffer memory.
(From the previous page)
3 - 22
3.3 I/O Signals for the Programmable Controller CPU
3.3.2 I/O signal details
3
POINT
Replace CompactFlash card
Power OFF programmable controller
(Operating)
(Operating)
(Stopped)
File access stop request (Y2)
Clear file access stop request (Y3)
File access status (X2)
CompactFlash card status (X1)
SPECIFICATIONS
(2) Output signal details
Device
No.
Y2File access stop request
Signal nameDescription
If turned ON, stops file access.
1
2
3
OVERVIEW
SYSTEM
CONFIGURATION
Clear file access
Y3
stop request
Programmable controller CPU
YB
time synchronization request
Y10Error clear request
*1
If turned ON, clears the file access stop.
(1) When the time synchronization setting is set to programmable controller CPU
synchronization, if turned on, the module synchronizes with the programmable controller
CPU time.
(2) Do not use when the time synchronization setting is set to "Synchronize with SNTP".
If turned ON when a module error has occurred, the following are executed.
• ERR.LED is turned OFF
• X10, X12 to X14, X16 to X19 are turned OFF
• Most recent error code is cleared
Section 18.1.1 Checking error codes
*1: When the auto logging function is enabled, the logging is restarted by turning Y3 ON.
*2: When the time data of the programmable controller CPU is updated,
wait for more than one second, and turn YB ON.
*2
(For ON/OFF timing, refer to the row for Y2)
Output signal is enabled when the signal is changed from OFF to ON.
When enabling the output signal again, turn the signal OFF from ON or vice versa.
SPECIFICATIONS
4
SETTINGS AND
PROCEDURES UP TO
OPERATION
5
HIGH SPEED DATA
LOGGER MODULE
TOOL STARTUP
6
FUNCTION LIST
7
3.3 I/O Signals for the Programmable Controller CPU
3.3.2 I/O signal details
3 - 23
DATA LOGGING
FUNCTION
8
EVENT LOGGING
FUNCTION
3
POINT
SPECIFICATIONS
3.4 Buffer Memory List
The following table shows the buffer memory list.
Address (Decimal)ApplicationReference
0 to 20Module status areaSection 3.4.1
21 to 25CompactFlash card information areaSection 3.4.2
47 to 64Network connection status areaSection 3.4.3
70 to 80Common setting status areaSection 3.4.4
100 to 109Time synchronization information areaSection 3.4.5
140 to 145Current error areaSection 3.4.6
150 to 247Error log areaSection 3.4.7
800 to 805General data sampling delay time areaSection 3.4.8
810 to 841Recipe file areaSection 3.4.9
1500 to 1593Access target CPU setting status areaSection 3.4.10
2000 to 2989Data logging status areaSection 3.4.11
3000 to 3989Event logging status areaSection 3.4.12
4000 to 4989Report creation status areaSection 3.4.13
5000 to 5992E-mail transmission status areaSection 3.4.14
6000 to 6001FTP server status areaSection 3.4.15
6002 to 7457FTP client status (PUT) areaSection 3.4.16
7999FTP client setting areaSection 3.4.17
10000 to 14095Event logging areaSection 3.4.18
(1) Addresses not listed in the table above are areas used by the system.
Do not use these areas as there is a risk of malfunction when writing to them.
(2) The values stored in the buffer memory are cleared when the programmable
controller is powered ON from OFF, or the programmable controller CPU is
reset.
3.4.1 Module status area (address: 0 to 20)
The status of the high speed data logger module can be checked in this area.
Decimal address
(Hexadecimal)
0 (0H)RUN LED status0: OFF 1: ON 2: FlashingR0
1 (1H)ERR. LED status0: OFF 1: ON 2: FlashingR0
2 (2H)CF LED status0: OFF 1: ON 2: FlashingR0
3 (3H)Switch 1 status
4 (4H)Switch 2 status
5 (5H)Switch 3 status15 to 255 (seconds): Response monitoring timeR0
Represented as a double word (32-bit value).
(unit: KB)
Represented as a double word (32-bit value).
(unit: KB)
Represented as a word (16-bit value).
(unit: %)
R: Read-only
Initial
value
R0
R0
R0
3.4.3 Network connection status area (address: 47 to 64)
The status of the high speed data logger module's connection to a network can be
checked in this area.
Decimal address
(Hexadecimal)
47 to 54 (2FH to 36H)IP address (string notation)
55 to 56 (37H to 38H)IP address
57 to 58 (39H to 3AH)Subnet mask
59 to 60 (3BH to 3CH)Default gatewayRepresented as a double word (32-bit value). R0
61 to 62 (3DH to 3EH)DNS server (primary)Represented as a double word (32-bit value). R0
63 to 64 (3FH to 40H)DNS server (secondary)Represented as a double word (32-bit value). R0
NameDescriptionR/W
Represented as a string.
Initial value is "192.168.3.3"
Represented as a double word (32-bit value).
Initial value is C0A80303H
Represented as a double word (32-bit value).
Initial value is FFFFFF00H (255.255.255.0)
R: Read-only
Initial
value
R-
R-
R-
3.4.4 Common setting status area (address: 70 to 80)
1
OVERVIEW
2
SYSTEM
CONFIGURATION
3
SPECIFICATIONS
4
SETTINGS AND
PROCEDURES UP TO
OPERATION
5
The status of the network setting ( Section 11.4.1) for the common setting can be
checked in this area.
Decimal address
(Hexadecimal)
70 (46H)
71 to 72 (47H to 48H)IP addressRepresented as a double word (32-bit value). R0
73 to 74 (49H to 4AH)Subnet maskRepresented as a double word (32-bit value). R0
75 to 76 (4BH to 4CH)Default gatewayRepresented as a double word (32-bit value). R0
77 to 78 (4DH to 4EH)DNS server (primary)Represented as a double word (32-bit value). R0
79 to 80 (4FH to 50H)DNS server (secondary)Represented as a double word (32-bit value). R0
IP address specification
method
NameDescriptionR/W
0: Auto-obtain, 1: SpecifyR0
R: Read-only
3.4 Buffer Memory List
3.4.2 CompactFlash card information area (address: 21 to 25)
Initial
value
3 - 25
HIGH SPEED DATA
LOGGER MODULE
6
7
DATA LOGGING
8
EVENT LOGGING
TOOL STARTUP
FUNCTION LIST
FUNCTION
FUNCTION
3
SPECIFICATIONS
3.4.5 Time synchronization information area (address: 100 to 109)
Information related to the time synchronization function ( Section 10.1) can be checked in this
area.
Decimal address
(Hexadecimal)
100 (64H)Time synchronization status
101 (65H)
102 (66H)Month 01 to 12R0
103 (67H)Day01 to 31R0
104 (68H)Hour00 to 23R0
105 (69H)
106 (6AH)
107 (6BH)
108 (6CH)Daylight saving time status
109 (6DH)
Time synchronization
result
SNTP time synchronization
processing time
(1) Time synchronization status (address: 100)
Time synchronization setting
Synchronize with the programmable
controller CPU time
Synchronize with SNTP
NameDescriptionR/W
0: Synchronize with the programmable controller CPU time
1: Synchronize with SNTP
Year4 digitsR0
Minute
00 to 59R0
Second
00 to 59R0
Day
0: Sunday, 1: Monday, 2: Tuesday, 3: Wednesday,
of
4: Thursday, 5: Friday, 6: Saturday
week
0: Not daylight saving time
1: Daylight saving time
Time required for the SNTP time synchronization (unit: ms)R0
R: Read-only
The operating status of the time synchronization setting ( Section 11.4.2) is
stored.
The following table shows the relationship of the value stored in the time
synchronization status to the time synchronization setting.
Time data from SNTP
server
-0: Synchronizing with programmable controller CPU time
Unobtainable0: Synchronizing with programmable controller CPU time
Obtained1: Synchronizing using SNTP
Time synchronization status
Initial
value
R0
R0
R0
3 - 26
(2) Time synchronization result (address: 101 to 107)
When "Synchronize with SNTP" is selected with the "Time synchronization setting",
the time information obtained from the SNTP server is stored.
When "Enable daylight saving" is selected, the time stored is the time after adjusting
for daylight saving time during the daylight saving time period.
When "PLC CPU synchronization" is selected in "Time synchronization setting", the
time information obtained from the programmable controller CPU is stored.
(3) Daylight saving time status (address: 108)
Information on whether or not the time synchronization result time is daylight savings
time is stored.
When the time synchronization status is '0: Synchronize with programmable controller
CPU time', '0: Not daylight saving time' is always stored.
(4) SNTP time synchronization processing time (address: 109)
The time required for SNTP time synchronization is stored. (unit: ms)
This area stores the time required for the last successful SNTP time synchronization.
It indicates the maximum deviation for the obtained SNTP server time.
3.4 Buffer Memory List
3.4.5 Time synchronization information area (address: 100 to 109)
3
Remark
SPECIFICATIONS
3.4.6 Current error area (address: 140 to 145)
The most recent error code which is currently occurring can be checked in this area.
Decimal address
(Hexadecimal)
140 (8CH)Error codeThe error code indicates the definition of the error. R0
141 (8DH)System area(Use prohibited)--
142 (8EH)
143 (8FH)
144 (90H)
145 (91H)
Time
(1) Error code (address: 140)
NameDescriptionR/W
Bits 0 to 7Last two digits of the yearR0
Bits 8 to 15Month: 01 to 12R0
Bits 0 to 7Day: 01 to 31R0
Bits 8 to 15Time: 00 to 23R0
Bits 0 to 7Minute: 00 to 59R0
Bits 8 to 15Second: 00 to 59R0
The error code ( Section 18.2) which indicates the definition of the occurred error
is stored.
Initial
value
R0
1
2
3
4
SYSTEM
OVERVIEW
CONFIGURATION
SPECIFICATIONS
(2) Time (address: 142 to 145)
The time the error occurred is stored in BCD code.
b15 to b8 b7 to b0
Buffer memory address: 142
143
144
145
(1) The current error area information can be checked with the following
diagnostics screens.
• Configuration Tool: The <<Module diagnostics>> tab under [Online] [Diagnostics]
Section 13.1.1
• GX Works2 or GX Developer: "Error Code" under [System monitor]
Section 18.1.3
(2) The current error information area can be cleared with the following methods.
• Configuration Tool: With the button on the <<Module
diagnostics>> tab under [Online] - [Diagnostics] ( Section 13.1.1)
• Turn ON error clear request (Y10)
• Power ON from OFF or reset the CPU module
Month (01H to 12H)
Hour (00
Second (00
Year (00H to 99H) first 2 digits
H to 23H)
H to 59H)
Year (00
H to 99H) last 2 digits
Day (01H to 31H)
Minute (00
Day of week (0
H to 59H)
H to 6H)
SETTINGS AND
HIGH SPEED DATA
PROCEDURES UP TO
5
LOGGER MODULE
6
7
DATA LOGGING
8
OPERATION
TOOL STARTUP
FUNCTION LIST
FUNCTION
3.4 Buffer Memory List
3.4.6 Current error area (address: 140 to 145)
3 - 27
EVENT LOGGING
FUNCTION
3
b15 to b8 b7 to b0
+2
+3
+4
+5
+1
System area (use prohibited)
+0
Error code
Time
Buffer memory address: 152 to 157Error log 1
Error log 2
Error log 16
158 to 163
242 to 247
Month (01H to 12H)
Hour (00
H
to 23H)
Second (00
H
to 59H)
Year (00H to 99H) first 2 digits
Year (00
H
to 99H) last 2 digits
Day (01H to 31H)
Minute (00
H
to 59H)
Day of week (0
H
to 6H)
SPECIFICATIONS
3.4.7 Error log area (address: 150 to 247)
The history of errors which have occurred on the high speed data logger module can be
checked in this area.
Decimal address
(Hexadecimal)
150 (96H)Error count
151 (97H)Error log write pointer
152 (98H)
153 (99H)System area(Use prohibited)--
154 (9AH)
155 (9BH)
Error log 1
156 (9CH)
157 (9DH)
158 to 247
H to F7H)
(9E
Error log 2 to 16Details are the same as error log 1. --
NameDescriptionR/W
The cumulative number of errors registered in the error
log area.
The error log number registered to the most recent error
log. 0: No errors, 1 to 16: Error log number
Error codeThe error code indicates the definition of the error. R0
Bits 0 to 7Last two digits of the yearR0
Bits 8 to 15Month: 01 to 12R0
Bits 0 to 7Day: 01 to 31R0
Bits 8 to 15Time: 00 to 23R0
Time
Bits 0 to 7Minute: 00 to 59R0
Bits 8 to 15Second: 00 to 59R0
The error log number registered to the most recent error log is stored.
For example, when the value is '16', the most recent error log is registered to the area
for error log 16.
(2) Error log 1 to 16 (address: 152 to 247)
The history of occurred errors is stored.
It is comprised of 16 error logs with the same data configuration.
(a) Error code
The error code ( Section 18.2) which indicates the definition of the occurred
error is stored here.
(b) Time
3 - 28
3.4 Buffer Memory List
3.4.7 Error log area (address: 150 to 247)
The time the error occurred is stored in BCD code.
3
POINT
SPECIFICATIONS
(1) The error log area information can be checked with the following diagnostics
screens.
(2) The error log area can be cleared with the following methods.
(3) When 17 or more errors occur, errors are registered again from error log 1.
(4) When an error that is already registered occurs, that error is not registered.
• Configuration Tool: With "Error log" on the <<Module diagnostics>> tab
under [Online] - [Diagnostics] ( Section 13.1.1)
• GX Works2 or GX Developer: "Error History" under [System monitor]
( Section 18.1.3)
• Configuration Tool: With the button on the <<Module
diagnostics>> tab under [Online] - [Diagnostics] ( Section 13.1.1)
• Power ON from OFF or reset the CPU module
1
2
3
OVERVIEW
SYSTEM
CONFIGURATION
3.4.8 General data sampling delay time area (address: 800 to 805)
Decimal address
(Hexadecimal)
800 to 801
H to 321H)
(320
802 to 803
H to 323H)
(322
804 to 805
H to 325H)
(324
The data sampling monitoring interval actually operating on the high speed data logger
module can be checked with this area.
The data sampling delay time of data logging, event logging, and report function in the
operation of general data sampling can be checked with this area.
NameDescriptionR/W
General data sampling delay time
(moving average)
General data sampling delay time
(maximum)
Allowed general data sampling
delay time
The general data sampling delay time is stored as the
moving average over 30 times.
(unit: ms)
The maximum value of general data sampling delay
time up to the present is stored.
(unit: ms)
Sets the allowed general data sampling delay time.
(unit: ms)
R: Read-only R/W: Readable/Writable
R/W0
Initial
value
R0
R0
SPECIFICATIONS
4
SETTINGS AND
PROCEDURES UP TO
OPERATION
5
HIGH SPEED DATA
LOGGER MODULE
TOOL STARTUP
6
FUNCTION LIST
7
3.4 Buffer Memory List
3.4.8 General data sampling delay time area (address: 800 to 805)
3 - 29
DATA LOGGING
FUNCTION
8
EVENT LOGGING
FUNCTION
3
Remark
SPECIFICATIONS
(1) Allowed general data sampling delay time (address: 804 to 805)
Sets the allowed general data sampling delay time.
0: Of the data sampling time for data logging, event logging, and report
function when general data sampling is specified, the allowed time is
half of the shortest data sampling time.
Example: If the data sampling time is 0.1 second: Allowed time = 50 ms.
Other than 0: The specified value is the allowed time. (unit: ms)
When general data sampling delay time (max) exceeds the allowed time, general data
sampling delay (X1E) turns ON.
About general data sampling delay time:
• The high speed data logger module executes general data sampling of
data logging, event logging, and report functions every 100ms. If the data
sampling interval is set to 0.2s or higher, elapsed time is checked every
100ms and general data sampling executes as necessary.
• If there are many general data sampling settings or much data, data
sampling takes time, and there may be cases where sampling each 0.1s
or checking the elapsed time cannot be done. In this case, the general
data sampling delay time is set as 100ms subtracted from the actual data
sampling time.
• When a general data sampling delay occurs, at maximum, there is the
possibility that a data sampling delay occurred of the amount of the
general data sampling delay time in data logging, event logging, or report
function. In this case, refer to the following section and take action.
Section 17.2 Checking Processing Time
When access target CPU error (the power interruption or network failure)
is detected, the sampling time is extended by maximum of the response
monitoring time (Section 4.5 (3) Response monitoring time setting
(Switch 3 (lower byte))) at detection.
3 - 30
Example) Processing is shown when the data logging and event
logging intervals are set to the same time.
Data sampling interval
Data logging
Event logging
No event
3.4 Buffer Memory List
3.4.8 General data sampling delay time area (address: 800 to 805)
Event
(Performs event
processing)
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.