Hello again BigDan,
You said:
" He also is going to evaluate the attached logs with a PE program. The more the merrier in evaluating what's going on."
So, for my own education, I'll take another shot - and because I'm totally unfamiliar with the Titan 50,and maybe have more questions than answers! The PHD2 Log Viewer gives the trace of your 45 minute GA run shown below.

The PA error isn't noted on this, but it shows some drift, so maybe it's worth another check using PHD2's drift alignment tool?
The trace contains 17 worm cycles in 45 minutes, indicating a primary period of about 160 seconds. Is that correct? - it seems unusually rapid. Are the mount driver parameters set correctly?
PHD2's periodic error analysis of the tracegives the following:

Here, the worm primary error at 160 sec (approx) has a Peak-to-Peak size of about 12.5 arcsec and RMS 4.4 arcsec. I think it appears rather large for a high end mount.
Apart from this main peak, there's a smaller one at around 323 seconds (twice the worm period) with a P-P of 3.2 arcsec and RMS 1.1 arcsec. I'd guess this is a gear/belt related overtone, your Titan specialist should know.
The single Dec glitch in this run was at about 19 minutes in. I won't even try to guess why. Whatever it was, the guide star was lost momentarily and the RA didn't really notice.
The only other comments I have is that your calibration is very good, but doesn't require the 150 pixel calibration distance you've set. I'd reset that to the default 25 or maybe 50 and/or adjust the guide rate closer to sidereal.
Goog luck.
- Jack