16 thoughts on “Telit GE865-QUAD – 3rd channel not operational?”
Hello There,
I am using a Telit GE865-QUAD installed with firmware version v10.00.003.
I am currently evaluating the use of multiplexing within our product and have a working CMUX protocol that meets the Basic requirements of the ETSI 07.10 specification.
As I understand the Telit GE865-QUED supports 3 virtual channels with a 4 channel for Python debugging. The problem is I am unable to get the 3rd channel to operate as the module reports a DM frame which equates to a decline.
However I am still left with a problem as all our production units are installed with firmware revision 10.00.003, hence it would more convenient at the moment to stick with this version instead of a making a bold change.
Hello Lucia,
Do you have the latest change control document along with the AT command document for firmware v10.01.000?
Hello Dharmesh,
do you mean hte delta SW?
do you have acces to Telit download zone?
Yes I am talking about the delta file.
Unfortunately I don’t have access to the download zone.
I understand your position, but let me explain mine.
Here the aCMUX is working also with the same old version you have, so to be honest with you, I have no clue ..
Maybe, for test purpose, you can try to downgrade the working module to the old FW and see what happens. If it still fail the only idea I have is to keep the newest version, sorry.
Hello, Luca,
Thank you for your quick response and the links to the requested files.
As you are already aware I am in an awkward position at the moment as the new firmware is of little use unless we upgrade our production units – hence the need for the data document.
To sell the overall concept I would need 3 channels otherwise It is just not worth the extra effort.
Question is why does version 10.01.000 work and 10.00.003 does not?
Also what happens to the NVM when the softare is upgraded/downgraded…? And does this have any affect on the operation of CMUX?
I don’t have firmware 10.00.003 as file. Are you able to send me a link?
Unfortunately
this opens up an ENTIRELY NEW discussion as the factory version functions
differently compared to the self programmed version. This would explain why you
are seeing a correctly operating 10.00.003 and why I ‘as an end user’ am not? –
Because you would just re-programme your unit to the appropriate version and
run the test? – You are not actually using a module installed with 10.00.003
that was programmed by the Factory.
This
outcome also means that other areas of the firmware could function differently
depending on how the firmware has been programmed…
Please can
you confirm if there are any other differences between the factory version and
the .bin version? As this is concerning.
With regards
to CMUX, It would not be practical to program each of the modules using Xfp.
Hello Luca,
I have now
downgraded my module to a 10.00.003 and surprise surprise the 3rd channel is
now operational!
Unfortunately
this opens up an ENTIRELY NEW discussion as the factory version functions
differently compared to the self programmed version. This would explain why you
are seeing a correctly operating 10.00.003 and why I ‘as an end user’ am not? –
Because you would just re-programme your unit to the appropriate version and
run the test? – You are not actually using a module installed with 10.00.003
that was programmed by the Factory.
This
outcome also means that other areas of the firmware could function differently
depending on how the firmware has been programmed…
Please can
you confirm if there are any other differences between the factory version and
the .bin version? As this is concerning.
With regards
to CMUX, It would not be practical to program each of the modules using Xfp.
Hi Dharmesh,
This is very strange to me indeed.
Did you test only one module in this way or also others?
And also, ALL your modules are suffering for this problem?
Can you write me a list ( as much as you can ) of IMEI code out from failed modules?
IMEI Ccna be read on the top cover or by means of AT+CGSN command.
Hello Luca,
I tested 2 modules that were factory programmed with 10.00.003 before re-programming one of them wih 10.00.003 with Xfp.
A third module was alreadly programmed with 10.00.005 and was re-programmed with 10.01.000.
Note: firmware 10.00.005 also suffered from the same problem.
Hi Dharmesh,
I can’t understand why you can’t ..
here below my log with the same FW version.
9/06/2014 09:34:56.532 [TX] – AT#SELINT=2<CR><LF>
09/06/2014 09:34:56.539 [RX] – AT#SELINT=2<CR><LF>
<CR><LF>
OK<CR><LF>
09/06/2014 09:34:56.560 [TX] – ATE0<CR><LF>
09/06/2014 09:34:56.571 [RX] – ATE0<CR><LF>
<CR><LF>
OK<CR><LF>
09/06/2014 09:34:56.590 [TX] – AT&S0&D2&K3+IPR=115200<CR><LF>
09/06/2014 09:34:56.603 [RX] – <CR><LF>
OK<CR><LF>
09/06/2014 09:34:56.608 [TX] – AT+CMUX=0<CR><LF>
09/06/2014 09:34:56.619 [RX] – <CR><LF>
OK<CR><LF>
——————————————
Opening 3 virtual channel
——————————————
09/06/2014 09:34:56.639 [TX] – F9 03 3F 01 1C F9
09/06/2014 09:34:56.651 [RX] – F9 03 73 01 D7 F9
Opening ch1
09/06/2014 09:34:58.657 [TX] – F9 07 3F 01 DE F9
09/06/2014 09:34:58.682 [RX] – F9 07 73 01 15 F9 F9 03 EF 09 E1 05 07 0C FB F9
Opening ch2
09/06/2014 09:34:58.878 [TX] – F9 0B 3F 01 59 F9
09/06/2014 09:34:58.890 [RX] – F9 0B 73 01 92 F9 F9 03 EF 09 E1 05 0B 0C FB F9
Opening ch3
09/06/2014 09:34:59.103 [TX] – F9 0F 3F 01 9B F9
09/06/2014 09:34:59.114 [RX] – F9 0F 73 01 50 F9 F9 03 EF 09 E1 05 0F 0C FB F9
Do you set teh same before sending AT+CMUX=0 (evemn if I can’t se the reason to fail only third ch … )
Hello Luca
Thankyou for your reply,
Currently I have no device specific initialisation. However I can tell you from my experience of Telit 865 that it always starts you as #SELINT 2.
I have now implemented the same initialisation commands as shown in your example but I am still getting a decline from the Telit module:
Tx [09:38:34]: 41 54 0d 0a AT..
Rx [09:38:36]: 0d 0a 4f 4b 0d 0a ..OK..
Tx [09:38:36]: 41 54 23 53 45 4c 49 4e 54 3d 32 0d 0a AT#SELINT=2..
Tx [09:38:36]: 41 54 45 30 0d 0a ATE0..
Rx [09:38:37]: 0d 0a 4f 4b 0d 0a ..OK..
Tx [09:38:38]: 41 54 26 53 30 26 44 32 26 4b 33 0d 0a AT&S0&D2&K3..
Rx [09:38:38]: 0d 0a 4f 4b 0d 0a ..OK..
Tx [09:38:39]: 41 54 2b 43 4d 55 58 3d 30 0d 0a AT+CMUX=0..
Rx [09:38:39]: 0d 0a 4f 4b 0d 0a ..OK..
Tx [09:38:41]: f9 03 3f 01 1c f9 ; Ch0 enable Req.
Rx [09:38:41]: f9 03 73 01 d7 f9 ; Ch0 enable Ack.
Tx [09:38:42]: f9 07 3f 01 de f9 ; Ch1 enable Req.
Rx [09:38:42]: f9 07 73 01 15 f9 f9 03 ef 09 e1 05 07 0c fb f9 ; Ch1 enable Ack.
Tx [09:38:43]: f9 0b 3f 01 59 f9 ; Ch2 enable Req.
Rx [09:38:43]: f9 0b 73 01 92 f9 f9 03 ef 09 e1 05 0b 0c fb f9 ; Ch2 enable Ack.
Tx [09:38:44]: f9 0f 3f 01 9b f9 ; Ch3 enable Req.
Rx [09:38:44]: f9 0f 1f 01 b1 f9 ; Ch3 enable Declined.
Is there something more to this? Reference the enclosed document.
Hi Dharmes,
this is a really mystery .. I’ve never seen something similar.
Also, going overand over the source code I can see the only one point where the DM frame
is sent happens in case of a DLCI not available ie greater than 3 …
Can you kyndly try the lates FW and see what happens?
You can download it from here: https://tcloud.telit.com/public.php?service=files&t=0e36918f746a00616a7659aa4ec654ef
Hello Luca,
Thankyou for your help.
I have updated my module to the latest firmware and once again initaited the CMUX protocol:
Tx [16:14:30]: 41 54 0d 0a AT..
Rx [16:14:30]: 0d 0a 4f 4b 0d 0a ..OK..
Tx [16:14:31]: 41 54 2b 47 4d 49 0d 0a AT+GMI..
Rx [16:14:31]: 0d 0a 54 65 6c 69 74 0d 0a 0d 0a 4f 4b 0d 0a ..Telit….OK..
Tx [16:14:32]: 41 54 2b 47 4d 52 0d 0a AT+GMR..
Rx [16:14:32]: 0d 0a 31 30 2e 30 31 2e 30 30 30 0d 0a 0d 0a 4f 4b 0d 0a ..10.01.000….OK..
Rx [16:14:33]: 0d 0a 4f 4b 0d 0a ..OK..
Tx [16:14:33]: 41 54 23 53 45 4c 49 4e 54 3d 32 0d 0a AT#SELINT=2..
Tx [16:14:34]: 41 54 45 30 0d 0a ATE0..
Rx [16:14:34]: 0d 0a 4f 4b 0d 0a ..OK..
Tx [16:14:35]: 41 54 26 44 32 26 4b 33 0d 0a AT&D2&K3..
Rx [16:14:35]: 0d 0a 4f 4b 0d 0a ..OK..
Tx [16:14:36]: 41 54 2b 43 4d 55 58 3d 30 0d 0a AT+CMUX=0..
Rx [16:14:36]: 0d 0a 4f 4b 0d 0a ..OK..
Tx [16:14:38]: f9 03 3f 01 1c f9 ; Ch0 enable Req.
Rx [16:14:38]: f9 03 73 01 d7 f9 ; Ch0 enable Ack.
Tx [16:14:39]: f9 07 3f 01 de f9 ; Ch1 enable Req.
Rx [16:14:39]: f9 07 73 01 15 f9 f9 03 ef 09 e1 05 07 0c fb f9 ; Ch1 enable Ack.
Tx [16:14:40]: f9 0b 3f 01 59 f9 ; Ch2 enable Req.
Rx [16:14:40]: f9 0b 73 01 92 f9 f9 03 ef 09 e1 05 0b 0c fb f9 ; Ch2 enable Ack.
Tx [16:14:41]: f9 0f 3f 01 9b f9 ; Ch3 enable Req.
Rx [16:14:41]: f9 0f 73 01 50 f9 f9 03 ef 09 e1 05 0f 0c fb f9 ; Ch3 enable Ack.
As you can see channel 3 does work as expected.
However I am still left with a problem as all our production units are installed with firmware revision 10.00.003, hence it would more convenient at the moment to stick with this version instead of a making a bold change.
Hello Lucia,
Do you have the latest change control document along with the AT command document for firmware v10.01.000?
Hello Dharmesh,
do you mean hte delta SW?
do you have acces to Telit download zone?
Yes I am talking about the delta file.
Unfortunately I don’t have access to the download zone.
Can you do the honours??
Hi,
here the link to download a zip with the deltaSW.
https://tcloud.telit.com/public.php?service=files&t=ffec4a0d11fffb3a6c2f5dbc38a301cf
and here the latest AT user guide.
https://tcloud.telit.com/public.php?service=files&t=fee7d9a94c9ec7e776597a3115c6a81c
for what concern your problem ..
I understand your position, but let me explain mine.
Here the aCMUX is working also with the same old version you have, so to be honest with you, I have no clue ..
Maybe, for test purpose, you can try to downgrade the working module to the old FW and see what happens. If it still fail the only idea I have is to keep the newest version, sorry.
Hello, Luca,
Thank you for your quick response and the links to the requested files.
As you are already aware I am in an awkward position at the moment as the new firmware is of little use unless we upgrade our production units – hence the need for the data document.
To sell the overall concept I would need 3 channels otherwise It is just not worth the extra effort.
Question is why does version 10.01.000 work and 10.00.003 does not?
Also what happens to the NVM when the softare is upgraded/downgraded…? And does this have any affect on the operation of CMUX?
I don’t have firmware 10.00.003 as file. Are you able to send me a link?
here is the stream:
https://tcloud.telit.com/public.php?service=files&t=172a20cfe4caa9095cd3fb5d594be2a4
as I told you both version are working here, so I really don’t understand why your is not.
When you chabnge the FW the NVM will contain the new FW …
this no affect the CMUX operation, unless you downgrade to the very oldest FW where CMUX was not implemented.
Hello Luca,
I have now
downgraded my module to a 10.00.003 and surprise surprise the 3rd channel is
now operational!
See log
below:
Tx
[15:53:09]: 41 54 0d 0a
AT..
Rx
[15:53:09]: 0d 0a 4f 4b 0d 0a
..OK..
Tx
[15:53:10]: 41 54 2b 47 4d 49 0d 0a
AT+GMI..
Rx
[15:53:10]: 0d 0a 54 65 6c 69 74 0d 0a 0d 0a 4f 4b 0d 0a
..Telit….OK..
Tx
[15:53:11]: 41 54 2b 47 4d 52 0d 0a
AT+GMR..
Rx
[15:53:11]: 0d 0a 31 30 2e 30 30 2e 30 30 33 0d 0a 0d 0a 4f 4b 0d 0a ..10.00.003….OK..
Tx
[15:53:12]: 41 54 23 53 45 4c 49 4e 54 3d 32 0d 0a
AT#SELINT=2..
Rx
[15:53:12]: 0d 0a 4f 4b 0d 0a
..OK..
Tx
[15:53:13]: 41 54 45 30 0d 0a
ATE0..
Rx
[15:53:13]: 0d 0a 4f 4b 0d 0a
..OK..
Tx
[15:53:14]: 41 54 26 53 30 26 44 32 26 4b 33 0d 0a
AT&S0&D2&K3..
Rx
[15:53:14]: 0d 0a 4f 4b 0d 0a
..OK..
Tx
[15:53:15]: 41 54 2b 43 4d 55 58 3d 30 0d 0a
AT+CMUX=0..
Rx
[15:53:15]: 0d 0a 4f 4b 0d 0a
..OK..
Tx
[15:53:17]: f9 03 3f 01 1c f9
;
Ch0 enable Req.
Rx
[15:53:17]: f9 03 73 01 d7 f9
; Ch0
enable Ack.
Tx
[15:53:18]: f9 07 3f 01 de f9 ;
Ch1 enable Req.
Rx
[15:53:18]: f9 07 73 01 15 f9 f9 03 ef 09 e1 05 07 0c fb f9 ;
Ch1 enable Ack.
Tx
[15:53:19]: f9 0b 3f 01 59 f9
;
Ch2 enable Req.
Rx
[15:53:19]: f9 0b 73 01 92 f9 f9 03 ef 09 e1 05 0b 0c fb f9 ;
Ch2 enable Ack.
Tx
[15:53:20]: f9 0f 3f 01 9b f9 ;
Ch3 enable Req.
Rx
[15:53:20]: f9 0f 73 01 50 f9 f9 03 ef 09 e1 05 0f 0c fb f9 ;
Ch3 enable Ack.
Unfortunately
this opens up an ENTIRELY NEW discussion as the factory version functions
differently compared to the self programmed version. This would explain why you
are seeing a correctly operating 10.00.003 and why I ‘as an end user’ am not? –
Because you would just re-programme your unit to the appropriate version and
run the test? – You are not actually using a module installed with 10.00.003
that was programmed by the Factory.
This
outcome also means that other areas of the firmware could function differently
depending on how the firmware has been programmed…
Please can
you confirm if there are any other differences between the factory version and
the .bin version? As this is concerning.
With regards
to CMUX, It would not be practical to program each of the modules using Xfp.
Hello Luca,
I have now
downgraded my module to a 10.00.003 and surprise surprise the 3rd channel is
now operational!
See log
below:
Tx
[15:53:09]: 41 54 0d 0a
AT..
Rx
[15:53:09]: 0d 0a 4f 4b 0d 0a
..OK..
Tx
[15:53:10]: 41 54 2b 47 4d 49 0d 0a
AT+GMI..
Rx
[15:53:10]: 0d 0a 54 65 6c 69 74 0d 0a 0d 0a 4f 4b 0d 0a
..Telit….OK..
Tx
[15:53:11]: 41 54 2b 47 4d 52 0d 0a
AT+GMR..
Rx
[15:53:11]: 0d 0a 31 30 2e 30 30 2e 30 30 33 0d 0a 0d 0a 4f 4b 0d 0a ..10.00.003….OK..
Tx
[15:53:12]: 41 54 23 53 45 4c 49 4e 54 3d 32 0d 0a
AT#SELINT=2..
Rx
[15:53:12]: 0d 0a 4f 4b 0d 0a
..OK..
Tx
[15:53:13]: 41 54 45 30 0d 0a
ATE0..
Rx
[15:53:13]: 0d 0a 4f 4b 0d 0a
..OK..
Tx
[15:53:14]: 41 54 26 53 30 26 44 32 26 4b 33 0d 0a
AT&S0&D2&K3..
Rx
[15:53:14]: 0d 0a 4f 4b 0d 0a
..OK..
Tx
[15:53:15]: 41 54 2b 43 4d 55 58 3d 30 0d 0a
AT+CMUX=0..
Rx
[15:53:15]: 0d 0a 4f 4b 0d 0a
..OK..
Tx
[15:53:17]: f9 03 3f 01 1c f9
;
Ch0 enable Req.
Rx
[15:53:17]: f9 03 73 01 d7 f9
; Ch0
enable Ack.
Tx
[15:53:18]: f9 07 3f 01 de f9 ;
Ch1 enable Req.
Rx
[15:53:18]: f9 07 73 01 15 f9 f9 03 ef 09 e1 05 07 0c fb f9 ;
Ch1 enable Ack.
Tx
[15:53:19]: f9 0b 3f 01 59 f9
;
Ch2 enable Req.
Rx
[15:53:19]: f9 0b 73 01 92 f9 f9 03 ef 09 e1 05 0b 0c fb f9 ;
Ch2 enable Ack.
Tx
[15:53:20]: f9 0f 3f 01 9b f9 ;
Ch3 enable Req.
Rx
[15:53:20]: f9 0f 73 01 50 f9 f9 03 ef 09 e1 05 0f 0c fb f9 ;
Ch3 enable Ack.
Unfortunately
this opens up an ENTIRELY NEW discussion as the factory version functions
differently compared to the self programmed version. This would explain why you
are seeing a correctly operating 10.00.003 and why I ‘as an end user’ am not? –
Because you would just re-programme your unit to the appropriate version and
run the test? – You are not actually using a module installed with 10.00.003
that was programmed by the Factory.
This
outcome also means that other areas of the firmware could function differently
depending on how the firmware has been programmed…
Please can
you confirm if there are any other differences between the factory version and
the .bin version? As this is concerning.
With regards
to CMUX, It would not be practical to program each of the modules using Xfp.
Hi Dharmesh,
This is very strange to me indeed.
Did you test only one module in this way or also others?
And also, ALL your modules are suffering for this problem?
Can you write me a list ( as much as you can ) of IMEI code out from failed modules?
IMEI Ccna be read on the top cover or by means of AT+CGSN command.
Hello Luca,
I tested 2 modules that were factory programmed with 10.00.003 before re-programming one of them wih 10.00.003 with Xfp.
A third module was alreadly programmed with 10.00.005 and was re-programmed with 10.01.000.
Note: firmware 10.00.005 also suffered from the same problem.
Do you have an email address??
Does anyone have any clues on this??