Use the datalog configuration windows in the I/O Tool Kit to define the rate and conditions (such as an event signal) by which datalogging will occur, and to define the I/O to be logged. To make configuration easy and accurate, the available I/O points are readily accessible from within a tag listing, based on the project file.
Datalogging will begin once the datalog configuration data is downloaded to the station. Data transfer options allow data to be easily read and then cleared, if desired. The retrieved data will be displayed in the Data Viewer main window and/or written to an ASCII text file on your hard drive.
Each TCP client transfer must have a unique IP port in the RTU configuration and the Datalog server must have the same TCP port added.Datalogging with TCP Client Transfers
How much data can I log?
STEP 1
- Observe the total number of bytes per datalog record
- The Record Content window includes a display of the total number of bytes each record
STEP 2
- Calculate the number of datalog records stored per day
Example: 1440 minutes per day ÷10 minute (logging rate) = 144 datalog records per day
STEP 3
- Calculate the total number of bytes per day
Example: 144 records x 54 bytes per record x 1.10 (10%) = 8554 total bytes per day
STEP 4
- Calculate how many days you can log data before reaching a given file size
Example: 400,000 bytes ÷8554 bytes per day @ 46.75 days
Setting up an FTP Client Transfer with IPm2m and FileZilla
Overview
- Tool Kit project with M2M, Datalog config, & an FTP Client Tranfer (enabled/executed via DI register).
- FileZilla - Setup user account and password the matched datalog configuration.
- Share datalog folder directory.
- Load IPM, Run server, toggle bit to transfer the file.
IPM setup
IPM IP address = 10.1.0.2.
PC IP address = 10.1.0.200
Modules:
Add Tags to log, and one DI to use as FTP transfer trigger.
Create Datalog configuration:
Setup Client Transfer (See image below and demo Project file):
- Fixed Log Rate – transfer rate. Will transfer only when the Start/Stop bit is set high/On.
- Start/Stop Control- any virtual DI/DO.
- Destination IP - must be the PC’s IP address that is running FileZilla.
- IP Port – FTP default is 21.
- Directory – “\” ; this will setup folders on the PC (server) to store the CSV file. It is set to “\” because it can also be setup with the server as used in this demo. Note: If a folder defined in the Server eg. “C:\misc\log” and a folder is setup in the datalog configuration “\log1” then the datalog CSV file location will be “C:\misc\log\log1\*.CSV”.
- User & Password – This information is required and case sensitive. See the User section of FileZilla (can be generic for all users).
Load to IPM
FileZilla Setup:
Install, and Run server….
General Settings – All Default
Users > Add User and Password (A Group configuration is not required)
Share the directory that you wish to put the CSV files in. Be sure to Enable the File options, and Directories options (check boxes)
Run Server.
Once the IPM is loaded you should be able to then Toggle the DI bit to run the FTP transfer.
Citect Datalogging
1. Follow the steps below if the Citect Datalog Server fails to start:
- Make sure that you register sxdlogsrv.dll.
- In order to do this, Run the command line utlity "Regsvr32.exe"
- Type in Regsvr32 "c:\program files\sixnet tools\programs\sxdlogsrv.dll"
- (Verify that the DLL file exists in this location)
- After doing this, Open and Run the Sxcitectsrv.exe and the citect server should run.
2. Follow the steps below if you run into the error message related to CTAPI.dll file:
- Go to Control Panel-> Advanced system settings-> Click on "Environmental variables-> Under "system variables” click on Path-> variable value
- Edit Variable value: Put a ; at the end and type in the location of the CTAPI.dll file (for example C:\Program Files\citect\citectscada7.10\bin)
- Click on OK. Open toolkit and run the citect data log server.
3. When you click on “Import Data” as shown below,
You might run into the below error message:
Make sure that the cicode file is in C:\ProgramData\Citect\CitectSCADA 7.20\User\Example location where the other cicode files reside.
Open Citect Scada Explorer, select the sxtrend.ci file and hit "compile and run"
4.When you move (.6pj)project File with Citect trend configuration in them from one PC to another, make sure to copy the sxtrendvars.dbf file from C:\Program Files\Sixnet Tools\Projects along with the project file to have all the information saved.
Disclaimer
It is the customer's responsibility to review the advice provided herein and its applicability to the system. Red Lion makes no representation about specific knowledge of the customer's system or the specific performance of the system. Red Lion is not responsible for any damage to equipment or connected systems. The use of this document is at your own risk. Red Lion standard product warranty applies.
Red Lion Technical Support
If you have any questions or trouble contact Red Lion Technical Support by clicking here or calling 1-877-432-9908.
For more information: http://www.redlion.net/support/policies-statements/warranty-statement