NTN with the nrf9151?

AchimKraus

Maybe this other user Accessing GNSS through the at_client program can help you with the antenna for GNSS.

careTacklePrince

Thankyou Achim.

Im coming from a software engineering / Web dev background so this is all quite new to me. I really appreciate the advice! Ill take a look at the Antennas you’ve mentioned and have asked in the other thread as well

jaredwolff

Sateliot is getting their Germany test license soon. May be worth testing @AchimKraus https://tech.sateliot.com/

AchimKraus

That would require a visit in sateliot labs in Barcelona …
For something I’m not paid and may get relevant only in a couple of years, I don’t think I will spend that time and money for it ;-)

jaredwolff

Really? Sounds like their new platform I linked is self service and almost ready for testing. What made you think you needed to go to Barcelona?

AchimKraus

Their (sateliot) presentation at the Deutsche Telekom NTN Early Adapter Kick Off in September 2025.
I was not on all monthly calls, but their argument was, that it’s much easier to setup the modem app to operate proper in the simulation lab than in the field.
In my understanding, that offers a “one-way” communication with potentially large transmission times additional to small availability windows. Yes, when the price goes down to TN, as they forecast, then it may be an idea. But for now, I don’t see, that this makes too much sense for me.

Do you have different infos?
(I will ask the Deutsche Telekom, maybe they know, if I have missed an update.)

rmartinezdatakorum

Hi guys, Achim we have met several times in the EAP from DT in Germany. Nice catching up with you. I am actually under validation with sateliot, we have passed all lab tests and we are planning to bring our device outside to fetch real satellites probably next week. Since I am based in Valencia it is true that I took one day to visit sateliot lab in Barcelona to get everything ready in the lab. They might be able to help you with the setup and everything but as Achim is suggesting it is not fast, and it takes time for changes and access.
Achim you are kind of wright with your arguments, you have a small window for the MO and then in the following pass you get the attach response so you have to do a doble attach process and then when you send message #1 you get the answer of message #1. This does not fit all applications obviously.
Achim if you need help to get in touch with them or maybe collaborate somehow just let me know, I normally speak to them every week.
I am actually using the nordic nRF9151 Devkit SMA using the serial lte modem with our third party MCU. We are planning to migrate our application to the nRF9151 but I am also thinking of using Jared´s feather first as it is more compact. Since I guess Achim owns at least one feather, I imagine Jared that you also can deliver to Spain…

jaredwolff

rmartinezdatakorum yup. The nRF9151 Feather is all set for EU.

AchimKraus

Recent update from the Deutsche Telekom:
Sateliot and Nordic are working on an extension library, which then obsoletes the visit at the labs in Barcelona. But for now, that visit is mandatory.

@rmartinezdatakorum
Thanks for offering help. But for me this is not within my current business and for freetime activities I’m pretty happy with Skylo ;-).

Since I guess Achim owns at least one feather, I imagine Jared that you also can deliver to Spain…

I have a couple of them :-). You may order them direct from Jared, which ensures you get A1A. Or from digikey, which in my experience also ships a A1A.
I use my two NTN SIM cards with two of these feathers. I patched the old NCS 3.1.0 to support NTN and with that, my client works pretty well with Skylo. I also tried to update to NCS 3.2.0, but for now that doesn’t work and I’m for the next weeks not able to spend time in migrating.

jaredwolff

AchimKraus which in my experience also ships a A1A

Indeed they are A1A.

rmartinezdatakorum

Hi Achim no worries at all, we are a small community after all. If you are planning attending to MWC26 maybe we might get to see each other, otherwise we will definitely catch up in Viena.
Jared thanks for the confirmation so I guess it is going to be easier for us to order from Digikey as it is one of your regular distributors we normally work with for samples and components. The PASSY-NRF9151-FEATHER I believe is the one I need to order:

https://www.digikey.es/es/products/detail/circuit-dojo/PASSY-NRF9151-FEATHER/26580618

Best

jaredwolff

@rmartinezdatakorum yes, that’s the only one.

sergimolina-siot

Hello guys!

Sergi here, from Sateliot Product Team. Glad to see Sateliot LEO NTN is sparking some discussions!

Let me clarify some concepts, so we all know what’s on the table:

We have developed the Sateliot Tech Portal, also on Nordic’s website, to bring a gateway for the IoT ecosystem to explore our connectivity straightforwardly. In it, there’s a quick test option, which allows you to do a quick cell detection trial with our network. It takes an hour or so to set up, and you are good to go (for you guys it would take 10 min I bet 😜). In a few weeks, 🇩🇪 Germany will be activated in this Portal
The full integration program, which is what @AchimKraus is referring to, enables customers to fully develop their product to be validated with our network, end-to-end

Give it a try, I’m convinced you’ll enjoy it as much as we did building it for you!

BR,
S

AchimKraus

Hi Sergi,

cool that you follow up the discussion here as well, because Jared’s nRF9151 feather is in my experience the first device, which will make it into the field. For GEO such a nRF9151 feather is already “live” since last September (at that time the device was “hand selected” by Jared :-) ).

In a few weeks, 🇩🇪 Germany will be activated in this Portal

That’s great to read. I guess we will be informed once in the regular Telekom call, when this gets available for testing.

It takes an hour or so to set up, and you are good to go (for you guys it would take 10 min I bet 😜).

That mainly depends on the application logic and maybe the used protocol. Beside of some very simple PoC tests, which I have in my card, “my coap/dtls way” will not be a that good match ;-) for LEO. But in my case it’s more to search for transfer technologies, which matches the coap/dtls stack. For others, application driven developments, that’s naturally different and they will have then a closer look.

torntrousers

Hello. I’m trying to connect a Feather over NTN and need to update the modem firmware for that. I have an NTN enable SIM and have it all running on an nRF9151 SMA DK, and now trying with the Feather.

I’ve got the modem updater with cargo install --git https://github.com/circuitdojo/modem_updater.git but then when i run that it fails:

updater program \Nordic\DT\mfw_nrf9151-ntn_1.0.0-1.alpha.zip
Programming error: An ARM specific error occurred.

and

set RUST_BACKTRACE=full && updater program \Nordic\DT\mfw_nrf9151-ntn_1.0.0-1.alpha.zip

thread 'main' (74500) panicked at src\bin\updater.rs:114:19:
Unable to attach to probe! Error: An ARM specific error occurred.
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

any help on getting this to work, or other approaches for updating the modem?

AchimKraus

Not sure, I use

cargo run –bin updater – program mfw_nrf9151-ntn_1.0.0-1.alpha.zip

to do that.

jaredwolff

@torntrousers are you on Linux? Did you setup the udev rules? https://probe.rs/docs/getting-started/probe-setup/

torntrousers

AchimKraus

with updater from where? With https://github.com/circuitdojo/modem_updater.git i need at least

git diff
diff --git a/src/bin/updater.rs b/src/bin/updater.rs
index b3427a9..a1c8c21 100644
--- a/src/bin/updater.rs
+++ b/src/bin/updater.rs
@@ -109,7 +109,7 @@ fn main() {
     probe.set_speed(12000).unwrap();

     // Attach
-    let mut session = match probe.attach("nRF9160_xxAA", Permissions::new().allow_erase_all()) {
+    let mut session = match probe.attach("nRF9151_xxAA", Permissions::new().allow_erase_all()) {
         Ok(s) => s,
         Err(e) => panic!("Unable to attach to probe! Error: {}", e),
     };

but then still:

cargo run --bin updater -- program \Nordic\DT\mfw_nrf9151-ntn_1.0.0-1.alpha.zip
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.30s
     Running `target\debug\updater.exe program \Nordic\DT\mfw_nrf9151-ntn_1.0.0-1.alpha.zip`
⠁ [00:00:00] [============================================================================================] 0 B/0 B (0s)[2026-04-03T10:41:38Z INFO  modem_updater] UICR.HFXOSR is not set, setting it to 0x0E
Programming error: An ARM specific error occurred.
error: process didn't exit successfully: `target\debug\updater.exe program \Nordic\DT\mfw_nrf9151-ntn_1.0.0-1.alpha.zip` (exit code: 3)

torntrousers

jaredwolff sadly WIndows

AchimKraus

I run on ubuntu …

« Previous Page Next Page »