Future Design MCT-CM, User Manual

Page: 127 / 247

MCT-CM
127
NOTE: Make sure proper permissions are set at the FileWeb server for access/creation of directories and
read/write access. Also check root directory structure at Server to identify the actual root that was
created for the files since there can be additional layers created by the server and displayed in the path.
The DataWeb interface allows the MCT to transfer data to a web data base service using MySQL and Microsoft
IIS as a web platform. The MCT can interface directly to a local or Web data base (Cloud) thereby allowing
access to any system globally without any special “client” applications required to view the data. This allows
the MCT to share data with local or global manufacturing systems by storing data directly to a manufacturing
database. The MCT supports https:// (secure) transfer of data.
MCT Field Setup DataWeb Server Setup
Type = DataWeb
FileWeb server setup (see Appendix section A.2 FTP,
FileWeb,
DataWeb Requirements/Installation for
additional information).
IP Add =
https://fdctuil.com/FDDataService.svc
Actual named address of DataWeb server/service.
User = userName
Actual user name for login at FileWeb server (required).
This is the directory where the database structure will
reside on the server. The MCT will use this directory path
for sending data to the database.
Password = userPassword Actual password for login at DataWeb server (required).
Server = not used
The directory where the database exists uses the
userName as the default location for data storage.
Port = not used
Data logging screen entries:
ID#1 = unit specific identifier
ID#2 = unit specific identifier
(see section 8.2 Starting/Stopping Data
Logging)
Used as the unit identifiers by the remote database in
order to store the data sent from the MCT. At least one
field must contain an entry and should be unique to any
other MCT
’s that connect to the same server database.
NOTE: An IT professional with experience is required for DataWeb server setup. Future Design Controls does
not support server-side programming or setup but can offer 3
rd
party resources to assist with or handle
complete server-side projects.
The DataWeb interface does not transfer complete files for backup like the FTP and FileWeb interfaces. The
DataWeb interface transfers records in real time based on the log setup interval at the MCT. When logging is
started at the MCT, data will begin transfer to the server-side site. Data will be transferred to the server at the
beginning of logging (one record) with additional records transferred based on the rate that the MCT data log
interval is set for.
If the data log interval rate is set for 60 seconds, the MCT will populate the database with a single set of records
(PV, SP, %Out determined by data log/server setup) once every 60 seconds. If the data log interval rate is set
for 120 seconds, the MCT will populate the database with a single set of records (PV, SP, %Out determined by
data log/server setup) once every 120 seconds. Data log intervals can be set as fast as 2 seconds since
buffering is used at the MCT for faster data log rates, but in this case the database would receive a total of 30
records once per minute (one record per second). Buffering for rates faster than 1 minute is used to reduce
access/overhead at the server side while still maintaining 2 second date/time stamps for database record
keeping.