# Notecard giving {network}{extended-network-failure} error

**URL:** <https://discuss.blues.com/t/notecard-giving-network-extended-network-failure-error/1049>\
**Category:** Hardware\
**Created:** [October 27, 2022, 3:29pm UTC](https://discuss.blues.com/t/notecard-giving-network-extended-network-failure-error/1049 "2022-10-27T15:29:24Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Karl\_iWell](https://avatars.discourse-cdn.com/v4/letter/k/7feea3/32.png) [@Karl\_iWell](https://discuss.blues.com/u/Karl_iWell)\
**Post date:** [October 27, 2022, 3:29pm UTC](https://discuss.blues.com/t/notecard-giving-network-extended-network-failure-error/1049/1 "2022-10-27T15:29:24Z")

</div>

I’m receiving an “extended-network-failure” error when trying to connect with Notecard (IMEI “dev:867730051834129”). The debug stream from my Arduino app on the feather is shown below. When I replace the Notecard everything works fine.

I did a hub.restore and get the same result.

Is this a known notecard failure mode?  
Any suggestion?

Here is the card.version data:

```auto

> {"req":"card.version"}
{
 "version": "notecard-3.5.1.15545",
 "device": "dev:867730051834129",
 "name": "Blues Wireless Notecard",
 "sku": "NOTE-NBGL-500",
 "board": "1.11",
 "api": 3,
 "body": {
  "org": "Blues Wireless",
  "product": "Notecard",
  "version": "notecard-3.5.1",
  "ver_major": 3,
  "ver_minor": 5,
  "ver_patch": 1,
  "ver_build": 15545,
  "built": "Oct 10 2022 12:37:13"
 }
}

Snippet from app debug messages:
09:09:32.813 -> Connected status false
09:09:32.813 -> {"req":"hub.status"}
09:09:32.885 -> {"status":"132s starting communications {wait-module} {connecting}"}
09:09:35.880 -> Connected status false
09:09:35.880 -> {"req":"hub.status"}
09:09:35.948 -> {"status":"4324912s starting communications {wait-module} {connecting}"}
09:09:38.926 -> Connected status false
09:09:38.926 -> {"req":"hub.status"}
09:09:38.994 -> {"status":"4324915s starting communications {wait-module} {connecting}"}
09:09:41.996 -> Connected status false
09:09:41.996 -> {"req":"hub.status"}
09:09:42.065 -> {"status":"4324918s starting communications {wait-module} {connecting} {network}{extended-network-failure}"}
```

---

<div class="post-metadata">

**Author:** ![RobLauer](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/roblauer/32/1567_2.png) [@RobLauer](https://discuss.blues.com/u/RobLauer)\
**Post date:** [October 27, 2022, 5:52pm UTC](https://discuss.blues.com/t/notecard-giving-network-extended-network-failure-error/1049/2 "2022-10-27T17:52:05Z")

</div>

Hi @Karl_iWell,

It looks like your Notecard is not able to connect to the network. Can you please [consult this help guide](https://discuss.blues.com/t/help-my-notecard-is-not-connecting-to-the-cell-network/73) and let us know if that helps?

Thanks,  
Rob

---

<div class="post-metadata">

**Author:** ![Karl\_iWell](https://avatars.discourse-cdn.com/v4/letter/k/7feea3/32.png) [@Karl\_iWell](https://discuss.blues.com/u/Karl_iWell)\
**Post date:** [October 28, 2022, 4:10pm UTC](https://discuss.blues.com/t/notecard-giving-network-extended-network-failure-error/1049/3 "2022-10-28T16:10:06Z")

</div>

Thanks Rob,

I followed the referenced instructions, doing the following steps:

1. Check antenna connection - I inspected the uFl connector on the notecard and saw no issues. I installed a new notecard on my Notecarrier AF board and it connected fine. I replaced the “problem” notecard.

2. Ensure antenna signal not interfered - Notecarrier in same position as my test with new notecard. Not the problem.

3. Try different location - the test with both the new and the “problem” notecard took place in a known good location in the office. This isn’t the problem.

4. Capture trace log. See below.

Thanks again,  
Karl

Trace Log:

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

* * *

~ Connected to serial  
~ DeviceUID dev:868050040769016 (NOTE-WBNA-500) running firmware 3.4.1.15128

> {“req”:“card.version”}  
> {“version”:“notecard-3.4.1.15128”,“device”:“dev:868050040769016”,“name”:“Blues Wireless Notecard”,“sku”:“NOTE-WBNA-500”,“board”:“1.11”,“api”:3,“body”:{“org”:“Blues Wireless”,“product”:“Notecard”,“version”:“notecard-3.4.1”,“ver\_major”:3,“ver\_minor”:4,“ver\_patch”:1,“ver\_build”:15128,“built”:“Aug 11 2022 18:38:27”}}  
> bootloader  
> ~ Disconnected from serial

- NetworkError: The device has been lost.  
~ Connected to serial  
~ DeviceUID dev:868050040769016 (NOTE-WBNA-500) running firmware 3.5.1.15545

> {“req”:“card.version”}  
> {“version”:“notecard-3.5.1.15545”,“device”:“dev:868050040769016”,“name”:“Blues Wireless Notecard”,“sku”:“NOTE-WBNA-500”,“board”:“1.11”,“api”:3,“body”:{“org”:“Blues Wireless”,“product”:“Notecard”,“version”:“notecard-3.5.1”,“ver\_major”:3,“ver\_minor”:5,“ver\_patch”:1,“ver\_build”:15545,“built”:“Oct 10 2022 12:37:13”}}  
> {“req”:“card.status”}  
> {“usb”:true,“status”:“{normal}”,“storage”:1,“time”:1666898045,“cell”:true}  
> {“req”:“note.template”,“file”:“sensor.qos”,“verify”:true}  
> {“template”:true,“body”:{“temp”:12.1,“battery”:12.1,“CL1”:12.1,“CL2”:12.1,“CL3”:12.1,“CL4”:12.1}}  
> ~ Disconnected from serial

- NetworkError: The device has been lost.  
~ Connected to serial  
~ DeviceUID dev:867730051834129 (NOTE-NBGL-500) running firmware 3.5.1.15545

> {“req”:“hub.sync.status”,“sync”:true}  
> {“status”:“modem now ON {modem-on}”,“sync”:true,“requested”:126}  
> {“req”:“card.version”}  
> {“version”:“notecard-3.5.1.15545”,“device”:“dev:867730051834129”,“name”:“Blues Wireless Notecard”,“sku”:“NOTE-NBGL-500”,“board”:“1.11”,“api”:3,“body”:{“org”:“Blues Wireless”,“product”:“Notecard”,“version”:“notecard-3.5.1”,“ver\_major”:3,“ver\_minor”:5,“ver\_patch”:1,“ver\_build”:15545,“built”:“Oct 10 2022 12:37:13”}}  
> {“req”:“card.wireless”}  
> {“status”:“{modem-on}”,“mode”:“auto”,“net”:{}}  
> {“req”:“card.wireless”}  
> {“status”:“{modem-on}”,“mode”:“auto”,“net”:{}}  
> {“req”:“card.wireless”}  
> {“status”:“{modem-on}”,“mode”:“auto”,“net”:{}}  
> {“req”:“card.trace”,“trace”:“mdmax”,“start”:“true”}  
> {“err”:“cannot interpret JSON: field ‘start’ should not be a JSON string {io}”}  
> {“req”:“card.trace”,“trace”:“mdmax”,“start”:true}  
> {“start”:true,“trace”:“comm,sync,mdm,mdmmax,mem,gps”}  
> {“req”:“hub.sync”}  
> {}  
> {“req”:“hub.sync.status”,“sync”:true}  
> {“status”:“modem: can’t connect (4.4 min remaining) {network}{extended-network-failure}”,“sync”:true,“requested”:1}  
> {“req”:“hub.sync.status”,“sync”:true}  
> {“status”:“modem: can’t connect (3.6 min remaining) {network}{extended-network-failure}”,“sync”:true,“completed”:1}  
> {“req”:“hub.sync.status”,“sync”:true}  
> {“sync”:true,“requested”:1}  
> {“req”:“card.trace”,“stop”:true}  
> {“text”:“M06:12.24 4325144 \< Heartbeat \r\nR06:23.13 sync: wakeup: hub.sync\r\nS06:23.19 sync: work: error in isSyncDue: modem: can’t connect (3.2 min remaining) {network}{extended-network-failure} {sync-error}\r\nS06:23.20 SyncOnSchedule: modem: can’t connect (3.2 min remaining) {network}{extended-network-failure}\r\nM06:32.49 4325164 \< Heartbeat \r\nM06:52.75 4325184 \< Heartbeat \r\nM06:56.50 \*\*\* MODEM TRANSACTION TOO LONG SIMResetOff at+cfun=0 (125 sec)\r\nM06:56.51 \_log.qo: \*\*\* MODEM HARD RESET SIMResetOff at+cfun=0 (125 sec)\r\nM06:56.51 4325188 \< HardReset \r\nM06:56.51 \*\*\* HARD RESET \*\*\*\r\nM06:56.51 4325188 \< HardPowerOff \r\nM06:56.51 modem: wireless: modem now OFF {modem-off}\r\nM06:56.51 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\r\nM06:56.51 modem: active for 133 sec\r\nM06:56.51 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\r\nM07:01.55 sync: wakeup: modem shutdown\r\nM07:01.65 modem: wireless: idle {disconnected} {network}{extended-network-failure}\r\nM07:01.65 0 \< PowerOn \r\nM07:01.66 modem: 5.10V 34.88C at power-on\r\nM07:01.66 modem: wireless: starting communications {wait-module} {connecting} {network}{extended-network-failure}\r\nM07:05.99 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\* ON \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\r\nM07:05.99 modem: wireless: modem now ON {modem-on}\r\nM07:07.05 4325199 \< PostReset RDY\r\nM07:07.05 4325199 \> EchoOff ate0\r\nM07:07.10 4325199 \< EchoOff ate0\r\nM07:07.10 4325199 \< EchoOff OK\r\nM07:07.60 4325199 \> IsEnabled at+cfun?\r\nM07:07.65 4325199 \< IsEnabled +CFUN: 1\r\nM07:07.65 4325199 \< IsEnabled OK\r\nS07:07.72 sync: work: error in isSyncDue: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure} {sync-error}\r\nS07:07.72 SyncOnSchedule: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure}\r\nS07:07.82 sync: work: error in isSyncDue: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure} {sync-error}\r\nS07:07.83 SyncOnSchedule: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure}\r\nS07:07.93 sync: work: error in isSyncDue: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure} {sync-error}\r\nS07:07.95 SyncOnSchedule: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure}\r\nM07:10.15 4325202 \> SIMResetOff at+cfun=0\r\nM07:30.45 4325222 \< Heartbeat \r\nR07:31.94 ARMED FOR 900 SECONDS\r\nR07:31.94 attn: ARMED\r\nR07:31.94 sync: wakeup: attn arm\r\nS07:31.95 sync: work: error in isSyncDue: modem: can’t connect (4.4 min remaining) {network}{extended-network-failure} {sync-error}\r\nS07:31.95 SyncOnSchedule: modem: can’t connect (4.4 min remaining) {network}{extended-network-failure}\r\nM07:50.71 4325242 \< Heartbeat \r\nM08:10.98 4325263 \< Heartbeat \r\nR08:19.65 sync: wakeup: hub.sync.status\r\nS08:19.66 sync: work: error in isSyncDue: modem: can’t connect (3.6 min remaining) {network}{extended-network-failure} {sync-error}\r\nS08:19.66 SyncOnSchedule: modem: can’t connect (3.6 min remaining) {network}{extended-network-failure}\r\nR08:22.17 i2c3: state auto-reset by timer\r\nM08:31.25 4325283 \< Heartbeat \r\nR08:41.03 sync: wakeup: hub.sync.status\r\nS08:41.03 sync: work: error in isSyncDue: modem: can’t connect (3.3 min remaining) {network}{extended-network-failure} {sync-error}\r\nS08:41.04 SyncOnSchedule: modem: can’t connect (3.3 min remaining) {network}{extended-network-failure}\r\nR08:43.55 i2c3: state auto-reset by timer\r\nM08:51.51 4325303 \< Heartbeat \r\nM09:11.77 4325323 \< Heartbeat \r\nM09:15.52 \*\*\* MODEM TRANSACTION TOO LONG SIMResetOff at+cfun=0 (125 sec)\r\nM09:15.52 \_log.qo: \*\*\* MODEM HARD RESET SIMResetOff at+cfun=0 (125 sec)\r\nM09:15.52 4325327 \< HardReset \r\nM09:15.52 \*\*\* HARD RESET \*\*\*\r\nM09:15.52 4325327 \< HardPowerOff \r\nM09:15.53 modem: wireless: modem now OFF {modem-off}\r\nM09:15.53 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\r\nM09:15.53 modem: active for 133 sec\r\nM09:15.53 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\r\nM09:20.57 sync: wakeup: modem shutdown\r\nM09:20.67 modem: wireless: idle {disconnected} {network}{extended-network-failure}\r\nM09:20.67 0 \< PowerOn \r\nM09:20.68 modem: 5.10V 34.88C at power-on\r\nM09:20.68 modem: wireless: starting communications {wait-module} {connecting} {network}{extended-network-failure}\r\nM09:24.99 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\* ON \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\r\nM09:24.99 modem: wireless: modem now ON {modem-on}\r\nM09:26.08 4325338 \< PostReset RDY\r\nM09:26.08 4325338 \> EchoOff ate0\r\nM09:26.12 4325338 \< EchoOff ate0\r\nM09:26.12 4325338 \< EchoOff OK\r\nM09:26.63 4325338 \> IsEnabled at+cfun?\r\nM09:26.67 4325338 \< IsEnabled +CFUN: 1\r\nM09:26.67 4325338 \< IsEnabled OK\r\nS09:26.72 sync: work: error in isSyncDue: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure} {sync-error}\r\nS09:26.72 SyncOnSchedule: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure}\r\nS09:26.82 sync: work: error in isSyncDue: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure} {sync-error}\r\nS09:26.82 SyncOnSchedule: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure}\r\nS09:26.93 sync: work: error in isSyncDue: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure} {sync-error}\r\nS09:26.93 SyncOnSchedule: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure}\r\nM09:29.18 4325341 \> SIMResetOff at+cfun=0\r\nM09:49.48 4325361 \< Heartbeat \r\nM10:09.75 4325381 \< Heartbeat \r\nM10:30.02 4325402 \< Heartbeat \r\nM10:50.29 4325422 \< Heartbeat \r\nM11:10.56 4325442 \< Heartbeat \r\nM11:30.83 4325462 \< Heartbeat \r\nM11:34.58 \*\*\* MODEM TRANSACTION TOO LONG SIMResetOff at+cfun=0 (125 sec)\r\nM11:34.58 \_log.qo: \*\*\* MODEM HARD RESET SIMResetOff at+cfun=0 (125 sec)\r\nM11:34.58 4325466 \< HardReset \r\nM11:34.59 \*\*\* HARD RESET \*\*\*\r\nM11:34.59 4325466 \< HardPowerOff \r\nM11:34.59 modem: wireless: modem now OFF {modem-off}\r\nM11:34.59 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\r\nM11:34.59 modem: active for 133 sec\r\nM11:34.59 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\r\nM11:39.88 sync: wakeup: modem shutdown\r\nM11:40.00 modem: wireless: idle {disconnected} {network}{extended-network-failure}\r\nM11:40.00 0 \< PowerOn \r\nM11:40.02 modem: 5.10V 36.13C at power-on\r\nM11:40.02 modem: wireless: starting communications {wait-module} {connecting} {network}{extended-network-failure}\r\nM11:44.36 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\* ON \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\r\nM11:44.36 modem: wireless: modem now ON {modem-on}\r\nM11:45.42 4325477 \< PostReset RDY\r\nM11:45.42 4325477 \> EchoOff ate0\r\nM11:45.47 4325477 \< EchoOff ate0\r\nM11:45.47 4325477 \< EchoOff OK\r\nM11:45.97 4325478 \> IsEnabled at+cfun?\r\nM11:46.02 4325478 \< IsEnabled +CFUN: 1\r\nM11:46.02 4325478 \< IsEnabled OK\r\nS11:46.07 sync: work: error in isSyncDue: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure} {sync-error}\r\nS11:46.07 SyncOnSchedule: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure}\r\nS11:46.17 sync: work: error in isSyncDue: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure} {sync-error}\r\nS11:46.17 SyncOnSchedule: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure}\r\nS11:46.27 sync: work: error in isSyncDue: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure} {sync-error}\r\nS11:46.27 SyncOnSchedule: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure}\r\nM11:48.52 4325480 \> SIMResetOff at+cfun=0\r\nM12:08.84 4325500 \< Heartbeat \r\nM12:29.10 4325521 \< Heartbeat \r\nR12:40.05 \_log.qo: penalty: removed from penalty box: hub.set\r\nR12:40.05 \_log.qo: penalty: removed from penalty box after hard failure\r\nR12:40.05 \_log.qo: penalty: removed from penalty box after insufficient current failure\r\nR12:40.05 sync: wakeup: hub.set\r\nR12:40.46 template set for sensor.qos bodyLen:72 payloadLen:0\r\nR12:43.00 i2c3: state auto-reset by timer\r\nR12:44.47 sync: wakeup: hub.sync.status\r\nR12:44.94 sync: wakeup: sensor.qos again\r\nR12:44.98 sync: wakeup: hub.sync\r\nM12:49.75 4325541 \< Heartbeat \r\nM13:10.00 4325562 \< Heartbeat \r\nM13:30.24 4325582 \< Heartbeat \r\nM13:50.48 4325602 \< Heartbeat \r\nM13:54.23 \*\*\* MODEM TRANSACTION TOO LONG SIMResetOff at+cfun=0 (125 sec)\r\nM13:54.34 \_log.qo: \*\*\* MODEM HARD RESET SIMResetOff at+cfun=0 (125 sec)\r\nM13:54.35 4325606 \< HardReset \r\nM13:54.35 \*\*\* HARD RESET \*\*\*\r\nM13:54.35 4325606 \< HardPowerOff \r\nM13:54.35 modem: wireless: modem now OFF {modem-off}\r\nM13:54.36 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\r\nM13:54.36 modem: active for 134 sec\r\nM13:54.36 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\r\nS13:54.43 checkpointAllNoteboxes {checkpointed} sensor.qos\r\nM13:59.39 sync: wakeup: modem shutdown\r\nM13:59.49 \_log.qo: penalty: entering penalty box: idle {disconnected} {network}{extended-network-failure}\r\nM13:59.49 modem: wireless: idle {disconnected} {network}{extended-network-failure}\r\nM13:59.49 0 \< PowerOn \r\nM13:59.50 modem: 5.11V 36.13C at power-on\r\nM13:59.50 modem: wireless: starting communications {wait-module} {connecting} {network}{extended-network-failure}\r\nM14:03.86 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\* ON \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\r\nM14:03.86 modem: wireless: modem now ON {modem-on}\r\nM14:04.89 4325616 \< PostReset RDY\r\nM14:04.89 4325616 \> EchoOff ate0\r\nM14:04.94 4325616 \< EchoOff ate0\r\nM14:04.94 4325616 \< EchoOff OK\r\nM14:05.44 4325617 \> IsEnabled at+cfun?\r\nM14:05.49 4325617 \< IsEnabled +CFUN: 1\r\nM14:05.49 4325617 \< IsEnabled OK\r\nS14:05.59 sync: work: error in isSyncDue: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure} {sync-error}\r\nS14:05.59 SyncOnSchedule: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure}\r\nS14:05.69 sync: work: error in isSyncDue: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure} {sync-error}\r\nS14:05.69 SyncOnSchedule: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure}\r\nS14:05.79 sync: work: error in isSyncDue: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure} {sync-error}\r\nS14:05.79 SyncOnSchedule: modem: can’t connect (4.8 min remaining) {network}{extended-network-failure}\r\nM14:07.99 4325620 \> SIMResetOff at+cfun=0\r\nM14:28.30 4325640 \< Heartbeat \r\n”}

---

<div class="post-metadata">

**Author:** ![RobLauer](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/roblauer/32/1567_2.png) [@RobLauer](https://discuss.blues.com/u/RobLauer)\
**Post date:** [October 28, 2022, 8:08pm UTC](https://discuss.blues.com/t/notecard-giving-network-extended-network-failure-error/1049/4 "2022-10-28T20:08:07Z")

</div>

Hi @Karl_iWell,

As you’re using a WBNA Notecard, do you have an additional antenna you can connect to the `DIV` U.FL connector on the Notecard? It looks like this Notecard was placed in a [penalty box](https://dev.blues.io/guides-and-tutorials/notecard-guides/understanding-notecard-penalty-boxes/) due to repeatedly not being able to connect. Usually it’s just poor signal strength that leads to this behavior (it’s a power-saving mechanism).

Also, can you send me the output of a `card.wireless` request?

Thanks,  
Rob

---

<div class="post-metadata">

**Author:** ![Karl\_iWell](https://avatars.discourse-cdn.com/v4/letter/k/7feea3/32.png) [@Karl\_iWell](https://discuss.blues.com/u/Karl_iWell)\
**Post date:** [October 28, 2022, 10:02pm UTC](https://discuss.blues.com/t/notecard-giving-network-extended-network-failure-error/1049/5 "2022-10-28T22:02:12Z")

</div>

Rob,

There is no socket on the notecard for a diversity antenna. Here is a picture of the notecard.

 ![IMG_1901.HEIC](https://us1.discourse-cdn.com/flex020/uploads/blues/original/1X/1a925558860470ac6af9a309a61094cfbbb61c5a.jpeg)

The card.wireless response and a few hub.status responses:

```auto
> {"req":"hub.status"}
{"status":"133s starting communications {wait-module} {connecting}"}
> {"req":"hub.status"}
{"status":"4324911s starting communications {wait-module} {connecting}"}
> {"req":"card.wireless"}
{
 "status": "{modem-off}",
 "mode": "auto",
 "net": {}
}
> {"req":"card.wireless"}
{
 "status": "{modem-on}",
 "mode": "auto",
 "net": {}
}

```

Thanks,  
Karl

---

<div class="post-metadata">

**Author:** ![RobLauer](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/roblauer/32/1567_2.png) [@RobLauer](https://discuss.blues.com/u/RobLauer)\
**Post date:** [October 29, 2022, 12:48am UTC](https://discuss.blues.com/t/notecard-giving-network-extended-network-failure-error/1049/6 "2022-10-29T00:48:01Z")

</div>

Hi @Karl_iWell,

Ok, it looks like you have a WBNA Notecard and a NBGL Notecard (I see the WBNA in the first set of commands and the NBGL in the latter). Is the WBNA (the one with the `DIV` U.FL port) the one that is working for you?

Assuming that’s the case, I’d be willing to bet it’s a signal strength issue with the NBGL. Do you have an external antenna you can attach to `MAIN` on the NBGL and try again? Try the `card.wireless` request a few times until you see something in the `net` object appear (it’ll update as it tries to connect).

Rob

---

<div class="post-metadata">

**Author:** ![Karl\_iWell](https://avatars.discourse-cdn.com/v4/letter/k/7feea3/32.png) [@Karl\_iWell](https://discuss.blues.com/u/Karl_iWell)\
**Post date:** [October 31, 2022, 7:17pm UTC](https://discuss.blues.com/t/notecard-giving-network-extended-network-failure-error/1049/7 "2022-10-31T19:17:54Z")

</div>

Rob,

Both of the Notecards I’ve been using on the issues, the working and the non-working notecards are marked NB GL on the label on the back of the notecard.

I used an external antenna on the non-working notecard and it did not connect. Here is a sequence of card.wireless responses:

```auto
> {"req":"card.wireless"}
{"status":"{modem-on}","mode":"auto","net":{}}
> {"req":"card.wireless"}
{"status":"{modem-on}","mode":"auto","net":{}}
> {"req":"card.wireless"}
{"status":"{modem-on}","mode":"auto","net":{}}
> {"req":"card.wireless"}
{"status":"{modem-off}","mode":"auto","net":{}}

```

Here is what I don’t understand and is a potential red flag. Doing a sequence of hub.status commands:

```auto
> {"req":"hub.status"}
{"status":"93s starting communications {wait-module} {connecting}"}
> {"req":"hub.status"}
{"status":"94s starting communications {wait-module} {connecting}"}
> {"req":"hub.status"}
{"status":"4325322s starting communications {wait-module} {connecting}"}
> {"req":"hub.status"}

```

Why does the time jump from 94seconds to 4325322 seconds?

I believe this notecard is faulty, that makes the most sense.

Thanks,  
Karl