Future Design MCT-MC 4.3, User Manual

Page: 169 / 186

MCT-MC
4.3
Appendix - 169 - FDC MCT-MC
DataMapID CustomerID FileColumn FieldName MC loop name
configured by
user at MC
8 SvpTest
(UserID or
RemoteUserID
used during login)
Temp Out
(Field must match
user configured
t
spa “Out”)
TempOut
(Field can be
named anything
with no space
characters)
Temp
(assigned by user
in config)
9 SvpTest
(UserID or
RemoteUserID
used during login)
RH PV
(Field must match
user configured
t
spa “PV”)
RHPV
(Field can be
named anything
with no space
characters)
RH
(assigned by user
in config)
10 SvpTest
(UserID or
RemoteUserID
used during login)
RH SP
(Field must match
user configured
t
spa “SP”)
RHSP
(Field can be
named anything
with no space
characters)
RH
(assigned by user
in config)
11 SvpTest
(UserID or
RemoteUserID
used during login)
RH Out
(Field must match
user configured
t
spa “Out”)
RHOut
(Field can be
named anything
with no space
characters)
RH
(assigned by user
in config)
Lastly, the database must be setup to match the data log “point” setup at the MC. The above table displays the
database setup for a dual loop controller data logging temp and RH loops with process value, set point and
percent output for each loop being logged. If only the process value from each loop was being logged, the
database setup would need to be setup for those two parameters only, with the additional parameters of set
point and percent output for each loop being removed.