AUTO_SIM on EM9291 Selects the wrong firmware package for MCC/MNC 302/480

Hello Semtech/Sierra Wireless,

I work for a small carrier in Canada. We have the very unfortunate displeasure of having the same MNC used by Verizon in the US - 480. You are not the first, and probably won’t be the last to have an issue in your firmware where, without checking the MCC you set the VERIZON firmware as soon as you see MNC 480. This breaks your device completely on our network as we don’t support weird “Verizon-ness”.

In the case of the EM9291 I have one here installed in a Ubiquiti UniFi5G Max device. We can see the IMSI of the installed SIM:

AT+CIMI
302480017122000

OK

Yep that’s 302480 (SSI Canada) , NOT 311480 (Verizon)

And yet we have:

AT!IMPREF?
!IMPREF:
 preferred fw version:    00.00.00.00
 preferred carrier name:  AUTO-SIM
 preferred config name:   AUTO-SIM_000.000_000
 preferred subpri index:  001
 current fw version:      03.04.10.01
 current carrier name:    VERIZON
 current config name:     VERIZON_040.025_001
 current subpri index:    001

When it should be GENERIC.

Please, please fix your firmware! We’re not a large carrier and not a direct customer of yours, but every single device that uses this module (and any others with this bug) will NEVER work on our network because we’re not Verizon!

Thanks!

have you contacted the distributor of your device?
Does it work if you set AT!IMPREF=“GENERIC”

We’ll try that too, but this isn’t really their issue. While they could override the incorrect firmware selection in the module the root cause of the issue lies here.

Yes it does work with the GENERIC firmware.

BTW, you can report to your product distributor first to get official fix of firmware

This is a Ubiquiti product. We will open a support ticket with them and hope they get official support, but I’m just trying to cover all the angles here in the hope someone can look at this. Ubiquiti is a big company and we may have a hard time getting their attention.

I very much doubt Ubiquiti’s front-line support agents will even have a clue what i’m talking about..

I have reported this issue internally

Thank you very much, it’s appreciated!