Show Posts

You can view here all posts made by this member. Note that you can only see posts made in areas to which you currently have access.


Messages - ILIMB

Pages: [1] 2
1
Technical Support / Re: Ghosting
« on: November 05, 2024, 11:20:25 pm »
Thanks for your reply, next time it occurs I'll take screenshots/record a video of the screen.

Essentially, without no prior warning, I instantly see an amber or red circle around my airplane on Skydemon, and an aural warning about the colliding traffic, often same altitude or slightly above/below.

Due to airspace limitations, were always flying at 1500aal (2000amls), and I often wonder if I'm picking up signals from aircraft on the ground.

But nevertheless, once the waning is out, I cannot see any trace of the other aircraft. Anyway, I'll try and provide more details, also about the configuration once I'm flying.

2
Technical Support / Re: Ghosting
« on: November 05, 2024, 01:35:25 pm »
I don't understand the comment, sorry. I wrote that the HEX code matches the transponder's, didn't mention the callsign. For every aircraft I fly I set up profiles with hex codes matching the transponder's. As recommended, the hex values are also checked with FlighRadar's and I only fly with S transponders.

I only mentioned "callsign" with regards to what appears on the screen, meaning that the conflict is always another aircraft's. But in reality there is none, and also the "ghost" is only on Skydemon, not on Rosetta's RADAR.

3
Technical Support / Re: Ghosting
« on: November 04, 2024, 07:44:25 am »
Did you fix the issue? I occasionally have the same problem, with a portable setup, and if I check the aircraft callsign is always an aircraft that is plausible. The Hex value corresponds to the transponder's. It's kind of scary.
Multiple times I tried to carefully "separate" from the "ghost" but did not get a distinct trace.
What's very strange is that on the radar I don't see them, only on Skydemon. Could it be a FLARM protocol issue?

4
Technical Support / Re: Anker recommended Power Supply... doesn't work
« on: December 06, 2023, 07:46:58 am »
Hi Peter,

The one that didn't work (for me) is exactly the second you posted, which I picked from the recommended list: https://www.amazon.it/gp/product/B019GJLER8

The one working "almost" fine (occasional voltage drops when I still had the igrid wifi module, so far fine without) is similar to the first, however 20100 wasn't available in Italy at the moment of purchase, so I went for the 20000, which I'm currently happy with: https://www.amazon.it/gp/product/B09SFS9J2K/

I also got the cigarette lighter adapter but never managed to use it, as recently I've only been flying dual for my IR and the take off checklists of most aircraft I fly mandate aux power to be operated only after takeoff, therefore no point using it, as I would have to wait for Rosetta to get a GPS fix exactly when there is more traffic: https://www.amazon.it/gp/product/B071WYF9HP

Regards

5
Finally, lets keep positive- we surely don’t need another flyer forum  :o

Wise words!

6
Technical Support / Re: Anker recommended Power Supply... doesn't work
« on: December 04, 2023, 09:11:12 pm »
I have a feeling it was something to do with the low pwer draw of the Paw unit that somehow fooled the powerbank into thinking nothing ws connected and switched itself off.

Spot on Alan, it's exactly what's happening. I can see Rosetta's LEDs for a while, then it all turns off, power bank included. I just returned the 10k as it's useless. Hopefully the 20k seems not as "smart", although I had purchased it to power multiple also the phone and I understood it's not a good idea to mix devices.

Anyway I'm charging the phone with the portable hotspot, another bonus of my setup :)

7
Technical Support / Re: Anker recommended Power Supply... doesn't work
« on: November 29, 2023, 02:54:33 pm »
Strangely enough, I confirm it just doesn't work with the PowerCore 10000, but it does nicely with the PowerCore 20000.

Same wiring, I just plug the USB in the 10k, leds turn on both on the power bank and inside Rosetta, then nothing else happens and the power bank leds turn off.
Unplugging the USB from the power bank side (so no change to Rosetta's side), I just plug it into the 20k and it works fine.

On a flight just yesterday I actually thought that the lack of connection was due to an issue with the SD card, which popped out (now I put some tape to keep it together), but today I couldn't get it working again.

I purchased the 10k because I saw some voltage errors on the 20k, following the recommendations, but perhaps those errors occurred when I was using the additional wifi module for iGRID, which I happily ditched. So now it should be fine, and btw I also have the Anker cigarette lighter (which I didn't use because it was my IFR check ride, so better avoiding complications in the front of the cockpit).

Just as shared by Keith Vinnings (thanks for the kind support) it might be that newer PowerBanks don't have the same specs as the old ones.

8
Have you ever considered how much time tinkerers, like you, take up in having to reply to unnecessary queries, brought about because you can’t just simply turn it in and allow it to do it’s job?.
This rant coming after the intended setup is complete, only increases the satisfaction.

You already showed unmistakable signs of functional illiteracy with the previous judgemental post, leaving only a stale smell as if coming from the past, only I was kind enough to avoid putting a spotlight on them earlier.

In case you haven't noticed during your *valuable" time spent commenting hundreds of posts on this forum (...), Rosetta isn't exactly an industrial, monolithic toaster, but rather the sheer result of tinkering with an open innovation platform (Raspberry PI) itself: bits and pieces of hardware produced for other purposes, assembled in a way that wasn't intended to be before, somehow squeezed in a plastic case. Far from being perfect, and little research shows it's constantly evolving, as it should.

What's an open forum like this supposed to be for, otherwise? Only sharing your experience about how to operate a toaster, accordingly to the manual, and occasionally fix it?

9
Rosetta sends UDP packets to its clients
If I understand correctly your ipad is a client of the router, not of rosetta
Therefore Rosetta does not send udp packets

The UDP data is unicast, not multicast

The address of 192.168.1.1 is hardcoded into skydemon


@admin out of curiosity, how would you explain the attached screenshot, according to the quoted texts above? As you can see, SD was happily connected to PAW (no GPS fix, meaning connection established, only indoor), the only issue being that the mobile device could not connect to the Internet. But it was indeed connected to the hotspot, not directly to Rosetta, and apparently was still receiving UDP unicast / was recognized as Rosetta's client?

PilotAware-TopGun is the hotspot, DoNotUse is Rosetta.


10
Ah I thought multicast! Why bother using unicast on a veeery private network?

Anyway, is connecting with FLARM equivalent or is there any loss of functionality?

P.S. Now Rosetta seems to be so happy to do only what she's meant to do, that even the GPS fix is much quicker. Normally I put her on the window for testing and it takes half an hour, now it's a matter of minutes. Also the web interface is much quicker without the hassle of WiFi connections.

11
But it's strange, I checked the network configuration with ssh and I saw that the hotspot has a br-lan bridge interface including UDP multicast between wlan0 and eth0, so UDP should have passed.

Anyway, great! Didn't know about FLARM, it works flawslessly! Sooo... seems the ultimate stable setup is ready, PAW wifi back to 1mW, router disabled and hopefully I should be able to use it on my next flight! :)

Is there any significant loss by using FLARM Vs. PilotAware?

Btw, does this strictly rely on Rosetta being on 192.168.1.1, right?

12
For the moment I just swapped the two USB modules, putting the GPS in the bottom left.

On that note, isn't the best reception at the bottom where the PAW sticker is?

13
Is the router function on? I'm guessing not, as it only appears when the second wlan is there...

Yes it is, but as you correctly say it's not required, as in this setup the router is the portable modem itself and Rosetta is just a client in the network, as it should be.

If you can open a terminal app in Android, can you ping 192.168.1.1 from it?

Of course. I can also ssh and access PAW web interface. All it's missing is SD "seeing" it.

Or can you see the phone's IP address on the WiFi?

Of course, it's on the same subnet.

The irony is in the previous posts: I thought I fooled SD by labelling the SSID PilotAware-xxx, and partially I did, but based on the selection of a random MAC address Vs. the phone's actual one, I can respectively get either access to SD or connection to the Internet, but not both at the same time, which apparently does not make any sense. In both circumstances, though, I can access PAW's web interface and Rosetta is connected to the Internet.

I'm still banging my head on this not just because it's the very last mile of the most logical network setup, but because using it with the standard configuration I still haven't managed to get a stable, reliable WiFi connection with more than a single device. The moment I connect two devices to Rosetta's WiFi, things get weird: one gets correctly routed to the Internet, the other not.

I also thought it was a problem with my android, but with an iPad I still get the same result. The next attempt will be trying to fit Rosetta in my home network, which requires a little bit more than just some tweaking, to exclude that the limitation lies with the portable hotspot itself...

14
@Admin, @Keithvinning, can you please shed some light in here?

I am trying again to make the simplified setup work, and I cannot understand why it shouldn't with the attached configuration, which I'm also pasting here:

PilotAware Rosetta-RX : Version(20231022) License Expires(20281009)
_   Interface   Status
HOSTID   B827EBFE2851
PLATFORM   Model B Pi 3+, 9 (stretch)/4.14.79-v7+
DATE   Sun Nov 26 14:06:03 2023
IP   eth0=192.168.1.1      wlan0=UP      iGRID-wg=10.200.0.48
UPTIME   14:06:03 up 0 days 00:06, Load 1.20:0.84:0.41
STATUS   Volt=OK   Freq=OK   Thro=OK   Temp=52.1/52.1   EM=0   SG=0
1090   Connected RX=1510(+6)
P3I   Connected UP=0.06% DN=0.00% Mode=Airborne
Traffic=0   METAR=0   Status=0   ATOM=0   SkyGRID=0   
Barometer   Configuring (Manual) QNH=1013mb QNE=426ft GNSS=0ft
GPS   RX=2863(+0) Fix="No fix" Mode="Not Available" Sat=4(use)/10(view)

It all work perfectly, except... Skydemon for some weirdness of their own can't see Rosetta. All protocols are enabled by default, eth0 is on 192.168.1.1. Could it be that for some reason UDP doesn't get through in this configuration, that it only relies on WiFi?



15
Is there an alternative GPS solution for a portable setup? It's already the second time that, after takeoff, I lose GPS fix, only to find out that the flawed culprit is... the GPS dongle disconnected inside the case.

I wouldn't mind having an external battery powered GPS, bluetooth or cabled, that I can keep on regardless of what happens to Rosetta in terms of power, etc. Said differently, I don't want to lose GPS fix just because Rosetta reboots or something weird happens.

Pages: [1] 2