iOptronV3 - Track mode automatically changes to Lunar #1681

evripidis · 2022-06-26T21:48:33Z

Describe the bug
"indi_ioptronv3_telescope"

When you are connected to mount's internal wifi hotspot, the track mode automatically changes from Sidereal to Lunar. This doesn't occur when you are connected through hand controller.

Indilib thread: https://www.indilib.org/forum/ekos/11170-track-mode-automatically-changes-to-lunar.html

To Reproduce
Exact steps to reproduce the behavior.

Connect computer's wifi to mount's wifi hotspot
Start Kstars/Ekos and run the profile with the driver indi_ioptronv3_telescope as driver for the GEM28
Start session and after a few moments the a Timeout Error appears on the console and the track mode changes to Lunar.

Expected behavior
Not changing the track mode.

knro · 2022-06-27T07:54:41Z

Need mount logs to see what triggers this. Please attach the logs.

evripidis · 2022-06-28T17:11:31Z

Hello @knro ,

I'm gonna recheck it from scratch cause I just gave up 4 months ago when I started the thread on indilib. My bad, I should have reported directly here.

As far as I can understand the pasted text there is not any useful correct?

knro · 2022-06-28T17:38:06Z

I can't read it, it needs to be attached as a file. Mount logging must be enabled before logs are collected for that.

evripidis · 2022-06-28T17:48:48Z

@knro I've just tried it and after just slew to a random area the issue came up . I hope this file to be ok.
log_20-26-41.txt

evripidis · 2022-07-06T09:32:56Z

I can't read it, it needs to be attached as a file. Mount logging must be enabled before logs are collected for that.

@knro When you have time, please just confirm that is the correct log that you were looking for.

evripidis · 2022-07-20T22:32:07Z

@knro Any idea for this please?

knro · 2022-07-21T04:34:32Z

No debug tracking in there. You checked both INDI + Mount (under drivers)? If yes, go to iOptron --> Options and make sure all the debug checkboxes are on. Because the log does not show the verbose logs we need to diagnose this.

evripidis · 2022-07-23T21:58:47Z

@knro Finally I've managed to install indi & Kstars on a fresh unit and I can replicate the issue instantly. Here is the correct full log I think this time.

log_00-53-31.txt

PS. I can see into the log that says "mount movement, calibration" etc. The mount is not moving or slewing.

…event any character remaining on buffer that do not get cleared for some reason by the IO flush. This might help fix issues reported in #1681

knro · 2022-07-24T07:14:15Z

@evripidis Thank you that was helpful. Please try to update from latest INDI from Git and report back with the log (even if it works, upload the logs).

evripidis · 2022-07-29T21:06:52Z

@evripidis Thank you that was helpful. Please try to update from latest INDI from Git and report back with the log (even if it works, upload the logs).

@knro I do not know if this has to do with the wifi option, but after installing the latest version, (and trying to troubleshoot the Toupcam issue) my mount crashes. Logs here
log_23-42-14.txt

.

knro · 2022-07-29T21:41:07Z

After timeout apparently the mount starts sending the previous command response.. I added a workaround. Can you test? it needs to be compile from libindi master. If you confirm it fixes the issue, I'll publish an update to the package.

evripidis · 2022-07-30T05:46:33Z

After timeout apparently the mount starts sending the previous command response.. I added a workaround. Can you test? it needs to be compile from libindi master. If you confirm it fixes the issue, I'll publish an update to the package.

@knro Ok I could say I'm officially lost.. Tried to compile INDI, tried to install individually the required drivers and libraries and now, I can't load my profile cause says "Ekos requires at least on CCD or guider to operate".

I've tried to create a new profile and the toupcam drivers are not there... :-/ I see them libtoupcam into my Project folder but Ekos is not :-(

EDIT:

Maybe it would be better for me just to wait for a nightly (timeframe?) that will include this and follow that path.

evripidis · 2022-07-30T20:28:48Z

After many hours messing around and trying to fix duplicates, overrides, discontinuities etc. I had no luck... Thank fully I had TimeShfit on so it was quite easy to revert back.

@knro It would be great if you pass tho changed to the nightly so I could continue there the troubleshooting. Just give me a heads up. Until then, back to the cable :-(

knro · 2022-07-30T20:36:21Z

Is there a chance you can setup teamviewer? this would be much quicker.

evripidis · 2022-07-30T20:54:34Z

Is there a chance you can setup teamviewer? this would be much quicker.

Of course, no problem, any time!

knro · 2022-07-30T20:56:02Z

ok please send email to support@stellarmate.com with the login details (ID + Password) and make sure the mount is connected.

evripidis · 2022-07-30T21:05:24Z

ok please send email to support@stellarmate.com with the login details (ID + Password) and make sure the mount is connected.

Consider it done

evripidis · 2022-08-02T20:38:35Z

@knro Please take a look on this thread: https://www.indilib.org/forum/ekos/10122-meridian-flip-not-triggering.html?start=12#84944

Is it possible those changes above to trigger this issue in MF ?

evripidis · 2022-08-03T09:45:14Z

@knro Something is going on with the driver. I've created a new profile, only with the mount (connected with usb & HC) and CCD simulator and after a few minutes tracking I can see errors again and goes to idle.

knro · 2022-08-03T09:59:21Z

I see it. No commands given. It's either power issue or something wrong in the mount electronics/hardware. This is not a software issue.

evripidis · 2022-08-03T10:09:56Z

I see it. No commands given. It's either power issue or something wrong in the mount electronics/hardware. This is not a software issue.

Please ignore the previous log, it is not from a fresh profile. This is the correct one.

log_12-29-06.txt

knro · 2022-08-04T05:03:37Z

No differences.

evripidis · 2022-08-20T15:18:03Z

It seems that the latest changes resolved the issue

evripidis · 2022-10-15T09:51:43Z

Hello @knro

Any idea why is that back ?

log_21-02-01.txt

knro · 2022-10-15T11:58:41Z

From the logs:

[2022-10-07T21:36:03.885 EEST DEBG ][           org.kde.kstars.indi] - iOptron GEM28 : "[SCOPE] RES <+3240000004370577021> "
[2022-10-07T21:36:04.470 EEST DEBG ][           org.kde.kstars.indi] - iOptron GEM28 : "[DEBUG] CMD <:MH#> "
[2022-10-07T21:36:04.470 EEST DEBG ][           org.kde.kstars.indi] - iOptron GEM28 : "[DEBUG] RES <+> "
[2022-10-07T21:36:04.886 EEST DEBG ][           org.kde.kstars.indi] - iOptron GEM28 : "[DEBUG] CMD <:GLS#> "
[2022-10-07T21:36:04.886 EEST DEBG ][           org.kde.kstars.indi] - iOptron GEM28 : "[DEBUG] RES <0796500047022000010911> "
[2022-10-07T21:36:04.890 EEST INFO ][           org.kde.kstars.indi] - iOptron GEM28 :  "[ERROR] bool IOPv3::Driver::getStatus(IOPv3::IOPInfo*): Expected 23 bytes but received 22. "
[2022-10-07T21:36:04.890 EEST DEBG ][           org.kde.kstars.indi] - iOptron GEM28 : "[SCOPE] CMD <:GEP#> "
[2022-10-07T21:36:04.890 EEST DEBG ][           org.kde.kstars.indi] - iOptron GEM28 : "[SCOPE] RES <+3240000004370572521> "
[2022-10-07T21:36:05.888 EEST DEBG ][           org.kde.kstars.indi] - iOptron GEM28 : "[DEBUG] CMD <:GLS#> "
[2022-10-07T21:36:05.888 EEST DEBG ][           org.kde.kstars.indi] - iOptron GEM28 : "[DEBUG] RES <1+0796500047022000020911> "
[2022-10-07T21:36:05.894 EEST INFO ][           org.kde.kstars.indi] - iOptron GEM28 :  "[ERROR] bool IOPv3::Driver::getStatus(IOPv3::IOPInfo*): Expected 23 bytes but received 24. "
[2022-10-07T21:36:05.895 EEST DEBG ][           org.kde.kstars.indi] - iOptron GEM28 : "[SCOPE] CMD <:GEP#> "

You see it is issued Go home :MH and instead of responding by "1" as expected, we get "+" which is part of the :GLS response. and then the "1" is receipved later on. Maybe you can increase driver polling from 1000 to 2000 and see if this improves this.

evripidis · 2022-10-16T23:54:52Z

@knro It seemed to be promising at the begging but then I had this
(while actually the session was keep going).

[2022-10-16T22:44:48.795 EEST DEBG ][ org.kde.kstars.ekos.guide] - PHD2: request: "{\"id\":2490,\"jsonrpc\":\"2.0\",\"method\":\"get_lock_position\"}" [2022-10-16T22:44:48.828 EEST DEBG ][ org.kde.kstars.ekos.guide] - PHD2: response: "{\"jsonrpc\":\"2.0\",\"result\":[347.65,588.10],\"id\":2490}\r\n" [2022-10-16T22:44:49.297 EEST DEBG ][ org.kde.kstars.ekos.mount] - **Mount status changed from "Tracking" to "Error"** [2022-10-16T22:44:49.562 EEST DEBG ][ org.kde.kstars.indi] - iOptron GEM28 : "[DEBUG] CMD <:GLS#> " [2022-10-16T22:44:49.562 EEST DEBG ][ org.kde.kstars.indi] - iOptron GEM28 : "[DEBUG] RES <+1586568211268141001> " [2022-10-16T22:44:49.563 EEST INFO ][ org.kde.kstars.indi] - iOptron GEM28 : "[ERROR] bool IOPv3::Driver::getStatus(IOPv3::IOPInfo*): Expected 23 bytes but received 20. " [2022-10-16T22:44:49.563 EEST DEBG ][ org.kde.kstars.indi] - iOptron GEM28 : "[SCOPE] CMD <:GEP#> " [2022-10-16T22:44:49.615 EEST DEBG ][ org.kde.kstars.indi] - iOptron GEM28 : "[SCOPE] RES <+0796500047022000010811> " [2022-10-16T22:44:49.616 EEST INFO ][ org.kde.kstars.indi] - iOptron GEM28 : "[ERROR] bool IOPv3::Driver::getCoords(double*, double*, IOPv3::IOP_PIER_STATE*, IOPv3::IOP_CW_STATE*): Expected 20 bytes but received 23. " [2022-10-16T22:44:50.121 EEST DEBG ][ org.kde.kstars.indi] - iOptron GEM28 : "[DEBUG] CMD <:ZQ00026#> "

log_20-39-41.txt

evripidis · 2023-05-08T07:55:04Z

Hello @knro

I am facing again the same (?) error

log_13-46-15.txt

knro · 2023-05-30T10:33:57Z

I created a PR 1093 that needs to be tested. Please report back.

knro · 2023-05-31T06:10:19Z

@evripidis Were you able to test the PR? I cannot merge the PR without confirmation that it works over extended periods of time.

evripidis · 2023-05-31T07:23:40Z

@knro I didn't have much time, I've tried only with the hand controller connected, with no issue just like the last time. So I can verify that the issue appears only when the mount is connected via wifi.

Since the last time, I've changed my mini PC, so there is a different wifi chip.

Probably something has to do with mount's wifi ? With the code? At least there are no disconnections.

knro · 2023-05-31T07:25:42Z

So WiFi was problematic and you could not test WiFi connection with this PR yet, correct?

evripidis · 2023-05-31T08:27:05Z

No, wifi works fine. The mini PC (stellarmate) automatically connects to the mount's wifi hotspot with no dropped connections. I'm sure there is nothing wrong with mini PC's wifi chip, cause I've already tested it with two different models.

A few months ago I saw that I have no errors if I connect my mount to the mini PC via the Hand controller and USB cable.
While I connect it via the wifi, intermittently I got those errors.

So from my point of view - I am far more than an expert:

There is something with the mount's wifi chip, even if there are no dropped connections (poor quality, slow response on commands etc.)
Something in the code - don't have a clue on that.

(Yes, I didn't try this PR version yet.)

knro · 2023-06-01T04:31:52Z

Thanks, let me know when you have time to test the PR yet since I need confirmation is works OK without any regressions.

JulesArcher · 2023-09-26T14:33:20Z

Hi @knro I have also commented on #1903, but wanted to include @evripidis in the reply. As I mentioned, I am getting the same reported errors:
[2023-09-25T18:01:01.845 PDT INFO ][ org.kde.kstars.indi] - iOptron CEM26 : "[ERROR] Error setting RA/DEC. "
[2023-09-25T18:01:46.918 PDT INFO ][ org.kde.kstars.indi] - iOptron CEM26 : "[ERROR] bool IOPv3::Driver::getCoords(double*, double*, IOPv3::IOP_PIER_STATE*, IOPv3::IOP_CW_STATE*): Expected 20 bytes but received 23. "

I am no SW expert, so I would need a new indi_ioptronv3_telescope driver file with the fix to be able to test it on my system. Could you please send it to me? If so I will gladly test.

Thanks!

evripidis · 2024-01-14T07:55:15Z

Hi @knro I have also commented on #1903, but wanted to include @evripidis in the reply. As I mentioned, I am getting the same reported errors: [2023-09-25T18:01:01.845 PDT INFO ][ org.kde.kstars.indi] - iOptron CEM26 : "[ERROR] Error setting RA/DEC. " [2023-09-25T18:01:46.918 PDT INFO ][ org.kde.kstars.indi] - iOptron CEM26 : "[ERROR] bool IOPv3::Driver::getCoords(double*, double*, IOPv3::IOP_PIER_STATE*, IOPv3::IOP_CW_STATE*): Expected 20 bytes but received 23. "

I am no SW expert, so I would need a new indi_ioptronv3_telescope driver file with the fix to be able to test it on my system. Could you please send it to me? If so I will gladly test.

Thanks!

I was connecting my mount to Stellarmate's wifi hotspot.

Now after this thread https://indilib.org/forum/ekos/14026-has-anyone-controlled-an-ioptron-mount-over-wifi-from-ekos.html I had the idea to connect my mount directly to my home wifi. That it was a success but the issue remains.

github-actions · 2024-04-07T02:05:47Z

This issue has been inactive for 60 days and is being marked as stale.

github-actions · 2024-04-14T03:08:01Z

This issue has been closed due to inactivity.

evripidis added the bug label Jun 26, 2022

knro added a commit that referenced this issue Jul 24, 2022

Add sendCommandOK to ensure we get the proper response back and to pr…

f3b9ca5

…event any character remaining on buffer that do not get cleared for some reason by the IO flush. This might help fix issues reported in #1681

evripidis closed this as completed Aug 20, 2022

evripidis reopened this Oct 15, 2022

evripidis closed this as completed Apr 10, 2023

evripidis reopened this May 8, 2023

knro added this to the 2.0.3 milestone May 31, 2023

github-actions bot added the Stale label Apr 7, 2024

github-actions bot closed this as completed Apr 14, 2024

iOptronV3 - Track mode automatically changes to Lunar #1681

iOptronV3 - Track mode automatically changes to Lunar #1681

Comments

evripidis commented Jun 26, 2022

knro commented Jun 27, 2022

evripidis commented Jun 28, 2022 • edited by knro Loading

knro commented Jun 28, 2022

evripidis commented Jun 28, 2022

evripidis commented Jul 6, 2022

evripidis commented Jul 20, 2022

knro commented Jul 21, 2022

evripidis commented Jul 23, 2022 • edited Loading

knro commented Jul 24, 2022

evripidis commented Jul 29, 2022

knro commented Jul 29, 2022

evripidis commented Jul 30, 2022 • edited Loading

evripidis commented Jul 30, 2022

knro commented Jul 30, 2022

evripidis commented Jul 30, 2022

knro commented Jul 30, 2022

evripidis commented Jul 30, 2022

evripidis commented Aug 2, 2022

evripidis commented Aug 3, 2022 • edited Loading

knro commented Aug 3, 2022

evripidis commented Aug 3, 2022

knro commented Aug 4, 2022

evripidis commented Aug 20, 2022

evripidis commented Oct 15, 2022

knro commented Oct 15, 2022

evripidis commented Oct 16, 2022

evripidis commented May 8, 2023

knro commented May 30, 2023

knro commented May 31, 2023

evripidis commented May 31, 2023

knro commented May 31, 2023

evripidis commented May 31, 2023

knro commented Jun 1, 2023

JulesArcher commented Sep 26, 2023

evripidis commented Jan 14, 2024

github-actions bot commented Apr 7, 2024

github-actions bot commented Apr 14, 2024

evripidis commented Jun 28, 2022 •

edited by knro

Loading

evripidis commented Jul 23, 2022 •

edited

Loading

evripidis commented Jul 30, 2022 •

edited

Loading

evripidis commented Aug 3, 2022 •

edited

Loading