We use the AIM* batch input file below to configure our off-platform
instance with local time. The instance uses 2 I/A NT remote collector and 1
OPC IO gate.
With this setting, the PC's on the corporate network can be set with the
local time zone.
Note1: replace GMT_MINUS_5 with your time zone.
Note2: Twice a year you will have to run a batch file to change the DST
parameter from YES to NO and vice-versa.
Regards,
Sylvain.
Sylvain Nadeau
Systems Integration & IT
Invensys Process Systems
Foxboro Canada Inc.
[EMAIL PROTECTED]
514-421-8107
Fax:514-421-8054
===================================================
0 CREATE AIMHIST myhst1
0 CREATE SESSION myhst1 SESKEY myhst1 rw
#
## AIM*HISTORIAN CONFIGURATION:
#
1 PUT AIMHIST myhst1 ARCHSIZE 10000000
.....
..more lines here....
.....
REDMEDINT = 0
REDSLOWINT = 0
IATIME = NO
ENABLE_STUBS = NO
#
## STATION CONFIGURATION:
#
#
## STATION :REALTIME_SERVER
#
1 CREATE STATION REALTIME_SERVER
ISIA = YES
TYPE = REALTIME_SERVER
PLATFORM = NT
TZ = GMT_MINUS_5
DST = YES
NODE = 1
IATIME = NO
BURSTINT = 0
ISREMOTE = NO
#
## STATION :MESSAGE_SERVER
#
1 CREATE STATION MESSAGE_SERVER
ISIA = YES
TYPE = MESSAGE_SERVER
PLATFORM = NT
TZ = GMT_MINUS_5
DST = YES
NODE = 1
IATIME = NO
BURSTINT = 0
ISREMOTE = NO
#
## STATION :myhst1
#
1 CREATE STATION myhst1
ISIA = YES
TYPE = IA_RT_COLLECTOR
PLATFORM = NT
TZ = GMT_MINUS_5
DST = YES
NODE = 1
IATIME = NO
CIRCFILESIZE = 1000000
BURSTINT = 0
BURSTBTPCT = 10
BURSTTTPCT = 90
SENDPASSSECS = 0.2
RECVPASSUPDS = 1000
CONSLEEPSECS = 5
ISREMOTE = NO
IPADDR =
#
## STATION :colnt1
#
1 CREATE STATION colnt1
ISIA = YES
TYPE = IA_RT_COLLECTOR
PLATFORM = NT
TZ = GMT_MINUS_5
DST = YES
NODE = 1
IATIME = NO
CIRCFILESIZE = 4000000
BURSTINT = 0
BURSTBTPCT = 10
BURSTTTPCT = 90
SENDPASSSECS = 0.2
RECVPASSUPDS = 1000
CONSLEEPSECS = 5
ISREMOTE = YES
COLDESC = "nt collector 1"
IPADDR =
#
## STATION :ntcol2
#
1 CREATE STATION ntcol2
ISIA = YES
TYPE = IA_RT_COLLECTOR
PLATFORM = NT
TZ = GMT_MINUS_5
DST = YES
NODE = 1
IATIME = NO
CIRCFILESIZE = 4000000
BURSTINT = 0
BURSTBTPCT = 10
BURSTTTPCT = 90
SENDPASSSECS = 0.2
RECVPASSUPDS = 1000
CONSLEEPSECS = 5
ISREMOTE = YES
COLDESC = "NT collector 2"
IPADDR =
#
## STATION :opccol
#
1 CREATE STATION opccol
ISIA = NO
TYPE = IOGATE_COLLECTOR
PLATFORM = NT
TZ = GMT_MINUS_5
DST = YES
NODE = 1
IATIME = NO
CIRCFILESIZE = 1000000
BURSTINT = 0
BURSTBTPCT = 10
BURSTTTPCT = 90
SENDPASSSECS = 0.2
RECVPASSUPDS = 1000
CONSLEEPSECS = 5
ISREMOTE = YES
COLDESC = "opc collector"
IPADDR = 142.70.154.53
#
## POINT CONFIGURATION:
#
1 DEL SESSION myhst1 SESKEY myhst1 commit
exit
===============================
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 24, 2001 12:22 AM
To: Foxboro DCS Mail List
Subject: AIM* timezone issues
I was wondering if anyone on the user list has had any problems with
timezones
in AIM* products. The following is a problem we are having in Australia...
We are running AIM* 3.02 on off-platform servers at two of our sites. One
site uses 50 series boxes as remote collectors, the other site uses 70
series as collectors.
At both sites, the AIM* server is configured to use UTC (GMT in the old
language) as its timezone. This matches the timezone on the I/A boxes so
data is logged nicely with UTC timestamps.
The problem arises in remote clients using Aim Datalink - and maybe in
AimExplorer - where the client PC's are setup to use Australian Eastern
Standard Time (AEST = GMT+10). On these client PC's, the data viewed using
the Aim Datalink Historian Browser is shifted forward by 10 hours to match
the local timezone.
Unfortunately, this requires a mental calculation when looking for data. For
example, to find a point of interest for something which occurred at 12
noon, you need to look at data from 10 PM onwards.
The answer we got back from our local Foxboro office (relayed from Foxboro
TAC) is that the client PC's need to be setup to use UTC (GMT) as the
timezone.
Since these client PC's operate within our corporate network of a couple of
hundred machines, it is neither feasible or desirable to have a dozen
machines operating in a different timezone.
I have read the timezone information in the AIM* manual, but frankly it
still isn't clear to us how to set the Aim* database to overcome this
problem.
Has anyone else seen this problem, and even better, found a way around it?
I can supply the Instance and Collector setup if this would be useful.
Regards
Rob Laghigna
Australian Vinyls
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
