×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

EQMod : "Can not change rate while motor is running (direction differs)."

  • Posts: 24
  • Thank you received: 1
So what I'm gathering from this is to up the minimum guide pulse in INDI and EKOS?
3 years 5 months ago #63585

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

  • Posts: 535
  • Thank you received: 109
I don't know yet whether I solved anything, to be honest, but what I did was to make the Guider settings fit inside the INDI settings. That is, INDI would not try to limit the guider on the low end or the top end. Max guide pulse in INDI, I think I set to 500, and set max in Ekos to 300. For the minimum, I went with 20 in INDI and 30 in Ekos. I also set the integral to 0 in the Ekos/Kstars guider config. There are too many variables to point to any one thing and say it fixed it, but if I get another session like the tail of this last one, I will be happy.

Jim
3 years 5 months ago #63611

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

  • Posts: 24
  • Thank you received: 1
I found this rather odd. I'm currently out at the moment and it still keeps happening. My guide rate is at 0.8 hence the 12.0329 but why is the RA then deciding to go at 1.8x sidereal
[2020-11-30T19:32:46.640 GMT DEBG ][           org.kde.kstars.indi] - EQMod Mount : "[DEBUG] Timed guide West 79 ms at rate 12.0329  "
[2020-11-30T19:32:46.640 GMT DEBG ][           org.kde.kstars.indi] - EQMod Mount : "[DEBUG] StartRATracking() : trackspeed = 27.0739 arcsecs/s, computed rate = 1.8 "
[2020-11-30T19:32:46.641 GMT DEBG ][           org.kde.kstars.indi] - EQMod Mount : "[DEBUG] SetRARate() : rate = 1.8 "
[2020-11-30T19:32:46.641 GMT DEBG ][           org.kde.kstars.indi] - EQMod Mount : "[MOUNT] SetMotion() : Axis = 1 -- dir=forward mode=slew speedmode=lowspeed "
[2020-11-30T19:32:46.641 GMT DEBG ][           org.kde.kstars.indi] - EQMod Mount : "[SCOPE] CheckMotorStatus() : Axis = 1 "
[2020-11-30T19:32:46.642 GMT DEBG ][           org.kde.kstars.indi] - EQMod Mount : "[COMM] dispatch_command: \":f1\", 4 bytes written "
[2020-11-30T19:32:46.642 GMT DEBG ][           org.kde.kstars.indi] - EQMod Mount : "[COMM] read_eqmod: \"=111\", 5 bytes read "
[2020-11-30T19:32:46.643 GMT DEBG ][           org.kde.kstars.indi] - EQMod Mount : "[MOUNT] SetSpeed() : Axis = 1 -- period=344 "
[2020-11-30T19:32:46.644 GMT DEBG ][           org.kde.kstars.indi] - EQMod Mount : "[COMM] dispatch_command: \":f1\", 4 bytes written "
[2020-11-30T19:32:46.645 GMT DEBG ][           org.kde.kstars.indi] - EQMod Mount : "[COMM] read_eqmod: \"=111\", 5 bytes read "
[2020-11-30T19:32:46.646 GMT DEBG ][           org.kde.kstars.indi] - EQMod Mount : "[COMM] dispatch_command: \":I1580100\", 10 bytes written "

A few seconds later, it receives a command after the spike occurs and is told to do a 1776ms @ 0.8x when it then only does 0.2x
[2020-11-30T19:32:54.476 GMT DEBG ][           org.kde.kstars.indi] - EQMod Mount : "[DEBUG] Timed guide East 1776 ms at rate 12.0329  "
[2020-11-30T19:32:54.476 GMT DEBG ][           org.kde.kstars.indi] - EQMod Mount : "[DEBUG] StartRATracking() : trackspeed = 3.00821 arcsecs/s, computed rate = 0.2 "
[2020-11-30T19:32:54.476 GMT DEBG ][           org.kde.kstars.indi] - EQMod Mount : "[DEBUG] SetRARate() : rate = 0.2 "
3 years 5 months ago #63638

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

  • Posts: 535
  • Thank you received: 109
Your first set of logs is "Timed guide West", and the second is "Timed guide East". To guide west, the mount has to go faster than 1.0 (sidereal), so with your setting of .8, the combined speed is 1.8x, and the application computes how long it needs to go at this rate and gives it a time in milliseconds (79ms). The opposite is for guiding east, it needs to slow the mount down by .8, giving you a .2 rate.
3 years 5 months ago #63639

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

  • Posts: 24
  • Thank you received: 1
3 years 5 months ago #63640

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

  • Posts: 24
  • Thank you received: 1
I do keep getting this error when they occur

EQMod Mount : "[COMM] read error, will retry again... "
3 years 5 months ago #63643

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

  • Posts: 535
  • Thank you received: 109
What are your settings, both in Ekos and in INDI for the pulse limits?
3 years 5 months ago #63645

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

  • Posts: 24
  • Thank you received: 1
Update. I ended up changing the time and location updates in the INDI options from KStars to the mount and there's no spikes to be seen. Currently been over 30 minutes
3 years 5 months ago #63647

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

  • Posts: 535
  • Thank you received: 109
Ah! yes, I knew there was one more change that I made, I just could not recall what it was. I had been reading the thread about GPS and time sync, so wanted to see what would happen if I changed to kstars updates mount some time ago. I did switch it back to using the GPS along with the other changes. If that is the only thing you have changed, that must be the problem.

Jim
3 years 5 months ago #63648

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

  • Posts: 24
  • Thank you received: 1
I've been having to throw away half of my subs for the past 3 months because of this issue, so hopefully it doesn't budge and stays exactly like it is

Matt
3 years 5 months ago #63649

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

  • Posts: 535
  • Thank you received: 109
Tonight we are back to this mess. No settings changed from 2 nights ago when I had excellent guiding.



continuing to investigate, checking hardware logs as well. Bad cable? Bad connection? It is possible that 3 people with 3 different EQmod mounts have bad connections... but how likely?

It is a little different tonight though.
1) I only have 1 line of the Invalid parameter error in the log.
2) I have 109 "read error, will retry again" messages in about 90 minutes of operation... seems high. I went back to my old log, where I had a long stretch of good operation... No read errors.
3) The system running the ZWO cameras is reporting a USB reset after every image comes in from the guider camera:
kernel: usb 1-4.3: reset high-speed USB device number 10 using xhci_hcd
I did not look at this log prior to know if it was still doing this during the good operating time. It is doing it during the short windows of good guiding tonight though.

Of these things, number 2 above bothers me the most. The read errors stopped at the same time the mount started acting normal 2 nights ago. Going out to check some hardware now. Will park and re-power the mount, will pull the EQdirect wire and inspect, etc.
Last edit: 3 years 5 months ago by Jim. Reason: more analysis
3 years 5 months ago #63656
Attachments:

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

  • Posts: 24
  • Thank you received: 1
I've just had a look and there's quite a few read errors on mine too. Sometimes just before the spike and some not. Communication error in the eqdirect wire? Could also be voltage drops from psu? What psu are you both using?
3 years 5 months ago #63658

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

Time to create page: 0.922 seconds