onum NUM 1060 USE OF THE UNI-TE PROTOCOL en-938914/0 05-94 en-938914/0— onum Despit the care taken in the preparation ofthis document, NUM cannot quarantoe the accuracy ofthe information itcontains and cannot be held responsible for any errors therein, nor for any damage which might result from the use or application ofthe document. “The physical, technicaland functional characteristics ofthehardware andsoftware productsandthe services descrbedin this documentare subject to medication and cannot under any circumstances be regarded as contractual ‘Tho programming examples described inthis manual ae intended for guidance only. They must be specially adapted before they can be used in programs with an industal application, according tothe automated system used and the safety levels required © Copyright NUM 1992. ‘Alright reserved. No partof this manual may be copiedr reproducedin any form orby any means whatsoever, including photographicormagnetic processes. The transcription on an electronic machine of all or par af the contants is forbidden, © Copyright NUM 1992 software NUM 1060, ‘This software isthe property of NUM, Each memorized copy ofthis sofware sold confers upon te purchaser a non-exclusive foance strict limited te tho uso of the said copy. No copy or other fom of duplication of this products authorized ri en 93891400Table of Contents 1 Introduction to UNI-TE 9 11 General 8 1.2 Operating Mode 8 13 Special features of NUM 1060 Numerical Controls 10 2 Request Codes 7 2.1 Standard Request Format 4 2.2 Standard Report Format 4 3 List of Requests 13 3.1 Access to Data 13 3.2 Unsolicited Data 13 3.3 General Purpose Requests 13 3.3.1 Requests Addressed to the System 13 3.3.2 Requests Concerning the Communication Interfaces 13 34 Operating Modes 14 35 File Transfers 14 38 Specific Requests 15 4 Description of Requests 7 41 Read and Write Object Requests 7 41.4 Read Objects 7 41.2 — Write Objects 19 4.1.3 Objects Accessible for Read and Write at 4.1.3.1 Objects of the NC Software 21 4.1.3.2 Objects of the PLC Software Programmed in Assembler 25 441.33 Objects of the PLC Software Programmed in Ladder Language 26 42 Unsolicited Data 27 4.3 Unit Identification 28 44 Unit Status Data 29 45 Testofthe System and Communication Path 30 46 Management of Unit Fault History 31 4.7 Stations Managed by the Master 32 4.8 Error Counter Reset 33 4.9 Running the Tasks of a Unit 33 4.10 Stopping Unit Tasks 34 4.11 Initialising a Unit 34 4.12 File Download Requests 35 4.12.1 Setting up a Download Sequence 35 4.12.2 Transferring a Segment 37, 4.12.3 Ending the Download Sequence 38 4.12.4 Example of File Download 39 4.12.4.4 Opening the File (Open-DownLoad-Sequence request) 39 4.12.42 Writing the Start of the Programme (Write-DownLoad-Segment request) 39 en. 93891400, 34.12.43 Writing the Next Part of the Programme {Write-DownLoad-Segment request) 40 4,12.4.4 Closing the File (Close-DownLoad-Sequence request) 40 413 File Upload Requests 4 4.13.1. Setting up an Upload Sequence at 4.13.2 Transferring a Segment 43 4.43.3 Ending the Upload Sequence 44 4.13.4 Example of File Upload 5 4.1.4.1. Opening the File (Open-Upload-Sequence request) 45 4.18.4.2. Reading the Start of the Programme (Read-Upload-Segment request) 45 4.18.4.3. Writing the Next Part of the Programme. (Read-Upload-Segment request) 46 4.18.44 Ending the Upload (Close-Upload-Sequence request) 46 4.14 Deleting a Programme from the RAM 47 4.15 Reading the Number of Bytes Available in the RAM 48 4.16 NC Memory Directory Read Requests 50 4.16.1 Reading the Start of the List of Programmes Present in the NC RAM 50 4.16.2 Reading the Next Patt of the List of Programmes Present inthe NC Memory 81 4.16.3 Closing a Directory Read 52 4.16.4 Example of Directory Read 53 4.16.4.1 Open-Directory Request 53 4.16.42. Reading the Next part of the Directory ectory request) 53 4.16.43 Close-Directory Request 54 417 Sending of Messages by the Supervisor. 55, 418 Stopping the PLC User Tasks 56 4.19 Initialising the PLC. 57 4.20 Running The PLC User Tasks 58 5 Request Transmission by a Client Application 39 5.1 Requester Function 59 5.2 Reception Function 6 4 cn 9389140Preliminary NUM 1060 Network Documentation Structure Integration Document This document is designed for integration of NUM 1060 numerical controls in a network. NUM 1060 UNLTELWAY INTEGRATION MANUAL. Operator Manual This document explains network transfers with a numerical control. en 9389140 - |— onum Use of the UNI-TE Protocol CHAPTER 1 INTRODUCTION TOUNLTE CHAPTER 2 REQUEST ‘CODES CHAPTER 3 ust oF 4 requests | | CHAPTER 4 DESCRIPTION OF REQUESTS ae 6 . Only the requests specific to NUM 1060 numerical controls are detailed herein 1.2 Operating Mode ‘A.unit supporting the UNI-TE protocol can have client andlor server status. The client unit takes the initiative of the communication. It asks @ question (read), sends data (write) or a command (RUN, STOP). The client is sometimes called «requester» The server unit performs the service requested by the client and sends a report after execution Request, cnr f Pew => ation Report Certain unitscan beboth clientandserver. Forinstance, a PLCisa serverforthe system tasks (programming, settings, diagnostic) and may be a client for the NETO and NET functions of the user program (sending of commands, read of states) for another unit, NUM PLC function Request | Request | xXeT8 svsTen |. ATVS {| application | SLAVE MASTER SLAVE Report Report cuIENT LS SERVER | CLIENT 2S SeRVER REMARK The client and server states are independent of the master and slave modes. 20 9389140 9— onum 1.3. Special features of NUM 1060 Numerical Controls NUM 1060 numerical controls include two entities that are capable of dialoguing with other units using the UNI-TE protocol + The NC function which manages path following in particular (execution of part programmes, management of tool and part offsets, axis and spindle measurement and control), = The PLC function that manages the automatic controls of the numerical control NUM 1060 NC Subserver NC FUNCTION ¢ Fopod (server) Aq Rp Request Cc nh Raq Rp. ° (ot Ga Requests M F Repot__}, Client application ve ‘ (client) N | cl Report R CR CHInG LU A System Reports By 9 C Request, een ° PLC Ml FUNCTION Both the NC function and PLC function (system) can act as server (see Chapter 3 for the requests sent to the NC). The PLC function (client application) includes the client function (see Chapter 5 for the request sending procedure). 10 0- 938914002 Request Codes Requests are a sequence of bytes, words (2 bytes) and long words (4 bytes). ‘The bytes of the words and long words are sent beginning with the low byte: Byte Word Long Word Tow T High | Low TWeight Weight) High byte | byte | byte ae MSI byte 2.1. Standard Request Format A request includes: = the request code (one byte) = the sender category code (one byte) - the parameters and/or data (bytes, words or long words: maximum 126 bytes) Taquast | Catogay code | co 2.2 Standard Report Format ‘A report includes: ~ the answer code (one byte) - the parameters and/or data (bytes, words or long words: maximum 127 bytes). It the report is positive, the answer code depends on the request For a negative report, the answer code is H’FD! fewer code Parameters/Data en-93891470 oo— onum 12 en 93891403 List of Requests 3.1. Access to Data These requests give access to the specific objects of the numerical control: Requests Request Answer Description See code code Reak objet ‘4 (H36) 102 (166) Read objects (bis, words) ant Write-Object, 55 (H37) 103 (H67) Write objects (bits, words) 412 3.2 Unsolicited Data This is the only service for which no report is returned. tis actually the answer to an implicit question. This service allows a byte string to be transferred between application programmes without a prior request. The use of these data is up to the receiver which must implicitly be on wait for this answer: Requests Request ~— Answer Description See code code. Unsoleied Data 252 AFC] — Send data wihou Wrstrecewing a request___42 3.3. General Purpose Requests 3.3.1 Requests Addressed to the System These requests are used for diagnostic and setting up. For the numerical control, they include: Requests Request Answer Desoription See code code Taentification 15 (HOF) 63 (HSF) Unit identification: product type, version as and part number Saws 4B(HST) 97 (FST) Information on the status of the unit a 3.3.2 Requests Concerning the Communication Interfaces These requests are used to access certain data of the communication interfaces. They do not include any elements, specific to NUM numerical controls: Requests Request Answer Description See code ___code Winrar 250 (HFA)_251 (TFB) Test of the system and communication path 45 Read-CPT 162 (HAZ) 210 (HZ) Management of the history of ink faults of 4.6 a unit Elat-Station T6S(HAS) 217 HDS) Indicates the number of stations managed by 4.7 the master and their status (connected or not) CleacCPT 6a (HAS) 254 HFE) Resets the error counters of a unit a5 £0 9389140 13— onum 3.4 Operating Modes ‘These requests are used to stop, start or initialise a unit connected to the bus: Requests Request Answer Description See code code Fun 36 (H2a) 254 (HFE)___Staris the tasks ofa a9 Stop 254 (HFE) Stops the tasks of aut 410 Thit 31 (W133) 99 63) Inilalises a unit aii 3.5 File Transfers These requests are used by a client unit to up- or download data blocks (segments), programmes or other data from orto a server. This service is carried out in three steps: = setting up of a sequence defining the nature of the service (upload or download) and identifying the data to be transferred + Tuning of the sequence at the initiative of the client + closing of the sequence. ‘The requests used include: Requests Request Answer Description See code. code ‘Open-DownLoad- 58 (WGA) 106 (WGA) Sets up a download sequence 4184 Sequence Write-DownLoad 59 (138) 107 (68) Transfers a segment aIaE Segment Close-DownLoad- 60 (130) 108 (HC) Closes the download sequence aia3 Sequence ‘Open-UpLoad- 61 (ASD) 10S (HED) Seis upan upload sequence a1at ‘Sequence Read-UpLoad- 2 (HSE) 110 (HOE) Transfers a segment T1S2 ‘Segment Close-UpLoad- 63 (WSF) 117 (HOF) Closes the upload sequence 433 Sequence 14 en 93691400List of Requests 3.6 Specific Requests These requests are specific to NUM 1060 numerical controls. The question and answer codes are set to H'FS!. The requests are differentiated by the additional request codes: Requests ‘Additional Adaiional Description Seo request. answer code code Delete-File 70 (H46) 118 (176) Deletes a programme from the RAM aia Read-Memory= 71(H47)_119(H77) __Relums the number of available bytes in 4.18 Free the RAM pen-Directory 72 (#48) 120 (78) Reads the start of the lst of programmes 4.167 present in the NC memory Directory 73 (449) 121 (A179) Reads the next part of the list or programmes 4.16.2 resent in the NC memos See TAR TATA Ents toad othe ato reas present in the NG memory Wrie-Message 75 (146) 123 (H'7B) Sending of messages by the supervisor a7 ‘Stop-Automate 76 (HC) 124 (H7C) Stops the PLC user tasks 4.18. Tni-Automate 77 (4D) 125 (17D) __Initialises the PLC. 49 jun-Automate, 75 (H4F) 123 (H7F) Starts the PLC user taal 420 09389140 15— onum 16 0 938914104 Description of Requests 4.1. Read and Write Object Requests 41.1 Read Objects Description The Read-Object request is used to read objects accessible for read by the NC and PLC servers of the NUM 1060 numerical control (see Sec. 4.1.3) The data are grouped by families of objects. Each family is identified by a number (segment number). Each object includes one or more data items. After receiving the request, the server returns an answer code followed by the data corresponding to the type of the object(s) requested Transmission Request code / Category code / Segment / Specific byte / Object address / Number of objects Request code 1 byte: 54 (H'36') Category code 1 byte: 0 Segment 1 byte: (see Sec. 4.1.3 for the segment numbers of objects accessible for read) Specific byte 1 byte (size of the object(s) to be read on a PLC programmed in Ladder language, not significant in other cases) Object address 1 word: address of the first object to be read in the family (see Sec. 4.1.3 for the address ofthe first object in the family) Number of objects to be read 1 word: number of bytes to be read starting with the first (see Sec. 4.1.3 for the total number objects in the family) REMARK If the quantity specified is such that the answer could contain more than 126 data bytes, the request is refused (negative answer code). Reception Positive answer Answer code / Specific byte / Data ‘Answer code 1 byte: 102 (H66') Specific byte 1 byte (same value as in the request) Data data bytes: bits, bytes, words or long words (see Sec. 4.1.3 forthe data type of the objects) Negative answer ‘Answer code Answer code 1 byte: 253 (HFD') A negative answer may be due to a segment number that is not recognised, an address outside the limits or an excessive number of objects ) Negative Answer No negative answer 28 00 93891400,Description of requests 4.4 Unit Status Data Description ‘The Status request returns the status of the complete numerical control (NC + PLC). Transmission Request code / Category code / Desired detail Request code 1 byte: 49 (H'31’) Category code 1 byte: 0 Desired detail 1 byte: axis group index Reception Positive answer Answer code / Current status / Status mask / Data / Specific data Answer code 1 byte: 97 (H61) Current status String of 8 bits: + bit 0: system inoperative, + bit 1: detection of a recoverable error, + bit 2: detection of an unrecoverable error, = bit 3: check the auxiliary power source, = bit 4: system reset, + bit 5: critical operation being executed, + bit 6: halt, + bit 7: local mode. Status mask String of 8 bits: mask giving the current significant status bits Data 82 bytes: + 22 bytes corresponding to the programme status of the axis group specified (segment 153 of the NC objects, see Sec. 4.1.3) + 1 byte: operator panel status (EN.100 in assembler, %R3.B in Ladder language), + 1 byte: NC status (EN.101 in assembler, %R5.B in Ladder language), = 1 byte: NC mode (EN. 20 in assembler, %R16.B in Ladder language), + 1 byte: machine mode (EN.22 in assembler, %'18.B in Ladder language), = 1 word: current programme number (ENN.2C in assembler, %R1A.WV in Ladder language), + 1 byte: PLC status + 0:no application + 2:running + 1: stopped + 3: faulty Specific data 16 bytes: table of the PLC memory field whose address is specified by the PL programme Negative answer Answer code ‘Answer code 1 byte: 253 (H'FD) Cause of rejection: axis group unknown, 0 92891400 29— onum 4.5 Test of the System and Communication Path Description The Mirror request tests the system and the communication path. The client sends a sequence to the server and the server returns the same sequence. This request does not contain anything specific to NUM numerical controls, Transmission Request code / Category code / Data Request code 1 byte: 250 (H'FA') Category code 1 byte: 0 Data Byte string (maximum 126) Reception Positive answer Answer code / Data Answer code 1 byte: 251 (H'FB) Data Byte string identical to the string sent Negative answer No negative answer. 30 093891400,Description of requests 4.6 Management of Unit Fault History Description Each station manages a history of link faults (character errors, frame errors, protocol errors) by counting four error types in counters (16-bit words}: = number of messages sent and not acknowledged, = number of messages sent and rejected, - number of messages received and not acknowledged, - number of messages received and rejected. REMARK There is never any counter overflow. The counters remain frozen at H'7FFF' (32767) until they are reset by a Clear-CPT request (see Sec. 4.8). The Read-CPT request is used to read the counters. This request does not include anything specific to NUM numerical controls. Transmission Request code / Category code Request code 1 byte: 162 (H'A2') Category code 1 byte: 0 Reception Positive answer Answer code / Data Answer code 1 byte: 210 (H1D2) Data 4 words: + number of messages sent and not acknowledged = number of messages sent and rejected = number of messages received and not acknowledged number of messages received and rejected Neg ‘Answer code 1 byte: 253 (HFD}) Cause of rejection: request unknown, en 93891400 31— onum 47 Stat ns Managed by the Master Description ‘The bus manager manages the number of stations (link addresses) set and the connected or unconnected status of these stations. The Etat-Station request returns the number of stations and their status, This request: + is processed only on the UNI-TELWAY master = does not include anything specific to NUM numerical controls, Transmission Request code / Category code Request code 1 byte: 163 (H'A3') Category code 1 byte: 0 Reception Positive answer Answer code / Number of stations / Station status Answer code 1 byte: 211 (H1D3) Number of stations 1 byte: number of stations managed Station status 1 bit per station (rank = station address): = bit = 1: station connected = bit = 0: station disconnected Negative answer Answer code 1 byte: 253 (H'FD') Cause of rejection: request unknown, manager not configured 32 en 93891400Description of requests 4.8 Error Counter Reset Deseription ‘The Clear-CPT request resets the error counters of a unit (see Sec. 4.6). This request does not contain anything specific to NUM numerical controls. Transmission Request code / Category code Request code 1 byte: 164 (HAA) Category code 1 byte: 0 Reception Positive answer ‘Answer code 1 byte: 254 (HE) Negative answer ‘Answer code 1 byte: 253 (HFD) Cause of rejection: request unknown, access rights insufficient. 4.9 Running the Tasks of a U Description ‘The Run request starts an NC cycle. Transmission Request code / Category code Request code 1 byte: 36 (H24') Category code 1 byte: 0 Reception Answer code Positive answer Answer code 1 byte: 254 (H'FE’) Negative answer Answer code 1 byte: 253 (H'FD') Cause of rejection: NC status incompatible with a cycle start en o389140 33— onum 4.10 Stopping Unit Tasks. Description The Stop request stops axis feed (FEED STOP). The spindles are not affected. Transmission Request code/ Category code Request code 1 byte: 37 (H25) Category code 1 byte: 0 Reception Answer code Positive answer Answer code 1 byte: 254 (HFE’) Negative answer ‘Answer code 1 byte: 253 (H'FD’) Cause of rejection: NC status incompatible with feed stop. 411i ing a Unit Description The Init request resets the NC. Transmission Request code / Category code Request code 1 byte: 51 (H'33) Category code 1 byte: 0 Reception Answer code / Result ‘Answer code 1 byte: 99 (H'63) Positive answer Result 1 byte: 0 Negative answer Result 1 byte: 10 (H'0A’) Cause of rejection: NC status incompatible with a reset. 34 en 93891400Description of requests 4.12 le Download Requests A file is downloaded as follows: + file opened by a first request (Open-DownLoad-Sequence) specifying the type and possibly the name of the file to be downloaded, ~ writing of the file data by consecutive numbered Write-DownLoad-Segment requests, = closing of the file by the last request (Close-DownLoad-Sequence). REMARKS A single file (all types) or all the Ladder modules can be downloaded. Part programme type files for storage are automatically closed by the NC if the requester does not act within a timeout set by machine parameter P84 (see Parameter Manual). 9 up a Download Sequence ‘The Open-DownLoad-Sequence request starts downloading a file Transmission Request Code / Category code / File identification [/Extension code / Filename] Request code 1 byte: 58 (HA) Category code 1 byte: 0 File identification 2 long words [Type code _ 3 bytes: additional identification | | Long word 1: file identitication Long word 2: additional information File ype tobe downloaded Type code Additional identification ‘Additional information byte 1 byte2___byte3___byted___long word 2 xis calibration Hoo not significant not significant Macros Hos ot significant ol significant Machine parameters: HOS" ot significant Tot significant PLC assembler Hoe o o 0 not significant binary code BUG Laser Bhan code 07 aS 0a tea 2:%TFi 0 Osis 15 The additional identification gives 3:%SPi 0 0sis255 the module type and number 4:%THI 0 Osis 15 5:%INI 0 ° 16:all 0 ° Ladder and C modules Tanguage fies HOS THOT Hat" Tol significant Tattle Hoo /Hor™ Her not significant Part programmes in drip Foc programme number indexed Ting buffer size: feed mode by the axis group (leven and 2048 ) Reception Answer code / Status ‘Answer code 1 byte: 106 (H'6A’) Status 1 byte: see table below ‘Status Type code of the fles concemed Description a all files: request executed i H06, HO7, HOC at Hz file already exists 2 Hos. HO7, HOC ot 12" ‘other programme being downloaded or edited 3 HOG, HOF et Hie" free memory space less than 128 bytes i Hoc* the NC is notin reset state a HOC et Hi [programme number incoherent or PPP buffer size incorrect, a H06 et HOT file type not recognised 28 ___H06 et Hor” ‘system error 36 w-9389140Description of requests Ce ee 4.12.2 Transferring a Segment Description The Write-DownLoad-Segment request is used to load data ina file that has already been opened (see Sec. 4.12.1) ‘A maximum of 122 data bytes can be sent per request. The complete programme is therefore sent using a sequence of requests numbered by increments of 1 Transmission Request code / Category code / Segment number / Segment length / Data Request code 1 byte: 58 (H'3B') Category code 1 byte: 0 Segment number 1 word: the number of the first request is 1 and the subsequent requests are numbered by increments of 4 Segment length 1 word: number of data bytes (maximum 122) Data Character string (ASCII codes) of the part of the programme contained in the request. In the case of a part programme, each block must end with GR and LF {ASCII codes H'0D' and HOA’) Reception Answer code / Status / Segment number Answer code 1 byte: 107 (H68)) Status 1 byte: see table below Sjats Type code of the fies concerned Descriphion a alles request executed 3 Hoe, Hor et Iz memory full a Hog. Ho7, HOG" et iz To file being downloaded 7 HOC” ring buffer full g 06, Hor, HOO et Ia data length error 10 Hoc* NC no longer in dip feed mode a Hoe, HO? et HOC" ‘a block has more than 120 characters, data incoherent 20 Hoe, 07, HOC et HT ‘other programme being downloaded, sender error 35 06, HO7, HOG et 12" ‘Sequence error 23 ____H06et HOT" system error ‘Segment number 11 word: the number corresponds to the segment number of the data being transmitted. en 9389140 374123 Ending the Download Sequence Description The Close-DownLoad-Sequence request is used to end downloading of a file already opened. Transmission Request code / Category code Request code 1 byte: 60 (H'3C') Category code 1 byte: 0 Reception Answer code / Status ‘Answer code 1 byte: 108 (H'6C’) Status 1 byte: see table below Status Type code of the fles concemed Desorption Q all files request executed a Hos, HOT, Ho tH i> no file being downloaded a Hz" file deleted: the last block Toaded did not end with LF 20 Hoe, Or, HOC et HI ‘other file being downloaded, sender error 28 (06 et H ‘system error 38 0 93891400,Description of requests 4.12.4 Example of File Download ‘The following programme is to be sent for storage: 982.1 N10 X0 YO N20 X-140 N3@ Y-60 41244 Opening the File (Open-DownLoad-Sequence request) Request 58 / 0/H'12000141'/ 0 where: - 58 ile open request (byte) - 0 category code (byte) + H'12000141" H'12:: part programme type file for storage 11000141" = 321: indexed programme number (long word) - 0 not significant (long word) Report 106 / 0 where: = 106 file open answer (byte) - 0 request executed (byte) 412.42 Writing the Start of the Programme (Write-DownLoad-Segment request) Request 59/.0/ 1/16 /H'4E -31 - 30 - 20-58 - 30 - 20-59-30 - 0D - 0A - 4E - 32 - 30 - 20 - 58! where: + 59 ‘segment transfer request (byte) -0 category code (byte) -4 segment number (word) - 16 number of data bytes (word) = H4E-31-...-20-58' conversion of the first byte and part of the second to ASCII code "N10_X0_YOcrirN20_X" (byte string) Report 107 10/1 where: - 107 ‘segment transfer answer (oyte) - 0 request executed (byte) “1 ‘segment number (word) 0.938910 39— onum 412.43 REMARK Request 59/0/2/16/H2D -31- 34-30 - 0D - 0A- 4E - 33-30-20 - 59 - 2D - 36 - 30 - OD - OA’ where: 59 0 2 16 HisE - 32 - Report 107/ 0/2 where: 107 ° 2 41244 Request 60/0 where: 60 0 Report 108 / 0 where: 108 0 40 Writing the Next Part of the Programme (Write-DownLoad-Segment request) The programme was short enough to be loaded by a single Write-DownLoad- Segment request. It was divided only to make the example more complete. = 0D - 0A’ segment transfer request (byte) category code 5) segment number (word) number of data bytes (word) conversion of the end of the second block and all of the thitd to ASCII code "14 0caifN30_Y-60cnis (byte string) segment transfer answer (byte) request executed (byte) segment number (word) Closing the File (Close-DownLoad-Sequence request) on 9389140 file close request (byte) category code (byte) file close answer (byte) request executed (byte)Description of requests 4.13 File Upload Requests A file is uploaded as follows: + file opened by a first request (Open-Upload-Sequence) specifying the type and possibly the name of the file to be uploaded = reading of the file data by consecutive numbered Read-Upload-Segment requests = closing of the file by the last request (Close-Upload-Sequence), REMARKS A single fie (all types) or all the Ladder modules can be uploaded, Part programme type files for storages are automatically closed by the NC if the requester does not act within a timeout set by machine parameter P84 (see Parameter Manual). 4.13.1 Setting up an Upload Sequence Description The Open-Upload-Sequence request opens the file to be uploaded. Transmit Request Code / Category code / File identification [/Extension code / Filename] Request code 1 byte: 61 (H'3D') Category code 1 byte: 0 File identification 2 long words: [Type code 3 bytes: additional identification | Long word 1: file identification Long word 2: additional information File type to be uploaded Type code Additional Wentification _ Additional information byte 1 byte2___byte3___byted___long word 2 Aix calbration Oz not significant Tot significant Macros HOS not significant not significant Machine parameters ———— Hog net stenfeant reat sacs significant not significant PLC assembler binary HOS 0 o 0 not significant code PLC Ladder binary code Hor TeTST 0 Dets4 not significant 2:%TF 0 0 245 specific NUM request (byte) - 0 category code (byte) - 70 additional fle deletion request code (byte) - 1112000189" H'12': part programme type file for storage H1000189' = 441: indexed programme number —_(/ong word) Report 245 1118/0 where: = 245 specific NUM answer (byte) 118 additional file deletion answer code (byte) a0) request executed (byte) 48 en 9389140Description of requests 4.15 Reading the Number of Bytes Available in the RAM Description The Read-Memory-Free request is a specific NUM request that returns the number of bytes available inthe NC RAM. Transmission Request code / Category code / Additional request code Request code 1 byte: 245 (HFS) Category code 1 byte: 0 Additional request code 1 byte: 71 (H47) Reception Answer code / Additional answer code / Status / Data ‘Answer code 1 byte: 245 (HFS!) Additional answer code 1 byte: 119 (H77) Status 1 byte: see table below Sats Desorption Foo" request executed Hor request rejected, operaton in the programme area Data 1 long word: number of bytes available en 9389140 49— onum 4.16 NC Memory Directory Read Requests Reading the list of programmes present in the NC RAM begins by the Open-Directory request. The list of programmes is read by increasing numerical order. Ifthe listis too long to be completely contained in the answer, the rest can be readby the Directory request (this request can be used as many times as necessary to read the complete list) The Close-Directory request is used to close the read operation at any time before reaching the end of the list 4.16.1 Reading the Start of the List of Programmes Present in the NC RAM Description The Open: Directory request is a specific NUM request that returns the list of part programmes present in the NC RAM (or only part of the list i the list is too long to be contained completely in the answer: the list can contain a maximum of 15 programme names). Ifthe list is completely contained in the answer to the request, the operation is automatically closed and the Close- Directory request is unnecessary. Transmission Request code / Category code / Additional request code / Programme number Request code 1 byte: 245 (H'F5') Category code 1 byte: 0 ‘Additional request code 1 byte: 72 (H'48) Programme number 1 long word: programme number on which the list is to be started (programme number x 10 + axis group number). If no programme with this number exists, the list begins on the next higher number. Reception Answer code/Additional answer code/Status/Data ‘Answer code 1 byte: 245 (HFS) Additional answer code 1 byte: 120 (H'78) Status 1 byte: see table below Satus Description a request executed, data remaining to be wansmitted 2 request rejected, operation in the programme area: g request rejected, buffer too small 6 Tequest executed, no more data, read operation automatically closed Data String of long words (2 per programme) containing the list of programmes Programme number x 10 + axis group number Programme length in bytes l | | Long word 1 Long word 2 50 20938914704.16.2 Reading the Next Part of the List of Programmes Present in the NC Memory Description The Directory requestisa specificNUM requestwhich returns the next partof thelist of part programmesafteran Open- Directory request or a previous Directory request (the list can contain a maximum of 15 programme names). I the end of the list is included in the answer to the request, the operation is automatically closed and the Close- Directory request is unnecessary, Transmission Request code / Category code / Additional request code Request code 1 byte: 245 (HFS') Category code 1 byte: 0 Additional request code 1 byte: 73 (H'49') Reception Answer code/Additional answer code/Status/Data ‘Answer code 1 byte: 245 (HFS!) ‘Additional answer code 1 byte: 121 (H79') Status 1 byte: see table below Sats Desorption eS SN o request executed, data remaining to be Nansmilted z Tequest rejected, operation in the programme area g request rejected, buffer too small eB Tequest executed, no more data, read operation automatically closed. Data String of long words (2 per programme) containing the list of programmes. Programme number x 10 + axis group number | Programme length in bytes | Long word 1 Long word 2 en 9389140 51— onum 4.16.3 Closinga Directory Read Description The Close-Directory request is a specific NUM request used to close read of the list of part programmes. Transmission Request code / Category code / Additional request code Request code 1 byte: 245 (HFS) Category code 1 byte: 0 Additional request code 1 byte: 74 (H'4A') Reception Answer code / Additional answer code / Status ‘Answer code 1 byte: 245 (HFS!) ‘Additional answer code 1 byte: 122 (H7A’) Status 1 byte: see table below Sats Description a request executed a request rejected, operation already closed 52 en 93891400Description of requests 4.16.4 — Example of Directory Read Read the list of programmes %9xxx.x. 4.16.44 Open-Directory Request Request 245 10/72 / 441 where: = 245 specific NUM request (byte) - 0 category code (byte) - 72 additional open directory request code (byte) = 90.000 the list is to begin with programme %9000.0 (long word) Report 245 | 118 /0/ Data where: + 245 specific NUM answer (byte) = 120 additional open directory answer code (byte) - 0 request executed, data remaining to be transmitted(byte) = Data the consecutive data are the part programme numbers indexed by the axis group and the length in bytes of the programmes (long words) Attest is made on the last received programme number (programme number > 100,000) to determine whether all the 8x00 x programmes are included in the list. If not, a directory request must be made to continue reading the directory. 4.16.42 Reading the Next part of the Directory (Directory request) Request 245 1 0 / 73 where: - 245 ‘specific NUM request (byte) - 0 category code (byte) - 73 additional directory request code (byte) Report 245/121 /0/ Data where: = 245 specific NUM answer (byte) > 121 additional directory answer code (byte) - 0 request executed, data remaining to be transmitted(byte) = Data the consecutive data are the part programme numbers indexed by the axis group and the length in bytes of the programmes (long words) ‘testis made on the last received programme number (programme number > 100,000) to determine whether all the %69xxx.x programmes are included in the lst. Ifnot, a directory request must be made to continue reading the directory and so forth until the complete list has been read, 0.938940 53— onum 416.43 Close-Directory Request Read of status 0 after the last directory read request means that the directory has not been closed. Request 245 / 0/74 where: + 245 specific NUM request (byte) - 0 category code (byte) - 74 additional directory close request code (byte) Report 245 / 122 / 0/ Data where: + 245 specific NUM answer (byte) 122 additional close directory request code (byte) -0 request executed, directory closed (byte) 54 0 9389140Description of requests 4.17 Sending of Messages by the Supervisor Description The Write-Message request is a specific NUM request allowing the supervisor to send one to three lines of 32 alphanumeric characters. These messages are displayed on the receiver NC. Transmission Request code / Category code / Question code / Message index / Length / Data Request code 1 byte: 245 (HFS!) Category code 1 byte: 0 Question code 1 byte: 75 (H'4B}) Message index 1 byte: not significant on NUM 1060 Length 1 byte: 1 to 3 (number of message lines sent) Data Data bytes: ASCII character string (H'1F" < ASCII code < H'80° the characters ‘outside this interval are not displayable) including 32 bytes per message line. Reception Answer code/Additional answer code ‘Answer code 1 byte: 245 (HFS) Positive answer Additional answer code 1 byte: 254 (HFE’) Negative answer Additional answer code 1 byte: 253 (H'FD!) Cause of rejection: request unknown en 9389140 554.18 Stopping the PLC User Tasks Description The Stop request is a specific NUM request used to stop the PLC tasks. Transmission Request code/Category code/Additional request code/Spare Request code Category code ‘Additional request code Spare Reception ‘Answer code ‘Additional answer code Positive answer Status Negative answer Status 56 en 9389140 1 byte: 245 (H'FS') 1 byte: 0 1 byte: 76 (HAC) 1 byte: 0 Answer code/Additional answer code/Status 1 byte: 245 (H'FS') 1 byte: 124 (H7C’) 1 byte: 0 1 byte: 10 (PLC status incompatible)Description of requests 4.19 Initial ig the PLC Description The Init request is a specific NUM request used to initialise the PLC. Transmission Request code/Category code/Additional request code/nit type Request code 1 byte: 245 (H'F5') Category code 1 byte: 0 Additional request code 1 byte: 77 (H'4D') Init type 1 byte: see table below Intype Description a ‘complete ini i partalint 2 init Reception Answer code/Additional answer code/Status Answer code 1 byte: 245 (HFS) Additional answer code 1 byte: 125 (H7D') Positive answer Status 1 byte: 0 Negative answer Status 1 byte: 10 (PLC status incompatible) 0.938940 57— onum 4.20 Running The PLC User Tasks Description ‘The Run request is a specific NUM request used to run the PLC user tasks. Transmission Request code/Category code/Additional request code/Spare Request code 1 byte: 245 (H'FS') Category code 1 byte: 0 Additional request code 1 byte: 79 (H4F) Spare 1 byte: 0 Reception Answer code/Additional answer code/Status ‘Answer code 1 byte: 245 (HFS!) Additional answer code 1 byte: 127 (H7F) Positive answer Status 1 byte: 0 Negative answer Status 1 byte: 10 (PLC status incompatible) 58 en 93891405 Request Transmission by a Client Application Requests are sent and reports received by the client application of a NUM 1060 numerical control using two functions: = one requester function: Neto - one reception function: Net 5.1 Requester Func Description The Neto functions used to senda request oa distant station. The request is sent on one of the 16 source ports (H'50' to H'5F’) in the case of a master station or source port H’50' in the case of a slave station. Before using the Neto function, the request must be stored in a transmission buffer. This function is non-blocking. It can be used in a sequential task %TSO to %TS4. Several requests can exist simultaneously if they use different source ports, Transmission ‘Syntax in Ladder Language Neto (Source port, Buffer address) ‘Syntax in Assembler LOB Source port Store in accumulator B Lx@ Buffer address Store in index register X NETO Send the request Where Source port ‘Source port number (H'50' to H'SF or only H'50' for a slave). Butter address Address of the butfer containing the request to be sent Transmission Butter Structure ee ere > Butter size Buffer size 1 word: not significant Request size 1 word: request length in bytes SAUITE reqesi size (maximum 128) Line number Line number 1 word: + H20, H21", H'24'to H12B" Spare Network (UNI-TELWAY lines) - ~ H30' (MAPWAY or ETHWAY) Station Port + Ho! (ETHERNET) Module Channel Server address 6 bytes: > Spare: not significant = Network: network number ~ Station: station number UNL-TE request = Port: port number ~ Module: module number + Channel: channel number UNL-TE request Data: bytes, words or long words (maximum 128 bytes) in the request en 389140 a— onum Code returned after the request ‘Answer code 1 byte: see table below Answer code Deseription o Transmission OK i uffer too Ton 2 zero buffer Tengu 3 queue full_all buffers full a port number error 5 ‘option not valid for this request zs Tine number not valid 60 n- 9389140Request Transmission by a Client Application 5.2 Reception Function Description The Neti function is used to receive a report on a request sent earlier or unsolicited data. The answer is received on one of the 16 source ports (H'50' to H'SF') in the case of a master station or source port H’50’in the case of a slave station. Before using the Neti function, the reception buffer size must be specified, This function is non-blocking. It can be used in a sequential task %TSO to %TS4, Several requests can exist simultaneously if they use different source ports. Transmission Syntax in Ladder Language Neti (Source port, Buffer address) Syntax in Assembler LOB Source port Lx@_ Buffer address NET Where Source port Buffer address Reception Buffer Structure Buffer size Request size Line number Server address UNI-TE answer Store in accumulator B Store in index register X Send the request Source port number (H'50' to H'SF’or only H'50'for a slave) same number as the port used to send the request Address of the buffer to receive the answer. Buffer address 1 word: the size in byte specified by the user does not include the word «buffer size» 1 word: request size in bytes 1 word: + H20;,H21', H24 to H2B" (UNI-TELWAY lines) ~ _H’30' (MAPWAY or ETHWAY) + H440' (ETHERNET) 6 bytes: = Spare: not significant + Network: network number = Station: station number + Port: port number + Module: module number + Channel: channel number > Butfer size UNI-TE answer size Line number Spare Network Station Port Module Channel UNI-TE answer Data: bytes, words or long words (maximum 128 bytes) in the answer en 9380140 61— onum ‘Code Returned after the request Answer code 1 byte: see table below Hiswercode Desariion 0 read OK i pot aD aTor 3 Fa request TecaWved On WTS BO 7 Taff tos Smal to contain Wes NOTaT 8 Tine number not valid REMARK if the answer code is 6, the request must be repeated until the expected answer is received. 62 en. 9389140