Ntn.status request misbehaviour: keeps responding with {no-ntn-module}, but sat qo is functional

Notecard API
1

Greeting Blues team,

I had some issues with {ntn.status} request, where I’d consistently receive {no-ntn-module} status, but the satellite communication is working just fine.
I can create a file which is properly templated with compact and port fields. I can send such a note and the notehub sees that note with “transport” : “ntn-udp”.
The classic example:

image
image815×700 50.4 KB

Currently, I am in a bind where I don’t have exposed uart or aux pins on notecard, so I cannot provide you with any trace logs (which will change down the line).

Are there any good troubleshooting hints that you can quickly list, besides Starnote quickstart and best practices articles?
After all, this could be a HW problem on our side.

Cheers!

3

Hi @Jakov,

The devil is in the details here :slight_smile:. "transport": "ntn:udp" means the Note was sent successfully using NTN over UDP (so using your Notecard, not the Starnote). If it were sent over satellite you’d see "ntn:skylo". In Notehub, you can quickly check this by looking at the icon under the transport heading as well:

image
image576×394 21.2 KB

Now as to why you’re seeing {no-ntn-module}. I’ve run into this before myself and this means that your Notecard is not paired with a Starnote. Here are some things I would check:

  1. Make sure you’re on the latest Notecard firmware.
  2. Try issuing an ntn.reset command.
  3. Re-seat the Starnote in its M.2 connector, just in case.

Let me know if this helps!

Rob

4

Just to come back with an update, the re-slotting of the Starnote to M.2 connector, didn’t make any difference. The firmware should be up to date:

image
image1076×725 87.9 KB

Soon enough, we should have trace logs from this, and we’ll troubleshoot the HW.

5

I got a hold of Notecarrier XS ( the breakout board that carries Starnote ) and it appears to be working just fine!