MOBY I ASM 420 Interface Module. Technical Description Release 07/99

Transcription

1 s MOBY I ASM 420 Interface Module Technical Description Release 07/99

2

3 ASM 420 Technical Description 6GT AF00--0DA2 Contents 1 General Features 2 2 ASM 420 Hardware Technical Data Pin Assignment Assignment of Basic Connector X ASM 420 Connector System Setting the Mode of Operation Hardware Configuration System Configuration Power Supply TTY Cabling RS 422 Cabling V.24 Cabling STG Cabling SINEC L1 Cabling SINUMERIK Cabling DI/DO Cabling 20 3 Programming the ASM 420 Module Software and Driver Telegram Layout Standard Telegrams System Commands Process All MDS Types (Normal Operation) ECC Special Driver Active (All MDS Types) SINUMERIK Telegrams Protocols R Protocol Lauf Protocol SINEC L Telegram Examples 39 4 ColdStartandRestart 42 5 DI/DOs and Proximity Detection Proximity Detection with 2 DIs Field Scanning as Proximity Detection Proximity Detection with Field Scanning and 1 DI 49 6 SLG and MDS Configuration and Installation Guidelines 50 7 Error Diagnosis and Error Messages 51 8 Warnings 59 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

4 6GT AF00--0DA2 ASM 420 Technical Description 1 General Features TheASM420interfacemoduleisageneral-puposemodulewithaserialinterfacethatallowsMOBY-I components to be used with any computer or PC.. An SLG 41, SLG 42, SLG 43 and SLG 44 read/write device can be operated on an ASM The module is a single-height Eurocard and can be inserted in any standard rack.. The ASM 420 can be addressed using the following protocols R --- Lauf --- SINEC L1. A special telegram format for SINUMERIK is provided by the 3964R protocol. Up to four ASM 420 modules can be operated on a single SINUMERIK serial interface.. Up to 16 ASM 420 modules, each with a digital input and output, can be operated on a serial interface (with RS 422 and TTY user interfaces only).. ThreeversionsoftheASM420moduleareavailable: ASM 420 / RS > 6GT CB00 ASM 420 / V > 6GT CA00 ASM 420 / TTY ---> 6GT CC00. Three LEDs allow the operational status of the ASM 420 to be monitored.. The module can be switched to dialog mode via expanded parameterization with the RESET command.. Starting with version release 7, the ASM 420 can be operated with an SLG 65 of MOBY-V. Parameterization is performed with the RESET command. Cf. chapter Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

5 ASM 420 Technical Description 6GT AF00--0DA2 2 ASM 420 Hardware Basic connector (X1) Fuse (T 315 ma) ANW aktiv Error EPROM Switch bank (S1) for setting mode of operation CPU 3LEDs: Red LED: indicates a fault (see chap. 7) Yellow LED: indicates that the SLG device is active Green LED: indicates that an MDS is present MOBY 9-way subminiature D connector (screw locking) (X2) for connecting the SLG read/write device (The SLG can also be connected via the basic connector if desired). Pin Assignment on ASM Pin Assignment on SLG Pin Function Pin Function Housing Free +transmit + receive Free --- receive --- transmit Ground (0 V) +24Volt Free Cable shield Receive +Send --- Send --- Receive Ground (0 V) +24Volt Cable shield 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

6 6GT AF00--0DA2 ASM 420 Technical Description 2.1 Technical Data Environmental conditions: --- Operating temperature: 0 C to+55 C --- Storage temperature: C to+70 C Protection rating in acc.w. IEC 529: IP 00 Serial interface (to computer/pc): --- Transmission rate: 2400 to 9600 Baud (38.4 kbaud) --- Protocol: 3964R SINEC L1 Lauf SINUMERIK protocol --- Cable lengths: TTY 1000 m (shielded) RS m (shielded) V m (shielded) Serial interface (to SLG): --- Transmission rate (gross): Baud --- Protocol: Asynchronous; 8 data bits; even parity MOBY-I: MDS protocol --- Cable lengths: SLG dependent; max. of 1000 m (see cable configurations in MOBY catalogue) Power supply: 20 to 30 V DC Current consumption: --- Max. off-load current: 200 ma (no SLG; DOs off-load) --- Max. current consumption of the SLG: 300 ma Dimensions: --- L x W x H 160 x 100 x 20 (mm) Weight: 0.2 kg DI/DO; Select; Request; Error; ANW: --- Digital inputs: 3 Non-floating Logical 0 : 0 V to 8 V Logical 1 : 15 V to 24 V (Ri = 10 kohm) Delay: < 10 msec --- Digital outputs: 5 non-floating (internal power supply) Short-circuit proof I max = 200 ma (per DO; or for 2 DO s) --- Max. cable lengths: 100 m Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

7 ASM 420 Technical Description 6GT AF00--0DA2 2.2 Pin Assignment Assignment of Basic Connector X1 b2 b4 b6 b8 b10 b12 b14 b16 b18 b20 b22 b24 b26 b28 b30 b32 Z2 Z4 Z6 Z8 Z10 Z12 Z14 Z16 Z18 Z20 Z22 Z24 Z26 Z28 Z30 X32 Power supply Serial interface to user Optional control and signal line Optional SLG connection Protective ground (shield) b2 0V z2 24 V Interface (type dependent) Interface (type dependent) V.24 RS 422 TTY V.24 RS 422 TTY b4 b6 b RxD R+ D+ D --- +EM +SE * z4 z6 z8 TxD --- GND E+ R --- E EM --- SE b10 z10 b12 b14 DI0 DO0 2 digital inputs and outputs each for controlling data carrier z12 z14 DI1 DO1 2 digital inputs and outputs each for controlling data carrier b16 ASM has user data or acknowledgement (Request) z16 Select module (Select) b18 b20 Error code (same as red LED) SLG receive + z18 z20 Presence (ANW) 2) (same as green LED) SLG receive --- b22 SLG transmit + z22 SLG transmit --- b24 z24 b26 z26 b28 b30 Protective ground ( ) z28 z30 Protective ground ( ) b32 0V z32 R+ (Terminating resistor) TxD (Transmit data) E+ (Receive) RxD (Receive data) D+ (Transmit) +EM (Receive) R --- (Terminating resistor) --- EM (Receive) D --- (Transmit) +SE (Transmit) E --- (Receive) --- SE (Transmit) * Pin b8 must not be connected in TTY mode. 2) The presence of an MDS is indicated on this pin with 0 V level. 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

8 6GT AF00--0DA2 ASM 420 Technical Description ASM 420 Connector System Connector: The connector used with the ASM 420 is a 48-way male connector conforming to DIN 41612, design F, whose soldering pins are bent at 90. Only rows z and b are assigned and soldered permanently to the ASM 420. Socket: Female connectors conforming to DIN 41612, design F must be used as mating components for the ASM 420 connector. All 48-way, -type female connectors conforming to DIN 41612, design F are suitable. Various types of female connectors are available. Examples: --- With soldered connection --- With a screw connection --- As wire wrap model Example:SFL0,5/F32/2B: zbd Female connector with screw connection 0.5 mm 2 ;rowszandb assigned. Design: rows of connectors --- Number of contacts: 32 (2 rows, each with 16 contacts) --- Contact principle: insulation displacement connector with double-sided contact spring --- Snap-in hooks and elements to ensure secure contact between male and female connectors Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

9 ASM 420 Technical Description 6GT AF00--0DA2 2.3 Setting the Mode of Operation Switch bank S1: ON ON =^ 1 OFF =^ 0 Setting the procedure to the user Control of MDS Control of MDS: The operating modes shown below simplify operation and monitoring of the data carrier by the user (see chapter 5 for more detailed information). Switch 7 8 Function 0 0 No control of data carrier Proximity detection is disabled TheDIs/DOscanbeprogrammedasrequiredusingthesystemcommand. When operating mode D0 or 90 is used (see page 24), switches 7 and 8 must be placed in this position. The NEXT command may not be used. 0 1 Proximity detection via ASM firmware DIs can be used as required and interrogated by the DI/DO command. 1 0 Proximity detection using DI0 and DI1, whereby DI0 = 1 MDS enters DI1 = 1 MDS leaves 1 1 Proximity detection using DI1, whereby DI1 = 1 MDS leaves DI0 is not used and can be interrogated by the status command.* * The RESET command can be used to set a time factor for field scanning when MDS 507 is used. Cf. chapter This setting is not available when SINUMERIK is used. 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

10 6GT AF00--0DA2 ASM 420 Technical Description Setting the protocol Switch b b b b b b a a 1 0 Function 3964R: ASM = Slave 3964R: ASM = Master Standard 3964R protocol for all interfaces The system processes standard telegrams from the ASM. b b = baud rate (see below) SINUMERIK 850/880 protocol (no response telegram) Connection of ASM to SINUMERIK 3964R protocol (cf. chapter 3.3.1); ASM = Slave Interfaces: RS 422 or TTY; Maximum of 4 ASMs on one interface If only one ASM is being used with SINUMERIK, an ASM with a V.24 interface may also be connected. Switch: 3 4 ASM address (=a a) bb=baudrate(seebelow) (always present) Caution: When SINUMERIK is used, some type of presence detectionmustbeswitchedonwithswitches7and8. b b b b b b b b These switch settings are not used at this time. (The ASM does not function with these switch positions.) Baud rate (= bb) (Applies to Lauf, 3964R and SINUMERIK protocols) 1 1 x x x x Baud (not approved for TTY interface) 0 0 x x x x 9600 Baud 0 1 x x x x 4800 Baud 1 0 x x x x 2400 Baud Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

11 ASM 420 Technical Description 6GT AF00--0DA2 Switch a a a a 1 1 Function SINEC L1 aaa = address of ASM on SINEC L1 bus (ASM is always a slave.) Theaddressissetasfollows: Switch: SINEC address SINEC addresses 17 to 31 cannot be set on the ASM and are therefore not available. The system processes standard telegrams from the ASM; RS 422 and TTY only. b b Lauf protocol The system processes standard telegrams from the ASM; all interfaces can be used. bb=baudrate STG interface 3964R protocol; ASM = slave Baud rate = 4800 Baud The telegram format, which is used internally by MOBY, is irrelevant as far as the user is concerned. ASM 420 user interface: RS 422 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

12 6GT AF00--0DA2 ASM 420 Technical Description 2.4 Hardware Configuration System Configuration The SLG read/write device can be connecterd to either the X1 basic connector or the 9-way subminiature D connector X2. Computer/PC Serial interface* Select Request DO DI SIEMENS SLG read/write device Please note: The Select and Request lines may be omitted if only one ASM 420 is being driven from a serial interface. The external wiring of unnecessary signals can also be omitted. * Daisy-chain mode is only possible with the RS 422 and TTY interfaces. SIEMENS SLG read/write device Max. length of the select and request line: 100 m (cf. chap ) One select line for each ASM 420 One request line for each ASM 420 PLC, PC or computer Serial interface 4 or 8 ASM 420 can be connected in standard MOBY housings. Max. of 16 ASM 420 in daisy-chain mode Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

13 ASM 420 Technical Description 6GT AF00--0DA2 ASM 420 interface modules can operate in daisy-chain mode when used with RS 422 or TTY user interfaces. This allows up to 16 interface modules to be driven from one serial interface. To achieve this, the ASM 420 must use either the 3964R or Lauf protocols (not SINUMERIK). The computer/pc must have one digital input (DI) and one digital output (DO) for each ASM 420. Mode of operation: Programming the ASM: The computer/pc selects the required module using Select and then transmits the job telegram to the module. Command processing: The ASM then processes the command, the length of time for which varies from command to command. Command processing can take any length of time (if no MDS is in the window). Transmission of result to user: The ASM indicates that it has a telegram to send by setting the Request bit. This is picked up by the computer/pc, which selects the module using Select. The selected ASM then sends the response telegram. Select Request ** * Select scan by ASM Data Job telegram to ASM Response telegram from ASM t t t t 4 t 5 t 2 Select Request Data Select timing when the result of a command is available immediately after the job telegram Response telegram from ASM t 2 t 6 t 1 > 30 msec : Delay between Select and start of data transmission (debouncing time of the Select signal) t 2 > 0 : Delay between end of data transmission and deselection of the ASM 420 t 3 = command dependent : Execution of user command by ASM 420 t 4 > 0 : Time from Request active and selection of the ASM 420 t 5 = 10 to 30 msec : Time between selection of the module and transmission of the response telegram t 6 < 30 msec : Deselect time: The ASM can still send a response telegram to the user during this time (debouncing time of the Select signal during deselection) Important: * When the response telegram is involved, the ASM only scans Select at the beginning of a transmission. If Select is deactivated during the telegram transmission, the ASM always sends the complete telegram to the computer. This ensures that no garbled telegrams are sent by the ASM. ** Select must be activated for the entire duration of a job telegram. 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

14 6GT AF00--0DA2 ASM 420 Technical Description Power Supply The cable between the ASM 420 and the SLG read/write device consists of 6 cores plus shield. 4 of these cores are assigned to the serial data interface and 2 to the power supply for the SLG read/write device. The maximum length of the data cables can, depending on the physical interface, be up to 1000 m. The maximum permitted cable length is usually shorter if the 24 V supply for the SLG read/write device is used by the ASM 420. The maximum cable length also depends on the voltage drop. The following table gives an overview of permitted cable lengths. Conductor cross section in mm 2 Conductor diameter in mm Resistance Ω/km *) SLG 40 / SLG 41 (I=90 ma) SLG 42 (I=180 ma) Max. cable length for Max. cable length for U V =24V U V =30VU V =24V U V =30V SLG 43 (I=250 ma) Max. cable length for U V =24V U V =30V SLG 44 (I=80 ma) Max. cable length for U V =24V U V =30V *) The values for resistance are average values and refer to the feed and return conductors. A single conductor has half the quoted resistance. If cable lengths longer than those in the table are required, the 24 V supply for the SLG read/write device must not be used by the ASM 420. Instead, a 24 V supply must be fed directly to the SLG. Highlighted field: The standard shielded LiYCY 6 x 0.5 cable recommended by SIEMENS. This cable is available from SIEMENS under the order number 6GT A... 1). 24 V supply to ASM 420: The maximum length of the power supply cable for the ASM 420 is restricted to 20 m. If a longer cable is used, or several ASMs are supplied from a single cable, the voltage drop on the supply cable to the ASM 420 and SLG read/write device must be considered individually. If necessary, the cross section of the supply cable must be increased. Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

15 ASM 420 Technical Description 6GT AF00--0DA TTY Cabling SLG ASM 420 (passive) Computer (active) X X1 b30/ z30 TxD RxD z6 b6 z4 b4 --- SE +SE --- EM +EM + + RxD TxD Max. length 1000 m The ASM module does not contain power sources for the active part of the TTY interface. Should, however, it become necessary for the ASM to power the interface, the active part of the ASM should be wired as follows. SLG ASM 420 (active) Computer (passive) X X1 z2 R R TxD RxD b30/ z30 z6 b6 z4 b4 b32 R R RxD TxD Max. length 1000 m The resistors R should each have a value of 470 Ohms if a current loop of 20 to 30 ma is present (P = 0.5 W). 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

16 6GT AF00--0DA2 ASM 420 Technical Description RS 422 Cabling SLG ASM 420 Computer X TxD RxD X1 b30/ z30 z8 z6 b8 b6 z4 b4 *) *) E --- D --- D+ E+ ** ** +5V Max. length 1000 m *) The cable can be terminated on the receiver side by setting jumpers z4 - b4 and z8 - z6. This will increase the system s immunity to interference. When daisy chain mode is used (cf. chap ), the jumpers may only be wired on the last ASM 420. **) The terminal resistors shown in the drawing must be present on the computer side (R = 220 to 1000 Ohm). If lines are short, these resistors can be wired on the ASM side. Jumpers z6 - z8 and b4 - z4 are then omitted. 2 jumpers are added: b4-b6andz6-b V.24 Cabling Example of standard cabling SLG ASM 420 Computer X RxD X1 b30/ z30 b32 RxD TxD b6 z4 TxD Max. length 30 m V.24 control lines (e.g., DSR, DTR, RTS and CTS) are not supported by the ASM. The acknowledgment of data is handled at the protocol level. Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

17 ASM 420 Technical Description 6GT AF00--0DA STG Cabling SLG ASM 420 STG 4 X TxD RxD 24 V 0V X1 z2 b30/ z30 z8 z6 b8 b4 b6 z4 b32 E --- D --- D+ E Max. length fo test cable 100 m The SLG can be operated directly with the STG 4 via a cable, or the complete distance can be tested via the ASM 420, as shown above SINEC L1 Cabling The ASM 420 can only be operated on SINEC L1 via RS 422 or TTY. A maximum of 16 ASM 420 modules can be connected to one SINEC L1 bus. The SINEC L1 address is determined by switches on switch bank S1 of the module. Additional information on configuring and programming the SINEC L1 bus can be found in the SINEC L1 bus system manual, order no. 6ES LA11. Bus topology: ASM 420 / RS 422 on SINEC L1 Control computer C P SINEC L1 master (addr. 0) TTY interface (with power supply for BT 777) SLG SLG SLG ASM 420 addr. 1 ASM 420 addr ASM 420 addr. 16 z4 z8b6b8 z4 z8b6b8 z4 z8b6b8z6b4 BT 777 (Bus terminal) 0B 1B 2B 3B 4B RS 485 *) Max m 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

18 6GT AF00--0DA2 ASM 420 Technical Description Or: Topology for 2 km bus: SLG ASM 420 addr SLG ASM 420 addr. 8 Control computer C SLG P RS 485 ASM 420 addr SLG ASM 420 addr. 16 z6b4 *) 0A 1A 2A 3A 4A BT 777 (Bus terminal) 0B 1B 2B 3B 4B *) Max m Max m *) The driver block on the ASM 420 must be terminated at the end of the SINEC L1 bus: jumpers from pin z6 - b8 and pin b4 - b6. Note: The ASM 420 on the BT 777 is wired differently on the A side of the terminal than on the B side. BT 777 Pin ass. X1 ASM 420 or BT 777 1A b6 1B 2A b8 2B 3A z4 3B 4A z8 4B Pin ass X1 ASM 420 z4 z8 b6 b8 The addresses of the individual ASMs can be distributed as required on the bus. The power supply of the ASM module is not shown in the diagram. Note: No other L1 device may be driven from this bus if an ASM 420 with an RS 422 interface is connected directly to the SINEC L1 bus. If other L1 devices are to be connected to the L1 bus (e.g., programmable controllers), the ASM 420 with a TTY interface must be operated on the BT 777 bus terminal. Caution: During installation, it is essential that layout, wiring, and connection to ground of the cable shield be correct. If not, the bus will be very sensitive to interference. Strong fields of interference (e.g., thunder storms) may destroy the hardware of the ASM 420 and the bus terminal. Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

19 ASM 420 Technical Description 6GT AF00--0DA2 Bus topology: ASM 420 / TTY on SINEC L1 SLG SLG Control computer C P V 24 V 220 V 5V ASM 420 addr Customer s distribution box way submin. D connector, slide lock 220 V 24 V 220 V 5V ASM 420 addr. 2 SIMATIC PLC 100U TTY interface SIMATIC PLC 100U BT 777 bus terminal BT 777 bus terminal BT 777 bus terminal BT 777 bus terminal BT 777 bus terminal A separate distribution box must be provided if the ASM 420 is to be operated via the bus terminal on the SINEC L1 bus. The distribution box performs the following functions: --- Provide 5 V DC to the bus terminal --- Provide 24 V DC to the ASM Adapter between the 15-way bus terminal connector and the 32-way ASM 420 male connector --- Housing for the bus terminal --- Housing for the ASM Optional: distribution of DI/DO of the attached ASM 420 (not shown in the diagram) When an indirect bus setup via the BT 777 bus terminals is used, data can be sent to and received from a ASM 420. In this case, a bus station which sends a command to ASM 420 will receive a response telegram in return. 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

20 6GT AF00--0DA2 ASM 420 Technical Description SINUMERIK Cabling The cabling shown below can also be used to connect any computer with the 3964R protocol. This enables up to 4 ASM 420 to be driven from one physical interface. Take note of the telegram structure described in section Connection diagram SLG SLG SLG SLG ASM 420 No. 1 ASM 420 No. 2 ASM 420 No. 3 ASM 420 No. 4 CP 315 / R protocol via CP315 or CP373 module DPR One hardware signal per ASM 420 indicates that an MDS is in the SLG s transmission window. COM MPR PLC Dig. I/O NC ASM 420 / TTY: Canbedrivendirectly on CP 315 / 373 ASM 420 / RS 422: Can only be driven by CP 315/373 using a V.24! RS 422 adapter ASM 420 / V.24: One ASM 420 only (no. 1)canbedrivendirectly by CP 315/373. The Hardware signal: The hardware signal is on the DO0 output of the ASM 420 (see chapter 5). The presence of an MDS is indicated to the PLC by a falling edge on DO0. Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

21 ASM 420 Technical Description 6GT AF00--0DA2 Control of the 3964R protocol: If more than one ASM 420 (max. of 4) is being operated on a single physical interface, ASM no. 1 is always the master protocol (i.e., ASM no. 1 picks up the DLE following the STX in the case of commands from the CP). ASM no. 1 must always be present. TTY interface SLG SLG SLG CP or computer Dig. inputs +TxD --- TxD +RxD --- RxD ASM 420 no. 1 ASM 420 no ASM 420 no V z z2 b b V 470 b32 z6 z4 b4 b6 z4 * * * z6 ** * b14... Active Passive Passive b4 b6 z4 b4 z6 b6 b14 Passive Max m *) This line must be looped through from the computer to the last ASM. See also section Where possible, the computer should handle the active part of the TTY interface, in which case the resistors shown on ASM no. 1 will not be needed. If this is not possible (as shown in the diagram), the active part of the interface must be simulated in the connector of ASM no. 1 using 4 resistors (R = 470 Ohm). The numbers in the diagram refer to pins in the 48-way female connector. Note: With this cabling, all the wired ASMs must actually be connected. Otherwise an open electric circuit will be created. 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

22 6GT AF00--0DA2 ASM 420 Technical Description RS 422 interface See section SLG SLG SLG ASM no. 1 ASM no ASM no. 4 CP or computer +E --- E z4 z8 z4 z8 Enable Enable Enable... z4 z8 z4 z8 +D --- D b6 b8 b6 b8 b6 b8 b14 b14 b14 b6 b8 Dig. inputs Max m DI/DO Cabling 220 V AC ASM V DC Proximity switch Relay, miniature motor lamps, etc. z2 z14 b14 z12 b12 DO 1 DO 2 DI 1 DI 2 b2 Cable length max. 100 m (shielded or unshielded) I max = 200 ma (per DO or total current) Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

23 ASM 420 Technical Description 6GT AF00--0DA2 3 Programming the ASM 420 Module 3.1 Software and Driver Various drivers for the control computer are available to the user. 3964R protocol: PC users: 3964R driver for MS-DOS users Uses PC interfaces 1 and/or 2 The driver can drive 4 interfaces if additional hardware is included. Runs on IBM-XT, IBM-AT 01, IBM-AT 03, Siemens PC 16-05, Siemens PC 16-20, Siemens PC 32-05, PG 750 and compatibles System SX microcomputer : 3964R protocol available as standard ES 120: SICOMP M: Can be called up directly in BASIC using the commands PUT, REQUEST or RECEIVE. (See ES 120 manual and example in section 3.4.) ASM connected via DU04 module (Set byte 3 of the parameter record to hexadecimal 80 and then transfer the parameter record to the DU04 with the PARAM command.) SINEC L1: Where a CP530 module is being used, COM 530 software is also available for configuring and testing the bus. Standard function blocks handle communication between the user and the CP530 module. The DF301X and DF32L1 modules are available for all AT-compatible PCs. A SINEC L1 package running under either FlexOS, MS-DOS, C-DOS XM or C-DOS 386 can be used to program the module. Lauf: The simplest way of communicating with ASM 420; for all computers that do not support 3964R or SINEC L1 (see section and programming example in section 3.4). SINUMERIK interface: The computer interface is available for telegram control if the SINUMERIK is connected via a CP315 or AS512. The SINUMERIK protocol can also be used with any computer or PC that supports the 3964R protocol. 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

24 6GT AF00--0DA2 ASM 420 Technical Description 3.2 Telegram Layout General: The telegrams shown in this section contain user data only. Additional bytes transmitted for protocol control are described in section Standard Telegrams The standard telegrams shown below are identical for all types of MDS and are provided for the. 3964R. SINEC L1. Lauf protocols. General telegram layout: Byte: n AB Command Stat. Command specific data The command related data are described in more detail in the following pages. The minimum length is 00 and the maximum data length 253 bytes. The status byte always has the value 00 when the command is output. Thebytewillhavethefollowingvalueinaresponseorerrortelegram. Bit: Batt.1 Batt.2 ECC E r r o r c o d e (00 to 1F) (Detailed error description: see chap. 7) 00 No error (default) ANW error: ANW error: MDS not in field when command active MDS passed SLG without command ErrorinconnectiontoSLG MDS memory error (not initialised) Unknown command from ASM Field interference on SLG Too many transmission errors A INIT: CRC error INIT: MDS cannot be initialized. 0B INIT: Timeout during initialization 0C INIT: Write error during initialization 0D Address error 0E 0F 10 ECC mode: Data in MDS incorrect Reset signal following return of power Next command invalid 19 Previous command is active. Only for MDS 507/407E: Status of the dialog battery on the MDS 1 = Battery too low WithotherMDSs,thebitcanhaveavalueof0or1. Battery voltage on MDS has fallen below threshold level. (This bit is always set in the case of MDSs with EEPROM memory.) The available commands are described in the following pages. They are divided into: --- System commands (see section ) --- Process all types of MDS normally (write/read/initialize) (see section ) --- ECC driver active: process all types of MDS (see section ) Number of bytes Length of user data in telegram (no. of characters minus AB byte) Minimum: AB = 2 Maximum: AB = 254 (depends on the length of the data blocks specified in the command) 1D 1E 1F Not enough RAM on the ASM Incorrect no. of characters in telegram ASM command aborted with RESET ECC correction was performed (data in response telegram OK) Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

25 ASM 420 Technical Description 6GT AF00--0DA System Commands Command table: Comm. (hex.) Description 00 RESET 1) 2) ASM is reset. The active command is aborted. The ASM requires about 200 msec to execute this command. (The reset acknowledgment returns the error 1F when an MDS command is aborted.) The following can be set during a RESET with parameter transmission. - Operation with MDS 507/407E - ASM 420 operates as dialog module (CAUTION: Activated dialog operation can only be deactivated by turning off the module.) - MOBY-V procedure for SLG Check status 1) 06 DI/DO command 1) Returns the status byte as the response. The status command can be sent to the ASM at any time. The ASM replies to it immediately. It can be used to check whether an MDS is present. Note: The ANW bit in the acknowledgment is only reported when some type of presence check is activated (cf. chapter 5). The status command has no effect on the MDS. Two digital output bits can be addressed directly. The response telegram contains the value of the two digital input bits. 07 Next The following command(s) should refer to the next MDS. This enables the user to initiate a command immediately even when the old MDS is still in the field. The NEXT command should only be used if proximity detection has been enabled on switches 7 and 8. If proximity detection is enabled, the NEXT command will flip the DOs (see chapter 5). 1) These commands are always accepted by the ASM module and processed with priority treatment. Check status and DI/DO command do not interrupt a pending MOBY command. 2) Caution: Before processing an MDS 507/407E, an extended RESET command with the parameter t ABTAST > 0 must be transferred to the module. 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

26 6GT AF00--0DA2 ASM 420 Technical Description Detailed telegram layout: Command Command Telegram to ASM 420 Response Telegram from ASM (RESET) RESET with parameter transfer F t ABTAST* Param RESET signal following power failure: is automatically transmitted once when power returns Scan intervals (Cf. MDS 507/407E description) Bit: = Continuous scanning for ANW check with field scanning (default) Time value: 01 to 3F (is multiplied by the time base) Time base: 00= Time value times 10 msec 01= Time value times 100 msec 10= Time value times 1 sec 11= Time value times 10 sec When dialog is activated, error message 03 is returned if no SLG is connected to the ASM. 00 = No special parameterization 81 = Activate dialog. C0 = Activate MOBY-V procedure. D0 = MOBY-V w. ANW Switches 7 and 8 90 = MOBY-I w. ANW must be on 00 (cf. chap. 2.3). 01 (Status) Status/ error ANW/ BUSY Bit: ANW Busy 06 (DI/DO) xx 0 No MDS in window 1 MDS in window xx 1 MDS command to ASM active 0 No command to ASM active; ASM can be programmed with read/write commands Control DOs Read DIs Bit: / DI1 DI0 DO1 DO0 0 DOs must be set or reset. 1 DOs to be OR-linked or left unchanged (interrogate DI/DO only) 07 (Next) *) Function of t ABTAST (important for MDS 507): If no MDS is in the field, the ASM continuously scans its surroundings for an MDS. When an MDS has been detected (i.e., ANW = 1, green LED ON), the surroundings are only scanned at the time interval specified by t ABTAST. This means that the ANW signal can only be removed at the t ABTAST time intervals. Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

27 ASM 420 Technical Description 6GT AF00--0DA Process All MDS Types (Normal Operation) Command table Command Hex. Decimal Description Read data block from MDS Write data block to MDS 24 Initialise MDS MDS Type INIT Duration End Addr bytes RAM MDS: 0.1 sec bytes EEPROM MDS: 6 sec kbytes RAM MDS: 0.3 sec kbytes EEPROM MDS: 25 sec kbytes RAM MDS: 2 sec Detailed telegram layout: Command Command Telegram to ASM 420 Response Telegram from ASM 420 *) Address MSB LSB LNG AB 50 00** Address LNG D1 to Dn (40,C0) MSB LSB 51 AB Address LNG D1 to Dn MSB LSB 00** (40,C0) Data End addr MSB LSB ** (40,C0) Where: D1 to Dn User data (max. of 248 bytes per command) LNG Length of data block (max. of 248 bytes) Note: Address + LNG must be less than the end address of the MDS. Address AB Data End addr. +1 Start address of the data to be processed on the MDS MSB = Most significant byte LSB = Least significant byte Number of subsequent characters in telegram AB=LNG+5 Data is written to the MDS during initialisation. Memory size of MDS *) If an error was detected, the response telegram will always be 3 bytes in length. 02 Command Error **) The status byte of the response telegram depends on the MDS type (status of battery). 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

28 6GT AF00--0DA2 ASM 420 Technical Description ECC Special Driver Active (All MDS Types) The ECC driver The ECC driver (Error-Correction-Code) can be activated by the command code in the telegram. Data correction: If 1 bit of information should be lost from MDS memory at any time (e.g. in the case of an MDS with an EEPROM that has been write-accessed frequently), the ECC driver can reconstruct the lost data bit. The user can be certain of receiving the correct data. The user can examine and evaluate the data correction using the status byte in the response telegram (e.g. initiate prompt replacement of the used MDS). Command table Command Hex. Decimal Description A Read data block from MDS with ECC Write data block to MDS with ECC 26 Initialise MDS MDS Type INIT Duration End addr bytes RAM MDS: 0.2 sec bytes EEPROM MDS: 12 sec kbytes RAM MDS: 4 sec kbytes EEPROM MDS: 50 sec kbytes RAM MDS: 53 sec Detailed telegram layout: Command Command Telegram to ASM 420 Response Telegram from ASM 420 *) Address LNG MSB LSB AB 40 00** Address LNG D1 to Dn (40,C0) MSB LSB 41 AB Address LNG D1 to Dn MSB LSB 00** (40,C0) 1A 06 1A 00 Data And addr MSB LSB 02 1A 00** (40,C0) Where: D1 to Dn User data (max. of 248 bytes per command) LNG Length of data block (max. of 248 bytes) Note: Address + LNG must be less than the end address of the MDS Address Start address of the data to be processed on the MDS MSB = Most significant byte LSB = Least significant byte AB Data End addr. +1 Number of subsequent characters in telegram AB=LNG+5 Data is written to the MDS during initialisation. Memory size of MDS *) If an error was detected, thw response telegram will always be 3 bytes in length. 02 Command Error **) The status byte of the response telegram depends on the MDS type (status of battery) Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

29 ASM 420 Technical Description 6GT AF00--0DA2 Function: The ECC driver divides MDS memory into 16-byte blocks, of which 14 bytes are user data and 2 bytes ECC information. At least one block is read or written each time the MDS is accessed (even if the user has only specified one byte). This slows down access to the MDS data (see table in catalogue). If an ECC MDS is read without the ECC driver (e.g. by the STG), the ECC bytes between the user data can be recognised. If an ECC MDS is written without the ECC driver, the data structure of the MDS will be destroyed. The MDS (or the corrupted data block) will no longer be able to be read by the ECC driver. Application: The ECC driver provides increased accuracy of the data on the MDS. Manufacturers of MDSs with EEPROMs will only guarantee up to 10,000 write operations. If the ECC driver is activated, the user can be assured of data integrity for the entire lifetime of the MDS. For reliability reasons, the ECC driver can also be used with MDSs having RAM memory if extremely high levels of interference are likely to affect the memory of the MDS. Example: Data structure of a 62-byte MDS. (The following table is for clarification purposes only and can be ignored by the programmer/user.) MDS Address as Seen by User Address on MDS Function ECC ECC 14 bytes of user data 1st block ECC ECC 14 bytes of user data 2nd block ECC ECC 14 bytes of user data 3rd block An incomplete block at the end of MDS memory cannot be used for user data. Note: --- More time is needed to access MDS data (i.e., less data can be processed in dynamic mode). --- The net capacity of the MDS will be reduced. --- When performing data correction, the response may be delayed by up to one second. --- A normal MDS must be initialised before going into service with an active ECC driver (e.g., with an STG). 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

30 6GT AF00--0DA2 ASM 420 Technical Description SINUMERIK Telegrams SINUMERIK telegrams use the 3964R protocol (see section 3.3.1). The ASM is always the SLAVE. In addition to the normal SINUMERIK applications, the telegrams described below can also be handled by all computers supporting the 3964R protocol. The difference between the SINUMERIK telegram and the standard 3964R telegram lies in the extended telegram header. An advantage of this type of telegram is that it allows up to 4 ASM 420 stations to be driven like a bus by a single serial interface (see section 2.4.8). The format of the SINUMERIK telegram as used in the System 800 forms the basis for the telegram layout and the exchange of telegrams between the controller and the ASM. The requirements for interfacing to SINUMERIK are described in the following section. The user (SINUMERIK) must always ensure that a command is only sent to one ASM at a time. The next command may only be transmitted after a response telegram has been received. If this rule is not followed, data on the serial interface may be corrupted, which would result in the ASM aborting the command. The sender would then not receive a response to his command. A command must always be sent from the SINUMERIK to an ASM when the corresponding digital input signals the presence of an MDS. If data carriers arrive at more than one SLG read/write device at the same time, they must be processed in sequence by the user. System commands, as used in the standard telegrams, are not possible with the SINUMERIK protocol. Note: --- When using the SINUMERIK protocol, one of the proximity detection mechanismus described in chapter 5 must be enabled. If this is not done, the ASM will not respond to telegrams. --- When the SINUMERIK protocol is used, no startup telegram is sent by the ASM 420 when power returns. --- When the SINUMERIK protocol is used, the dialog function cannot be used. Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

31 ASM 420 Technical Description 6GT AF00--0DA2 General telegram layout: Minimum telegram length n(bytes) Telegram header (e.g., AS512) DW no. TEDAL (hex) IDENTIFICATION (ASCII) Telegram fnr (fixed point) data User data (coded by user) Data in the telegram header are not evaluated by the ASM. The SINUMERIK receives the telegram header back in the response (i.e., positive or negative). The DW no. (hex.) is corrected and returned in the response telegram. It is calculated as: Length of data in telegram. The sum of IDENTIFICATION + fnr + user data andisatleast10byteslong. Error numbers (see chapter 7) IDENTIFICATION contains thetypeofcommandand is described below. The length of user data ranges from 0 to 224 bytes. The data can contain any values. (TEDAL + 2) 2 Reading data carriers: Command telegram from SINUMERIK to ASM 420: IDENTIFICATION fnr User Data T 20 C R I/F no. ASM no. Type Address Amount Acknowledgment telegram: Positive acknowledgment (with data): IDENTIFICATION fnr User Data R 20 C R I/F no. ASM no. Type Address Amount Data read from MDS (1 to 214) Negative acknowledgment (with error): IDENTIFICATION T 20 C R 20 F fnr No. as in list User Data I/F no. ASM no. 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

32 6GT AF00--0DA2 ASM 420 Technical Description Writing to data carrier: Command telegram from SINUMERIK to ASM 420: IDENTIFICATION fnr User Data R 20 C I/F ASM W Type Address Amount no. no. Data to be written to MDS (1 to 214) Acknowledgment telegram: Positive acknowledgment: IDENTIFICATION fnr User Data T 20 C W I/F no. ASM no. Type Address Amount Negative acknowledgment (with error): IDENTIFICATION R 20 C W 20 F fnr No. as in list User Data I/F no. ASM no. RESET command: IDENTIFICATION C 20 C R fnr I/F no. User Data ASM no. The RESET command can be sent to a specified ASM at any time. It cancels any pending command and is used to synchronize the ASM with SINUMERIK. The RESET command is best programmed during cold start and restart sequences. Note: The ASM 420 does not send any further response message or acknowledgment in response to the RESET command. An acknowledgment can be sent when the RESET command cannot be interpreted. Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

33 ASM 420 Technical Description 6GT AF00--0DA2 NEXT command: Command telegram from SINUMERIK to ASM 420: IDENTIFICATION C 20 C N fnr I/F no. User Data ASM no. Acknowledgment telegram: Positive acknowledgment: IDENTIFICATION Q 20 C N frn No. as in list User Data I/F no. ASM no. Negative acknowledgment: IDENTIFICATION C 20 C N 20 F fnr No. as in list User Data I/F no. ASM no. The NEXT command terminates the dialog with a data carrier. If a new MDS is to be processed by the ASM without previous programming of a NEXT command, the logic in the ASM will generate an error. The NEXT command directly affects the control of the ASM s digital outputs (see chap. 5). 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

34 6GT AF00--0DA2 ASM 420 Technical Description Description of telegram data (with error numbers): IDENTIFICATION: 1st byte: T = Transmit R = Receive C = Command Q = Acknowledgment 3rd byte: C = Code carrier 4th byte: R = Read W = Write N = NEXT command R = RESET command 6th byte: F = Error telegram fnr: Error numbers from ASM to SINUMERIK (see chap. 7 for detailed description): 0001 = Read / write not possible since no MDS present 0002 = Error in user data during read (type, address, amount or length of data) 0003 = Read operation aborted since MDS has left the window 0004 = Error in user data during write (type, address, amount or length of data) 0005 = Write operation aborted since MDS has left the window 0040 = Error in interface to SLG read/write device 0041 = Error in MDS memory 0042 = Previous command still active 0043 = NEXT command not permitted 0044 = Field interference in SLG read/write device 0045 = Too many transmission errors 0046 = Cannot write to MDS memory 0047 = ECC error 0050 = MDS battery nearly discharged (not an error message; this message is transmitted to the user in the acknowledgment telegram without the F identification. This message is standard for all MDSs with EEPROM memory = The 2nd MDS battery is nearly discharged = ECC correction was performed. Error numbers from SINUMERIK to ASM: 0302 = Watchdog period for response telegram from MDS has expired.! ASM performs a RESET. All other error messages that the ASM receives are ignored. I/F no.: Interface number: This is provided by the user. This number is returned to the user in the response telegram (positive as well as negative). This enables the user program to allocate a response telegram to a specific channel. Since the ASM does not use the I/F no. parameter for any other purpose, it can contain any value. In the special SINUMERIK environment it contains the numbers 0 to 3 (ASCII) (i.e., hex: 30 to 33). Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

35 ASM 420 Technical Description 6GT AF00--0DA2 ASM no.: Address from 0 to 3 (ASCII) (i.e., hex: 30 to 33). Address of the ASM to which the command is addressed, or from which a response telegram is received. The ASM no. is set using the ASM switch bank S1 (see section 2.3). If more than one ASM is being driven from a serial interface, each ASM will be able to pick up the command. The command will only be executed by the addressed ASM, however. Type: Command type: The following numbers are permitted = Read/write all types of MDS; ECC = enabled (see section ) 0006 = Read/write all types of MDS; normal operation (without ECC) Address: Address specifies the start of a data block on the MDS. It depends on the type of MDS and the type of command. TheaddressiscodedinBCD. MDS Type Comm. Type Start Address 62 byte RAM byte EEPROM 5 6 2kbyte 5 RAM 6 8kbyte 5 EEPROM 6 32 kbyte 5 RAM GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

36 6GT AF00--0DA2 ASM 420 Technical Description Amount: Indicates the size of the data block. The maximum size depends on the type of MDS. The number is coded in BCD. MDS Type Comm. Type Block Length 62 byte RAM byte EEPROM 5 6 2kbyte 5 RAM kbyte 5 EEPROM 6 32 kbyte 5 RAM User data: User data are user specific and can be in any format. The amount of user data varies between 0 and 224 bytes. The user stores his data in a data block. The user data of the acknowledgment telegram are stored in a data block. Other definitions: If the ASM receives a telegram containing the error identification F, it ignores the telegram without any visible reaction. Some error telegrams are handled internally like a RESET command. If the ASM receives an unknown IDENTIFICATION, the unknown IDENTIFICATION is returned with the error identification F. Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

37 ASM 420 Technical Description 6GT AF00--0DA2 3.3 Protocols Protocol ASM 420 (V.24/RS 232) ASM 420 (RS 422/RS 485/V.11) ASM 420 (TTY) 3964R Yes Yes Yes SINUMERIK Yes (with CP 315 only 1 ASM permitted) Yes (with CP 315) Yes Lauf Yes Yes Yes SINEC L1 No Yes (direct connection to SINEC L1) Yes (connected via bus terminal) R Protocol The 3964R protocol provides secure data transmission over a point-to-point connection. Security is provided by transmitting data one block at a time, with parity check, block check character (BCC) and acknowledgment of receipt. All characters from 00hex to FFhex can be sent in the data block. Feature of SINUMERIK protocol: Up to 4 ASM 420 stations can be driven from a single serial interface on the computer. Control of the protocol (command acknowledgment) is always handled by ASM no. 1. The other ASMs (nos. 2, 3, and 4) can also pick up the command but the command will only be executed by the ASM specified in the telegram. Character frame: Transmission: Asynchronous Baud rate: 2400, 4800, 9600 Baud Data bits: 8 Parity: odd parity Stop bits: 1 The exact format of the protocol is described in a number of Siemens publications (e.g. order no. C71000-T8700-C25-1. Control characters used in the 3964R protocol: Character Code (Hex) Meaning STX DLE ETX DLE NAK DLE DLE Initializes a send procedure (signals readiness to send) End of transmission block Ready to receive (or duplicated DLE in data stream) Negative response following Block Check Error or start character undetected Duplicated DLE in data block; used when the value 10hex occurs in the data stream 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

38 6GT AF00--0DA2 ASM 420 Technical Description Block transmission sequence: Sender Receiver Data block STX 1st user data byte 2nd user data byte. Last user data byte. DLE t z = Watchdog timer on ASM 300 msec t z DLE ETX BCC DLE Lauf Protocol Simple protocol for point-to-point connection with a parity check for data security. This protocol does not support additional acknowledgment or error identification procedures. The Lauf protocol is not uniform (i.e., the protocol cannot transmit all characters). For this reason, the telegrams described in section are recoded if the Lauf protocol is used. Method: 1userdatabyte(hex.)willbetransmittedto/fromtheASMas2ASCIIbytes(seeexample). Character frame: Transmission: Asynchronous Baud rate: 2400, 4800, 9600 Baud Data bits: 8 Parity: odd parity Stop bits: 1 Control characters: STX (= 02hex) Start of telegram ETX (= 03hex) End of telegram CR (= 0Ahex) New line (carriage return) The control characters may not be used as user characters. Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

39 ASM 420 Technical Description 6GT AF00--0DA2 Data format: Data are transmitted as data blocks. STX (02hex) Data (only ASCII characters 0 to 9, A to F) ETX (03hex) The maximum block length including STX, ETX is 514 bytes. Block transmission sequence: Sender Receiver STX Data block 1st user data byte 1st ASCII byte 2nd ASCII byte 2nd user 3rd ASCII byte data byte 4th ASCII byte t z t z t z =Watchdogtimer on ASM 300 msec Last ASCII byte CR ETX *) *) A CR as the next to the last character in the telegram is optional. The ASM does not necessarily expect one in the command. The ASM always returns a CR in the response telegram. Watchdog timer: The watchdog timer on the ASM is set to 300 msec for all baud rates (i.e., once the transmission of a block has been started with STX to the ASM, the next byte must arrive within 300 msec). If the watchdog time interval expires, ASM ignores the corrupted telegram. Data collision: If the ASM and the computer send a telegram at the same time, the ASM acts as the master and is allowed to send its telegram immediately. An incoming telegram can be handled by the ASM at the same time as it transmits a telegram. (The ASM can operate in full-duplex mode.) Ensuring security of transmission to the ASM 420 Corrupt telegrams and telegrams with parity errors are ignored by the Lauf protocol on the ASM, and no response is sent. By using the status command at the telegram level, the user has a means of interrogating the ASM. The status command returns the status byte immediatelyin response. Bit 0 of the ANW/BUSY byte indicates whether the ASM is currently processing a command. 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

40 6GT AF00--0DA2 ASM 420 Technical Description Another way of monitoring transmission is by setting a watchdog timer for the response telegram. A rough guide for the duration of this timer is indicated below. Example: The ASM requires about 1 second to transmit 1000 bytes of data to/from the MDS, assuming the MDS is already in the transmission window. This only applies to RAM versions. Transmission of the RESET command using the Lauf protocol: Standard telegram (see section 3.2.1): (hex.) Telegram currently being transmitted: A 03 (hex.) STX RESET command (coded in ASCII) (CR) ETX optional All telegrams described in section can be recoded in accordance with this method. Example for read times with Lauf procedure: Reading 1250 bytes with 5 commands at 250 bytes each and a Baud rate to the PC: 9600 Baud: = 4.3 seconds Baud: = 2 seconds Other processing times on the PC are not included SINEC L1 The protocol on the SINEC L1 bus cannot be accessed by the user. It is processed automatically by the SINEC L1 master. The SINEC L1 master consists of the SIMATIC CP530 module with COM530 software, for example. Standard function blocks (handling blocks) are provided for handling communication with the CP530 module (SEND, RECEIVE, CONTROL, SYNCHRON). Data in the data blocks for the SINEC L1 function blocks must be formatted as described in section (standard telegrams). The DF30IX or DF32L1 module can be used in all IBM-AT compatible PCs. This permits a SINEC L1 master to also be set up on the PC. Additional information about the structure of the SINEC L1 bus can be found in the manual: SIMATIC S5; Bus System SINEC L1, order no. 6ES5998-7LA11. Note: In configurations with many L1 bus stations, it may take a relatively long time (1 to 2 seconds) before the bus master fetches a telegram from the ASM. This time must be taken into account, particularly during dynamic operation, if a point is to be set after an MDS has been read by MOBY. Some examples of telegramsareshowninsection3.4. Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

41 ASM 420 Technical Description 6GT AF00--0DA2 3.4 Telegram Examples Example 1 (with ES120): The ES120 is to read a data block (address 10 to 19) from the data memory using the 3964R protocol. The terminal must first be parameterised with the IP command. Program: 10 MDSA 5H, 40H, 0, 0, 10, DIM E#[256], X$[4], Y$[4], Z$[4] 30 REQUEST: CHN {1} 40 REM Send read command to ASM 50 READ A&, B&, C&, D&, E& 60 PUT: CHN{1} FROMA&,B&,C&,D&,E&,F& 70 REM Get result 80 PUT: MAS FROM IM Get result 90 RECEIVE E# 100 F% = E#[5:1] 110 IF F% <> 0 THEN REM Result in buffer from address 9 onwards 130 PUT: MAS FROM Data:, E#[9:10] 140 GOTO REM Error handling 310 X% = E#[3:1] 320 Y% = E#[4:1] 330 Z% = E#[5:1] 340 X$ = HEX$(X%) 350 Y$ = HEX$(Y%) 360 Z$ = HEX$(Z%) 370 PUT: MAS FROM Error:, X$[3:2], Y$[3:2], Z$[3:2] 400 RESTORE END 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

42 6GT AF00--0DA2 ASM 420 Technical Description Example 2 (with ES120): A data block is to be read from a 32-KB MDS and displayed: Addr. 250, length 10 bytes The system is to wait for the next data carrier following the read operation. The read and display procedure is then repeated. The program is written for an ES120. The LAUF driver is used. This example can be used for other PCs relatively easily. Program flowchart: General definitions NEXT command to ASM: The next command refers to the next MDS to enter the transmission window. Wait for telegram Telegram = NEXT? Yes Send command to ASM: Command = 50 Wait for response telegram from ASM Status byte = 00? Yes Display response telegram on screen. No No Program for example 2: 10 DIM E#[256], E1$[50], F#[256] 20 REQUEST: CHN {1} 30 REM NEXT Send command 40 PUT: CHN{1} FROM RECEIVE E# 60 E1$ = E#[3:6] 70 IF E1$[1:6] <> THEN 400 ; Error 80 REM Output chained command 100 PUT: CHN{1} FROM FA0A 110 REM Get response telegram from ASM 150 RECEIVE F# 160 E1$ = E#[3:6] 170 IF E1$[5:2] <> 00 THEN REM Display data read 190 PUT: MAS FROM IM Data:, F#[15:20] 200 GOTO REM Output error 410 PUT: MAS FROM M Error:, E1$[1:6] 420 END Output error and error number (wait for error acknowledgment) Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

43 ASM 420 Technical Description 6GT AF00--0DA2 Example 3: Programming of function block calls using SINEC L1 in SIMATIC S5: DB150 The command and response are stored in DB150 0 : KH= 0000; 1 : KH= 0540; 2 : KH= 0001; 3 : KH= 003A; 1st DW to be sent: must always be 0000 Command starts here: Read 32 KB MDS... from address 256 (page 1, addr. 0); length = 58 bytes (= maximum SINEC L1 block length) 64 : KH= 0003; 65 : KH= 0100; SINEC L1 header : : : KH= 003A; KH= 3F40; KH= 0001; MOBY command executed (see standard telegrams) : : : KC= MOBY-I, THE RELIABLE IDENTIFICATION SYSTEM KC= NR1 ; The data read from the data carrier are stored in the DB, starting at data word Transmit telegram :SPA FB247 NAME :CONTROL SSNR : KYO,2 A-NR : KYO,1 ANZW : MW100 PAFE : MB102 : :U E 8.0 :UN M :U M :R M :S M :SPB FB244 NAME :SEND SSNR : KYO,2 A-NR : KYO,1 ANZW : MW100 QTYP : KCDB DBNR : KYO,150 QANF : KF+0 QLAE : KF+33 PAFE : MB102 : TRANSMIT SWITCH = ON? TRANSMIT READY New Transmit command --> INTERNAL FLAG: The formatted telegram was sent ; Data block = 150 ; Send from address 0 ; Block length = 66 byte ; of which 64 bytes are ; user data ; (= maximum length ; of data block) --- Receive telegram : :SPA FB247 NAME :CONTROL SSNR : KY0,2 A-NR : KY0,101 ANZW : MW104 PAFE : MB106 ; :UN M :BEB -> STILL NO DO TELEGRAM : :SPA FB245 NAME :RECEIVE SSNR : KY0,2 A-NR : KY0,101 ANZW : MW104 ZTYP : KCDB DBNR : KY0,150 ZANF : KF+64 ZLAE : KF-1 PAFE : MB106 : :L DL64 :L KB0 :!=F :BEB --> NOTHING RECEIVED :T DL64 = RESET RECEIVE :L DW66 = 1st incoming user data word : (format as for standard telegram) : EVALUATION OF MDSs FOLLOWS : **************************** :L KB0 Error analysis: Status byte must be 0!! :L DL67 :><F :SPB = ERR : : -> Run error routine; Invalid data 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

44 6GT AF00--0DA2 ASM 420 Technical Description 4 Cold Start and Restart ASM always executes the cold start and restart procedure following a failure of the 24 V supply. ThepresenceofanMDSischeckedwhenpowerreturnsandtheDOsarecontrolledaccordingly(onlyif ANW check is enabled). The ASM then attempts to issue a RESET telegram. Lng Command Status No startup telegram for F SINUMERIK and SINEC L1 This telegram tells the user that the ASM is operational (the startup process takes a maximum of 1.5 secs). The ASM is still operational even if the computer does not accept the startup telegram. The ASM does not repeat the startup telegram, however. Digital outputs: Caution: Both DOs are active for about 200 ms after power is first switched on. This brief startup time is caused by the ASM hardware and cannot be eliminated. Proximity detection during startup: The procedure to determine whether an MDS is in the SLG s window during startup is always the same. The ASM scans its surroundings for about 200 msec to determine whether a mobile data carrier is present. DO0/DO1 are controlled, depending on whether an MDS is present, and the startup telegram shown above is then sent. Note: If the 3964R protocol is being used and the startup telegram was not acknowledged by the computer (computer not connected or switched off), the ASM will need about 5 seconds before proximity detection becomes operational. SINEC L1: The ASM, and consequently proximity detection, will not function if the SINEC L1 bus is in STOP, or if the SINEC L1 master does not correspond to the number set on the ASM. During startup, the ASM responds as follows if... a) No MDS is present: The ASM waits for an MDS or a read/write command. A NEXT command will be ignored. b) An MDS is present: TheASMwaitsforaread/writecommandbeforetheMDSleavestheSLGwindow.ANEXTcommand causes a subsequent read/write command to be performed on the next MDS that enters the window, not the one that is already there. Startup for SINUMERIK protocol: Approximately 1.5 seconds after power returns, the computer can interrogate DO0 of the ASM (i.e., digital input on computer) to establish whether there is an MDS in the SLG window. Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

45 ASM 420 Technical Description 6GT AF00--0DA2 5 DI/DOs and Proximity Detection Various modes of operation can be set using switches 7 and 8. The precise interaction between these modes and the components below are described in this chapter (see also section 2.3). --- DI/DO --- Proximity detection --- Status byte --- DI/DO command --- NEXT command Definitions: -- Proximity detection Proximity detection is a recognition logic in the ASM firmware that detects whether a mobile data carrier is currently within range of the SLG read/write device. It can be controlled in three ways. a) Via 2 DIs: The ASM receives a signal on DI0 when the data carrier enters the window. The ASM receives a signal on DI1 when the data carrier leaves the window. b) Via field scanning: The ASM firmware constantly monitors its magnetic field to determine whether a mobile data carrier is present. Hysteresis prevents the system toggling rapidly between present and not present when the data carrier stops at the edge of the field. c) Via 1 DI: DI1 tells the ASM that an MDS has left the window. The ASM is ready for programming of the next MDS. The presence of an MDS is determined by field scanning. -- Presence: A mobile data carrier is currently within range of the SLG. The ANW bit is set during the status command (see section ). The presence of an MDS can also be detected from the status of the digital outputs. The digital output z18 (i.e., ANW) is the same as the ANW bit of the status command. 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

46 6GT AF00--0DA2 ASM 420 Technical Description -- Digital inputs DI0, DI1 for a) Automatic control of the presence of an MDS b) One or two general-purpose digital inputs which can be interrogated by the computer with the DI/DO command. Note: The DIs can also be interrogated by the DI/DO command if operating under a). -- Digital outputs DO0, DO1 for a) Transport control when using proximity detection DO0 controls the motor of a conveyor belt or is an output signal indicating the presence of a mobile data carrier. DO1 controls a pallet stopper or indicates the presence of a mobile data carrier. DO0/DO1 can also be wired directly to the inputs of a controller (e.g., in SINUMERIK applications). b) 2 general-purpose digital outputs when working without proximity detection The status of the DOs can be interrogated and modified by the computer (set, reset). -- ANW/Busy byte: The ANW/Busy byte can be interrogated using the STATUS command. Bit 1 indicates whether a data carrier is present, among other information. Bit 0 indicates whether an MDS command is currently being processed (see section ). -- NEXT command: The NEXT command is used to advance the ASM controller to the next mobile data carrier. The NEXT command must always be programmed if proximity detection is being used. The NEXT command tells the ASM to flip the digital outputs (see diagrams on the following pages). A read/write command for the next MDS can be sent to the SLG read/write device as soon as the ASM has acknowledged the NEXT command. The new command remains in the ASM until the old MDS has left the window and a new MDS has entered. This programming method means that an ASM command can be executed as soon as an MDS enters the SLG window. There is no difficulty in complying with the MOBY-I project design guidelines as the response times of the computer or serial transmission speed to the ASM do not become factors in the configuration. Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

47 ASM 420 Technical Description 6GT AF00--0DA2 5.1 Proximity Detection with 2 DIs Diagram: a a MDS Direction of MDS SLG Proximity switch on DI0 Proximity swich on DI1 Computer or PC ASM 420 a: Distance from center of SLG read/write device to input/output proximity switch: 10cm<a<50cm The maximum value of a can also be larger. Remember that 2 MDSs cannot then be positioned between the input and output proximity switch at the same time. The minimum distances between each MDS must also be maintained. (See MOBY catalogue.) DI0: DI1: Receives a signal when the MDS comes within range of the SLG read/write device. This signal can be received before the MDS actually enters the SLG window. The input signal may also be generated by a controller. Receives a signal when the MDS goes out of range of the SLG read/write device. The ASM is then ready to process the next data carrier. While a command is active, the MDS can leave and re-enter the magnetic field of the SLG any number of times. The ASM command must have been completely executed before the MDS reaches the DI1 switch. 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

48 6GT AF00--0DA2 ASM 420 Technical Description Timing diagram: DI0 Pulse width at least 50 msec A number of pulses may occur in sucession. DI1 DO0 DO1 ANW** (Status command) Activate ASM: RESET ASM ready to receive (no MDS present) MDS comes Read/ ASM has re- MDS within range of SLG write commands executed by ASM ceived a NEXT command. The DOs are set accordingly. *) leaves SLG window. A command for a new MDS can now come from the computer. *) The DOs also flip when the MDS goes out of range of the SLG before a next command arives (signal on DI1). **) The ANW signal on the basic connector is an inverted version of the signal shown above. Error messages: Error 01: Error 02: A signal is received on DI1 while the ASM is executing a command with the MDS. The command is aborted. The data are invalid. The ASM has received a signal on DI0 (MDS enters) and then a signal on DI1 (MDS leaves) without receiving a data carrier command from the user. Note: This error is not signalled to the control computer until the next command has been received. Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

49 ASM 420 Technical Description 6GT AF00--0DA2 5.2 Field Scanning as Proximity Detection How field scanning works The SLG read/write device scans its surroundings for a data carrier. If one is detected, the ANW bit is set during the status command. When the MDS has left the magnetic field, the ANW bit is also reset during the status command while the SLG scans the field for the next MDS. A hysteresis function ensures that the presence bit is not constantly flipped should the data carrier stop exactly on the boundary of the SLG s magnetic field. This hysteresis function is handled by the processor on the ASM. Read/write commands are handled completely transparently by the ASM and have no effect on proximity detection. Similarly, the presence bit retains its validity after the start of a command. W SLG L c b b a h Hysteresis field for proximity detection MDS L, W: Dimensions of the transmission window of an SLG read/write device at operational distance to MDS (see MOBY catalogue) L = Field length; W = Field width h: Hysteresis: Area in which an ANW bit remains set once it has been set Transmission window: Exchange of data between MDS and SLG h=0.1to15mm (depends on type of MDS) a: The point at which the mobile data carrier is detected by the SLG. The pending MOBY command will now be performed on the MDS. The presence bit remains set. b: The MOBY command must be completed by this point since the data carrier is about to leave the transmission window. The presence bit still remains set. c: The presence bit in the status byte is reset. The MDS has passed out of range of the SLG. Any command that has not yet been processed will be aborted and acknowledged with error 01. DI0,DI1: Both digital inputs can be used as desired by the user. The inputs can be interrogated by the DI/DO command. 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

50 6GT AF00--0DA2 ASM 420 Technical Description Timing diagram: DO0 DO1 ANW** (Status command) 0.5 sec Activate ASM 420: RESET ASM ready to receive (no MDS present) MDS comes within range of SLG Read/write commands executed by SLG SLG has received anext command. The DOs are set accordingly. MDS leaves SLG window. A command for a new MDS can now come from the computer. DO1 goes ON again 0.5 secs after the MDS leaves the transmission window. *) The DOs also flip when the MDS leaves the hysteresis field of the SLG without a NEXT command. **) The ANW signal on the basic connector is an inverted version of the signal shown above. Error messages: Error 01: Error 02: The MDS passed out of range of the SLG while a command was being executed on the MDS. The command is aborted. The data are invalid. There is no command active on the ASM. During this time, an MDS passes through the SLG window shown above. This error is not signalled to the control computer until the next command has been received. Note: The ASM cannot tell whether the MDS has passed through the entire field, or whether it has just entered the field very briefly and then backed out again. Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

51 ASM 420 Technical Description 6GT AF00--0DA2 5.3 Proximity Detection with Field Scanning and 1 DI Diagram: a a MDS Direction of MDS SLG Proximity switch on DI1 Computer or PC ASM 420 The MDS is detected using field scanning (see section 5.2). The DOs flip when the SLG read/write device detects an MDS. The MDS remains present (bit 1 of the ANW/Busy byte set) until a signal is received on DI1. a: Distance from center of SLG to output proximity switch to be configured: 20 cm < a < 50 cm The maximum value of a can be also larger. Remember that 2 MDSs cannot then be positioned between the SLG and the output proximity switch at the same time. The minimum distances between each MDS must also be maintained. See MOBY catalogue. DI0: DI1: Thisdigitalinputcanbeusedasdesiredbytheuser.TheDI/DOcommandcanbeusedtointerrogate the input. Receives a signal when the MDS goes out of range of the SLG. The DI1 switch must not coincide with the edge of the SLG field. If DI1 is outside the field, it makes no difference how often the MDS leaves and re-enters the field while a command is pending on the ASM. The ASM command must have been completely processed before the MDS reaches the DI1 switch. 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

52 6GT AF00--0DA2 ASM 420 Technical Description Timing diagram: <2sec DI1 Pulse width at least 50 msec A number of pulses may occur in rapid sucession. DO0 DO1 ANW** (Status command) Activate ASM: RESET ASM ready to receive (no MDS present) MDS comes Read/write SLG has MDS within range leaves of SLG. commands executed by SLG received anext command. The DOs are set accordingly. *) SLG window. A command for a new MDS can now come from the computer. *) The DO s also flip when the MDS goes out of range of the SLG before a NEXT command arrives (inputs on DI1). **) The ANW signal on the basic connector is an inverted version of the signal shown above. Error messages: Error 01: Error 02: A signal is received on DI1 while the ASM is executing a command on the MDS. The command is aborted. The data are invalid. The ASM registers a second DI1 signal (after T > 2 sec). The ASM did not receive any data carrier command (incl. NEXT command) from the computer during this period. Note: This error is not signalled to the control computer until the next command has been received. 6 SLG and MDS Configuration and Installation Guidelines The configuration and installation guidelines for the SLG and the MDS can be found in chapter 2 of the MOBY catalogue or in the installation and service manual. All types of SLGs can be connected to the ASM 420. All types of MDS can be processed. Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

53 ASM 420 Technical Description 6GT AF00--0DA2 7 Error Diagnosis and Error Messages Meaning of the LEDs RED: This LED flashes when an error occurs. The most recently detected error status is indicated with the display being overwritten each time a new error occurs. The error indicator can only be reset through a RESET. The b18 pin on the basic connector (X1) carries the same signals as the red LED. Flashing is indicated with 0 V pulses. Flashing of the red LED during normal operation is of secondary importance to the user as long as the system continues to run normally. Some errors can be evaluated by the programmer in his program and responded to accordingly. The error LED is particularly useful during commissioning and service activities. YELLOW: Rapid, irregular flashing indicates that a dialog with the SLG or the mobile data carrier (MDS) is currently in progress. This LED is on continuously when proximity detection is enabled. GREEN: This LED is only of significance if the user has enabled one of the types of proximity detection on switch bank S1. It shows the presence of an MDS in the SLG field. OFF = No data carrier present or proximity detection disabled ON = An MDS is currently within range of the SLG. The z18 pin on the basic connector (X1) carries the same signals as the green LED, but is an inverted version of the green LED. Error indications Errors are indicated on the red LED. Hardware error on ASM: TheASMcannotbeaddressedfollowingahardwareerror.Theerrorisnotsenttotheuser.TheASM must be replaced. ON permanently (shines brightly, pin b18 static low): The PROM on the ASM is defective. ON permanently (shines faintly, pin b18 toggles): TheCPUontheASMisdefective. Medium fast flashing: (Approx. 4 Hz). External RAM on the ASM is defective. Flashing patterns: All other errors are indicated by an easily recognizable flashing pattern. The error is identified by counting the number of pulses following one long pause and the next. These errors are passed to the user (or STG service and test unit). 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

54 6GT AF00--0DA2 ASM 420 Technical Description The ASM is equipped with LEDs for status and error indication. It is nevertheless helpful for commissioning and diagnostic purposes to have test tools available. STG service and test unit: The STG service and test unit is an important tool. The basic functions and hardware of the ASM can be tested using the cable described in section (only RS 422 at present). Interface tester: An interface tester (line tracer) is essential for diagnosing errors at the telegram level. This instrument is connected between the ASM and the computer and records all telegram communication. User programming errors or ASM malfunctions can be clearly identified. Make sure that the ASM interface and that of the line tracer are identical (V.24, RS 232; RS 422, RS 485; TTY). SINEC L1 test: The general functions of a SINEC L1 station can be tested by connecting a programming unit (e.g. PG 750) to the SINEC L1 master. If the functions on the PG do not provide a clear answer, a SINEC L1 bus tester can be used. This consists of a PG, FOX PG software and a special interface cable. It permits all telegram communication on the bus to be recorded. Proximity detection, DI/DO: If proximity detection is being used (see chapter 5), it is very easy to check that it is working properly by connecting a lamp (e.g., LED) to DO1 (or DO0, or ANW). DO1 ca. 3.3 kω LED or: DO1 20 to 30 V DC max. 100 ma per DO If no computer command is active, the lamp will light up as long as there is a mobile data carrier within the transmission window (see timing diagram in chapter 5). The circuits shown above can also be installed in a user junction box to provide a permanent indication of this ASM function. The user will then have a visual means of checking that the ASM is functioning properly. Note: 3964R standard telegrams: If the computer is not ready during startup, it may take about 5 seconds before proximity detection functions. SINEC L1: Proximity detection will not function if the bus is down or the ASM address is not in the distribution list of the SINEC L1 master. Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

55 ASM 420 Technical Description 6GT AF00--0DA2 Troubleshooting a) Check power supply to ASM basic connector X1 or SLG connector using an appropriate measuring instrument. b) Check that the ASM hardware is functioning properly. --- Use an STG service and test unit. --- Enable proximity detection and check whether the green LED indicates that an MDS is present. c) Check parameterization: Baud rate, protocol and proximity detection (switch bank S1). d) DOs do not flip: Measure current from the DOs (max. of 200 ma for 1 or 2 DOs). If the DOs were short-circuited or the current is too high, the DOs are automatically deactivated (over-voltage protection). To commission the system again, disconnect the 24 V supply to the ASM briefly. Reconnect the supply (after about 10 seconds), and the DOs will then be operational again. e) Check cabling to the computer (see chapter 2.4). --- Do the ASM and the computer have the same physical interface? --- Does the interface cable have the correct polarity (RS 422 or TTY)? --- Are the data cables crossed? (RxD from ASM must be connected to TxD of the computer, and vice versa.) --- Is the cable shield positioned correctly? f) When the Lauf driver is used, the telegrams must be sent to the ASM as described in chapter Otherwise, the telegram will not be processed by the ASM. No error message is generated. Error messages: An error message can be output to the computer in the 3rd byte (i.e., status byte) of a standard telegram. The user should interrogate this status byte after each command to check that it has the value 00 (bits 0 to 5 only). With the SINUMERIK protocol, an error is indicated by an F in byte 18. The error number itself is contained in bytes 21 and 22 of the response. The meaning of the various error numbers is shown in the following table. 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

56 6GT AF00--0DA2 ASM 420 Technical Description Status Byte Standard Telegram Cause and Remedy Equivalent SINUMERIK Error Number Hex. Dec. 1) (Fixed Point) No error; result OK *** AsingleflashoftheerrorLEDindicatesthattheASMhasexperienced a return of power but has not yet received a RESET command from the user Proximity error: MDS has left the SLG s transmission window. The MOBY command was only partially processed. Read command: No data sent to the computer Write command: The data carrier that has just left the window has an incomplete data record.! S a (Operating distance from SLG to MDS) is not be maintained.! Configuration error: The data block to be processed is too large (in dynamic mode). The following command will be automatically executed on the next MDS. READ, WRITE or NEXT commands are valid Proximity error:! A mobile data carrier passed by the SLG but was not processed with a command.! The old MDS has left the field. A new MDS is currently located in the field and has received a read/write command. If a NEXT command was programmed instead of the read/ write command, this is acknowledged without an error. This error message is not sent to the computer immediately. The ASM first waits for the next command (Read, Write, Status or Next), which will be rejected immediately with an error. A read/write command was not be executed. The next command is then executed by the ASM normally. A RESET command from the computer also eliminates this error Proximity error: The read/write command cannot be executed at present as there is no MDS in the SLG window. This error is also returned if the SINUMERIK protocol is being used but proximity detection has not been enabled on the ASM (switch 7; 8) ) Corresponds to flashing of the red LED ***) This message only appears on the red LED Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

57 ASM 420 Technical Description 6GT AF00--0DA2 Status Byte Standard Telegram Cause and Remedy Equivalent SINUMERIK Error Number Hex. Dec. 1) (Fixed Point) Error in the connection to the SLG:! ASM power supply < 20 V! Voltage drops on 24 V supply MDS memory error: Nothing has ever been written on the data memory, or its memory contents have been lost due to a battery failure.! Initialize data carrier with the STG service and test unit.! For the ASM: Call initialization command (standard telegrams only).! Check MDS battery, or change MDS if necessary.! Data carrier is defective S Invalid command: ASM cannot interpret the command byte (2nd byte in standard telegrams or IDENTIFICATION with SINUMERIK protocol). S The MDS reports an addressing error. (Check telegram.) Only for MOBY-F:! Read/write area has password protection! FFT command with presence check! Operating mode not appropriate for command (MOBY-I with FFT command) Interference on SLG: The SLG is picking up interference from its surroundings.! External interference field; the interference field can be identified with the inductive field indicator of the STG service and test unit.! The distance between two SLGs is too small and does not conform to the configuration guidelines Too many send errors: Despite several attempts, the MDS was unable to receive the command or the write data from the SLG correctly.! The MDS is right on the edge of the transmission window.! Data transmission to the MDS was affected by external interference The MDS reports very frequent CRC errors.! The MDS is located in the field boundary area or the SLG.! TheMDSand/ortheSLGhas/haveahardwaredefect / ) Corresponds to flashing of the red LED 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

58 6GT AF00--0DA2 ASM 420 Technical Description Status Byte Standard Telegram Cause and Remedy Equivalent SINUMERIK Error Number Hex. Dec. 1) (Fixed Point) During initialization only: CRC error on receipt of acknowledgment from MDS! Same cause as error 06 Only for MOBY-F:! Wrong MDS type with special commands (type 3) 0A 10 During initialization only: MDS cannot execute INIT command.! MDS is defective. 0B 11 During initialization only: Timeout during initialization! The MDS is right on the edge of the transmission window.! The MDS is using too much power(defective).! Only for MDS 507/407E: MDS 507/407E operation was not activated with the reset with parameter transfer command. 0C 12 Cannot write to MDS memory! MDS memory defective! MDS EEPROM has been written too often and has reached its limit. 0D 13 Error in the specified address! The specified address does not exist on the MDS.! Check and correct the telegram formatting command.! The status byte in the command does not have the value 00. 0E 14 ECC error Data cannot be read from MDS.! MDS data are lost (MDS defective).! The MDS was not been initialized by the ECC driver.! Initialize MDS.! MDS with EEPROM has reached the end of its life; the data are lost.! Replace MDS.! TheMDSmovedoutofthefieldwhilebeingwriteaccessed.! The MDS is not positioned correctly / ) Corresponds to flashing of the red LED Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

59 ASM 420 Technical Description 6GT AF00--0DA2 Status Byte Standard Telegram Cause and Remedy Equivalent SINUMERIK Error Number Hex. Dec. 1) (Fixed Point) 0F 15 RESET message from ASM to the computer This message is issued once by the ASM when power is switched on again. This gives the computer the opportunity to recognize that power has returned to the ASM which is consequently operational again. This message will be lost if the computer is not on. Only for MOBY-F:! Internal driver error! FFT command with MDS F1xx in the field NEXT command not possible or invalid! ASM working without proximity detection! ASM still processing a read/write command! ASM has already received a NEXT command Previous command still active A new read/write command has been sent to the ASM even though the previous command is still being processed.! An active command can only be aborted by the RESET command.! The new command will be terminated with error 19 hex; ASM continues to process the old command ** Receive error between user and ASM B 27 Only for MOBY-F:! CRC check in data telegram is wrong! Data distortion! Interface defective ** Send error between user and ASM E 30 S The telegram is not in the format shown in section S AB byte does not correspond to the telegram length.! Check and correct the telegrams in the user program. 1F 31 Communication with the MDS aborted by RESET. This error can only be returned by a RESET command ) Corresponds to flashing of the red LED ** These errors are only indicated by the LED on the front panel or on connector b18. These errors are not transferred to the user. 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

60 6GT AF00--0DA2 ASM 420 Technical Description Status Byte Standard Telegram Cause and Remedy Equivalent SINUMERIK Error Number Hex. Dec. 1) (Fixed Point) 20 (binary xx1x xxxx) 32 Not an error message! Only occurs when the ECC driver is active. Indicates that the driver has detected and corrected a 1 bit error. Data being read or written are OK. 0052* 40 (binary x1xx xxxx) 80 (binary 1xxx xxxx) 64 Not an error message! This bit is normally always set. It is reserved for indicating the status of a 2nd battery on the MDS. When the MDS 507/407E is involved, this bit indicated a low dialog battery. 128 Not an error message! Voltage of MDS battery has dropped below threshold value. Recommended that the MDS be replaced immediately. This status bit is always set on MDSs with an EEPROM. With SINUMERIK, the IDENTIFICATION field will not contain an F in this case. To check for a weak battery, examine the fnr field whenever necessary. 0051* 0050* 1) Corresponds to flashing of the red LED * The following priority applies if several status messages are issued simultaneously: 0052, 0050, Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

61 ASM 420 Technical Description 6GT AF00--0DA2 8 Warnings 6GT CA00 ASM 420 / V.24 Subject to change without notice! GT CC00 ASM 420 / TTY J31069-D0100-U001-A1-7618

62 6GT AF00--0DA2 ASM 420 Technical Description Notes Subject to change without notice! J31069-D0100-U001-A GT CA00 ASM 420 / V.24 6GT CC00 ASM 420 / TTY

63

64 Siemens AG Automation and Drives Systems Engineering P.O. Box 2355, D Fuerth Siemens Aktiengesellschaft Siemens AG, 1999 Subject to change without prior notice Order no.: 6GT2097-3AF00-0DA2 Printed in the Federal Republic of Germany