Announcement

Collapse
No announcement yet.

Windows Setup/Feed Migration (virtualVM) Assistance

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

  • #31
    You could also use this as the content of the udev file instead.


    But you would need to change the path to /dev/beast in the /etc/fr24feed.ini and add the fr24 user to the group beast (and create the group beast).

    That is a little more targeted and elegant than giving everyone access to /dev/ttyUSB

    Comment


    • #32
      For some reason it can no longer connect to ttyUSB0, although the ls command shows it is present. My sudo usermod line doesn't fix it, nor does wiedehopf's custom udev rule. That'll do for this morning, thanks all. Noted the comment Oblivian about PP config, I'll try it later without the wizard.

      Comment


      • #33
        Currently working (as seen by background greens)

        planeplotter.jpg

        If I accidentally set to a wrong port, or wrong IP (or USB direct) = crash

        Which is what is happening when FR24 decides to stop accepting connections on me and it retries (grrr!)
        Posts not to be taken as official support representation - Just a helpful uploader who tinkers

        Comment


        • #34
          Originally posted by Oblivian View Post
          Currently working (as seen by background greens)

          [ATTACH=CONFIG]10475[/ATTACH]

          If I accidentally set to a wrong port, or wrong IP (or USB direct) = crash

          Which is what is happening when FR24 decides to stop accepting connections on me and it retries (grrr!)
          Now if I could get FR24feed talking to ttyUSB0 again I'd replicate those settings.......

          Comment


          • #35
            Maybe just do a reboot and check if ttyUSB0 is still present?
            this will show it present:
            ls /dev/ttyUSB*

            Comment


            • #36
              Originally posted by wiedehopf View Post
              Maybe just do a reboot and check if ttyUSB0 is still present?
              this will show it present:
              ls /dev/ttyUSB*
              Yes, still shows present. Whether its related I don't know, but Ubuntu is throwing up an unspecified software error now and asking if I want to report it. There is no clue as to what the error or software is.

              Comment


              • #37
                Just in case remove the file with the udev rule. Maybe it's complicating something.

                Then do another reboot.

                Comment


                • #38
                  It appears it may be related to the fr24feed auto-start. On rebooting I entered 'fr24feed -status' and saw that it was creating the FR24 feed and then trying to connect to the Beast via ttyUSB0. So after a minute or two of connecting attempts, I opened another terminal and ran 'sudo service fr24feed stop'. The original terminal continued to show connection attempts. In the second terminal I then ran 'sudo fr24feed' and everything came up and running. I'll have to look back through a few posts to find out what steps I used.

                  I've configured Planeplotter as per Oblivian's settings, and also activated the software. Getting shared traffic, but yet to get the local traffic.
                  Last edited by Stealth; 2019-03-30, 05:34.

                  Comment


                  • #39
                    fr24feed -status

                    Will re-run a second copy. Default install is run-as-service =conflict of devices

                    the proper command is

                    sudo fr24feed-status.... no space! Or it runs the command 'fr24feed' on it's own (ignoring the 2nd portion as no valid option record)

                    I'm advised the .deb install version requires sudo fr24feed --status
                    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                    Comment


                    • #40
                      Ahhhh, that could be the issue. I think that's confirmed when I browse to localhost:8745 and it tells me no aircraft have been uploaded, but FR web site is showing traffic being uploaded.

                      EDIT
                      Tried:
                      sudo fr24feed-status
                      sudo fr24feed--status

                      Both gave unknown command

                      sudo fr24feed --status >brought up fr24feed, appeared that it had started the app

                      localhost:8745 now shows it running correctly with MLAT

                      Planeplotter is now showing local traffic.

                      EDIT No.2 Planefinder is also now working (linux not wine)
                      Last edited by Stealth; 2019-03-30, 06:29.

                      Comment


                      • #41
                        Just when I thought I was on a roll, more issues. Seems that FR24feed doesn't like more than one additional connection. After adding Planefinder and watching it for a few minutesI went for a refreshing walk, came back to fr24 protesting "Too many connections!"

                        I'll restart it and monitor, but is it at this point I just say too hard.....?

                        Comment


                        • #42
                          Originally posted by Stealth View Post
                          Just when I thought I was on a roll, more issues. Seems that FR24feed doesn't like more than one additional connection. After adding Planefinder and watching it for a few minutesI went for a refreshing walk, came back to fr24 protesting "Too many connections!"

                          I'll restart it and monitor, but is it at this point I just say too hard.....?
                          You can have 5 connections. I run 4. And I think PP (or one of my others) refreshes itself as every now and then it says one disconnected, connection detected - 1 left.

                          Be thankful I got them to raise it from 2 saying it wasn't enough!

                          /edit at least I think the Pi version is 5. Windows sure was as I struck issues
                          Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                          Comment


                          • #43
                            Originally posted by Oblivian View Post
                            You can have 5 connections. I run 4. And I think PP (or one of my others) refreshes itself as every now and then it says one disconnected, connection detected - 1 left.

                            Be thankful I got them to raise it from 2 saying it wasn't enough!

                            /edit at least I think the Pi version is 5. Windows sure was as I struck issues
                            I ran it again for about 30 minutes and the problem didn't come up. What I did notice is that the data flow is interrupted and that a connect/disconnect sequence to the beast is occurring every 10 or 15 seconds. I monitored Planefinder's data page and data was dropping out for a second or two on a regular basis. It's not so easy to see on Planeplotter. I also noticed that PF wasn't getting any Mode AC packets.

                            Other than power outages, the mini-PC has run PP, PF, VRS and FR24, H24 for more than a year. I'll need that kind of confidence before I'll commit to a switch.

                            Comment


                            • #44
                              Originally posted by Stealth View Post
                              I ran it again for about 30 minutes and the problem didn't come up. What I did notice is that the data flow is interrupted and that a connect/disconnect sequence to the beast is occurring every 10 or 15 seconds. I monitored Planefinder's data page and data was dropping out for a second or two on a regular basis. It's not so easy to see on Planeplotter. I also noticed that PF wasn't getting any Mode AC packets.

                              Other than power outages, the mini-PC has run PP, PF, VRS and FR24, H24 for more than a year. I'll need that kind of confidence before I'll commit to a switch.
                              Planeplotter, Piaware, SQL poll (30003) and ModeSMil uploader.

                              Every 2 mins...

                              2019-03-30 10:44:47 | [feed][i]sent 20,2 AC
                              2019-03-30 10:44:50 | [feed][i]removed 1 of 24 AC
                              2019-03-30 10:44:52 | [feed][i]sent 20,2 AC
                              2019-03-30 10:44:57 | [feed][i]sent 21,2 AC
                              2019-03-30 10:44:59 | [bs][i]New client connected 192.168.0.8:60028
                              2019-03-30 10:44:59 | [bs][i]Client disconnected, 2 left
                              2019-03-30 10:45:02 | [mlat][i]Pinging the server
                              2019-03-30 10:45:02 | [feed][i]sent 20,2 AC
                              2019-03-30 10:45:02 | [mlat][i]Stats 1191992/418
                              2019-03-30 10:45:07 | [feed][i]sent 19,2 AC
                              2019-03-30 10:45:12 | [feed][i]sent 19,2 AC
                              2019-03-30 10:45:17 | [feed][i]sent 20,2 AC
                              2019-03-30 10:45:22 | [feed][i]sent 19,2 AC
                              2019-03-30 10:45:22 | [mlat][i]Pinging the server
                              2019-03-30 10:45:22 | [mlat][i]Stats 1192425/433
                              2019-03-30 10:45:27 | [feed][i]sent 19,2 AC
                              2019-03-30 10:45:32 | [feed][i]sent 20,2 AC
                              2019-03-30 10:45:33 | [feed][i]filtering out 2 overlapping AC (saving bandwidth)
                              2019-03-30 10:45:37 | [feed][i]sent 19,2 AC
                              2019-03-30 10:45:42 | [feed][i]sent 20,2 AC
                              2019-03-30 10:45:42 | [mlat][i]Pinging the server
                              2019-03-30 10:45:42 | [mlat][i]Stats 1192856/431
                              2019-03-30 10:45:47 | [feed][i]sent 19,2 AC
                              2019-03-30 10:45:52 | [feed][i]sent 20,2 AC
                              2019-03-30 10:45:57 | [feed][i]sent 21,2 AC
                              2019-03-30 10:45:58 | [feed][i]removed 2 of 25 AC
                              2019-03-30 10:46:02 | [mlat][i]Pinging the server
                              2019-03-30 10:46:02 | [mlat][i]Stats 1193254/398
                              2019-03-30 10:46:02 | [feed][i]sent 21,2 AC
                              2019-03-30 10:46:07 | [feed][i]sent 19,1 AC
                              2019-03-30 10:46:12 | [feed][i]sent 19,1 AC
                              2019-03-30 10:46:17 | [feed][i]sent 19,1 AC
                              2019-03-30 10:46:22 | [mlat][i]Pinging the server
                              2019-03-30 10:46:22 | [mlat][i]Stats 1193625/371
                              2019-03-30 10:46:22 | [feed][i]sent 19,2 AC
                              2019-03-30 10:46:26 | [bs][i]New client connected 192.168.0.8:60038
                              2019-03-30 10:46:26 | [bs][i]Client disconnected, 2 left
                              2019-03-30 10:46:27 | [feed][i]sent 20,1 AC
                              2019-03-30 10:46:32 | [feed][i]sent 18,1 AC
                              2019-03-30 10:46:33 | [feed][i]filtering out 4 overlapping AC (saving bandwidth)
                              2019-03-30 10:46:37 | [feed][i]sent 16,3 AC
                              2019-03-30 10:46:42 | [mlat][i]Pinging the server
                              2019-03-30 10:46:42 | [mlat][i]Stats 1194049/424
                              2019-03-30 10:46:42 | [feed][i]sent 16,3 AC
                              2019-03-30 10:46:47 | [feed][i]sent 15,3 AC
                              2019-03-30 10:46:52 | [feed][i]sent 18,4 AC
                              2019-03-30 10:46:58 | [feed][i]sent 17,4 AC
                              2019-03-30 10:47:02 | [feed][i]removed 1 of 24 AC
                              2019-03-30 10:47:02 | [mlat][i]Pinging the server
                              2019-03-30 10:47:02 | [mlat][i]Stats 1194435/386
                              2019-03-30 10:47:03 | [feed][i]sent 17,4 AC
                              2019-03-30 10:47:08 | [feed][i]sent 17,4 AC
                              2019-03-30 10:47:13 | [mlat][i]Received ADS-B time references AC:
                              Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                              Comment


                              • #45
                                Any command like "fr24feed" or "fr24feed -foo" or "fr24feed --foo" will start a NEW instance of fr24feed.
                                The systemd service has already started fr24feed.
                                Why you have to start it again by any other command?

                                To check status, use this command:
                                Code:
                                abcd@ubuntu-bionic:~$ sudo systemctl status fr24feed 
                                
                                [sudo] password for abcd:
                                
                                ● fr24feed.service - Flightradar24 Decoder & Feeder
                                   Loaded: loaded (/lib/systemd/system/fr24feed.service; enabled; vendor preset: enabled)
                                   Active: active (running) since Sat 2019-03-30 03:38:00 EDT; 8min ago
                                 Main PID: 702 (fr24feed)
                                    Tasks: 10 (limit: 2318)
                                   CGroup: /system.slice/fr24feed.service
                                           └─702 /usr/bin/fr24feed
                                
                                Mar 30 03:38:00 ubuntu-bionic systemd[1]: Started Flightradar24 Decoder & Feeder.
                                Last edited by abcd567; 2019-03-30, 07:56.

                                Comment

                                Working...
                                X