Module # 020 MUST HAVE SHOULD HAVE COULD HAVE

Slides:



Advertisements
Similar presentations
MUST HAVE SHOULD HAVE COULD HAVE Module # 000. Qi Matroller Technical Training session 2006 Presented by Bradley Timm & Rodger Jeffery.
Advertisements

IND780batch EM, CM, and Material Path setup. Internal usage only 2 Batch Terminology - A Simple System Overview Control I/O Module - Defines what I/O.
Ethernet Switch Features Important to EtherNet/IP
Chapter 7: System Buses Dr Mohamed Menacer Taibah University
TCP-IP Primer David Cozens. Targets Have a basic understanding of Ethernet network technology Be aware of how this technology is applied on the 5000 series.
Niobrara R&D Corp Compact PLC Upgrades With the CERI.
MUST HAVE SHOULD HAVE COULD HAVE Module # 150. Dealing with Process Upsets Objectives –Will be able to recognize an Upset –Will be able to analyze an.
Introduction to the Enhanced AIM When Q.i was first introduced, a ladder logic driver program – called the Application Interface Module (AIM) - was created.
1 Hardy Process Solutions – New Product Introduction HI6600 Series – Modular Sensor System Hardy delivers productivity solutions to manufacturers and processors.
S88 structure used in system configuration
Switchgears Control Using SCADA System Based on PLC
1 Chapter 8 Local Area Networks - Internetworking.
TECH CH03 System Buses Computer Components Computer Function
Introduction. 2 What Is SmartFlow? SmartFlow is the first application to test QoS and analyze the performance and behavior of the new breed of policy-based.
CS335 Networking & Network Administration Tuesday, April 20, 2010.
1 K. Salah Module 4.3: Repeaters, Bridges, & Switches Repeater Hub NIC Bridges Switches VLANs GbE.
MUST HAVE SHOULD HAVE COULD HAVE Module # 010. Qi Hardware Objectives Recognize hardware Know how to interface to field equipment Know the 4 different.
CHE 185 – PROCESS CONTROL AND DYNAMICS DCS AND PLC FUNDAMENTALS.
SCADA and Telemetry Presented By:.
Basic Concepts of Computer Networks
1 MUST HAVE SHOULD HAVE COULD HAVE Module # Configuring the Qi Cluster Objectives: Know the sequence of configuring the Qi Cluster Know how to.
Mapping Internet Addresses to Physical Addresses (ARP)
DMT File Management Common Problems Managing DMT files –Reliable Upload –Reliable Download –Where are the files kept? –Tedious Procedures Using DOS commands.
MUST HAVE SHOULD HAVE COULD HAVE Module # 120. Communicating with a Host Controller Will know: Supported communications Sequence of events when talking.
1 MUST HAVE SHOULD HAVE COULD HAVE Module # 140. Practical Class Exercise’s, 2 nd session Objectives: Know how to: –Setup a Flowmeter –add Channel based.
Momentum 2009 Spyder® for Plant Control John Hutchey – Lou Jones.
TAKING CARE GUIDELINES Sub-title Place, Month Year.
MXclusters, Redundancy, XRS12, EPA3 Yang Guo Manager of Business Development for Asia Pacific.
CTSP TRAINING Router 101 And Networking Basics. You Don’t Need Internet Access to Run or Connect your devices to an Ethernet switch or Router Enable DHCP.
Automatic Software Testing Tool for Computer Networks ADD Presentation Dudi Patimer Adi Shachar Yaniv Cohen
Internal usage only Nestle Chembong – IND780 Q.i System Overview.
CHAPTER 3 TOP LEVEL VIEW OF COMPUTER FUNCTION AND INTERCONNECTION
1 © 2003, Cisco Systems, Inc. All rights reserved. CCNA 2 Module 9 Basic Router Troubleshooting.
MUST HAVE SHOULD HAVE COULD HAVE Module # 040. PAC Algorithms Which one to use? Objective: Know when to use which algorithm. Know how each Algorithm behaves.
Top Level View of Computer Function and Interconnection.
TCP/IP TCP/IP LAYERED PROTOCOL TCP/IP'S APPLICATION LAYER TRANSPORT LAYER NETWORK LAYER NETWORK ACCESS LAYER (DATA LINK LAYER)
Chapter 6 – Connectivity Devices
LAN Switching and Wireless – Chapter 1
1 © 2003, Cisco Systems, Inc. All rights reserved. CCNA 4 v3.0 Module 4 ISDN and DDR.
MUST HAVE SHOULD HAVE COULD HAVE Module # 130. Maintaining a Qi Cluster Objectives –Know which files must be backed up –Know how to restore a system from.
1 Module # A About your Q.i training program presented by : Rodger Jeffery company: Mettler Toledo Inc duration: 15 mins.
MUST HAVE SHOULD HAVE COULD HAVE Module # 030. Qi Parameters defined Objectives Know which two PAC databases exist within the Qi Be aware of the parameters.
EEE440 Computer Architecture
Module 1: Configuring Routing by Using Routing and Remote Access.
1 OUT OF THE BOX configurable SOLUTIONS powered by.
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network, Enhanced Chapter 12: Planning and Implementing Server Availability and Scalability.
1 MUST HAVE SHOULD HAVE COULD HAVE. 2 Module # C Functions that need to be considered for Batch Material Transfer Controls presented by : Rodger Jeffery.
1 Module # A About your Q.i training program presented by : Rodger Jeffery company: Mettler Toledo Inc duration: 15 mins.
GPRS functionality overview in Horner OCS. GPRS functionality – Peer to Peer communication over GPRS – CSCAPE connectivity over GPRS – Data exchange using.
Networking And their components. What is Networking? In it’s simplest term, networking is when two or more things are able to communicate and understand.
Virtual Local Area Networks (VLANs) Part II
Hardware Introduction – Standard vs Q.i
Quality Improvements Quantity Increases Quantifiable Results Configuration and Run Exercise Press the Space Bar when ready to Continue.
IND780batch Model Code Order Examples. Internal usage only 2 IND780batch – Product Circle Hardware Security Key (I-button) Manual, Auto, & Auto with Q.i.
HDL-MGSM.431. Description MGSM.431 is an automation module based on GSM monitoring and controlling. Being at a great distance you can operate a target.
Technical Introduction April Internal usage only 1 General Features  Self contained batch solution for small, standalone applications.  All functionality.
Hardware, 010 – Revision notes Scales use Controller board O/Ps for Feed Control (FCE’s) Flow meters use their own on board O/Ps for Feed Control (FCE’s)
MUST HAVE SHOULD HAVE COULD HAVE Module # Bonus. Screen Captures with notes The following set of slides provides the Screen captures of various Feeds.
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network, Enhanced Chapter 12: Planning and Implementing Server Availability and Scalability.
Do-more Technical Training
Do-more Technical Training
Chapter 9: Virtual Memory
Informatica PowerCenter Performance Tuning Tips
How SCADA Systems Work?.
William Stallings Computer Organization and Architecture 7th Edition
Presentation transcript:

Module # 020 MUST HAVE SHOULD HAVE COULD HAVE Talk about how it all fits together Module # 020

Qi System Architecture Objectives Know where the Qi physically fits, in the Control system Aware of Cluster’s and their growth structure  Be able to describe the function of the Matroller Be able to describe where the Matroller takes control of the batch sequence, and where it relinquishes control. Reference material: Qi –Technical Manual Ch 11 - Glossary

Configuration & Setup Sequence Plan hardware options (scale, flowmeter cards, etc) Construct (install cards) Calibrate instruments ------------------------------------------------------------------------------ Plan PAC configuration (# Material Paths, Channels) Configure PAC database Commision Materials and Channels Optimize PAC parameters System Overview Control Hardware

A Qi Cluster - standalone Valves controlled by Qi Matroller Valves controlled by Qi Matroller Flowmeter Reports Controlled via JagBASIC JagBASIC writes to shared data variables “Lite” will Support Two speed feed !

A Qi Cluster – PC Control Controlled via PC based application Valves controlled by Qi Matroller Valves controlled by Qi Matroller Flowmeter Reports Ethernet Qi 365 ! JagBASIC writes to shared data variables User Program Use: Mettler Toledo API UDP Commands

Optional A Qi Cluster - simple SeparateEthernet PLC is starting feeds using hardwired logic into the Matroller Inputs Only for small systems !! Optional Qi 365 ! SCADA Valves controlled by Qi Matroller AND PLC Valves controlled by Qi Matroller AND PLC SeparateEthernet Flowmeter PLC Start Abort 2x Scale Control of Matroller via discrete I/O NB: only for small systems due to limited I/O available Control wiring omitted for clarity 4x FlowM JagBASIC program required ! Valves controlled by Qi Matroller AND PLC

Optional A Qi Cluster - simple SeparateEthernet Qi 365 ! SCADA Valves controlled by Qi Matroller AND PLC Valves controlled by Qi Matroller AND PLC Optional Qi 365 ! SeparateEthernet SCADA Flowmeter PLC CNet 2x Scale PLC with one Qi on ControlNet Hub not shown 4x FlowM Valves controlled by Qi Matroller AND PLC

Requires a CNet comms card for CNet AND EtherNetIP !! A Larger Cluster Requires a CNet comms card for CNet AND EtherNetIP !! 2x Scale Term 4 CNet 4x FlowM 2x Scale Term 1 SeparateEthernet 4x FlowM 1 x ControlNet network 2 x Qi “Bridges” 1 x Qi “Master” 3 x Qi “Remote” 28 x Channels ( 1 to 28 ) 22 x Assembly Slots (1 to22), bridge 1 6 x Assembly Slots (1 to 6), bridge 2 1 x Ethernet TCP/IP network 4x FlowM Term 2 4x FlowM 4x FlowM Illustrate that there as the system grows additional “bridge” Qi will be required. Which is the Master? 2x Scale Term 3 2x Scale Ethernet Switch

Qi Matroller position in a Batching System Last control component in the sequence Receives Target and Material info (with implied Start Command) Reports back to Control system at the end of the Feed HMI PLC Qi Matroller Batch Server Multiple Recipes Target & Material Path Recipe Illustrating the movement of Command Qi processes the Recipe One Material (phase) at a time. Keeps a Channel and Material database

Commands The Matroller supports the following commands: Start Material Transfer. Start Material Transfer with Gross Weight Target. Start Hand Add. Acknowledge Material Transfer or Hand Add Complete Abort Material Transfer Reset Slow Step Timer Start Manual Mode Turn on FCE in Manual Mode – Target is ON Time Turn off FCE in Manual Mode Restart Auto Mode Complete Feed in Manual Mode Master Reset – Instrument channel Report Last Status Master Reset – Cluster Validate Aggregate Secondary Feeds Reset Local ControlNet Card Reset all ControlNet Cards in Cluster

Command Responses: (available after every command) After every command a response (Status) is available. SUCCESS – Command Complete SUCCESS – Start Gain-In-Weight Material Transfer Complete SUCCESS – Start Loss-In-Weight Material Transfer Complete. SUCCESS – Start Flow Meter Material Transfer Complete. SUCCESS – Start Validate Aggregate Feed Complete. SUCCESS – Start Hand Add Command Complete. Command Not Complete – Request status again after delay ERROR – Invalid Instrument Channel Number ERROR – Invalid Material-Path Table Index Number ERROR – Invalid Algorithm in Material-Path Table Entry ERROR – Invalid Feed Type in Material-Path Table Entry ERROR – Invalid Measuring Device Channel ERROR – Invalid Gain In Weight Feed and Dump to Empty Algorithm ERROR – Invalid Destination in Material Path Table Entry. ERROR – Other invalid data in Material Path Table Entry ERROR – Invalid data In Measuring Device Channel Table Entry ERROR – Requested add amount would bring Scale over capacity ERROR – Scale Device Currently over Capacity WARNING – Delayed start to feed due to overlapping feed. WARNING – Abort ignored, Time to Complete < Feed Override Time WARNING – Waiting for All Secondary Requests. WARNING – Waiting for Measuring Device Stability. ERROR – Device not configured or calibrated properly. ERROR – Communications Error ERROR – Invalid Command ERROR – Overlap Feed Request Error ERROR – Invalid Mode for Command ERROR – Requested add amount too small ERROR – Scale Device Currently under Zero ERROR – Instrument Malfunction ERROR – Target Weight is less than Spill ERROR – Response Timeout ERROR – Too many overlapping feeds ERROR – Invalid overlap group number ERROR – Not Enough Material.

Material controlled by PLC Qi wiring example 1 Material controlled by PLC +V MP2 MP3 CNet FCE Status is Read via the CNet Network MP1 Cyclic data is a slow update 3 materials Controlled by PLC PLC reads status of Qi FCE via CNet etc !! Update rate via Cnet is 500mS !! Qi must NOT be used like this - ever

Material controlled by PLC Qi wiring example 2 Material controlled by PLC +V MP2 MP3 CNet FCE Wired Directly To PLC MP1 PLC has a finite cycle time. This adds a varying delay to the Cutoff Control and degrades the accuracy 3 materials Controlled by PLC PLC reads status of Qi FCE PLC introduces delay !! Qi must NOT be wired like this

Material selected by PLC Qi wiring example 3 Material selected by PLC (steering Matrix) +V FCE MP2 MP3 CNet MP1 Same O/P is used by Qi to Control 3 Materials. PLC only ever has ONE of its Material Enables on at any one time. Called the Steering Matrix 3 material Controlled by 1 Qi O/P Qi is in DIRECT Control of the FEED Qi MUST be wired like this

Timing diagram – 3 MPs Qi FCE MP1 En MP2 En MP3 En Start Cmd MP1 Feeding Feeding Feeding Qi FCE MP1 En Note the OFF Delay ! MP2 En Special Note: The Material Enable (Select) MUST always stay on longer than the FCE O/P MP3 En Start Cmd MP1 Start Cmd MP2 Start Cmd MP3

Review questions How many simultaneous feeds can there be in a Matroller with 1 scale and 1 flowmeter  What will happen if the comms between the PLC and Matroller fails during a Feed Two, each Channel operates independently Qi will complete the Feed normally

Architecture, 020 - Revision notes The Qi Ethernet network must be physically separate from the admin and plant control network. (VLAN is sometimes acceptable) Do not rely on an Ethernet Switch to separate network traffic. Note the correct way of wiring the Qi O/P Controller board O/P1 is associated with ScaleA Controller board O/P2 is associated with ScaleB etc