Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SoftRF show its own deviceID as traffic #76

Closed
1 of 8 tasks
8lazo8 opened this issue Jan 9, 2020 · 10 comments
Closed
1 of 8 tasks

SoftRF show its own deviceID as traffic #76

8lazo8 opened this issue Jan 9, 2020 · 10 comments
Labels

Comments

@8lazo8
Copy link

8lazo8 commented Jan 9, 2020

Hardware

  • Standalone
  • Prime Mark II
  • Dongle
  • SkyView EZ
  • Raspberry Edition
  • UAV
  • UAT978 module
  • Flight Recorder

IMG_20200109_171300

Firmware version

Screenshot_2020-01-09-17-41-51-117_com android browser

Firmware settings

Screenshot_2020-01-09-17-42-00-724_com android browser

Describe the bug (or ask a question)

I am a new SoftRF user, today I went out for a test on the ground.
Next week I plan to make an in flight test.

When the Prime MKII is near to an aircraft - 2-300 meters or closer - equiped with OGN tracker periodically it seems to "receive" its own tracker ID as foreign tracker and it is listed as traffic in the Skyview and in xcsoar as well. The phenomenon is intermittent.
It tested this with two different aircrafts.

After the aircrafts departured the "self reflection" disappeared only the real aircraft was seen on the screen.

To Reproduce

Te be close to an OGN tracker equipped aircraft, maximum 2-300 meters.

Expected behavior

To receive/display only the foreign aircraft deviceID but not itself.

@Ben64Smith
Copy link

From memory I think paweł added rebroadcast functionality in the later versions of the OGN tracker, this is probably the cause of your issue.

@8lazo8
Copy link
Author

8lazo8 commented Jan 9, 2020

From memory I think paweł added rebroadcast functionality in the later versions of the OGN tracker, this is probably the cause of your issue.

This means that the foreign aircraft rebroadcasted my deviceID? I am pretty sure it was not SoftRF device inside.

Does this rebroadcast function has anything to do to proximity of the trackers? So its not active on larger distances? I mean I should have to receive it all the time. And it also would cause alerts.
Or in this case the self deviceID should be filtered?

@lyusupov
Copy link
Owner

lyusupov commented Jan 9, 2020

@Ben64Smith
Correct. I also expect that this likely happens due to re-broadcast feature of OGN tracker.
I don't remember if I had seen this with my build of STM32 OGN tracker on a breadboard.
It probably depends on particular revision of OGN firmware, settings and certain conditions has to be met.

@8lazo8
Could you connect your Prime Mk2 to a PC and capture a NMEA log on 38400,8*N1 ?
If there is a 'ghosting traffic' - we will likely see it in a PFLAA sentence.

BTW, nice picture of Prime2 and EZ in genuine SoftRF enclosure(s) !     👏

@8lazo8
Copy link
Author

8lazo8 commented Jan 9, 2020

@Ben64Smith
Correct. I also expect that this likely happens due to re-broadcast feature of OGN tracker.
I don't remember if I had seen this with my build of STM32 OGN tracker on a breadboard.
It probably depends on particular revision of OGN firmware, settings and certain conditions has to be met.

@8lazo8
Could you connect your Prime Mk2 to a PC and capture a NMEA log on 38400,8*N1 ?
If there is a 'ghosting traffic' - we will likely see it in a PFLAA sentence.

Yes I can do that. You need the capture when "ghosting" can be seen on the screen?

I have two Mk2-s but between them this never happened. To reproduce the phenomenon I will need to go for another field trip.
I will capture the log ASAP whichever is needed.

@lyusupov
Copy link
Owner

lyusupov commented Jan 9, 2020

No rush. Take it when able. ZIP , then drag and drop here.

You need the capture when "ghosting" can be seen on the screen?

Yes.

lyusupov added a commit that referenced this issue Jan 9, 2020
@lyusupov lyusupov added the bug label Jan 9, 2020
lyusupov added a commit that referenced this issue Jan 9, 2020
@8lazo8
Copy link
Author

8lazo8 commented Jan 11, 2020

No rush. Take it when able. ZIP , then drag and drop here.

You need the capture when "ghosting" can be seen on the screen?

Yes.

Hi,
Today I managed to collect logs. After all I could not take it from the serial but I hope xcsoar NMEA dump will be good as well.
There were lots of "ghostings".
2020-01-11_10-53.zip

@lyusupov
Copy link
Owner

Thanks!

I've committed b0ddbac and 6e4e9bb

Build and update your Prime MkII(s).

Those 2 commits above should fix this issue. Please, test and confirm.

@8lazo8
Copy link
Author

8lazo8 commented Jan 11, 2020

Thanks!

I've committed b0ddbac and 6e4e9bb

Build and update your Prime MkII(s).

Those 2 commits above should fix this issue. Please, test and confirm.

Update has been done, will test it soon.

@8lazo8
Copy link
Author

8lazo8 commented Jan 17, 2020

There is IMC in the area since a week, hopefully next week the weather will good enough for a test.

@lyusupov
Copy link
Owner

Resolution: fixed in b0ddbac and 6e4e9bb

Repository owner locked as resolved and limited conversation to collaborators Feb 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants