Q2: Can I have extension I/O racks like on a PLC when my rack is full?
A2: No, the system is not designed that way, it is designed for geographic and functional distribution of risk. The processor being sized to implement control and sequence functions in an optional redundant processor on the directly connected I/O removing the need for lots of interconnecting cables and connector systems all of which increase the availability of the system. The sizing and pricing of the racks and control processors are such that we can be competitive with the larger processor systems but provide choice of redundancy and better scalability for the smaller system without compromising on functionality.
Q3: Which System Platform version does Wonderware PAC use?
A3: Wonderware PAC is compatible with System Platform 4.0. Application Server 3.1 SP2 and SP3. It is also compliant with InTouch 10.1 SP3, Historian Server/Client 10.0, InBatch 9.0 SP1.
Q4: On which operating system is Wonderware PAC V5.0 supported?
A4: Wonderware PAC Software 5.0 is supported on 32 bits operating system (i.e. Windows XP SP3 and Windows 2003 Server SP2).
Q5: Do I need to purchase the Development Studio from Wonderware to get the configuration tools (LINTOOLS) for the PAC on Standalone systems?
A5: No. With every Foxboro PAC hardware system shipped, we include a tools CD called Tactician which is included at no charge. This provide full configuration capability for the hardware when not integrated into the system platform or using the integrated IDE version included with Wonderware PAC software. If you require a tools license without purchasing Foxboro PAC hardware this can be ordered using order code is T555F on BuyAutomation.
Q6: Where do I need a Wonderware PAC license and where does it reside?
A6: The Wonderware PAC licenses resides on each platform which runs the DA server connected to the Foxboro PAC communications bus. (i.e. PAC_DINetwork instance).
The license is one per Galaxy but requires a serialize license version for each DA Server.
Q7: Does the PAC support HART protocol?
A7: Not directly, however the AI3 modules can be part of the HART 4-20mA loop using an external Hart multiplexer, but cannot currently acquire the HART data directly.
Q8: Can the PAC network protocol reside on a standard Ethernet network?
A8: Yes. The PAC communication protocol, ELIN (Ethernet Local Instrument Network), is supported on COTS (commercial off the shelf) standard Ethernet components (10/100Mb switches, Managed switches, Routers…).
Q9: Can the PAC system support other Ethernet based protocols?
A9: Yes. The Foxboro PAC processors can simultaneously support Modbus-TCP both master and slave in addition to the ELIN peer to peer protocol.
Q10: Does the PAC provides additional communications cards?
A10: No. However those are not required as each Foxboro PAC processor provides both Ethernet and serial communications Additional serial communications ports are added by using additional processors that can be mounted in special bases that do not include I/O cards.
Q11: Is the redundancy native in the product or needs extra programming?
A11: Yes, The Foxboro PAC T1550 and T2750 processors and bases are all supplied redundant ready. Redundancy is a no tools function in the system and is only a matter of installing an additional (duplicate) processor and pushing a synchronize button. All necessary files are copied and the application database execution is then synchronized, the process takes several seconds. Redundancy of the processors automatically provides redundancy of communications as each processor has its own communications ports.
Q12: Is the Foxboro PAC systems Store and Forward compliant with 21 CFR Part 11?
A12: The complete Store and Forward path is 21 CFR Part 11 compliant, from the data recording filing system at source in the Foxboro PAC processors, including the safe data updates passed to the Wonderware Historian engine using the toolkit and the secure writes to the Alarm DB logger interface.
Q13: What are the main features of Wonderware PAC 5.0?
A13: This release includes the following feature:
· Full DA server support
o DA Server deployment & Browser extensions
o Device Integration objects with diagnostic symbols
· PAC tools complete integration to Integrated Development Environment
· PAC application repository in the Galaxy
· Application objects
o Base objects (Alarm “Ack in” field functionality & Time Stamp from Source)
§ I/O reference binding
o Process application objects
· Binding tool
· Store and Forward extension
Q14: Is the PAC programming tool easy to use?
A14: LINTOOLS is an IEC 1131 Part 3 tool set. Any customer OEM or SI with PLC/DCS programming skills can acquire the knowledge very quickly following our standard training courses.
Q15: Can the PAC be programmed in Ladder logic?
A15: Yes, although the base language is FBD (Function Block Diagram) ladder sections can be run under control of FBD or SFC (Sequence Function Chart). The product cannot be programmed totally in Ladder.
Q16: Where is the alarm management being implemented?
A16: The alarm generation and acknowledgment in the Foxboro PAC System is done at source in the Foxboro PAC hardware. Alarm and Event lists are supplied via Wonder PAC software in Eycon or Wonderware System platform (see next question).
Q17: Are the alarms presented to the operator real Archestra alarms?
A17: Yes. The alarms generated by the Foxboro PAC system appear in the standard Wonderware alarm components (i.e. Alarm summary, Alarm History…).
Q18: Are the alarms time stamped at source?
A18: Yes. When System Platform displays alarms generated by the Foxboro PAC the time stamp was generated at source and passed to System Platform by the Wonderware PAC software.
Q19: Is Wonderware PAC compatible with other System Platform applications like InBatch?
A19: Yes. The Foxboro PAC System provides a phase logic function block which map directly to InBatch.
Q20: Where do I need to install Wonderware PAC?
A20: Wonderware PAC should be installed on the same machine hosting the IDE and the Historian machine if it is a separate machine for Store and Forward extension software to be installed.
Q21: Is the Foxboro PAC - Store and Forward able to write to Historian 10 Tiers 1 & Tiers 2?
A21: The system has been tested writing data to Tiers 1 only. The replication of data between Tiers 1 and Tiers 2 is then doing the additional transfer of data.
Q22: Can I use a derived template of the PAC Device Integration objects?
A22: No, the device integration objects need to be of the “raw” template type.
Q23: Are the Strategy objects deployable?
A23: No. the Foxboro PAC system does not support deployment of strategy objects.
Q24: How does LINTOOLS communicates with my instrument when no DI objects are deployed?
A24: On the new PAC Strategy tab, available when you have installed Wonderware PAC software, there is a port setup tool which configures the communications from the IDE to the instrument. The IDE which is running LINtools needs to be connected to the control network, it cannot be routed through the DA server(s).
Q25: Which Device Integration object should I use?
A25: The two Device Integration objects to use are the PAC_DINetwork and the PAC_DIDeviceDiag. The second DI object provides a dynamic symbol which can be used on maintenance mimics.
Q26: Do I need to create an object/UDA to be able to display PAC field data in InTouch?
A26: No. There Wonderware PAC software extension to the Galaxy browser which is available in InTouch to display any field data from the Foxboro PAC system.
Q27: How many Wonderware I/O references can I get through the same DA Server?
A27: The answer is 2500 – This is under review please contact the factory for the most current details.
Q28: How many instances of the PAC_DINETWORK can I get on the same platform?
A28: Only one – This is under review please contact the factory for the most current details.
Q29: Where do I get support for my technical questions?
A29: Local Invensys Operations Management offices should provide this first level support.
Q30: How should I install the Wonderware PAC license?
A30: Wonderware PAC licenses are standard WWSUITE.LIC Wonderware licenses. They need to be added to the license server.
Q31: Is Wonderware PAC 5.0 supported in a Virtual Machine?
A31: No. Wonderware PAC has not been tested on Virtual Machines even though Wonderware has made a statement concerning support for products running in a virtual machine environment.