Go to page of
Similar user manuals
-
Cell Phone
Siemens A56
11 pages 0.1 mb -
Cell Phone
Siemens SF65
71 pages 1.38 mb -
Cell Phone
Siemens 300E
48 pages 0.39 mb -
Cell Phone
Siemens S42
44 pages 1.35 mb -
Cell Phone
Siemens A35
43 pages 1.26 mb -
Cell Phone
Siemens 150 E, 150 H
66 pages 0.89 mb -
Cell Phone
Siemens XT55
20 pages 1.82 mb -
Cell Phone
Siemens Gigaset S1
110 pages 2.05 mb
A good user manual
The rules should oblige the seller to give the purchaser an operating instrucion of Siemens Mux_guide_v06, along with an item. The lack of an instruction or false information given to customer shall constitute grounds to apply for a complaint because of nonconformity of goods with the contract. In accordance with the law, a customer can receive an instruction in non-paper form; lately graphic and electronic forms of the manuals, as well as instructional videos have been majorly used. A necessary precondition for this is the unmistakable, legible character of an instruction.
What is an instruction?
The term originates from the Latin word „instructio”, which means organizing. Therefore, in an instruction of Siemens Mux_guide_v06 one could find a process description. An instruction's purpose is to teach, to ease the start-up and an item's use or performance of certain activities. An instruction is a compilation of information about an item/a service, it is a clue.
Unfortunately, only a few customers devote their time to read an instruction of Siemens Mux_guide_v06. A good user manual introduces us to a number of additional functionalities of the purchased item, and also helps us to avoid the formation of most of the defects.
What should a perfect user manual contain?
First and foremost, an user manual of Siemens Mux_guide_v06 should contain:
- informations concerning technical data of Siemens Mux_guide_v06
- name of the manufacturer and a year of construction of the Siemens Mux_guide_v06 item
- rules of operation, control and maintenance of the Siemens Mux_guide_v06 item
- safety signs and mark certificates which confirm compatibility with appropriate standards
Why don't we read the manuals?
Usually it results from the lack of time and certainty about functionalities of purchased items. Unfortunately, networking and start-up of Siemens Mux_guide_v06 alone are not enough. An instruction contains a number of clues concerning respective functionalities, safety rules, maintenance methods (what means should be used), eventual defects of Siemens Mux_guide_v06, and methods of problem resolution. Eventually, when one still can't find the answer to his problems, he will be directed to the Siemens service. Lately animated manuals and instructional videos are quite popular among customers. These kinds of user manuals are effective; they assure that a customer will familiarize himself with the whole material, and won't skip complicated, technical information of Siemens Mux_guide_v06.
Why one should read the manuals?
It is mostly in the manuals where we will find the details concerning construction and possibility of the Siemens Mux_guide_v06 item, and its use of respective accessory, as well as information concerning all the functions and facilities.
After a successful purchase of an item one should find a moment and get to know with every part of an instruction. Currently the manuals are carefully prearranged and translated, so they could be fully understood by its users. The manuals will serve as an informational aid.
Table of contents for the manual
-
Page 1
User’s Guide Multiplexer User's Guide Siemens Cellular Engines Version: 06 DocID: Mux_guide_v06[...]
-
Page 2
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 2 of 36 30.06.2004 Document Name: Multiplexer User's Guide Version: 06 Date: June 30, 2004 DocId: Mux_guide_v06 Status: Confidential / Released General notes Product is deemed accepted by Recipient and is provided without interface to Recipient’s products.[...]
-
Page 3
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 3 of 36 30.06.2004 Contents 0 Document history.......................................................................................................... 5 1 Introduction .............................................................................................[...]
-
Page 4
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 4 of 36 30.06.2004 5 Multiplexer protocol version control ......................................................................... 33 5.1 Introduction .......................................................................................................... 33 5[...]
-
Page 5
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 5 of 36 30.06.2004 0 Document history This chapter reports modifications and improv ements over previous versions of this document. Preceding document: “Multiplexer User's Guide” Version 05 New document: “Multiplexer User's Guide” Version 06 Cha[...]
-
Page 6
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 6 of 36 30.06.2004 1 Introduction Siemens GSM engines support the basic option of the multiplexer according to the ETSI TS 101 369, GSM 07.10 Multiplexer Protocol. This allows a mobile to run a triple session over a serial link interface. Outside the GSM engine, [...]
-
Page 7
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 7 of 36 30.06.2004 1.1 Supported products and related documents Supported products • AC43 • AC45 • MC35i • MC35i Terminal • MC39i • MC45 • MC46 • MC388 • MC5x • TC35i • TC35i Terminal • TC45 • XT55 Related documents [1] Hardware Interfac[...]
-
Page 8
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 8 of 36 30.06.2004 1.3 Term and abbreviations Abbreviation Description CSD Circuit Switched Data CTS Clear to Send DCD Data Carrier Detect DLCI Data Link Control Identifier DSB Developer Support Box DSR Data Set Ready DTR Data Terminal Ready FC Flow Control FFC F[...]
-
Page 9
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 9 of 36 30.06.2004 2 Multiplexer protocol – an overview 2.1 Product concept and architecture The multiplexer mode enables one serial interface to transmit data to three different custo- mer applications. This is achieved by providing three virtual channels usin[...]
-
Page 10
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 10 of 36 30.06.2004 2.2 Virtual channels and AT commands Please note that a cellular engine designed for multiplex operation does not include three different devices. Only one single air interface (RF part) is available. As mentioned before the multiplexer enable[...]
-
Page 11
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 11 of 36 30.06.2004 3 Integrating multiplexer into the customer application When designing a multiplexer application, you can create your own sources or take advantage of the sources delivered upon reques t by Siemens. The Siemens sources are packed in a *.zip fi[...]
-
Page 12
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 12 of 36 30.06.2004 3.1.3 Dependencies between multiplexer channels and restrictions of use When using the following functions, be aware of possible dependencies between the different channels. One way of avoiding problems may be to dedicate certain commands/feat[...]
-
Page 13
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 13 of 36 30.06.2004 3.1.5 Timing conditions Switching on the multiplexer with AT+CMUX=0 causes a 5s timer to start. If the multiplexer control channel is not established within this time, the module returns to “normal AT command mode” without multiplexer. Thi[...]
-
Page 14
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 14 of 36 30.06.2004 3.2 Multiplexer control and signaling lines The following chapter covers all information you need to develop and set up a virtual driver. Differences and restrictions in comparison to the unframed module are pointed out. 3.2.1 Flow control Log[...]
-
Page 15
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 15 of 36 30.06.2004 RTS/CTS on the logical channels The customer application needs to regulate the data flow according to the logical flow control. The implementation of the WinMux 2k is a good example. It maps the 3 decoded channels to 3 serial interfaces as wel[...]
-
Page 16
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 16 of 36 30.06.2004 3.2.2 Escape sequence When the multiplexer protocol is active only coded data is transmitted over the UART. The coding includes a header and a checksum. Therefore, the direct parsing of this sequence is not possible. An escape might be undetec[...]
-
Page 17
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 17 of 36 30.06.2004 Addre ss 1 Octet Control 1 Octet Flag 1 Octet 0xF9 DLCI DLCI: Data Link Connection Identifier C/R: Command / Response EA: extension bit; EA = 1 Frame ty pe: SABM Set Asynchr onous Balanced Mode UA Unnumbered Acknowledgement DM Disconnected Mod[...]
-
Page 18
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 18 of 36 30.06.2004 4.2.1 Flag sequence A flag sequence is a specific bit pattern (usually 11111001; hexadecimal: 0xF9) used to mark the beginning and the end of a frame of data. Each frame begins and ends with a flag sequence. Only one flag sequence occurs betwe[...]
-
Page 19
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 19 of 36 30.06.2004 4.2.3 Control field The control field contains control information to define the frame. Frame Type 1 2 3 4 5 6 7 8 SABM (set asynchronous balanced mode) 1 1 1 1 P/F 1 0 0 UA (unnumbered acknowledgement) 1 1 0 0 P/F 1 1 0 DM (disconnected mode)[...]
-
Page 20
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 20 of 36 30.06.2004 4.2.4 Length indicator The length indicator specifies the length of the following information field. As the maximum frame size N1 is 98 bytes and cannot be changed the E/A bit is always 1. The setting E/A = 0 defined in GSM 07.10 for a frame s[...]
-
Page 21
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 21 of 36 30.06.2004 4.3 State diagrams The multiplexer protocol is based on two state machines (see Figure 4). One state machine initiates the setup of the logical channels, the other one responds to the requests. The GSM engine can only respond to requests. A hi[...]
-
Page 22
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 22 of 36 30.06.2004 Figure 4: Relationship between the customer µC and the GSM engine µC DI S- CONNECT ED DI S- CONNECTED- NEGOT I AT I ON CONNECT ED CLOSED- DOW N St a r t Up DLC Establ i shment Close Down Close Down Cl ose Do wn DLC parameter negoti ati on DL[...]
-
Page 23
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 23 of 36 30.06.2004 Cus t omer µC GSM e n gi n e µC Clos ed Dow n Cl o se d Do wn Request St art Up ResponseSt ar t Up Con f i r mS t ar t Up In d ica ti o nS ta rtU p Dis connec te d Dis connec t ed Ser i a l inte rfa c e Start Up "AT+CM UX" Connect [...]
-
Page 24
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 24 of 36 30.06.2004 C ustom er µC G SM engi ne µC Dis connect ed Di sc onnect ed Ser i a l i nt e r f a ce DLC Release Connect ed Connect ed Request DI SC I ndi cat i o nD I SC Res p on s eUA Con f i r mUA Re quest C l oseDo w n I ndi cat i onCl oseDow n R e sp[...]
-
Page 25
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 25 of 36 30.06.2004 4.3.1 Start-up procedure The only approach to activate the multiplexer protocol is entering the appropriate AT command AT+CMUX=0. This enables the multiplexer control channel. The next step is to set up the multiplexer control channel as descr[...]
-
Page 26
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 26 of 36 30.06.2004 4.3.4 DLC release No provision is made to repeat the request if no response is received. Customer µC GSM engine DISC: P = 1 UA: F = 1 DM : F = 1 respondi ng s t ati on i s al ready disconnect ed Figure 9: DLC release 4.3.5 Close-down procedur[...]
-
Page 27
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 27 of 36 30.06.2004 Length field: Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 Bit 8 EA L1 L2 L3 L4 L5 L6 L7 EA bit: Extension bit. In t he last octet of the sequence the EA bit = 1, otherw ise = 0. If there is only one octet, EA bit = 1 is set. L-bits: Number of va[...]
-
Page 28
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 28 of 36 30.06.2004 4.3.9 Modem status command (MSC) The Modem Status Command is used for software flow control. Comman d 1 octet Length 1 octet DLCI 1 octet V.24 signals 1 octet Break Signals (optional) 1 octet Command: Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 [...]
-
Page 29
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 29 of 36 30.06.2004 Note: The mappings are valid for version 3 and an MSC request only. Descriptions of all other versions are available in Chapter 5. The response to any MSC must be always the same data already sent. Please keep in mind that it is impossible to [...]
-
Page 30
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 30 of 36 30.06.2004 4.3.10 Power saving control (PSC) The power saving control message uses the following type field octet: Type: Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 Bit 8 1 C/R 0 0 0 0 1 0 C/R bit: Indicates whether the sequence is a command or a response.[...]
-
Page 31
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 31 of 36 30.06.2004 No Value octet (Length=0) Switches into SLEEP mode, like AT+CFUN=0 Note: According to the GSM 07.10 standard PSC supports no value octets. The optional value octet was added to increase flexibility. Developed as a substitute to the AT+CFUN com[...]
-
Page 32
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 32 of 36 30.06.2004 4.4 Example: Establishing logical channels without parameter negotiation • Send AT+CMUX=0; wait for the response • Send Request SABM for DLCI = 0; wait for the response • Send Request SABM for all requested DLCIs; wait for the response A[...]
-
Page 33
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 33 of 36 30.06.2004 5 Multiplexer protocol version control 5.1 Introduction The multiplexer protocol offers a version control to ensure that TE and MS support the same extent of functionality and to maintain upward and downward compatibility when later firmware v[...]
-
Page 34
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 34 of 36 30.06.2004 5.2 Multiplexer protocol versions This section summarizes the differences of the existing multiplexer protocol versions. 1. No version check • No break signal is sent 2. First version including the version check • Additional features: Tran[...]
-
Page 35
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 35 of 36 30.06.2004 5.3 Implementing version control The TE initiates the version check by sending the Test command via the multiplexer control channel DLCI 0 (with TEMUX_Version). As specified in the GSM recommendation 07.10 (chapter 5.4.6.3.4) the opposite enti[...]
-
Page 36
Multiplexer User's Guide Confidential / Released s m o b i l e Mux_guide_v06 Page 36 of 36 30.06.2004 5.3.2 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”[...]