Dude that is wild and interesting, thanks for the explanations. And wow, that’s a lot. Awhile back I read through your plans for FPH on a heat pump system, I knew it would be complicated. But it’s perhaps enough to frighten away anyone thinking of implementing FPH to a home AC/heatpump. First, I didn’t realize FPH even had a different controller for driving heat pumps, now I start to understand why.
More thoughts, if you’re interested in continuing…… If not I’ll understand.
“In my system where the reversing valve solenoid is active during cooling it will stay active even after the system switches off”. Do you mean that is the heat pump design such that it leaves that valve energized even when the system is off/idle? I could see a motivation for that to prevent unnecessary moving of refrigerant around, but If so that still seems like an odd design to leave a coil (for a relay or valve or whatever) energized all the time even when the entire system is idle. Still, being all grumpy about your heat pump’s design doesn’t help you much!
Anyway, for such a system (active valve coil when idle) it seems to indicate a need for FPH to find a better way of sensing the mode of the heat pump. Duh, right? Maybe some other signal from the thermostat – cool vs heat mode perhaps - driving a small relay (eg opto isolating chip) to interrupt the sensing wire back to the right place in FPH. Unless I’m misunderstanding, my logic (and my head hurts) tells me that if FPH needs to sense that reversing valve signal, how could they interrupt that same sensing with
anything – let alone a simple device like a diode. Even if their FPH logic is sound, meaning the diode is in the right place to prevent back feeding, the diode will only suppress one half the current (the negative-going cycle or positive, whichever based on polarity of insertion). So some current would flow regardless, and who knows if that current is sufficient to cut off the device it’s driving. Hence your idea of something better to cutoff all current, whether a transistor or something else. But either way, it seems like a tail chasing scenario wherein “I need that signal to know the mode, but I also need to ignore it – “sometimes”. Ugh. If I sound confused, I probably am! Perhaps one part of the FPH always needs to sense it, and another FPH input needs to ignore it. Again, circular logic, and more weirdness.
“which puts the system into a very dangerous state where the reversing valve switches and the racetrack is still active from the FPH controller effectively causing the compressor to pump down into a vacuum state. Ask me how I figured this out” Well, I’m asking, but I have 3 guesses. If the low side was in vacuum then the high side should be very high. Dangerous indeed! If you didn’t have gauges on there when it first happened, I’m guessing the compressor cut-out – either due to high pressure, or low pressure on that side, or it cut-out from overcurrent/overheating. Then gauges would have confirmed the action. Nothing that you want your compressor experiencing, of course. Third guess is that something popped and you lost all refrigerant, yuk that.
Hopefully FPH gets back to you with a better solution. Maybe not hold our breath, right? I watched their site for diagram changes for awhile after I advised them back in 2012-ish they specified the wrong rib relay for the cooling fan cutoff (NC vs NO) but never saw the change. Perhaps they fixed it or you caught it yourself.
“Technically the common is shared” I guess you mean that one side of the 24vac circuits are common to ground and therefore “shared”. Not sure that needs to be the case, but either side (FPH or heat pump) could ground one side, so shared in that sense, with possible stray currents. Might be interesting, if so, to find where and isolate the 24vac circuits from ground.
“and the racetrack is still active” Is racetrack a typo? Or I don’t know what that is, except that it’s a place to lose money
So.... How is it working out for extending your swim season with free heat? Free if you don't consider paying yourself for tons of hours troubleshooting!