Jepp Mobile FD for iPad
Join Date: Sep 2003
Location: Australia
Age: 47
Posts: 728
Likes: 0
Received 0 Likes
on
0 Posts
Got the download today, with FD yes you can point the finger and add waypoints but its still basic compared to Oz runways as Jabba has said.
i still prefer Jepp plates though and i think this App in the longrun has some potential....at least they are working on it
i still prefer Jepp plates though and i think this App in the longrun has some potential....at least they are working on it
i still prefer Jepp plates though and i think this App in the longrun has some potential....at least they are working on it
Join Date: Jun 2011
Location: Australia
Posts: 42
Likes: 0
Received 0 Likes
on
0 Posts
Jeppesen have been pretty slow off the mark in terms of GA flight planning software in Australia for a long time. They seem to have no interest in selling any of their packages such as FliteStar etc, which I've found surprising because it appears to be a reasonable package.
Jeppesen in Australia have had their bread buttered for years with the old school chart service and extracting very large fees from organisations such as the RAAF for their JetPlan service.
Seems strange, noting they actually already have the software sitting there. As far as I'm aware you can't buy it anywhere except perhaps by looking up their corporate office in Canberra and calling them.
They installed a new General Manager a year or two ago, so perhaps he'll set a new direction.
Porting FliteStar over to an iPad format [which I'm sure they will soon enough due to the US market] would be quite interesting.
Jeppesen in Australia have had their bread buttered for years with the old school chart service and extracting very large fees from organisations such as the RAAF for their JetPlan service.
Seems strange, noting they actually already have the software sitting there. As far as I'm aware you can't buy it anywhere except perhaps by looking up their corporate office in Canberra and calling them.
They installed a new General Manager a year or two ago, so perhaps he'll set a new direction.
Porting FliteStar over to an iPad format [which I'm sure they will soon enough due to the US market] would be quite interesting.
Last edited by MilFlyer; 17th Mar 2012 at 07:06.
A major update for JeppFD from Jeppesen and I still can't put in a route from Adelaide to Melbourne via the TBD VOR. It defaults to the NDB and there is no way to specify the VOR. This is very basic functionality for a flight routing app and it doesn't do it.
May be it works if you don't put YMML in as the destination airfield. If you put YPAD as the departure field, and YMML as the destination then either drag or write in the route, it defaults to the NDB, even if you drag to the VOR, get the VOR details up, and tap the add to route button. Sounds like omitting the destination airfield until the route is entered might be a good work around, I'll try it.
Edit: Nope, it still goes to the NDB. I start at AD, tap the TBD VOR, the window pops up with the TBD VOR details, I tap "add to route" and it still draws the route to the NDB.
Edit: Nope, it still goes to the NDB. I start at AD, tap the TBD VOR, the window pops up with the TBD VOR details, I tap "add to route" and it still draws the route to the NDB.
Bottums Up
The email below was received in August last year from Jeppesen as a result of my enquiry, related to the App not accepting routes. I'm disappointed they haven't fixed it yet.
Good afternoon Claret,
*
Your service request has been escalated to my attention. I understand that you’ve been having some problems with various routes not being accepted in the Mobile FliteDeck application. It appears that most of the routes in your example include a VOR entry/exit point that shares the same ID as a nearby NDB (e.g. GV, CS, AS, AYE). This is causing the problem, because the application will sometimes default to the NDB if it is nearer to the direct route. However, since the NDB is not the entry/exit point to the airway, the route fails. This is a known issue that our Development group is aware of and are working to address in a future update to the application. I apologize for any inconvenience this may be causing.
*
Best Regards,
*
Aaron Rocky Smith
Tier 2 Technical Support Specialist - Nav
Technical Support Services
______________________________________
Jeppesen
A Boeing Company
[email protected]
55 Inverness Drive East | Englewood, CO 80112 USA
Jeppesen – Transforming the Way the World Moves
*
*
Your service request has been escalated to my attention. I understand that you’ve been having some problems with various routes not being accepted in the Mobile FliteDeck application. It appears that most of the routes in your example include a VOR entry/exit point that shares the same ID as a nearby NDB (e.g. GV, CS, AS, AYE). This is causing the problem, because the application will sometimes default to the NDB if it is nearer to the direct route. However, since the NDB is not the entry/exit point to the airway, the route fails. This is a known issue that our Development group is aware of and are working to address in a future update to the application. I apologize for any inconvenience this may be causing.
*
Best Regards,
*
Aaron Rocky Smith
Tier 2 Technical Support Specialist - Nav
Technical Support Services
______________________________________
Jeppesen
A Boeing Company
[email protected]
55 Inverness Drive East | Englewood, CO 80112 USA
Jeppesen – Transforming the Way the World Moves
*
Thanks Claret, you can force the VOR to be used by using a dummy route to start with that has the VOR closer than the NDB, it will then use the VOR. Once the VOR is in the route you can change the rest of the route to what it should be. This is pretty useless though, I'm surprised you can't just type "TBD" and get a popup window asking to select either the NDB or VOR. I suspect that the American designers forgot that NDBs are still in use in other parts of the world.
Interestingly enough, even when I do get TBD VOR in the route, it still won't accept the airway Y12 that starts at the TBD VOR. It seems there are two problems. You can also have routing problems from an RNAV waypoint.
Interestingly enough, even when I do get TBD VOR in the route, it still won't accept the airway Y12 that starts at the TBD VOR. It seems there are two problems. You can also have routing problems from an RNAV waypoint.
Join Date: May 2009
Location: Owen Stanley's "Real World"
Posts: 88
Likes: 0
Received 0 Likes
on
0 Posts
It appears that most of the routes in your example include a VOR entry/exit point that shares the same ID as a nearby NDB (e.g. GV, CS, AS, AYE). This is causing the problem, because the application will sometimes default to the NDB if it is nearer to the direct route. However, since the NDB is not the entry/exit point to the airway, the route fails.
I thought our FMS was using Jeppesen NavData.. wonder why there software would be different?
That is the Jeppesen convention. (NB for a NDB)
This is why GPS RNAV initial waypoints for a northern approach are named NA, NC & ND but not NB.
This is why GPS RNAV initial waypoints for a northern approach are named NA, NC & ND but not NB.
That is the Jeppesen convention. (NB for a NDB)
Real FMSs don't have the ND suffix; the pilots thereof are clever enough to work out what aid is what waypoint.The NB caused a bit of consternation at some places as there were two, for example, CUNNBs within a few nms of each other in the early days.
GPS for iPad
There are currently four GPS that will work with the iPad (that I know of).
The first i the Bad Elf which plugs straight int the iPad dock connctor and is about3cm square. It uses the iPads batery and unless one uses an extension lead it is hard to place in a good position on an airliner with heated windows.
The next three are all bluetooth but Apple specific Bluetooth Protocol.
The first is the GNS5780. I had one until I left it on the glareshile. It was pretty good at acquiring and had very good battery life but had a quirky swipe strip to turn off and on and thye had major problems with being unable to swipe it off. It requird only a bare touch to turn it on, the upshot of which was it was easy to inadvertantly turn on when one put it in ones bag and thus was usually flat when you wanted it. I do believe they have now solved this issue.
Dual XGPS-150. Generally good performance though can really take some time to acquire position. Has a downloadable app which indicates satellite acquisition and battery state which was nice. Battery life good but one bugbear was that if not requested for position info for more than 15mins, it would go into a standby mode and then when asked again would have to re-acquire position. This is frustrting if one is in a descent with the STAR up on JeppFD for 20 mins and then on landing when selecting 10-9 Airport and expecting position info/ownship there would often be nothing. More so than in the air, it is on the ground taxiing that ownship really scores. Has a good positive on/off button function.
Recently released is a new GPS by Garmin Called the GLO. This is a combined GPS and GLonass receiver. It has excellent battery life-10hours plus and is really fast to acquire a position. It aso has a removable battery which is a standard Nokia BL-5CA phone battery which can be picked up cheaply as a spare/backup. There is unfortunately no app to acompany and the manual is pis poor-it seems you can only charge the device if it is switched on but nothing about that in the paperwork. It has a push on off button but again it is quite easy to turn on accidentally. However as the newest GPS available this one has been the most impressive it terms of acquisition time and battery life.
The first i the Bad Elf which plugs straight int the iPad dock connctor and is about3cm square. It uses the iPads batery and unless one uses an extension lead it is hard to place in a good position on an airliner with heated windows.
The next three are all bluetooth but Apple specific Bluetooth Protocol.
The first is the GNS5780. I had one until I left it on the glareshile. It was pretty good at acquiring and had very good battery life but had a quirky swipe strip to turn off and on and thye had major problems with being unable to swipe it off. It requird only a bare touch to turn it on, the upshot of which was it was easy to inadvertantly turn on when one put it in ones bag and thus was usually flat when you wanted it. I do believe they have now solved this issue.
Dual XGPS-150. Generally good performance though can really take some time to acquire position. Has a downloadable app which indicates satellite acquisition and battery state which was nice. Battery life good but one bugbear was that if not requested for position info for more than 15mins, it would go into a standby mode and then when asked again would have to re-acquire position. This is frustrting if one is in a descent with the STAR up on JeppFD for 20 mins and then on landing when selecting 10-9 Airport and expecting position info/ownship there would often be nothing. More so than in the air, it is on the ground taxiing that ownship really scores. Has a good positive on/off button function.
Recently released is a new GPS by Garmin Called the GLO. This is a combined GPS and GLonass receiver. It has excellent battery life-10hours plus and is really fast to acquire a position. It aso has a removable battery which is a standard Nokia BL-5CA phone battery which can be picked up cheaply as a spare/backup. There is unfortunately no app to acompany and the manual is pis poor-it seems you can only charge the device if it is switched on but nothing about that in the paperwork. It has a push on off button but again it is quite easy to turn on accidentally. However as the newest GPS available this one has been the most impressive it terms of acquisition time and battery life.
I could mention also, the Bad Elf Pro -
BE-GPS-2200 for those who like the numbers.
Wifi unit about half the size of a mobile phone, self contained = own battery and can be 'chucked' up on a window sill somewhere to WIFI connect with the I-pad, for which it is 'Apple approved'.
Can be charged in use via the 'cigar lighter' / supplied USB cable.
Advantage is several pages / bits of info on the unit's own screen, and is completely independant of I-pad port, leaving it avbl for charging etc.
USD$149 plus postage....
Seems to work quite well so far......
(No, not on commission.......)
Cheers
BE-GPS-2200 for those who like the numbers.
Wifi unit about half the size of a mobile phone, self contained = own battery and can be 'chucked' up on a window sill somewhere to WIFI connect with the I-pad, for which it is 'Apple approved'.
Can be charged in use via the 'cigar lighter' / supplied USB cable.
Advantage is several pages / bits of info on the unit's own screen, and is completely independant of I-pad port, leaving it avbl for charging etc.
USD$149 plus postage....
Seems to work quite well so far......
(No, not on commission.......)
Cheers
Dual XGPS-150. Generally good performance though can really take some time to acquire position.
one bugbear was that if not requested for position info for more than 15mins, it would go into a standby mode and then when asked again would have to re-acquire position.
I could mention also, the Bad Elf Pro - BE-GPS-2200 for those who like the numbers.
Join Date: Jan 2006
Location: Brisbane
Posts: 308
Likes: 0
Received 0 Likes
on
0 Posts
Has anyone else had issues with an extetnal GPS connecting to their iPad 2 since installing ios6? It connects via bluetooth ok, but won't show up your position on Jepp FD, OzRunways etc unless you reset your privacy/location settings before launching the app. I'm using a Dual XGPS - nothing is on their website and the above work around I picked up from an Apple forum. No more running multiple GPS-reliant apps at the same time...
