MOBY -I/-L and M Identification System T3964R Driver

Transcription

1 MOBY -I/-L and M Identification System T3964R Driver Technical Description Release 2.96

2 Contents Page General Operation of the Driver Initialization Status Request Transmitting Data Receiving Data Switch the Driver Off Change Address and Interrupt Test Program Example Program Conditions of Use Warnings RD: 2/96

3 General The driver program runs on IBM compatible PCs under MS DOS. It uses the standard interface ports COM and/or COM 2. Should more interfaces using the 3964R protocol be required, the driver can through the additional hardware use interface ports COM 3 and/or COM 4. The driver works in accordance with the Siemens 3964R protocol. The exact protocol description can be taken from various Siemens descriptions. (e.g. Order no: E80850 A82 X A3). In its existing form the driver has only been tested with MOBY components. Parallel Operation of Several COM Interface Ports Several interface ports can be operated in parallel when you use the T3964R.EXE driver. The T3964R.EXE driver must then be loaded and started several times. You cannot operate several COM interface ports in parallel if you are using C calls. In this case, we recommend starting the driver separately as T3964R.EXE and not linking it as.obj. T3964R Driver in BASIC Environments: This T3964R driver is not designed for BASIC environments. If you do use this driver in a BASIC environment, the following restrictions apply. Call from BASIC interpreter: Call from program compiled in BASIC: Not available Only possible when BASIC is equipped with language elements for accessing the processor registers, and an INT call. New, starting 08/96: Interrupt no. and address can be configured as desired with function 6. Six interfaces can be operated in parallel. RD: 2/96 2

4 Three versions of this program are supplied: A) T3964R.EXE The driver is loaded before the start of the application software. It remains resident in memory and passes control back to the operating system. The connection between the user and the driver is established through a software interrupt. This interrupt can be defined through a parameter on the command line. Should no para meter be transferred, or should this parameter be incorrect, then the interrupt 62hex will be used. The driver can be loaded several times in this way. An example and test program written in TURBO PASCAL is included in the package (see Section 3). Call: T3964R Call interrupt: 62hex T3964R A2 A2hex Function number in AX: = = = = = Initialization Status request Transmitting data Receiving data Switching the driver off 6 = Change default setting of address and interrupt B) T3964S.OBJ Small linkable module for Microsoft C. C) T3964L.OBJ Large linkable module for Microsoft C. Calls to the driver functions for B) and C) are identical and are both described under B). The result of a function is always in the form of an integer, and corresponds to the AX value described under A) unless stated otherwise. The T3964.H module is included on the program floppy disk. You should include this module in your C program with the INCLUDE command. The transfer parameters to the driver are then automatically checked for plausibility during compilation, and Warnings output in case of errors. 3 RD: 2/96

5 2 Operation of the Driver 2. Initialization A) Input: AX = ES = segment address of string DI = offset address of string Init. String Pos. Length Code Stringlength Async. adapter no. ( to 4) 2 Baud rate 3 No of data bits (7 or 8) No of stop bits ( or 2) Parity (E or O or N) Master / slave (M or S) BCC checksum (Y or N) bin ASCII ASCII ASCII ASCII ASCII ASCII ASCII The string length is added automatically by PASCAL. It does not need to be taken into consideration by the programmer. 2 Adapter : Address 3F8H Interrupt 4 Adapter 2: Address 2F8H Interrupt 3 Adapter 3: Address 338H Interrupt 7 Adapter 4: Address 238H Interrupt 5 Adapter 5: Address 3E8H Interrupt 4 Adapter 6: Address 2E8H Interrupt 3 Address and interrupt can be changed before initialization with function 6. 3 Baud rate: = 50 Baud 2 = 300 Baud 3 = 600 Baud 4 = 200 Baud 5 = 2400 Baud 6 = 4800 Baud 7 = 9600 Baud 8 = 9200 Baud 4 When being used with MOBY this value should always be parameterized as Y. If an N is parameterized this procedure is no longer 3964R, but Operation: The current initialization setup of the serial module is saved. The module and the driver software are initialized, the error counters are cleared. Output: AX = 0 Init. OK. AX = Error in init. string. AX = 2 Hardware error. B) C Call: result = t39 init (char *init string): init string is the ASCII ZERO string and begins at position. The current initialization of the serial module is not saved. RD: 2/96 4

6 2.2 Status Request A) Input: AX = 2 Operation: The driver status and error statistics are returned. Output: AX: Bit 5 = Transmission error 2 Bit 4 = Timeout during transmission 2 Bit 3 Bit 2 Bit = Waiting for acknowledgement Bit 0 = Transmission active Bit 9 = Awaiting DLE after STX (Trx) Bit 8 = Ready for transmission 2 Bit 7 = Receive error 3 Bit 6 = Timeout during receive 3 Bit 5 = Port error Bit 4 = BCC error Bit 3 Bit 2 = Waiting for BCC Bit = Receive active Send status Receive status BX = Number of BCC errors (count from init. to FFFF hex) CX = Number of port status errors (as above) DX = Number of repeated transmissions (as above) SI = Number of received timeouts (as above) B) C Call: result = t39_stat (unsigned int*stat_array): stat_array is BX, CX, DX, SI See A) (output AX) for setup of result. Sending status and receiving status are updated separately. This means: Only the sending status is evaluated during sending data. Only the receiving status is evaluated during receiving data. 2 These bits should always be scanned during the sending status scan. 3 These bits should always be scanned during the receiving status scan. 5 RD: 2/96

7 2.3 Transmitting Data A) Input: AX = 3 ES = Segment address of string DI = Offset address of string String Stringlength* Data Pos. Length Code bin bin Operation: The transmission of data is started. Output: AX = 0 Transmission successful AX = Unable to transmit B) C Call: result = t39 write (int length, char *data_buffer): data_buffer is a string from position. 2.4 Receiving Data A) Input: AX = 4 ES = Segment address of string DI = Offset address of string String Stringlength* Data Pos. Length Code bin bin Operation: The received data are transferred. Output: AX = 0 Send data transferred correctly AX = No data available B) C Call: result = t39 read (char *data_buffer): data_buffer is a string from position. Result: >0 Number of bytes received =0 No data available After loading and initializing the driver, it is ready to receive. When the driver has correctly received a telegram, the received data are temporarily stored in the driver. Any telegrams arriving after this time will not be acknowledged or will be rejected. The user program must interrogate the receipt of data cyclically or on demand. It can be seen in the response to the user program if the driver has received data. * The string length is automatically added by PASCAL. The programmer does not need to consider it. RD: 2/96 6

8 2.5 Switch the Driver Off A) Input: AX = 5 Operation: All driver functions are broken off. The setup of the serial module saved at reset is restored. Output: B) C Call: t39 off (): The serial module is not reset. 2.6 Change Address and Interrupt A) Input: AX = 6 BX = Asynchronous adapter no. ( to 6) CX = Asynchronous adapter address DX = Asynchronous adapter interrupt no. (0 to 5) Operation: The call must be made before initialization. The transferred values for address and interrupt are assigned to the asynchronous adapter no. The standard values (cf. chapter 2.) are overwritten. Output: AX = 0 Address and interrupt changed AX = Parameter error B) C Call: result = t39_preset (int adapter, int adresse, int interrupt); 7 RD: 2/96

9 3 Test Program A small test program is included on the floppy disk. A test of the driver and the serial connections to the peripheral device is possible. The test program has an all purpose design. Characters are input/output via the keyboard as ASCII characters. Use command 6 (binary sending) to transfer a MOBY command to SIM (ASM 420/42/520). After calling the TEST.BAT program the following menu appears. Test 3964R Treiber. Init Initialize 2. Status Status 3. Senden Transmit 4. Empfang Receive 5. Aus Off 6. Senden (binär) Send (binary) 7. Ende End Function: Init String eingeben: 78OMY Com ; 9600 Baud; 8 Data Bits; Stop Bit; Odd parity; PC = master; 3964R Enter string Function: Status Calling Status will reset a driver error. Senden Empfang Transmit Receive BCC Fehler: 0 BCC Error Port Status Fehler: 0 Port Status Error Sendewiederholung: 0 Repeat Transmit Empfangstimeout: 0 Receive Timeout Function: Senden Transmit String eingeben: Enter a string This is a test text The string input and transmission takes place as ASCII text. Transmission is started after entry of. Function: Empfang Receive Error: No data is available; the driver received no data. RD: 2/96 8

10 Function: Aus End the 3964R driver Off OK: 0 Function: Senden (binär) Zeichen dezimal eingeben: Transmit (binary) Enter values in decimal The entry is concluded by two consecutive s, and the transmission is started. ABCD The ASCII values of the values sent are displayed here. OK: 0 Example: To read data from an MDS through a MOBY SIM The command reads: Read the next 6 bytes from MDS address 28. The following is transmitted to the SIM over the interface: With the Empfang (Receive) Function the data read can be collected and displayed. 9 RD: 2/96

11 4 Example Program #include <stdio.h> #include <conio.h> #include <string.h> #include <mem.h> #include t3964.h /* Header of the 3964R driver */ #define byte unsigned char /* Definition */ #define wort unsigned int /* Definition */ byte send_puf[250]; /* Sending buffer */ byte empf_puf[250]; /* Receiving buffer */ unsigned err[4]; /* Is required in this form by the driver */ byte string[]= these are data ; /* Write these data to the MDS */ /*================================================================================================= This is an example of the 3964R driver and a write command. The program was written in programming language C since OBJ files are only available in C. Components: PC and ASM 420. PC is master. Driver: 3964R Note: After compilation of the program, this must be linked with the T3964S.OBJ file (small) or the T3964L.OBJ file (large). ========================================================== */ unsigned int main() { wort fehler; /* Variable */ printf( \ninitialization of the driver\n ); t39_off(); /* If driver still loaded > switch off*/ fehler= t39_init( 78OMY ); /* CAUTION CAPITAL LETTERS */ /* COM,9600 baud,8 bits/character, stop,parity odd, PC is master, with BCC */ if(fehler!=0) { printf( Initialization incorrect > END!\n ); printf( Cause: %d\n,error);t39_off();return(0); } printf( Initialization > OK!\n\n ); /*- -Set up write command and issue */ send_puf[]=0x5; /* Write command without ECC */ send_puf[2]=0x00; /* Status always 0 Hex at start of command*/ send_puf[3]=0x00; /* From address MSB = 0 Hex */ send_puf[4]=0x00; /* From address LSB = 0 Hex */ send_puf[5]=0x0e; /* 4 bytes of string[] are to be written */ memmove(&(send_puf[6]),string,4); /* Add on user data and the complete command is then set up*/ send_puf[0]=5+4; /* Calculate AB. AB is the first byte of the command telegram. AB = user data + 5*/ printf( The data are now sent!\n ); fehler=t39_write((send_puf[0]+),send_puf); /* Send command */ if(fehler!=0) { printf( Error while issuing the command.end!\n );t39_off(); return(0); } do /* Wait till driver reports that command was issued */ { fehler=t39_stat(err); /* Fetch status */ } while( (fehler & 0x000)==0);/* until ready to send again */ if((fehler & 0x8000)!=0) {printf( Error during sending command. END!\n );t39_off();return(0);} printf( The data have been sent!\n ); /* Fetch command acknowledgement */ do /* Wait for acknowledgement */ { fehler=t39_stat(err); /* Fetch status */ } while( (fehler & 0x000)==0);/* until receiving data are available */ if((fehler & 0x0080)!=0) {printf( Error during receiving. END!\n );t39_off();return(0);} fehler=t39_read(empf_puf); /* Read in receiving data. The length in bytes is located in the error variable */ printf( Command acknowledgement was read\n ); /* È */ printf( The status byte is %x \n,empf_puf[2]); t39_off(); /* Turn off 3964R driver mandatory */ return(0); /* END */ } RD: 2/96 0

12 5 Conditions of Use The basis for use of the T3964R driver is the Contract for use of software products against a single fee from SIEMENS. The software contract is included with every driver. It is also contained on pages 2/4 ff of the ST50 catalog (997). The use of this driver is only permitted in connection with the MOBY system. RD: 2/96

13 6 Warnings RD: 2/96 2

14 Siemens AG Automation Technology Identification Systems Combination Technology PO Box 2355, D 9073 Fuerth Siemens Aktiengesellschaft Subject to change without prior notice Order No: Printed in the Fed. Rep. of Germany