Joseph,
Or...Daisy Chain
You could VPN into another computer first. From there, you could RDP (or
rlogin, if it is UNIX) into the AW in which you run the ICC. If you lose your
VPN connection, the computer in the middle will maintain the connection to the
AW with the open ICC session. It likely will not maintain it forever, but it
will buy you some time to reconnect. (I have inadvertently signed out of a
Windows server and left an RDP session to a Workstation running. I went on
vacation. It was still there when I got back. Your mileage may vary.)
You should verify this advance (without opening the ICC--no sense in adding
risk) to feel comfortable with it.
Chuck Jones
Automation Technologist
Tate & Lyle
External use permitted
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx <foxboro-bounce@xxxxxxxxxxxxx> On Behalf Of
Joseph M. Riccardi
Sent: Wednesday, July 15, 2020 12:21 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [EXTERNAL] Re: [foxboro] V9.3 System that still has the ICC
Dirk,
Great idea on the PLB Library suggestion, I forgot about that feature. I will
probably go that route to minimize any P2P issues.
However, you raise a red flag about the RDP connection with "When you're in the
ICC and you lose the connection, your changes are lost and you possibly might
have a corrupt CP dbse." Again, most of my experience is on the UNIX Version
Systems and maybe they are different but from memory, when on a remote
connection and the connection was lost (which was often at some plants), the
procedure I followed was something like this...
***** I could not open another ICC session because the ICC was locked so...
***** I searched for the open ICC Process ID (forgot actual name) and killed
it.
***** It seems to me I had to perform another task but I cannot remember the
details.
***** Then I could remotely open an ICC session again but I do not remember
any file corruption issues, especially any direct CP corruption issues. At the
time of the disconnection, changes DONE were still there but all was lost after.
Since I will be implementing these changes on a running plant, I definitely
cannot risk direct CP corruption issues. Can you please explain what "corrupt
CP dbse" could mean outside of lost changes not DONE...
Thanks again.
Joseph
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Dirk Pauwels
Sent: Wednesday, July 15, 2020 11:36 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] V9.3 System that still has the ICC
Hi Joe,
Maybe copying the PLB layout to the PLB library can also help you. You then
have a file you can copy from one AW to another. This is only the plb line
layout, so no C:B:P addresses. And you still have to create the block and name
it on the AW2, but it saves using function keys to build the layout.
It's accessed in the PLB builder from "file"
D:\opt\fox\ciocfg\plblibrary
We're accessing our boothost (we only have one, hosting 6 ft CP's) remote
(RDP) for years now, including from home using VPN. Works well but a good
connection is a plus. When you're in the ICC and you lose the connection, your
changes are lost and you possible might have a corrupt CP dbse. We've been
lucky sofar, we only had blocked CP dbse's and one time a DBsynch error.
Rgds,
Dirk
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Joseph M. Riccardi
Sent: Wednesday, July 15, 2020 4:36 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] V9.3 System that still has the ICC
****EXTERNAL EMAIL - Exercise caution, this email originated from outside of
the company. DO NOT reply to, open attachments or click links if the email
looks suspicious or is from an unknown sender.****
________________________________
Folks,
I have a V9.3 IA System that still has the ICC. Plan A had a couple of trips
to the site planned to implement some ICC changes but the Coronavirus has
changed that because I cannot travel at this point in time. The ICC changes
will include adding/editing/copying some PLBs. Looking ahead to Plan B, I have
requested a remote access account on the plant's Network with plans to connect
to the IA System via RDP to an Engineering AW Workstation on site. Any
warnings I need to consider?
Since the majority of my work has been on the older UNIX Systems (yes, they are
still out there), I need to refresh my memory on the limitations associated
with the Windows version. The main limitation is that ICC changes to the CPs
can only be implemented from the host AWs. But can I copy a block from a CP
hosted by AW1 into a CP hosted by AW2? Normally this would involve an Add
Block selection, Type (PLB) 'C:Blocknametobecopied'.
If they are in CPs with different hosts, will this add/copy a PLB still work?
Ditto for C:B:Parameter connections between CPs with different hosts. No
limitations?
Any warnings I need to consider?
Thanks
Joseph
********************************************************************************************************
This email and any files transmitted with it are confidential and intended
solely for the
use of the individual or entity to whom they are addressed. If you are not the
intended
recipient or the person responsible for delivering the email to the intended
recipient, be
advised that you have received this email in error that any use, dissemination,
forwarding, printing, or copying of this email is strictly prohibited. If you
have received
this email in error please notify the sender immediately. Please note that we
reserve
the right to monitor and read any emails sent and received by the Company in
accordance with and to the extent permitted by applicable legal rules.
*********************************************************************************************************
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at 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
