Instead it commanded the AP to turn right over to wrong side of the plotted pattern and completed a teardrop on the wrong side.  I let it complete the turn but was perturbed.

What could have caused that?  What could I be missing?

The approach was activated automatically before the IAF on the IFD as expected and because it was a PT required entry, the hold was part of the approach.  I ‘armed’ the approach on my EFIS after activation and ‘executed’ it before the IAF.  The entire approach was flown with the AP with the right turn into a parallel entry being the only unexpected behavior

My EFIS does not graphically show the hold or entry track and I the small display of the 440 made it difficult to notice the track of the entry. 

It sounds as if the autopilot is steering direct to the next waypoint instead of flying the hold. That would be the expected behavior without roll steering commands.

Rolfe

I had a G430w before that I did the plug-in replace with the IFD.  No other changes.

The setup would fly holds in the miss correctly.  I can’t recall flying reversal turn holds because that’s not typical.  I’m looking forward to being able to fly ad hoc holds with the IFD.

What do you mean by ‘roll steering commands’?  How does that differ from what I might otherwise have?

I need the logs from the IFD, which you can download to the USB stick.  Instructions for downloading logs are in the IFD440 Pilot's Guide on page 6-63.  

Given what you’ve told me so far, it does sound like the AP was commanded to simply turn back to the KAKLE and took the shortest route which would have been a right turn.  The hilpt was simply not commanded.  It worked because I was at 4,000 already and there was no other traffic or obstructions present but it wasn’t the right thing to do.

You don't need to go fly again.  Just put the USB stick into the IFD, power it up, and then download the logs.