´╗┐
×

INDI Library v1.7.9 Released (23 Jun 2019)

INDI Library v1.7.9 is mostly a maintenance release to fix a few bugs in several drivers.

guide module (internal)

  • Posts: 82
  • Thank you received: 13

Replied by wotalota on topic guide module (internal)

Ron,
Comparing your good night to the bad ones, was the quality of "seeing" and the target/elevation similar.
The guide star you presented on the good night looks decent compared to the bloated one on the bad night.
Just wondering why the results with same balance/focus settings etc. are so different.

I'm out of it for a bit, just changing over to a heavy long focal length payload and waiting for some extra weights to arrive
to be able to balance.
Mach1, ES80 x0.8, ASI071, ASI120 OAG, focusPro
2 months 2 days ago #38263

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

  • Posts: 326
  • Thank you received: 50

Replied by Ron Kramer on topic guide module (internal)

4. While using the Pulse Guide option further consideration need be given the pulse length as set up in the options (click the "Options ..." button on the lower right corner) in the Guide Module of EKOS. (Following is a simplified explanation) Any pulse length of 1000 (ms) or longer is handled with a different move command in the driver rather than the standard pulse command due to a limitation on the GTOCP3 controller. Michael had this working well and then had to fix this again in recent weeks due to a regression in the code. I have tested his recent fix and it seems to be working properly again.

I use a pulse length of 900 (the default unit is ms) and I usually only do 4 or 5 iterations and have found that this works well for the calibration of the mount while using either the ST4 connection or the Pulse Guide function. I have been using KStars/Ekos/INDI with my kit for 2+ years and in recent months run several all night "automated" imaging runs with good success. I understand the frustration of software bugs or user error in learning a new set of tools and encourage you to keep at it as I am sure it will come together for you.


Thanks - I had all correct, but I have over 1000 in this field. I'll set it to 900. Thank you - when it starts jumping across the sky - might be when it uses the other move motion. Can't wait to try it again.
AP Mach1 / CP4 APCC & PEMpro.
EXP SCI - ED152cf APO - Celestron 11" RASA - Stellarvue 80mm
Baader F2 HS NB filters, Lodestar X2 guide camera / OAG - ZWO 290mm mini
ZWO ASI1600MM Pro / ASI174M (solar) / ASI094MC
NEXDome, CLoudwatcher, AVX mount/ASIair and Stellarmate

2 months 1 day ago #38275

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

  • Posts: 326
  • Thank you received: 50

Replied by Ron Kramer on topic guide module (internal)

Yes - conditions were close enough. The difference is - sometimes when I calibrate it goes jumping around instead of just nudging the star. The good night (the only one I had). it somehow skipped calibration and worked WELL.
The above msg points out that a <1000 needs to be entered for max pulse. I've had 1000-2000 and 5000 in there. He suggests 900. So that it my next test. If it can calibrate I should be golden.
AP Mach1 / CP4 APCC & PEMpro.
EXP SCI - ED152cf APO - Celestron 11" RASA - Stellarvue 80mm
Baader F2 HS NB filters, Lodestar X2 guide camera / OAG - ZWO 290mm mini
ZWO ASI1600MM Pro / ASI174M (solar) / ASI094MC
NEXDome, CLoudwatcher, AVX mount/ASIair and Stellarmate

2 months 1 day ago #38276

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

  • Posts: 326
  • Thank you received: 50

Replied by Ron Kramer on topic guide module (internal)

I t can't hurt. But I already knew the settings/options just by seeing them in the driver. AP does say guiding rate is 1.00.
I knew about ST4 and Pulse and I was using it correctly. (I guess guessed, locially) but I never knew about the <1000 move. I'll set my max pulse to 900 and try again!
I have a newer Mach1 with GTO4 (their latest) with >V chip and latest firmware.

Ihoujin wrote: That's quite a lot of useful information by 'LinuxUser' specifically that the driver is only suited for certain controllers, or firmware and specific toggles for st4/pulse guiding...

Anybody else feel that indi drivers should have an Info tab with developer notes for such key information?

AP Mach1 / CP4 APCC & PEMpro.
EXP SCI - ED152cf APO - Celestron 11" RASA - Stellarvue 80mm
Baader F2 HS NB filters, Lodestar X2 guide camera / OAG - ZWO 290mm mini
ZWO ASI1600MM Pro / ASI174M (solar) / ASI094MC
NEXDome, CLoudwatcher, AVX mount/ASIair and Stellarmate

2 months 1 day ago #38277

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

  • Posts: 82
  • Thank you received: 13

Replied by wotalota on topic guide module (internal)

Ron,
No errors in your log/indi telescope panel when it goes bad?

Hope the 900ms setting helps but you should not be encountering that problem, Mike fixed it about 4 months ago.
indilib.org/forum/mounts/4280-astrophysi...l-pulse-guiding.html
/tom
Mach1, ES80 x0.8, ASI071, ASI120 OAG, focusPro
2 months 1 day ago #38310

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

  • Posts: 326
  • Thank you received: 50

Replied by Ron Kramer on topic guide module (internal)

I can include logs here. I tried last night at a max pulse of 900.
Same thing occured (small steps - then large jumps during calibration). I did later get it to calibrate, but guiding was mediocre and the guide star was often lost. (I have not focused the guide scope since I switched to it) I need to try that to see if it helps.

Anyone know the difference in the 2 axis calibration button? I suspect that means calibrate NS and EW (both directions) wouldn't we WANT TO DO THAT ALWAYS? - I turned it off and it did calibrate if I did iterations reduced to 3.

I turned it back on and it calibrated sometimes and later started jumping across the sky again. It seemed like 50/50 if a calibration would work or it would start jumping. When it did calibrate, guiding was pretty poor. (NOT ANYHING like that GREAT FLUKE guiding I had last week in previous post in here).

Trying some test subs. I couldn't get a usable sub in 180 seconds. Luckily I'm a nebula lover and nothing above my tree line this month. I suppose I could try PHD on the server again. = (

I'd give most anything to have guiding be like it was last week resulting in under .39 for over 2 hours straight. I'll check my balance, I'll swap the 290mm to the Lodestar, I'll fine focus the guide scope and see what becomes of that.
AP Mach1 / CP4 APCC & PEMpro.
EXP SCI - ED152cf APO - Celestron 11" RASA - Stellarvue 80mm
Baader F2 HS NB filters, Lodestar X2 guide camera / OAG - ZWO 290mm mini
ZWO ASI1600MM Pro / ASI174M (solar) / ASI094MC
NEXDome, CLoudwatcher, AVX mount/ASIair and Stellarmate

2 months 8 hours ago #38356

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

  • Posts: 842
  • Karma: 6
  • Thank you received: 223

Replied by wvreeven on topic guide module (internal)

Ron, could you once more explain how you connect your mount to Ekos (cables, driver, etc) and what mount you have? That may give us a hint as to what's happening.

And perhaps you could list your imaging gear in your signature as most of us do so it is easy to see that.
ASI1600MM-Pro Cooled and filter wheel with a SkyWatcher Esprit 80 ED on a SkyWatcher HEQ5-Pro

ASI1600MM-Pro Cooled and filter wheel with an 8" TS Ritchey-Chr├ętien on a SkyWatcher EQ6-R
The following user(s) said Thank You: Ron Kramer
2 months 7 hours ago #38360

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

  • Posts: 326
  • Thank you received: 50

Replied by Ron Kramer on topic guide module (internal)

wvreeven wrote: Ron, could you once more explain how you connect your mount to Ekos (cables, driver, etc) and what mount you have? That may give us a hint as to what's happening.


AP Mach1 (recent) GTO4 latest chip (V+)
I have excellent guiding results using windows and PHD2 (Typically guiding at .35 average total rms. This is when I used SGP and PHD2.

With indi - I have a PI with Stellarmate installed. All hardware is connected to the pi. (lots of devices are connected to a quality powered 3.0 HUB on the mount that has never been a problem. (yet).
The mount however I run directly to the pi with its own cable. (guide camera is through hub).
I am using USB connection to GTO4. I also tried ST4 (which seemed to work better for calibration but didn't guide well. (over 1.2 tot rms and all over the place).

Driver is AP experimental (likely latest) as I always update.

Currently a new ASI290 mini (but I had exact same issue with the lodestar SX ) I will probably change back to. I am using the ZWO CCD driver with the mini, but I use the lodestar SX driver with that guide camera.

With everything connected to the PI. I then connect to it from my windows desktop. (wifi) through mesh router. (win 10)

And perhaps you could list your imaging gear in your signature as most of us do so it is easy to see that.

Will do.

So curious... I'm checking the log. I see during calibration the steps say move N 500# does this 4 times, E and S and all that - but near the end
it says SIMULATED pulse? for 1000? (HAULTED) which is probably me clicking STOP because it likely started jumping across the sky?

[2019-04-23T23:05:32.874 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[DEBUG] GuideSouth using simulated pulse for duration 1000 "
[2019-04-23T23:05:32.882 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[DEBUG] selectAPMoveToRate: Setting move to rate to GUIDE "
[2019-04-23T23:05:32.890 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] CMD <#:RG#> "
[2019-04-23T23:05:32.899 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] <MoveTo> "
[2019-04-23T23:05:32.907 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] CMD <:Ms#> "
[2019-04-23T23:05:32.979 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[DEBUG] Moving toward South. "
[2019-04-23T23:05:33.174 Eastern Daylight Time DEBG ][ org.kde.kstars.ekos.guide] - Capturing frame...
[2019-04-23T23:05:33.194 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] CMD <:GR#> "
[2019-04-23T23:05:33.208 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] CMD <m> "
[2019-04-23T23:05:33.215 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] RES <M 0> "
[2019-04-23T23:05:33.249 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] CMD <q> "
[2019-04-23T23:05:33.258 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] RES <Q 232.7> "
[2019-04-23T23:05:33.267 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] CMD <z> "
[2019-04-23T23:05:33.277 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] RES <Z 0> "
[2019-04-23T23:05:33.290 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] CMD <k> "
[2019-04-23T23:05:33.300 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] RES <K 1269 1272 0> "
[2019-04-23T23:05:33.350 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] CMD <o> "
[2019-04-23T23:05:33.389 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] RES <12:23:10.4> "
[2019-04-23T23:05:33.397 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] VAL [12.3862] "
[2019-04-23T23:05:33.405 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] CMD <:GD#> "
[2019-04-23T23:05:33.439 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] RES <O 0.69> "
[2019-04-23T23:05:33.448 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] CMD <u> "
[2019-04-23T23:05:33.480 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] RES <U 1 1> "
[2019-04-23T23:05:33.524 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] CMD <b> "
[2019-04-23T23:05:33.554 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] RES <B 90.00> "
[2019-04-23T23:05:33.561 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] RES <+27*22:21> "
[2019-04-23T23:05:33.569 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] VAL [27.3725] "
[2019-04-23T23:05:33.584 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[DEBUG] CMD: <:pS#> "
[2019-04-23T23:05:33.596 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] Snooped RA-DEC: 12.386222222222221134 "
[2019-04-23T23:05:33.606 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] Snooped RA-DEC: 27.372499999999998721 "
[2019-04-23T23:05:33.623 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] Snooped RA: 185.793 - DEC: 27.3725 "
[2019-04-23T23:05:33.692 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[DEBUG] RES: <West> "
[2019-04-23T23:05:33.730 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[DEBUG] AstroPhysicsGuideTimeoutNS() pulse guide simul = 1 "
[2019-04-23T23:05:33.738 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] <HaltMovement> "
[2019-04-23T23:05:33.784 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] CMD <:Qs#> "
[2019-04-23T23:05:33.794 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[DEBUG] Movement toward South halted. "

File Attachment:

File Name: log_23-01-55.zip
File Size:82 KB

File Attachment:

File Name: log_23-08-24.zip
File Size:193 KB
AP Mach1 / CP4 APCC & PEMpro.
EXP SCI - ED152cf APO - Celestron 11" RASA - Stellarvue 80mm
Baader F2 HS NB filters, Lodestar X2 guide camera / OAG - ZWO 290mm mini
ZWO ASI1600MM Pro / ASI174M (solar) / ASI094MC
NEXDome, CLoudwatcher, AVX mount/ASIair and Stellarmate

2 months 6 hours ago #38362
Attachments:

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

  • Posts: 326
  • Thank you received: 50

Replied by Ron Kramer on topic guide module (internal)

Driver Info

AstroPhysics Experimental
indi_lx200ap_experimental
vers 2.0
interface 5
AP Mach1 / CP4 APCC & PEMpro.
EXP SCI - ED152cf APO - Celestron 11" RASA - Stellarvue 80mm
Baader F2 HS NB filters, Lodestar X2 guide camera / OAG - ZWO 290mm mini
ZWO ASI1600MM Pro / ASI174M (solar) / ASI094MC
NEXDome, CLoudwatcher, AVX mount/ASIair and Stellarmate

2 months 6 hours ago #38364

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

  • Posts: 326
  • Thank you received: 50

Replied by Ron Kramer on topic guide module (internal)

those error logs of any help to those that know what it means? I tried 900 and acted pretty much the same as before. I went to 999 and same. I'll go back to 900 and hope it works. SKIES CLOUDY AND RAINING A LOT LATELY. = ( I wish we could guide during the day. (to work out issues).

A CAP THAT CHANGES THE SUN TO A SINGLE POINT? ;-)

Why do I see simul... and simulated pulse. (1000) I tested at 900 and 999?


ODDLY in the 2nd log - I don't see any guiding commands past the initial boot up? I just have tried to calibrate 16 times!? does it appear under something other that 'guide' or 'guiding'? no nudge of pulse either?

Looking in the first attached file I see more guiding. Simul=0 I suspect means simulator "off". I believe mN is move North - I'm trying to track through the log for calibration. I'll go back to it.
AP Mach1 / CP4 APCC & PEMpro.
EXP SCI - ED152cf APO - Celestron 11" RASA - Stellarvue 80mm
Baader F2 HS NB filters, Lodestar X2 guide camera / OAG - ZWO 290mm mini
ZWO ASI1600MM Pro / ASI174M (solar) / ASI094MC
NEXDome, CLoudwatcher, AVX mount/ASIair and Stellarmate

Last edit: 1 month 3 weeks ago by Ron Kramer.
1 month 3 weeks ago #38628

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

  • Posts: 326
  • Thank you received: 50

Replied by Ron Kramer on topic guide module (internal)

[2019-04-23T23:05:32.874 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[DEBUG] GuideSouth using simulated pulse for duration 1000 "
[2019-04-23T23:05:32.882 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[DEBUG] selectAPMoveToRate: Setting move to rate to GUIDE "
[2019-04-23T23:05:32.890 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] CMD <#:RG#> "
[2019-04-23T23:05:32.899 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] <MoveTo> "
[2019-04-23T23:05:32.907 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] CMD <:Ms#> "
[2019-04-23T23:05:32.979 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[DEBUG] Moving toward South. "
[2019-04-23T23:05:33.174 Eastern Daylight Time DEBG ][ org.kde.kstars.ekos.guide] - Capturing frame...
[2019-04-23T23:05:33.194 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] CMD <:GR#> "

Trying to learn the logs... why a simulated pulse of 1000? (simulated?) and I have max pulse set to 900. ?

Changed rate to guide rate ok. (It's pulling this from settings I have set?) not shown in the log?

Ms - move south... but Isn't there suppose to be an amount? Ms# (how much?)

Moving toward south? (how much?) ? Indefinite until halted?

LATER I see...

[2019-04-23T23:05:33.389 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] RES <12:23:10.4> "
[2019-04-23T23:05:33.397 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] VAL [12.3862] "
[2019-04-23T23:05:33.405 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] CMD <:GD#> "
[2019-04-23T23:05:33.439 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] RES <O 0.69> "
[2019-04-23T23:05:33.448 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] CMD <u> "
[2019-04-23T23:05:33.480 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] RES <U 1 1> "
[2019-04-23T23:05:33.524 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] CMD <b> "
[2019-04-23T23:05:33.554 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] RES <B 90.00> "
[2019-04-23T23:05:33.561 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] RES <+27*22:21> "
[2019-04-23T23:05:33.569 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] VAL [27.3725] "
[2019-04-23T23:05:33.584 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[DEBUG] CMD: <:pS#> "
[2019-04-23T23:05:33.596 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] Snooped RA-DEC: 12.386222222222221134 "
[2019-04-23T23:05:33.606 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] Snooped RA-DEC: 27.372499999999998721 "
[2019-04-23T23:05:33.623 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - NexDome : "[DEBUG] Snooped RA: 185.793 - DEC: 27.3725 "
[2019-04-23T23:05:33.692 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[DEBUG] RES: <West> "
....................
[2019-04-23T23:05:33.730 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[DEBUG] AstroPhysicsGuideTimeoutNS() pulse guide simul = 1 "
[2019-04-23T23:05:33.738 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] <HaltMovement> "
[2019-04-23T23:05:33.784 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] CMD <:Qs#> "
[2019-04-23T23:05:33.794 Eastern Daylight Time DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[DEBUG] Movement toward South halted. "

Simul=1? (yes?) it was = 0 (off?)
Qs ? (quit movement south?)



With the command set I got from AP - can the code specify the amount to move? (moving until halt) seems - imprecise to say the least?

This browser does not support PDFs. Please download the PDF to view it: Download PDF

AP Mach1 / CP4 APCC & PEMpro.
EXP SCI - ED152cf APO - Celestron 11" RASA - Stellarvue 80mm
Baader F2 HS NB filters, Lodestar X2 guide camera / OAG - ZWO 290mm mini
ZWO ASI1600MM Pro / ASI174M (solar) / ASI094MC
NEXDome, CLoudwatcher, AVX mount/ASIair and Stellarmate

Last edit: 1 month 3 weeks ago by Ron Kramer.
1 month 3 weeks ago #38629
Attachments:

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

  • Posts: 82
  • Thank you received: 13

Replied by wotalota on topic guide module (internal)

Not that I can answer your questions, but I did look at the logs when you posted them, mainly to see if you were getting the calibration error I was last time I imaged. You were not, and calibration when pulse guiding appeared to succeed for you.

The way I understand the maximum pulse business is that its use has a limit of ~999ms. When the amount of needed correction exceeds that amount an alternative approach is needed. That is when the move command is used instead, but I don't think it is imprecise as these things go. The movement's progress is monitored and stopped when the needed correction has been reached.
When I experienced the bug, the problem was the movement was not being stopped and the mount continued to move until it crashed or was manually stopped. As previously stated that is no longer a problem and the bug was fixed some time ago.

I thought perhaps the "simulated" phrase you referred to was with this use of the move command.
It might be but there seem to be additional cases. There seems to be a "Timeout" of some kind related, and also the 0 value instances. I don't know if these indicate some kind of issue or are just diagnostic logging information.

Something that does stand out is the high values of the guide correction pulses in the file, often up at the 900 limit, indicating the wild swings you describe.
Mach1, ES80 x0.8, ASI071, ASI120 OAG, focusPro
1 month 3 weeks ago #38633

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

Time to create page: 0.296 seconds