PilotAware
British Forum => General Discussion => Topic started by: flying_john on December 15, 2015, 02:58:29 pm
-
I upgraded this morning to 20151205, but when I plugged in the SD and started a browser session the log just said that the licence key was invalid.
Aha, I thought, you must have to get a fresh licence key when you load a new version.
So I applied for a licence key, but its the same as the previous one.
What have I done wrong ?
John
-
Hi John
You have done everything correct, you just need to re-enter the key.
When the disk is reformatted all data is lost.
At the moment we have no implemented a neater upgrade feature, it is basically discard the old installation and install from fresh.
So this means you need to re-enter
1. License Code
2. Hex Code (ICAO)
Please re-post if you are still having trouble.
Thx
Lee
-
Hello Lee
I am having the same issue after loading latest version.
The licence key and hex code have been re-entered, but it still shows licence expired.
Key and code are still showing after a reboot.
regards
Steve
-
If you requested a key based upon the WiFi Dongle, this may cause an issue.
Please request another key based upon your WiFi Hotspot, let me know if this solves the issue.
Thx
Lee
-
Lee, I thought the license was linked to the LAN MAC addresss?
-
It was initially. I think it was changed to allow or ensure the WiFi Mac Address was not the predominant identifier.
That would make licensing aligned with Device. I could be be totally wrong......
-
Hi all
The license is (now) linked to the LAN MAC Address.
The reported WiFi hotspot name, uses the LAN MAC Address
Previously the WiFi hotspot name used the WiFi MAC Address
Sorry for any confusion this may have caused
In summary, if you have a license failure - request a license using the WiFi reported name.
This should not fail under normal circumstances
Thx
Lee
-
If this is the case can you please update the Software Installation Document as it is saying use the WiFi MAC address.
-
If this is the case can you please update the Software Installation Document as it is saying use the WiFi MAC address.
I have taken a look at the document, the only reference I can find is on page 9 where it says
(Licences are now based on the Raspberry Pi’s Ethernet MAC address rather than the Wi-Fi dongle’s MAC address)
Can you point me to where it says
use the WiFi MAC address.
Maybe you are looking at an old document pre version 0.6 ?
Thx
Lee
-
Lee,
Page 18, Section 8. Vers 0.6
It may be correct but the number displayed on Page 18 suggests it is the WiFi address and not the LAN address.
Page 19 states (Licences are now based on the Raspberry Pi’s Ethernet MAC address rather than the Wi-Fi dongle’s MAC address)
May be a bit confusing for the uninitiated.
-
Please post corrections / suggestions to the Documentation thread so I have one place to track these and pick them up for the next version of the guide - thanks!
-
Is this issue still open ?
I have not seen any further responses
Thx
Lee
-
Mines working now, thankyou.
-
There is a strange messages in the start up process towards the end on the 19th Dec build.
Mounting File System READWRITE
Mounting File System READONLY
TRX-SER: ERROR!!! comms buf=' '
Connection works as before to SkyDemon and the ARF is transmitting on 868.3MHz so not quite sure to what this error message refers. Is it relevant?
Also pleased to see that this build also works on PI2 (despite including a ARM/ARM7 warning message in the log). Haven't yet tried the ARF in the Pi2.
Someone earlier reported that the USB GPS Global Sat BU-353S4 worked with PAW. It hasn't worked in the previous build or this Dec one. The device shows up as a 'Prolific' device.
Good new configuration menu. I did note that the TX counter on the Pi2 was increasing despite not actually having the ARF unit fitted.
I have a slightly dodgy USB connection on the RTL unit so it disconnects sometime and consequently the ADS-B detection stops and no further planes are identified. If reconnection is made the RTL unit does not appear to reinitialise and no further planes are detected. Is it meant to restart on reinsertion?
-
There is a strange messages in the start up process towards the end on the 19th Dec build.
Mounting File System READWRITE
Mounting File System READONLY
TRX-SER: ERROR!!! comms buf=' '
Probably looks onerous, but actually nothing to worry about, I think I may remove some of these errors, they are more for my debug purposes than anything.
This is simply saying communication failed with the new RF Module - which of course it will, because you do not have one yet ;-)
Also pleased to see that this build also works on PI2 (despite including a ARM/ARM7 warning message in the log). Haven't yet tried the ARF in the Pi2.
Thats good, the Pi2 does seem to be working OK for me too, but the recommendation is still PiB+
Someone earlier reported that the USB GPS Global Sat BU-353S4 worked with PAW. It hasn't worked in the previous build or this Dec one. The device shows up as a 'Prolific' device.
Cannot comment on this, I do not have access to one of these I'm afraid.
U-Blox Dongle, and U-Blox G-Mouse have been proven to work well.
Good new configuration menu. I did note that the TX counter on the Pi2 was increasing despite not actually having the ARF unit fitted.
I need to investigate this at some point, somebody else reported this also - I am surprised having looked through the code, will try to investigate.
I have a slightly dodgy USB connection on the RTL unit so it disconnects sometime and consequently the ADS-B detection stops and no further planes are identified. If reconnection is made the RTL unit does not appear to reinitialise and no further planes are detected. Is it meant to restart on reinsertion?
This is a little more trick to handle to be honest.
There may be a method to improve the handling of this issue, but for now, all I can say is 'do not remove the dongle, or you need a reboot'
Many thanks for the feedback - keep it coming ....
Thx
Lee
-
Does the new software still support the old ARF for the moment?
My Pi B counts up ARF Tx packets but doesn't have an ARF installed.
-
Does the new software still support the old ARF for the moment?
My Pi B counts up ARF Tx packets but doesn't have an ARF installed.
PilotAware should still work with either shield, it attempts to connect and negotiate to decide which one is fitted
Thx
Lee
-
Hi John
You have done everything correct, you just need to re-enter the key.
When the disk is reformatted all data is lost.
At the moment we have no implemented a neater upgrade feature, it is basically discard the old installation and install from fresh.
So this means you need to re-enter
1. License Code
2. Hex Code (ICAO)
Please re-post if you are still having trouble.
Thx
Lee
I updated to 20151219 this afternoon , and despite following the above advice, it still reports "license expired"
John ( not the poster to whom you were replying)
-
Hi Exatco
Can you please post images of
1. The webserver home page
2. The webserver configure page
Thx
Lee
-
Thanks Lee, I'll try to post them tomorrow.
John
-
Lee here are the screenshots:
Edit. having trouble getting them into message :(
John
-
Hopefully the config screen
-
Hi Exatco,
I see the error.
In the license field of the Configure page you have entered your MAC Address,
not the license code you received in an email from the license system
Thx
Lee
-
Thank you Lee, that's resolved it :)
John
-
Hi Lee,
I just loaded the latest update to the software onto my machine and found that after some considerable time loading, I now have a completely different Wi-Fi Pilotaware address!
My original - that works fine was 000F600632CC but with the new software my Ipad is showing a PilotAware - B827EBBDA90 code and although the Ipad will connect, CollisionAware will not - it shows "connecting" for about 5 minutes and then slips back to "disconnected" - having never connected in the first place.
Any idea what is going on here?
I have 2 sim cards and have put the old one back in and it all works perfectly again. Sorry but I don't know what version software I have on my operating card, but I haven't updated for some time now.
Regards Alan Powell 27/12/2015
-
That's your Ethernet MAC address which PilotAware uses now instead of the Wifi MAC address.
It doesn't make any difference to the operation though.
Have you re-entered the licence information on the config page ?
(by going to address 192.168.1.1 on your iPad browser when connected to the PAW Wifi, then tap "Configure").
Enter the licence then tap "Save". Your old licence will still work with the new address.
-
Hi Alan
Please request a new license code using the reported hotspot address, that should resolve the issue
Thx
Lee
-
OK - thanks I'll try that.
Regards Alan
-
I tried Ian's suggestion of re-entering my licence details in the 192.168 config page and that has now allowed me to connect.
I like the registration marks being shown - cool !
Regards & thanks Alan
-
A further update - I did obtain another software key as I had the satellites "dropping out" after I had entered my old key.
The new licence key works a treat - why don't I do as I am told ? ? ?
Thanks again.
Alan
-
Hi
I have just made up the box and downloaded the software etc but have run into a bit of a roadblock. No doubt I have made a basic error as to be honest I don't really understand exactly what I'm at.
Pat
-
Pic 2
-
Hi postman
Did you procure items from the known good hardware list ?
The rtlsdr dongle looks like it is un-recognised
Thx
Lee
-
I suspect the licence bit hasn't been done properly. It's showing licence expired.
-
Hi Lee yes all the stuff was off the list supplied. Are you talking about the ADS-B Receiver dongle? The other one is at least talking to my tablet.
Mini USB DVB-T RTL-SDR Realtek RTL2832U & R820T Tuner Receiver MCX Input Laptop
Very quick reply BTW
Thanks pat
-
My MAC address was hopefully correct but I was wondering if 0's were O's
-
Hi
Your license request was wrong, not sure what made you use the number you did.
The correct number is under "hostid" on the web page
I would be interested in knowing why you chise the number you did, so we can put more info in the installation docs
Thx
Lee
-
The licence was got by using the link to the automated licence page. That may have been using the link available to non members ie before you log in ( if that makes sense). Sorry but I don't see anyway of inserting a hyperlink here.
Regards
Pat
-
I've just tried applying again using the link inside the members forum and it has given me the same licence.
-
Hi Pat,
Firstly, looks like the code you should use for the license request is B827EBCCF68D
More importantly we need to fix our processes ...
I am misunderstanding something here :-\
Looking at your request you have entered a request key for
6021C0C70FE8
I think what I am asking, is: where did you get this number from ?
The number which should be entered is based upon your HOTSPOT, ie in your case I am guessing
PilotAware-B827EBCCF68D
I can see from the page you posted earlier in this thread that your request number should be:-
B827EBCCF68D
In order that we can make sure our documentation is not misleading I would really like to know :-
1. Where you obtained the number 6021C0C70FE8 ?
2. What instructions led you to enter this number for the license request ?
If you have made this mistake, others will too, so we need to fix our documentation
Thx
Lee
-
Hi Lee
That number is my Wi-Fi MAC address for my Samsung tablet. Now I'm not too au fait with a lot of (ie any) computer stuff so had to google how to find my MAC address. If there is a difference between those 2 I for one was unaware of it.
Regards
Pat
ps is all I have to do now apply for a new licence under B827EBCCF68D ?
-
Lee
Thanks for all the help. I went ahead and got a new licence under the new number you suggested. My mistake was confusing which device was being referred to. I thought the MAC address being asked for was the one for my tablet and not the pilotaware box. I probably jumped in a little quickly and was looking at some of this stuff before registering on the site and was using links etc which are open to all. On closer inspection once a member the tutorials available are much more comprehensive and cover all relevant material for numpties like me. Maybe disabling or redirecting the stuff available before one logs on would help this not happening in the future.
I think I've managed to get my setup working as I've just observed a couple of airliners on Skydemon.
Thanks again
Pat
-
I think I've managed to get my setup working as I've just observed a couple of airliners on Skydemon.
Great news, well done
Thx
Lee