EM7565 Firmware Problems with CA?

IoT Modules MC/EM Series
1

Hello,

now my module is working great in my Turris Omnia. But i have another Problem.
RSRP show me some interesting things…

ok lets take a look:
CA is B1+B3 for my provider…

at!gstatus?
!GSTATUS:
Current Time:  435781           Temperature: 50
Reset Counter: 1                Mode:        ONLINE
System mode:   LTE              PS state:    Attached
LTE band:      B1               LTE bw:      10 MHz
LTE Rx chan:   397              LTE Tx chan: 18397
LTE SSC1 state:ACTIVE           LTE SSC1 band: B3
LTE SSC1 bw  : Unknown          LTE SSC1 chan: 1875
LTE SSC2 state:NOT ASSIGNED
LTE SSC3 state:NOT ASSIGNED
LTE SSC4 state:NOT ASSIGNED
EMM state:     Registered       Normal Service
RRC state:     RRC Connected
IMS reg state: No Srv

PCC RxM RSSI:  -97              PCC RxM RSRP:  -93
PCC RxD RSSI:  -57              PCC RxD RSRP:  -83
SCC1 RxM RSSI: -98              SCC1 RxM RSRP: -134
SCC1 RxD RSSI: -58              SCC1 RxD RSRP: -83
Tx Power:      -2               TAC:         x(x)
RSRQ (dB):     -6.7             Cell ID:     x(x)
SINR (dB):     28.2

SCC1 RxM RSRP: -134 ?? This is not possible…

Speedtest shows me:

Ok, CA is working, but not really good?? Why? ok, i will show you…

Here is the output of B1 and B3 alone:
Take a look at the RSRP! all fine…

at!gstatus?
!GSTATUS:
Current Time:  438121           Temperature: 46
Reset Counter: 1                Mode:        ONLINE
System mode:   LTE              PS state:    Attached
LTE band:      B1               LTE bw:      10 MHz
LTE Rx chan:   397              LTE Tx chan: 18397
LTE SSC1 state:NOT ASSIGNED
LTE SSC2 state:NOT ASSIGNED
LTE SSC3 state:NOT ASSIGNED
LTE SSC4 state:NOT ASSIGNED
EMM state:     Registered       Normal Service
RRC state:     RRC Connected
IMS reg state: No Srv

PCC RxM RSSI:  -65              PCC RxM RSRP:  -92
PCC RxD RSSI:  -57              PCC RxD RSRP:  -83
Tx Power:      8                TAC:         x (x)
RSRQ (dB):     -7.2             Cell ID:     x (x)
SINR (dB):     26.2

Speedtest shows me:

B3 alone:
RSRP is fine!

at!gstatus?
!GSTATUS:
Current Time:  438322           Temperature: 43
Reset Counter: 1                Mode:        ONLINE
System mode:   LTE              PS state:    Attached
LTE band:      B3               LTE bw:      15 MHz
LTE Rx chan:   1875             LTE Tx chan: 19875
LTE SSC1 state:NOT ASSIGNED
LTE SSC2 state:NOT ASSIGNED
LTE SSC3 state:NOT ASSIGNED
LTE SSC4 state:NOT ASSIGNED
EMM state:     Registered       Normal Service
RRC state:     RRC Connected
IMS reg state: No Srv

PCC RxM RSSI:  -69              PCC RxM RSRP:  -98
PCC RxD RSSI:  -55              PCC RxD RSRP:  -82
Tx Power:      16               TAC:         x (x)
RSRQ (dB):     -9.3             Cell ID:     x (x)
SINR (dB):     22.8

Speedtest shows me:

CA have a problem? Firmware has a problem? i am confused
Checking Speed with my Smatphone (Pixel2) - This shows me ~130 mbit download at the same place … and it has the same modem inside.

2

I have the exact same problem. Same module, provider and bands as well. There seems to be something wrong with RxM reception while in B1+B3 CA mode. Other people with the exact same configuration have this problem too.

PCC = B3 (BW: 15 MHz, DL EARFCN: 1875)
SCC1 = B1 (BW: 10 MHz, DL EARFCN: 397)

PCC RxM RSSI:  -101             PCC RxM RSRP:  -85  <-- Why is the RSSI -101 dBm?
PCC RxD RSSI:  -61              PCC RxD RSRP:  -79
SCC1 RxM RSSI: -100             SCC1 RxM RSRP: -134 <-- What's wrong with the RSRP?
SCC1 RxD RSSI: -56              SCC1 RxD RSRP: -79

I have been shown the correct RSRP values exactly once and got about ~ 30 Mbit/s of better downlink speeds:

PCC RxM RSSI:  -58              PCC RxM RSRP:  -80
PCC RxD RSSI:  -56              PCC RxD RSRP:  -80
SCC1 RxM RSSI: -51              SCC1 RxM RSRP: -78
SCC1 RxD RSSI: -49              SCC1 RxD RSRP: -75

Then I let the connection into the idle modle (RRC released) and the same thing with RxM happened again. I haven’t seen the correct RSRP again since then.

Is there any way to talk to the EM7565 development team? Or will they see this? This seems to be a major issue. It looks to like the module tries to use a non-existant antenna (since the X16 actually supports 4x4 MIMO). Or there is something else wrong.

There appears to be a problem with the CQI received via the SDK as well.

CQI2 is always 255 for some reason.

CQI1: 15, CQI2: 255
RSRP: -79, RSRQ: -8, RSSI: -52, SINR: 27.0, TX: -11.0

Also, is there any way to figure out whether QAM 256 DL is active? There are two versions of the CQI. One with up to 64 QAM and one up to 256 QAM. Both range from 1 to 15. How do I know which version of the CQI is active? Our provider claims to support 256 QAM nation wide.

Firmware Version:

ATI
Manufacturer: Sierra Wireless, Incorporated
Model: EM7565
Revision: SWI9X50C_01.00.02.00 6ff48a jenkins 2017/09/29 05:54:26
3

Operating within the same environment (module, provider and bands) I habe the same phenomena as @sin10 and @unknown.

gstatus shows:

at!gstatus?
!GSTATUS: 
Current Time:  251406           Temperature: 38
Reset Counter: 1                Mode:        ONLINE         
System mode:   LTE              PS state:    Attached     
LTE band:      B3               LTE bw:      15 MHz  
LTE Rx chan:   1875             LTE Tx chan: 19875
LTE SSC1 state:ACTIVE           LTE SSC1 band: B1     
LTE SSC1 bw  : Unknown          LTE SSC1 chan: 397
LTE SSC2 state:NOT ASSIGNED
LTE SSC3 state:NOT ASSIGNED
LTE SSC4 state:NOT ASSIGNED
EMM state:     Registered       Normal Service 
RRC state:     RRC Connected  
IMS reg state: No Srv   

PCC RxM RSSI:  -100             PCC RxM RSRP:  -90
PCC RxD RSSI:  -68              PCC RxD RSRP:  -80
SCC1 RxM RSSI: -100             SCC1 RxM RSRP: -137
SCC1 RxD RSSI: -64              SCC1 RxD RSRP: -88
Tx Power:      -2               TAC:         27b3 (10163)
RSRQ (dB):     -6.4             Cell ID:     xxxxxxxxx
SINR (dB):     27.2

OK

Best regards,
Monty

4

Its the same for me. B3 + B1 does a strange behaviour.

RSRP-Main of SSC1 is anywhere below others where it can’t be in real.
All RSSI are so far apart that this also can’t correspond to reality. (In Addition RSSI of Main-Band is Jumping all over the chart)

The following charts are created with the output of the command “AT!GSTATUS?”



1 Like
5

Hello, We cant get our EM7565 firmware to work with the test sim we obtained.

What firmware are you using? The generic one that came loaded does not seem to work.

What test sim or network sim are you using?

Thanks,

Bill

6

We are using the pre-installed pre-certified Generic version.

Model: EM7565
Revision: SWI9X50C_01.00.02.00 6ff48a jenkins 2017/09/29 05:54:26

We are all on Drei Österreich / Three Austria or simply “3”.

Please consider opening a new thread.

7

Hello Support Team,

same Situation here. Does anybody know when there will be a firmware update and when the module is integrated into FOTA?

Thank you,

Michael

8

Same with me. Only getting 41+41. I should be getting 41+41+41. Please let us know something. I spent a lot of money on a cat 12 that only does cat 6.

9

Any update on this?

10

Guys,

Just to answer the firmware availability question, the current build is release 7 (1.2.1), release 8 is scheduled to be out next week sometime which is intended to be the candidate release to start operator approvals with. As normal you need to go through your commercial channel to get your hands on newer firmware releases.

Regards

Matt

11

So no release on source.sierrawireless? Why not?

12

Because it is not declared as commercially available and hence we do not have a fully approved release yet for the M2M versions.

Regards

Matt

13

CA is still broken @ B1+B3 and 256 QAM doesn’t seem to work either (Operator: Hutchison Drei Austria / MCCMNC: 23210).

Revision: SWI9X50C_01.02.01.00 e84ea4 jenkins 2017/11/01 19:34:14
!GSTATUS: 
Current Time:  566              Temperature: 38
Reset Counter: 1                Mode:        ONLINE         
System mode:   LTE              PS state:    Attached     
LTE band:      B3               LTE bw:      15 MHz  
LTE Rx chan:   1875             LTE Tx chan: 19875
LTE SSC1 state:ACTIVE           LTE SSC1 band: B1     
LTE SSC1 bw  : Unknown          LTE SSC1 chan: 397
LTE SSC2 state:NOT ASSIGNED
LTE SSC3 state:NOT ASSIGNED
LTE SSC4 state:NOT ASSIGNED
EMM state:     Registered       Normal Service 
RRC state:     RRC Connected  
IMS reg state: No Srv   

PCC RxM RSSI:  -97              PCC RxM RSRP:  -73
PCC RxD RSSI:  -54              PCC RxD RSRP:  -77
SCC1 RxM RSSI: -95              SCC1 RxM RSRP: -120
SCC1 RxD RSSI: -50              SCC1 RxD RSRP: -74
Tx Power:      -15              TAC:         .... (....)
RSRQ (dB):     -7.6             Cell ID:     .... (....)
SINR (dB):     24.6
14

I can confirm @unknown’s findings using the new firmware.

Regards,
Monty

15

For the EM7455, B1 + B3 was not a supported combination, only (B1 + B8), (B3 + B7) or (B3 + B2) (and some more outside Europe), as noted in the PTS.

For the 7565, the PTS lists no band combinations yet, so (B1 + B3) support TBD, especially regarding supported BW and modulation.

16

R6 lists the supported band combinations (Feb. 18). And as I already noted in a previous post, all four streams work from time to time (very rarely), but not consistently.

17 
PCC RxM RSSI:  -54              PCC RxM RSRP:  -74
PCC RxD RSSI:  -57              PCC RxD RSRP:  -77
SCC1 RxM RSSI: -46              SCC1 RxM RSRP: -72
SCC1 RxD RSSI: -49              SCC1 RxD RSRP: -75
Tx Power:      -14              TAC:         .. (..)
RSRQ (dB):     -8.7             Cell ID:     ... (...)
SINR (dB):     21.0

All four streams are working at the moment. But letting the connection into idle will cause breakage again. Will we ever see a fix for this + 256 QAM? I see B1+B3 as supported in the document. My mobile UE works flawlessly with the same network and 256 QAM works as well.

18

All,

FYI there is a a new PTS which is about to be posted to the source which has a great big table listing of all of the CA combo’s.

Regards

Matt

19

That doesn’t solve the problem though. We already know that B1+B3 is supported.

20

Still struggeling with this issue. Is there any roadmap for a firmware with fixing B1+B3?