I’ve realized CMUX protocol on GL865 and it’s working. But I can’t run remote sim on the same virtual port from which I sent at command to enable Remote Sim. I want to use it without bluetooth only through USART. SAP server will be use only CMUX and USART.
When I send AT command AT#RSEN=1,1,0,2,10 in CMUX mode to 1-irst CMUX firtual port and in AT command declare 2-cond virtual port, modulse response me OK.
Before, I had opened second port
<- AT#RSEN=1,1,0,2,10 TO first CMUX VIRTUAL PORT
->OK
The most interesing fact after response ‘OK’ module doesn’t send any connections requests but according datasheet it must send:
// On virtual COM 2
// Connection Request with Max Message Size = 300 (SIM Access Profile User Guide, page 14)
When I send AT command AT#RSEN=1,1,0,21,0 in CMUX mode to 2-cond CMUX firtual port and in AT command declare 2-cond virtual port, modulse response me ERROR.
Before, I had opened second port
<- AT#RSEN=1,1,0,2,10 TO second VIRTUAL PORT
-> ERROR
Hi Dmitriy,
sorry for my late but I also failed in the test as you and I fightened a lot …
only now I could be able to see my error ( and perhaps your?)
When opened a virtual channel on CMUX by default the RTD flag is set to 0.
This doesn’t matter when sending AT command since flow control is disabled, but the CONNECTION REQUEST behaves in the same way as for CONNECT mode so it use
One has not to care with the first two number in the last fieldm, which are used to differentiate the products … the important char is tha last one ie 5 or 6 ..
FW is
10.00.xy6 where:
10 set the HW platform
00 not used now
xy are used to recognixe the module type ( ie GL865 rather than GE864 ..)
6 is the FW version
Thank
you for your quick answer, I suspected it, but I wanted to know exact
answer, because the numeration isn’t too clear. So we will buy
modules with new versions.
Hi Augusto,
I guess you rised a question and answer from yourself 🙂
or if you need more help let me kknow
Hi Augusto,
I write down a page with a sample of MSC frame explained …
I hope cna be clòear and helpful for you and all guys browsing the forum ..
Hardware wise is I2C, for software protocols see here:
Of course if you are sending "F9 03 3F 01 1C F9" text is not OK, you must send the respective bytes Use a terminal which can handle hex, like Bray’s terminal.
We use cookies to enhance your browsing experience and help us improve our websites. To improve our website, we carefully select third parties that use cookies to allow us to serve specific content and achieve the purposes set out in our cookie policy. For more information on how to make adjustments through your browser to the cookies being used on your device, please click Find Out More link. By closing this banner or continuing to browse our website, you agree to our use of such cookies. FIND OUT MORE
Hi!
I’ve realized CMUX protocol on GL865 and it’s working. But I can’t run remote sim on the same virtual port from which I sent at command to enable Remote Sim. I want to use it without bluetooth only through USART. SAP server will be use only CMUX and USART.
When I send AT command AT#RSEN=1,1,0,2,10 in CMUX mode to 1-irst CMUX firtual port and in AT command declare 2-cond virtual port, modulse response me OK.
Before, I had opened second port
<- AT#RSEN=1,1,0,2,10 TO first CMUX VIRTUAL PORT
->OK
The most interesing fact after response ‘OK’ module doesn’t send any connections requests but according datasheet it must send:
// On virtual COM 2
// Connection Request with Max Message Size = 300 (SIM Access Profile User Guide, page 14)
When I send AT command AT#RSEN=1,1,0,21,0 in CMUX mode to 2-cond CMUX firtual port and in AT command declare 2-cond virtual port, modulse response me ERROR.
Before, I had opened second port
<- AT#RSEN=1,1,0,2,10 TO second VIRTUAL PORT
-> ERROR
Hi Dmitriy,
sorry for my late but I also failed in the test as you and I fightened a lot …
only now I could be able to see my error ( and perhaps your?)
When opened a virtual channel on CMUX by default the RTD flag is set to 0.
This doesn’t matter when sending AT command since flow control is disabled, but the CONNECTION REQUEST behaves in the same way as for CONNECT mode so it use
flow control.
So now I tried to rise it via MSC command
F9 03 EF 09 E3 05 0B 0D FB F9 //ch 2
and now it works!
I got the
F9 09 EF 19 00 01 00 00 00 00 00 02 01 2C 00 00 C3 F9
frame as expected.
I’ve done the same as you wrote and it works, but I have the next problem now.
When I’ve got a request to connection (third channel):
I send a connection response.
And after this module send me requests…such as SIM ON, SIM ATR
I send responses for this requests and ofter I sent SIM ATR, I got
a data to the first AT channel – "#RSEN: 1".
What I have to do that module will start send APDU requests ?
Hi Dmitriy,
once you estabuilish a data connection with your SIM you have to switch the PDU request to the remote SIM… and PDU from remote SIM to the module ..
The bluetooth connection emulate the SIM CARD data connection with the local SIM
It seems to me everything is working, the remote sim card was registreted.
But we have a module, telit GL-865QUAD, wich doesn’t support a configurable CMUX, but it would be great to make frame length longer.
In manual is written that if module answers:
AT+CMUX=?
+CMUX: (0),(0)
OK
in this case it isn’t configurable.
Could you tell me please, wich vesion of firmware(release) suports configurable CMUX?
If we know version of firmware wich supports configurable CMUX we will buy modules only with this firmware version.
Is it really to update firmware in our module?
Or which version we have to buy a module to have a configurable cmux?
Hi Dmitriy,
you can buy modules with 10.00.x06 FW version or upgrqade your own with this version.
So you can set length frame greater than 127; from AT user guide you see you need to set CPUMODE=3 to improve the size ..
Thank you for support.
My gsm module has 10.00.145 firmware version, and I reckon it’s greater than 10.00.x06 , but answer to the AT+CMUX=? command:
AT+CMUX: (0),(0)
But must be:
AT+CMUX: (0),(0),(5),(1-1509),(1-255),(0-100),(2-255),(1-255),(1-7)
Where is a problem, can you explain, please?
Hi Dimitry,
maybe it’s not too clear here.
FW 10.00.145 is older than 10.00.x06 ..
One has not to care with the first two number in the last fieldm, which are used to differentiate the products … the important char is tha last one ie 5 or 6 ..
FW is
10.00.xy6 where:
10 set the HW platform
00 not used now
xy are used to recognixe the module type ( ie GL865 rather than GE864 ..)
6 is the FW version
Thank
you for your quick answer, I suspected it, but I wanted to know exact
answer, because the numeration isn’t too clear. So we will buy
modules with new versions.
Hi Augusto,
I guess you rised a question and answer from yourself 🙂
or if you need more help let me kknow
Hi Augusto,
I write down a page with a sample of MSC frame explained …
I hope cna be clòear and helpful for you and all guys browsing the forum ..
Hardware wise is I2C, for software protocols see here:
http://mobileforensics.files.wordpress.com/2007/03/sim-card-protocols.pdf
Of course if you are sending "F9 03 3F 01 1C F9" text is not OK, you must send the respective bytes Use a terminal which can handle hex, like Bray’s terminal.
Please provide an exact log including timings.