Announcement

Collapse
No announcement yet.

Afatech AF9033 (ITE IT9135) Compatibility

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

  • Afatech AF9033 (ITE IT9135) Compatibility

    Hi! I have a Raspberry Pi working with DVB-T receiver "Afatech AF9033" with ITE IT9135 chip. The receiver works fine on /dev/dvb/adapter0 in tvheadend, however, fr24feed does not seem to recognize this adapter and tries to connect to Beast receiver.

    Log:
    Code:
    pi@servername:~ $ sudo fr24feed
    2016-05-03 07:23:27 | [main][i]FR24 Feeder/Decoder
    2016-05-03 07:23:27 | [main][i]Version: 1.0.18-5/generic
    2016-05-03 07:23:27 | [main][i]Built on Mar  4 2016 15:21:10 (HEAD-d11ca48.git/Linux/armv7l)
    2016-05-03 07:23:27 | [main][i]Copyright 2012-2016 Flightradar24 AB
    2016-05-03 07:23:27 | [main][i]DNS mode: LIBC
    2016-05-03 07:23:27 | [main][i]Automatic updates are DISABLED
    2016-05-03 07:23:27 | ERROR
    2016-05-03 07:23:27 | [httpd][e]bind function failed, errno: 98
    2016-05-03 07:23:27 | [httpd][d]Master thread terminated
    2016-05-03 07:23:27 | [main][i]Reader thread started
    2016-05-03 07:23:27 | [master][i]Starting processing thread
    2016-05-03 07:23:27 | [reader][i]Initializing reader
    2016-05-03 07:23:27 | [main][i]MLAT data feed started
    2016-05-03 07:23:27 | [reader][i]Connecting to Beast receiver via (exe:///usr/lib/fr24/dump1090  --raw --mlat)
    2016-05-03 07:23:27 | [mlat][i]Waiting for MLAT configuration
    2016-05-03 07:23:27 | [reader][i]Connected to the receiver, configuring
    2016-05-03 07:23:27 | [reader][i]Configured, processing messages
    No supported RTLSDR devices found.
    2016-05-03 07:23:27 | [reader][i]Connection terminated
    2016-05-03 07:23:27 | [main][i]Terminating child process 1386 with SIGETERM
    2016-05-03 07:23:28 | [time][i]Synchronizing time via NTP
    2016-05-03 07:23:31 | [time][i]Time synchronized correctly, offset -0.0014 seconds
    2016-05-03 07:23:31 | [main][i]Feed Network client started
    2016-05-03 07:23:31 | [feed][i]Downloading configuration
    2016-05-03 07:23:31 | [feed][c]Interval: 5s
    2016-05-03 07:23:31 | [feed][c]Latitude: XX.XXXX
    2016-05-03 07:23:31 | [feed][c]Longitude: XX.XXXX
    2016-05-03 07:23:31 | [feed][c]GND: YES
    2016-05-03 07:23:31 | [feed][c]NonADSB: YES
    2016-05-03 07:23:31 | [feed][c]Timestamps: optional
    2016-05-03 07:23:31 | [feed][c]Max range AIR: 350.0nm
    2016-05-03 07:23:31 | [feed][c]Max range GND: 100.0nm
    2016-05-03 07:23:31 | [feed][i]defined 4 servers
    2016-05-03 07:23:31 | [stats][i]Stats thread started
    2016-05-03 07:23:31 | [feed][n]XXXXX@XXXXXXXXXX:XXXX/UDP
    2016-05-03 07:23:31 | [feed][n]connecting
    2016-05-03 07:23:33 | [reader][i]Connecting to Beast receiver via (exe:///usr/lib/fr24/dump1090  --raw --mlat)
    2016-05-03 07:23:33 | [reader][i]Connected to the receiver, configuring
    2016-05-03 07:23:33 | [reader][i]Configured, processing messages
    No supported RTLSDR devices found.
    2016-05-03 07:23:33 | [reader][i]Connection terminated
    2016-05-03 07:23:33 | [main][i]Terminating child process 1392 with SIGETERM
    2016-05-03 07:23:38 | [reader][i]Connecting to Beast receiver via (exe:///usr/lib/fr24/dump1090  --raw --mlat)
    2016-05-03 07:23:38 | [reader][i]Connected to the receiver, configuring
    2016-05-03 07:23:38 | [reader][i]Configured, processing messages
    No supported RTLSDR devices found.
    2016-05-03 07:23:38 | [reader][i]Connection terminated
    "No supported RTLSDR devices found."

    /etc/fr24feed.ini:
    Code:
    receiver="dvbt"
    fr24key="XXXXXXXXXXXXXXXX"
    path="/usr/lib/fr24/dump1090"
    bs="no"
    raw="no"
    logmode="0"
    mlat="yes"
    mlat-without-gps="yes"
    Webinterface:
    Code:
    Flightradar24 Feeder/Decoder
    
    Linux/generic/armv7l/1.0.18-5
    
    Updated: 07:18:55 GMT+0200 (W. Europe Daylight Time)
    
    FR24 Link:	Connected via UDP
    FR24 Radar Code:	 XXXXXXXXXXX
    Aircraft Tracked (ModeS & ADS-B):	0
    Aircraft Uploaded:	N/A
    Receiver:	dvbt, Connected
    MLAT running:	NO
    Any idea if this adapter actually is not supported / compatible or whether it will be in the near future?

    Thanks for your help!
Working...
X