Internal Guider not calibrating
geehalel wrote: Hi,
I looked at the log and considered a guide pulse (line 38858) 1000ms@0,5x):
- it starts at 22:20:50:556, and the actual track speed modification occurs at 22:20:50:656. There is a 47ms delay between the two first log messages, 0ms between all the others, but the last, with a 53ms delay which may be due to the real serial comm occuring here.
- the end of the pulse occurs at 22:20:51:715 (line 38897) after the end of a mount probe started at 22:20:51:372, The actual speed modification occurs at 22:20:51:832.
I have thought serial comm could be the problem but in the first part, a ':f1' serial command gets its response in the same millisecond, but the same command in the second part took 50ms. I believe the timestamps in log messages are added by the indi framework and thus we see when they have been processed, not when they have been queued. Furthermore the indi-eqmod driver uses the timer callback mechanism of the indi framework too, that explains why they may be delayed by the normal mount probe processing. I think we have to look at the eventloop of the indi framework as the timer callbacks are managed with select timeouts. Anyway a first idea would be to delay the ReadscopeStatus callback while pulse guiding.
Now none of this happens when you use ST4 guiding, you could do that with your ASI120MM and your AZ-EQ5.
Actually now that I think about it, the logs are from KStars. So IDMessage(...) is being sent to KStars and then it is logged, this is not done inside INDI directly, so the timestamps could be off, but the delays appear consistent nevertheless.
Attached my log file. Would be great if problem can be resolved. If issue is on my side (e.g. mount), would be curious to know as well - if for instance "backlash" was an issue, I would not know what to do.
Thanks a lot as always for the terrific support! Helge
Select the ASI120 in the menu to use its ST4 port.
And try again using the default settings. That should work, I use the same setup
Anyway your last log file was almost empty.
Anyway, thanks for the feedback, and good to know better not to touch the backlash - do you think that could have been disturbing the calibration?
Quick question: is the calibration process affected the brightness of the stars, should the autostretch function be enabled?
Why should subframing be avoided?
Subframing shouldn't be used, binning 2x2 or higher, exposure time 1-2 seconds.
Raspbian Buster with AstroPi3 script configuration
Skywatcher HEQ5 Pro Mount
Canon 600D Camera
Orion SSAG/ASI120mm @280mm Guide Scope
Adafruit Motor Hat shield
Adafruit GPS Module
Generic Bluetooth Joystick.
Startech 7 port powered USB Hub.
1. under profile editor, guiding set to internal
2. Under Guide tab, choose via EQmod moun and bin to 2x2
3. under guide option page, follow my setting in attached photo if you wish to perform dithering.
4. Please remove ST4 cable!!!!!!!
Are you using USB to connect to the mount? I am doing that as well.
My personal experience was that BT is even more unreliable than Wifi connections but it could also be just delusion
HelgeMK wrote: Hm..does it mean that the BT connection is not good enough to support guiding?
pls excuse my bad english!