76
Show Posts
You can view here all posts made by this member. Note that you can only see posts made in areas to which you currently have access.
77
General Discussion / Re: EasyVFR
« on: November 15, 2015, 09:14:27 am »Whoop,Whoop, I've got little green planes buzzing me on EVFR!
Roweda talked me through connecting PAW to EV by phone, on Thursday evening. Comparing logging messages with his unit, I appeared to have a software corruption on my PAW because the boot-up sequence was stopping prematurely.
Downloaded software once again and installed in PAW. Also took the precaution of using a higher current power bank to eliminate low voltage problems during initial boot-up.
In the meantime Dave had sent a PAW unit to Rob Weijers at the Pocket FMS Foundation for testing with iOS devices. Rob discovered a potential problem with PAW having no DNS address in the Pilotaware hotspot IP DHCP settings. Apparently Flarm does have DNS and the "FLARM" interface in EV requires this. It had been omitted by Lee in response to a request for cellular iPads to be able to retain cellular connectivity for downloading weather, notams etc while connected to EVFR and PAW.
I did an initial boot of my PAW earlier today and suffered the same lack of connectivity between my iPad and PAW that I was getting previously. I decided to try the work-around that Rob suggests in the PFMS forum EasyVFR thread, "Known issue with EasyVFR and Pilotaware on Apple devices without cellular datalink". Once I applied the work-around to the PAW hotspot settings in "iPad settings", all of the interface problems disappeared. This workaround should NOT have been necessary with a "working" cellular model, but I am on Pay as You Go, and don't have a current data allowance, so it seems I have to apply it also in these circumstances.
I'd like to thank both Dave and Rob for their first class support with this issue.
Can you post a link here to the magic needed to get Wifi iPads to work ? Or post the info itself ? I have a friend with this problem.
78
General Discussion / Re: Quick Summary Of Pinouts And Connections
« on: November 14, 2015, 06:12:36 pm »
Hi,
I used the Slice of Pod so I just connected more wires from it to the Baro chip.
I am not sure about this but after moving the Baro to the other side of the SOP board from the ARF it worked more reliably. Whether this was heat, RF or something else I am not sure.
I used the Slice of Pod so I just connected more wires from it to the Baro chip.
I am not sure about this but after moving the Baro to the other side of the SOP board from the ARF it worked more reliably. Whether this was heat, RF or something else I am not sure.
79
General Discussion / Re: Windows 10 & SD Formatter
« on: November 11, 2015, 08:32:53 pm »
Very strange - sadly (or fortunately) I don't have Windows 10 to try here.
There might be other drive partitioning software you can try.
There might be other drive partitioning software you can try.
80
General Discussion / Re: Windows 10 & SD Formatter
« on: November 11, 2015, 07:54:11 pm »
Did you definitely format with "FULL (Overwrite)" not FULL (Erase) or other options and with the resize option ON ?
It's critical to use those settings. If the formatted ran OK I'd be surprised if it was a Win 10 issue.
Also can you define "crash" ? If you have a monitor connected to the HDMI what do you see ?
It's critical to use those settings. If the formatted ran OK I'd be surprised if it was a Win 10 issue.
Also can you define "crash" ? If you have a monitor connected to the HDMI what do you see ?
81
General Discussion / Re: NMEA out to transponder.
« on: November 11, 2015, 05:47:24 pm »Well until you get a copy of that, why not turn on the ADSB logging, it will be pretty noisy
but you just need to look for your ICAO code coming through as an ADSB message.
Doh! Yes, that is the other thing I did - forgot to mention that. Good point!
82
General Discussion / Re: NMEA out to transponder.
« on: November 11, 2015, 05:44:55 pm »
Set the a/c PAW to another hex code, not the correct one for the a/c.
Assuming you have the transponder set up with the correct hex code and registration you'll see your reg on the 2nd unit or worst case the real a/c hex code from the transponder. If you see the temporary "wrong" hex code - that is over the P3i interface (ARF).
Really it's much simpler to run FlightRadar24 and see yourself on there with it NOT showing as "T-MLAT" (the vanilla Mode S system) instead showing something like "F-EGTK2"
Assuming you have the transponder set up with the correct hex code and registration you'll see your reg on the 2nd unit or worst case the real a/c hex code from the transponder. If you see the temporary "wrong" hex code - that is over the P3i interface (ARF).
Really it's much simpler to run FlightRadar24 and see yourself on there with it NOT showing as "T-MLAT" (the vanilla Mode S system) instead showing something like "F-EGTK2"
83
General Discussion / Re: Version PilotAware Release 20151107
« on: November 11, 2015, 02:44:02 pm »Hi Lee
I followed your instructions and of course worked flawlessly
As mentioned previously that is the first time I have had to select the
FORMAT TYPE: FULL (Overwrite)
in previous formats I have only selected
FORMAT TYPE: FULL (Quick) and had no problems.......
I live and learn !!
Just for information the new instructions in the software information guide on the top page specify
FORMAT TYPE: FULL (Erase)
Not sure what the fundamental differences are
Hi - this is interesting. I only see FULL (Erase) and FULL (Overwrite).
I think the guide is wrong and it should be FULL (Overwrite) - will correct it in v0.4
84
General Discussion / Re: XC Soar free Android software and PilotAware
« on: November 11, 2015, 01:48:59 pm »
Made some XC Soar screenshots so I just need to integrate them with Paul's info into the guide.
Coming in v0.4 of the guide!
Coming in v0.4 of the guide!
85
General Discussion / Re: EasyVFR
« on: November 11, 2015, 01:47:52 pm »
Easy VFR screenshots are now in the latest version of the guide which is now on the forum for download.
86
General Discussion / Re: XC Soar free Android software and PilotAware
« on: November 11, 2015, 08:37:11 am »
I need to add it all to the Software Installation guide too
87
General Discussion / Re: PilotAware Map
« on: November 10, 2015, 09:12:42 pm »
The exact position doesn't matter btw - it's just to show roughly where people are so people close to each other can get together if they want to 
88
General Discussion / Quick Summary Of Pinouts And Connections
« on: November 10, 2015, 08:46:09 pm »
NOTE! ARF and Baro chips are now obsolete and replaced with the new plug in board coming Spring 2016!!
Please someone double check this for me, but here's a quick summary of pin-outs and connections in one place:
ARF
With the ARF face up (chips up) with the antenna connection at the top, pin 1 is the topmost pin on the left edge. Pin 2 is below that etc. with pin 10 the bottom-most on the same (left) edge.
PIN 1 3.3v IN - connect to any 3.3v output from Slice of POD / POD or Adafruit Baro chip VOUT, or Digole board 3.3v output.
PIN 2 TX - connect to GPIO pin 10 RX
PIN 3 RX - connect to GPIO pin 8 TX
PIN 10 GND - any GND on POD or GPIO (pins 6,9,14,20,25)
ADAFRUIT BARO
Vin 5v Connect to any 5v output from Slice of POD board or GPIO pin 2
GND Connect to any GND from GPIO (pins 6,9,14,20,25) or Slice of POD board etc
SDA Connect to SDA on GPIO pin 3
SCL Connect to SCL on GPIO pin 5
HOBBYTRONICS BARO
Vin 3v Connect to any 3.3v from Slice of POD or POD or Adafruit Baro chip or Digole board
GND Connect to any GND from GPIO (pins 6,9,14,20,25) or Slice of POD board etc
SDA Connect to SDA on GPIO pin 3
SCL Connect to SCL on GPIO pin 5
Notes
- GPIO 3.3v supply (pin 1) is NOT sufficiently powerful to use, hence the use of the POD or Digole boards.
- Take extra care with the GPIO pin numbering. It is not like regular IC numbering (down once side and up the other), instead even numbers are on one side, odd on the other.
Please someone double check this for me, but here's a quick summary of pin-outs and connections in one place:
ARF
With the ARF face up (chips up) with the antenna connection at the top, pin 1 is the topmost pin on the left edge. Pin 2 is below that etc. with pin 10 the bottom-most on the same (left) edge.
PIN 1 3.3v IN - connect to any 3.3v output from Slice of POD / POD or Adafruit Baro chip VOUT, or Digole board 3.3v output.
PIN 2 TX - connect to GPIO pin 10 RX
PIN 3 RX - connect to GPIO pin 8 TX
PIN 10 GND - any GND on POD or GPIO (pins 6,9,14,20,25)
ADAFRUIT BARO
Vin 5v Connect to any 5v output from Slice of POD board or GPIO pin 2
GND Connect to any GND from GPIO (pins 6,9,14,20,25) or Slice of POD board etc
SDA Connect to SDA on GPIO pin 3
SCL Connect to SCL on GPIO pin 5
HOBBYTRONICS BARO
Vin 3v Connect to any 3.3v from Slice of POD or POD or Adafruit Baro chip or Digole board
GND Connect to any GND from GPIO (pins 6,9,14,20,25) or Slice of POD board etc
SDA Connect to SDA on GPIO pin 3
SCL Connect to SCL on GPIO pin 5
Notes
- GPIO 3.3v supply (pin 1) is NOT sufficiently powerful to use, hence the use of the POD or Digole boards.
- Take extra care with the GPIO pin numbering. It is not like regular IC numbering (down once side and up the other), instead even numbers are on one side, odd on the other.
89
General Discussion / Re: EasyVFR
« on: November 10, 2015, 08:05:46 pm »
I have the Asus Memopad 173X and have not seen this. Latest Skydemon. Android 4.2.2
90
General Discussion / Re: EasyVFR
« on: November 10, 2015, 03:20:02 pm »
Thanks - please post info re. documentation changes to me directly or via the Documentation thread. Best to email screenshots directly (email on that thread).