Author Topic: No ADSB traffic reported on Logging  (Read 10137 times)

flying_john

No ADSB traffic reported on Logging
« on: December 02, 2015, 12:59:11 pm »
All the bits arrived today so followed instructions and everything seems fine.

BUT - I cant see any ADSB traffic - I was expecting to see commercial stuff, even if no-one is mad enough to go out and fly themselves today. I do not have the RF board fitted.

My log shows:
TRX-SER: Data Mode
TRX-SER: ERROR!!! Comms buf=''
TRX-SER: Apply Default settings
TRX-SER: write CMD_SV650_RD_PAR
TRX-SER: CMD_SV650_VER -> ''
TRX-SER: write CMD_SV650_VER
TRX-SER: Control Mode
TRX-SER: Awake
TRX-SER: Sleep
TRX-SER: SV650 Programming Begin
TRX-SER: Configuration Failed
TRX-SER: Failed Communication at 57600 Baud
TRX-SER: Attempt 10 Communication at 57600 Baud
TRX-SER: Attempt 9 Communication at 57600 Baud
TRX-SER: Attempt 8 Communication at 57600 Baud
TRX-SER: Attempt 7 Communication at 57600 Baud
TRX-SER: Attempt 6 Communication at 57600 Baud
TRX-SER: Attempt 5 Communication at 57600 Baud
TRX-SER: Attempt 4 Communication at 57600 Baud
TRX-SER: Attempt 3 Communication at 57600 Baud
TRX-SER: Attempt 2 Communication at 57600 Baud
TRX-SER: Attempt 1 Communication at 57600 Baud
TRX-SER: Await Command mode Timeout
TRX-SER: Failed Communication at 9600 Baud
TRX-SER: Attempt 5 Communication at 9600 Baud
TRX-SER: Attempt 4 Communication at 9600 Baud
TRX-SER: Attempt 3 Communication at 9600 Baud
TRX-SER: Attempt 2 Communication at 9600 Baud
SDR-USB: Connected
SDR-USB: Attempting connection
NAV-TCP: Listening... 2000
NAV-TCP: Listening for Connection
TRP-USB: Startup
RX-GPS-USB: Startup
GPS-TCP: Listening... 2001
GPS-TCP: Listening for connection
TRX-SER: Attempt 1 Communication at 9600 Baud
TRX-SER: ARF Programming Begin
License Fail for wlan0 00:13:EF:C7:09:8F
License Fail for  eth0 B8:27:EB:C5:D5:0F
License Fail for wlan0 00:13:EF:C7:09:8F
License Fail for  eth0 B8:27:EB:C5:D5:0F
License Fail for wlan0 00:13:EF:C7:09:8F
License Fail for  eth0 B8:27:EB:C5:D5:0F
License Fail for wlan0 00:13:EF:C7:09:8F
License Fail for  eth0 B8:27:EB:C5:D5:0F
License Fail for wlan0 00:13:EF:C7:09:8F
License Fail for  eth0 B8:27:EB:C5:D5:0F
License Fail for wlan0 00:13:EF:C7:09:8F
License Fail for  eth0 B8:27:EB:C5:D5:0F
License Fail for wlan0 00:13:EF:C7:09:8F
License Fail for  eth0 B8:27:EB:C5:D5:0Fa

exfirepro

Re: No ADSB traffic reported on Logging
« Reply #1 on: December 02, 2015, 02:02:19 pm »
From my limited knowledge, it looks like you haven't put in your licence details on the configuration screen. Could this be the case?

Hopefully Lee will pick up on this and confirm.

ianfallon

Re: No ADSB traffic reported on Logging
« Reply #2 on: December 02, 2015, 02:33:29 pm »
It does rather look that way.

See p19 and p21 of the software installation guide:

http://forum.pilotaware.com/index.php/topic,231.0.html

flying_john

Re: No ADSB traffic reported on Logging
« Reply #3 on: December 02, 2015, 02:51:40 pm »
Thanks for advice.

I have re-checked the input of the supplied licence key and still  nothing displayed under Traffic on the laptop and yet the count of ADSB messages is increasing. I was looking for a simple way to test it is receiving traffic (i.e the Tuner dongle was working) before I go over the airfield and connect up to the Ipad running RunwayHD. I  want to get this bit working before the P3i is added.

Is there a way of running a Term session on the USB serial out to the transponder to see whether it is outputing any NMEA sentences.

Or perhaps using the RJ45 interface and looking.

One of the most frustrating things is keep having to swap Wi-Fi from the PAW to the home network, but if I dispensed with the Paw Wi-fi whilst testing and could plug the RJ45 from the laptop to the PAW it would simplify things. Is there a way ?

JOhn


Richard

Re: No ADSB traffic reported on Logging
« Reply #4 on: December 02, 2015, 02:56:04 pm »
Could it be that you have not set the "show tragic above alt" or is it "hide tragic above alt" in the settings ?
« Last Edit: December 02, 2015, 02:57:53 pm by Richard »
Richard.
Europa XS

Admin

Re: No ADSB traffic reported on Logging
« Reply #5 on: December 02, 2015, 03:24:08 pm »
Thanks for advice.

I have re-checked the input of the supplied licence key and still  nothing displayed under Traffic on the laptop and yet the count of ADSB messages is increasing. I was looking for a simple way to test it is receiving traffic (i.e the Tuner dongle was working) before I go over the airfield and connect up to the Ipad running RunwayHD. I  want to get this bit working before the P3i is added.

Is there a way of running a Term session on the USB serial out to the transponder to see whether it is outputing any NMEA sentences.

Or perhaps using the RJ45 interface and looking.

One of the most frustrating things is keep having to swap Wi-Fi from the PAW to the home network, but if I dispensed with the Paw Wi-fi whilst testing and could plug the RJ45 from the laptop to the PAW it would simplify things. Is there a way ?

JOhn

Techy Mode ON
ok, you can connect PAW to your wired network, the Fixed IP address is 192.168.0.100, the subnet mask on your router must be setup to pass traffic, so would need to be 255.255.255.0

yes you can run a terminal, try connecting to port 2000 on the PAW WiFi=192.168.1.1 Wired=192.168.0.100
    telnet 192.168.0.100 2000
or
    telnet 192.168.1.1 2000
You will be asked for a 'PASS?', which I suggest would be 6001
Messages are then streamed to your terminal

Alternately, much simpler to attach a web browser to 192.168.1.1 or 192.168.0.100 accordingly
This has a logging feature, log verbosity can be enabled under config menu
Techy Mode OFF

Hope that helps

flying_john

Re: No ADSB traffic reported on Logging
« Reply #6 on: December 02, 2015, 03:35:10 pm »
Quote
Alternately, much simpler to attach a web browser to 192.168.1.1 or 192.168.0.100 accordingly
This has a logging feature, log verbosity can be enabled under config menu

Am connected to the PAW via browser session and am in the log screen. I have tried to switch on NMEA and ADSB logging in config, but doesn't change what is on the logging screen. Seems to be stuck with ERROR Coms buf=' ' Data Mode.

Quote
Could it be that you have not set the "show tragic above alt" or is it "hide tragic above alt" in the settings ?
Cant find anything in config about showing traffic above/below a certain altitude.

What now, I wonder.

Admin

Re: No ADSB traffic reported on Logging
« Reply #7 on: December 02, 2015, 03:39:01 pm »
Hi John

Go to the home screen for 192.168.1.1
There is a table with an entry for each interface, easiest to post the entire table

Quote
Cant find anything in config about showing traffic above/below a certain altitude.
This is a NAV tool option to display traffic at certain height separation

Thx
Lee
« Last Edit: December 02, 2015, 03:42:20 pm by Admin »

flying_john

Re: No ADSB traffic reported on Logging
« Reply #8 on: December 02, 2015, 05:10:33 pm »
Configure  Logging  Traffic
PilotAware (20151114), Expires 20161201
______________Interface______________   __________________Status__________________
NAVIGATION   Off
Sorry the table formating gets lost in the cut n paste:-

ADS-B (DVB-T)   Enabled Msgs=96199(+3526)
TRX (RXTX)   Enabled TX=0 RX=0 CRCFAIL=0
Pressure Altitude (BMP)   Unavailable (Manual) QNH=1013mb QNE=0ft GNSS=0ft
GPS Sentences (TCP)   Msgs=0(+0)
GPS Sentences (UDP)   Msgs=0(+0)
GPS Sentences (USB)   Msgs=0(+0) Fix="Invalid" Mode="Undefined" Satellites=0
USB Bus 001 Device 002: ID 0424:9514   Standard Microsystems Corp.
USB Bus 001 Device 001: ID 1d6b:0002   Linux Foundation 2.0 root hub
USB Bus 001 Device 003: ID 0424:ec00   Standard Microsystems Corp.
USB Bus 001 Device 004: ID 0bda:2838   Realtek Semiconductor Corp. RTL2838 DVB-T
USB Bus 001 Device 005: ID 148f:5370   Ralink Technology, Corp. RT5370 Wireless Adapter

Quote
This is a NAV tool option to display traffic at certain height separation
Is this in PAW config, or are you refering to the Nav App running on the tablet.
I havent got as far as linking to RunwayHD yet as I want to see it logging ADSB and putting out NMEA sentences before trekking up the aircraft.

ianfallon

Re: No ADSB traffic reported on Logging
« Reply #9 on: December 02, 2015, 05:42:30 pm »
No GPS signal at all.

It needs to be outdoors to work, especially the first time the GPS boots up (if using a USB one).

If you don't have a USB GPS you need the PilotAware / CollisionAware app running to feed GPS to PilotAware from your tablet/phone.

flying_john

Re: No ADSB traffic reported on Logging
« Reply #10 on: December 02, 2015, 08:17:38 pm »
Thanks Ian - I didnt appreciate you had to have the GPS input to receive the ADSB. I was expecting the ADSB reception to work without GPS connected.

John

Admin

Re: No ADSB traffic reported on Logging
« Reply #11 on: December 02, 2015, 09:26:36 pm »
Thanks Ian - I didnt appreciate you had to have the GPS input to receive the ADSB. I was expecting the ADSB reception to work without GPS connected.
John

The traffic info is position-relative, so you must know your own position

Thx
Lee

flying_john

Re: No ADSB traffic reported on Logging
« Reply #12 on: December 02, 2015, 11:13:17 pm »
O.k - think its working now. Using my android phone as GPS source and Pilotawareandroid  and with XC-Soar loaded (it seems its a freebie) it starts logging aircraft and displaying them on the  XC-soar chart.


Next step - up to the airfield and get it running with RunwayHD.

I am not sure whether this has been asked before, but if I connect the Pi to my home router via rj45, I assume I can connect up to it using 192.168.0.100 could I then run a mapping app on a pc and use it a bit like FlightRadar24 but for local aircraft.

It would be a nice step for an A/G or Fiso tower to be able to see ADSB and Pi3 traffic.

John

Richard

Re: No ADSB traffic reported on Logging
« Reply #13 on: December 03, 2015, 06:22:49 am »
Hi john
   Yes you can run it on a pc. The is a thred on this forum on how to do it. I can not just find it at the moment I will look for it for you later today
Richard.
Europa XS

Admin

Re: No ADSB traffic reported on Logging
« Reply #14 on: December 03, 2015, 11:27:24 am »
Hi John

Quote
O.k - think its working now. Using my android phone as GPS source and Pilotawareandroid  and with XC-Soar loaded (it seems its a freebie) it starts logging aircraft and displaying them on the  XC-soar chart.

I have to say users have reported issues with this application freezing up when supplying the GPS data.
My advice is to use a USB/GPS dongle from the Hardware list on this site (ublox 7)

Thx
Lee