Subscribe to Our Youtube Channel
Summary of Contents for Watson-Marlow MC100
- Page 1 User’s Manual MC100 MC100 Pump Control Module User’s Manual (DeviceNet) MC100 DeviceNet OM 1.01 EN.doc Version: 1.01 Page 1 of 36...
-
Page 2: Table Of Contents
5.3.4 Dipswitch ..........................13 Configuring the fieldbus network to the MC100 ..............14 Connecting the MC100 and the pumps for the first time ............14 Configuring the DeviceNet network..................15 Operating the MC100 ......................16 Process Data Exchange (Cyclic data)..................16 7.1.1... - Page 3 Users Manual MC100 Declaration of Conformity......................36 MC100 DeviceNet OM 1.01 EN.doc Version: 1.01 Page 3 of 36...
-
Page 4: Introduction
This manual should be read thoroughly before using the MC100. It is strongly advised that No wiring is connect or disconnect on the MC100, while power supply is turned ON The MC100 must mounted in an environment, that adheres to EN 60204-1:2006 4.4.3-6 The MC100 must not to be used in explosion hazardous environments. -
Page 5: General Description Of Mc100
2 General description of MC100 2.1 Overview MC100 is a Pump control module capable of controlling up to 16 WMF Pumps. The basic function is to receive filling data from the filling line control system through an industrial fieldbus and to calculate operating values for the pumps. -
Page 6: Technical Specifications
Users Manual MC100 MC100 holds no recipes, historical data or audit trail, only current runtime parameters for the filling system is stored internally. 3 Technical specifications 3.1 Dimensions MC100 DeviceNet OM 1.01 EN.doc Version: 1.01 Page 6 of 36... -
Page 7: Specifications
3.2 Specifications Fieldbus: DeviceNet Pumps: Max 16 pumps can be connected and controlled. Pumps must be able communicate with MC100 via FlexNet protocol. Material and surface treatment: Mounting box made from aluminium. All aluminium parts anodised (conductive). Environmental: Ingress protection according to IP30. -
Page 8: Unpacking And Inspection Of Mc100
Users Manual MC100 3.3 Unpacking and inspection of MC100 With the shipment of MC100 you should receive: • The MC100 • Declaration of Conformity • CD-rom with documentation: Manual for installation, programming and service of MC100 Documentation and support-files for Anybus CompactCom fieldbus module Please check that all ordered items have been received and that no items were damaged during transport. -
Page 9: Identifying The Parts
3.4 Mounting 3.4.1 Choosing a place to mount the MC100 The MC100 must be mounted in an environment that adheres to the specifications in 3.2. Be sure that the MC100 is also protected from the following conditions Rain and moistures... -
Page 10: Wiring
Connector Connect with N.C. +24V PHOENIX PHOENIX MC 0,5/ 4 –G-2,5THT FK MC 0,5/ 3 –ST 2,5 Use 0.5 mm2 wires, terminal tubes must be minimum 8 mm long. MC100 DeviceNet OM 1.01 EN.doc Version: 1.01 Page 10 of 36... - Page 11 9 pole SubD female RS485 – B Fieldbus Interface DeviceNet Connect with for example Black Data Blue CAN_L PHOENIX Part number Shield SHIELD 28 62 57 6 Data White CAN_H +24V MC100 DeviceNet OM 1.01 EN.doc Version: 1.01 Page 11 of 36...
-
Page 12: Fieldbus Network Node Address And Front Plate Indicators
P4/P5 display for 5 seconds, where it is possible to change back to the old address. After 5 seconds the MC100 will do a total factory reset and start up using the new address. 5.2 P1/P2 LED indicators:... -
Page 13: Display P4/P5
Users Manual MC100 5.3 Display P4/P5 This display is used for general indication of the start up states in the MC100 and for various other purposes. 5.3.1 Start up states: P4/P5 Description Note Initial start up state S.U. Internal communications started S.0. -
Page 14: Configuring The Fieldbus Network To The Mc100
“ MC100 MFSC Ver. x.yy.” (x.yy will be the current version) The MC100 will then try to identify all connected pumps on the Flexnet; the LED indicator X1 will flicker and finally be steady green. If for example 4 pumps are detected, the following line will be: “Pumps: 1 2 3 4... -
Page 15: Configuring The Devicenet Network
Users Manual MC100 6.2 Configuring the DeviceNet network The description is on how to configure the MC100 for DeviceNet using RSNetWorx is described in the HMS document DeviceNet RSNetWorx 1 03.pdf, the newest verison can be downloaded from http://www.hms.se/support/support.asp?PID=324&ProductType=Anybus-CompactCom. In section 4.4... -
Page 16: Operating The Mc100
When connected to the Fieldbus network the MC100 will always transmit and receive 1 word for the MC100 function and minimum 1 word for the pumps (even if only 1 pump is connected there will still be allocated 1 word, where the highest 8 bits will be empty). -
Page 17: Process Status Bits From Mc100
Alarm Note B1.4 in the MC100 control bits is used as a READY- /BUSY bit for explicit parameter transfers, the bit will go low when accepting an explicit parameter transfer and will go high again when the data is processed, thereby enabling a new transfer, this handshake mechanism MUST be respected otherwise data will be lost. -
Page 18: Process Control Bits For The Pumps
Bit 7 Reserved for future use The DISP bit has higher priority and must be cleared before setting the PUMP bit. Available for pumps able to handle this function (GD30). MC100 DeviceNet OM 1.01 EN.doc Version: 1.01 Page 18 of 36... -
Page 19: Process Status Bits From The Pumps
Minimum one word is received with status from the pumps. The number of pumps connected is a parameter, which is part of the configuration of the number of cyclic bytes of the network. The MC100 will always automatically send the number of bytes for the connected pumps, after a factory reset to defaults. -
Page 20: Operation Parameters / Parameter Specifications
It’s possible for to read minimum and maximum values from the ADI’s to be used as limitations for inputs, but the MC100 will also handle these ranges and discard the input and set a warning if out of range, the warning will automatically be cleared if a value within the range is sent, but can also be cleared using B1.5 Alarm reset bit in MC100 control bits. -
Page 21: List Of Additional Adi's
ADI 8, 15 and ADI 13, 16 and ADI 14, 17 are equal except for the data types, where ADI15,16,17 are available to make things more easy in Allan Bradley PLC’s. MC100 DeviceNet OM 1.01 EN.doc Version: 1.01 Page 21 of 36... -
Page 22: Detailed Description Of The Adi's
Users Manual MC100 7.2.3 Detailed description of the ADI’s Default values are values in the MC100 after a factory default reset, the values depends on the pump types and the examples below are for PD12B pump types Instance Volume Attribute ID... - Page 23 0,5 * the value In instance 1 Value from instance 1 Default value Double Integer (no calibration done) Write Data value Double Integer >= Min and <= max value MC100 DeviceNet OM 1.01 EN.doc Version: 1.01 Page 23 of 36...
- Page 24 Alarm – number is a reference to the Alarm list (Chapter 8).The text-string can also be read from Instance 9, Attribute 7.The number is also flashing on the 2-digit display [AL][number] MC100 DeviceNet OM 1.01 EN.doc Version: 1.01 Page 24 of 36...
- Page 25 Warning – number is a reference to the Warning list The text-string can also be read from Instance 9, Attribute 8. The number is also flashing on the 2-digit display [ER][number] MC100 DeviceNet OM 1.01 EN.doc Version: 1.01 Page 25 of 36...
- Page 26 Tube 2 Tube 3 Tube 4 Tube 5 Tube 6 Tube 7 Tube 8 Tube 9 Tube 10 NB! Tube steps/ml = 0 denotes no tube in that entry. MC100 DeviceNet OM 1.01 EN.doc Version: 1.01 Page 26 of 36...
- Page 27 The values in the table are the inner diameter of the tube multiplied by 10. Example Tube 3 = 32, equals an inner diameter of 3.2 mm. NB! Tube diameter = 0 denotes no tube in that entry. MC100 DeviceNet OM 1.01 EN.doc Version: 1.01 Page 27 of 36...
- Page 28 Tube 2 Tube 3 Tube 4 Tube 5 Tube 6 Tube 7 Tube 8 Tube 9 Tube 10 NB! Tube steps/ml = 0 denotes no tube in that entry. MC100 DeviceNet OM 1.01 EN.doc Version: 1.01 Page 28 of 36...
-
Page 29: Alarm And Warnings
8 Alarm and warnings 8.1 Alarms handling When MC100 is in Alarm state, the only possible action is to reset the alarm. Only applies if the alarm causes are removed, otherwise the alarm will re-appear at the next attempt. Alarms are cleared one-by-one, starting top down – meaning lowest number first. -
Page 30: Warnings Handling
Calibration is out of range Calibration attempt for individual Common calibration in parallel pump, calibrate pump 0 only. Calibration attempt for Pump 0, Individual calibration in serial calibrate pumps individually MC100 DeviceNet OM 1.01 EN.doc Version: 1.01 Page 30 of 36... -
Page 31: Trouble Shooting
Solution: First check if all the pump(s) has power applied and are indicating power ON. If this is OK, then the MC100 has stored a different configuration and must be reconfigured using the factory default configuration. Make a factory reset to default by following the steps below: 1. -
Page 32: Opening The Mc100 For Service/Replacement Of Pcb's
Users Manual MC100 9.2 Opening the MC100 for service/replacement of PCB’s Power OFF for the 24V to the Module Remove all cables attached the MC100. To access the 2 circuit boards, remove the front cover by removing the 4 countersunk pozidrive screws and the front cover will come off. -
Page 33: Decommissioning
Disconnect all connections to other equipment. 10.2 Environmental conditions / -regulations A MC100 is subject to the WEEE-system and may not be disposed using normal refuse collection. The machine must be collected and disposed separately as it contains electrical components such as batteries, electrolytic capacitors and printed circuit boards. -
Page 34: Appendix 1
If more Pumps are connected to the MC100, they can, if they are of the same type, work synchronously with the same set of parameters. In parallel mode, only parameters in Pump 0 will be used i.e. - Page 35 12.1 Tube tables 12.1.1.1 PD12 Tube Number Inner Diameter [mm] 12.1.1.2 PD22 Tube Number Inner Diameter [mm] 10.0 12.5 12.1.1.3 GD30 Tube Number Inner Diameter [mm] 1.0 (pseudo number) MC100 DeviceNet OM 1.01 EN.doc Version: 1.01 Page 35 of 36...
- Page 36 According to the provisions in the Directives: 2004/108/EC On the approximation of the laws of the Member States relating to electromagnetic compatibility Signature: April 2009 Jørn Jeppesen, Development Manager Ringsted, Denmark MC100 DeviceNet OM 1.01 EN.doc Version: 1.01 Page 36 of 36...
Need help?
Do you have a question about the MC100 and is the answer not in the manual?
Questions and answers