Siemens 7 User's Manual
Contents
1. Signal Description RING Received with Modem Status Command DCD Received with Modem Status Command DSR Received with Modem Status Command DTR Set by user sent with Modem Status Command initialized with 1 CTS Received with Modem Status Command RTS Set by user Send with Modem Status Command initialized with 1 2 5 Limitation of Virtual Ports Flow control can be set to RTS CTS or DSR DTR XON XOFF flow control is not supported Hardware flow con trol on the virtual COM ports is handled internally by the Multiplexer Protocol The WinMux2k driver handles neither modem nor serenum IO control requests The WinMux2k driver supports only 8 data bits no parity and one stop bit The function IOCTL SERIAL XOFF COUNTER is not supported The following functions return success but have no effect at all e OCTL SERIAL SET BREAK ON e OCTL SERIAL SET BREAK OFF e OCTL SERIAL SET XOFF e OCTL SERIAL SET XON e OCTL SERIAL RESET DEVICE Virtual ports accept any baud rate though the changed setting will be ignored Calling the function Open to a virtual port can take up to 40 seconds It fails if the module is not connected Mux Drv DevGuide v07 Page 14 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide 2 6 Module Initializing Sequence 2 6 Module Initializing Sequence SIEMENS Due to different requirements of the supported products the initialization sequence varies with t2. Mux Drv DevGuide v07 Page 23 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide 4 2 Settings Stored in the Windows Registry SI E M ENS The following Registry values in the path HKLM System CurrentControlSet Services winmux2k Parameters are used to configure the TRACE out puts These values are only valid for the debug version of the device driver Table 7 Registry values for trace outputs Values Data Example Properties DebugBaud 57600 Baud rate used if DebugPort is different from 0 DebugMask 0x0000003 DebugMask determine which reports from the device driver are printed to the DebugPort Masks 0x0000001 Errors 0x0000002 Warnings 0x0000004 Information s 0x0000008 PnP 0x0000010 Power management 0x0000020 Data control commands 0x0000040 Open Close Cleanup 0x0000080 Dispatch Device Control 0x0000100 Dispatch Read Write 0x0000200 Submit control requests 0x0004000 framed data read write 0x0008000 frequently traces submit wrsupport The mask 0x7 means that all three traces are on The next masks are only for driver checks and represent internal variables and states of the serial Multiplexer Device driver 0x0001 0000 Frame information send and receive 0x0002 0000 Frame information HDLC 0x0004 0000 Status information from virtual channels 0x0008 0000 Status information from Multiplexer control channel 0x0010 0000 Output Names from WinMux2k functions 0x1000 0000
3. SIEMENS 4 2 Settings Stored in the Windows Registry The WinMux2k driver parameters are located in the registry path HKLM System CurrentControlSet Enum Root winmux 000X Device Parameters X is the number of the device instance All values listed below will be created during the installation of the WinMux2k driver The settings are provided by the winmux2k inf file If you want to write your own preferences to the Registry you can edit the inf file before installing the driver Table 6 Registry values Value Data Example Properties BasePort COM1 The physical serial port that connects the module to the PC BaudRate 115200 Baud rate used on the physical port BaudRateString AT IPR 115200 This string is used to set the module to the given baud rate Note This string must contain the same value as the BaudRate value If you select a higher baud rate be sure it is supported by the module For details see 3 ModemInit AT This multi string value contains several AT commands AT amp SO which are used to switch the module to multiplexer mode AT Q3 Possible ERROR codes resulting from unsupported com AT ICF 3 mands are ignored by the WinMux2k initialization sequence AT CMUX 0 RequestTimeout 2000 Timeout value used only during the initialization of the mod ule 2000 is the maximum number of milliseconds the mod ule can take to respond to AT requests VirtPort1 COM10 Name of the first virtual po
4. Furthermore all safety instructions regarding the use of mobile technical systems including GSM products which also apply to cellular phones must be followed Siemens or its suppliers shall regardless of any legal the ory upon which the claim is based not be liable for any consequential incidental direct indirect punitive or other damages whatsoever including without limitation damages for loss of business profits business interruption loss of business information or data or other pecuniary loss arising out the use of or inability to use the docu mentation and or product even if Siemens has been advised of the possibility of such damages The foregoing limitations of liability shall not apply in case of mandatory liability e g under the German Product Liability Act in case of intent gross negligence injury of life body or health or breach of a condition which goes to the root of the contract However claims for damages arising from a breach of a condition which goes to the root of the contract shall be limited to the foreseeable damage which is intrinsic to the contract unless caused by intent or gross negligence or based on liability for injury of life body or health The above provision does not imply a change on the burden of proof to the detriment of the recipient Subject to change without notice at any time The interpretation of this general note shall be governed and construed according to German law without reference to
5. last virtual port is closed The following sections describe the behavior of the software in these three cases The commands sent to the module are taken from the Registry values PowerDown for PC suspend ClosePort for closing the last virtual port and ShutDown for a shut down of the PC These values are copied from the winmux2k inf file into the Registry during installation of the driver For further details on the Registry values see below and Section 4 2 2 8 1 Power Down on PC Suspend When the PC enters the suspend mode the module stays in multiplexer mode A virtual channel is activated and used to send the commands from the Registry value PowerDown or via the PowerDownFrame available from Multiplexer Protocol version 3 onwards All pending send requests are stopped When the PC wakes up the module gets an RTS impulse and the pending send buffers are re enabled 2 8 2 Power Down after Closing the Last Port When the last virtual port is closed the module switches from multiplexer mode to normal AT command mode This is accomplished by sending the strings of the Registry value ClosePort to the module AT IPR 0 and depending on the product AT SMSO If the module is switched off with AT SMSO the driver waits for the DSR signal to go low after switch off Oth erwise reopening a virtual port may fail because the module hasn t finished its shutdown procedure This behav ior is supported by Multiplexer Protocol v
6. Choose Uninstall Driver and answer the confirm dialog with yes to finally uninstall the driver oa fF ORN Windows XP new desktop not the classic desktop Start the Control Panel Under Performance and Maintenance select System Select the Hardware property sheet Double click the Device Manager button Under Multi port serial adapters right click Serial Multiplexer Choose Uninstall Driver and select Yes from the Confirm File Deletion dialog oa fF QON Mux_Drv_DevGuide_v07 Page 19 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide SIEMENS 4 Device Settings and Properties 4 Device Settings and Properties 4 1 Settings on the Serial Multiplexer Properties Page From the Serial Multiplexer Properties page see Section 3 3 for details where to find the page select the Port Settings tab The baud rate used on the physical serial port can be changed individually Serial Multiplexer COM3 Properties p 32 x General PortSettings Driver r Physical Serial Modem Port Modem Port Name cows Baud Rate bps 115200 Virtual Serial Modem Ports Virtual Parts Virtual Port 1 data channel z Virtual Port 2 cout 2 Virtual Port 3 cow OK Cancel Figure 2 Serial Multiplexer Properties page Mux Drv DevGuide v07 Page 20 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide 4 2 Settings Stored in the Windows Registry
7. Figure 2 Serial Multiplexer Properties Page ccescecceeeceeseeeeeeeeeeeeaeeeseeeeceaaeseeaaeeseaeeeeaaeesseneeeeaeeseeneeees 20 Figure 3 Interaction of the different driver objects sssseeeeennenen nennen 27 Figure 4 State diagram of the internal driver states sssssssssssssseeeeeenenenene enn 28 Figure 5 Driver internal buffer handling essen ennemis 29 Figure 6 Block flow diagram for data received by the module seen 30 Figure 7 Block flow diagram for data sent to the module via a virtual port sseeeesssssss 31 Figure 8 SerM xSend f liction eo t ee e tO ERE ena tna b ce EU E tee baise esta 32 Figure 9 Send function from the virtual communication ports sssssssssseeeeeneeen 33 Figure 10 State diagram of the 4 parser sssssssssssssssssssseeeeeen nennen nennen tenens nnne nennen 34 Mux Drv DevGuide v07 Page 6 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide SIEMENS 0 Document History 0 Document History Preceding document Multiplexer Driver Developer s Guide Version 06 New document Multiplexer Driver Developer s Guide Version 07 Chapter What is new 1 1 Enhanced list of supported products 4 2 Table 6 Added optional Registry values supported as of Multiplexer Protocol version 4 Table 7 Added value 0x0002 0000 Frame informat
8. Multiplexer Driver Developer s Guide SIEMENS 8 Known Problems 8 Known Problems 8 1 Booting Operating System Windows 2000 and Windows XP toggle the signals of the serial interfaces As a result the module will be switched on even if the WinMux2 driver is not active The driver accesses the connected module only when the virtual ports are accessed If the WinMux2k driver is used by accessing one or more of the virtual ports it switches off the module when the last virtual port is closed again Only TC45 and XC18 do not switch off in this case 8 2 Shutdown of the Operating System If the supported operating system has been installed in ACPI mode the power supply will be automatically switched off This power down might cause pulses on those signals of the serial interfaces which are responsible for switching the module on This may happen even if it had correctly switched off before by the driver If the module has its own power supply it might stay switched on after the shutdown procedure of the computer has completed 8 3 Standby of the Operating System If the operating system has been installed in ACPI mode it supports improved power management by also send ing computer components into suspend mode The serial WinMux2k driver supports this power management by switching the module into standby mode if the driver is in use by accessing one or more of the virtual ports If the operating system has been properly configured togethe
9. Re initialization eee ted en De ee un eda ata tes 16 2 9 wPowerDOWLD etti dete ide i eb guia 16 2 8 1 Power Down on PC Suspend sse nennen enne nennen nennen ns 16 2 8 2 Power Down after Closing the Last Port 16 2 8 3 Power Down on PC Shutdown sssssssssssseseseeeene nennen ennt 17 3 ECL EL m 18 3 1 Files Required for WinMux2k Driver Installation seeem m 18 3 2 Installing the WinMux2k Driver ses eraa ENEE AE EI nennen nemen nennen ennemi nn en nne nn nnns 18 23 I Deinstalling the DrVer uc eicit et erect ponant iet eta ER eivai 19 4 Device Settings and Properties leeeeeeeeeeeiseesiseeeeeees eee enn nennen nannte nnn nass nnn a nunne nunne nnmnnn nnn 20 4 1 Settings on the Serial Multiplexer Properties Page ssssseseneneeeennnn 20 4 2 Settings Stored in the Windows Registry sssssssssssssseeseneneneeee nennen nnne 21 5 Settings for Applicatioris cette eee acta itte eaa aa ra eae Sp Oae e tecta ra retine enter inna crien 25 5 1 Dial up Network Settings ioco eden eese er redes egt eo dese peed Rae ERE hd ranae 25 5i2 JFaxSeltihgs uen ne a Hee E rure vedi doge ue ee aee Eb eee XE Cod age eae Dae 25 6 Translate Source COode coeant aaa aaa eI sae Aasna na none sonam mea iaoiai sisitan 26 6 1 Software Requiremients iae ime ettet ge eset edet
10. WrConnectPort send aSABM Frame STATE DISCONNECT REQUEST rcv a DM Disconnect Frame STATE CONNECT REQUEST WrConnectPort send a SABM Frame WrDisconnectPort send a DISC Frame STATE VERSION ERROR this state exists only for port 0 rcv a TEST command with a VERSION Controlbyte STATE_ VERSION __ REQUEST this state exists only for port 0 not correct Version Versionstring from MS and TS Version are identical S for Ports other than port 0 EN receive a UA Frame for the desired port Figure 4 State diagram of the internal driver states Mux Drv DevGuide v07 Page 28 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide 7 3 Buffer Handling 7 3 Buffer Handling SerMux SerPortN Mulitplexer Control Port 0 Channel number Priority with MaxSequence Timeouts Request Timeouts and Scanning Timeouts Statistics V24 Status from itself and the Modem Handshake Status Current Read and Write Status Circular Buffer Params ScanSendRequest Send RCV Queue Queue Requests Requests Circular Circular buffer buffer Send RCV ConfirmCommand Buffer if receive a Control Command Special control functions Circular buffer EstablishDLC Send ReleaseDLC CloseDown CommandBuffer SetModemStatus SendVersionCommand GetFrameBufferPortO SerPortOIndicateFrame Timer functions WrTimer OnTimerS
11. driver version 3 000 or later The following optional values can be manually added to the Registry when needed MaxMuxVersion 3 This registry value provides the possibility to force the driver to use a lower multiplex protocol version than the maximum supported The multiplex protocol has been improved con tinuously by adding several features The multiplex protocol version is negotiated with the connected module during mul tiplex startup It is used to ensure compatibility between dif ferent multiplex driver and module generations The registry value isn t mandatory by default the WinMux driver uses always the latest protocol implementation with all available features If for some reason an older multiplex protocol shall be used it can be controlled with that registry value For fur ther information about the multiplex protocol versions refer to the Multiplexer User s Guide HdlcWindowSize 4 Modules with multiplex protocol version 4 and above use a kind of HDLC framing to secure the data transmission on the virtual ports and avoid data loss at high transfer rates and much data traffic This registry value provides the possibility to adjust the size of the HDLC window which defines the maximal number of outstanding HDLC packets It can be between 2 and 7 This Registry value is not mandatory If it is not added to the Registry the value 4 will be assumed by default Please note that the value is negotiated with the module
12. o e CRM HR Ra HERR e naga 26 6 2 Preparing the Translation n nenne ihnen D nennen 26 6 3 Compiler Flag S inte nep ote cett ue ede 26 7 Additional Source Documentation eeeesieeee eese sees eeeeeeeee nennen nnn nnn asas nnn nunna ennenen nennen 27 7 1 Interaction of the Different Driver Objects sssssssssssseeeeeeeneneeneen nnne nennen 27 7 2 Interal Driver Statess une ie nee ree bebe ioo 28 Co Butter Handling 5 oer ue tute E ED eii ts 29 EA IData Transferxsi eee peer dec c pt ture Sagan e ape vv apto E epe ue Ede quate depu e e ee 30 7 4 1 Block Flow Diagram for Data Received by the Module see 30 7 4 2 Block Flow Diagram for Data Sent to the Module via Virtual Port 31 7 4 3 serMuxSend F nctiofi nere cnm eru tie RR cose i dtss 32 7 5 Tho A ParSer nauis aient pn aet aderit dee trie e er ROS EDS Diva Bf c ee Od 34 8 Known Problems 2 24 ce ee Settee Eiane KEANE AUE TERE ENAKA ENEE AETA eSEE KANAE AEAEE 35 8 1 Booting Operating Systemi zc eec tenete dC ne Haee a gt e EEan O Hd e pL rapere TAES 35 Mux Drv DevGuide v07 Page 3 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide SIEMENS Contents 8 2 Shutdown of the Operating System sssssssssssssssssssseeeee nennen nnne rnnt nnns 35 8 3 Standby of the Operating System ssssssssssssssssseseeeeenteneen nennen
13. the supported Siemens wire less modules they are particularly noted The Multiplexer sources are available on request In the case you wish to receive the source code of the MinMux2k driver packed into a zip file containing the complete source files together with corresponding MS Visual Studio 6 0 project files see Chapter 6 Mux Drv DevGuide v07 Page 10 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide 1 2 Related Documents 1 2 Related Documents SIEMENS 1 3G TS 27 010 3rd Generation Partnership Project Technical Specification Group Terminals Terminal Equipment to Mobile Station TE MS multiplexer protocol 2 Digital Cellular Telecommunications Systems Phase 2 Terminal Equipment to Mobile Station TE MS Multiplexer Protocol ETSI TS 101 369 V7 1 0 1999 11 GSM 07 10 Version 7 1 0 Release 1998 3 AT Command Set of your Siemens wireless engine 4 Hardware Interface Description of your Siemens wireless engine 5 Multiplexer User s Guide 6 MC35 Multiplexer User s Guide for MC35 only 7 TC3x Multiplexer User s Guide for TC35 and TC37 only To visit the Siemens Website you can use the following link http www siemens com wm 1 3 Abbreviations Abbreviation Description ACPI Advanced Configuration and Power Interface CTS Clear to Send DCD Data Carrier Detect DDK Driver Development Kit Microsoft driver develop
14. traces how and because a Request completed 0x2000 0000 traces V 24 signals and change of these sig nals 0x4000 0000 traces in which state is the parser for scanning the sequence 0x8000 0000 traces states for scanning a Frame DebugPort 0x0 0 Output from the driver is redirected to the kernel debugger default value 1 4 Output is redirected to a COM port Mux Drv DevGuide v07 Page 24 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide 5 Settings for Applications SI E M ENS 5 Settings for Applications 5 1 Dial up Network Settings The dial up network settings must be configured according to the requirements of the network provider The WinMux2k driver has no special requirements 5 2 Fax Settings There are no special settings for the fax service of the operating systems Note If the fax service is enabled for receiving fax messages the virtual port is opened all the time In this case the driver cannot be disabled or unloaded To change port settings the PC must be rebooted Mux Drv DevGuide v07 Page 25 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide SIEMENS 6 Translate Source Code 6 Translate Source Code 6 1 Software Requirements The WinMux build environment has been designed to work together with a Microsoft Visual Studio 6 0 SP3 or higher and the Microsoft Windows XP SP1 DDK It is possible to use a Windows 2000 DDK as well bu
15. SIEMENS opino suesn Multiplexer Driver Developer s Guide SIEMENS Document Name Multiplexer Driver Developer s Guide Version 07 Date 2006 9 27 Docld Mux_Drv_DevGuide_v07 Status Confidential Released General Notes Product is deemed accepted by recipient and is provided without interface to recipient s products The documen tation and or product are provided for testing evaluation integration and information purposes The documen tation and or product are provided on an as is basis only and may contain deficiencies or inadequacies The documentation and or product are provided without warranty of any kind express or implied To the maximum extent permitted by applicable law Siemens further disclaims all warranties including without limitation any im plied warranties of merchantability completeness fitness for a particular purpose and non infringement of third party rights The entire risk arising out of the use or performance of the product and documentation remains with recipient 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 Applications incorporating the described product must be designed to be in accordance with the technical specifications provided in these guidelines Fail ure to comply with any of the required procedures can result in malfunctions or serious discrepancies in results
16. SR changes This feature can be switched off if an application controls the DSR line with AT amp S 1 Default for all modules except XC18 The driver tries to reconnect to the module if DSR changes The driver can detect if the module was disconnected and reinitializes it before the first data errors occur ClosePort AT IPR 0 A multi string sent to the module if the last port is closed not applicable to AT SMSO TC45 and XC18 ClosePort AT IPR 0 A multi string sent to the module if the last port is closed TC45 XC 18 only PowerDown AT CFUN 0 A multi string sent to the module if the PC goes to suspend mode or hibernate state The command AT CFUN 0 has been chosen as factory default for compatibility with older Siemens products If you prefer to use one of the more efficient CYCLIC SLEEP modes it can be replaced with AT CFUN 5 or 6 or 7 or 8 or 9 See 3 and 4 to verify the SLEEP mode types supported by your product To avoid editing the Windows Registry you can alter the corresponding parameter in the winmux2k inf file and then reinstall the driver ShutDown AT IPR 0 A multi string sent to the module if the PC is shut down or AT SMSO rebooted Note Some PCs generate a DTR spike during turn off and the module wakes up again WaitForDSR 1 0 Default for TC45 and XC18 The driver does not wait for the DSR signal to go low when the module is shut down Instead the parameter Recover Time see below is used 1 Def
17. al serial port Signal Description RTS CTS Hardware controlled DTR Set to 1 Baud rate Variable parameter read from registry Data bits 8 Parity No Stop bits 1 2 3 Module Detection The module supports an auto baud mode and constant baud rates Furthermore the module can stay in normal AT command mode or in WinMux2k mode To establish a communication to the module the correct baud rate and the state of the module must be found Therefore it is recommended to set the module into auto baud mode If the baud rate is programmed to a constant value the driver has to find the correct baud rate To do so the driver sends an AT command to the module trying different baud rates until the correct one is found If the mod ule doesn t answer to the initial AT sent at the first baud rate the driver tries to disable the possibly enabled multiplexer mode This is done because the module might still be kept in multiplexer mode due to an earlier fail ure If this fails the driver sends again the initial AT command using the next baud rate from the list of supported baud rates The driver must wait for a given timeout before the decision can be made that the module does not answer at any baud rate The timeout value can be changed in the Windows Registry see RequestTimeout value in Table 6 It can take some time before the driver finds the correct baud rate or before the driver fails to call the Open function Ev
18. any other substantive law Copyright Transmittal reproduction dissemination and or editing of this document as well as utilization of its contents and communication thereof to others without express authorization are prohibited Offenders will be held liable for payment of damages All rights created by patent grant or registration of a utility model or design patent are re served Copyright Siemens AG 2006 Mux_Drv_DevGuide_v07 Page 2 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide SIEMENS Contents Contents 0 DOCUMENT FIISTONY e 7 1 Junigere UI CUO oec MD EE 9 i Supported Product Versions iei ee eka tii fe te Eb nd die e ens 10 1 2 Related Documents stie nee ele eie ete b D EN e ei e 11 TB Abbreviations tr ihe HG ree n Eee are a et oa Ere yl eh eit e t vere Beer b us 11 2 f ireii zsd lie mL 12 2 1 Hierarchy Chart in the System ssssssssssssssssssseseeen nennen nennen nne nennen nennen 12 2 2 Handling of the Physical Serial Port esssssssssssssessssseeeeeen nennen entente nennen 13 2 9 Module DetectiOn erii re ep rea p EIE ier idet neo 13 2 4 Handling of Control Lines on Virtual Ports sssssssssseseeeneneneenee enne 14 2 5 Limitation of Virt al Ports cited de ie fett temere 14 2 6 Module Initializing Sequence sse enne nnne tenere siint 15 2 7 Module
19. ault for all modules except TC45 and XC18 The driver waits for the DSR signal to go low when the mod ule is shut down In this case the parameter RecoverTime is not used If the module is not switched off with the AT com mands defined in the parameter ClosePort this parameter must be set to 0 RecoverTime 2000 Minimum number of milliseconds between close and the next open call PowerDownFrame 2 From version 3 onwards the Multiplexer Protocol supports power saving control with a special multiplex control frame This provides the possibility of sending power down com mands to the module without accessing any data channel If the connected module only supports the Multiplexer Pro tocol version 2 this value is not used If the supported Multi plexer Protocol version is 3 or higher the multiplex power control is used instead of the values PowerCmdPort and PowerDown In this case this value corresponds to the power down command of the multiplex power down frame described in 5 If the value is greater than 255 there is no power down frame sent for Multiplexer Protocol 3 Mux Drv DevGuide v07 Page 22 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide 4 2 Settings Stored in the Windows Registry SI E M ENS Table 6 Registry values Value Data Example Properties Optional values supported as of Multiplexer Protocol version 4 i e supported by the WinMux2k
20. d ProcessChar no Frame valid gt DemuxindicateFrame yes Address DLCI SerPortlndicateFrame amp amp UIH Frame other ports than 0 i es UIH Frame x M search the next Control Command in the no Information field all UIH Control yes Gommands scanned SerPortOScanUlIHComtrol see sheet 2 no check a UIH ControlFrame return SendPort SerPortOConfirm Request SABM or DISC Frame not valid Master v SerMuxSend must call if receive a FC Bit 0 then start the sending Figure 6 Block flow diagram for data received by the module Page 30 of 36 2006 9 27 Multiplexer Driver Developer s Guide 7 4 Data Transfer SI E M ENS 7 4 2 Block Flow Diagram for Data Sent to the Module via Virtual Port Send Request Flow of a virtual Channel with scanning of Break Signal only the schema WrSendRequest ReadintervalTime 0 TotalTlme 0 ScanFlags 0 PlusNb 0 TimeStamp ActualTimerTick Y DlistInsertHead Y SerMuxSend e Figure 7 Block flow diagram for data sent to the module via a virtual port Mux Drv DevGuide v07 Page 31 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide 7 4 Data Transfer 7 4 3 SerMuxSend Function SIEMENS The figure shows the flow diagram of the SerMuxSend function which sends the data to the module SerMuxSend and SerMuxSendPortO Functions Locations from where to call the SerMuxSend Functions Func
21. en if the module is not connected to the serial port or is turned off the long timeout period occurs If the connection to the module has been established the baud rate set in the Registry is used for further com munications Closing the last port deactivates the multiplexer mode and causes the module to return to normal AT command mode without multiplexer Also autobauding AT IPR 0 will be enabled once again Finally the AT SMSO command will be sent to switch the module off Only in the case of TC45 and XC18 AT SMSO will not be sent Instead TC45 and XC18 remain in normal AT command mode and can be quickly accessed from the PC debug environment Mux Drv DevGuide v07 Page 13 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide 2 4 Handling of Control Lines on Virtual Ports SI EM ENS 2 4 Handling of Control Lines on Virtual Ports Summary of control line handling Table 2 Virtual serial port with Multiplexer Protocol version 2 Signal Description RING Read from hardware port distributed to the first virtual port DCD Read from hardware port distributed to the first virtual port DSR Received with Modem Status Command DTR Set by user sent with Modem Status Command initialized with 1 CTS Received with Modem Status Command RTS Set by user sent with Modem Status Command initialized with 1 Table 3 Virtual serial port with Multiplexer Protocol version 3
22. enne ns 35 84 Wake on RING traori iena ANANN RA ARERR RASAR ERTER ARAARA NERSE ERRE EREITEA 35 8 5 Special Environments seirian a a ae aaa aa iaaa aa Eea sen aidea aaa aaia aa aiia 36 8 6 Operation on Virtual USB Port sssssssssssssssseseeee nennen nennen tennis sentent nnns nnne nnns 36 8 7 Automatic Shutdown in case of Emergency sssssssssssssssesee eene 36 Mux Drv DevGuide v07 Page 4 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide List of Tables SI EM ENS Tables Table 1 Physical serial pOFt copine edite tese Dedit e edd redeundi edoctus 13 Table 2 Virtual serial port with Multiplexer Protocol version 2 ssen em 14 Table 3 Virtual serial port with Multiplexer Protocol version 3 ssseee nnn 14 Table 4 Module initialization of supported modules sseeeenee nennen 15 Table 5 Required driver files 2 2n ca rh uie tede dtm EAE RE KRATSIE KATTEE INRE COEN edi 18 Table 6 RROGISUY ATI E 21 Table 7 Registry values for trace outputs ssssssssssssesssesseseeeeeee enne nennen nene 24 Mux Drv DevGuide v07 Page 5 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide SIEMENS List of Figures Figures Figure 1 Driver architecture sc0c c2iecte se sceds i cnctedend deeded deg ceived se ucaieedendlinb anand aelidied deeded a 12
23. erPortO OnTimerSerPort Escape Sequence Control Timeouts for Send and Receive Queue Requests for repeating Control Commands and Timeouts for scanning the Frame Assembly and check Send function state machine Demux while GetWriteBuffer IndicateRead SerPort GetNextSerPort ProcessData check frame crc SerPort gt GetFrame SerPortIndicateFrame SubmitWriteBuffer indicate frame to a SerPort instance SIEMENS Mux_Drv_DevGuide_v07 Confidential Released WrGetWriteBuffer void Buffer ULONG amp Length void WrlndicateReadBuffer void Buffer ULONG Length WrSubmitWriteBuffer void Buffer ULONG Length WrWriteComplete WrReturnWriteBuffer Write Buffer Read Buffer Pool Pool Figure 5 Driver internal buffer handling Page 29 of 36 Wrapper 2006 9 27 Multiplexer Driver Developer s Guide 7 4 Data Transfer 7 4 Data Transfer SIEMENS 7 4 1 Block Flow Diagram for Data Received by the Module SerMux functions sequence if characters from the physical Device to the SerMux Object are indicated W rindicateReadBuffer c SerPortOIndicateFrame Mux Drv DevGuide v07 Confidential Released yes all bytes scanne
24. ersion 02 New document Multiplexer Driver Developer s Guide Version 03 Chapter What is new ay he Updated list of supported products and information about version control Throughout Complete revision of all chapters Added information specific to TC35i and TC45 manual Updated Description of Registry values Mux_Drv_DevGuide_v07 Page 8 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide SIEMENS 1 Introduction 1 Introduction The multiplex mode according to the ETSI TS 101 369 GSM 07 10 Multiplexer Protocol enables one physical serial interface to be partitioned into three virtual channels This allows you to take advantage of three simulta neous sessions running on one serial interface For example you can send or receive data on the first channel while the other two channels are free to control the GSM GPRS engine with AT commands In order to properly communicate with the wireless modem the application needs to support the Multiplexer Pro tocol and 3 virtual ports must be installed For this purpose a Windows 2000 XP multiplexer driver WinMux2k can be provided The driver offers basic multiplexer functionality and serves as a reference implementation to aid developers and system integrators in designing developing and testing customized multiplexer applications As such it has been tested by Siemens using a variety of applications and platforms but naturally even the most ex
25. ersion 3 or later and enabled by the Registry value WaitForDSR 1 Due to different requirements of the supported products the Registry values ClosePort and WaitForDSR vary with the module type By default all modules except for TC45 and XC18 will be switched to autobauding with IPR 0 and then turned off by AT SMSO with the WaitForDSR feature being enabled TC45 and XC18 how ever will only be set to autobauding and not switched off and therefore the WaitForDSR feature is disabled As stated in Section 2 3 this default behavior of TC45 and XC18 was implemented for faster access from the PC debug environment Mux Drv DevGuide v07 Page 16 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide SIEMENS 2 8 Power Down 2 8 3 Power Down on PC Shutdown When the PC is shut down the multiplexer mode is turned off and the strings from the Registry value ShutDown are sent to the module if a virtual port is in use Note During shutdown some PCs may generate an impulse on the lines of the serial interface In applications where the DTR line connects to the ignition line IGT an impulse received on DTR will immediately cause the module to be restarted from Power Down mode Mux_Drv_DevGuide_v07 Page 17 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide SIEMENS 3 Installation 3 Installation 3 1 Files Required for WinMux2k Driver Installation Table 5 Required drive
26. he module type This means that when you migrate to another module type you are required to uninstall the driver and reinstall it with the new module The settings are taken from the winmux2k inf file The tables below list the commands sent to the module during the initialization As the init string information is stored in the Windows Registry the corresponding values are also listed For further details on the Registry see Section 4 2 Table 4 Module initialization of supported modules Command Response Function Associated Registry value AT OK Detection of connected module AT IPR 115200 OK Baud rate specified in the Windows Registry during WinMux2k installation The value may be different according to individual settings BaudRateString AT OK Check if change of baud rate was suc cessful Modemlnit AT amp S0 Q3 OK Sets DSR always on and hardware flow control The settings are read from the Windows Registry Modemlnit AT ICF 3 OK ERROR Sets interface mode 8N1 This com mand works only on modules support ing different interface modes TC35i TC63 TC65 MC75 AC75 The set tings are read from the Windows Regis try The resulting ERROR on modules with out support of the AT ICF command is ignored by the WinMux2k driver Modemlnit AT CMUX 0 OK Switches to multiplexer mode This sequence is read from the Windows Registry M
27. install the driver and reinstall it with the new module This way you can take advantage of the module specific power down sequence determined during the driver installation and executed each time after closing the last virtual port see Section 2 8 2 and Section 4 2 Although it is not recommended it is possible to modify the driver s factory defaults by editing prior to the driver installation the parameters contained in the winmux2k inf file This approach can be used for example if you want to use another default baud rate or if you want to replace the string AT CFUNZO with one of the CYCLIC SLEEP mode settings supported by your module such as AT CFUN 5 or 6 or 7 or 8 or 9 See also Section 4 2 Note During the installation a pop up dialog with Digital Signature Not Found will appear Please ignore this message and continue the installation process The reason for the message is that the driver has not been reg istered with Microsoft but its correct functionality is ensured Mux Drv DevGuide v07 Page 18 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide 3 3 Deinstalling the Driver SI EM ENS 3 3 Deinstalling the Driver In order to uninstall the Windows Multiplexer Driver perform the following steps Windows 2000 Start the Control Panel Select System Select the Hardware property sheet Double click the Device Manager button Under Multi port serial adapters right click Serial Multiplexer
28. interface for use with the WinMux2k driver the virtual COM port assigned to the module s USB interface shall be set to max 115200 bps To do so use the Serial Multiplexer Properties page described in Section 4 1 The setting is only needed to open the virtual multiplex channels on the virtual COM port assigned to the USB interface There is no loss of performance because the virtual baud rate on the USB interface has no influence on the data transfer rate 8 7 Automatic Shutdown in case of Emergency Please note that while Multiplex mode is active the automatic shutdown mechanism described in 3 and 4 is not effective If fault conditions arise such as over and undertemperature or undervoltage overvoltage shut down is product dependent the module shuts down after sending the alert URCs e g SBC undervoltage or SCTM A B 2 2 but is then restarted by the WinMux2k driver Therefore to avoid problems it is strongly recommended to close all virtual ports as soon as alert URCs are sent by the module Please refer to 3 and 4 as the SBC and SCTM URCs are product specific Mux Drv DevGuide v07 Page 36 of 36 2006 9 27 Confidential Released
29. ion HDLC 6 1 6 2 Updated requirements for Windows environment Preceding document Multiplexer Driver Developer s Guide Version 05 New document Multiplexer Driver Developer s Guide Version 06 Chapter What is new 1 1 Enhanced list of supported products 8 6 Added Chapter Operation on Virtual USB Port 8 7 Added Chapter Automatic Shutdown in case of Emergency Preceding document Multiplexer Driver Developer s Guide Version 04 New document Multiplexer Driver Developer s Guide Version 05 Chapter What is new 1 1 Updated list of supported products 2 6 Changed description within Table 4 to cover all supported modules Deleted tables for particular modules 3 2 Hints on migration to different modules changed 4 2 Updated description of the Registry values Modemlnit ClosePort WaitforDSR Preceding document Multiplexer Driver Developer s Guide Version 03 New document Multiplexer Driver Developer s Guide Version 04 Chapter What is new Throughout In several chapters added information specific to XC18 manual 1 1 Updated list of supported products 2 6 Added note regarding user profile settings 4 1 Added figure and modified description Mux Drv DevGuide v07 Page 7 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide SIEMENS Preceding document Multiplexer Driver Developer s Guide V
30. ment DSR Data Set Ready DTR Data Terminal Ready ETSI European Telecommunications Standards Institute FIFO First in first out GPRS General Packet Radio Service GSM Global System of Mobile Communication MS Mobile Station PC Personal Computer PDA Personal Digital Assistant RI Ring Indicator RTS Request to Send TE Terminal Equipment UART Universal Asynchronous Receiver Transmitter Mux Drv DevGuide v07 Page 11 of 36 Confidential Released 2006 9 27 Multiplexer Driver Developer s Guide SIEMENS 2 Architecture 2 Architecture 2 1 Hierarchy Chart in the System Sessions running simultaneously Va Bis TE SMS functions Ad Terminal poer 1 padnnele channel 3 SON COM10 COM 11 COM 12 direct connection File object for File object for File object for virtual COM port virtual COM port virtual COM port File object for physical COM1 port Device object winmux2k sys Multiplexer Protocol GSM 07 10 one control channel and data channels erial sys port COM1 Kernel Hardware Phys serial port RS 232 connection Modem Siemens GSM engine with Multiplexer Protocol Figure 1 Driver architecture Mux Drv DevGuide v07 Page 12 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide 2 2 Handling of the Physical Serial Port SI EM ENS Figure 1 shows the driver architecture of winmux2k sys in the operati
31. ng system The device driver winmux2k sys emulates virtual serial ports The lower layer of the WinMux2k driver is the physical serial port driver serial sys The WinMux2k driver is loaded during system startup It creates virtual port objects The physical port is opened when the first virtual port is opened by an application If the last virtual port is closed the physical port will be released by the WinMux2k driver This allows applications to access the module without the WinMux2k driver If the WinMux2k driver is opened by at least one application a special device object is attached to the driver stack of the serial sys driver This device object is used to control the power management request It is detached from the stack if the last handle is closed 2 2 Handling of the Physical Serial Port When the physical port is opened the WinMux2k driver initializes it During the initialization the physical port is setto hardware handshake This means the RTS and CTS signals on the port side are controlled by the hardware and the WinMux2k device driver The DTR signal is set to 1 The port mode is set to 8 bits 1 stop bit no parity The baud rate can be configured using the winmux2k inf file or the Serial Multiplexer property page If fast baud rates are selected e g 115200 bps the receive FIFO of the UART should be configured for a size of 8 bytes This can be done using the property page of the COM Port in the device manager Table 1 Physic
32. ntial Released 2006 9 27 Multiplexer Driver Developer s Guide SIEMENS 7 5 The Parser 7 5 The Parser The following state diagram shows the states of the parser Internal states of the ScanRequest Object for scanning each character in a Send Request for one Port Object if BreakCount gt 0 then send first Nc the breaks After check for incoming Request also check if Break Count gt 0 and then characters Timeout 1s and SerMuxSend BreakCount 0 If rcv a SendRequest then Flag SCAN_LATER rev BreakChar rev char unequal or Timeout 1s or difference between current and last Request too big rcv any character with time differences over One second to the last character Timeout or the ScanRequest Timer go to zero if rcv then in the Timer BreakCount 1 WaitResponseTimer if receive the MSC Response if BreakCount 3 Send MSC command with ESCAPE 1 1 If the next incoming request has a Timeout to the last request then switch to WAIT BREAK without Timerfunction Request Flag SCAN LATER 2 if the ScanRequest Timer go to zero If rcv a SendRequest then Flag SCAN LATER if Timer go to 0 if Timer go to zero if STATE WAIT BREAK then STATE WAIT CHAR if STATE PLUS then STATE WAIT CHAR if STATE PLUS TIMEOUT then STATE WAIT BREAK Figure 10 State diagram of the parser Mux Drv DevGuide v07 Page 34 of 36 2006 9 27 Confidential Released
33. of data the multiplexer driver switches on the hardware flow control on the module This means that the module cannot send data to the PC if the operating system is in standby mode and therefore the serial interface is blocked by the hardware flow control As a consequence the operating system does not wake up if the system ignores the RING signal because the module cannot send the RING or CALA messages to the PC Mux Drv DevGuide v07 Page 35 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide SIEMENS 8 5 Special Environments 8 5 Special Environments The driver expects a module connected to the COM port in a way where the ignition signal to start the module is connected with the DTR signal of the COM port so that the driver is able to switch the module on via the DTR signal If the driver is used for modules built into environments where this connection does not exist e g like laptops with a hard mounted module it cannot power on the module In this case the automatic power down of the module after closing the last virtual channel has to be disabled by replacing the line HKR ClosePort 0x00010000 AT IPRZO AT SMSO with the line HKR ClosePort 0x00010000 AT IPR 0 In the case of TC45 and XC 18 there is no need to alter the value ClosePort in the Registry 8 6 Operation on Virtual USB Port This section applies only to Siemens GSM modules equipped with a USB interface To configure the USB
34. ore AT commands can be sent to the module at this point ModemInit Note The initialization sequence overrides the user profile settings defined with AT amp W on channel 1 for the com mands AT amp S AT Qn and AT ICF After restart without multiplexer the user profile will be loaded with all your individual settings Mux_Drv_DevGuide_v07 Confidential Released Page 15 of 36 2006 9 27 Multiplexer Driver Developer s Guide SIEMENS 2 7 Module Re initialization 2 7 Module Re initialization If the module is disconnected or powered off during normal operation the driver detects this and tries to reinitial ize the module Because the module state can be changed while disconnected the multiplexer mode has to be completely initialized The driver checks the following situations Invalid frames from the module are received Timeout occurs during sending frames DSR signal goes to zero can be turned off with Registry value If one of these conditions is detected the driver starts the following actions Tryto send an MSC command to the module If the module answers it is assumed that the module is working and no re initialization is required Generate an RTS impulse Wait for CTS to ensure that the module has been properly started after re initialization e Reinitialize the module 2 8 Power Down The module switches to Power down mode when the PC enters the suspend mode or shuts down or when the
35. r Objects Object chart of the device driver winmux2k sys WDM Model Driver object winmux2k Device object Device extension struct DEVICE DPOOL request pool Control Irp for serial driver gt Lar eo IRP Complete object 5 gt Context i Wait Irp for serial events Port objects DLIST IRP_QUEUE Read queue SerMux IRP_QUEUE Write queue SendBuffer p RevBuffer b gt Y PORT OBJ virtual serial port Kg gt SER_PORT Mux Drv DevGui ANSI C WinMux object SerPortO object ChkFrame object PtrSerPort Buffer for read and write requests DLIST Sendqueue DLIST Rcv queue CIRCBUF Objects for circular send and receive buffer Parameter for the virtual serial port Figure 3 Interaction of the different driver objects de v07 Confidential Released Page 27 of 36 2006 9 27 Multiplexer Driver Developer s Guide SIEMENS 7 2 Internal Driver States 7 2 Internal Driver States SerMux internal states STATE CLOSE _ DOWN initial state rcv a DM Frame send a SABM Frame STATE DISCONNECT
36. r files File Comment Wmuxinst exe WinMux2k driver installation program Winmux2k inf INF file for the WinMux2k driver It contains all driver settings and module specific set tings stored in the Windows Registry during the installation See Section 4 2 for fur ther details on the Registry Winmux2k sys Device driver image Wmuxprop dl Property page for the module co installer 3 2 Installing the WinMux2k Driver Before starting the installation make sure that all files are located in the same folder as the wmuxinst exe e winmux2k inf winmux2k sys wmuxprop dll Start the program wmuxinst exe Ensure that the module is connected to a serial port and turn the module power on Press the Scan button of the application All Siemens modules found will be listed in a box If no modem has been installed yet the virtual ports can be selected If it is properly installed the virtual ports are shown If at least one modem is found the Install button becomes active Pressing this button will cause the selected modules to be installed e N 4 Use the Device Manager to check that the installation was successful The virtual ports are available without reboot The driver instances are visible in the device manager class Multi port Serial Adapters If you wish to uninstall the driver see Section 3 3 When migrating from TC45 or XC18 to another module type or vice versa we recommend to un
37. r with the BIOS incoming calls or real clock alarms wake the operating system up again During this wake up the first characters sent by the module to the operating System via the serial interface are lost This is no restriction of the serial WinMux2k driver but caused by the operating system E g in case of an incoming call the first RING event is lost Usually this causes no problem because the RING is repeated every few seconds However in case of the real clock alarm the module only sends one CALA URC As a result the URC will not be indicated though the alarm will be correctly executed Additionally in some cases when the computer switches to suspend mode this causes pulses on the serial inter face signals which wake up the module again 8 4 Wake on Ring If the operating system is in standby mode and the module has not been switched off incoming calls and real time clock alarms should wake up the operating system wake on RING This feature belongs to the ACPI power management mechanisms which are not properly implemented on all PC systems It is independent of the mul tiplexer driver When the ring signal toggles on the serial interface like on incoming calls and real time clock alarms this should wake up the operating system if the PC has been properly configured On some systems not the RING signal but data transferred to the PC the RING or CALA messages from the module wake up the operating system To avoid loss
38. rt Each virtual port must have a unique name Otherwise the driver will fail to start up VirtPort2 COM 1 See VirtPort1 VirtPort3 COM12 See VirtPort1 VirtualChannels 3 Number of Virtual Channels visible as COM ports The WinMux2k driver supports up to 3 virtual ports The number of VirtualChannels must be less or equal to TotalChannels TotalChannels 3 If the number of TotalChannels is greater than VirtualChan nels and no VirtPortX value for additional channels is defined these additional ports are not visible as COM ports They can be accessed by the link named SERMUX_CONTROL_PREFIX defined in sermux_i h This allows to hide virtual ports to the user Each physical port can have one hidden port WakeUpTime 4000 Timeout during module initialization The timeout takes effect only when the driver tries to restart the module from Power Down or to wake it up from SLEEP mode AT CFUN 0 The time is given in milliseconds PowerCmdPort 3 This virtual channel is used to send the power down com mands to the module The data state on this channel may be disturbed during power down and cannot be reconstructed by the driver Mux_Drv_DevGuide_v07 Confidential Released Page 21 of 36 2006 9 27 Multiplexer Driver Developer s Guide 4 2 Settings Stored in the Windows Registry SI E M ENS Table 6 Registry values Value Data Example Properties ReinitOnDSR 1 0 Default for XC18 The driver does not try to reconnect to the module if D
39. t in this case adaptations to the different build control files might be necessary 6 2 Preparing the Translation 1 Create the environment variables WINMUXVSTUDIOROOT and WINMUXDDKROOT containing the path to the root of your Visual Studio and Windows DDK installation Alternatively you can edit the file driver dir_env cmd and enter the correct paths to the DDK and the VC 6 0 there 2 Open the workspace sermux in the root directory Select batch build 3 The executable files can be found under lib wdm fre chk _wxp_x86 i386 Note The DDK is a software tool for Windows driver development 6 3 Compiler Flags There is only one compiler flag MUX MANUAL for a conditional compile of the driver With this compiler flag set the driver can be compiled in a special manual version where opening and closing of the multiplexer can be controlled via special DeviceloControl commands instead of automatic control via the opened virtual channels This manual version is used for internal automated module testing and is not relevant for usual driver operation Mux Drv DevGuide v07 Page 26 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide 7 Additional Sou rce Documentation 7 Additional Source Documentation SIEMENS This chapter contains additional flow charts and state diagrams which give more detailed information on the structure and the content of the sources 7 1 Interaction of the Different Drive
40. tensive test setup can never be adequate to cover all conceivable configurations The Siemens AG does not guarantee any support regarding the integration of the driver into a customer s appli cation However the documentation as well as code binaries and source files can be provided and used for fur ther development This document describes how to install the Windows 2000 XP multiplexer driver WinMux2k in a Windows 2000 XP based application Related Documents Mux Drv DevGuide v07 Page 9 of 36 2006 9 27 Confidential Released Multiplexer Driver Developer s Guide SIEMENS 1 1 Supported Product Versions 1 1 Supported Product Versions Please note that this User s Guide covers the three different versions of the Multiplexer Protocol The following products support the Siemens Multiplexer Protocol version 2 TC35 TC35 Terminal and TC37 from Release 03 10 e MC35 from Release 03 00 AC35 The following products support the Siemens Multiplexer Protocol version 3 AC43 AC45 e MC35i e MC35i Terminal e MC39i MC45 MC46 e MC388 e MC5x TC35i TC35i Terminal TC45 XC18 e XT55 XT56 e MC75 TC63 TC65 TC65 Terminal e WinMux2k driver earlier than version 3 000 The following products support the Siemens Multiplexer Protocol version 4 AC65 AC75 XT65 XT75 e WinMux2k driver as of version 3 000 Where differences occur between the two Multiplexer Protocol versions or between
41. tion that calls from SerMux Wrapper WrSendRequest SerMuxSend Send UIH Frames from E WriteRequests to the virtuals Ports Function that calls from SerMux Wrapper WrTimer WrWriteComplete Function that calls from ChkFrame SerPortOIndicateFrame SerPortIndicateFrame SerMuxSendPortO Send Control Frames to Mux Drv DevGuide v07 Confidential Released the Multiplexer Control Port Channel 0 Figure 8 SerMuxSend function Page 32 of 36 Function that calls from SerPort0 EstablishDLC ReleaseDLC CloseDown SetModemStatus SendVersionCommand SendUAFrame 2006 9 27 Multiplexer Driver Developer s Guide 7 4 Data Transfer Mux_Drv_DevGuide_v07 Send function from the virtual Communication Ports the SerPort Object Function SerMuxSend only sends UIH Frames unnumbered information which come in from WriteRequest to the virtual serial communication port sm gt v WrGetWriteBuffer no GetBuffer SIEMENS sked all Port twi times and no Frames sent yes no GetFrameBufferPort _ Get WriteBuffer no yes yes v WrSubmitWriteBuffer WrReturnWriteBuffer re Figure 9 Send function from the virtual communication ports Page 33 of 36 Confide
Download Pdf Manuals
Related Search