Announcement

Collapse
No announcement yet.

Windows Setup/Feed Migration (virtualVM) Assistance

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Oblivian
    replied
    Almost 2 weeks with no broken stats or crashing feed app with beast via splitter doing the hardware connection instead

    So current version sure has an issue with multi direct downstream TCP connections it would seem.

    Leave a comment:


  • Stealth
    replied
    Originally posted by wiedehopf View Post
    the fr24feed on linux talks to Windows over the network
    That's lateral thinking; I like it.

    Leave a comment:


  • wiedehopf
    replied
    Originally posted by Stealth View Post
    Just to be sure that we are not talking at cross purposes. Are we talking about Oracle VM installed on Windows and running a linux virtual machine?
    Yes, you run Windows as per usual. Then install Virtualbox or Oracle VM. On the virtual machine you run linux.
    You can give the virtual machine control of a USB device and then handle the ModeS Beast in the virtual machine.
    Or you just get the data out of the Beast under Windows and the fr24feed on linux talks to Windows over the network

    Originally posted by Stealth View Post
    The Mode-S Beast may be a little more expensive, but better chance that the cost of pre-amps and filters will be saved and best of all, no dump1090 or derivatives.
    The pre-amp i linked employs triple filtering. Antenna --> high pass filter --> LNA --> SAW fitler --> LNA --> SAW filter --> output.
    But yeah if you don't like running dump1090 then you need a beast ;P

    Leave a comment:


  • Stealth
    replied
    Originally posted by wiedehopf View Post
    I'm not sure what would be best to talk to the ModeS Beast under Windows.
    You could just pass the USB device to the virtual machine and let the planefinder client handle it there, you are running that client anyway and it seems quite robust.
    I believe ModeSmixer2 also talks to the Beast under Windows.
    Not sure about planeploter?
    Just to be sure that we are not talking at cross purposes. Are we talking about Oracle VM installed on Windows and running a linux virtual machine?

    The Mode-S Beast may be a little more expensive, but better chance that the cost of pre-amps and filters will be saved and best of all, no dump1090 or derivatives.
    Last edited by Stealth; 2019-04-01, 12:10.

    Leave a comment:


  • wiedehopf
    replied
    Originally posted by Stealth View Post
    You are presumably talking about Oracle VM or similar? That thought had crossed my mind, the PC should have enough grunt and has plenty of space to run it. The question then is what to run as the feeder, as I'm not a fan of the fr24 variety at the moment. I'd prefer not to be getting my data from it alone.
    I'm not sure what would be best to talk to the ModeS Beast under Windows.
    You could just pass the USB device to the virtual machine and let the planefinder client handle it there, you are running that client anyway and it seems quite robust.
    I believe ModeSmixer2 also talks to the Beast under Windows.
    Not sure about planeploter?

    Leave a comment:


  • wiedehopf
    replied
    Originally posted by Oblivian View Post
    It was the first generation of devices sent to users before the radarcape...

    Worse, will be SBS users. Of which NONE have reported back their progress. le sigh.
    I guess they will just have to send out some of their complete receiver packages then

    (At this point I wonder if the SBS options for fr24feed even work, the feedback of people attempting to connect them hasn't been great)

    Leave a comment:


  • wiedehopf
    replied
    It's also rather expensive.

    Often a filtered LNA like this one is a cheaper alternative: https://www.rtl-sdr.com/new-product-...mhz-ads-b-lna/

    Of course the ModeS Beast performs very well and will catch more messages than the mentioned LNA combine with a rtl-sdr v3 dongle for example.

    But with that or a similar LNA you get good performance and it's usually sufficient.
    Last edited by wiedehopf; 2019-04-01, 11:38.

    Leave a comment:


  • Stealth
    replied
    Originally posted by wiedehopf View Post
    >SNIP<



    Also there just aren't that many ModeS Beast owners.
    There should be more, as in my case (fairly high background RF) it is shit loads better than a SDR, even with filters fitted.

    Leave a comment:


  • Oblivian
    replied
    Originally posted by wiedehopf View Post

    Also there just aren't that many ModeS Beast owners.
    It was the first generation of devices sent to users before the radarcape...

    Worse, will be SBS users. Of which NONE have reported back their progress. le sigh.

    Leave a comment:


  • wiedehopf
    replied
    Oh well.

    If you only run fr24feed it should be fine and not disconnect?

    Anyway making it 32 instead of 5 connections maximum shouldn't be that hard and i'm not quite sure how they came up with that limit.

    Also there just aren't that many ModeS Beast owners.
    Last edited by wiedehopf; 2019-04-01, 10:24.

    Leave a comment:


  • Oblivian
    replied
    Kinda overlooked my point...
    Complexity to me is nada. (And I've basically done all that already, But majority not running at once)

    Think of someone that's just bought a Pi (as advised by feed.flightradar24.com) cause their beloved windows is about to die.

    This is all the official support channel is going to want to support. The majority of which AREN'T likely forum users.

    Then realise how much we voluntarily give time to already, to provide them ongoing support outside of installing FR24feed. Attaching USB.
    without going down totally separate beastsplitter options - but opening our basic support up to those sort of configurations opens a whole lot of pain.
    If we thought there was a bunch of hurt assisting DVBT users....

    Leave a comment:


  • wiedehopf
    replied
    If you have piaware installed already you can install beast-splitter with:
    sudo apt-get install beast-splitter

    (No need for the piaware sd-card image, you just need the repository package)

    Next step is to enable it in its configuration file and point fr24feed and the other stuff to port to 30005.

    And i don't see much more complication compared to fr24feed being connected directly.
    Actually this way it's less of a "daisy-chain" and more a star model

    As there is no decoding necessary beast-splitter shouldn't use much CPU at all.
    Might actually reduce CPU load depending on how efficient the network side of fr24feed is coded.

    Leave a comment:


  • Oblivian
    replied
    I know y'all keen to throw all the bells and whistles suggestions at me like we do to most users to get things sorted.

    And well aware of the various possibilities. But I'm an advanced user, looking at it from a generic beast owner perspective, wanting to keep their Business plan - moving to a Pi following the instructions I come up with on notice of the Windows demise.
    - A basic overview without making it too hard for others. Almost matching current expected setups. (case in Point Stealth who tried 1:1 settings at first)

    Daisy chaining is just urg to those not aware how to. Which also leads to a few gotchas.
    Because its not an SDR, Can't use raw out of Piaware - it acts as a data-in only (SDR uses dump1090 SW decoding and opens the outputs). So can't swap around to hang FR off an FA output either.

    That is, if I read it right, unless I use their image. Which has the splitter built in. But that goes against FRs instructions some users may follow etching their image *sigh*
    Which strikes another option out that SDRs have an advantage over and introduces strife for anyone wanting to 'feed other sites' via USB without going down totally separate beastsplitter options - but opening our basic support up to those sort of configurations opens a whole lot of pain.

    At the same time, with such a focus on SDR modules, I feel I'm highlighting something that other Beast Owners with no choice migrating to a Pi - may have an issue with.
    Likely an indifference to the data out handling of windows port, in my case the only difference is the USB cable has been swung to a PI - of which FR24feed was always installed on for testing reported SDR experiences. Just not running at startup. (only to test beast MLAT worked from Pi version, or windows feeder via Pi hosted RAW out, but not direct USB in windows!)

    FA was always LAN feed (based on the Pi)
    FR24 was feed from windows direct USB (now direct USB pi)
    Apps used RAW out directly.



    Footnote-
    In my case, it's also an older Pi. And already loaded up with an SDR doing POCSAG decoding and some database work. Although I CAN load it up with all and sundry of converters/splitters, Attempting to avoid more process required apps to malform/convert the data when a native direct hardware connection should take care of it.

    Leave a comment:


  • wiedehopf
    replied
    Just don't use fr24feed to talk to the ModeS Beast.

    You can either use beast-splitter as i described in the other thread or you could for example run the planefinder client.
    (beast-splitter can be installed via apt-get on the RPi when you have the flightaware repository installed, no need to compile it)
    Under linux it can talk to the beast-splitter and will give out beast-tcp on port 30054.

    And i'm pretty sure both don't have any limitation on the number of connections or disconnect at random times.

    Leave a comment:


  • Oblivian
    replied
    Now like this for a bit (sooo many feed stats gaps in stats since going off windows..)

    Beast -> PI -> FR24 + FA

    Laptop: FR24feed (30334) -> ModeSMixer (30333) -> Planeplotter
    Laptop: FR24feed (30003) -> Logger

    Extra unnecessary step. But I want to make sure Planeplotter isn't hating on the raw port and eating up 5 connections it doesn't flush

    Next stop if it continues will be test without FA MLAT (apparently causes extra connections) or putting it back to

    Beast -> Laptop -> Planeplotter

    Pi: Planeplotter -> FR24feed

    And for the visual impact..
    FR24feed.jpg

    Leave a comment:

Working...
X