TAMAGAWA TS5238N352 TS5238N352 TS5238N352 TS5238N352 TS5238N352 TS5238N352

TS5238N352

TS3617N1E3

TS3617N1E1

TS3617N1E2

TS3617N2E4

TS3630N11E1

TS3664N2E4

TS3653N13E7

TS3653N12E6

TS3653N2E5

TS3624N2E3

TS3653N13E9

TS3653N2E6

TS3653N3E7

TS3653N3E8

TS3653N3E9

TS1980N43E12

TS1980N56E12

TS1981N134E9

TS1981N53E19

TS1981N56E19

TS1981N56E19

TS1982N126E6

TS1982N128E6

TS1982N53E6

TS1982N56E18

TS1983N146E5

TS252N30E1

1 8070 All internal instance memory is in use.
1 8092 Data log does not exist.
1 80B0 Data log file is not open (for explicit open mode only).Allows your program to create a new data
log file based upon an existing data log file.
STEP 7 automatically creates the associated
instance DB when you insert the instructionA low to high (positive edge) signal starts the operation. (Default value:
False)
RECORDS IN UDInt The maximum number of data records the circular data log can contain
before overwriting the oldest entry. (Default value: 1)
The header record is not included. Sufficient available CPU load memory
must exist in order to successfully create the data log.
NAME IN Variant Data log name: You provide the name. This variant only supports a String
data type and can only be located in local, DB, or M memory. (Default value:
' ')
The string reference is also used as the name of the data log file. The name
characters must follow the Windows file system naming restrictions.
Characters / : * ? " < > | and the space character are not allowed.)
ID In/Out DWord Numeric data log identifier(Default value: 0):
 At execution, the ID input identifies a valid data log. The new data log
configuration is copied from this data log.
 After execution, the ID parameter becomes an output that returns the ID
of the newly created data log file.
Note: Symbolic name access for this parameter is not allowed.
DONE OUT Bool The DONE bit is TRUE for one scan, after the last request was completed
with no error.
BUSY OUT Bool  0 - No operation in progress
 1 - Operation on progress
ERROR OUT Bool The ERROR bit is TRUE for one scan, after the last request was terminated
with an error. The error code value at the STATUS parameter is valid only
during the single scan where ERROR = TRUE.
STATUS OUT Word Execution condition code (Default value: 0) You can execute the DataLogNewFile instruction when a data log becomes full or is deemed

completed and you do not want to lose any data that is stored in the data log. A new empty
data log file can be created based on the structure of the full Data log file. The header record
will be duplicated from the original data log with the original data log properties (DATA record
buffer, data format, and timestamp settings). The original Data log file is implicitly closed and
the new Data log file is implicitly opened.
DataLogWrite parameter trigger: Your program must monitor the ERROR and STATUS
parameters of each DataLogWrite operation. When the final record is written and a data log
is full, the DataLogWrite ERROR bit = 1 and the DataLogWrite STATUS word = 1. These
ERROR and STATUS values are valid for one scan only, so your monitoring logic must use
ERROR = 1 as a time gate to capture the STATUS value and then test for STATUS = 1 (the
data log is full).
DataLogNewFile operation: When your program logic gets the data log is full signal, this
state is used to activate a DataLogNewFile operation. You must execute DataLogNewFile
with the ID of an existing (usually full) and open data log, but a new unique NAME
parameter. After the DataLogNewFile operation is done, a new data log ID value is returned
(as an output parameter) that corresponds to the new data log name. The new data log file is
implicitly opened and is ready to store new records. New DataLogWrite operations that are
directed to the new data log file, must use the ID value returned by the DataLogNewFile
operation.
Note
A DataLogNewFile operation extends over many program scan cycles. The actual time
required for the log file creation depends on the record structure and number of records.
Your program logic must monitor and catch the DataLogNewFile DONE bit's transition to the
TRUE state, before the new data log can be used for other data log operations. The data log files are stored as comma separated value format (*.csv) in persistent flash
memory. You can view the data logs by using the PLC Web server feature or by removing
the PLC memory card and inserting it in a standard PC card reader.
Viewing data logs with the PLC Web server feature
If the PLC PROFINET port and a PC are connected to a network, then you can use a PC
web browser like Microsoft Internet Explorer or Mozilla Firefox to access the built-in PLC
Web server. The PLC may be in run mode or stop mode when you operate the PLC Web
server. If the PLC is in run mode, then your control program continues to execute while the
PLC Web server is transferring log data through the network.
Web server access:
1. Enable the Web server in the Device Configuration for the target CPU (Page 504).
2. Connect your PC to the PLC through the PROFINET network (Page 505).
3. Log in to the built-in Web server (Page 506).
4. Download the recent records, all records, clear records, or delete log files with the "Data
Log" standard web page (Page 516).
5. After a copy of a data log file is downloaded to your PC, you can open the .csv file with a
spreadsheet application like Excel.
Viewing data logs on a PLC memory card
If the CPU has a "Program" type memory card inserted, then you can
remove the memory card and insert the card into a standard SD (Secure Digital) or MMC
(MultiMediaCard) card slot on a PC or PG. The PLC is in stop mode when the memory card
is removed and your control program is not executed.
Use the Windows file explorer and navigate to the DataLog directory on the memory card.
All your *.csv data log files are located in this directory.
Make a copy of the data log files and put the copies on a local drive of your PC. Then, you
can use Excel to open a local copy of a *.csv file and not the original file that is stored on the
memory card.