2 second serial interface asc1, Second serial interface asc1 – Siemens AC75 User Manual
Page 122
![background image](/manuals/154345/122/background.png)
AC75 AT Command Set
4.10 AT+CMUX
s
AC75_ATC_V01.002
Page 122 of 569
10/30/06
Confidential / Released
4.10.2
Second serial interface ASC1
The second serial interface ASC1 is intended as an auxiliary interface for applications which need multiple par-
allel access to the module (e.g. to query status information during a data call), but cannot use the GSM 07.10
multiplexing protocol. Therefore this interface offers limited functionality only.
• No DTR, DSR, DCD, RING signals. These hardware lines do not exist. As a result, AT commands controlling
the behavior of these lines (
) are not allowed and return ERROR.
• No presentation of ^SYSSTART URCs on ASC1. After restart or reset of the ME, either check that the URC
has been sent on ASC0 or wait approximately 3 seconds before entering the first AT command on ASC1.
• No Autobauding. The hardware is not capable of automatically detecting the baudrate on this interface, so
the AT command which selects autobauding (
=0) is not allowed and returns ERROR.
• No CSD calls, so all related AT commands cannot be used and return ERROR.
• No fax calls, so all AT+F commands cannot be used and return ERROR.
• No GSM 07.10 Multiplexer. If issued on the second interface
=0 returns ERROR.
ASC1 is disabled when the multiplexer is enabled on the first serial interface ASC0. Yet, both ASC1 and the mul-
tiplexer channel 2 are using the same parameters, and thus, the same user defined profile (if any). As a result,
a user profile stored on multiplexer channel 2 takes effect on ASC1 after closing the multiplexer and starting up
ASC1. Likewise, a user profile stored on ASC1 will be loaded on multiplexer channel 2.
This may be a problem when ASC1 is not connected, but flow control (for example
3) is stored to
the user profile on the multiplexer channel 2. In this case, flow control takes effect on ASC1, when the multiplexer
is switched off. If then for example a large amount of URCs is generated, their transmission might be stopped
due to the flow control. To avoid this problem we recommend that you do not activate flow control on multiplexer
channel 2 when you set up a user profile with
- A75
- SXG75
- CX65
- A50
- C30
- A65
- SL75
- A35
- M75
- SX1
- C55
- M55
- SL45
- S65
- S75
- CF75
- CFX65
- AX75
- C75
- M65
- CX75
- ST60
- U15
- CF62
- C45
- C45
- Xelibri 8
- Xelibri 7
- SL42
- SL45i
- Xelibri 3
- ST55
- SL55
- C62
- C62
- Xelibri 6
- M50
- Xelibri 2
- Xelibri 4
- A57
- A36
- Xelibri 1
- Xelibri 5
- C70
- Gigaset SL 740
- Mobile Phone C35i
- 4110
- RS-485
- A55
- Gigaset SL55
- Gigaset C450 IP
- Gigaset E45
- S42
- Gigaset 150
- XT75
- SL370
- M30
- A40
- S56
- TDMA 800
- S40
- 150 H
- MT50
- C60
- SL 42
- CL50
- 1168
- C35i
- A52
- SL56
- A60
- SX66
- 4000
- MOVIEMATE 50
- XT55 AVL
- XT55
- 3000
- Gigaset 200
- Mobile
- Mux_guide_v06
- Gigaset S450 IP
- MC60
- Hicom 300E
- SF65
- CXV70
- CXV65
- 8WD44
- C61
- C56
- S45i
- MC55
- CX70
- PEGASUS-DTC AX72
- C70 CT70
- 4010
- Gigaset SL1
- Gigaset C100 DECT
- Gigaset S1
- 4000i
- Gigaset 3000 Classic