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

It seems short messages are not decoded #117

Closed
gariac opened this issue Mar 22, 2024 · 11 comments
Closed

It seems short messages are not decoded #117

gariac opened this issue Mar 22, 2024 · 11 comments

Comments

@gariac
Copy link

gariac commented Mar 22, 2024

I put this in the "discussion" section but on second thought maybe I should bring this up as an issue. The Rust version decodes less messages than the "normal" dump1090 (if such a thing exists). It documented this in my comparison write up:
Comparing rust version of dump1090 The traditional dump1090 decodes shorter messages.

Is anything useful not being decoded?

I find the rust version gets more position data which is the objective after all.

@wcampbell0x2a
Copy link
Member

I'm getting a code 403 on that link.

@gariac
Copy link
Author

gariac commented Mar 26, 2024

I'm getting a code 403 on that link.

Well I copied a list of bad referrers for my website and github.com was on it. This is where uttering "Doh!" is appropriate.

Could you try again. I hope this isn't going to be a browser cache issue.

I attached all the images from the page.

vrs3
vrs2
messages
cpu

@gariac
Copy link
Author

gariac commented Mar 26, 2024

I'm getting a code 403 on that link.

The output from dump1090_rs are in the right hand panels.

@wcampbell0x2a
Copy link
Member

Interesting! This rust version does decode short frames, you can read the number on the Stats display. Just, way way less.

Interesting tool however, I'll have to play around with throughput and CPU usage.

@gariac
Copy link
Author

gariac commented Mar 27, 2024

Interesting! This rust version does decode short frames, you can read the number on the Stats display. Just, way way less.

Interesting tool however, I'll have to play around with throughput and CPU usage.

Well two terminals side by side are just raw dumps. What could I have possibly done to build the code in a manner where it doesn't do short decodes? I will admit building Rust is quite foreign to me.

I just do a git clone and the link. Is there some secret sauce I need for git?

The webpage link is fixed. (Actually nginx map fixed.) I did include the version of the program and cargo data. I posted it below for convenience.

`
The program is under development. This is a test of rev 0.7.

This is the installed version of cargo on Opensuse:
cargo -V
cargo 1.76.0

`

@wcampbell0x2a
Copy link
Member

Pushed a WIP MR that should fix this issue: #130

@gariac
Copy link
Author

gariac commented Aug 31, 2024

I'm not a programmer. Was I supposed to do something special or just build the code. I'm still not seeing any short messages. I haven't run VRS to collect stats but it is pretty obvious all the messages are the same length.

@wcampbell0x2a
Copy link
Member

Just build the code from that branch, you should get SHORT and LONG messages in the output.

Here is an already built version: https://wcampbell.dev/public/bins/dump1090_rs

@gariac
Copy link
Author

gariac commented Aug 31, 2024

Your binary works. However I would like to know how to compile the code.

@wcampbell0x2a
Copy link
Member

  1. Install rust
  2. Install soapysdr-dev, for example on ubuntu: apt install libsoapysdr-dev
  3. after cloning this repo, cargo build --release

@wcampbell0x2a
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants