Yes, I think it's a good idea to have the HC handy in case the mount gets confused.
I intend to use this mount mostly for travelling to dark sites - I will need it anyway to update the location.
Yes. I don't know what happened the first time I tried the meridian flip...
The second time it worked fine.
Also when I enabled the "simulate the pier side" option it made matters worse. I keep it OFF.
Continuing talking to myself...
Tonight, I am having a second night out with the mount.
Same thing - guides smoothly at 0.6-0.8"RMS total and then every 1-3 min RA spikes.
Out of curiosity I installed a counterweight (2kg). Luckily, I had a proper shaft and a weight.
Guess what? No more RA spikes/runaways!
That's with my smallish but very back heavy AT72 (ASI2600 and a filed-flattener).
I wanted to lighten my travel bag with this mount but it's not going to happen....
Guiding is really great at 0.6-1.0" RMS now.
Also, after the flip, the DEC guiding became worse but RA spikes disappeared.
The flip didn't go well.
It went under horizon.
When I parked after that - the position was off by 90dgrs in RA.
I guess, I had to have "simulate pier side" option enabled (without it the pier side was "unknown').
Next time I'll see if it helps.
Running it outside with everything attached.
Will have the flip in 15 min.
Guiding is good - below 1" RMS but even after tweaking I still have RA runaways every 1-3 minutes.
Those are just spikes which settle in 10-30 sec.
I guess it's OK but if someone knows how to get rid of them - please let me know.
For guiding I settled at:
Min/Max RA 120/12
Min/Max DEC 900/12
0.5s guiding interval.
Looks like I figured this mount out.
I am testing it outside for guiding right now.
Performed the PA routine. It worked nicely.
Control knobs of the mount are very smooth.
Guiding is good at around 1" RMS total (0.5 sec interval) with occasional RA runaways.
I had to adjust Min/Max parameters quite a bit (from what I am used to with HEQ5) for guiding to work.
Can someone please share good Control Parameters for the Internal Guider?
Will be much appreciated!
Is this still the case? I think - yes.
Any chance for a change?
knro post=49946 wrote: IIRC, you cannot set time/date on the mount from the command set so KStars plays no role in setting this.
I moved the cables around. All is well now.
It was a bad connection somewhere.
I am not sure what happened but the meridian flip used to work for me a few months ago.
Now, after the flip, RA ALWAYS goes in the wrong direction during calibration.
When stopped and restarted - all is well.
Now, the confusion starts.
- is it enough to connect the HC just once for a certain location to sync the GPS data?
- or I need to do this every session?
- is it save to disconnect the HC after GPS sync and proceed with Ekos?
- my concern is the Meridian Flip - if the HC is connected it will interfere with Ekos.
What is the workflow? Anyone?
OK. Figured this one out.
The hand-controller has to be connected to provide coordinates/date/time to Ekos.
Once I connected the HC, selected "Mount updates KStars", PA procedure went as it should
I got it today!
Connected to Stellarmate to test with the CCD Simulator.
Hand-controller is not connected.
Slewing to targets seem to go in right directions.
I tried to perform Polar Alignment - it was scary!
Slewed to Polaris and started the procedure.
Instead of going 30dgrs it went full 360 and wanted to go further but I stopped it.
I pressed Park (which I set to 0,270) - it went 360 in the other direction and parked successfully.
Location/date/time is set correctly in KStars
What could be wrong?
Tonight was more of the same but now it consistently did this during calibration:
-- RA forward and reverse - OK
-- DEC forward - OK
-- DEC reverse - goes for just one step and claims that the calibration is successful.
Guiding goes nowhere after this.
I again, booted/rebooted, connected/reconnected cables and finally it worked.
Can a flaky cable or a loose USB connector cause this?
If it's a cable/connector - why it only affects the DEC?
I've been using this setup/rig without any real problems (occasional meridian flip problems, making my new ASI2600MC to work correctly) for well over a year, maybe more.
Had several successful sessions around last New Moon.
Tonight, the Guide Module gave me a real headache.
It was really doing strange things during the calibration step.
-- didn't do anything but claimed that the calibration was successful.
-- would go RA forward for a couple of steps and claim that the calibration was successful.
-- would go RA forward and back but skip DEC and claim that the calibration was successful.
-- after that the guiding was atrocious
-- sometimes the Drift Plot wouldn't show anything at all even though the guider was (badly) guiding.
So, I kept doing and redoing the calibration, rebooting RPI, connecting/disconnecting cables and eventually the calibration went through
and now it guides quite reasonably.
What could be the cause for this?
My guess it's either the FTDI cable (quite new) to the mount or the mount itself (quite old HEQ5) or just a bad connection somewhere.
Using the latest stable INDI/KStars/Ekos. It was the same with Windows and RPI client.