CCAS - Collision warning -> iPad connection drop

I use the CCAS app on iOS and iPadOS — when the cellular connection was interrupted during flight, traffic is not displayed in the Moving Map even after the connection is restored. Although the CCAS app itself shows the data again.
I tested the same case on Android — the problem does not occur there.

Settings on the iPad:

  • Location - Access: Always
  • Local Network: Discovery allowed
  • Cellular Data: allowed
  • Background App Refresh: The app is not listed there (however I always keep it active in the foreground in split-screen and still, after the cellular connection is restored, traffic is shown only in the CCAS app and no longer in the Moving Map)

Could this possibly be a fundamental problem with iOS and iPadOS (since the problem does not occur on Android), or does anyone have any ideas what else I could change?

I must confess, I use SkyDemon as my moving map, not VFR Nav — but unfortunately I couldn’t find a dedicated forum for CCAS.

1 Like

Hi Bernd,

…Well, since CCAS automatically re-displays the traffic during mobile data dropouts, it won’t be due to CCAS. In VFRnav there is the option to view the incoming traffic data ( e.g. from the Stratux or CCAS).

→ Is there such an option in the SD as well?

Flyer greetings, Karsten

Hi Karsten,

thanks for your reply!

I couldn’t find that feature in SkyDemon and first contacted SkyDemon support. They referred me to CCAS support.

(Because with SafeSky I don’t have this problem with SkyDemon and both programs deliver the traffic data to SkyDemon via the GDL90 interface).

Hi Bernd,
I forwarded this to my colleague who is taking care of the iOS implementation. Please be a little patient. In the CCAS project everyone works on a voluntary basis and Alex became a father again three weeks ago :partying_face:
I’m sure he’ll take a look at this soon.

Pilot’s regards
Hermann

Hi Hermann,

Thanks for your feedback and congratulations to your colleague :star_struck:

Good morning,

I also have a question about CCAS with VFRnav and didn’t want to open a new thread for it. Is it possible with VFRnav to run CCAS and Stratux on the same device and have information from both systems displayed in VFRnav?

The background is that on my iPad I connect VFRnav to my Stratux via Wi‑Fi, which works great, and so far I run CCAS via my separate mobile phone (because the iPad lacks cellular), which of course means I only transmit that way and the CCAS information doesn’t end up directly in VFRnav.

In the future I’d like to run Stratux over Wi‑Fi and CCAS over cellular in parallel on one device so I can see consolidated information from both systems in VFRnav.

Is that possible?? Can VFRnav handle two traffic sources over different paths (UDP/TCP ports) at the same time?

Thanks and regards

Stefan

Hello Stefan,

yes, that should work the way you wrote.

Another option would be to use the Stratux access point function. That is intended for when only one device on board has an internet connection (e.g., a mobile phone (Handy) usually has mobile data/internet — if available — and a tablet without a SIM card has no internet).

-> in this case you create a classic hotspot on the phone and enter the access credentials in Stratux. Now all devices can connect to the Stratux access point and have (if available in the air) internet.

-> So also CCAS

Anyone who has the “luxury” :rofl: and has all devices equipped with SIM/internet doesn’t need this, of course.

Receiving CCAS data and Stratux is therefore possible.

Tip: use, if applicable, the Filter function under the -Filter- item to pre-filter desired visibilities/data already in CCAS that will be passed to VFRnav. You can also make the settings in VFRnav.

Happy flying,

Karsten

Hello Karsten,

Many thanks for the quick reply. I had tried that before with the AccessPoint function of Stratux, but on the one hand it wasn’t stable and on the other I sometimes had to intervene manually again and again to get the connection to work. I can’t use that as an additional task during the warmup or during the flight, when there are other things to be handled, which is why I’m taking this approach now.

I’ll try it at the next opportunity.

Thanks again and best regards

Stefan

…yes, in early versions the feature was unstable, that’s true. Especially in the AP Client area there were a few fixes and improvements… it’s actually running pretty stably. …however, I’m building my own image and can’t say much about the official one at this point anymore.

Try your idea, it’ll work!

Blue skies,

Karsten

Hi everyone,

the way I consider the “nicest” is to connect Stratux via Bluetooth. CCAS supports this as a beta feature. The advantage is that CCAS also “sees” the Stratux data and can share it onto the network.

Additionally, this leaves Wi-Fi completely free.

So I would proceed like this:

Stratux → Bluetooth → CCAS (on the iPAD).
iPAD → Hotspot → Smartphone-Internet

I don’t know which phone you use. I personally use the Hotspot function on Android very frequently, which lets you turn the phone into an AccessPoint. That way the iPad has access to the internet.
Maybe someone knows whether that also works under iOS?!

Happy flying
Hermann

Hello Hermann,

this is indeed a possibly preferred way for this idea.
BT:

I had experience here with pairing errors between the systems. BT and BTLE. LE — really bad when manually “by accident” paired. Specifically the T-Beam. This also enables BT by default.

-> I’d also be very interested in feedback here!

If you use Stratux in the usual way over WLAN, I recommend disabling BT on the Pi. Those who use the above-mentioned suggestion, of course, should not!

…

Hello Hermann,

I’ve thought about using Bluetooth as a connection to the Stratux, too, but on the one hand I haven’t read exclusively positive things about it and on the other hand it just works very well for me over Wi‑Fi and, above all, without problems during the flight. I really don’t feel like troubleshooting during the flight :wink:

But maybe I’ll try your suggestion soon while sitting near my seat.

Thanks also for the input :slightly_smiling_face:

Regards

Stefan

Yeah, I know a few reports about Stratux and Bluetooth. I haven’t followed the topic over the last nine months either and I’m not really up to speed on whether anything might have changed.

But I’m grateful for any firsthand reports. Maybe we’ll come up with another practical solution.

If VFRnav supports multiple data sources, that would be a solution for now. In my opinion, though, a more elegant solution would be a stable Stratux -> CCAS -> VFRnav.