Back again with my calibration issue.
Now calibration always fails.
I have upgraded the CEM60 with latest firmwares. All works fine apart in Ekos for calibration.
The calibration works very fine in PHD2 and I am obliged to use it for autoguiding.
I don't understand what the problem is. Looks like the guiding rates are sometimes taking into account sometimes not. Lately all the attempts to use it in Ekos failed.
Sound a very weird behaviour.
Read More...
I have a similar issue with my CEM60. I use KStars V3.6 and INDI V 1.9.7 on Raspberry Pi. The driver for the CEM60 is the one specific to the mount.
The calibration fail always.
Hopefully PHP2 works fine and ufffff I can shoot the stars. Otherwise that won't be possible.
The guiding rates are well defined in the mount via the handpad.
There is no track of the guiding rate values in the xml configure file of the CEM60.
So I wonder that those values are read from the mount if not there is no track of those values other than in tab of the mount.
I wonder that values of those guiding rates are either equal to zero either crushed by some memory leak.
The fact is that at the moment guiding with CEM60 and Ekos is not usable.
Read More...
Hello all,
Desperate by the issues I met with the Legacy driver I have done an upgrade of the firmware on the CEM60. I must admit that I was close to heart attack doing this process. I have done it on many devices but never on a mount. So I was afraid to brick my mount. Hopefully all went good. All seems to work fine and the guiding rates are same on handpad and in mount config.
Two nights ago I have done a session. For the calibration I still have to set the pulse to 4000 to have a significant displacement in RA (I was on Cephee Iris Nebula). That makes me doubtful. On the other hand the pulse value seems to be huge for calibration on DEC axle.
Whatever, the calibration went to finish. I haven't change any parameters on guiding process.
The guiding session have been ugly. In the past, before issues with Legacy driver I was guiding between -0.25 to 0.25 arc sec RMS with low values of plus or minus 0.11 arc second RMS.
Now, the RMS values are pic to pic between -1.5 to 1.5 arc sec and RMS around plus or minus 0,75 arc sec.
Is there some advice concerning the guiding parameters that you can give me to improve the guiding process ?
Read More...
Trying to fix the problem introducing those lines in the xml relative to ioptron legacy files under ~/.indi.
without any success. Looks like guiding rates are dead parameters. Whatever I do to fix the problem, I fail.
Damn I give up as I can't do anything to fix it.
<newNumberVector device='iOptron iEQ Legacy' name='GUIDE_RATE'>
<oneNumber name='GUIDE_RATE_WE'>
0.4000000000000000222
</oneNumber>
<oneNumber name='GUIDE_RATE_NS'>
0.5
</oneNumber>
</newNumberVector>
Read More...
I opened a new topic because the calibration issue I met is not fixed. Seems that this is linked to weird phenomena taking in account and storing the guiding rates for the ioptron legacy.
For the moment I can't guide and my last session failed and I closed my telescope shelter for a while until I find a solution.
www.indilib.org/forum/mounts/12215-recur...acy-driver-ekos.html
Read More...
I browsed the xml config files under .indi folder and none store the guiding rate values. I wondered it would be possible to hardcode the values in the xml config file. But as the values are not named it is impossible. On the other hand, whatever the values I have entered in the tab motion control it seems to have no effect on calibration process.
<INDIDriver>
<newSwitchVector device="iOptron iEQ Legacy" name="DEBUG">
<oneSwitch name="ENABLE">
On
</oneSwitch>
<oneSwitch name="DISABLE">
Off
</oneSwitch>
</newSwitchVector>
<newNumberVector device="iOptron iEQ Legacy" name="POLLING_PERIOD">
<oneNumber name="PERIOD_MS">
1000
</oneNumber>
</newNumberVector>
<newSwitchVector device="iOptron iEQ Legacy" name="CONNECTION_MODE">
<oneSwitch name="CONNECTION_SERIAL">
On
</oneSwitch>
<oneSwitch name="CONNECTION_TCP">
Off
</oneSwitch>
</newSwitchVector>
<newTextVector device="iOptron iEQ Legacy" name="DEVICE_PORT">
<oneText name="PORT">
/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A105ZAWW-if00-port0
</oneText>
</newTextVector>
<newSwitchVector device="iOptron iEQ Legacy" name="DEVICE_BAUD_RATE">
<oneSwitch name="9600">
On
</oneSwitch>
<oneSwitch name="19200">
Off
</oneSwitch>
<oneSwitch name="38400">
Off
</oneSwitch>
<oneSwitch name="57600">
Off
</oneSwitch>
<oneSwitch name="115200">
Off
</oneSwitch>
<oneSwitch name="230400">
Off
</oneSwitch>
</newSwitchVector>
<newSwitchVector device="iOptron iEQ Legacy" name="DEVICE_AUTO_SEARCH">
<oneSwitch name="INDI_ENABLED">
Off
</oneSwitch>
<oneSwitch name="INDI_DISABLED">
On
</oneSwitch>
</newSwitchVector>
<newSwitchVector device="iOptron iEQ Legacy" name="DEBUG_LEVEL">
<oneSwitch name="DBG_ERROR">
On
</oneSwitch>
<oneSwitch name="DBG_WARNING">
On
</oneSwitch>
<oneSwitch name="DBG_SESSION">
On
</oneSwitch>
<oneSwitch name="DBG_DEBUG">
On
</oneSwitch>
<oneSwitch name="DBG_EXTRA_1">
On
</oneSwitch>
</newSwitchVector>
<newSwitchVector device="iOptron iEQ Legacy" name="LOGGING_LEVEL">
<oneSwitch name="LOG_ERROR">
On
</oneSwitch>
<oneSwitch name="LOG_WARNING">
On
</oneSwitch>
<oneSwitch name="LOG_SESSION">
On
</oneSwitch>
<oneSwitch name="LOG_DEBUG">
Off
</oneSwitch>
<oneSwitch name="LOG_EXTRA_1">
Off
</oneSwitch>
</newSwitchVector>
<newSwitchVector device="iOptron iEQ Legacy" name="LOG_OUTPUT">
<oneSwitch name="CLIENT_DEBUG">
On
</oneSwitch>
<oneSwitch name="FILE_DEBUG">
Off
</oneSwitch>
</newSwitchVector>
<newTextVector device="iOptron iEQ Legacy" name="ACTIVE_DEVICES">
<oneText name="ACTIVE_GPS">
GPS Simulator
</oneText>
<oneText name="ACTIVE_DOME">
Dome Simulator
</oneText>
</newTextVector>
<newSwitchVector device="iOptron iEQ Legacy" name="DOME_POLICY">
<oneSwitch name="DOME_IGNORED">
On
</oneSwitch>
<oneSwitch name="DOME_LOCKS">
Off
</oneSwitch>
</newSwitchVector>
<newNumberVector device="iOptron iEQ Legacy" name="GEOGRAPHIC_COORD">
<oneNumber name="LAT">
43.947777777777773167
</oneNumber>
<oneNumber name="LONG">
1.5691666666666665986
</oneNumber>
<oneNumber name="ELEV">
220
</oneNumber>
</newNumberVector>
<newSwitchVector device="iOptron iEQ Legacy" name="TELESCOPE_REVERSE_MOTION">
<oneSwitch name="REVERSE_NS">
Off
</oneSwitch>
<oneSwitch name="REVERSE_WE">
Off
</oneSwitch>
</newSwitchVector>
<newSwitchVector device="iOptron iEQ Legacy" name="TELESCOPE_SLEW_RATE">
<oneSwitch name="1x">
Off
</oneSwitch>
<oneSwitch name="2x">
Off
</oneSwitch>
<oneSwitch name="3x">
Off
</oneSwitch>
<oneSwitch name="4x">
Off
</oneSwitch>
<oneSwitch name="5x">
Off
</oneSwitch>
<oneSwitch name="6x">
Off
</oneSwitch>
<oneSwitch name="7x">
Off
</oneSwitch>
<oneSwitch name="8x">
Off
</oneSwitch>
<oneSwitch name="9x">
On
</oneSwitch>
</newSwitchVector>
<newSwitchVector device="iOptron iEQ Legacy" name="TELESCOPE_TRACK_MODE">
<oneSwitch name="TRACK_SIDEREAL">
On
</oneSwitch>
<oneSwitch name="TRACK_SOLAR">
Off
</oneSwitch>
<oneSwitch name="TRACK_LUNAR">
Off
</oneSwitch>
<oneSwitch name="TRACK_KING">
Off
</oneSwitch>
<oneSwitch name="TRACK_CUSTOM">
Off
</oneSwitch>
</newSwitchVector>
<newNumberVector device="iOptron iEQ Legacy" name="TELESCOPE_TRACK_RATE">
<oneNumber name="TRACK_RATE_RA">
15.04106717867020393
</oneNumber>
<oneNumber name="TRACK_RATE_DE">
0
</oneNumber>
</newNumberVector>
<newSwitchVector device="iOptron iEQ Legacy" name="USEJOYSTICK">
<oneSwitch name="ENABLE">
Off
</oneSwitch>
<oneSwitch name="DISABLE">
On
</oneSwitch>
</newSwitchVector>
<newTextVector device="iOptron iEQ Legacy" name="JOYSTICKSETTINGS">
<oneText name="MOTIONDIR">
JOYSTICK_1
</oneText>
<oneText name="MOTIONDIRNS">
AXIS_8
</oneText>
<oneText name="MOTIONDIRWE">
AXIS_7
</oneText>
<oneText name="SLEWPRESET">
JOYSTICK_2
</oneText>
<oneText name="SLEWPRESETUP">
BUTTON_5
</oneText>
<oneText name="SLEWPRESETDOWN">
BUTTON_6
</oneText>
<oneText name="ABORTBUTTON">
BUTTON_1
</oneText>
<oneText name="PARKBUTTON">
BUTTON_2
</oneText>
<oneText name="UNPARKBUTTON">
BUTTON_3
</oneText>
</newTextVector>
<newTextVector device="iOptron iEQ Legacy" name="SNOOP_JOYSTICK">
<oneText name="SNOOP_JOYSTICK_DEVICE">
Joystick
</oneText>
</newTextVector>
<newSwitchVector device="iOptron iEQ Legacy" name="MOTION_CONTROL_MODE">
<oneSwitch name="MOTION_CONTROL_MODE_JOYSTICK">
On
</oneSwitch>
<oneSwitch name="MOTION_CONTROL_MODE_AXES">
Off
</oneSwitch>
</newSwitchVector>
<newSwitchVector device="iOptron iEQ Legacy" name="JOYSTICK_LOCK_AXIS">
<oneSwitch name="LOCK_AXIS_1">
Off
</oneSwitch>
<oneSwitch name="LOCK_AXIS_2">
Off
</oneSwitch>
</newSwitchVector>
<newSwitchVector device="iOptron iEQ Legacy" name="SIMULATE_PIER_SIDE">
<oneSwitch name="SIMULATE_YES">
Off
</oneSwitch>
<oneSwitch name="SIMULATE_NO">
On
</oneSwitch>
</newSwitchVector>
</INDIDriver>
Read More...
Hello all,
I still have serious problems with guiding. And more precisely calibration.
The values of the guiding rate is not keep when saving options and I have a very ugly calibration process and a guiding session that is really bad.
I set the values to 0,5x on both axes with the handle pad. I set the same values in the tab mount of devices manager. Then saved the options.
Exited properly from Ekos, stopped indiserver and entered back to Kstars/Ekos and after having restarted indiserver and connected the mount I saw that the guiding rate are back to weird values of 0 on both axes.
As I said in a previous post calibration is robust and go to the end but with unexpected results.
If someone can tell me why the guiding rate values are not saved and used by the calibration process that would help a lot.
Regards
Read More...
Hello Astromuni,
I am not sure to be the right person to answer. Otherwise, in my opinion, HFR with Bahtinov might be of poor help.
Maybe some people using this function can answer in a better way.
Clear skies
Read More...
I meet a new problem. I must park my setup with tube located horizontally on est side and the counterweight bar horizontal too pointing western side.
When I move the mount to this position and want to set the parking position, Ekos return that the object is below horizon. My setup is on a fix pier since 4 months now. I didn't have the problem before last update. Do I make some mistake or is there something that has changed ?
Read More...
All worked fine. Calibration is perfect using 2500 pulse value and a 0,5x sidereal rate. The result is a RMS error od 0,5 arc seconds which means that the movements around the zero axle are greater than + or - 0,5s. I don't know if the instrument specification in the guiding tab is used by guiding process or only used to compute the error on main instrument level.
Read More...
You are right Peter.
1/ on the hand controller the values of guiding rate were 0.05 and 0.5.
2/ On the motion control tab the values (that were not in the set place values) were 0.01 and 0.10
In both cases the values ratio are the same.
I am using the Legacy driver. I didn't made a firmware update so I don't use a recent driver for CEM60. I am afraid of doing this because of the freeze risk. Maybe I will have to do it very soon.
Thank you Peter
Test will be done if the sky is with me.
Read More...
Before describing my problem let says that I have corrected 2 days ago the polar alignment and have now 14" polar alignment error on both axis.
New test last this night.
I selected as target Theta Aquilae close to the celestial equator to get a better pulse movement in RA.
Unfortunately, there is no more improvement. With 5000 as pulse the calibration process moves just a fraction of pixels in RA (on display) and/or does some erratic moves forward/backward in both X and Y. The spot doesn't come back to the origin before starting DEC process.
In autoguiding session the RMS error on RA is between 0,25" to 0,5". Two months ago, calibration process worked differently, my RMS error on RA was between 0,10" to 0,25".
I am not sure that the guiding correction is working while autoguiding.
I tested PHD2 using INDI server for mount and camera autoguider. The calibration always failed on "not enough move on East/West axle".
I am not sure this is a INDI problem, but the only change in 2 months is an update of INDI/Ekos/Kstars and my setup didn't change.
As the movements of the mount on both axles and tracking looks fine I don't understand what the problem is.
Another issue is that the mount parking position is lost between 2 sessions. But this is another problem.
Read More...
Peter, I calibrate every session , yesterday I was on Perseus double cluster.
Maybe I am wrong doing calibration each session.
Read More...
I have a problem that didn't occurs in previous versions of INDI
On my iOptron CEM60 the calibration on the RA axes barely moves the mount. I set the impulsion and the result is the same. And unfortunately the DE axes does larger movements due to this value that I set to 5000.
I wonder if :
1/ This is a problem with the mount that by accident appears at same time as the update of libindi.
2/ There is some issue on the impulse of the RA for this mount.
Seems that the consequence is that there is a very weird guiding with some periodic drift that is compensated by the algorithm afterwards (Proving that this algorithm is very robust.)
Read More...