Kevin Ross replied to the topic 'EQ6-R PPEC - Questions' in the forum. 2 years ago

Even though the driver is called EQMod, it actually has nothing to do with the Windows ASCOM driver by the same name. In particular, there is no place to put a PPEC file for the driver to use.

To upload a PEC curve to the mount, the easiest thing to do is to do it via Windows and PEMPro.

Unfortunately, when you clicked the button to record the PEC to the mount, all you did was record an empty curve (a flatline). This is because while it is recording, it is "listening" for guiding pulses, and uses those to create the internal PEC model in the mount. But because you had guiding output disabled, you didn't actually record anything.

Please note that using PHD2 to try to create a PEC curve will not be optimal. It will record all the noise resulting from bad seeing, etc. since it will only record for a single worm period. Software like PEMPro will collect data over many worm cycles, create a smoothed curve, and can then upload that to the mount (through the Windows ASCOM driver).

To add some confusion, the Windows ASCOM driver can do its own PEC, independent of the PEC stored internal to the mount. That's not what we want. We want the PEC to be stored in the mount, so that when we reboot into Linux for INDI, the PEC is inside the mount and will just work.

The messages about the PEC being disabled while guiding are normal messages, which should probably be removed (or turned into debug messages). When you have PEC enabled in the mount, guiding pulses can end up being ignored or truncated. So to overcome that, the driver will turn off PEC, send the guiding pulse, then turn PEC back on. Those are the messages you are seeing, and is nothing to be concerned about.

Read More...