Some people reported not working AP with GNS530 in the Just Flight Arrows. I own them too so tried it:

I tested the 530 in the Arrow. I got it working but not as it is supposed to work:

I started with a loaded PLN, which showed up nicely in the Garmin. But the planes goes in spiral dive when putting AP in NAV mode while CDI is in GPS mode and NAV-GPS switch is in GPS position.

Quickly turned off AP and manually leveling off. Then tried some things.

What worked for me: in the tablet switch to no GPS but radios. AP off and all switches GPS off (dont know if that is necessary but its what I did). Then on the tablet choose GNS530 again. Switch to GPS mode, and then it would follow the PLN.

TimeClimb fix is now added after SU5 for all imported Flightplans. I have found that whenever you are "going to" or "coming from"  TIMECLIMB , GPS AP NAV won´t follow the path even after a Direct To has been set.

Once in between two original flighplan fixes(not TimeClimb Asobo thingie) GPS AP works as expected. My advice is to set a fix very close to departure, so that TimeClimb fix is almost inmediately gone and  allows you to follow the Magenta line almost inmediately after takeoff. For PMS 50 GTN 750 users, another workaround is to import FLP , that way you skip that TimeClimb fix completely. 

Edited August 6, 20214 yr by Aristoteles

22 minutes ago, Aristoteles said:

TimeClimb fix is now added after SU5 for all imported Flightplans. I have found that whenever you are "going to" or "coming from"  TIMECLIMB , GPS AP NAV won´t follow the path even after a Direct To has been set.

Once in between two original flighplan fixes(not TimeClimb Asobo thingie) GPS AP works as expected. My advice is to set a fix very close to departure, so that TimeClimb fix is almost inmediately gone and  allows you to follow the Magenta line almost inmediately after takeoff. For PMS 50 GTN 750 users, another workaround is to import FLP , that way you skip that TimeClimb fix completely. 

What is TimeClimb fix?

23 minutes ago, Rene_Feijen said:

What is TimeClimb fix?

We don't know - Asobo have not explained what this is meant to represent or why they have added it.

Current work around is to create the flight plan on the GPS unit after the flight has started (or if you are using the PMS50 mod, load a saved flight plane into the GPS itself)

I'm having problems with my parking brake settings on the JF arrow. The parking brake works correctly on other aircraft as in it's set to work as a toggle, yet on the JF Arrow I have to hold down the parking break to release the brake.

29 minutes ago, eaim1973 said:

I'm having problems with my parking brake settings on the JF arrow. The parking brake works correctly on other aircraft as in it's set to work as a toggle, yet on the JF Arrow I have to hold down the parking break to release the brake.

Are you on version 0.4.0 of the Arrow released yesterday? The parking brake issue was supposed to have been fixed. 

For me with the latest JF update the parking brake works correctly.

I know there was a nasty bug with the AP where the plane would bank hard and dive.  The workaround was to always turn on heading hold first, then turn the ap on, then nav mode.  I'm not sure if the latest patch fixes it or not (haven't installed), but try that.  It isn't correct behavior, but it keeps you from almost crashing the plane.  Basically, turn on heading hold and leave it on the whole flight.  It seemed to work for me, but again this is before the latest patch. 

For me worked, did it just now: loaded the Arrow on parking of KORS. Started the plane, on the tablet switched to radios, then to GPS 530 again. Entered flightplan manually KORS W49 KFHR KBVS KSEA.

Took off, then switched all correctly for GPS flying, turned on AP and it followed the plan to W49. After W49 leg to KGHR became active, Arrow turned correctly.

Before reaching KFHR I activated the leg to KBVS, and that worked.

I then activated leg to KSEA and that worked also.

So I could succesfully bypass 2 legs

with latest Arrow update and latest PMS50 mod for G530ot in the plane.

5 minutes ago, kerosene31 said:

I know there was a nasty bug with the AP where the plane would bank hard and dive.  The workaround was to always turn on heading hold first, then turn the ap on, then nav mode.  I'm not sure if the latest patch fixes it or not (haven't installed), but try that.  It isn't correct behavior, but it keeps you from almost crashing the plane.  Basically, turn on heading hold and leave it on the whole flight.  It seemed to work for me, but again this is before the latest patch. 

I had that sometimes to also, randomly it seemed, before SU5.

1 hour ago, Matchstick said:

We don't know - Asobo have not explained what this is meant to represent or why they have added it.

Current work around is to create the flight plan on the GPS unit after the flight has started (or if you are using the PMS50 mod, load a saved flight plane into the GPS itself)

There is another workaround that solved the problem for me: Reverse the flightplan twice in the GPS.

This way you can still create or import the flightplan in MSFS before starting the flight. Once you sit in the aircraft you can perform this double reverse in the GPS and the TIMECLI fix is gone.

Just now, orchestra_nl said:

There is another workaround that solved the problem for me: Reverse the flightplan twice in the GPS.

This way you can still create or import the flightplan in MSFS before starting the flight. Once you sit in the aircraft you can perform this double reverse in the GPS and the TIMECLI fix is gone.

CLEVER ! 🙂

42 minutes ago, orchestra_nl said:

There is another workaround that solved the problem for me: Reverse the flightplan twice in the GPS.

How do you do this with the GNS and the GTN?

15 minutes ago, captain420 said:

How do you do this with the GNS and the GTN?

In the GNS530/430, you open the flightplan (FPL button), then the "Menu" button and select "Invert Flight Plan".

That immediately takes care of the TIMECLI fix but now the flightplan is in reverse so you need to invert it a second time.

I assume the GTN also has an invert/reverse option somewhere.

Edited August 6, 20214 yr by orchestra_nl
spelling

After updating yesterday I found in the Turbo variant that engine damage now happens immediately when going into "boost" mode. I took off at altitude and needed the extra power and the engine quit on me less than a minute from setting take off power. checking the EFB after confirmed engine damage was 100%. This wasn't an issue before the update. Can anyone confirm? I thought there should be a grace period and you can give it full power so long as you don't leave it there too long.