×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

HEQ5 guiding problems

  • Posts: 16
  • Thank you received: 0
Hi all,

After weeks of cloudy weather, yesterday it was finally clear. So I could test my setup for the first time. I have a mobile set-up :
  • HEQ5
  • Skywatcher refractor 120/600
  • Canon 700D
  • Guiding : ZWO 120mini on a guiderscope 50/160
  • Raspberry Pi 3B+

I have my HEQ5 connected by a cable between the handcontroller and the raspberry PI. When using the EQMOD - driver I set the handcontroller to PC direct. During photographing a serie I notice the HEQ5 stops tracking which results in a failure of guiding. As a consequence I need to recenter the object and restart the guiding. Sometimes it happens after 4 photo's, sometimes after one.

Any insights in what I'm doing wrong?

kind regards,
Gunther
Remote PI : Raspberry PI 3B+ with Stellarmate 1.16.2 /
Telescope : Skywatcher HEQ5 /
Camera : Canon 700D
5 years 2 months ago #33860

Please Log in or Create an account to join the conversation.

  • Posts: 1309
  • Thank you received: 226

Replied by Andrew on topic HEQ5 guiding problems

This sounds like a tracking error caused by interruption in communications, not specifically a guiding issue. It may be your cable connection. Are you connected through a usb hub? Do you have a good quality adapter? Cheap ones can suffer in the cold. You can try the Synscan driver or Synscan legacy driver if you suspect it is a driver issue.
5 years 2 months ago #33872

Please Log in or Create an account to join the conversation.

  • Posts: 472
  • Thank you received: 165
My HEQ5 used to be very picky about power and would at times disconnect the serial port which caused tracking to stop. I added a second power connector that screws tightly and haven't had an issue since. So I'd recommend checking the power cable connections and batttery voltage at least. Also EQDir-cable would probably be more robust than running through the hand controller serial port as the driver doesn't like serial disconnects.
5 years 2 months ago #33878

Please Log in or Create an account to join the conversation.

  • Posts: 16
  • Thank you received: 0
It seems I found reason why the HEQ5 randomly stops tracking. It seems that the EQMOD driver is loaded with the option to stop tracking when the horizon is on its limits. When I unmark this option the HEQ5 tracks without a problem. I was logging the mount and I found following records at the moment the tracking stopped :

2019-02-16T09:37:47: [INFO] Setting Backlash compensation - RA=10 microsteps DE=10 microsteps
2019-02-16T09:37:47: [INFO] updateLocation: long = 4.72417 lat = 50.8297
2019-02-16T09:37:47: [INFO] Loading device configuration...
2019-02-16T09:37:47: [WARNING] Can not load HorizonLimits Data File ~/.indi/HorizonData.txt: No such file or directory
2019-02-16T09:37:47: [INFO] updateLocation: long = 0 lat = 0
2019-02-16T09:37:47: [INFO] Mount is parked.

Now during tracking I get the following messages :
2019-02-16T23:03:01: [INFO] Align: current point is 7
2019-02-16T23:03:00: [WARNING] Horizon Limits: Scope outside limits. Nothing to abort.
2019-02-16T23:03:00: [INFO] Align: current point is 0
2019-02-16T22:17:10: [INFO] Align: current point is 7
2019-02-16T22:17:09: [INFO] Align: current point is 0
2019-02-16T21:23:41: [INFO] Align: current point is 7
2019-02-16T21:23:40: [INFO] Align: current point is 3
2019-02-16T21:17:52: [INFO] Align: current point is 7
2019-02-16T21:17:51: [INFO] Align: current point is 0
2019-02-16T21:06:10: [INFO] Align: current point is 7
2019-02-16T21:06:09: [INFO] Align: current point is 0
2019-02-16T20:59:30: [INFO] Align: current point is 7
2019-02-16T20:59:29: [INFO] Align: current point is 0
2019-02-16T20:59:10: [INFO] Align: current point is 7
2019-02-16T20:59:09: [INFO] Align: current point is 0
2019-02-16T20:43:39: [WARNING] Horizon Limits: Scope outside limits. Nothing to abort.
2019-02-16T20:42:38: [INFO] Align: current point is 7
2019-02-16T20:42:37: [INFO] Align: current point is 0
2019-02-16T20:39:56: [WARNING] Horizon Limits: Scope outside limits. Nothing to abort.
2019-02-16T20:33:53: [INFO] Align: current point is 7
2019-02-16T20:33:52: [INFO] Align: current point is 0

So he still gives a warning, but he doesn't abort the tracking.

kind regards,
Gunther
Remote PI : Raspberry PI 3B+ with Stellarmate 1.16.2 /
Telescope : Skywatcher HEQ5 /
Camera : Canon 700D
Last edit: 5 years 1 month ago by Gunther Fleerackers.
5 years 1 month ago #35093

Please Log in or Create an account to join the conversation.

  • Posts: 1309
  • Thank you received: 226

Replied by Andrew on topic HEQ5 guiding problems

Try resetting EQmod driver to default configuration and ensure time and geographic location are accurate.
5 years 1 month ago #35097

Please Log in or Create an account to join the conversation.

  • Posts: 80
  • Thank you received: 2

Replied by Philip Mair on topic HEQ5 guiding problems

I have exactly the same issue.

It seems that the driver sometimes read some wrong position data, because the next readed position is correct again. This also happens due to parking mode and no movement. In KStars the position is jumping for a second to another place and then jumps back to it's original Position.

Here is my log:

2020-01-27T18:01:44: [WARNING] Horizon Limits: Scope outside limits. Nothing to abort.
2020-01-27T17:54:55: [INFO] Device configuration saved.
2020-01-27T17:54:55: [INFO] Saving device configuration...
2020-01-27T17:54:55: [INFO] Observer location updated: Longitude (10.7178) Latitude (57.9369)
2020-01-27T17:54:55: [INFO] updateLocation: long = 10.7178 lat = 57.9369
2020-01-27T17:54:55: [INFO] Setting UTC Time to 2020-01-27T17:54:54, Offset 0
2020-01-27T17:54:55: [INFO] Device configuration saved.
2020-01-27T17:54:55: [INFO] Saving device configuration...
2020-01-27T17:54:54: [INFO] Device configuration saved.
2020-01-27T17:54:54: [INFO] Saving device configuration...
2020-01-27T17:54:54: [INFO] Device configuration applied.
2020-01-27T17:54:54: [INFO] Inverting Declination Axis.
2020-01-27T17:54:54: [INFO] Setting Slew rates - RA=64.00x DE=64.00x
2020-01-27T17:54:54: [INFO] Setting pulse limits: minimum pulse 10 ms, minimum timer pulse 100 ms
2020-01-27T17:54:54: [INFO] Setting Custom Tracking Rates - RA=0.5 arcsec/s DE=0.5 arcsec/s
2020-01-27T17:54:54: [INFO] Use Backlash : RA: False, DE: False
2020-01-27T17:54:54: [INFO] Setting Backlash compensation - RA=10 microsteps DE=10 microsteps
2020-01-27T17:54:54: [INFO] Observer location updated: Longitude (10.7178) Latitude (57.9369)
2020-01-27T17:54:54: [INFO] updateLocation: long = 10.7178 lat = 57.9369
2020-01-27T17:54:54: [INFO] Loading device configuration...
2020-01-27T17:54:54: [INFO] updateLocation: long = 0 lat = 0
2020-01-27T17:54:54: [INFO] Mount is parked.

I have to disable the stop Tracking option to, to avoid guiding problems ...
4 years 2 months ago #48632

Please Log in or Create an account to join the conversation.

  • Posts: 80
  • Thank you received: 2

Replied by Philip Mair on topic HEQ5 guiding problems

I had exactly the same issues with my HEQ5-PRO ... the cause was the pc direct mode ... it happend never since i use a self made eqdirect usb adapter
4 years 1 month ago #49115

Please Log in or Create an account to join the conversation.

Time to create page: 0.841 seconds