Sometimes takes a while to send outbound data even in continuous mode

1

Why does it sometimes take so long to send outbound Notes to Notehub? There’s this specific case where I’m having an issue. I’m in continuous mode with “sync”: true and I detect inbound Notes with the ATTN pin. An inbound Note {“send”: true} from the “data.qi” file is received, which tells me to immediately send an outbound Note to Notehub. So I call “NoteRequest(req)”, but it takes about 35 seconds to finish executing. Is there a way to make this faster?

To be specific, I am measuring 35 seconds right before and after the “NoteRequest(req)" call.

2

Hey @yunzheng,

That does seem excessive. A few questions:

Can you share the output of running a card.version call on your Notecard so I can get a sense of what kind of device and firmware you’re running?

Why does it sometimes take so long

Does the Notecard usually send Notes faster? If so, how often are you seeing these slower calls?

Can you share any other requests your firmware is making to the Notecard? My guess is that the Notecard is doing something else in the background (GPS?) during this slow calls that it needs to finish before processing your request.

TJ

1 Like
3

The Notecard usually sends Notes much faster. These slower calls consistently only happen in the specific case I outlined above.

All requests that my firmware makes to the Notecard are
“hub.set”
“card.attn”
“note.get”
“note.add”
While I do use the GPS feature sometimes, this delay happens even when I turn GPS off.

I’ll send an output of “card.version” later

5

Here is the output from “card.version”

{
    "version": "notecard-7.2.2.16518",
    "device": "dev:860322060156350",
    "name": "Blues Wireless Notecard",
    "sku": "NOTE-WBNAN",
    "ordering_code": "EA0WT1N0AXBB",
    "board": "5.13",
    "cell": true,
    "gps": true,
    "api": 7,
    "body": {
        "org": "Blues Wireless",
        "product": "Notecard",
        "target": "u5",
        "version": "notecard-u5-7.2.2",
        "ver_major": 7,
        "ver_minor": 2,
        "ver_patch": 2,
        "ver_build": 16518,
        "built": "Apr 10 2024 04:26:44"
    }
}
6

The narrowband Notecards are slower than wideband ones, especially when establishing a connection, so that might be relevant.

Could you also do a card.wireless request and see what comes back from that? Curious what your network and signal strength look like.

Thanks,
TJ

1 Like
7

Here is what I get

{
    "status": "{network-up}",
    "mode": "auto",
    "count": 1,
    "net": {
        "iccid": "89011704278930029956",
        "imsi": "310170893002995",
        "imei": "860322060156350",
        "modem": "EG91NAXDGAR07A01M1G_20.004.20.004",
        "band": "LTE BAND 2",
        "rat": "lte",
        "internal": true,
        "rssir": -53,
        "rssi": -54,
        "rsrp": -91,
        "sinr": -4,
        "rsrq": -17,
        "bars": 1,
        "mcc": 310,
        "mnc": 410,
        "lac": 293,
        "cid": 5320456
    }
}
8

I think it actually doesn’t matter that I’m specifically trying to send an outbound Note. It seems like the >30 second delay happens with any request I try to make.

In the same situation as I outlined above but instead of sending an outbound Note to Notehub (with a “note.add” request), I made a “card.wireless” request. It took over 30 seconds for the “card.wireless” request to finish executing as well. I tested this with a “card.version” request as well, and it also took over 30 seconds for it to finish executing.

9

That’s really weird. Are you seeing those delays when you interact with the Notecard in a terminal, or are you seeing that while running your firmware?

If you DM me your firmware I can look it over to see if see anything that looks suspicious.

TJ

1 Like
10

Actually @yunzheng I’m pretty confident your issues are related to signal quality. Your SINR and RSRQ are both very poor Diagnosing Cellular Connectivity Issues - Blues Developers.

2 Likes