Jump to content
  • 0

DDM85 position error crashes


sdufoer

Question

All,

 

I experience the last months some very troublesome issues with my DDM85 mount that is installed on a remote observing facility in Spain. The mount is an incremental encoder version.

 

The mount is used for automated variable star surveys and has a 16”F6.7 Corrected-Dall Kirkham mounted on it. It sweeps from object to object, takes snapshots and it’s mixed with some long timeseries where it stays on the same object for several hours. Hence, the telescope is slewing around a lot.

 

The nature of the problem is that I get a multitude of “position errors”. Most of the times this happens in RA-axis, but sometimes it also happens on DEC-axis.
I wake up and see in the log a lot of position errors, mostly he could correct himself.

Sometimes (a lot) he cannot correct the error and then the mount stalls and I find it crashed.  Very dangerous because when it would start to rain the autopark from cloudwatcher will NOT work because mount is crashed.

Other times he just stops tracking for several hours, but doesn’t show a “position error”.

Because I sleep during the night and the telescope doesn't snow much issues when doing snapshots in the beginning of the night, I'm not around when it happens.  Usually it happens from 2-5am orso, when the telescope is busy with taking a long timeseries on an object.

 

Last night it was quite bad. I woke up around 5am and found the mount pointing upwards and has been crashed. Stop-start motors and trying to park the mount resulted in a series of uncorrectable position-errors. I had to stop-start motors again and again to move the mount even a bit. I park the mount horizontally (under a roof), and just before parking even the slightest move on the RA-axis would result in a crash. I retried and retried. I can only close the roof when mount is in park-position.  Motor on/off, then autoslew on/off and also power to the mount on/off. Almost 20 times until finally during one of these attempts autoslew itself crashed and windows reported error and killed autoslew. When I restarted autoslew after that crash the mount slewed around happily like nothing happened. 😕 This makes me wonder if the problem is software? 

 

When I do the motor calibration (when you power on the motors for first time), it most of the time shows a sinus wave, but lately these sinus waves are bit irregular and smaller and far away from each other.

 

I tried aproach after aproach after aproach to correct this:
-Rebalance several times. (Using help from the guys from the remote site.)
-New motor tuning. Fast & high performance mixed.
-Manual motor tuning. Usually the high performance auto tuning gives the best results and nothing weird to see there...
-New mount model, then different pointing models with different settings.
-Do homing position routine every night.
-Place the flexibility of position high (up to 30 degrees).  But even then it crashes, when I place it low (1 degree), it shows a train of position errors.

Nothing seems to help.

What is weird is that these kind of errors sometimes are gone away for some nights, then slowly it becomes worse and worse.


Some motor-ci error logs:
 

04:58:10.164: Axis 2 Pos:-109.90° Curr:+00.4A MagAng:+335° PosErr:+04.86arcsec

04:58:12.347: Axis 1 slewing to -38.21

04:58:12.371: Axis 2 slewing to -109.89

04:58:12.981: Axis 1 slewing to -38.20

04:58:13.006: Axis 2 slewing to -109.89

04:58:13.220: Axis 1 Pos:-042.35° Curr:+05.0A MagAng:+204° PosErr:+14946.64arcsec

04:58:16.326: Axis 2 Pos:-109.90° Curr:+00.2A MagAng:+335° PosErr:-00.02arcsec

04:58:19.382: Axis 1 Pos:-042.35° Curr:+05.0A MagAng:+204° PosErr:+15921.74arcsec

04:58:22.489: Axis 2 Pos:-109.90° Curr:+00.4A MagAng:+335° PosErr:+00.00arcsec

04:58:25.525: Axis 1 Pos:-042.35° Curr:+05.0A MagAng:+204° PosErr:+16899.64arcsec

04:58:28.667: Axis 2 Pos:-109.90° Curr:+00.4A MagAng:+335° PosErr:+00.00arcsec

04:58:31.608: Axis 1 Pos:-042.35° Curr:+05.0A MagAng:+204° PosErr:+17867.23arcsec

04:58:32.636: Axis 1 trying to autocorrect tracking error

04:58:34.963: Axis 2 Pos:-109.90° Curr:+00.2A MagAng:+335° PosErr:-00.02arcsec

04:58:38.100: Axis 1 Pos:-042.35° Curr:+05.0A MagAng:+204° PosErr:+645.13arcsec

 

 

And bit later during crash itself.

05:00:22.588: Axis 1 Pos:-042.35° Curr:+05.0A MagAng:+204° PosErr:+6527.77arcsec

05:00:25.555: Axis 2 Pos:-109.90° Curr:+00.2A MagAng:+335° PosErr:+00.00arcsec

05:00:28.685: Axis 1 Pos:-042.35° Curr:+05.0A MagAng:+204° PosErr:+7498.19arcsec

05:00:31.646: Axis 2 Pos:-109.90° Curr:+00.2A MagAng:+335° PosErr:+00.00arcsec

05:00:34.773: Axis 1 Pos:-042.35° Curr:+05.0A MagAng:+204° PosErr:+8467.02arcsec

05:00:37.395: Axis 1 slewing to -37.59

05:00:37.420: Axis 2 slewing to -109.89

05:00:37.760: Axis 2 Pos:-109.90° Curr:+00.3A MagAng:+335° PosErr:+08.06arcsec

05:00:39.957: Axis 1 slewing to -37.59

05:00:39.983: Axis 2 slewing to -109.89

05:00:40.591: Axis 1 slewing to -37.59

05:00:40.616: Axis 2 slewing to -109.89

05:00:40.921: Axis 1 Pos:-042.35° Curr:+05.0A MagAng:+204° PosErr:+17175.15arcsec

05:00:43.943: Axis 2 Pos:-109.90° Curr:+00.5A MagAng:+335° PosErr:-00.14arcsec

05:00:47.158: Axis 1 trying to autocorrect tracking error

05:00:48.457: Axis 1 Pos:-042.35° Curr:+00.1A MagAng:+204° PosErr:+00.40arcsec

05:00:49.516: Axis 2 Pos:-109.90° Curr:+00.1A MagAng:+335° PosErr:+00.08arcsec

05:00:54.690: Axis 1 Pos:-042.35° Curr:+05.0A MagAng:+204° PosErr:+968.47arcsec

05:00:55.629: Axis 2 Pos:-109.90° Curr:+00.1A MagAng:+335° PosErr:-00.04arcsec

05:01:00.787: Axis 1 Pos:-042.35° Curr:+05.0A MagAng:+204° PosErr:+1938.87arcsec

05:01:01.726: Axis 2 Pos:-109.90° Curr:+00.1A MagAng:+335° PosErr:+00.02arcsec

05:01:06.870: Axis 1 Pos:-042.35° Curr:+05.0A MagAng:+204° PosErr:+2906.74arcsec

 

And still bit later:

05:01:44.495: Axis 2 Pos:-109.90° Curr:+00.1A MagAng:+335° PosErr:+00.00arcsec

05:01:49.758: Axis 1 Pos:-042.35° Curr:+05.0A MagAng:+204° PosErr:+9731.88arcsec

05:01:50.613: Axis 2 Pos:-109.90° Curr:+00.1A MagAng:+335° PosErr:+00.02arcsec

05:01:51.406: Axis 1 slewing to -37.28

05:01:51.431: Axis 2 slewing to -109.89

05:01:53.963: Axis 1 trying to autocorrect tracking error

05:01:55.277: Axis 1 Pos:-042.36° Curr:+00.1A MagAng:+204° PosErr:+00.26arcsec

05:01:55.326: Axis 1 slewing to -37.28

05:01:55.351: Axis 2 slewing to -109.89

05:01:57.494: Axis 2 Pos:-109.89° Curr:+01.6A MagAng:+335° PosErr:+00.36arcsec

05:01:57.580: Axis 1 slewing to -37.27

05:01:57.604: Axis 2 slewing to -109.89

05:01:59.093: Axis 12 Tracking errors within 60 seconds, giving up

05:02:01.200: Axis 1 Pos:-042.36° Curr:+00.0A MagAng:+204° PosErr:+00.00arcsec

05:02:03.308: Axis 2 Pos:-109.89° Curr:+01.2A MagAng:+335° PosErr:+00.00arcsec

05:02:07.393: Axis 1 Pos:-042.36° Curr:+00.0A MagAng:+204° PosErr:+00.00arcsec

05:02:09.474: Axis 2 Pos:-109.89° Curr:+01.2A MagAng:+335° PosErr:+00.02arcsec

05:02:13.564: Axis 1 Pos:-042.36° Curr:+00.0A MagAng:+204° PosErr:+00.00arcsec

05:02:15.633: Axis 2 Pos:-109.89° Curr:+01.3A MagAng:+335° PosErr:+00.00arcsec

05:02:19.728: Axis 1 Pos:-042.36° Curr:+00.0A MagAng:+204° PosErr:+00.00arcsec

05:02:21.785: Axis 2 Pos:-109.89° Curr:+01.3A MagAng:+335° PosErr:+00.00arcsec


And then when it finally crashes:
 

05:02:58.780: Axis 2 Pos:-109.89° Curr:+01.3A MagAng:+335° PosErr:-00.02arcsec

05:03:02.885: Axis 1 Pos:-042.36° Curr:+00.0A MagAng:+204° PosErr:+00.00arcsec

05:03:04.957: Axis 2 Pos:-109.89° Curr:+01.3A MagAng:+335° PosErr:+00.06arcsec

05:03:08.519: Axis 1 Error Cleared

05:03:08.527: Axis 1 turned on Motor

05:03:08.532: Axis 1 turned off Motor

05:03:08.568: Axis 1 turned on Motor

05:03:09.057: Axis 1 Pos:-042.36° Curr:+01.9A MagAng:+204° PosErr:+01.81arcsec

05:03:09.751: Axis 1 slewing to 0.05

05:03:09.776: Axis 2 slewing to 0.22

05:03:11.224: Axis 2 Pos:-108.55° Curr:+01.6A MagAng:+352° PosErr:-00.60arcsec

05:03:13.527: Axis 1 trying to autocorrect error and slewing again to 0.05

05:03:18.252: Axis 1 autocorrect slewing error failed

05:03:18.281: Axis 1 Pos:-042.35° Curr:+00.0A MagAng:+204° PosErr:+00.02arcsec

05:03:18.311: Axis 2 Pos:-101.14° Curr:+01.5A MagAng:+351° PosErr:+30.07arcsec

05:03:18.445: Axis 12 Tracking errors within 60 seconds, giving up

05:03:24.439: Axis 2 Pos:-067.17° Curr:+00.7A MagAng:+085° PosErr:+00.00arcsec

05:03:24.628: Axis 1 Pos:-042.36° Curr:+00.0A MagAng:+204° PosErr:+00.00arcsec

05:03:30.557: Axis 2 Pos:-067.17° Curr:+00.8A MagAng:+085° PosErr:+00.00arcsec

05:03:30.745: Axis 1 Pos:-042.36° Curr:+00.0A MagAng:+204° PosErr:-00.02arcsec

05:03:36.708: Axis 2 Pos:-067.17° Curr:+00.8A MagAng:+085° PosErr:+00.00arcsec

05:03:36.898: Axis 1 Pos:-042.36° Curr:+00.0A MagAng:+204° PosErr:-00.04arcsec

05:03:42.836: Axis 2 Pos:-067.17° Curr:+00.7A MagAng:+085° PosErr:-00.02arcsec

05:03:43.026: Axis 1 Pos:-042.36° Curr:+00.0A MagAng:+204° PosErr:+00.00arcsec

05:03:48.999: Axis 2 Pos:-067.17° Curr:+00.7A MagAng:+085° PosErr:+00.00arcsec

05:03:49.178: Axis 1 Pos:-042.36° Curr:+00.0A MagAng:+204° PosErr:+00.00arcsec

05:03:55.141: Axis 2 Pos:-067.17° Curr:+00.7A MagAng:+085° PosErr:-00.02arcsec

05:03:55.331: Axis 1 Pos:-042.36° Curr:+00.0A MagAng:+204° PosErr:+00.00arcsec


These are the motor settings nowadays:
 

[Tuning Parameter of Axis 1]

Velocity Proportional Factor KP=1800

Velocity Integral Factor KI=100000

Position Proportional Factor KP=20

[Fast Tuning Parameter of Axis 1]

Velocity Proportional Factor KP=600

Velocity Integral Factor KI=30000

Position Proportional Factor KP=4

[Filter Parameter of Axis 1]

Filterfrequency of velocity measurement=2000

Filter Gain of Current=1

Filter numerator of Current Tz=0

Filter dunmerator of Current DZ=0

Filter numerator of Current Wz=3553058

Filter denominator of Current Tp=1

Filter denominator of Current Dp=7540

Filter denominator of current Wp=3553058

[Autofind Parameter of Axis 1]

No Hall measuring time (ms)=25

No Hall step size (degree)=12

No Hall test current (A)=1.30000000819564

[Tuning Parameter of Axis 2]

Velocity Proportional Factor KP=2355.138460584

Velocity Integral Factor KI=180000

Position Proportional Factor KP=19.8

[Fast Tuning Parameter of Axis 2]

Velocity Proportional Factor KP=850

Velocity Integral Factor KI=39000

Position Proportional Factor KP=4

[Filter Parameter of Axis 2]

Filterfrequency of velocity measurement=2000

Filter Gain of Current=1

Filter numerator of Current Tz=0

Filter dunmerator of Current DZ=0

Filter numerator of Current Wz=3553058

Filter denominator of Current Tp=1

Filter denominator of Current Dp=7540

Filter denominator of current Wp=3553058

[Autofind Parameter of Axis 2]

No Hall measuring time (ms)=22

No Hall step size (degree)=12

No Hall test current (A)=1.72799998894334

 

Anybody who can give my ANY insight is greatly appreciated !

What ARE these position errors exactly ?

Link to comment
Share on other sites

20 answers to this question

Recommended Posts

  • 0

The log shows that every instance of a position error is associated with the RA motor current increasing to 5Amps. In normal slewing or tracking this level of current should not be reached by either motor.

It also appears from the error log that the slew to -38.2 degrees stops at ~-42.

This raises several questions:

1. Is the mount running into an obstruction during the slew? Are there trailing wires which could snag? (this may seem a silly question, but it has happened before)

2. Does this behaviour occur at other positions?

3. Does it ever happen while tracking, or only during a slew?

Current running away during a slew is most likely due to an obstruction. The logs support this possibility, as the mount seems unable to get past -42 degrees when it is trying to get to -38. This sudden behaviour occurring during a slew is almost certainly not due to imbalance unless that imbalance is seriously high.

RA current running away during a long tracking period is usually due to imbalance, but it happens gradually until the mount mistracks. This can occur even if the balance is only a little off. With a heavy payload this type of failure is more likely than if the mount is not heavily loaded. Check that the payload is within the mount specification.

The problem is unlikely to be software.

If you have not already done so, I suggest you test the system during the day by slewing and tracking at varying positions and obtaining Clservo logs for the whole time you are doing the tests. You need to see what the logs show when the system is working properly as well as when it fails. Do you have a camera in the observatory so you can see what the system is doing?

Hope this helps

Link to comment
Share on other sites

  • 0

That is a VERY useful explanation Mark. Thanks a lot for your time !!!

I was especially puzzled by this important paragraph you’ve written.

Quote

RA current running away during a long tracking period is usually due to imbalance, but it happens gradually until the mount mistracks. This can occur even if the balance is only a little off. With a heavy payload this type of failure is more likely than if the mount is not heavily loaded. Check that the payload is within the mount specification.

 

Last night I had this issue again. The telescope observed the evening snapshots for almost 2,5 hours long, These were around 35 objects, so an equal amount of slews without issues.

Then the telescope started to run a long timeseries around midnight. The first 16 minutes were fine, then startrails. Which means: my frame taken at 00h18 was fine. The frame taken at 00h20 had startrails. It finally crashed around 00h40 and I found the instrument this morning pointing somewhere off and stalled. It parked without issues...

 

The Autoslew logs show the following:
 

-------------12:42:21 AM------------
Axis RA/AZ reported the following Problem:
Position Error
Position Error during slewing autocorrected by ClServo
Position Error correction failed
-------------12:41:01 AM------------
Axis RA/AZ reported the following Problem:
Position Error
Position Error during slewing autocorrected by ClServo
Position Error correction failed
-------------12:40:40 AM------------
Axis RA/AZ reported the following Problem:
Position Error
Position Error autocleared by ClServo

….(INSERT SAME POSITION ERROR here 10x )…….

-------------12:28:42 AM------------
Axis RA/AZ reported the following Problem:
Position Error
Position Error autocleared by ClServo
-------------12:21:11 AM------------
Axis RA/AZ reported the following Problem:
Position Error
Position Error autocleared by ClServo
-------------9:29:57 PM------------
DE/AL calibrated OK !
-------------9:29:46 PM------------
RA/AZ calibrated OK !
-------------9:26:50 PM------------


Then when I look into the CI Motor logs I see the first issue around 00h21. (PS: I enabled dithering in the hope it would “reset” possition error more easily).
 

00:20:58.852: Axis 2 Pos:-013.73° Curr:+02.1A MagAng:+309° PosErr:-00.04arcsec
00:20:59.426: Axis 1 Pos:-098.50° Curr:+05.0A MagAng:+219° PosErr:+16447.86arcsec
00:21:05.130: Axis 2 Pos:-013.73° Curr:+02.2A MagAng:+309° PosErr:+00.00arcsec
00:21:05.600: Axis 1 Pos:-098.50° Curr:+05.0A MagAng:+219° PosErr:+17430.12arcsec
00:21:09.640: Axis 1 Error: Position Error
00:21:09.655: Axis 1 trying to autocorrect tracking error
00:21:10.944: Axis 2 Pos:-013.73° Curr:+02.3A MagAng:+309° PosErr:+00.12arcsec
00:21:12.078: Axis 1 Pos:-098.50° Curr:+12.0A MagAng:+219° PosErr:+150.04arcsec
00:21:17.052: Axis 2 Pos:-013.73° Curr:+02.1A MagAng:+309° PosErr:+00.04arcsec
00:21:18.166: Axis 1 Pos:-098.50° Curr:+05.0A MagAng:+219° PosErr:+1115.10arcsec
00:21:23.231: Axis 2 Pos:-013.73° Curr:+02.1A MagAng:+309° PosErr:-00.02arcsec

00:28:33.549: Axis 2 Pos:-013.73° Curr:+00.9A MagAng:+309° PosErr:-00.06arcsec
00:28:38.609: Axis 1 Pos:-098.50° Curr:+05.0A MagAng:+219° PosErr:+17692.50arcsec
00:28:39.660: Axis 2 Pos:-013.73° Curr:+01.0A MagAng:+309° PosErr:-00.02arcsec
00:28:40.681: Axis 1 trying to autocorrect tracking error
00:28:45.122: Axis 1 Pos:-098.50° Curr:+05.0A MagAng:+219° PosErr:+471.84arcsec
00:28:45.631: Axis 1 slewing to -96.08
00:28:45.656: Axis 2 slewing to -13.72
00:28:46.076: Axis 2 Pos:-013.73° Curr:+00.5A MagAng:+309° PosErr:+15.25arcsec
00:28:48.169: Axis 1 slewing to -96.08
00:28:48.194: Axis 2 slewing to -13.72
00:28:48.793: Axis 1 slewing to -96.07
00:28:48.828: Axis 2 slewing to -13.72
00:28:50.836: Axis 1 Pos:-098.50° Curr:+05.0A MagAng:+219° PosErr:+9017.56arcsec
00:28:52.229: Axis 2 Pos:-013.73° Curr:+01.2A MagAng:+309° PosErr:+00.00arcsec
00:28:56.924: Axis 1 Pos:-098.50° Curr:+05.0A MagAng:+219° PosErr:+9986.29arcsec
00:28:58.328: Axis 2 Pos:-013.73° Curr:+01.5A MagAng:+309° PosErr:+00.00arcsec

00:29:46.015: Axis 1 Pos:-098.50° Curr:+05.0A MagAng:+219° PosErr:+17798.43arcsec
00:29:47.618: Axis 2 Pos:-013.73° Curr:+01.1A MagAng:+309° PosErr:+00.02arcsec
00:29:48.084: Axis 1 trying to autocorrect tracking error
00:29:51.579: Axis 1 Pos:-098.50° Curr:+05.0A MagAng:+220° PosErr:+324.18arcsec
00:29:53.522: Axis 2 Pos:-013.73° Curr:+00.9A MagAng:+309° PosErr:+00.04arcsec
00:29:57.688: Axis 1 Pos:-098.50° Curr:+05.0A MagAng:+220° PosErr:+1296.35arcsec
00:29:59.590: Axis 1 slewing to -95.77
00:29:59.615: Axis 2 slewing to -13.72
00:29:59.651: Axis 2 Pos:-013.73° Curr:+00.8A MagAng:+309° PosErr:+03.20arcsec
00:30:02.147: Axis 1 slewing to -95.77
00:30:02.172: Axis 2 slewing to -13.72
00:30:02.771: Axis 1 slewing to -95.77
00:30:02.797: Axis 2 slewing to -13.72
00:30:04.030: Axis 1 Pos:-098.48° Curr:+05.0A MagAng:+220° PosErr:+9919.69arcsec
00:30:05.924: Axis 2 Pos:-013.73° Curr:+01.4A MagAng:+309° PosErr:-00.12arcsec
00:30:10.168: Axis 1 Pos:-098.48° Curr:+05.0A MagAng:+220° PosErr:+10896.34arcsec
00:30:12.042: Axis 2 Pos:-013.73° Curr:+01.5A MagAng:+309° PosErr:-00.02arcsec

00:30:52.895: Axis 1 Pos:-098.48° Curr:+05.0A MagAng:+220° PosErr:+17695.18arcsec
00:30:54.774: Axis 2 Pos:-013.73° Curr:+01.2A MagAng:+309° PosErr:-00.02arcsec
00:30:54.963: Axis 1 trying to autocorrect tracking error
00:30:58.405: Axis 1 Pos:-098.47° Curr:+05.0A MagAng:+220° PosErr:+311.92arcsec
00:31:00.358: Axis 2 Pos:-013.73° Curr:+01.1A MagAng:+309° PosErr:+00.00arcsec

00:31:59.687: Axis 1 Pos:-098.47° Curr:+05.0A MagAng:+220° PosErr:+17661.86arcsec
00:32:01.554: Axis 2 Pos:-013.73° Curr:+01.5A MagAng:+309° PosErr:+00.00arcsec
00:32:02.773: Axis 1 trying to autocorrect tracking error
00:32:05.196: Axis 1 Pos:-098.47° Curr:+12.0A MagAng:+220° PosErr:+152.64arcsec
00:32:07.154: Axis 2 Pos:-013.73° Curr:+01.1A MagAng:+309° PosErr:+00.04arcsec
00:32:11.309: Axis 1 Pos:-098.47° Curr:+05.0A MagAng:+220° PosErr:+1122.07arcsec

00:38:40.717: Axis 2 Pos:-013.72° Curr:+01.5A MagAng:+309° PosErr:-10.15arcsec
00:38:43.783: Axis 1 trying to autocorrect tracking error
00:38:45.187: Axis 1 Pos:-098.47° Curr:+02.4A MagAng:+220° PosErr:+07.86arcsec
00:38:47.154: Axis 2 Pos:-013.73° Curr:+01.9A MagAng:+309° PosErr:+00.02arcsec
00:38:51.314: Axis 1 Pos:-098.46° Curr:+05.0A MagAng:+220° PosErr:+965.76arcsec

00:40:35.901: Axis 1 Pos:-098.46° Curr:+05.0A MagAng:+220° PosErr:+17609.00arcsec
00:40:37.963: Axis 2 Pos:-013.73° Curr:+01.8A MagAng:+309° PosErr:-00.02arcsec
00:40:38.967: Axis 1 trying to autocorrect tracking error
00:40:42.364: Axis 1 Pos:-098.46° Curr:+05.0A MagAng:+220° PosErr:+312.53arcsec
00:40:44.381: Axis 2 Pos:-013.73° Curr:+01.5A MagAng:+309° PosErr:+00.06arcsec
00:40:48.521: Axis 1 Pos:-098.46° Curr:+05.0A MagAng:+220° PosErr:+1291.77arcsec
00:40:50.479: Axis 2 Pos:-013.73° Curr:+01.5A MagAng:+309° PosErr:+00.02arcsec
00:40:54.695: Axis 1 Pos:-098.46° Curr:+05.0A MagAng:+220° PosErr:+2274.07arcsec
00:40:54.929: Axis 1 slewing to -93.03
00:40:54.954: Axis 2 slewing to -13.72
00:40:56.652: Axis 2 Pos:-013.72° Curr:+02.9A MagAng:+309° PosErr:+00.22arcsec
00:40:58.061: Axis 1 trying to autocorrect error and slewing again to -93.03
00:41:01.842: Axis 1 autocorrect slewing error failed
00:41:01.876: Axis 1 Pos:-098.46° Curr:+00.0A MagAng:+220° PosErr:+00.10arcsec
00:41:02.032: Axis 12 Tracking errors within 60 seconds, giving up
00:41:02.986: Axis 2 Pos:-013.72° Curr:+01.8A MagAng:+309° PosErr:+00.08arcsec
00:41:08.190: Axis 1 Pos:-098.47° Curr:+00.0A MagAng:+220° PosErr:+00.00arcsec
00:41:09.139: Axis 2 Pos:-013.72° Curr:+01.8A MagAng:+309° PosErr:+00.00arcsec

00:42:04.501: Axis 2 Pos:-013.72° Curr:+01.8A MagAng:+309° PosErr:+00.02arcsec
00:42:09.740: Axis 1 Pos:-098.47° Curr:+00.0A MagAng:+220° PosErr:+00.00arcsec
00:42:10.684: Axis 2 Pos:-013.72° Curr:+01.8A MagAng:+309° PosErr:+00.02arcsec
00:42:12.006: Axis 1 Error Cleared
00:42:12.017: Axis 1 turned off Motor
00:42:12.042: Axis 1 turned on Motor
00:42:12.047: Axis 1 turned on Motor
00:42:13.147: Axis 1 slewing to 7.61
00:42:13.172: Axis 2 slewing to 96.46
00:42:16.228: Axis 1 trying to autocorrect error and slewing again to 7.61
00:42:20.913: Axis 1 autocorrect slewing error failed
00:42:20.943: Axis 1 Pos:-098.46° Curr:+00.0A MagAng:+220° PosErr:+00.08arcsec
00:42:20.973: Axis 2 Pos:-008.17° Curr:+01.3A MagAng:+285° PosErr:+02.07arcsec
00:42:21.102: Axis 12 Tracking errors within 60 seconds, giving up
00:42:27.091: Axis 2 Pos:+025.36° Curr:+01.0A MagAng:+019° PosErr:+00.02arcsec
00:42:27.276: Axis 1 Pos:-098.47° Curr:+00.0A MagAng:+220° PosErr:+00.00arcsec
00:42:33.230: Axis 2 Pos:+025.36° Curr:+01.1A MagAng:+019° PosErr:+00.02arcsec

 

Now, when I look into the currents and how they evolve, I see the voltage indeed slowly increasing. As the following excepts lines show.

 

00:01:28.128: Axis 1 Pos:-102.92° Curr:+01.4A MagAng:+171° PosErr:-26.19arcsec
00:01:34.361: Axis 1 Pos:-102.90° Curr:+02.0A MagAng:+171° PosErr:-00.04arcsec
00:01:58.950: Axis 1 Pos:-102.80° Curr:+02.3A MagAng:+172° PosErr:+00.12arcsec
00:04:51.066: Axis 1 Pos:-102.08° Curr:+02.7A MagAng:+180° PosErr:+00.04arcsec
00:09:26.731: Axis 1 Pos:-100.93° Curr:+03.3A MagAng:+193° PosErr:+00.02arcsec
00:13:01.025: Axis 1 Pos:-100.03° Curr:+03.8A MagAng:+203° PosErr:+00.04arcsec
00:13:56.106: Axis 1 Pos:-099.80° Curr:+04.0A MagAng:+205° PosErr:-00.12arcsec
00:18:44.865: Axis 1 Pos:-098.60° Curr:+04.2A MagAng:+218° PosErr:-00.02arcsec
00:18:57.087: Axis 1 Pos:-098.55° Curr:+04.9A MagAng:+219° PosErr:+07.17arcsec
00:19:09.279: Axis 1 Pos:-098.51° Curr:+05.0A MagAng:+219° PosErr:+96.08arcsec
00:19:33.772: Axis 1 Pos:-098.50° Curr:+05.0A MagAng:+219° PosErr:+2817.23arcsec

What puzzles me is that there are some (3) outliers up to 12V !!

00:14:33.162: Axis 1 Pos:-099.65° Curr:+04.1A MagAng:+207° PosErr:+00.02arcsec
00:14:39.315: Axis 1 Pos:-099.62° Curr:+11.4A MagAng:+207° PosErr:-01.35arcsec
00:14:45.529: Axis 1 Pos:-099.60° Curr:+04.2A MagAng:+207° PosErr:+00.10arcsec

Or:

00:21:12.078: Axis 1 Pos:-098.50° Curr:+12.0A MagAng:+219° PosErr:+150.04arcsec
00:21:18.166: Axis 1 Pos:-098.50° Curr:+05.0A MagAng:+219° PosErr:+1115.10arcsec
00:21:24.254: Axis 1 Pos:-098.50° Curr:+05.0A MagAng:+219° PosErr:+2083.69arcsec

Or:

00:31:53.503: Axis 1 Pos:-098.47° Curr:+05.0A MagAng:+220° PosErr:+16678.17arcsec
00:31:59.687: Axis 1 Pos:-098.47° Curr:+05.0A MagAng:+220° PosErr:+17661.86arcsec
00:32:02.773: Axis 1 trying to autocorrect tracking error
00:32:05.196: Axis 1 Pos:-098.47° Curr:+12.0A MagAng:+220° PosErr:+152.64arcsec
00:32:11.309: Axis 1 Pos:-098.47° Curr:+05.0A MagAng:+220° PosErr:+1122.07arcsec

 

To further answer on your questions:

Quote

1. Is the mount running into an obstruction during the slew? Are there trailing wires which could snag? (this may seem a silly question, but it has happened before)

Most of my wires go though the mount. There is 1 external cable, but this one never blocks anything. If it would block something, it would show errors during the slews while taking the snapshots.

Quote

2. Does this behaviour occur at other positions?

Yes, it occurs at random at different objects in the sky, when I take a long timeseries and the mount has to track for a long time.  But the amount of errors is higher in the East side of the sky (where objects rise).

Quote

3. Does it ever happen while tracking, or only during a slew?

Sometimes while a slew, but very rare. This occurs most of the time, let's say 95%, during longterm tracking.

 

Quote

If you have not already done so, I suggest you test the system during the day by slewing and tracking at varying positions and obtaining Clservo logs for the whole time you are doing the tests. You need to see what the logs show when the system is working properly as well as when it fails. Do you have a camera in the observatory so you can see what the system is doing?

 

I attach Autoslew to planetarium program CartesduCiel and then I can click on different objects and it slews happily around without many issues. I can see this on the camera.
I have to do this during night because the instrument is installed under a roll-off roof and I’m worried about passing the sun and hence destroying the CCD. 
This slewing around works fine.  It's same principle as taking the snapshots.

Quote

With a heavy payload this type of failure is more likely than if the mount is not heavily loaded. Check that the payload is within the mount specification.

 

It’s a 40cm ODK Cassegrain, not a newton with camera’s mounted at the side. Only “inbalance” is bit a mounthubpro on top, a 30mm finder mounted on top + cables.

I have around +-60kg of counterweights. 2X20kg, 1x10kg, 2x5kg on different positions on counterweight bar. I use the 10kg counterweight to do the RA-balance.

See here for a picture: 
http://www.astronomie.be/sdufoer/equipment/odk16.jpg


I have chosen this setup especially because it would be as balanced as possible. I even opted for a FLI centerline filterwheel because of the orthogonal balance symmetry. It’s basically a round tube, with FLI atlas focuser, FLI centerline FW and CCD camera.

 

I’m after your explanation inclined to think the issue would indeed still be balance. I checked the balance again this morning.
The ASA manual states that both axis need to be horizontal. Which means there are basically 4 positions to do balance:
-telescope west, scope pointing north horizon.
-telescope west, scope pointing south horizon.
-telescope east, scope pointing north horizon.
-telescope west, scope pointing south horizon.

I did a check on the balance on these 4 different positions. Each position was a bit different and had slightly different behaviour. Probably this is because there is still some assymetry in the OTA (finder, mounthubpro, cables)…

I need the support of staff of the remote observing facility that can do the physical actions for me while I look on the screen. They charge a small fee for this.

I balance the mount on RA axis using the 10kg weight that slides bit east/west. On the DEC-axis I have the dewcover that I can push a bit forwards/backwards.

I think my next action will be to work further on the balance and do trail&error.
Bit to the left, then try another night, bit forward, then try another night...

 

I have some more questions:

-In the balance it seems DEC is pretty "point on", more than RA that behaves more different at different balance positions.  Is it possible this position error issues in RA can still be due to DEC balance issues?

-Is there an ideal balance position to be chosen? I found that this error occurs mostly in the East part of the sky (because that’s where the timeseries objects naturally rise).

-
I still wonder if there is some parameter tuning I can do in the motor tuning window? What sliders can I work on to go to a more "relaxed" state?

-What exactly happens in the Servo Setup window Position error axis RA/DEC. Would it help if I disable “ignore”, or “motor off” ? The sliders are now at RA:5degrees; DEC:20degrees, but I found that when I goo too sensitive I get more position errors, too relaxed sensitivy I have too much failed frames with startrails.  What would be the ideal value here?

Link to comment
Share on other sites

  • 0

It is very unlikely from my experience that small DE imbalance will cause RA tracking failure. Your Clservo log shows that the Axis 2 currents generally remain <2amps.

You could probably refine the DE balance - concentrate on the OTA horizontal position. Your on-site assistants need to realise how critical the balance is. Adjusting DE balance by moving the OTA is tedious and tricky. 1mm can make a significant difference.

RA Balance definitely needs refining. It also needs very fine adjustments to the counterweight position. My procedure - which is not done remotely - is to use the Balance Tool with the counter weight bar pointing east and then west. The best position of the counterweight is different for each side. I set it between the two positions, and then let the mount track for a long time. I have a 0-5amp digital ammeter in the 12V power line to the mount, and I watch and record the current over time.

If the current starts to run away, I move the counterweight accordingly. I then do the same on the other side of the meridian. This enables me to refine the counterweight position better than the Balance Tool does

In my case the final optimum favours the east side (I'm in the Southern Hemisphere) slightly.

In regards to 'relaxing' the mount, there are two important issues. Firstly, it is vital not to set the tuning parameters too tight (PID numbers too high). I have found it better to set the tuning manually. Generally the heavier the load, the tighter the tuning needs to be. But I would always try to set the lowest tuning numbers I can while still obtaining good tracking for up to 15 minute subs.

The load on my DDM85 is approximately 29kg, whereas your is at least 42 or so (OTA + FW + Camera + bits and pieces) so I don't require as tight tuning as you. But I suggest you experiment with lower numbers. (Incidentally, the sensitivity slider on my set-up is 1 degree for both axes.)

There is another important setting, particularly for heavy loads. In Sequence you can program periodic 'Stick/Slip' slews, which are designed to relieve excess current build-up during long runs. You can program intervals between the slews and the distance in degrees for the slew. Then during the run every,say 40min, the mount will slew 5 degrees, or whatever you set, and back again. I include the routine on both my DDM mounts, one which is relatively heavily loaded (DDM60), and the other, (DDM85) which is lightly loaded.

If you are not using Sequence, I strongly advise you to program such a feature into your routine.

Mark

Link to comment
Share on other sites

  • 0

Thanks again Mark for your very useful reply!

In meantime, I did some further experimentation.  RA-Axis balance seems absolutely spot on in the balance tool.  Even at 1A, it shows nice balance.  DEC is further off.  I can indeed ask local support to slide the counterweight 2mm upwards.  I noticed that I get the crash mainly when the OTA is pointed more towards the horizon so I have to slide the weight bit upwards.
I rather not touch the DEC balance, since balancing there involves moving the dew cover and that's not very easy on a scope that hanging free in the air, even when I do it myself.  That imbalance can be result of refocusing the CCD-camera.

I'm indeed trying now to do a platesolve+sync every 15 minutes.  I don't use a far-away slew of multiple degrees yet but I can implement this easily in CCDCommander (which I use).  A first try with the platesolve-sync workaround shows that it sometimes stops tracking, but then it's restored quickly.  I have to further experiment on this.

I placed my "relaxation" on 30 degrees.  I try to tune also the manual PID's.

I also asked ASA support if they have an idea what's happening with the logfiles.  This is what their support writes me:

Quote

Unfortunately it indicates that the mount has developed a bearing problem.
In the Cl-Servo.log you can see that the amp draw goes up to 5A, this is where you get the position error, as the motors can´t follow the encoder position anymore.
The best solution would be to send the mount in for a bearing service.
What you could also try before you decide to send the mount is to set up a simulated random pointing model like in the attached document.
It usually helps to give a better lubrication distribution.
Best regards
Wolfgang

The random-pointing model they talk about, is a dry pointingmodel run with simulated exposures with 1000 stars.  It seems that just sweeping around the mount nonstop for over some hours could free the lubrication.  But I already do this every night...  This instrument is a work-horse.

Sending the mount back to ASA is naturally a nightmare.  The telescope has to be remotely disassembled and then it has to be assembled again.

Because this would involve an expensive trip to Spain, and with these Covid19 lockdowns,.... this would naturally be my last option...  😞  Assuming the support in Spain can disassemble the telescope themselves.  Assembly of the telescope is only something I can do myself.  

Link to comment
Share on other sites

  • 0

I did not want to suggest bearing problems until you tried everything else.

I hope you can resolve the problem even if it means the mount must go back to ASA.

I can understand your frustration with lockdowns - here we have a 5km limit on travel, so I have not been able to get to either of my sites for 3 months.....they are not remotely operated

Mark

Link to comment
Share on other sites

  • 0

Hi,

I also experience the problem that after about 30 to 40 minutes, I get a position error due to the current reaching 5 amp. Using the "relax slew" option in Sequence is a feasible workaround for the moment but obviously does not cure the core of the problem. The idea to redistribute the lubrication by doing a pointing-file with hundreds of stars sounds interesting. I think I will give it a try tonight.

Best regards,

Robert

Link to comment
Share on other sites

  • 0

Hello Robert, sounds very familiar.

I can use the mount on a limited set of objects now.  On snapshots I don't have the issue and when I do timeseries I loop nonstop between 2 objects with every 30min a platesolve+sync on a 3th object.  The max exposure time is 90s.  This way it's usable, but the objects where I need to stay for hours on the same position are out of my observation loop.  😞

I tried the "relax slew" method, but in CCDCommander on a timeseries object and then I experienced another crash after several hours.  Which means, the mount needs to be slewing nonstop to have a workaround on this issue.

However, I decided that my mount needs to return to ASA for replacement of bearings.  I'm awaiting until they have time for disassembly in the remote hosting facility (E-Eye in Spain).

Link to comment
Share on other sites

  • 0

Maybe nothing to do with your problem at hand, but while your setup will be dismantled and your mount is going back to ASA, 
it may be a good thing to get more stability by removing the 'rat-cage' construction on your pier, or at least make it more rigid by using a piece of steel pipe close to the pier's diameter in between the pier and the mounting plate if you need the extra height...
This kind of rat-cage construction is a weak link in your setup and will be or already is cause of deflection and vibration.

Link to comment
Share on other sites

  • 0
23 hours ago, maxmirot said:

Has anyone disassembled to DDM85 or tried to replace the bearings themselves?

This seems to be a common problem.

You might need a hydraulic press but bearing replacement should not be too hard.  

 

Max

That wil probably void any warranty... (and maybe more difficult than expected)

Link to comment
Share on other sites

  • 0

Hi,

last week, I did a random 500 star pointing file to try to redistribute the lubrication - but that did not show any positive effects with regards to the raising current resulting in a position error "crash" once 5amps were reached. I get those crashes in the RA-axis after about 30-50 min when the mount is tracking continously.

Today I tried the following with interesting results:

First, I put the counterweight bar in a horizontal position and carefully checked the balance of the RA axis. The balance graph in autoslew indicated around 1 amp when moving the scope in and against the RA direction. Then I let the mount track in that position. The current of the RA-axis raised from 1.4 amps at the beginning and after about 50 minutes the axis crashed after the current reached 5 amps.

Then, I slewed back to the start position and moved the innermost weight on the counterweight  bar about 4cm towards the mount introducing a noticeable inbalance. The scope was on the west side, so the setup was heavier on that side and as expected, the balance graph showed a big inbalance: about 0.6 amps in RA-direction and about 1.4 amps in the opposite direction. Then I let the mount track in that position. The current of the RA-axis was about 0.9 amp at the beginning and slowly increased over time, but never exceeded 3.2 amps within the next 5 hours! So it did not crash.

I will try to do the test again within the next few days, but in case you experience those pointing error crashes, it might be a workaround to have the RA-axis a little heavier on the west side instead of trying to find the perfect balance. I have to check how little imbalance prevents the crashes from happening and whether it has a negative impact on tracking precision.

Maybe you can try that also and report back your findings,

best regards,

Robert

 

balanced_1105.PNG

unbalanced_1206.PNG

current.PNG

Link to comment
Share on other sites

  • 0

Robert,

I definitely get best long term performance if I finalise RA balance by running the system for an hour or so on each side of the meridian, and adjusting counterweights until I get the most equal current draw over time on each side.

  I find that in the Southern Hemisphere the optimum  current  occurs when the counterweight slightly favours the East side.

See my above post also.

Mark

Link to comment
Share on other sites

  • 0

Hello Mark,

thanks for your feedback, your experience seems to support my recent tests. I did another test 2 days ago with the scope on the east side and pointing to the south-east. With a well-balanced configuration I got the over-current-error after about 65 minutes. Then I slightly moved one of the counterweights (much less than in the first test) to make the setup slightly west-heavy. After more than 3 hours, the current was still under 3.5 amps.

As I have a bended pier and do not have to do a meridian-flip, in many cases I might get away with setting the slight unbalance at the beginning of the session for the whole night.

I will try your more sophisticated approach in trying to find the sweet spot but will probably still stick to performing relax slews in sequence (which won't work if I e.g. do sequences of planetary images or the sun).

Best regards,

Robert

 

Link to comment
Share on other sites

  • 0

I know I'm late, but maybe this piece could help:

I experienced a similar issue with my DDM60 back in august. Basically the logs were full of odd magnetic angles and high powers, with the mount not even moving anymore.

The scope was perfectly balanced (it's a remote system). After much back and forth with ASA we decided to swap the circuit board. Not easy with Covid and everything going on, but I still made it down to Namibia and swapped that circuit (plenty of tiny wires to check, trust me).

Okay so long story short, the swap didn't improve anything. I still had this weird issue.

The solution was to reset the "Autofind" settings: I played around with the values, and basically reset them, and did a "manual" Autofind for each axis. And suddenly it worked again like a charm. Seems that for whatever reason the starting values were in such a wrong combination that it caused the Autofind, happening when you first power up the motors, to give bad values and lead to all sorts of issues (position errors, swinging motors, the likes).

This might be completely unrelated, but maybe worth giving it a try. Btw, I will get my hands on a new direct drive mount from another Manufacturer (big US player) and I am eager to compare the performance with the ASA. I am still unhappy with the software, albeit having it run on a total of three mounts currently night after night. 

Link to comment
Share on other sites

  • 0

A few days ago I encountered the same problem with my DDM60. I suspect that the problem is the data from the servo / encoder. meanwhile I plug the powered usb hub on my mounting and it looks like it can return to normal. ASA gave me 3 meter USB cable maybe this is too long so data from servo / encoder is lost. shortening the USB cable is quite possibly the right solution. Thanks and sorry my english.

Regards,

Ishaq Zunaedi

Edited by gusdur2004
Link to comment
Share on other sites

  • 0
On 11/28/2020 at 9:49 AM, lukepower said:

Btw, I will get my hands on a new direct drive mount from another Manufacturer (big US player) and I am eager to compare the performance with the ASA. I am still unhappy with the software, albeit having it run on a total of three mounts currently night after night. 

Sorry for the hijack, but I am very curious. Lukas...

Link to comment
Share on other sites

  • 0
On 10/15/2020 at 10:03 PM, maxmirot said:

Has anyone disassembled to DDM85 or tried to replace the bearings themselves?

This seems to be a common problem.

You might need a hydraulic press but bearing replacement should not be too hard.  

 

Max

I strongly recommend to talk to ASA support directly before doing this. I'm sure they will give assistance and helpt to do that without harming the mount. 

Link to comment
Share on other sites

  • 0
On 11/28/2020 at 12:49 AM, lukepower said:

 

The solution was to reset the "Autofind" settings: I played around with the values, and basically reset them, and did a "manual" Autofind for each axis. And suddenly it worked again like a charm. Seems that for whatever reason the starting values were in such a wrong combination that it caused the Autofind, happening when you first power up the motors, to give bad values and lead to all sorts of issues (position errors, swinging motors, the likes).

 

Hi Luke, how do you reset the "Autofind"? Do you mean assign some other alt/az location as the new "home" position? Thanks! Yizhou

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...