Boron404X cellular connectivity issue

rizwan23 · April 13, 2023, 2:32pm

I have a few particle Boron404X boards. I have same software on few units with os 4.0.2. All boards are currently in test phase and found 2 boards connects without any issue while other boards have problem with cellular connectivity.
Now I have swapped battery/usb power / sim card etc but it is always same boards that connects without any issue while others fail to connect.
Following is the log for both with good connection and bad connection.
Any input would be greatly appreciated.

Good Connection Board

-----------Power Up ---------------

0000000369 [app] INFO: Strating setup.

Activated external SIM :
End OF Setup
0000000375 [system.nm] INFO: State changed: DISABLED → IFACE_DOWN
0000000380 [system.nm] INFO: State changed: IFACE_DOWN → IFACE_REQUEST_UP
0000000386 [ncp.client] TRACE: Powering modem on, ncpId: 0x47
0000000392 [ncp.client] TRACE: Modem already on
0000000397 [ncp.client] TRACE: Setting UART voltage translator state 1
0000000403 [system.nm] INFO: State changed: IFACE_REQUEST_UP → IFACE_UP
0000000409 [app] INFO: deviceID=e00fce68d1f646bcdaa8d166
Device ID : e00fce68d1f646bcdaa8d166
0000000503 [ncp.client] TRACE: Setting UART voltage translator state 0
0000000604 [ncp.client] TRACE: Setting UART voltage translator state 1
0000000605 [ncp.client] TRACE: Muxer is not currently running
0000000611 [ncp.client] TRACE: Initialized muxer @ 460800 baudrate
0000000616 [mux] INFO: Starting GSM07.10 muxer
0000000623 [mux] INFO: GSM07.10 muxer thread started
0000000630 [ncp.client] TRACE: Resumed muxed session
0000000631 [mux] INFO: Openning mux channel 1
0000000682 [ncp.at] TRACE: > AT
0000000686 [ncp.at] TRACE: < OK
0000000686 [ncp.client] TRACE: NCP ready to accept AT commands
0000000690 [ncp.at] TRACE: > AT
0000000693 [ncp.at] TRACE: < OK
0000000696 [ncp.at] TRACE: > ATI9
0000000699 [ncp.at] TRACE: < 03.15,A00.01
0000000704 [ncp.at] TRACE: < OK
0000000706 [ncp.client] TRACE: App firmware: 1
0000000710 [ncp.at] TRACE: > AT+UGPIOC?
0000000715 [ncp.at] TRACE: < +UGPIOC:
0000000717 [ncp.at] TRACE: < 16,255
0000000721 [ncp.at] TRACE: < 19,255
0000000723 [ncp.at] TRACE: < 23,0
0000000726 [ncp.at] TRACE: < 24,255
0000000729 [ncp.at] TRACE: < 25,255
0000000732 [ncp.at] TRACE: < 33,255
0000000738 [ncp.at] TRACE: < 42,255
0000000740 [ncp.at] TRACE: < 46,255
0000000743 [ncp.at] TRACE: < OK
0000000746 [ncp.at] TRACE: > AT+UGPIOR=23
0000000749 [ncp.at] TRACE: < +UGPIOR: 23,0
0000000754 [ncp.at] TRACE: < OK
0000000756 [ncp.client] INFO: Using external Nano SIM card
0000000760 [ncp.at] TRACE: > AT+CPIN?
0000000765 [ncp.at] TRACE: < +CPIN: READY
0000000768 [ncp.at] TRACE: < OK
0000000771 [ncp.at] TRACE: > AT+CCID
0000000819 [ncp.at] TRACE: < +CCID: 89610185002844769463
0000000819 [ncp.at] TRACE: < OK
0000000825 [ncp.at] TRACE: > AT+IFC?
0000000829 [ncp.at] TRACE: < +IFC: 2,2
0000000830 [ncp.at] TRACE: < OK
0000000832 [ncp.at] TRACE: > AT+IFC=2,2
0000000836 [ncp.at] TRACE: < OK
0000000842 [ncp.at] TRACE: > AT
0000000844 [ncp.at] TRACE: < OK
0000000846 [ncp.at] TRACE: > AT+CCID
0000000870 [ncp.at] TRACE: < +CCID: 89610185002844769463
0000000870 [ncp.at] TRACE: < OK
0000000875 [ncp.at] TRACE: > AT+CIMI
0000000923 [ncp.at] TRACE: < 505016010448089
0000000923 [ncp.at] TRACE: < OK
0000000927 [ncp.at] TRACE: > AT+UMNOPROF?
0000000932 [ncp.at] TRACE: < +UMNOPROF: 4
0000000932 [ncp.at] TRACE: < OK
0000000938 [ncp.at] TRACE: > AT+COPS=3,2
0000000942 [ncp.at] TRACE: < OK
0000000944 [ncp.at] TRACE: > AT+CGEREP=1,0
0000000947 [ncp.at] TRACE: < OK
0000000949 [ncp.at] TRACE: > AT+URAT?
0000000955 [ncp.at] TRACE: < +URAT: 7
0000000955 [ncp.at] TRACE: < OK
0000000961 [ncp.at] TRACE: > AT+CPSMS?
0000000965 [ncp.at] TRACE: < +CPSMS: 0,“00111000”,“00100001”
0000000968 [ncp.at] TRACE: < OK
0000000972 [ncp.at] TRACE: > AT+CEDRXS?
0000000976 [ncp.at] TRACE: < +CEDRXS: 4,“0000”
0000000979 [ncp.at] TRACE: < OK
0000000982 [mux] INFO: Mux channel 1 already opened
0000000989 [ncp.at] TRACE: > AT
0000000992 [ncp.at] TRACE: < OK
0000000993 [ncp.client] TRACE: NCP state changed: 1
0000000996 [net.pppncp] TRACE: NCP event 1
0000001002 [net.ppp.client] TRACE: PPP thread event ADM_UP data=0
0000001005 [ncp.at] TRACE: > AT+CFUN?
0000001007 [net.ppp.client] TRACE: State NONE → READY
0000001011 [ncp.at] TRACE: < +CFUN: 1,7
0000001018 [ncp.at] TRACE: < OK
0000001021 [ncp.at] TRACE: > AT+CGDCONT?
0000001028 [ncp.at] TRACE: < +CGDCONT: 1,“IP”,“telstra.m2m.mnc001.mcc505.gprs”,“10.146.151.23”,0,0,0,2,0,0,0,0,0,0,0
0000001034 [ncp.at] TRACE: < OK
0000001039 [ncp.at] TRACE: > AT+CFUN?
0000001043 [ncp.at] TRACE: < +CFUN: 1,7
0000001045 [ncp.at] TRACE: < OK
0000001050 [ncp.at] TRACE: > AT+CEREG=2
0000001054 [ncp.at] TRACE: < OK
0000001055 [ncp.client] TRACE: NCP connection state changed: 1
0000001061 [net.pppncp] TRACE: NCP event 2
0000001062 [net.pppncp] TRACE: State changed event: 1
0000001068 [ncp.at] TRACE: > AT+COPS?
0000001073 [ncp.at] TRACE: < +COPS: 0,2,“50501”,7
0000001077 [ncp.at] TRACE: < OK
0000001078 [ncp.at] TRACE: > AT+CEREG?
0000001083 [ncp.at] TRACE: < +CEREG: 2,1,“302c”,“08314d0b”,7
0000001069 [net.ppp.client] TRACE: PPP thread event LOWER_DOWN data=0
0000001090 [ncp.at] TRACE: < OK
0000001096 [ncp.client] TRACE: NCP connection state changed: 2
0000001102 [mux] INFO: Openning mux channel 2
0000002532 [net.pppncp] TRACE: NCP event 100
0000002532 [net.pppncp] TRACE: New auth info
0000002540 [net.pppncp] TRACE: NCP event 2
0000002540 [net.pppncp] TRACE: State changed event: 2
0000002546 [net.ppp.client] TRACE: PPP thread event LOWER_UP data=0
0000002551 [net.ppp.client] TRACE: State READY → CONNECT
0000002557 [net.ppp.client] TRACE: State CONNECT → CONNECTING
0000002547 [ncp.at] TRACE: > AT+CIMI
0000002573 [ncp.at] TRACE: < 505016010448089
0000002573 [ncp.at] TRACE: < OK
0000002578 [ncp.at] TRACE: > AT+CGATT?
0000002581 [ncp.at] TRACE: < +CGATT: 1
0000002583 [ncp.at] TRACE: < OK
0000003587 [ncp.at] TRACE: > AT
0000003591 [ncp.at] TRACE: < OK
0000003591 [ncp.at] TRACE: > AT+UPORTFWD=100,1
0000003595 [ncp.at] TRACE: < +UPORTFWD: 100,1
0000003598 [ncp.at] TRACE: < OK
0000003603 [ncp.at] TRACE: > ATD99**1#
0000003611 [ncp.at] TRACE: < CONNECT
0000003611 [net.ppp.client] TRACE: PPP phase → Initialize
0000003617 [net.ppp.client] TRACE: PPP phase → Establish
0000003622 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x58520204> ]
0000003636 [lwip.ppp] TRACE: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x58520204> ]
0000006902 [lwip.ppp] TRACE: rcvd [LCP ConfReq id=0x1 <asyncmap 0x0> <mru 1500> ]
0000006909 [lwip.ppp] TRACE: sent [LCP ConfAck id=0x1 <asyncmap 0x0> <mru 1500> ]
0000006920 [lwip.ppp] TRACE: sent [LCP EchoReq id=0x0 magic=0x58520204]
0000006924 [net.ppp.client] TRACE: PPP phase → Authenticate
0000006930 [lwip.ppp] TRACE: sent [PAP AuthReq id=0x1 user=“” password=“”]
0000006936 [lwip.ppp] TRACE: rcvd [LCP EchoRep id=0x0 magic=0x0]
0000006943 [lwip.ppp] TRACE: rcvd [PAP AuthAck id=0x1 “Login successful.”]
0000006949 [net.ppp.client] TRACE: PPP phase → Network
0000006952 [lwip.ppp] TRACE: sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> <msdns1 8.8.8.8> <msdns2 8.8.4.4>]
0000006964 [lwip.ppp] TRACE: rcvd [IPCP ConfReq id=0x0 <addr 192.168.201.2>]
0000006969 [lwip.ppp] TRACE: sent [IPCP ConfNak id=0x0 <addr 192.168.201.2>]
0000006976 [lwip.ppp] TRACE: rcvd [IPCP ConfNak id=0x1 <addr 192.168.201.1> <msdns1 101.168.244.101> <msdns2 101.168.244.103>]
0000006987 [lwip.ppp] TRACE: sent [IPCP ConfReq id=0x2 <addr 192.168.201.1> <msdns1 101.168.244.101> <msdns2 101.168.244.103>]
0000006998 [lwip.ppp] TRACE: rcvd [IPCP ConfReq id=0x1 <addr 192.168.201.2>]
0000007006 [lwip.ppp] TRACE: sent [IPCP ConfAck id=0x1 <addr 192.168.201.2>]
0000007015 [lwip.ppp] TRACE: rcvd [IPCP ConfAck id=0x2 <addr 192.168.201.1> <msdns1 101.168.244.101> <msdns2 101.168.244.103>]
0000007025 [system.nm] INFO: State changed: IFACE_UP → IFACE_LINK_UP
0000007032 [net.ppp.client] TRACE: PPP thread event UP data=0
0000007037 [net.ppp.client] TRACE: State CONNECTING → CONNECTED
0000007042 [net.pppncp] TRACE: Negotiated MTU: 1500
0000007033 [system.nm] INFO: State changed: IFACE_LINK_UP → IP_CONFIGURED
0000007054 [net.ppp.client] TRACE: PPP phase → Running
0000007059 [system] INFO: Cloud: connecting
0000007064 [system] INFO: Cloud socket connected
0000007065 [comm.protocol.handshake] INFO: Establish secure connection
0000007076 [comm.dtls] INFO: session has 0 uses
0000007091 [comm.dtls] INFO: (CMPL,RENEG,NO_SESS,ERR) restoreStatus=0
0000007093 [comm.dtls] INFO: out_ctr 0,1,0,0,0,0,0,24, next_coap_id=13
0000007101 [comm.dtls] INFO: restored session from persisted session data. next_msg_id=19
0000007111 [comm.dtls] INFO: session cmd (CLS,DIS,MOV,LOD,SAV): 2
0000007465 [ncp.at] TRACE: > AT+CFUN?
0000007469 [ncp.at] TRACE: < +CFUN: 1,7
0000007470 [ncp.at] TRACE: < OK
0000007471 [ncp.at] TRACE: > AT+CCID
0000007519 [ncp.at] TRACE: < +CCID: 89610185002844769463
0000007519 [ncp.at] TRACE: < OK
0000007522 [ncp.at] TRACE: > AT+CGSN
0000007527 [ncp.at] TRACE: < 351457830323678
0000007531 [ncp.at] TRACE: < OK
0000007533 [ncp.at] TRACE: > ATI9
0000007537 [ncp.at] TRACE: < 03.15,A00.01
0000007538 [ncp.at] TRACE: < OK
0000007544 [comm.protocol.handshake] INFO: Skipping HELLO message

Fail to Connect Board

-----------Power Up ---------------

0000000389 [app] INFO: Strating setup.

Activated external SIM :
End OF Setup
0000000395 [system.nm] INFO: State changed: DISABLED → IFACE_DOWN
0000000401 [system.nm] INFO: State changed: IFACE_DOWN → IFACE_REQUEST_UP
0000000406 [ncp.client] TRACE: Powering modem on, ncpId: 0x47
0000000412 [ncp.client] TRACE: Modem already on
0000000417 [ncp.client] TRACE: Setting UART voltage translator state 1
0000000423 [system.nm] INFO: State changed: IFACE_REQUEST_UP → IFACE_UP
0000000429 [app] INFO: deviceID=e00fce68f43ec7b017e98234
Device ID : e00fce68f43ec7b017e98234
0000000522 [ncp.client] TRACE: Setting UART voltage translator state 0
0000000623 [ncp.client] TRACE: Setting UART voltage translator state 1
0000000624 [ncp.client] TRACE: Muxer is not currently running
0000000631 [ncp.client] TRACE: Initialized muxer @ 460800 baudrate
0000000636 [mux] INFO: Starting GSM07.10 muxer
0000000642 [mux] INFO: GSM07.10 muxer thread started
0000000649 [ncp.client] TRACE: Resumed muxed session
0000000650 [mux] INFO: Openning mux channel 1
0000000702 [ncp.at] TRACE: > AT
0000000705 [ncp.at] TRACE: < OK
0000000706 [ncp.client] TRACE: NCP ready to accept AT commands
0000000710 [ncp.at] TRACE: > AT
0000000712 [ncp.at] TRACE: < OK
0000000715 [ncp.at] TRACE: > ATI9
0000000719 [ncp.at] TRACE: < 03.15,A00.01
0000000724 [ncp.at] TRACE: < OK
0000000726 [ncp.client] TRACE: App firmware: 1
0000000730 [ncp.at] TRACE: > AT+UGPIOC?
0000000735 [ncp.at] TRACE: < +UGPIOC:
0000000737 [ncp.at] TRACE: < 16,255
0000000741 [ncp.at] TRACE: < 19,255
0000000743 [ncp.at] TRACE: < 23,0
0000000747 [ncp.at] TRACE: < 24,255
0000000749 [ncp.at] TRACE: < 25,255
0000000752 [ncp.at] TRACE: < 33,255
0000000758 [ncp.at] TRACE: < 42,255
0000000760 [ncp.at] TRACE: < 46,255
0000000763 [ncp.at] TRACE: < OK
0000000766 [ncp.at] TRACE: > AT+UGPIOR=23
0000000770 [ncp.at] TRACE: < +UGPIOR: 23,0
0000000774 [ncp.at] TRACE: < OK
0000000777 [ncp.client] INFO: Using external Nano SIM card
0000000781 [ncp.at] TRACE: > AT+CPIN?
0000000786 [ncp.at] TRACE: < +CPIN: READY
0000000788 [ncp.at] TRACE: < OK
0000000792 [ncp.at] TRACE: > AT+CCID
0000000839 [ncp.at] TRACE: < +CCID: 89610185002683350763
0000000839 [ncp.at] TRACE: < OK
0000000845 [ncp.at] TRACE: > AT+IFC?
0000000849 [ncp.at] TRACE: < +IFC: 2,2
0000000850 [ncp.at] TRACE: < OK
0000000852 [ncp.at] TRACE: > AT+IFC=2,2
0000000856 [ncp.at] TRACE: < OK
0000000862 [ncp.at] TRACE: > AT
0000000865 [ncp.at] TRACE: < OK
0000000866 [ncp.at] TRACE: > AT+CCID
0000000894 [ncp.at] TRACE: < +CCID: 89610185002683350763
0000000894 [ncp.at] TRACE: < OK
0000000900 [ncp.at] TRACE: > AT+CIMI
0000000946 [ncp.at] TRACE: < 505016004922187
0000000946 [ncp.at] TRACE: < OK
0000000950 [ncp.at] TRACE: > AT+UMNOPROF?
0000000954 [ncp.at] TRACE: < +UMNOPROF: 100
0000000956 [ncp.at] TRACE: < OK
0000000961 [ncp.at] TRACE: > AT+UBANDMASK?
0000000965 [ncp.at] TRACE: < +UBANDMASK: 0,6170,0
0000000967 [ncp.at] TRACE: < OK
0000000972 [ncp.at] TRACE: > AT+COPS=3,2
0000000976 [ncp.at] TRACE: < OK
0000000978 [ncp.at] TRACE: > AT+CGEREP=1,0
0000000981 [ncp.at] TRACE: < OK
0000000984 [ncp.at] TRACE: > AT+URAT?
0000000989 [ncp.at] TRACE: < +URAT: 7
0000000989 [ncp.at] TRACE: < OK
0000000995 [ncp.at] TRACE: > AT+CPSMS?
0000000999 [ncp.at] TRACE: < +CPSMS: 0,“00010011”,“00000011”
0000001002 [ncp.at] TRACE: < OK
0000001006 [ncp.at] TRACE: > AT+CEDRXS?
0000001010 [ncp.at] TRACE: < +CEDRXS: 4,“0000”
0000001013 [ncp.at] TRACE: < OK
0000001017 [mux] INFO: Mux channel 1 already opened
0000001023 [ncp.at] TRACE: > AT
0000001026 [ncp.at] TRACE: < OK
0000001027 [ncp.client] TRACE: NCP state changed: 1
0000001030 [net.pppncp] TRACE: NCP event 1
0000001036 [net.ppp.client] TRACE: PPP thread event ADM_UP data=0
0000001041 [net.ppp.client] TRACE: State NONE → READY
0000001041 [ncp.at] TRACE: > AT+CFUN?
0000001050 [ncp.at] TRACE: < +CFUN: 1,7
0000001052 [ncp.at] TRACE: < OK
0000001056 [ncp.at] TRACE: > AT+CGDCONT?
0000001061 [ncp.at] TRACE: < +CGDCONT: 1,“IP”,“telstra.m2m”,“0.0.0.0”,0,0,0,2,0,0,0,0,0,0,0
0000001069 [ncp.at] TRACE: < OK
0000001069 [ncp.at] TRACE: > AT+CFUN?
0000001074 [ncp.at] TRACE: < +CFUN: 1,7
0000001077 [ncp.at] TRACE: < OK
0000001080 [ncp.at] TRACE: > AT+CEREG=2
0000001083 [ncp.at] TRACE: < OK
0000001086 [ncp.client] TRACE: NCP connection state changed: 1
0000001091 [net.pppncp] TRACE: NCP event 2
0000001097 [net.pppncp] TRACE: State changed event: 1
0000001099 [net.ppp.client] TRACE: PPP thread event LOWER_DOWN data=0
0000001100 [ncp.at] TRACE: > AT+COPS?
0000001110 [ncp.at] TRACE: < +COPS: 0
0000001114 [ncp.at] TRACE: < OK
0000001116 [ncp.at] TRACE: > AT+CEREG?
0000001120 [ncp.at] TRACE: < +CEREG: 2,4
0000001125 [ncp.at] TRACE: < OK
0000016227 [ncp.at] TRACE: > AT+CEREG?
0000016231 [ncp.at] TRACE: < +CEREG: 2,4
0000016231 [ncp.at] TRACE: < OK
0000016232 [ncp.at] TRACE: > AT+UCGED?
0000016239 [ncp.at] TRACE: < +UCGED: 2
0000016240 [ncp.at] TRACE: < 6,2,fff,fff
0000016244 [ncp.at] TRACE: < 65535,255,255,255,ffff,0000000,65535,00000000,ffff,ff,255,255,255,1,255,255,255,255,255,0,255,255,0
0000016255 [ncp.at] TRACE: < OK
0000031258 [ncp.at] TRACE: > AT+CEREG?
0000031261 [ncp.at] TRACE: < +CEREG: 2,4
0000031262 [ncp.at] TRACE: < OK
0000031265 [ncp.at] TRACE: > AT+UCGED?
0000031272 [ncp.at] TRACE: < +UCGED: 2
0000031273 [ncp.at] TRACE: < 6,2,fff,fff
0000031274 [ncp.at] TRACE: < 65535,255,255,255,ffff,0000000,65535,00000000,ffff,ff,255,255,255,1,255,255,255,255,255,0,255,255,0
0000031285 [ncp.at] TRACE: < OK
0000046291 [ncp.at] TRACE: > AT+CEREG?
0000046294 [ncp.at] TRACE: < +CEREG: 2,4
0000046295 [ncp.at] TRACE: < OK
0000046296 [ncp.at] TRACE: > AT+UCGED?
0000046302 [ncp.at] TRACE: < +UCGED: 2
0000046304 [ncp.at] TRACE: < 6,2,fff,fff
0000046310 [ncp.at] TRACE: < 65535,255,255,255,ffff,0000000,65535,00000000,ffff,ff,255,255,255,1,255,255,255,255,255,0,255,255,0
0000046321 [ncp.at] TRACE: < OK

rickkas7 · April 13, 2023, 3:44pm

The BRN404X is not supported outside of the United States, Canada, and Mexico. In the first case, it looks like you’ve manually set the the MNO profile to 4 (Telstra).

0000000927 [ncp.at] TRACE: > AT+UMNOPROF?
0000000932 [ncp.at] TRACE: < +UMNOPROF: 4

In the failure case, the device is using the Device OS set profile (100) and the US/CA/MX band mask (6170 = 2, 4, 5, 12, and 13).

0000000950 [ncp.at] TRACE: > AT+UMNOPROF?
0000000954 [ncp.at] TRACE: < +UMNOPROF: 100
0000000956 [ncp.at] TRACE: < OK
0000000961 [ncp.at] TRACE: > AT+UBANDMASK?
0000000965 [ncp.at] TRACE: < +UBANDMASK: 0,6170,0

The problem is that this band mask does not include the bands that are used in Australia, so it will never connect. While you can attempt to override the MNO profile or band mask, Device OS will periodically reset it to the US/CA/MX value, so this will be tricky.

Dan-Kouba · April 13, 2023, 8:25pm

@rizwan23, as an alternative our B524 SOM supports Australia connectivity OOTB on CAT 1 (and any other SKU ending in “524”). We have an online tool to look up which devices are supported in which countries here.

As Rick mentioned, workarounds are required to force your device on the network and they are unsupported by Particle. Additionally, the Boron 404X is not certified or optimized for the bands in use in the region. I highly recommend continuing testing with one of the approved SKUs.

rizwan23 · April 14, 2023, 10:16am

@rickkas7 & @Dan-Kouba
Thanks for your prompt response.
We have 70 Units deployed in US, Australia and Newzealand.
Boron LTE 2g/3g Boron 402x (I think) and recently a few Boron 404x.
And 30 Units of Boron 404x are sitting on my table for test and deploy (Some in Australia and some in US). These were purchased in Jan 2023. And another 50 Units we are hoping to get order in next 2 month or so.
All information can be provided or look for this serial number “P044AD244SLNA3W” and you will find us on Particle Io portal.

Now I have to find solution to over come the problem of “band mask” etc.
Please advise work around / solution for Boron404x for Australian cellular connectivity.
And once we exhausted the stock in hand we will look for suitable product from Particle.

Unit only reads inputs 4/6/12 times per day pass the information to Particle portal and goes to sleep unit next external interrupt by the External RTC.
Any Boron OS is acceptable as long as there is solution.
So any work around / solution for cellular connectivity greatly appreciated.

Riz

Dan-Kouba · April 14, 2023, 6:19pm

@rizwan23, as I shared above, we do not support using the Boron 404X in Australia at this time. The Boron 404X is only certified and supported for use in North America.

Since you have deployments in both North America and in Aus/NZ, the recommended path for you is to use our M.2 SOM series (B404X and B524). For your NA deployments, you would fit a B404X unit and for units in Aus/NZ you would fit a B524. The two modules are pin and code compatible, although you will have to compile separate binaries for each.

Here are some design resources available for you to use when evaluating the BSOM modules:

system · May 17, 2023, 12:09am

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
BRN404X continuously blinking green - running 4.1.0 Connectivity boron	4	231	December 13, 2023
BRN404X and External SIM Problems Cellular cellular	2	247	January 29, 2024
B404x Slow Connectivity Cellular	4	543	November 30, 2022
Boron Initial Setup Connectivity Problem Connectivity boron	7	315	February 15, 2024
Boron LTE connectivity issue - Green LED Blinking Cellular boron	5	421	January 18, 2023

Boron404X cellular connectivity issue

Good Connection Board

-----------Power Up ---------------

Fail to Connect Board

-----------Power Up ---------------

Related topics