PilotAware
British Forum => OGN-R PilotAware => Topic started by: Andrzej on August 13, 2017, 08:23:55 pm
-
HI
I am just finish a PAW/OGn up link . Just find a problem .
Up link do not see a PAW device .
When open a http://192.168.0.51:8082/ i should to see a PAW with details .. nothink listed on table , but NG starts to counting up .. when switch down PAW ... counting stops ..
LED on board blinkink on green only when PAW is switch ON .
Flarm trafic Ok .
BR
Andrzej
-
Hi Andrzej
Pilotaware has a simple 8 bit checksum in order to validate packets.
We found multiple bit errors could still cause the checksum to pass.
In which case we have added heuristics based upon the base station location, for example
Received signals distance < 50km
Height < 20000ft
Etc
So one thing could be that your receiver would thinks it is further away than it really is ?
I would also recommend logging on and running
telnet localhost 50002
This will give some diagnostics
Thx
Lee
-
Hi Lee
hmm ... PAW and OGN up link i have in same room .. so distans is aprox 10 m ( due testing ) . I get my PAW and gone by car to end of connection nothing changing .. Lee please give some help in simply words . I am not a software specialist :)
PAW classic do not get any TX from OGN up link ( no trafic to transmit ? ) .. all RX in up link looks wrong ( TX from PAW ) .. My PAW was working well 100% fev weaks ago ( tested with other PAW ) .. all in setup green
BR
Andrzej
-
Hi Anrzej
Apologies, I did not mean physical distance, I meant reported distance
When installing the ground station, you provided coordinates and elevation, are these correct
?
Also, using telnet to interrogate the data, and posting here will help diagnose the issue
Thx
Lee
-
HI Lee
All i thing is Ok , Just look for picture .. Station appears in OGN range tool Yesterday i get one glider with flarm .
It is important ? : sudo:unable to resolve host ognpaw : ???
BR
Andrzej
-
I had the same sudo error, and the "measurements appear inconsistent" warning when setting up my OGN basestation yesterday. It seems to work though - although the "green pin" goes mauve a little too often for comfort. I believe Keith and Lee are looking into both errors.
-
I have also had the 'Measurements appear inconsistent' warning, but ignored it and my station is working fine. It might be something to do with the fact that the TCXO dongles we are (I presume) using for OGN-R have virtually no frequency drift and this is confusing the GSMscan software.
I have never seen the 'sudo: unable to resolve ognpaw' message.
Regards
Peter
-
Hi to All
Due intensive testing today with 4 PAW classic nothing change :( ... We was flying over Up link 20 minutes with 3 planes ,,,only negative readings ... Before testing i instal again software and calibrate .
sudo:unable to resolve host ognpaw exist again
200 NG readings 0 OK readings
http://192.168.0.51:8082/
BR
Andrzej
-
Andrzej and Peter.
I had the same message on my station, the problem is the default hosts file is incorrectly configured,
In a terminal window change to the etc_org directory and type
sudo nano hosts
On the last line change it from
127.0.1.1 raspberrypi
To
127.0.1.1 ognpaw
Then reboot (I cannot remember if this works straight away or if a reboot is needed) and then you shouldn't see this message again.
Ben.
<SNIP>
I have never seen the 'sudo: unable to resolve ognpaw' message.
Regards
Peter
-
Ok Ben
I do that , but it not resolve problem ... PAW is not read by up link :(
I use to save ctr O ...ist saved but after reboot it comes to default rasbberypi
link to my uplink
http://ognrange.onglide.com/?#PWPRZESOC,max,today,53.5187_14.5668,11,#00990000:#009900ff,circles;
BR
Andrzej
-
Andrzej,
One step I forgot to add,
sudo /root/mount_rw.bash
This enables you to write to the disk,
When you are finished then:
sudo /root/mount_ro.bash
Will write protect it again.
Also make sure you are editing the hosts file in /etc_ogn NOT the one in /etc as that is only held in ram-disk and is cleared on reboot!
Linux is a tricky thing at times and I am far from an expert, I usually have a book on Linux in one hand when I try to do anything.
Ben.
Also, this error shouldn't be causing you any uplink problems, it didn't stop my station from working, it was just a nuisance but nothing worse.
Ok Ben
I do that , but it not resolve problem ... PAW is not read by up link :(
I use to save ctr O ...ist saved but after reboot it comes to default rasbberypi
link to my uplink
http://ognrange.onglide.com/?#PWPRZESOC,max,today,53.5187_14.5668,11,#00990000:#009900ff,circles;
BR
Andrzej
-
Andrzej,
Just a thought. Are you running the latest PAW-OGN software v.0.2.6.arm? If not, this might explain why you aren't seeing gliders. This is not yet available via the 'public forum' and Lee is on holiday, so I will PM you the links. Needs a full reinstall, then auto configure via SSH as per the install instructions.
Regards
Peter
EDIT: Just read back through this thread again and noticed from the first attachment that you ARE running the latest script. Something is definitely wrong though, as you are showing no PAW P3i contacts at all on OGNRange and only the 1 glider contact - despite the fact that the other local stations are both showing lots of 'OGN', though mostly more than 30 days ago (check the 'When' Tab).
It might be worth trying a software re-install to see if this resolves the issue. Also partly a matter of waiting for gliders to come in range - most of them seem to be well to the south-west of you and your location looks hilly, so your antennas may be screened.
This doesn't, however, explain why your other PAWs aren't being reported! You could try running 'normal' PAW software in the unit temporarily to test that the RF Bridge is working properly (test against one of your other PAWs to see if they talk to each other). You would need to put in a 'temporary 28-day licence' from the pilotaware.lode.co.uk site to get the unit to transmit as a PAW and would need to 'borrow' the 'missing' GPS and WiFi dongles from another PAW. The OGN antenna and dongle will be fine for a test. Worth a try as it would eliminate any issues with the PAW side of things.
Peter
-
Andrzej,
Sorry, cross-posted - see my Edit above.
Peter
-
Hi Freinds
I get new board from Keith , change it , reinstall software , put new SD card ( formated ) .....and NOTHING :( ... My OGN link reads only NG packets from my PAW Classic who is 100% good . ..
last thing what can i do will get new one PI2 B 1v1
BR
Andrzej
-
Something is not right
Can you show the output of
telnet localhost 50002
When your PulotAware is in range
Thx
Le
-
part 1
-
part 2
-
part 3 when i switch off PAW classic
-
Hi Anrzej
Very strange
As you can see, your paw is being picked up, it is reported in the log
The problem is that the base station thinks it is 6100 km away, so is an error
I think what is happening is that your receiver is located at lat 0.0, lon 0.0
The position of the receiver should be determined after less than 10 mins,
I capture the outgoing message to the ogn, and use this info, I think
Something is going wrong at that point
I cannot investigate fully until Friday as I am away on vacation
Thx
Lee
-
Andrzej,
I take it you reconfigured your OGN software properly after re-installing it on your reformatted card?
You can check the configuration screen manually from the Pi login screen...
pi@ognpaw ~$ cd rtlsdr-ogn
sudo /root/mount_rw.bash
Then... sudo nano rtlsdr-ogn-paw.conf
Check and if necessary correct your Lat and Long settings manually. (a before and after screengrab will confirm your settings.)
'Ctrl O' then Enter to save the changes, then 'Ctrl X' to exit the .conf file
sudo /root/mount_ro.bash Enter to write protect the file
sudo reboot Enter to restart the unit.
Worth a try! Worst case scenario you need to start again with a new software install.
Regards
Peter
-
Peter
I was perform new instalation , new SD card w fev times with first bridge and new bridge - no change . I will try Yours way ...
But look for picture ...Like Lee sugestion very strange ,,, all looks good but is something what maybe i do wrong and cant see that .
I am waiting for new PI board
Other thinks i am thinking that maybe my ruter blocks some trafic to OGN ... "DDB 0" ...
BR
Andrzej
-
Hi Andrzej
I think its a software bug, it looks like the PAW receiver software cannot determine the location
Thx
Lee
-
Hi Andrzej
are you using any special characters in your station name ?
I notice that the name for your station (in Polish) could use the special 'e' character.
Please confirm the characters are standard 8bit ASCII names.
Could you also try a test of naming your station
PAWTEST
edit:
Actually now looking at the messages you reported, I think this could be the issue, looks like in the name you are using an extended ascii character, this would affect the message parsing.
Thx
Lee
-
Hi Lee
I am sure that i use name with standard ...PRZESOC i do not use ĆÇ ĘÄ etc !! I will check and change it fo your sugestion aprox 21.00 LT ..
BR Andrzej
-
Hi Andrzej
The issue is an APRS Parsing bug, I have reproduced your issue, I am looking at a fix
edit: Uploaded a Fix
Thx
Lee
-
Hi to All
Problem solved , THX a lot Lee for fast killing a bug ..
I downloaded a new software from server and my PAW Classic is visible by OGN system :)
So i will soon install a station on EPSD :) now name is PWTEST
http://ognrange.onglide.com/#PWPWTEST,max,all,53.549716_14.551694,10,#000000ff:#000000ff,circles;
Best Regards
Andrzej
Poland
-
Lee,
Is this bug in the PAW or the OGN-R software? Do we all need to replace our existing?
Regards
Peter
-
Lee,
Is this bug in the PAW or the OGN-R software? Do we all need to replace our existing?
Regards
Peter
:-[ only if you are East of the Greenwich Mean Line
It was a silly parsing error of Easterly co-ordinates for the Ground Station location
I will be putting up a new release today, which will report to Glidernet which version of Software is being run by the groundstation, this will help in diagnosing any problems, it will appear like this :-
14580 PWCoventr 80.6.96.170:33530 Yes 3m 3m OGN-R/PilotAware 20170826 0 0/0/0 929 71 4.3 / 0 0 0 g/ALL
I will also post details of an incremental update, which means you simply type a command - and all is done, no recalibration, full install etc
thx
Lee
-
Update Instructions Topic
http://forum.pilotaware.com/index.php/topic,1012.0.html
Thx
Lee
-
For what it's worth, I'm running pretty much the same setup as Andrzej, and it does work OK for me. My version does not run 0.2.6 though, it's 0.2.5?
Version 20170830 : Date 2017-09-09 12:44:48 : Station PWHLaken
P3I Packets OK=152778 NG=0
ICAO Type Dist(KM) Alt(FT) Uplink
4845C4 PAW 0.01 0 -
-
Hi Rob
I think you should upgrade
I dont think 0.2.5 can detect all flarm devices since the upgrade
Thx
Lee
-
Well, that's odd.. I got the latest image, re-installed from scratch, and now i'I'm in the same situation as Andrzej was before :'(
Version 20170908 : Date 2017-09-09 19:57:15 : Station
P3I Packets OK=0 NG=59
ICAO Type Dist(KM) Alt(FT) Uplink
My PAW no longer receives valid packets from the OGN system, and vice versa.
EDIT: Well, I spoke too soon! Now it's there again, after about 5 minutes things started working!
Version 20170908 : Date 2017-09-09 20:02:55 : Station PWHLaken
P3I Packets OK=182 NG=64
ICAO Type Dist(KM) Alt(FT) Uplink
4845C4 PAW 0.01 0 -
-
Yep takes 5 minutes to listen to the servers, this is absolutely normal
Thx
Lee