ELS61-US - not able to see 4G band 4 (1700/2100Mhz) | Telit Cinterion IoT Developer Community
November 15, 2018 - 4:40pm, 5889 views
We've found that the modem fails to scan (or camp on) cell towers in 4G Band 4.
We have a Telit LE910-NA1 that is able to camp on these cells without problem.
The Telit modem describes the tower as:
AT&T RSRP:-94 RSRQ:-9 TAC:5411 Id:29D7C17 EARFCN:2150 PWR:-61dBm DRX:0
ATI1 returns:
Cinterion ELS61-US REVISION 01.000 A-REVISION 00.014.00 OK
I notice there is a new version of f/w available for this modem, released in August. I can't find the release notes for this though - could you make them available, please.
Thanks
Just to elaborate:
I'm setting the bands:
AT^SCFG="Radio/Band/4G","0x81a"
^SCFG: "Radio/Band/4G","0x0000081A"
OK
The access technology:
AT^SXRAT=4,3
OK
And scanning:
AT^SNMON="INS",2
.......
OK
I can confirm that I get visible cell towers on most of the other bands, as expected.
Thanks again.
Hello,
There is an update possible to A-REVISION 00.026.00. I can send you release notes document for this version but there's nothing about such problems.
And have you tried to configure the only one LTE band and try if the module can register to LTE? Or is only that SNMON does not seem to scan this band? Do you deregister from the network before scanning with AT^SNMON="INS",2 command?
I suppose that you were testing Telit in the same place and SIM.
Regards,
Bartłomiej
Hello, Thanks for your response.
The attached log is taken from the same modem model (ELS61-US) but taken in the UK, that is why there are no cells listed. This log shows the sequence that the modem is going through.
Yes, I have tried setting the module to just this band and all bands it doesn't show any cells for 4G band 4.
Yes, I am deregistering first, I can see cells for all the other bands.
Yes, the Telit device is being used in the same location with the same SIM.
Please could you send the release notes - I think my email address is linked to this account?
Regards
Steve
I have sent you the release notes documents.
Please also test if the module can register to LTE band 4 in US.
Regards,
Bartłomiej
Thanks for the documentation, but you don't appear to have included release notes for the latest f/w release - v2.002 (see attached image).
Sorry, I didn't realise that I'd not been clear from the start. The testing we've done has been in the US; in Ohio & Kentucky. The log that I sent was taken from an ELS61-US which is in the UK, as I'm unable to get a log from the US. The AT command sequence is the same though.
To re-iterate the ELS61-US does not see and will not camp on LTE Band 4 towers in the US.
Regards
Steve
Hello,
So you have access to release notes. I didn't attach release note document for revision 2 because you have revision 1 module.
I was only able to see in the log that you test the network with AT^SNMON="INS",2 command but didn't see any checks if the module was able to register to LTE when the mask “0x00000008“ was set - that's why I was asking about it.
Anyway this problem would require some testing. I'm not located in US and I can't verify it myself. I think that in such case when you suspect that there may be something incorrect with the module's behavior you could report it to Gemalto support - it would then be assigned to US team and you'd be able to communicate with them directly. But before that you should update the module to the latest firmware available for revision 1 and test again.
Best regards,
Bartłomiej
Hi Bartlomiej
Thanks, I didn't notice the v2 was for h/w version.
Ok. I'll get the module updated and then come back.
Regards
Steve
It's not the general rule but for this module revision 2 ***** a dedicated hardware.
BR,
Bartłomiej
Hi Bartlomiej
We've updated the f/w on a ELS61-US from A-REVISION 00.014.00 to A-REVISION 00.026.00.
I did a final check before the update and a check after the update. After the update cell towers on LTE band 4 were seen and connected to.
I've attached a log of scanning the cell towers before/after the f/w update.
I would be very interested to hear what Gemalto know about this fault. Is this a known fault? If it is then why wasn't it included on the release notes. If it isn't then has it been fixed?
It occurs to me that what we see here could just be an accidental change to the f/w that only makes the problem less bad without actually fixing it. How can we be sure that this issue will not be seen elsewhere in the US?
Regards
Steve
Hi Bartlomiej
Is there any news on this, yet?
Thanks again
Steve
Pages