Has anyone successfully used ntrip over bluetooth?

Has anyone successfully used ntrip bluetooth in the Flow app advanced settings? I’m having a devil off a time getting RS4 to accept rtcm

I use it, and in my case it works perfectly.
A friend has issues and cannot connect, but we determined it’s related to the tablet is using. There is no way to convince it to stay connected. It simply connects for a split second then drops the connection.
Same setup with any other phone works fine.

Massimo

what ntrip service/app are you using on the device? I’m not talking about using Flow as the ntrip provider. Im talking about the advanced setting to allow a third party ntrip over bluetooth

What device are you running Emlid Flow on and which NTRIP service are you attempting to connect to?

Have you tried any other NTRIP service providers like RTK2Go…

Edit: OK hang on I’ve just seen your other thread you started here - so this issue is with an iPad?? this sounds very much like a device issue, rather than NTRIP.

(polite hint: it’s best not to start multiple threads about the same issue; becomes difficult for others to help you and follow up. Also it’s considered poor forum etiquette (generally).

Two very different issues surrounding communicating in to the rs4. One may be iPad hardware/firmware related. my iPad is having issues that my iPhone does not when using Flow and concurrent appManaged and deviceManaged bluetooth. Or it may be with Emlid’s documentation of using com.emlid.nmea and com.emlid.corrections protocols, creating two EASession instances — one for input (NMEA) and one for output (RTCM). My ntrip script communicates just fine with a handful of ublx and unicorn receivers. The issue is RS4 not accepting the rctm output that is confirmed working with other receivers connected to my ntrip app.

Which app is it?

my app, I coded it and it works with zed9 and unicorn receivers just fine. It’s verified working ntrip provider

Hi @ericrosenwald73 ,

I just want to check a couple of things that may help us narrow this down.

When the issue occurs, do you have any other devices connected to or receiving corrections from the NTRIP app? I’m wondering whether your NTRIP application has a limit on the number of simultaneous connections, which could explain the behavior you’re seeing.

Additionally, could you confirm whether Background App Refresh toggle is enabled for Emlid Flow on your iPad’s settings? This can allow the app to continue operating in the background. I have attached a screenshot from an iPhone, but I believe it should be the same on your iPad.

Hello community!

I’m having issues with Flow app and iPad Pro 11.

Unlike an iPhone that allows both appManaged and deviceManaged bluetooth connections at the same time, my iPad absolutely will not allow the RS4 to receive ntrip in the background from Flow app (appManaged) while another app is connected via deviceManaged bluetooth. This background connection works flawlessly on my iPhone. iPad refuses to open both connections to the RS4.

Anyone seeing the same bug when using an iPad?

Thanks

Eric

If this is the same issue as your other thread here - its best and most polite/helpful to keep the discussions in one thread.

I’ll keep my answers/replies over there. :backhand_index_pointing_right:

different issue exposed by my attempts to solve the other threads issue. iPad absolutely will not allow the flow app to remain open in the background on an appManaged bluetooth connection when you also open a deviceManaged connection to receive nmea via bluetooth in the advanced settings. iPad will only maintain one connection to rs4 but not both the way the Flow app is intended to work

Ok this issue has resolved itself with both a RS4 firmware reflash and an iPad iOS update. I’ll close this thread

Great. Nice simple solution :ok_hand:

whelp that was short lived fix. Powered cycled rs4 and iPad and now its back to same odd behavior. iPad can not maintain both the appManaged and deviceManaged connection . @#$! this is maddening LOL

This evening I can borrow my other half’s iPad mini to see if I can replicate this with my RX2.

Just to be clear you’re using Emlid Flow (running in the background for NTRIP input) and the foreground app is your own app - or have you tested with something else?

The ipad issue has nothing to do with my app. Here is the sequence:

  1. Open Flow - connect in app (appManaged)
  2. Open iOS Bluetooth - select reach
  3. Either refuses to connect or disconnects the appManaged connection

I cant even get to the point of opening my app.
Ipad refuses to open both Bluetooth connections to Flow.

@ericrosenwald73 ,

I moved the thread here to just keep things in one place. Were you able to look at the post here?

Everything is configured properly. Ipad still refuses to honor both the Flow app AND the ios managed connections. Works fine on iphone. And to be clear this is not the ntrip issue Im trying to solve with my app. I can delete my app from ipad and this Bluetooth issue persist so I disagree with everything thinking the two are related. Am I not explaining both issues clearly? The ipad issue is clearly a ble/bluetooth classic/registered device issue and not an issue due to my app. Am I not using the correct terms to describe app vs device managed connections?

I get you, but I’m wondering if the issue is peculiar to your particular iPad (or model type / age range) perhaps with a chipset peculiarity or weird combo of iOS version and model.

Really want to see if the issue persists with other iPad models since we know iPhone is fine.

It’s a brand new 11”pro M5 chip on latest os update