REMOTE DEVICE USER REFERENCE SHEET FOR REMOTE SERIAL COMMUNICATION CONTROLLER LAN NODE PCB (RSC) Part No. 46S02790-0030 For use on MicroTrac DSD Local Area Network Effective 9/25/90 1
CONTENTS INTRODUCTION...3 HARDWARE DESCRIPTION...3 Power Requirements...3 LAN Interconnect...3 LAN Node Address Switches...3 RS-232 Serial Port Interconnect...4 LED...4 OPERATIONAL DESCRIPTION...4 LED States...4 RS-232 Serial Port...5 RS-232 Serial Port Parameters...5 RS-232 Serial Port Protocol...5 MSG Type Values...6 MSG Data Content...6 IEEE Single Precision Floating Point Format...15 Examples of RSC Messages...16 2
INTRODUCTION The Remote Serial Communications Controller LAN Node PCB (RSC) allows communication between an external device with an RS-232 serial port and products on the MicroTrac DSD LAN. The RSC has a single RS-232 port for communication to an external device with a serial port (e.g. IBM PC, terminal, etc.). The RSC communicates to MicroTrac DSD products through an ARCNET LAN using a proprietary message protocol defined by MagneTek. This protocol allows messages to be sent to and from the RSC in order to pass display, numeric, and logic information (e.g. Armature Current, Line Speed, Run, etc.). This document explains the hard-ware and software operations of the Remote Serial Communications Controller LAN Node PCB (RSC). In the text, hexadecimal numbers will have a prefix of 0 and a suffix of the letter H. For example, the hexadecimal number representing the decimal number 43 would be 02BH. Furthermore, the terms "most significant byte" and "least dignificant byte" are abbreviated as "msb" and "lsb", respectively. HARDWARE DESCRIPTION POWER REQUIREMENTS The power connector on the RSC is used to supply the RSC with power. To select a properly sized power supply, the current (I) requirements of the RSC for each of the voltages must be known. The I requirements are as follows: I for +5 VDC = 1250 ma I for +15 VDC = 0 ma I for -15 VDC = 270 ma I for +24 VDC = 0 ma LAN INTERCONNECT There are 2 connections to be made in order to connect the RSC to the LAN. The first connector, J6 (faston tab), is to be connected to chassis ground. This is necessary in order to provide a return path for the snubber network of the LAN. The other connector, J2, is a BNC connector to be connected to the ARCNET LAN coaxial cable. The RSC uses a High Impedence Transceiver (HIT) for signal transceiving in order to utilize a bus topology on the LAN. In order to meet LAN requirements, type RG-62/U coaxial cable must be used. NOTE For a full discussion of the LAN, refer to the MicroTrac DSD technical manual, TM 6100. LAN NODE ADDRESS SWITCHES The LAN Node address switches allow for the selection of the network ID. The RSC may have a Node address from 100 to 199. Since the Node address is in the hundreds range, the 1 in the hundred s place is assumed, and silk-screened on the PCB as a reminder. There is a rotary switch for each of the other two numeric positions, ten s place (S1) and one s place (S2). These switches must be set before power up, and remain set while powered up, for proper operation. If the switches are changed while powered up, then the LAN Node will get a new network ID; however, the software will not (and cannot) be made aware of the ID change, thus invalid operation will occur. RS-232 SERIAL PORT CONNECTION The RSC communicates with an external device through use of an RS-232 serial port. The RSC is set up as a Data Carrier Equipment (DCE). A 9-pin, D-type female connector (J4) is provided on the RSC to allow cable connections to the serial port. The function of each of the 3
pins on the connector is as follows: J4 SIGNAL PIN # NAME DESCRIPTION 1 DCD Data Carrier Detect. From RSC. A positive voltage is always provided on this pin to resolve the external device's needs if necessary. 2 RXDATA Receive Data. From RSC. Serial data is sent from the RSC to the external device through this pin. 3 TXDATA Transmit Data. To RSC. Serial data is sent from the external device to the RSC through this pin. 4 NC No connection 5 COM Common. Signal ground. 6 DSR Data Set Ready. From RSC. A positive voltage is always provided on this pin to resolve the external device's needs if necessary. 7 RTS Request To Send. To RSC. A negative voltage on this pin will prevent the RSC from sending data to the external device. 8 CTS Clear To Send. From RSC. A negative voltage on this pin indicates that the RSC is LED 9 NC No connection. not ready to receive data from the external device. There is an LED on the RSC (DS1) that is used to indicate the operating status of the RSC. OPERATIONAL DESCRIPTION LED STATES The LED on the RSC is used to indicate the operating status of the RSC. The way in which the LED gives its status is as follows: RSC OPERATING LED STATE STATUS On, steady On, blinking Off RS-232 SERIAL PORT Power is applied, and the RSC software is executing. Power is applied, the RSC software is executing, and the RSC is receiving LAN messages. Power is not applied, or power is applied and the RSC has experienced a fault and has halted execution. RS-232 Serial Port Paramaters The RSC has parameters which determine the speed and format of the serial 4
data. These parameters are fixed in the software and can only be changed by changing the software version and providing new EPROMs. The format of the data is 1 start bit, 8 data bits, no parity bit, and 1 stop bit, for a total of 10 bit transmission frame. The speed of the RS-232 serial data is 9,600 baud (bits/second). RS-232 Serial Port Protocol All messages passed to and from the RSC on the RS-232 serial port are in the following format: [ SOH NOT SOH LENGTH DRIVE # MSG TYPE MSG DATA CHECKSUM ] The SOH is a single byte field that is the first part of the start message synchronization sequence. It is represented by the ASCII SOH character, value 001H. It, together with the NOT SOH field, is to be used to synchronize the start of a message. The NOT SOH is a single byte field that is the second, and last, part of the start of message synchronization sequence. It is represneted by the logical NOT of the ASCII SOH character, value 0FEH. It, together with the SOH field, is to be used to synchronize the start of a message. The LENGTH is a single byte field that is the hexadecimal number of bytes in the message. The value of length is the sum of the number of bytes in the DRIVE #, MSG TYPE, MSG DATA and CHECKSUM fields. The DRIVE # is a single byte field that is the hexadecimal number of the drive that is being communicated with. When the RSC sends a message to the external device, the DRIVE # is the source of the message. When the RSC receives a message from the external device, the DRIVE # is the destination of the message. The range of valid DRIVE #'s is from 001H to 063H (1 to 99 decimal). The MSG TYPE is a single byte field that is the hexadecimal code whose value defines the significance and length of the message data. The MSG DATA is a multi-byte field whose contents are dependent upon the MSG TYPE field value. The CHECKSUM is a single byte field that is a byte wide checksum of the message, in hexadecimal format. The checksum is the sum of all previous characters except the start of message sychronization characters (SOH and NOT SOH). It is used to check the vaildity of the message. MSG Type Values. The following is a list of the message type values that are used: MSG TYPE MEANING 010H 011H 012H 013H Remote Logic Output Allocation Request Remote Numeric Output Allocation Request Remote Logic Input Configure Remote Numeric Input Configure MSG TYPE MEANING 020H 021H 022H 023H 024H 025H Display Node Request Display Abort Display Message ASCII Response Display Variable ASCII Response Display Value Response RDU Lockout Command 5
026H 027H 028H 029H 02AH 02BH 02CH 030H 031H 0DBH 0DCH 0DDH 0DEH 0DFH RDU Value Change RDU Configuration RDU Select Menu Item Command Display Logic Message ASCII Response Display Logic Variable ASCII Response Display Logic Value Response RDU Logic Value Change Numeric Update Message Logic Update Message Remote No Output Update Error Numeric Input Request Error Logic Input Request Error Numeric Output Allocation Error Logic Output Allocation Error MSG Data Content. Since the message data content is dependent upon the message type field value, the message data contents are defined in the order of message type value. The syntax of the message is shown with the most significant byte field on the left and the offset into the message data shown below the syntax. In the messages, reference is made to Channels and Subchannels. The PAC language identifies a physical input or output device by use of a Node, Channel and Subchannel number. The Node is a term normally used to identify the base address of devices connected to the LAN. Thus, for the RSC, the Node number is the setting on the LAN Node Address Switches. The Channel is the second level address to further define the location of information external to the PAC environment. To access information external to the PAC environment requires reference to that information by an address which includes all levels of addressing defined for that particular information. That is, to use a Channel number also requires the associated Node number such as Node 210, Channel 21. The Subchannel number refers to a specific input or output of a given Node and Channel. Remote Logic Output Allocation Request (010H) This message is sent to a Remote node at power-up when the drive wants to allocate a particular Remote logic output. [ MSG TYPE = 010H CHANNEL # OUTPUT TIME FAULT MASK LOGIC MASK ] 3-6 7-10 The CHANNEL # is a byte representing the channel selected on the Remote node. The Remote node should expect to see output updates within the prescribed time contained in OUTPUT TIME. The format of OUTPUT TIME is in number of whole seconds, not to exceed 36 seconds (a value of 0 means that there is no update time limit). If the Remote node does not see an output update within the prescribed time, it should take appropriate safe action (i.e. set the output to 0). The FAULT MASK is used when a timeout occurs. The FAULT MASK describes how the Remote node should react to a fault (no output within the prescribed time). A bit set to 0 in the FAULT MASK means the reaction to a fault should be to leave the output allocated. A bit set to 1 in the FAULT MASK means the reaction to a fault should be to deallocate the output. For example, if an output has not been updated within the time specified in OUTPUT TIME, then the output should be set to a safe state (i.e. set the output to 0). If later on an update message is received for the output, then the FAULT MASK is consulted. If the output's FAULT MASK bit is not set, then the output is still allocated and the latest update is allowed to change the state of the output. Of the output's FAULT MASK bit is set, then the output has been deallocated and is left 6
at the safe state until a new Remote Logic Output Allocation Request for the output is received. The FAULT MASK msb is at offset 3. Subchannel 0 corresponds to data bit 0 of the mask lsb, and Subchannel 31 corresponds to data bit 7 of the mask msb. The LOGIC MASK will have bits set for every bit on the Remote node that the drive wishes to allocate. Since the drive sends four bytes of logic information in each Logic Update message, the LOGIC MASK selects which bits are significant. Therefore, the Remote node must keep a copy of the LOGIC MASK for future use when the drive wants to set the state of a logic output. The LOGIC MASK msb is at offset 7. Subchannel 0 corresponds to data bit 0 of the mask lsb, and Subchannel 31 corresponds to data bit 7 of the mask msb. Remote Numeric Output Allocation Request (011H) This message is sent to a Remote node at power-up when the drive wants to allocate a particular Remote numeric output. It will also set the initial conditions for the numeric output. [ MSG TYPE = 011H CHANNEL # SUBCHANNEL # OUTPUT TIME FAULT DCP ] 3 4 5 The CHANNEL # is a byte representing the channel number selected on the Remote node. The SUBCHANNEL # is a byte representing which subchannel is used. The Remote node should expect to see output updates within the prescribed time contained in OUTPUT TIME. The format of OUTPUT TIME is in number of whole seconds, not to exceed 36 seconds (a value of 0 means that there is no update time limit). If the Remote node does not see an output update within the prescribed time, it should take appropriate safe action (i.e. set the output to 0). The FAULT byte is used when a timeout error occurs. The FAULT byte describes how tht Remote node should react to a fault (no output update within the prescribed time). FAULT set to 0 means the reaction to a fault should be to leave the output allocated. FAULT set to nonzero means the reaction to a fault should be to deallocate the output. For example, if an output has not been udated within the time specified in OUTPUT TIME, then the output should be set to a safe state (i.e. set the output to 0). If later on an update message is received for the output, then the FAULT byte is consulted. If the output's FAULT byte is 0, then the output is still allocated and the latest update is allowed to change the state of the output. If the output's FAULT byte is non-zero, then the output has been deallocated and is left at the safe state until a new Remote Numeric Output Allocation Request for the output is received. The DCP is the decimal point location to be used to display the numeric value. The DCP value is equal to the number of digits to the right of the decimal point. Remote Logic Input Configure (012H) This message is sent from a drive that wants to know the state of a logic input connected to a Remote node. If one or more of the desired input logic bits change state, then a LAN message must be sent back to the drive. A LAN message must also be sent at regular 4 second intervals fixed at the Remote node; the drive expects periodic updates, and will take appropraite action if it is not updated within 5 seconds. [ MSG TYPE = 012H CHANNEL # LOGIC MASK -5 SINK/SOURCE MASK ] 6-9 7
The CHANNEL # is a byte representing the selected channel on the Remote node. The LOGIC MASK is a 4 byte mask (msb at offset 2) used by the Remote node to inform it of which bits this particular drive is interested in (bit = 1 means the drive is interested). Subchannel 0 corresponds to data bit 0 of the mask lsb, and Subchannel 31 corresponds to data bit 7 of the mask msb. The SINK/SOURCE MASK is a 4 byte mask (msb at offset 6) used by the Remote node to inform it of what type of inputs are being configured (sink type or source type). This SINK/SOURCE field applies only to DC inputs that have the ability to be programmed for sink or source. When the DC input is grounded, then the input will be a logic "1" for sink or a logic "0" for source, respectively. The SINK/SOURCE MASK bit should be a "0" to specify sink or a "1" to specify source. Subchannel 0 corresponds to data bit 0 of the mask lsb, and Subchannel 31 corresponds to data bit 7 of the mask msb. Numeric Input Configure (013H) This message is sent from a drive that wants to know the value of a numeric input connected to a Remote node. If the numeric value of the input changes, then a LAN message must be sent back to the drive. A LAN message must also be sent at regular 4 second intervals fixed at the Remote node; the drive expects periodic updates, and will take appropriate action if it is not updated within 5 seconds. [ MSG TYPE = 013H CHANNEL # SUBCHANNEL # DCP ] 3 The CHANNEL # is a byte representing the selected channel of the Remote node. The SUBCHANNEL # is a byte representing which subchannel is used. The DCP is the decimal point location expected when inputting the numeric value. The DCP value is equal to the number of digits to the right of the decimal point. Display Node Request (020H) This is the request from a Remote node to the drive for display information. This request is made once and the drive responds by sending one of the Display ASCII Response messages to the appropriate Remote node, then updates the information on a regular basis using one of the Display Response messages, with no further requests necessary. This type of message is used whether the Remote node is modifying, or only displaying a particular piece of data. The drive will send updates when the data changes and at regular 4 second intervals. If the Remote node does not receive an update within 5 seconds, appropriate action should be taken, because the last received data may not be valid. When the operator changes the requested display at the Remote node, the Remote node must first cancel the current request (with the Display Abort message) before issuing the new Display Node Request. A particular RDU may only be receiving updates for one specific item of data at a time. [ MSG TYPE = 020H CHANNEL # SUBCHANNEL # -3 RDU # ] 4 The CHANNEL # must be 065H. The Subchannel # must be the desired Control Display Unit (CDU) Function Number defined in the PAC diagram. The msb of the SUBCHANNEL # is at offset 2. channel the information is to be periodically sent to. This number is used to identify the data in the Display Response messages. Display Abort 8
(021H) This message is sent to the drive from the Remote node to halt updates of the indicated display from the drive. After this message is sent, nothing will be sent to that channel until another Display Node Request message is sent. [ MSG TYPE = 021H RDU # ] 0 1 channel is to stop receiving information. Display Message ASCII Response (022H) Ths drive sends this message only once, after receiving the Display Node Request, to provide the ASCII string used as a legend for the display and the initial numeric display value. When the Remote node receives this message, it knows that the data is to be displayed only, and will not allow any modification of the value. Subsequently, the drive will send only the numeric value to the Remote node, with the use of the Display Value Response message, when the data changes and at regular 4 second intervals. [ MSG TYPE = 022H RDU # BOTTOM LINE ASCII -17 TEXT TOP LINE ASCII TEXT VALUE ] 18-33 34-37 channel is to receive this information. The BOTTOM LINE ASCII TEXT is the legend for the data; the first character of the string is at offset 2. The TOP LINE ASCII TEXT contains the drive name and the units for the data; the first character of the string is at offset 18. The VALUE contains the initial value of the data in the IEEE single precision floating point format; the msb is at offset 34. Display Variable ASCII Response (023H) This mesage is sent only once, after the Display Node Request, to provide the ASCII string used as a legend for the display and the initial numeric value. When the Remote node receives this message, it knows that the data may be modified, and will allow modification of the value. Subsequently, the drive will send only the numeric value to the Remote node, with use of the Dispaly Value Response message, when the data changes and at regular 4 second intervals. { MSG TYPE = 023H RDU # BOTTOM LINE ASCII -17 TEXT TOP LINE ASCII TEXT UPPER LIMIT 18-33 34-37 LOWER LIMIT VALUE ] 38-41 42-45 channel is to receive this information. The BOTTOM LINE ASCII TEXT is the legend for the data; the first character of the string is at offset 2. The TOP LINE ASCII TEXT contains the drive name and the units for the data; the first character of the string is at offset 18. If the value is modified, then limit checking must be performed by the Remote node. The modified value must be within the range of the UPPER LIMIT and the LOWER LIMIT. The modified value may equal the limits, but may not exceed them. The UPPER LIMIT value is in IEEE single precision floating point format; the msb is at offset 34. The LOWER LIMIT value is in IEEE precision floating point format; the msb is at offset 38. The VALUE contains the initial value of the data in IEEE single precision floating point format; the msb is at offset 42. 9
Display Value Response (024H) This message is sent from the drive to the Remote node and channel when the data changes and at regular 4 second intervals until the display is aborted. If the Remote node does not receive an update within 5 seconds, appropriate action should be taken, because the last received data may not be valid. [ MSG TYPE = 024H RDU # VALUE ] -5 channel is to receive this information. The VALUE contains the most recent value of the data in IEEE single precision floating point format; the msb is at offset 2. RDU Lockout Command (025H) An RDU in an "unlocked" state may have its display modified by a keypad connected to any other RDU connected to the same Remote node. An RDU in a "locked" state may not have its display modified by a keypad connected to any other RDU connected to the same Remote node. At power-up, the default state of all RDUs is "unlocked". This message is sent by a drive to the Remote node to set the default state of a particular RDU to "locked". [ MSG TYPE = 025H RDU # ] 0 1 The RDU # is the specific Remote node channel that the data is intended for. RDU Value Change (026H) This message is sent from a Remote node to a drive when an RDU wants to change the value of a numeric parameter on the drive. This message will only be sent after the RDU's ENTER key is pressed. [ MSG TYPE = 026H CHANNEL # SUBCHANNEL # -3 RDU # VALUE ] 4 5-8 The CHANNEL # must be 065H. The SUBCHANNEL # must be the desired Control Display Unit (CDU) Function Number defined in the PAC diagram. The msb of the SUBCHANNEL # is at offset 2. channel the information is coming from. The VALUE contains the desired new value of the parameter and is in IEEE single precision floating point format; the msb is at offset 5. RDU Configuration (027H) This message is sent by the drive to the Remote node at power-up to initialize the default message menu items. The default menu items (and these messages) are determined through the PAC source program. The drive will send one of these messages for each menu item to be initialized. [ MSG TYPE = 027H RDU # MENU ITEM # CHANNEL # SUBCHANNEL # DCP ] 3 4-5 6 channel the information is intended for. The MENU ITEM # is a vlaue between 1 and the maximum menu size, which points to the proper parameter within the RDU. The CHANNEL # must be 065H. The SUBCHANNEL # must be the desired Control Display Unit (CDU) Function 10
Number defined in the PAC diagram. The msb of the SUBCHANNEL # is at offset 4. The DCP is the decimal point location to be used to display the numeric value. The DCP value is equal to the number of digits to the right of the decimal point. RDU Select Menu Item (028H) This message is sent from a drive to the Remote node in order to select a menu item for a particular RDU. This type of message makes it possible to change menu items without forcing the user to press any keys at the Remote node. When the Remote node receives this message, it will send a Display Abort message to the drive corresponding to the currently selected menu item. It will then send a Display Node Request message to the drive corresonding to the newly selected menu item. [ MSG TYPE = 028H RDU # MENU ITEM # ] channel the information is intended for. The MENU ITEM # is a value between 1 and the maximum menu size, which points to the desired parameter within the RDU. Display Logic Message ASCII Responsse (029H) The drive sends this message to the Remote node only once, after receiving the Display Node Request, to provide the ASCII string used as a legend for the display and the initial logic display value. When the Remote node receives this message, it knows that the data is to be displayed only, and will not allow any modification of the value. Subsequently, the drive will send only the logic value to the Remote node, with use of the Display Logic Value Response message, when the data changes and at regular 4 second intervals. [ MSG TYPE = 029H RDU # BOTTOM LINE ASCII -17 TEXT TOP LINE ASCII TEXT VALUE ] 18-33 34 channel is to receive this information. The BOTTOM LINE ASCII TEXT is the legend for the data; the first character of the string is at offset 2. The TOP LINE ASCII TEXT contains the drive name and the units for the data; the first character of the string is at offset 18. The VALUE contains the initial value of the data; a logic 0 is represented by VALUE equal to 0, and a logic 1 is represented by VALUE equal to 0FFH. Display Logic Variable ASCII Response (02AH) The drive sends this message to the Remote node only once, after receiving the Display Node Request, to provide the ASCII string used as a legend for the display and the initial logic display value. When the Remote node receives this message, it knows that the data may be modified, and will allow modification of the value. Subsequently, the drive will send only the logic value to the Remote node, with the use of the Display Logic Value Response message, when the data changes and at regular 4 second intervals. [ MSG TYPE = 02AH RDU # BOTTOM LINE ASCII -17 TEXT TOP LINE ASCII TEXT VALUE ] 18-33 34 11
channel is to receive this information. The BOTTOM LINE ASCII TEXT is the legend for the data; the first character of the string is at offset 2. The TOP LINE ASCII TEXT contains the drive name and the units for the data; the first character of the string is at offset 18. The VALUE contains the initial value of the data; a logic 0 is represented by VALUE eual to 0, and a logic 1 is represented by VALUE equal to 0FFH. Display Logic Value Response (02BH) This message is sent from the drive to the Remote node and channel when the data changes and at regular 4 second intervals until the display is aborted. If the Remote node does not receive an update within 5 seconds, appropriate action should be taken, because the last received data may not be valid. [ MSG TYPE = 02BH RDU # VALUE ] channel is to receive this information. The VALUE contains the most recent value of the data; a logic 0 is represented by VALUE equal to 0, and a logic 1 is represented by VALUE equal to 0FFH. RDU Logic Value Change (02CH) This message is sent from a Remote node to a drive when an RDU wants to change the value of a logic parameter on the drive. This message will only be sent after the RDU's ENTER key is pressed. [ MSG TYPE = 02CH CHANNEL # SUBCHANNEL # -3 RDU # VALUE ] 4 5 The CHANNEL # must be 065H. The SUBCHANNEL # must be the desired Control Display Unit (CDU) Function Number defined in the PAC diagram. The msb of the SUBCHANNEL # is at offset 2. channel the information is coming from. The VALUE contains the desired new value of the parameter; a logic 0 is represented by VALUE equal to 0, and a logic 1 is represented by VALUE equal to 0FFH. Numeric Update (030H) This message is sent from a drive to a Remote node to keep the drive's numeric output updated, after the drive sends a Remote Numeric Output Allocation Request message. As long as the drive is powered up, it will continue to send this message at regular intervals and when the data changes. If the Remote node does not see a Numeric Update message within the prescribed time given in the Output Allocation message, then it should take appropriate safe action (i.e. set the output to 0). This message is also sent from a Remote node to the drive to keep the drive's numeric input updated, in response to a Remote Numeric Input Configure message. If the numeric value of the input changes, then a LAN message must be sent. A LAN message must also be sent at regular 4 second intervals fixed at the Remote node; the drive expects periodic updates in response to the Input Configure message, and will take appropriate action if it is not updated within 5 seconds. [ MSG TYPE = 030H CHANNEL # SUBCHANNEL # VALUE ] 3-6 The CHANNEL # is a byte representing the selected channel of the Remote node. 12
The SUBCHANNEL # is a byte representing the selected subchannel of the Remote node. The VALUE contains the most recent value of the data in IEEE single precision floating point format; the msb is at offset 3. Logic Update (031H) This message is sent from a drive to a Remote node to keep the drive's logic output(s) updated, after the drive sends a Remote Logic Output Allocation Request message. As long as the drive is powered up, it will continue to send this message at regular intervals and when the data changes. If the Remote node does not see a Logic Update message within the prescribed time given in the Output Allocation message, then it should take appropraite safe action (i.e. set the output to 0). This message is also sent from a Remote node to the drive to keep the drive's logic input updated, in response to a Remote Logic Input Configure message. If the logic state of the input(s) changes, then a LAN message must be sent. A LAN message must also be sent at regular 4 second intervals fixed at the Remote node; the drive expects periodic updates in response to the Input Configure message, and will take appropriate action if it is not updated within 5 seconds. [ MSG TYPE = 031H CHANNEL # VALUE ] -5 The CHANNEL # is a byte representing the selected channel of the Remote node. The VALUE contains the logic states for each of 32 subchannels. The logic state of Subchannel 0 is the state of the least significant bit (D0) of the lsb of VALUE (at offset 5). The logic state of Subchannel 31 is the state of the most significant digit (D7) of the msb of VALUE (at offset 2). NOTE The Remote node should use the LOGIC MASK, sent in the Output Allocation or the Input Configure message, to determine which logic bits in VALUE are of interest. Remote No Update Error (0DBH) This message is sent from a Remote node to the drive when it does not receive an output update LAN message from a drive, that has allocated one or more outputs, within the prescribed time. [ MSG TYPE = 0DBH DRIVE # OUTPUT TIME ] The DRIVE # contains the number of the drive that has not sent the output update within the prescribed time. The OUTPUT TIME is the prescribed time sent to the Remote node upon the allocation of an output. The format of OUTPUT TIME is in number of whole seconds (a value of 0 means to never time out). Numeric Input Request Error (0DCH) This message is sent from the Remote node to the drive when the Remote node cannot provide a numeric input to a drive for reasons other than LAN failure. A typical reason for this condition might be that there is no numeric input for the requested channel/subchannel. [ MSG TYPE = 0DCH CHANNEL # SUBCHANNEL # ] The CHANNEL # is the channel of the Remote node on which the drive had attempted to configure a numeric input. 13
The SUBCHANNEL # is the channel of the Remote node on which the drive had attempted to configure a numeric input. Logic Input Request Error (0DDH) This message is sent from the Remote node to the drive when the Remote node cannot provide a logical input for reasons other than LAN failure. A typical reason for this condition might be that there is no logic input channel located at the given channel/subchannel. [ MSG TYPE = 0DDH CHANNEL # LOGIC MASK ] -5 The CHANNEL # is the channel of the Remote node on which the drive had attempted to configure a logic input. The LOGIC MASK contains the error states for each of 32 subchannels. The error state of Subchannel 0 is the state of the least significant bit (D0) of the lsb of LOGIC MASK (at offset 5). The error state of Subchannel 31 is the state of the most significant bit (D7) of the msb of LOGIC MASK (at offset 2). Bits set to logic state 1 in the LOGIC MASK are in error. Numeric Output Allocation Error (0DEH) This message is sent from the Remote node to the drive when the Remote node cannot allocate a numeric output to a drive for reasons other than LAN failure. A typical reason for this condition might be that a different drive has already allocated the output. Another reason for this condition might be that there is no numeric output at the requested channel/subchannel. [ MSG TYPE = 0DEH CHANNEL # SUBCHANNEL # DRIVE # W/ALLOCATION ] 3 The CHANNEL # is the channel on the Remote node on which the drive attempted to allocate a numeric output. The SUBCHANNEL # refers to the subchannel on the Remote node on which the drive had attempted to allocate a numeric output. The DRIVE # W/ALLOCATION is the drive number that has previously allocated an output within this particular numeric output channel/subchanle. If the Remote node detects that there is no numeric output at the requested channel/ subcnhannel, the DRIVE # W/ALLOCATION will be 000H. Logic Output Allocation Error (0DFH) This message is sent from the Remote node to the drive when the Remote node cannot allocate a logic output to a drive for reasons other than LAN failure. A typical reason for this condition might be that a different drive already has the output allocated. Another reason for this condition might be that there is no logic output at the requested channel/subchannel. [ MSG TYPE = 0DFH CHANNEL # DRIVE # W/ ALLOCATION LOGIC MASK ] 3-6 The CHANNEL # is the logic channel of the Remote node on which the drive had attempted to allocate a logic output. The DRIVE # W/ALLOCATION is the drive number that has previously allocated an output within this particular logic output channel/subchannel. If the Remote node detects that there is no logic output at the requested channel/subchannel, the DRIVE # W/ALLOCATION will be 000H. 14
The LOGIC MASK contains the error states for each of 32 subchannels. The error state of Subchannel 0 is the state of the least significant bit (D0) of the lsb of LOGIC MASK (at offset 6). The error state of Subchannel 31 is the state of the most significant bit (D7) of the msb of LOGIC MASK (at offset 3). Bits set to logic 1 in the LOGIC MASK are in error. IEEE Single Precision Floating Point Format. Numeric values passed in the messages are in the number format set by the IEEE 754 single precision floating point standard. Its bit form representation is as follows: SEEE EEEE Most Significant Byte (MSB) EMMM MMMM MMMM MMMM MMMM MMMM Least Significant Byte (LSB) "S" is the sign bit (1 if negative, 0 if positive). The "E" field is the two's exponent. It is a two's complement value biased by 127 (decimal). The "M" field is the 23 bit normalized mantissa. The most significant bit is always assumed to be 1, and so is not explicitly stored. This yields an effective precision of 24 bits. The value of the floating point number described above is obtained by multiplying 2 raised to the power of the unbiased exponent, by the mantissa. The assumed bit of the binary mantissa (the most significant bit) has a value of 1.0, with the remaining bits providing a fractional value (i.e. the value of the mantissa is greater than or equal to 1.0 and less than 2.0). The dynamic range of the IEEE 754 single precision floating point format is +/-1.75494E-38 to 3.402823E+38. 15
Examples of RSC Messages. EXAMPLE 1. Drive allocates a numeric output and then keeps the output updated. EX1.1. Drive #4 powers up and sends a Remote Numeric Output Allocation Request. The data sent over the serial port from the RSC to the external device is as follows (in the given order): 001H 0FEH 007H 004H 011H Start of message sequence (SOH, NOT SOH) 001H 0FEH Length, 7 bytes 007H Drive #4 004H Message Type 011H, Remote Numeric Output Allocation Request 011H 002H 00CH 005H 000H 02FH Channel #2 002H Subchannel #12 00CH Output time of 5 seconds 005H Fault reaction to leave allocated 000H Checksum 02FH EX1.2. Drive continues to keep the output updated by sending Numeric Update messages when the data changes and at 4 second intervals. The data sent over the serial port from the RSC to the external device is as follows (in the given order): 001H 0FEH 009H 004H 030H Start of message sequence (SOH, NOT SOH) 001H 0FEH Length, 9 bytes 009H Drive #4 004H Message Type 030H,Numeric Update 030H 16
002H 00CH 03FH 080H 000H 000H 00AH Channel #2 002H Subchannel #12 00CH Value, floating pt value of 1.0 03F800000H Checksum 00AH EXAMPLE 2. External device requests that a new modifiable parameter be displayed, and then modifies the value. EX2.1. External device sends a Display Abort message to drive #20. The data sent over the serial port from the external device to the RSC is as follows (in the given order): 001H 0FEH 004H 014H 021H Start of message sequence (SOH, NOT SOH) 001H 0FEH Length, 4 bytes 004H Drive #20 014H Message Type 021H, Display Abort 021H 00AH 043H RDU #10 00AH Checksum 043H EX2.2. External device sends a Display Node Request to drive #1. The data sent over the serial port from the external device to the RSC is as follows (in the given order): 001H 0FEH 007H 001H 020H Start of message sequence (SOH, NOT SOH) 001H 0FEH Length, 7 bytes 007H Drive #1 001H Message Type 020H, Display Node Request 020H 065H 000H 06EH 00AH 005H Channel #101 065H Subchannel #110 0006EH RDU #10 00AH Checksum 005H 17
EX2.3. Drive #1 responds with Display Variable ASCII Response message. The data sent over the serial port from the RSC to the external device is as follows (in the given order): 001H 0FEH 030H 001H 023H Start of message sequence (SOH, NOT SOH) 001H 0FEH Length, 48 bytes 030H Drive #1 001H Message Type 023H, Display Variable ASCII Response 023H 00AH RDU #10 00AH 020H 020H 020H 04CH 049H 04EH 045H 020H 053H 050H 045H 045H 044H 020H 020H 020H Bottom Line ASCII Text LINE SPEED 043H 04FH 041H 054H 045H 052H 020H 020H 020H 020H 020H 020H 020H 046H 050H 04DH Top Line ASCII Text COATER FPM 044H 07AH 000H 000H Upper Limit, floating pt value of 1000 0447A0000H 000H 000H 000H 000H Lower Limit, floating pt value of 0 000000000H 000H 000H 000H 000H Initial Value, floating pt value of 0 000000000H 016H Checksum 016H 18
EX2.4. Drive #1 continues to keep the display updated by sending Display Value Response messages when the data changes and at 4 second intervals. The data sent over the serial port from the RSC to the external device is as follows (in the given order): 001H 0FEH 008H 001H 024H Start of message sequence (SOH, NOT SOH) 001H 0FEH Length, 8 bytes 008H Drive #1 001H Message Type 024H, Display Value Response 024H 00AH RDU #10 00AH 000H 000H 000H 000H Value, floating pt value of 0 000000000H 037H Checksum 037H EX2.5. External device desires to change the value of the numeric parameter on the drive, so it sends an RDU Value Change message to the drive. The data sent over the serial port from the external device to the RSC is as follows (in the given order): 001H 0FEH 00BH 001H 026H Start of message sequence (SOH, NOT SOH) 001H 0FEH Length, 11 bytes 00BH Drive #1 001H Message Type 026H, RDU Value Change 026H 065H 000H 06EH 00AH Channel #101 065H Subchannel #110 0006EH RDU #10 00AH 042H 0C8H 000H 000H Value, floating pt value of 100 042C80000H 019H Checksum 019H 19
EX2.6. Drive #1 continues to keep the display updated with the new value by sending Display Value Response messages when the data changes and at 4 second intervals. The data sent over the serial port from the RSC to the external device is as follows (in the given order): 001H 0FEH 008H 001H 024H Start of message sequence (SOH, NOT SOH) 001H 0FEH Length, 8 bytes 008H Drive #1 001H Message Type 024H, Display Value Response 024H 00AH RDU #10 00AH 042H 0C8H 000H 000H Value, floating pt value of 100 042C80000H 041H Checksum 041H EXAMPLE 3. Drive configures 3 logic inputs on external device and external device keeps drive updated. EX3.1. Drive #15 powers up and sends a Remote Logic Input Configure message. The data sent over the serial port from the RSC to the external device is as follows (in the given order): 001H 0FEH 00CH 00FH 012H Start of message sequence (SOH, NOT SOH) 001H 0FEH Length, 12 bytes 00CH Drive #15 00FH Message Type 012H, Remote Logic Input Configure 012H Channel #4 004H 004H 20
020H 000H 008H 001H Logic Mask, configuring subchannels 0, 11, and 29 020000801H 000H 000H 000H 000H Sink/Source Mask, all sink 000000000H 05AH Checksum 05AH EX3.2. External device keeps drive #15 updated by sending Logic Update messages when any of the configured logic inputs change state and at approximately 4 second intervals. The data sent over the serial port from the external device to the RSC is as follows (in the given order): 001H 0FEH 008H 00FH 031H Start of message sequence (SOH, NOT SOH) 001H 0FEH Length, 8 bytes 008H Drive #15 00FH Message Type 031H, Logic Update --- 031H 004H Channel #4 004H 000H 000H 008H 000H Value, subchannel 0 and 29 at logic 0 and subchannel 11 at logic 1 ------- 000000800H 054H Checksum 054H 21