Notecard could not connect

We have a notecard NBGL500 that works fine for months, and then could not connect anymore.

The customer sends it back to us. We try to change the antenna without success, but changing the notecard works. We try to debug it by adding trace (see below). Is there something we can do to know why it does not want to connect with this card?

Welcome to the Notecard In-Browser Terminal.
Start making requests below.
(For advanced info, use the ‘help’ command.)


~ Connected to serial
~ Sync Status Monitor enabled
~ DeviceUID dev:863940055930815 (NOTE-NBGL-500) running firmware 6.2.5.16868
Hint: A newer firmware, notecard-10.1.1 (LTS 10 Release Candidate), is available. Run ‘firmware install latest’ to update.

{
“req”: “hub.sync.status”
}
{“status”:“modem now ON {modem-on}”,“mode”:“{modem-on}”,“sync”:true}
{“req”:“card.trace”,“mode”:“on”}
{“stop”:true}
{“req”:“hub.sync”}
{}
S01:30.86 sync: project: modem: can’t connect (4.4 min remaining) {network}{extended-network-failure}
S01:30.87 sync: work: error in isSyncDue: modem: can’t connect (4.4 min remaining) {network}{extended-network-failure} {sync-error}
S01:30.87 syncOnSchedule: modem: can’t connect (4.4 min remaining) {network}{extended-network-failure}
S01:30.87 sync: project: modem: can’t connect (4.4 min remaining) {network}{extended-network-failure}
{“req”:“card.wireless.penalty”,“reset”:true}
{}
{“req”:“hub.sync”}
{}
S02:09.20 sync: connect requested by first sync; explicit sync request; continuous connection mode; periodic inbound sync due (DATA)
S02:09.21 connect: 5.36V 24.63C before comms power-on
S02:09.22 apn: for a.notefile.net using apn a-notehub.com.attz
S02:09.22 sync: wireless: domain a.notefile.net using APN a-notehub.com.attz
S02:09.22 sync: wireless: starting communications {wait-module} {connecting} {transport}
S02:09.23 modem: beginning power-on sequence
S02:13.28 modem: *************** ON ***************
S02:13.28 sync: wireless: modem now ON {modem-on}
M02:34.38 *** MODEM TRANSACTION TOO LONG aftr (20 sec)
M02:34.39 _log.qo: *** MODEM HARD RESET aftr (20 sec)
M02:34.39 *** HARD RESET ***
M02:34.40 modem: wireless: modem now OFF {modem-off}
M02:34.40 modem: **********************************
M02:34.41 modem: active for 25 sec
M02:34.41 modem: **********************************
S02:34.42 _log.qo: penalty: entering penalty box: modem: can’t connect (5.0 min remaining) {network}{extended-network-failure}
S02:34.42 sync: project: modem: can’t connect (5.0 min remaining) {network}{extended-network-failure}
S02:34.43 sync: notehub: disconnected (was {connecting}) via close of notebox {notehub-disconnected}
S02:34.43 sync: work: error in isSyncDue: modem: can’t connect (5.0 min remaining) {network}{extended-network-failure} {sync-error}
S02:34.44 syncOnSchedule: modem: can’t connect (5.0 min remaining) {network}{extended-network-failure}
S02:34.45 sync: project: modem: can’t connect (5.0 min remaining) {network}{extended-network-failure}
S02:34.46 sync: next wake-up due in 30s for lower latency continuous-mode sync
M02:39.78 sync: wakeup: modem shutdown
S02:39.79 sync: notehub: disconnected (was {connecting}) via close of notebox {notehub-disconnected}
S02:39.79 sync: work: error in isSyncDue: modem: can’t connect (4.9 min remaining) {network}{extended-network-failure} {sync-error}
S02:39.79 syncOnSchedule: modem: can’t connect (4.9 min remaining) {network}{extended-network-failure}
S02:39.80 sync: project: modem: can’t connect (4.9 min remaining) {network}{extended-network-failure}
S02:39.81 sync: next wake-up due in 30s for lower latency continuous-mode sync
S03:09.98 sync: work: error in isSyncDue: modem: can’t connect (4.4 min remaining) {network}{extended-network-failure} {sync-error}
S03:09.99 syncOnSchedule: modem: can’t connect (4.4 min remaining) {network}{extended-network-failure}
S03:09.99 sync: project: modem: can’t connect (4.4 min remaining) {network}{extended-network-failure}
S03:10.00 sync: next wake-up due in 4m 24s on expiry of extended error
{“req”:“card.trace”,“mode”:“off”}
{“stop”:true}

Hi @Laurent Thanks for reaching out via our forum. I’ve just sent you a direct message so we can look into this issue further.