MicroBrick I/O - Industrial Control Links

More documents

Recommendations

Info

MicroBrick Distributed I/O ModulesReading the Analog Inputs on the MicroBrick is the same as reading the DI's only adifferent data type:You should now have a Network Event List like the following:The setup is complete. Connect your I/O module to the port defined, make sure theSlave number and baud rate are correct and download the application to the controller.Consult your hardware manual for the appropriate cabling to connect your I/Omodule.Different products have different I/O based on the model numberand type. Interfacing to all of them is similar to what is shown here.32Copyright © 2007 Industrial Control Links, Inc. All Right Reserved
MicroBrick Distributed I/O ModulesDF1 CommunicationsDue the installed base of Allen-Bradley programmable logic controllers and the highcost of protocol adapter modules, the DF1 protocol is a popular means of interfacingthese PLCs with ICL controllers. In the DF1 protocol, a single Master communicateswith up to 254 slaves. Slaves do not send messages on their own; they respond tomessages from the Master. DF1 is designed to operate over serial networks; RS-232 forshort point-to-point connections, RS-485 for longer distance hard-wired networks, andradios and modems for even longer distances. DF1 can support three types of data;bits, integers and floating point numbers. DF1 over Ethernet is not supported at thistime.MicroBrick units can communicate using Allen-Bradley’s DF1 protocol using the DH-485 transport layer. This protocol allows the RTU to respond to messages that are sentfrom a DF1 master device. These messages can read and write information stored inregisters.Data Type DF1 Type DescriptionDigital Input B3 Read Only bitsDigital Output B13 Read/Write bitsAnalog Input N7 Read Only 16-bit valuesAnalog Output N17 Read/Write 16-bit valuesNote: 32-bit registers are not currently supported in ICL’s RTU implementation of DF1.Note: ScadaWorks users will not use the ‘N’ character when setting up r/w DF1 events. Instead they willselect the ‘Number’ option from the ‘Source’ dropdown in the network event configuration window and enterin either ‘13’ or ’17’.’ICL RTUs support the serial, half-duplex version of DF1with CRC errorchecking. BCC error checking in RTU units is not supported at this timeCopyright © 2007 Industrial Control Links, Inc. All Right Reserved33
Page 7: MicroBrick Distributed I/O ModulesS
Page 10 and 11: MicroBrick Distributed I/O ModulesI
Page 12 and 13: MicroBrick Distributed I/O ModulesR
Page 14 and 15: MicroBrick Distributed I/O ModulesM
Page 16 and 17: MicroBrick Distributed I/O ModulesO
Page 20 and 21: MicroBrick Distributed I/O ModulesV
Page 22 and 23: MicroBrick Distributed I/O ModulesD
Page 24 and 25: MicroBrick Distributed I/O ModulesC
Page 30 and 31: MicroBrick Distributed I/O ModulesY
Page 36 and 37: MicroBrick Distributed I/O ModulesW
Page 38 and 39: MicroBrick Distributed I/O ModulesP
Page 46 and 47: MicroBrick Distributed I/O Modulesr
Page 50 and 51: MicroBrick Distributed I/O Modulesr
Page 53 and 54: Type II - Deg C -40.1ºC to 203.4º
Page 55 and 56: MicroBrick Distributed I/O Modules-
Page 57 and 58: MicroBrick Distributed I/O ModulesT
Page 59 and 60: Register Map - Universal Input UI8I
Page 61 and 62: Discrete I/O ModulesMicroBrick Dist
Page 63 and 64: MicroBrick Distributed I/O Modulesl
Page 65 and 66: Modbus Register MapSTATUS (Read Onl
Page 67 and 68: MicroBrick Distributed I/O Modulesp
Page 69 and 70: MicroBrick Distributed I/O ModulesL
Page 71 and 72: Combo I/O ModulesMicroBrick Distrib
Page 73 and 74: MicroBrick Distributed I/O Modulesi
Page 75 and 76: MicroBrick Distributed I/O ModulesO
Page 77 and 78: Register Map - Combo I/O MicroBrick
Page 79 and 80: MicroBrick Distributed I/O ModulesC

MicroBrick I/O - Industrial Control Links

Create successful ePaper yourself

Delete template?

Save as template?