PilotAware
British Forum => Technical Support => Topic started by: comanchebob on June 26, 2022, 03:19:28 pm
-
My Aircrew instrument is powered from my Rosetta.
I tried repeatedly to update its Firmware using an Android tablet (the IOS version simply does not work), but achieved the message 'Update Failed' every time, and was left with a non working instrument and unable able to do a factory reset.
I finally solved the problem by switching off Rosetta powering the Aircrew independently, and running the upgrade routine.
All working perfectly now.
I hope this information is helpful to any 'Aircrew' users.
-
I did the same and it worked for me also. I used my ipad(iOS) and a battery pack. Haven’t noticed any difference since the update only an extra page showing a G meter. Has anyone noticed any further changes?
-
Hi Guys,
Bob,
I would certainly recommend powering Aircrew from a separate source during updates, rather than from PilotAware - simply to avoid any possibility of any 'glitch' corrupting the update - as you experienced. I have had that happen before, and it can be a real PITA trying to recover the unit if it 'seizes up' during the update process.
For the benefit of anyone else reading this thread, I hadn't updated my Aircrew for a while so (even though it was already running a 1.09 Beta Tester), I just ran a full update (remote from the aircraft and powered with the cable which normally feeds my printer from my laptop as I couldn't find my 'spare' USB A to USB B) to confirm the process. The update was deliberately performed using my 'older' iPad Mini 3 (running iPadOS 12.5.5) and all worked as expected - except that I had forgotten that in order to connect the iPad to the Aircrew, you have to first download the update (by opening the Aircrew Updater App on your Tablet, Phone or PC) while connected to the internet), then scroll through the Aircrew / Config settings to 'Update' and Press the Button to select 'Update', which starts the process and importantly activates the Aircrew WiFi Hotspot, so it appears on the tablet/phone/PC WiFi List allowing you to connect the Pad to the Aircrew Device and start the installation process.
Dave / All,
You will presumably be aware that James had to cease production of Aircrew a while back during Covid, as he simply couldn't obtain the required chipsets due to the World shortages. He has spent considerable time and effort redesigning the board, so that an alternative chipset can be used and my most recent news was that new units should be available to order in July.
In the meantime, communication has been a bit 'sketchy' so I need to speak to James again and get an update on his latest developments!
In particular, I must have missed the G-meter Screen. Looks interesting - though not sure my Inspector (/CFI) would be keen on me 'exploring the limits' in my flexwing.
That said, Aircrew is still one of the most useful devices in my aircraft.
Best Regards
Peter
-
Thanks for your replies.
I tried with my iPhone, iPad and Mac PC to log on to the update site but each time it returned the message 'This app is currently not available in your country or region'.
My Aircrew instrument was recently purchased and came with 1.08 firmware.
It would be helpful if these problems that may be experience could be mentioned on the Aircrew update site.
Thanks again for your feedback.
-
Dear Peter, I’m only assuming the extra page on the Aircrew instrument is a Gmeter.. I’m open to any other suggestions as I haven’t tried it in my PA28.!!. Does anyone know of any other changes since the update .
-
The latest firmware update give an option to show or hide the G meter screen. I tried 'show' but no joy !
Another feature is the improved magnetic calibration screen but no details of what to do to do a compass swing. I presume taxi in a circle or perhaps a figure of 8.
There is an absence of information in the Aircrew manual and no response from Aircrew if contacted by email.
-
Hi Folks,
As promised, I spoke to James last week. He apologised for not keeping in touch, but has been up to his eyes building Aircrew units and trying to complete and test part-finished software development projects before the official resumption of Aircrew Sales - which is why he has been effectively unreachable. He did say that he is hoping to resume normal sales and service later this month, while still continuing with project development and with a view to (potentially) expanding his product range.
With regard to the 'G-Meter' screen, this was apparently part of a development requested by an individual aerobatics pilot, and is still in 'Beta' development mode, which is why it hasn't been 'officially announced', or made its way into the Aircrew Manual yet.
Best Regards
Peter
-
It would be nice if Aircrew had its own online forum. Perhaps worth suggesting to James !
-
It would be nice if Aircrew had its own online forum. Perhaps worth suggesting to James !
If some one is ultra busy, this suggestion may not help them...
Setting up a forum is a lot of work and as someone who helps administer one, unless you have a lot of users and a need for lots or different areas, it's not worth it. Much easier to have a Google Group, or set up something on groups.io if you need to host documents and other stuff to be read or downloaded.
The biggest problem with forums is scammers and forum spam. Attacks from hackers trying to get the forum databases (user names/passwords) is another problem. Hosting needs, forum software, database and php updates...
For low traffic and low maintenance, groups.io or Google Groups.
Get users to learn to filter mail into mailboxes away from their In Box, otherwise older users who aren't familiar with email freak out if they get more than 10 emails a day. Google Mail and Thunderbird will also thread emails with a mailbox...
-
Hi Bob,
Thanks for the comments. I know James does monitor the PilotAware Forums when he has time because he often phones me about things posted on here, but while reading posts is fairly quick, I can vouch for the fact that (especially when you are up against it), answering them (as Steve has said) can add a whole other level of pressure and time commitment!
I'm sure James has considered the 'options', in the meantime, I've been an Aircrew Tester and User since pretty much the first prototypes, so I'm happy to answer Aircrew queries on here to the best of my ability as long as I've not just made another rod for my own back :-\.
Best Regards All
Peter
-
Hi All, A couple of us at my home airfield have had a magenta line appear on the aircrew instrument since we’ve updated the latest software version. It only appears when we zoom out to above about 10 miles. It appears from the side of the screen and bears no resemblance to our heading/track. Just wondering if any one else has experienced this. It doesn’t really worry us since we usually have the scale set to 6/8 miles.
Thanks for your comments
Davd
-
Hi Dave,
Thanks for letting us know. Sounds like some development testing that James is working on might have sneaked into the update by mistake. I will pass this on.
Best Regards
Peter
-
Hi Peter, Thanks for your reply. It’s not a major problem but you wouldn’t notice it unless you zoomed out. It’s not just mine but also my friends system also.
Regards Davd
-
Hi Dave,
I was surprised, as I was using my aircrew at the weekend and didn't notice this, but I have passed your observations on to James.
Best Regards
Peter
-
Hi Bob,
Thanks for the comments. I know James does monitor the PilotAware Forums when he has time because he often phones me about things posted on here, but while reading posts is fairly quick, I can vouch for the fact that (especially when you are up against it), answering them (as Steve has said) can add a whole other level of pressure and time commitment!
I'm sure James has considered the 'options', in the meantime, I've been an Aircrew Tester and User since pretty much the first prototypes, so I'm happy to answer Aircrew queries on here to the best of my ability as long as I've not just made another rod for my own back :-\.
Best Regards All
Peter
Thank you Peter - may I ask you just one question ?
My Aircrew is connected to Pilot Aware by a USB cable and displays only ADSB traffic with their Hex Codes.
I have also clicked to connect it to Pilot Awares' WiFi but I have a doubt that it is actually connected.
All traffic is displayed on my Sky Demon. Is there a way of displaying all traffic on the Aircrew Instrument ?
Best regards, Bob.
-
Hi Bob,
The problem is that the USB connection option uses the FLARM protocol from PAW, which only sends the Hex ID to Aircrew. If you want to see aircraft registrations, you need to use the WiFi data option - see page 17 of the Aircrew Manual here... https://aircrew.co.uk/downloads/Manual.pdf
Ideally, you should power your Aircrew from a separate USB (or 12 volt) supply* (which also reduces the power load on your PAW and frees up a slot for iGRID). Your WiFi connection to PAW is then easy to set up following the steps in the manual, and will supply the Reg IDs for aircraft. If you enable Bearingless targets (Mode-C/S - or Mode-C/S + Filter if you run a transponder) in PilotAware, Aircrew will also display banner alerts warning you of the presence of those aircraft. I also advise enabling Mode-S 3D in PilotAware if you have not already done so, as this will show Mode-S as actual moving aircraft on your Aircrew, in the same way as ADSB.
Hope this helps.
Best Regards
Peter
* 12 volt power cables for Aircrew are normally available from the Aircrew site, but can also be sourced elsewhere using the plug dimensions given in the Aircrew Manual - just make sure you connect to a switched supply (or your battery will go flat) and make sure you add an inline fuse into the supply cable.
-
Thanks Peter for the valuable information. I thought tat may be the case but I am reluctant to power the aircrew from another USB as I thought the cable direct to Pilot Aware was the preferred way.
I thought also that the power drain from Pilot Aware may be a problem but at 2 watts it is clearly not.
Best regards, Bob.
-
Hi Bob,
2 watts shouldn’t be a problem at present, but could potentially become an issue if we keep adding extra things like the WiFi dongle for iGRID. I have always powered my Aircrew since Day 1 of testing the prototype, via USB from my Charge 4, but have now run out of USB slots ??? so will be swapping it over to a switched and fused 12volt feed when I can find the time.
Dave,
I got word back from James re the magenta lion - as I suspected it’s a spin off from something James was toying with and shouldn’t be in the Public Release update. It won’t cause any issues though.
Best Regards
Peter
-
Remember the Raspberry Pi's are physically limited to the power that can be provided to the USB ports..
This table is taken from https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#typical-power-requirements
I can't remember which is the Pi of choice for PAW.
-
Hi Peter, Thanks for your reply to the magenta line. Much appreciated.
Dave
-
Hi All,
Thanks Jeremy. Pi of choice is Model 2B for the Classic and Model 3B for Rosetta.
Best Regards
Peter
-
Hi All,
Thanks Jeremy. Pi of choice is Model 2B for the Classic and Model 3B for Rosetta.
Best Regards
Peter
OK, so the total available to all 4 USB ports combined is physically limited to 1200ma - or there will be issues.
-
OK, so the total available to all 4 USB ports combined is physically limited to 1200ma - or there will be issues.
Is it possible to work out the total draw when all 4 USB ports are in use? In my case:
1. GPS Mouse
2. WiFi Dongle
3. USB to RS232 Serial Adapter - GPS to Trig for ADSB out
4. SDR
-
OK, so the total available to all 4 USB ports combined is physically limited to 1200ma - or there will be issues.
Is it possible to work out the total draw when all 4 USB ports are in use? In my case:
1. GPS Mouse
2. WiFi Dongle
3. USB to RS232 Serial Adapter - GPS to Trig for ADSB out
4. SDR
GPS probably 50ma max
WiFi maybe 200ma max
USB-RS232 I'd be surprised if more than 20ma, but call it 50ma max.
SDR is the biggest, could be up to 300ma depending on model, so lets say 400ma max
So this gives, 700ma max from the USB ports. But if any of these goes a bit iffy, then all will suffer as a result.
How do you tell if something has gone a bit iffy, normally they quickly get very hot after power on.
I haven't measured a Rosetta boot and running power, but the older classic was running at a peak of ~1300ma. The consumption of a PAW system isn't steady state by any means, it's very bursty and totally different to charging a battery. I can't find the dataset just a low quality screen grab of around a couple of seconds of current consumption from back in the dark ages (2016). The PAW does more work than it did back then, maybe I need to dig out my Classic or build a Rosetta and take some up to data measurements....
-
How do you tell if something has gone a bit iffy, normally they quickly get very hot after power on.
That is the bit that worries me. It does get hot quickly but I'm told that the SDR card does generate a lot of heat.
-
How do you tell if something has gone a bit iffy, normally they quickly get very hot after power on.
That is the bit that worries me. It does get hot quickly but I'm told that the SDR card does generate a lot of heat.
I have an SDR on the bench here, been running flat out for a week. Checking it with a FLIR camera, it's holding at 40℃, I can hold it OK - it's warm, but not uncomfortable. When things are too hot to touch, then I'd say there is a problem.
SDR's are very inefficient, hence they generate a lot of heat. A WiFi dongle or GPS in comparison should not really get warm at all. A USB to serial adapter should never be above ambient.
-
SDR’s get hot, they are rated to 85degC, we gave pushed them and the PI (by increasing ambient temperature and workload) to over 100 degC without issue
Jeremy, are you running the SDR under workload, or just plugged int USB ?
Just plugging in will not necessarily generate heat
Thx
Lee
-
SDR’s get hot, they are rated to 85degC, we gave pushed them and the PI (by increasing ambient temperature and workload) to over 100 degC without issue
Jeremy, are you running the SDR under workload, or just plugged int USB ?
Just plugging in will not necessarily generate heat
Thx
Lee
Oh, it’s working hard… as the Pi 4 it’s connected too.
-
I now power my "Aircrew" using the 12 volt supply (not from Pilot Aware). What a transformation !
This is a much better and now reliable option option. It now connects to Pilot Aware by wifi, giving more traffic (including registration numbers) on the traffic display.
Also, no losses of signal due to voltage errors etc. I really think that Pilot Aware is not capable of supplying reliable external output power.
-
Hi Bob,
Thanks for the update. Good to know you have now got things running properly by powering your Aircrew from your aircraft 12 volt supply (suitably switched and fused I trust).
The Raspberry Pi's used in PAW (Classic or Rosetta) are both generally fine with their designed power draws (including USB to RS232 converters and the 'extra' WiFi for iGRID, as these have all been tested in development. As we have discussed before, adding any additional loads can be asking for trouble (especially if anything goes wrong - such as an SDR or GPS developing a fault).
Remember that when James compiled the Aircrew Manual, he would have been working with a 'bare' PAW without USB to RS232 or iGRID, so it would be perfectly capable 'power wise' of supporting the Aircrew in that state. In a similar vein, that's why we always recommend powering PAW from its own dedicated supply - i.e. not 'sharing' a 2-port USB adaptor - especially with a power-hungry 'flat' tablet or phone. As you are of course now aware, connecting the Aircrew to the PAW by USB (rather than WiFi) also prevents display of aircraft Reg ID as I reported previously, so swapping it to an external supply with WiFi connection to your PAW automatically resolves that issue.
Good result!
Best Regards
Peter