AcarsDeco2 Development

[Hobbyd]

Hi Sergsero,
Just gave it a very quick go and it seems that --device-index arg is not working (as I would expect).

This is what I did/tried:
./acarsdeco2 --device-list
AcarSDeco2 v.20170819
Available Devices:
0 mnf: Realtek prod: RTL2838UHIDIR serial: 00000011


./acarsdeco2 --device-serial 00000011 --freq 131525000 131725000 131825000
AcarSDeco2 v.20170819
Device not found.


./acarsdeco2 --device-serial 11 --freq 131525000 131725000 131825000
AcarSDeco2 v.20170819
Device not found.

Cheers,
Dick

[Hobbyd]

Hi Sergsero,
This is probably a newbie question.

The help states:
--no-sq               Don't display messages with SQ label (default: on)

I understand that this means that messages with an SQ label are not logged.
What should I do when I DO want to log the Squitter messages?

Cheers,
Dick

[sergsero]

Hi Dick,

Thank you for testing.
Indeed, in this version was temporarily disabled capability of using a dongle via the serial number. It will be included in the next test version.

If I understand correctly, you want to keep Squitter messages but not display its?
I will try to implement it in next version.

Regards,
sergsero

[Hobbyd]

Hi Sergsero,

Well, I would like to find the SQ messages in the log, because to me it is interesting to see DX squitters.
I live too far from the airport to see all the squitters, so I only catch a few and most of them are DX..
You will be surprised to see how far an SQ signal on 131 MHz can travel :-)

I feed the data to Planeplotter and use a headless RPi, so I never see the SQ on the screen. They do appear in the PP log, but as it are only a few that is OK for me.

Thanks,
Dick

[Hobbyd]

Hi Sergsero,
As to the
" --no-sq               Don't display messages with SQ label (default: on)"

I was confused by the " --no-sq" and the "(default: on)".
Looking at the log I now understand that when " --no-sq" is not used the SQ messages are displayed and appear in the log.
So the "on" in "(default: on)" does not mean the option is true / "on" but it means that the SQ messages are displayed.

Maybe it is just me but I always have a problem understanding 'negative options' (like " --no-sq" ) and their = true or false state.
In this example it might be better to mention:
" --no-sq               Don't display messages with SQ label (default: these are displayed)".
Likewise it might be more clear to say:
"--no-empty            Don't display empty messages (default: empty messages are displayed)".

Thank you for your patience,
Dick

[Hobbyd]

One more observation:
I run acarsdeco2 like this:
./acarsdeco2  --no-console --freq-correction +4 --freq 131525000 131725000 131825000 --http-port 8888 --logfile test &

When I connect to port 8888 the Log tab shows
RegNo: PH-EZO Callsign: KL085F
But the Flights tab only shows the Regno, not the Callsign.

Cheers,
Dick

[Attachment deleted by Admin to save file space]

[Radio2.0]

Does anything on the Reception change?

[Hobbyd]

One more observation.
As most users I did not read the readme globally not carefully.
So I defined the 3 frequencies this way
--freq 131525000 131725000 131825000
And that works fine.

The .readme and the --help state that the correct way is --freq XX --freq YY, but  --freq XX YY .... also works.

  --freq arg            Set receiver frequency, Hz
                        Specify option --freq multiple times to multiple
                        channels (Example: --freq XX --freq YY ...)

Cheers,
Dick

[evangel]

Hi Sergsero

excellent work ! works ok my end with

Code Select Expand

cmd /c acarsdeco2.exe --gain 38.6 --freq-correction -9 --http-port 8282 --vrs-url http://127.0.0.1:8484 --db f:\db\bs.sqb --frdb f:\db\fr.sqb --silhouettes f:\db\silhouettes --pictures f:\db\pictures --banners f:\db\logos --outServer ad2:31108  --freq 131550000 131725000 130450000 131475000 --logfile c:\adsb\acarsdeco2017\acars.log





A nice add-on will be to have a 'Log Playback'  feature/button.

brgds/evangel

[Attachment deleted by Admin to save file space]

[HF-GCS]

Hi Forum, hello Sergsero,

at the first - thank you, for the new version, the webinterface is really beautiful!

It works so far, but i noticed some issues.
(Testing only the Windows versions)

• The decoded message rate is lower
• The timestamps of the ACARS messages, have a weird behavior, for example actual time is 10:51 UTC, timestamp of the actual received Message is 09:05 UTC!
  But the clock in the right corner of the webinterface, shows the right time in UTC and local!
  Same time mismatch in the command line window

Got this only with the versions 20170819 and 20170309, version 20150718 is great and the message rate is noticeable higher!
My PC-Clock is ok and i use the Meinberg NTP tool for accurate time sync.
After running the program for a short time, the time difference in the meanwhile are up to 4 minutes (please have a look on the screenshot)

• There are some special characters (only in messages in the command line) on Lat, Lon, Heading

I'm using Windows 10 with the latest updates!
I hope this feedback helps!?

[Attachment deleted by Admin to save file space]

[sergsero]

Hello,

Thank you for testing and for reporting about detected errors in the program. I carefully check and will try to fix it in next test version.

Best regards,
sergsero

[Radio2.0]

Does the Decoder Change?

[sergsero]

Hello,

Thank you very much for testing!

Best regards,
sergsero

[sergsero]

Hi,

Let me remind that for a successful receive ACARS messages you should be using the 'Frequency Correction' field in the configuration popup of SDRSharp to correct the frequency variation of a particular dongle.
Typically, once it's set it doesn't vary much from day to day. But you must do it after the dongle has been powered on for a while.

The difference between carrier frequency of the aircraft's transmitter and tuning frequency of the receiver should be minimal after about a 30 minute warm up.

Here is picture, which shows a method of exact adjustment of the frequency of dongle oscillator.

Regards,
sergsero

[Attachment deleted by Admin to save file space]

[Nigel]

The new test version is working fine for me. Thanks for the PlanePlotter fix. The new Web interface is excellent.

Many thanks

Nigel