Pec Graph Window.


Carl Roland
 
Edited

Question,  Does the vertical bar that progresses across the Pec Graph window have any correlation to the function of PEC?  Here is what's happening on mine, The progress bar gets to the right side of the window and then it takes 25 seconds before it restarts on the left side. I do have a PEC trigger setup. As soon as it hits the trigger, that's when it restarts.       I don't have the PEC activated, or the auto guiding running. 
I know I have my tic count fairly close because I set a star on the cross hairs and 2 hours later, the star is just a couple of star diameters off the cross hairs.

  Thanks, Carl


Dan Gray
 

My guess is your ticks per worm rev are wrong, so it gets to the end of the predicted location, and it's waiting for the PEC trigger.
Dan


On Wed, Nov 9, 2022 at 5:38 PM Carl Roland <screwu@...> wrote:

[Edited Message Follows]

Question,  Does the vertical bar that progresses across the Pec Graph window have any correlation to the function of PEC?  Here is what's happening on mine, The progress bar gets to the right side of the window and then it takes 25 seconds before it restarts on the left side. I do have a PEC trigger setup. As soon as it hits the trigger, that's when it restarts.       I don't have the PEC activated, or the auto guiding running. 
I know I have my tic count fairly close because I set a star on the cross hairs and 2 hours later, the star is just a couple of star diameters off the cross hairs.

  Thanks, Carl


Carl Roland
 

If that was the case, Wouldn't my tracking speed be way off?  I place a star in the cross hairs, and two hours later it is still reasonably close.  If the speed was 25 seconds off per worm cycle, the star would be long gone. 
Unfortunately the worm/ring gear I bought has roughly 30"PV error.  I create the PEC curve with Pempro, and that cures most of the error.  My AO-8 takes care of the rest of it. 

PlatformTrackingRate=15094
PlatformUpDownAdjust=200
PlatformGoal=20000000
Latitude=4225
AzimuthEncoderTicksPerRev=40000
AltitudeEncoderTicksPerRev=40000

AzimuthMotorTicksPerRev=38523039       <----   Is this what controls the speed?

AltitudeMotorTicksPerRev=37909155


Dan Gray
 

AzimuthMotorTicksPerRev=38523039       <----   Is this what controls the speed?

I Carl,
don't think of ticks per rev as a speed control.  Think of it as an angle. So you have 38,523,039.  You have a fully geared system, right?  It should be easy to calculate.
How many teeth on the worm gear?
You must have a reduction between the worm and the motor.
So, basically you divide your ticks per rev by the number of teeth on the worm.  If you have 360 teeth on your worm, in your case, yourTicks per worm rev should be: 107008.
Don't forget to save the new ticks per worm rev.  I think you have to click twice.


image.png



On Thu, Nov 10, 2022 at 1:30 PM Carl Roland <screwu@...> wrote:
If that was the case, Wouldn't my tracking speed be way off?  I place a star in the cross hairs, and two hours later it is still reasonably close.  If the speed was 25 seconds off per worm cycle, the star would be long gone. 
Unfortunately the worm/ring gear I bought has roughly 30"PV error.  I create the PEC curve with Pempro, and that cures most of the error.  My AO-8 takes care of the rest of it. 

PlatformTrackingRate=15094
PlatformUpDownAdjust=200
PlatformGoal=20000000
Latitude=4225
AzimuthEncoderTicksPerRev=40000
AltitudeEncoderTicksPerRev=40000

AzimuthMotorTicksPerRev=38523039       <----   Is this what controls the speed?

AltitudeMotorTicksPerRev=37909155


Carl Roland
 
Edited

Dan, I'm absolutely not trying to argue  with you.  I'm just saying what is happening.  Yes, I do have a reduction in the drive train.
Motor  = 5.9:1
Encoder = 2000
Reduction = 9:1
Ring Gear = 364
So when I compute all the numbers, I get a total tic count of 38,656,800.   I had this number in the Servo.Cfg  file for a couple years.  I noticed that during auto guiding, the guider would always bump the mount to slow down.  So last week I did a star drift test without PEC or Guiding.  After two hours, the had drifted half way across the screen (fast). I then stopped the mount and it took 25 seconds to get back to the center cross hairs. I re-calculated the tic count to come up with
38,523,039.  A couple nights later, I did another drift test.  This time it stayed almost dead on except for the PE. 

I entered the final number in the box that you shown above and clicked it to "update TicksPerWormRev", then clicked again to "Save PEC Configuration". I close the Auto PEC window then re-open it and the number stayed.  I shut SiTech down and when I reopen SiTech, it reverted back to default number.  I then found the config file for the APEC and changed the number there. I saved that file and re-opened it right away and it stayed as I entered it.  I then restarted SiTech, Opened the Auto PEC tab and the number was back to the default. I watched the Worm Cycle status bar and it shown WormCycle=2 WormAngle236.? in between the Worm Sensor reset.

So I went through the process again, with "File Explorer"  checked the config file, it had the correct time stamp on it and when I opened the file, it had this
AutoLoadPECFileOnStart=0
SensorAlignWorm=1
AutoPlayOnStart=0
AutoDriftCorrectionOnStart=0
LagValue=2
TicksPerWormRevAz=39948   <-----   This number always comes back


I did a search in the SiTech.cfg file for the 39948 number to see if SiTech.cfg  was over-riding it but it did not find it.

EDIT: Okay, I just looked at the PEC Graph window, the vertical status bar gets to he right side when the "PEC is Playing #"  gets to 229  but the counter keeps going until it hit 255 when it resets.  Bottom line is that, is the PEC is correcting for the entire worm cycle, then I have zero problem with any display anomalies.

      Carl.


Dan Gray
 

Hi Carl, Sounds like there's a bug reading this file.  I'm coming out with a new version soon, I'll try to fix this.
In the mean time, just change it manually when you start your session.
Dan


On Sat, Nov 12, 2022 at 9:58 AM Carl Roland <screwu@...> wrote:

[Edited Message Follows]

Dan, I'm absolutely not trying to argue  with you.  I'm just saying what is happening.  Yes, I do have a reduction in the drive train.
Motor  = 5.9:1
Encoder = 2000
Reduction = 9:1
Ring Gear = 364
So when I compute all the numbers, I get a total tic count of 38,656,800.   I had this number in the Servo.Cfg  file for a couple years.  I noticed that during auto guiding, the guider would always bump the mount to slow down.  So last week I did a star drift test without PEC or Guiding.  After two hours, the had drifted half way across the screen (fast). I then stopped the mount and it took 25 seconds to get back to the center cross hairs. I re-calculated the tic count to come up with
38,523,039.  A couple nights later, I did another drift test.  This time it stayed almost dead on except for the PE. 

I entered the final number in the box that you shown above and clicked it to "update TicksPerWormRev", then clicked again to "Save PEC Configuration". I close the Auto PEC window then re-open it and the number stayed.  I shut SiTech down and when I reopen SiTech, it reverted back to default number.  I then found the config file for the APEC and changed the number there. I saved that file and re-opened it right away and it stayed as I entered it.  I then restarted SiTech, Opened the Auto PEC tab and the number was back to the default. I watched the Worm Cycle status bar and it shown WormCycle=2 WormAngle236.? in between the Worm Sensor reset.

So I went through the process again, with "File Explorer"  checked the config file, it had the correct time stamp on it and when I opened the file, it had this
AutoLoadPECFileOnStart=0
SensorAlignWorm=1
AutoPlayOnStart=0
AutoDriftCorrectionOnStart=0
LagValue=2
TicksPerWormRevAz=39948   <-----   This number always comes back


I did a search in the SiTech.cfg file for the 39948 number to see if SiTech.cfg  was over-riding it but it did not find it.

EDIT: Okay, I just looked at the PEC Graph window, the vertical status bar gets to he right side when the "PEC is Playing #"  gets to 229  but the counter keeps going until it hit 255 when it resets.  Bottom line is that is the PEC is correcting for the entire worm cycle, the I have zero problem with any display anomalies.

      Carl.


Carl Roland
 

Very good Dan.  Thank you Sir.