Announcement

Collapse
No announcement yet.

FR24 Hardware not feeding since I moved to a new location

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

  • FR24 Hardware not feeding since I moved to a new location

    My feeder, F-KBTV1 is not connecting to FR24 and providing data and I am unsure why. The device is properly connected to the internet, the GPS and antenna are functional and connected. There are only so many things that I can do in terms of configuring the device and I have done everything I can think of. There is no clear reason why the device fails to feed its data. I am providing a short snippet of the log.


    2015-10-30 22:10:55 | [gps][i]Connected to the GPS receiver
    2015-10-30 22:10:56 | [feed][n]ping 62
    2015-10-30 22:10:56 | [gps][i]New position: 41.34,-71.99, 2.0,22:11:15
    2015-10-30 22:10:56 | [mlat][i]Configuring UDP connection udp://usa-2.fr24.com:19788
    2015-10-30 22:10:56 | [mlat][i]Timebase is GPS
    2015-10-30 22:10:56 | [mlat][i]Registering MLAT station
    2015-10-30 22:10:56 | [mlat][i]Registering MLAT station: SUCCESS
    2015-10-30 22:10:57 | [time][e]Time synchronized, offset +2.0371 seconds, drift 0.0209 seconds/minute
    2015-10-30 22:10:59 | [mlat][i]Pinging the server
    2015-10-30 22:10:59 | [time][i]Synchronizing time via NTP
    2015-10-30 22:11:01 | [time][e]Time synchronized, offset +2.0714 seconds, drift 0.0144 seconds/minute
    2015-10-30 22:11:03 | [time][i]Synchronizing time via NTP
    2015-10-30 22:11:06 | [time][e]Time synchronized, offset +3.0086 seconds, drift 0.0156 seconds/minute
    2015-10-30 22:11:08 | [time][i]Synchronizing time via NTP
    2015-10-30 22:11:10 | [time][e]Time synchronized, offset +3.0441 seconds, drift 0.0149 seconds/minute
    2015-10-30 22:11:12 | [time][i]Synchronizing time via NTP
    2015-10-30 22:11:14 | [time][e]Time synchronized, offset +3.0809 seconds, drift 0.0153 seconds/minute
    2015-10-30 22:11:16 | [time][i]Synchronizing time via NTP
    2015-10-30 22:11:19 | [mlat][i]Stats 0/0
    2015-10-30 22:11:20 | [time][e]Time synchronized, offset +4.0276 seconds, drift 0.0194 seconds/minute
    2015-10-30 22:11:22 | [time][i]Synchronizing time via NTP
    2015-10-30 22:11:25 | [time][e]Time synchronized, offset +4.0747 seconds, drift 0.0195 seconds/minute
    2015-10-30 22:11:26 | [feed][n]ping 63
    2015-10-30 22:11:27 | [time][i]Synchronizing time via NTP
    2015-10-30 22:11:30 | [time][e]Time synchronized, offset +5.0075 seconds, drift 0.0135 seconds/minute
    2015-10-30 22:11:31 | [mlat][i]Pinging the server
    2015-10-30 22:11:31 | [mlat][i]Stats 0/0
    2015-10-30 22:11:32 | [gps][e]No time update for 30/120 seconds or more, disconnecting from GPS
    2015-10-30 22:11:32 | [gps][i]Connected to the GPS receiver
    2015-10-30 22:11:32 | [time][i]Synchronizing time via NTP
    2015-10-30 22:11:33 | [gps][i]New position: 41.34,-71.99, 2.0,22:11:55
    2015-10-30 22:11:33 | [mlat][i]Configuring UDP connection udp://usa-2.fr24.com:19788
    2015-10-30 22:11:33 | [mlat][i]Timebase is GPS
    2015-10-30 22:11:33 | [mlat][i]Registering MLAT station
    2015-10-30 22:11:33 | [mlat][i]Registering MLAT station: SUCCESS
    2015-10-30 22:11:34 | [time][e]Time synchronized, offset +5.0459 seconds, drift 0.0158 seconds/minute
    2015-10-30 22:11:36 | [time][i]Synchronizing time via NTP
    2015-10-30 22:11:38 | [time][e]Time synchronized, offset +5.0816 seconds, drift 0.0146 seconds/minute
    2015-10-30 22:11:40 | [time][i]Synchronizing time via NTP
    2015-10-30 22:11:43 | [time][e]Time synchronized, offset +6.0157 seconds, drift 0.0139 seconds/minute
    2015-10-30 22:11:45 | [time][i]Synchronizing time via NTP
    2015-10-30 22:11:47 | [time][e]Time synchronized, offset +6.0500 seconds, drift 0.0140 seconds/minute
    2015-10-30 22:11:49 | [time][i]Synchronizing time via NTP
    2015-10-30 22:11:51 | [time][e]Time synchronized, offset +6.0868 seconds, drift 0.0150 seconds/minute
    2015-10-30 22:11:53 | [time][i]Synchronizing time via NTP
    2015-10-30 22:11:56 | [time][e]Time synchronized, offset +7.0272 seconds, drift 0.0163 seconds/minute
    2015-10-30 22:11:56 | [feed][n]ping 64
    2015-10-30 22:11:57 | [mlat][i]Pinging the server
    2015-10-30 22:11:57 | [mlat][i]Stats 0/0
    2015-10-30 22:11:58 | [time][i]Synchronizing time via NTP
    2015-10-30 22:12:01 | [time][e]Time synchronized, offset +7.0651 seconds, drift 0.0153 seconds/minute
    2015-10-30 22:12:01 | [time][i]Synchronizing time via NTP
    2015-10-30 22:12:03 | [time][e]Time synchronized, offset +7.0894 seconds, drift 0.0098 seconds/minute
    2015-10-30 22:12:14 | [time][i]Synchronizing time via NTP
    2015-10-30 22:12:16 | [time][e]Time synchronized, offset -0.0519 seconds, drift -0.3363 seconds/minute
    2015-10-30 22:12:18 | [time][i]Synchronizing time via NTP
    2015-10-30 22:12:20 | [mlat][i]Pinging the server
    2015-10-30 22:12:20 | [mlat][i]Stats 0/0
    2015-10-30 22:12:20 | [time][e]Time synchronized, offset -0.0163 seconds, drift 0.0142 seconds/minute
    2015-10-30 22:12:22 | [time][i]Synchronizing time via NTP
    2015-10-30 22:12:26 | [time][e]Time synchronized, offset +0.0249 seconds, drift 0.0164 seconds/minute
    2015-10-30 22:12:28 | [time][i]Synchronizing time via NTP
    2015-10-30 22:12:30 | [time][e]Time synchronized, offset +0.0650 seconds, drift 0.0159 seconds/minute
    2015-10-30 22:12:32 | [time][i]Synchronizing time via NTP
    2015-10-30 22:12:35 | [feed][n]ping 65
    2015-10-30 22:12:36 | [time][e]Time synchronized, offset +1.0076 seconds, drift 0.0168 seconds/minute
    2015-10-30 22:12:38 | [time][i]Synchronizing time via NTP
    2015-10-30 22:12:41 | [time][e]Time synchronized, offset +1.0456 seconds, drift 0.0149 seconds/minute
    2015-10-30 22:12:42 | [mlat][i]Pinging the server
    2015-10-30 22:12:42 | [mlat][i]Stats 0/0
    2015-10-30 22:12:43 | [time][i]Synchronizing time via NTP
    2015-10-30 22:12:46 | [time][e]Time synchronized, offset +1.0941 seconds, drift 0.0190 seconds/minute
    2015-10-30 22:12:48 | [time][i]Synchronizing time via NTP
    2015-10-30 22:12:52 | [time][e]Time synchronized, offset +2.0307 seconds, drift 0.0143 seconds/minute
    2015-10-30 22:12:54 | [time][i]Synchronizing time via NTP
    2015-10-30 22:12:56 | [time][e]Time synchronized, offset +2.0783 seconds, drift 0.0185 seconds/minute
    2015-10-30 22:12:58 | [time][i]Synchronizing time via NTP
    2015-10-30 22:13:02 | [time][e]Time synchronized, offset +3.0138 seconds, drift 0.0138 seconds/minute
    2015-10-30 22:13:04 | [time][i]Synchronizing time via NTP
    2015-10-30 22:13:05 | [feed][n]ping 66
    2015-10-30 22:13:06 | [time][e]Time synchronized, offset +3.0614 seconds, drift 0.0184 seconds/minute
    2015-10-30 22:13:08 | [time][i]Synchronizing time via NTP
    2015-10-30 22:13:10 | [time][e]Time synchronized, offset +3.0985 seconds, drift 0.0143 seconds/minute
    2015-10-30 22:13:12 | [time][i]Synchronizing time via NTP
    2015-10-30 22:13:14 | [mlat][i]Pinging the server

  • #2
    Well after about 6 hours of what I posted above occurring I noticed the following:

    2015-10-31 01:41:39 | [stats][e]Cached feed_id=1820 for network F
    It appears to be slowly sorting itself out (I hope).

    It still is not utilizing the antenna at all, while ADS-B/Mode S are connected they have yet to actually track a single play.
    Last edited by drew13btv; 2015-10-31, 01:58.

    Comment


    • #3
      As you would know FR2 is monitors and controls your box remotely. If you are worried notify them on support@fr24.com

      BTW, have you informed them about your new location? MLAT calculations depend on exact location info, and I believe the GPS is only use for time synchronization and not for position (not 100% sure)

      Comment


      • #4
        Originally posted by Kpin View Post
        As you would know FR2 is monitors and controls your box remotely. If you are worried notify them on support@fr24.com

        BTW, have you informed them about your new location? MLAT calculations depend on exact location info, and I believe the GPS is only use for time synchronization and not for position (not 100% sure)
        Thank you for your response. The location is up to date and not the reason for the issues it is having. It correctly identifies its position and in the log it shows that it is using the new coordinates for MLAT capability properly.

        I did reach out to support when I made this post. I was just reaching out for help in multiple locations to try and get this resolved. Thank you for your response

        Comment

        Working...
        X