search

TLeconte / acarsdec

ACARS SDR decoder
336 stars 90 forks source link

Using 2 instances of acarsdec on rpi #81

Closed keukenrol closed 2 years ago

keukenrol commented 2 years ago

Hi

I am interested in using 2 instances of acarsdec with two different rtl dongles. Reason being that the dongles have a bandwidth of 2.4MHz which is too narrow to cover both 131 and 136MHz acars channels. What should be the best method? Call the program twice with different parameters and run in background?

Second question: Is it possible to have a web preview?

Third question: Can the logs be written realtime to a csv? I would love to show them on my custom webpage and possibly link them to the basestation.sqb from VRS like they did with acarsdeco2.

Kind regards

TLeconte commented 2 years ago
keukenrol commented 2 years ago
  • I never try that, but yes you must be able to run 2 acarsdec instances with different rtl device number (ie : -r 0 and -r 1 ) But where will you send the results ?

By for example using a csv :).

  • What do you mean by a web preview ? An integrated web server ?

Yes, I come from acarsdeco2, where all decoded messages are shown on a webpage.

  • You want that I add a csv format to -o option ?

Yes, by integrating this it is easy to display the acars yourself on a webpage, no need to implement the webserver in acarsdec then. In case you use two instances, I think it would be good to have the option to also set a filename.

For example: Instance 1: acarsdec -r 0 131.550 131.725 131.825 -o csv acars_131.csv Instance 2: acarsdec -r 1 136.750 136.900 136.950 -o csv acars_136.csv

Thanks for your reply, appreciate it.

TLeconte commented 2 years ago

I will not code an integrated web server, not my domain. Don't json a good format for the log ? Because it already exist : -o 4 I don't think csv is a good format for acars because there are \n in message acars body There is already the -l option to tell where acarsdec save its log

keukenrol commented 2 years ago

Allright, fairly new to it all. I'll use the json. Thanks!