A couple of suggestions:
Read the driver help. It tells you what information I need, in this case a driver log. This will show why the driver thinks that it doesn't support pulse guiding.
You need to talk to the PHD people about why their application fails to close properly.
I've just tried it with my AZEQ6 and PHD 2.6.1 and had no problems. It connects and can do pulse guiding. This is an indoor test but I can see the position change when pulseguide commands are sent.
Chris
Edit:
I've got the logs you sent to me privately, thanks, just what I needed.
From a quick look there didn't seem to be any problem from the driver point of view.
The log starting at 2359 shows CanPulseGuide returnng true and guide commands being done with no obvious problem.
But then, at 00:17:08 there's a CanPulseGuide that's returning false, even though there was a successful guide done a few seconds earlier.
Do you know if something changed at this time? I guess that PHD was connected before that and was guiding. Did another application connect to the driver?
I've had a total of 6 emails from you today so it looks as if this connection works - but you do need to give me time to respond.
Chris