Page 2
This product is not intended for use in life support appliances, devices or systems where a malfunction of the product can reasonably be expected to result in personal injury. Siemens AG customers using or selling this product for use in such applications do so at their own risk and agree to fully indemnify Siemens for any damages resulting from illegal use or resale.
TC3x Multiplexer User's Guide Contents Introduction..........................6 Supported product versions and related documents............6 References .......................... 6 Abbreviations........................7 Technical Requirements for system with PC Mux ..............8 System Software ......................... 8 PC Multiplexer Simulation Software ..................8 Hardware ..........................8 2.3.1 Using virtual COM Ports..................
Page 4
TC3x Multiplexer User's Guide Integrating the multiplexer into the customer application ............ 27 Tips and Tricks ........................27 7.1.1 Terminal Flow Control ..................27 7.1.2 Timeout after starting the multiplexer..............27 Restrictions........................27 Multiplexer control and signaling lines................28 7.3.1 Flow Control .......................
Page 5
TC3x Multiplexer User's Guide Figures Figure 1: Multiplexer architecture......................10 Figure 2: Example configuration of the COM Ports when using virtual COM Ports....... 12 Figure 3: Connection of the COM ports when using an 8 Port serial Card ..........12 Figure 4: Simcominstall Tool........................
The purpose of this document is to describe how to install, configure and use the multiplexer in the module as well as the Simulation of the multiplexer protocol (PC Mux) for Siemens TC3x GSM engines and to explain how to integrate the external multiplexer in your application.
TC3x Multiplexer User's Guide 1.3 Abbreviations Circuit Switched Data Clear to Send Data Carrier Detect DLCI Data Link Connection Identifier Developer Support Box Data Set Ready Data Terminal Ready Flow Control Flat Flex Cable GPRS General Packet Radio Service Global System of Mobile Communication Information Element Identifier Internet Protocol Mobile originated...
TC3x Multiplexer User's Guide 2 Technical Requirements for system with PC Mux 2.1 System Software • Windows NT4.0 This requirement only refers to PC Mux software which we provide for testing purposes. It has been developed for Windows NT 4.0. Of course the multiplexer protocol can be implemented in any OS. 2.2 PC Multiplexer Simulation Software In order to use the PC Mux, you get a *.zip file, which includes files to install the PC Multiplexer Simula- tion Program on your PC.
TC3x Multiplexer User's Guide 3 System Overview for the PC Mux The multiplex mode allows to communicate with the module over one serial interface simultaneously with 3 different customer applications (e.g. terminal programs). This is achieved by providing three vir- tual channels using a multiplexer (Mux).
TC3x Multiplexer User's Guide Table 1 shows which features are available on each channel. Table 1: Comparison of multiplexer channels Voice calls Data calls Phonebook incoming/outgoing incoming/outgoing incoming management commands /outgoing Channel 1 Channel 2, 3 indicates that the functionality is available on the channel indicates that the functionality is not available on the channel except for AT commands related to data Examples :...
TC3x Multiplexer User's Guide 4 Installation of the components for the PC Mux 4.1 Hardware Installation The following chapters describe the two different possibilities how to realize the physical connection from the application (PC) to the module. 4.1.1 Using virtual COM Ports Creating virtual COM ports avoids the installation of 7 COM ports (8 Port serial card) in your PC.
TC3x Multiplexer User's Guide Install the 7 COM ports (8 Port serial card) in your PC. Some systems may show problems and not all cards may be compatible with your system. The 8 Port serial card in your PC allows the usage of physical ports for the applications.
Page 14
TC3x Multiplexer User's Guide • Section CHANNEL0 This section contains the configuration of the physical COM port your DSB35 or TC35T is connected to. You may modify the selected Port and the Baud rate. When using all 3 virtual channels, we recommend you use a baud rate of 57600 bps (AT+IPR=57600<CR><LF>). Note : Autobauding must be turned off! Example for the physical channel:...
Page 15
TC3x Multiplexer User's Guide Example for the second logical channel: [CHANNEL2] ; type specifies the executable to start Type=PORT ; own server name Name=channel1 ; default destination [CONTROL] Destination=ctrl ; serial interface Port=COM25 Baud=57600 DataBits=8 ; parity: 0=no, 1=odd, 2=even, 3=mark, 4=space Parity=0 ;...
TC3x Multiplexer User's Guide 5 Using the PC Mux as external multiplexer The PC Mux simulates the multiplexer on a PC and can be used as an external multiplexer. However, this requires some configuration as described in the following chapters. Note : The usage of the multiplexer is not possible, when auto bauding (AT+IPR) has been activated.
TC3x Multiplexer User's Guide There are two ways to start the multiplexer: A. Follow the steps highlighted in Figure 7: • (1) Choose Enable Multiplexer from the Combo Box menu of the PC Mux window • (2) Click on the button Send •...
TC3x Multiplexer User's Guide Figure 9: Multiplexer Simulation status field description When PC Mux is in service, it disposes of the 4 COM Ports which have been defined in simulation.ini and no other application can use them. 5.2 Stopping the PC Mux To stop the multiplex mode, choose Disable Multiplexer from the Combo Box of the Multiplexer Simulation.
TC3x Multiplexer User's Guide 5.3 Additional buttons of the PC Mux In addition to the functions already described the PC Mux has a display and a trace possibility. With Enable Display/Disable Display the running Mux protocol can be displayed in the status win- dow.
TC3x Multiplexer User's Guide Figure 11: Multiplexer activation on Hyperterminal With AT+CMUX=0 the multiplexer has been activated. Now all terminals can be used. Figure 12 shows that all terminals are ready to process AT commands. TC3x_UG_01_V03.10 - Released Page 20/50 10.01.2002...
TC3x Multiplexer User's Guide Figure 12: Three active logical channels The Source Code for the Status messages of the PC Mux is available so that the message flow can be interpreted. TC3x_UG_01_V03.10 - Released Page 21/50 10.01.2002...
TC3x Multiplexer User's Guide are active. The data flow from the module's port now runs through the multiplexer (muxappl.exe and pcmux.dll), i.e. it does not go directly through the controller to the first PC port as in the disabled mode (again the red connection).
TC3x Multiplexer User's Guide void MP_Dummy_WriteCOM(unsigned int cnt, const char far *msg) This function is called by the multiplexer when it has finished framing one data package received from one of the logical channels ports and wants to send it out through the multiplexer port. MP_TransmitData Logical channels MP_Dummy_WriteCOM...
TC3x Multiplexer User's Guide 6.1.4 Chopper.exe Due to the limited memory of the module's hardware the multiplexer implementation can handle only smaller data packages (the frames for the different ports). For this reason the chopper.exe chops large incoming frames into blocks of maximum 100 bytes. This maximal frame size can be configured in the simulation.ini file (refer to chapter 6.2.1 ) 6.1.5 Muxtester.exe The muxtester.exe is an application only for debug and test reasons.
TC3x Multiplexer User's Guide 6.2.5 Trace.exe Because the PC multiplexer implementation is based on several connected but separated applications the trace information for the debug traces must be collected out of several trace files created by the various modules. Trace.exe does this collecting by opening several trace files, searching cyclically for new information, sorting the found trace information and writing it altogether to a file which then contains the trace output of the whole system as a formatted text.
TC3x Multiplexer User's Guide 7 Integrating the multiplexer into the customer application If you want to make your own design of the multiplexer, you may use the delivered sources. You get a *.zip file, which includes files you can use to include the multiplexer in your application. Naturally you may instead make your own implementation of the multiplexer.
TC3x Multiplexer User's Guide • A call can be answered or ended on every channel. See AT commands like ATD, ATA, ATH. • The PC Mux environment can only be started once on a PC. • XON/XOFF are not allowed in the multiplex mode (AT\Q2). •...
TC3x Multiplexer User's Guide 7.3.1 Flow Control RTS/CTS on the physical channel: It is recommended to use AT\Q3 when the multiplexer is switched on. The customer application de- and encodes the data. It needs to respect the flow control given by the MP.
TC3x Multiplexer User's Guide Note 1: It must be taken into account, that a call can only be accepted once. So some kind of mutual locking mechanism must be realized. Note 2: See also chapter 7.1.1 for terminal flow control problem. 7.3.2 Escape Sequence When the MP is active only coded data is transmitted over the UART.
TC3x Multiplexer User's Guide 8 Structure of the multiplexer protocol 8.1 Introduction of the multiplexer protocol The multiplexer protocol conforms with the multiplexer protocol GSM 07.10. The non-error recovery mode was implemented with the basic option. The frames have a start and a stop byte. A checksum is calculated to protect the transferred data. Frame repetition is not enabled.
TC3x Multiplexer User's Guide 8.2.1 Flag sequence Each frame begins and ends with a flag sequence. The flag sequence contains a bit sequence: 11111001 (hexadecimal: 0xF9). Only one flag sequence occurs between any two frames. If two successive flag sequences do occur, the frame is regarded as being empty and is discarded.
TC3x Multiplexer User's Guide 8.2.3 Control field The control field defines the frame type. Table 8: Coding of the control field Frame Type SABM (Set Asynchronous Balanced Mode) (Unnumbered Acknowledgement) (Disconnected Mode) DISC (Disconnect) (Unnumbered Information with Header check) P/F: Poll/Final bit Commands: P = 1, Responses: F = 1 For each DLCI, only one frame with P = 1 may ever be expected.
TC3x Multiplexer User's Guide 8.3 State Diagrams The multiplexer protocol is based on two state machines (see Figure 16). One state machine initiates the setup of the logical channels, while the other responds to the requests. The TC3x can only respond to requests. A higher level for controlling the state machines is not implemented.
TC3x Multiplexer User's Guide 8.3.2 DLC Establishment The multiplexer control channel must be set up as the first channel followed by all other DLCIs. To do so, a SABM frame (see Section 8.2.3) must be sent to the TC3x. The TC3x responds with either a UA frame –...
TC3x Multiplexer User's Guide 8.3.5 Closedown After the close down procedure both stations return to operation in the AT command mode. The following options exists for the close down procedure: Disconnect all DLCIs (DLCI Command); the last disconnection is for DLCI = 0 Multiplexer close down command (CLD).
TC3x Multiplexer User's Guide 8.3.6.2 Test command (Test) The test command is intended to test the connection between MS and TE. Type field: Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 Bit 8 The length byte indicates the number of test bytes sent in the value bytes. The responding station should respond with precisely the same bit sequence.
TC3x Multiplexer User's Guide Note: This command supports no parameters. Instead we use this optional parameter to transport an escape sequence detection from the host to the module. If the hosts detects an escape sequence (usually +++), it sends this optional octet with bit 1 set to 1. The module calls its original escape sequence. 8.3.6.4 Non-supported command response (NSC) This response is sent whenever a command type is not supported by the receiving entity.
In these cases the version number is increased. When using the multiplexer protocol sources delivered by Siemens AG, the version check is included implicitly. When you implement the multiplexer protocol yourself, you need to implement the version check as well, if you want to use features which are included in later versions.
Siemens AG sources. This case should not happen, since the customer application is put into service with the features which are being offered by Siemens AG at that point of time. New protocol features can only be contacted by the application when they have been implemented on the MS side.
TC3x Multiplexer User's Guide same version shall be used. If there is a mismatch between the entities the earlier internal version is used. From multiplexer version 2 onwards, the version check is automatically executed during the start up procedure (at+cmux=0). Version 2 is the first version with multiplexer version check. The version check procedure is triggered by the TE side by sending the Test Request Message with the multiplexer version number.
TC3x Multiplexer User's Guide <Message flow case (01)> - AT+CMUX=0 enable DLC (DLCI=0) enable DLC (DLCI=1) enable DLC (DLCI=2) enable DLC (DLCI=3) No version check takes place ! 9.4.2 Description Case (02) For Case (02) only on TE side software with version check is installed. The Test Command Message is sent back from the MS side but no Test Message with the MS multiplexer version is triggered.
TC3x Multiplexer User's Guide <Message Flow Case (02)> - AT+CMUX=0 enable DLC (DLCI=0..3) UIH TestCommand (P=0, C/R=1, TEMUX_Version) UIH TestCommand_Resp (P=0, C/R=0, TEMUX_Version) <no Test Command with MS multiplexer version is triggered > - The lowest multiplexer version is used on TE side 9.4.3 Description Case (03) In this case the software version number on both sides is equal.
TC3x Multiplexer User's Guide 9.4.4 Description Case (04) There is a version conflict – the lowest internal version is used. <Message Flow Case (04)> - AT+CMUX=0 enable DLC (DLCI=0..3) - Version check UIH TestCommand (P=0, C/R=1, TEMUX_VersionX) UIH TestCommand_Resp (P=0, C/R=0, TEMUX_VersionX) UIH TestCommand (P=0, C/R=1, MSMUX_VersionY) UIH TestCommand_Resp...
F9 03 EF 25 23 21 08 4D 53 4D 55 58 56 45 52 53 49 4F 4E 32 00 00 9.5.1 Coding of “TestCommand” message The coding of the multiplexer stack version is used specifically for SIEMENS equipment and is not defined in ETSI standards. The IEI values defined for the verification pattern of the “TestCommand”...
TC3x Multiplexer User's Guide 9.5.2 Example of “TestCommand” message An example for coding a “TestCommand” message is illustrated in Table 11. Table 11: Coding of “TestCommand” (Example) IEI coding Information element name 8 7 6 5 4 3 2 1 0x 1 0 0 1 1 1 1 1 F9 START Flag Address Field DLCI=0,C/R=0,EA=0...