Watlow CLS200, MLS300 and CAS200 Manual do Utilizador Página 1

CLS200, MLS300, and CAS200CommunicationsSpecification Watlow Anafaze Repairs and Returns: 1241 Bundy Blvd.Winona, MN 55987 Customer Service: Phone..

4 Communications Specification Chapter 1: ANAFAZE/AB Protocol Transaction Sequence Here are the four steps in a transaction between the host softwa

Chapter 1: ANAFAZE/AB ProtocolCommunications Specification 5 This flowchart shows one way for the host software to handle errorchecking. (If you are

6 Communications Specification Chapter 1: ANAFAZE/AB Protocol Packet Format Messages are transmitted in the form of packets. Command and replypacke

Chapter 1: ANAFAZE/AB ProtocolCommunications Specification 7 CMD • The CMD byte indicates the command that the host software sends to the controlle

8 Communications Specification Chapter 1: ANAFAZE/AB Protocol ADDL • The low byte of the beginning data table address of the block of data to read

Chapter 1: ANAFAZE/AB ProtocolCommunications Specification 9 For instance, the block read example shown in the examples section, adds x08 00 01 00 0

10 Communications Specification Chapter 1: ANAFAZE/AB Protocol Examples The host software sends two kinds of commands: block reads and blockwrites.

Chapter 1: ANAFAZE/AB ProtocolCommunications Specification 11 The next picture shows the read command. The controller sends a DLE-ACK:x10 02 08

12 Communications Specification Chapter 1: ANAFAZE/AB Protocol Then the controller sends its reply:Then the host software sends a DLE-ACK:x10 02

Chapter 1: ANAFAZE/AB ProtocolCommunications Specification 13Block WriteThis section describes the block write command.This example shows the block w

Copyright © 1996, 1997, 2003Watlow Anafaze Information in this manual is subject to change without notice. No part of this publication may bereprod

14 Communications SpecificationChapter 1: ANAFAZE/AB ProtocolHere’s a picture of the controller’s reply:Then the host software sends a DLE-ACK:Messa

Chapter 1: ANAFAZE/AB ProtocolCommunications Specification 15Data for a Write CommandFor a block write command, the block contains the bytes to write

16 Communications SpecificationChapter 1: ANAFAZE/AB ProtocolAnafaze/AB Data Table SummaryEach address holds one byte of data. Each parameter value

Chapter 1: ANAFAZE/AB ProtocolCommunications Specification 17Ordering of Heat and Cool Channel ParametersFor parameters that have both heat and cool

18 Communications SpecificationChapter 1: ANAFAZE/AB Protocol15 Ambient Sensor Readings 0720 SI 216 Pulse Sample Time 0730 UC 117 High Process Varia

Chapter 1: ANAFAZE/AB ProtocolCommunications Specification 1954 Ready Event States 1180 UC MAX_RSP * MAX_DIGOUT_BYTES55 Segment Setpoint 1280 SI MAX_

20 Communications SpecificationChapter 1: ANAFAZE/AB Protocol84 PV Retransmit Minimum Input 4330 UI MAX_CH * 485 PV Retransmit Minimum Output 43C0 U

Chapter 2: Modbus-RTU ProtocolCommunications Specification 21Chapter 2: Modbus-RTU ProtocolOverviewTransactions on Modbus-RTU NetworksStandard Modbus

22 Communications SpecificationChapter 2: Modbus-RTU ProtocolThe Query-Response CycleThe QueryThe function code in the query tells the addressed slav

Chapter 2: Modbus-RTU ProtocolCommunications Specification 23• 8 data bits, least significant bit sent first• 2 stop bits• No parityError Check FieldCy

ContentsCommunications Specification i Contents Overview... 1 In This Manual ..

24 Communications SpecificationChapter 2: Modbus-RTU ProtocolWhen a message is sent from a master to a slave device, the functioncode field tells the

Chapter 2: Modbus-RTU ProtocolCommunications Specification 25The data field can be nonexistent (of zero length) in certain kinds ofmessages, where the

26 Communications SpecificationChapter 2: Modbus-RTU ProtocolThis process is repeated until eight shifts have been performed. After thelast shift, th

Chapter 2: Modbus-RTU ProtocolCommunications Specification 27NOTEThe function will override the controller’s memory protectstate and the coil’s disab

28 Communications SpecificationChapter 2: Modbus-RTU Protocolresponse is returned. This function is the only one that brings the port out of Listen O

Chapter 2: Modbus-RTU ProtocolCommunications Specification 29operation, or power-up.Subfunction Data Field (Query) Data Field (Response)x00 0C x00 00

30 Communications SpecificationChapter 2: Modbus-RTU ProtocolWriting DataWatlow Anafaze controller memory is divided into approximately 100parameters

Chapter 2: Modbus-RTU ProtocolCommunications Specification 31ExamplesRead ExamplesThe data read must be sequentially located. If you’re reading a coi

32 Communications SpecificationChapter 2: Modbus-RTU ProtocolWrite ExamplesThe data written is echoed back to the controller.Sample Packet for Host T

Chapter 2: Modbus-RTU ProtocolCommunications Specification 33Sample Packet for Host Transmission, a Multipoint WriteThe data must be written to seque

ContentsCommunications Specification ii Chapter 3: Controller Parameter Descriptions ... 39 Correlating Menu Items with Parameters ...

34 Communications SpecificationChapter 2: Modbus-RTU ProtocolThe storage requirements for some parameters depend on the number ofdigital inputs or di

Chapter 2: Modbus-RTU ProtocolCommunications Specification 35Relative and Absolute Modbus AddressesIn the tables on the following pages, absolute add

36 Communications SpecificationChapter 2: Modbus-RTU Protocol27 Not used 40942 03AD UC 128 Override Digital Input 40943 03AE UC 129 Override Polarity

Chapter 2: Modbus-RTU ProtocolCommunications Specification 3761 Output Limit 48147 1FD2 SI MAX_CH * 262 Output Limit Time 48213 2014 SI MAX_CH * 263

38 Communications SpecificationChapter 2: Modbus-RTU Protocol87 Cacade Base Setpoint 49306 2459 SI MAX_CH88 Cascade Minimum Setpoint 49339 247A SI MA

Chapter 3: Controller Parameter DescriptionsCommunications Specification 39Chapter 3: Controller Parameter DescriptionsThis section provides specific

40 Communications SpecificationChapter 3: Controller Parameter DescriptionsIn the following tables, “RS” in the Product(s) column indicates that thep

Chapter 3: Controller Parameter DescriptionsCommunications Specification 41Input Units All Units 33Input Reading Offset All Units 17, 18Reversed T/C

42 Communications SpecificationChapter 3: Controller Parameter DescriptionsCool Output Action Not CAS/CAS200 4, 98Cool Output Limit Not CAS/CAS200 61

Chapter 3: Controller Parameter DescriptionsCommunications Specification 43Additional menus are found in controllers with Ramp and Soak andEnhanced F

ContentsCommunications Specification iii Last Segment (51) ... 62Number of Cycles (52)...

44 Communications SpecificationChapter 3: Controller Parameter DescriptionsSegment ## Edit Seg Trggrs RS Front Panel onlySeg ## Trig # Input NR RS 56

Chapter 3: Controller Parameter DescriptionsCommunications Specification 45Parameters (by number)Proportional Band/Gain (0)The MLS and CLS controller

46 Communications SpecificationChapter 3: Controller Parameter DescriptionsInput Type (3)This parameter specifies the input type.• Range: 0 to 19 defin

Chapter 3: Controller Parameter DescriptionsCommunications Specification 47• Proportional band• High process alarm• Low process alarm• Deviation band

48 Communications SpecificationChapter 3: Controller Parameter DescriptionsBits 0 and 1 work together to determine some of the output’scharacteristic

Chapter 3: Controller Parameter DescriptionsCommunications Specification 49• Default: 3 scans.Output Value (8)This parameter contains the output valu

50 Communications SpecificationChapter 3: Controller Parameter DescriptionsNOTEProcess alarms, deviation alarms, and failed sensor alarmsare set indi

Chapter 3: Controller Parameter DescriptionsCommunications Specification 51When using the Anafaze protocol, when an Alarm_Status bit haschanged, and

52 Communications SpecificationChapter 3: Controller Parameter DescriptionsAmbient Sensor Readings (15)This parameter returns the value of the system

Chapter 3: Controller Parameter DescriptionsCommunications Specification 53NOTEUse the High Process Variable and Low Process Variablefor an offset on

ContentsCommunications Specification iv Controller Address (101)... 77Baud Rate (102) ...

54 Communications SpecificationChapter 3: Controller Parameter Descriptions(3) If the original precision value (from the table below) was a negative

Chapter 3: Controller Parameter DescriptionsCommunications Specification 55The Anafaze/AB protocol returns all 8 bits in 1 byte. See the tablebelow.T

56 Communications SpecificationChapter 3: Controller Parameter DescriptionsSystem Status (30)The system status command consists of internal registers

Chapter 3: Controller Parameter DescriptionsCommunications Specification 57Data Changed Register (32)The data changed register acts as a First-In-Fir

58 Communications SpecificationChapter 3: Controller Parameter DescriptionsFor linear and pulse inputs, users can select three characters to display.

Chapter 3: Controller Parameter DescriptionsCommunications Specification 59Process Power Digital Input (36)Enable the thermocouple short detection fe

60 Communications SpecificationChapter 3: Controller Parameter Descriptions• Range: 0 to 255.• Default: 5.Startup Alarm Delay (40)This parameter desi

Chapter 3: Controller Parameter DescriptionsCommunications Specification 61• Default: 0 (no low deviation alarm output).Channel Profile and Status (46

62 Communications SpecificationChapter 3: Controller Parameter DescriptionsCurrent Segment (47)This parameter returns the segment number that is curr

Chapter 3: Controller Parameter DescriptionsCommunications Specification 63• Default: 19.Number of Cycles (52)This parameter represents the total num

OverviewCommunications Specification 1 Overview This reference guide is designed to help applications softwareprogrammers with the following tasks:

64 Communications SpecificationChapter 3: Controller Parameter DescriptionsIn the Anafaze/AB protocol, the states are stored as bits in 5 bytes. Each

Chapter 3: Controller Parameter DescriptionsCommunications Specification 65• Default: 0 (no trigger assigned).Bits 0 to 3 determine the input number

66 Communications SpecificationChapter 3: Controller Parameter DescriptionsBits 0 to 5 determine the output number for an event: Segment Time (58)Thi

Chapter 3: Controller Parameter DescriptionsCommunications Specification 67* The controller toggles a bit in the data-changed register to notify high

68 Communications SpecificationChapter 3: Controller Parameter DescriptionsAlarm_Control (63)Setting a bit for an alarm in the Alarm_Control variable

Chapter 3: Controller Parameter DescriptionsCommunications Specification 69This variable is currently used for deviation and process alarms. Processa

70 Communications SpecificationChapter 3: Controller Parameter DescriptionsOutput Linearity Curve (69)This parameter lets users set heat and cool out

Chapter 3: Controller Parameter DescriptionsCommunications Specification 71• Default: 1000 (10.00 volts) or 2000 (20.00 mA).Save Setup to Job (73)Thi

72 Communications SpecificationChapter 3: Controller Parameter DescriptionsT/C Failure Detection Flags (78)This parameter determines the thermocouple

Chapter 3: Controller Parameter DescriptionsCommunications Specification 73WARNINGThis command should only be used when it is necessary toperform the

2 Communications Specification Overview

74 Communications SpecificationChapter 3: Controller Parameter DescriptionsPV Retransmit Minimum Output (85)This parameter specifies the minimum outpu

Chapter 3: Controller Parameter DescriptionsCommunications Specification 75Cascade Heat/Cool Span (90)This parameter is multiplied by the heat and co

76 Communications SpecificationChapter 3: Controller Parameter Descriptions• Range: –999 to 9999 (depending on the precision in the master loop).• De

Chapter 3: Controller Parameter DescriptionsCommunications Specification 770 = Reverse1 = Direct• Default: 0 for heat outputs, 1 for cool outputs.Con

78 Communications SpecificationChapter 3: Controller Parameter Descriptions2 = 19200• Default: Varies by controller.Ready Events (103)This parameter

Appendix A: Communications DriverCommunications Specification 79Appendix A: Communications DriverCompiling and LinkingThe driver is compiled and link

80 Communications SpecificationAppendix A: Communications Driverchar error_check; Set to BCC, or CRC. BCC = 1. CRC = 2;Example Call:Init_Comm_Port(1

Appendix A: Communications DriverCommunications Specification 81char sts; Controller status. See the AnafazeController/Host InterfaceDataand Communic

82 Communications SpecificationAppendix A: Communications DriverExample Call:return_value = DownLoad(TYPE_CLS8, 1, SETPT, 0, 8, sp); This callUploads

GlossaryCommunications Specification 83GlossaryACK (Acknowledge) A control code that signals that a syntactically correct message packet has been rec

Chapter 1: ANAFAZE/AB ProtocolCommunications Specification 3 Chapter 1: ANAFAZE/AB Protocol This section explains the ANAFAZE/Allen Bradley protocol

84 Communications SpecificationGlossaryDeadband, alarmThe range through which a process variable must travel from the alarm setpoint toward the proce

GlossaryCommunications Specification 85LSB Least Significant Byte. For all two-byte data types, the LSB is transmitted before the MSB (Most Significant

86 Communications SpecificationGlossarySet, bit See Cleared, bit.Single-bit errorAn error in which only one bit is incorrect.Stop bit The last part o