Re: [foxboro] AIM* OPCHDA
- From: "Pulas, Philip" <Philip.G.Pulas@xxxxxxxxxxx>
- To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 5 Feb 2013 16:57:07 +0000
William,
We had a lot of trouble getting OPCHDA working. We did have to change the OPC
server box to have a fox user with the same I/A password and run the OPC
service under that user. It worked for a few days, but after testing it again
with reboots, it never worked again. We had to switch to the MatrikonOPC
Server software, which has had no issues and was up and running after less than
hour. TAC was unable to figure the problem out and got annoyed that we kept
calling in about it each day. Yes, we had to waste the OPCHDA license we
purchased, but I highly recommend the MatrikonOPC Server software.
Thanks,
Philip Pulas
Tesoro
Golden Eagle Refinery
Martinez, CA
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of William C Ricker
Sent: Tuesday, February 05, 2013 8:33 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] AIM* OPCHDA
We have that much in place. The OPCHDA runs as a service on a server box, but
has no historian
there. (one will be there in future). An XP based AW has a small historian and
we wish to pull
data from it through the OPC server. Applicable license codes are in. The OPC
server does work
quite nicely when asked to pick up real time data, but we've not managed to
make it see our
historian.
We have connectivity between the Server and XP. OPCHDA is turned on for the
<letterbug> user on
the server. At the XP we have tried enabling AIMHIS for various users (as it
is a 200 point
historian we can only enable one user at a time). we have no luck.
Mr. Peck suggested that the user name on the historian box should be the user
which runs the
OPC software on the server. If this runs as a service, should it be
Administrator? System?
the letterbug?
Thanks for your help,
W C Ricker
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Landry, Scott
Sent: Tuesday, February 05, 2013 11:02 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] AIM* OPCHDA
Chris,
AIM*AT OPC Server Installation B0400DG – Rev B
page 19
Before you can use the OPC server to communicate with AIM servers, each AIM
Server must
have an Invensys supplied license authorization code entered on the AIM Server.
License codes are
available to an unlimited number of AIM servers.
The package code determines the type of connection authorized for the OPC
server. The two
types of package codes are as follows:
♦ The OPCDAO package code enables the OPC server to establish a connection for
real-time data transfer.
♦ The OPCHDA package code enables the OPC server to establish a connection for
both real-time and historical data transfer.
In addition, the computer name of the station that is hosting the OPC server
must be configured
as a user name on the AIM server.
NOTE
If the station that hosts the OPC Server is an I/A Series station (AW70), then
the
computer name is the station letterbug name.
Regards,
Scott
________________________________________
From: foxboro-bounce@xxxxxxxxxxxxx [foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of
William C Ricker [wcricker@xxxxxxxxxxxxxxx]
Sent: Monday, February 04, 2013 5:26 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] AIM* OPCHDA
RE: >User Name on the AIM OPC box must be listed as a package user in the
AIM Historian
Thanks, but more questions 'cause I can't get it to work .
Does the name in the historian box need to be something like "fox" ?
Does it include the station name ?
If my OPC box has the server running as "SYSTEM", should that name be
"SYSTEM" or "ADMINISTRATOR" ?
Is your OPC running as a service ?
W C Ricker
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
