I have a Dell notebook that stays in my CJ2+ baggage compartment. It is has the Williams engine diagnostic software to plug into the FADEC and is used to update the PL21 DBs. Never used for anything else and always with the plane regardless of crew.

Such first world problems you have to deal with....

Enjoy the ride.

Peace,
Don

Maybe so, but an expired database with no way to update it is a BDD.

Seriously? No.

I mean it would work but consider 1) weight 2) making sure it charges 3) cost 4) finding high speed internet 5) damage risk. Etc

Way too complex.

Sorry if I wasn’t clear. It has a 510. Owner has no more seat licenses. I try to sign in on his account and there are no seats available. Uses all three. So now what?

I'm still using older Garmin products, but I have a second set of data cards and program them BEFORE I leave on a trip with the next data cycle so I can swap on the road. On the extremely rare occasion that the next data cycle has not yet been published I have to take a laptop with me.

Matt

Does it matter than one of my cards is a 510?

Dunno. I don’t even know what a 510 card is.



Does it matter than one of my cards is a 510?

Does it matter than one of my cards is a 510?

Heard from Garmin (aka Trek)

They have heard about this issue before but don't have an elegant solution. No can do for the time being on multiple accounts sharing one aircraft database. Something about database royalties. I suspect that is an artifact of a time where this type of situation was not an issue.

Answer is to make it work with GP and iPad is to sign into BOTH the GP account and the FlyGarmin of the owner. After the databases are uploaded i need to sign out of both GP and FlyGarmin and back into my accounts. I also need to deactivate my device so as to free up the seat license. So

1) log out of two accounts 1) my GP, 2) my flyGarmin
2) Log in to two accounts 1) his GP, 2) his FlyGarmin
3) enable database concierge service (everytime I log into an account)
4) manage downloads (everytime I log into an account)
5) select tail number
6) download databases
7) upload databases
8) deactivate seat license
9) log out of two accounts 1) his GP, 2) his FlyGarmin
10) log into two accounts 1) my GP, 2) my FlyGarmin

Other gotchas:

1) he as two aircraft so I need to select the correct aircraft and not all aircraft
2) i have to record his user and password in my contacts or notes (security risk)
3) I MUST remember to log out before I fly (Gamin Support said why?) If I don;t my flight info goes to his logbook, not mine (bad)
4) if he had the GSR 56 sat system I could read all his text messages because Garmin doesn't allow you to delete text messages. (unacceptable).


So simple enough...10 steps and I am good to go.

Right...but the idea is to have two sets of cards. SO i can bring freshly updated cards to the aircraft without needing to get the cards that are in the aircraft. My question is what if I have a FS510? Will I have to buy a second 510? Or can I just pull out the 510, put in a standard card, update, and then put the 510 back in?

Right...but the idea is to have two sets of cards. SO i can bring freshly updated cards to the aircraft without needing to get the cards that are in the aircraft. My question is what if I have a FS510? Will I have to buy a second 510? Or can I just pull out the 520, put in a standard card, update, and then put the 510 back in?

That works for the Nav, basemap, Safetaxi, and Obstacle databases.

But Terrain and Charts don't get loaded into the GTN, they are stored on the card. Terrain doesn't update very often so not a big deal.

If you aren't using Charts then your scheme will work.

Mark would not an iPad that is dedicated to the plane work, and have the plane have its own account signed in on the iPad with LTE service. And just carry a back up battery in your bag, just in case the iPad is dead when you arrive.

It would in theory but now you have $500-$1000 invested. An LTE annual plan. Battery issues. Heat/cold issues. Plus you will want still have your own iPad for planning and data logging. So you have two iPads to deal with. And for what? Keeping databases up to date?

Not very elegant.