×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

iOptron SmartEQ and ZEQ25GT connectivity problems.

  • Posts: 140
  • Thank you received: 9
They are definitely different versions of firmware yes.

Go2Nova 8408 hand controller firmware (V150302)

That is the latest version avalable for the ZEQ25GT and SmartEQ. Prior to today, both were running 140219. I can check with iOptron to see if I can upgrade to a later code. I will gladly do so if that fixes this issue.
5 years 11 months ago #25035

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

Mount log is required. Did you check this here: indilib.org/devices/telescopes/ioptron.html ?
5 years 11 months ago #25036

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

  • Posts: 1119
  • Thank you received: 182

By all means, CHECK! Don't take my word for it. I am currently not able to verify the firmware version and I am recalling it from memory. I would hate messing up your HC because I might have had a senior moment.... :(
5 years 11 months ago #25037

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

  • Posts: 140
  • Thank you received: 9
I am not sure what you mean by mount log in this case. I went to the link and I do have the following firmwares:

ZEQ25 GT 8408 2013 V1.4 V150302,N/A,V150302
SmartEQ/SmartEQ Pro 8408 2013 V1.4 V150302,N/A,N/A
5 years 11 months ago #25038

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

  • Posts: 140
  • Thank you received: 9
In case you were wanting logs from the ekos menu.....

2018-04-12T21:37:39: [ERROR] Timeout error
2018-04-12T21:37:34: [ERROR] Failed to set longitude.
2018-04-12T21:37:34: [ERROR] Timeout error
2018-04-12T21:37:29: [INFO] Time and date updated.
2018-04-12T21:37:28: [INFO] Device configuration saved.
2018-04-12T21:37:28: [INFO] Saving device configuration...
2018-04-12T21:37:28: [INFO] Device configuration applied.
2018-04-12T21:37:28: [ERROR] Timeout error
2018-04-12T21:37:23: [ERROR] Failed to set longitude.
2018-04-12T21:37:23: [ERROR] Timeout error
2018-04-12T21:37:18: [INFO] Loading device configuration...
2018-04-12T21:37:18: [INFO] Mount is unparked.
2018-04-12T21:37:18: [INFO] Mount UTC offset is 0.20. UTC time is 1999-12-30T23:48:00
2018-04-12T21:37:18: [INFO] iOptron SmartEQ is online.

After that, just sitting there idling at home position yields these constantly:
2018-04-12T21:40:21: [ERROR] Only received #10 bytes, expected 7.
2018-04-12T21:40:20: [ERROR] Timeout error
2018-04-12T21:40:15: [ERROR] Only received #10 bytes, expected 7.
2018-04-12T21:40:14: [ERROR] Timeout error
2018-04-12T21:40:09: [ERROR] Only received #10 bytes, expected 7.
2018-04-12T21:40:08: [ERROR] Timeout error
2018-04-12T21:40:03: [ERROR] Only received #10 bytes, expected 7.
2018-04-12T21:40:01: [ERROR] Timeout error
5 years 11 months ago #25039

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

  • Posts: 1119
  • Thank you received: 182


What I wrote earlier may not be relevant for your SmartEQ Pro, as it was based on my experience with my SmartEQ Pro+. The website for which Jasem posted the link shows what I wrote, i.e. both mounts use the same HC, but require different firmware. Therefore, the CEM60 driver, which I found works for the most part with my Pro+ may not at all work for your SmartEQ/Pro mount.
5 years 11 months ago #25041

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

  • Posts: 140
  • Thank you received: 9
I am not sure if this helps or not, but it seems that the driver is unable to set longitude from the SmartEQ. I haven't confirmed this with the ZEQ25 but suspect that will be the case there too.

2018-04-13T01:10:23: [ERROR] Only received #10 bytes, expected 7.
2018-04-13T01:10:22: [ERROR] Timeout error
2018-04-13T01:10:17: [ERROR] Only received #10 bytes, expected 7.
2018-04-13T01:10:17: [ERROR] Failed to set longitude.
2018-04-13T01:10:17: [ERROR] Timeout error
2018-04-13T01:10:12: [INFO] Time and date updated.
2018-04-13T01:10:11: [INFO] Device configuration saved.
2018-04-13T01:10:11: [INFO] Saving device configuration...
2018-04-13T01:10:11: [ERROR] Timeout error
2018-04-13T01:10:06: [ERROR] Only received #10 bytes, expected 7.
2018-04-13T01:10:05: [INFO] Device configuration applied.
2018-04-13T01:10:05: [ERROR] Failed to set longitude.
2018-04-13T01:10:05: [ERROR] Timeout error
2018-04-13T01:10:00: [INFO] Loading device configuration...
2018-04-13T01:10:00: [INFO] Mount is unparked.
2018-04-13T01:10:00: [INFO] Mount UTC offset is 0.37. UTC time is 2000-07-30T23:37:59
2018-04-13T01:10:00: [INFO] iOptron SmartEQ is online.
Last edit: 5 years 11 months ago by John S..
5 years 11 months ago #25045

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

  • Posts: 140
  • Thank you received: 9
Jasem,

I apologize. I have never had to do debug logging in kstars before. I turned on verbose logging, connected and slewed to M42 and back to home. I then disconnected. I saw quite a few errors in the status window, but it did complete the slews.
5 years 11 months ago #25046
Attachments:

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

From log it seems to have problems to CMD (:GEC#), however, the log still misses important info that were acquired during mount initialization. Can you please restart KStars and then try to connect to your mount, slew to any object, and then post it back?
5 years 11 months ago #25051

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

  • Posts: 140
  • Thank you received: 9
I can do that. Is there some additional logging other than mount logging you would like?
5 years 11 months ago #25055

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

  • Posts: 140
  • Thank you received: 9
Jasem,

Here is the log file. I noticed it failed to slew to NGC869 when I tried several times. That object is circumpolar and I am not sure why it failed to slew to it. I went to M74 and back to home position. It did corkscrew my mount pretty badly when I went to M74 and I would have almost certainly had an OTA/Mount crash if I had an OTA on it. I wasn't paying attention to where it was in the sky. I just wanted to slew to an object for the log data. I can try these same tests and logs on my ZEQ25 if you think it will help isolate this. They are exhibiting the same behavior so I suspect it's the same issue. To be clear, the mount does ultimately respond, but it seems to have difficulty communicating with it. I suspect if I were guiding it would be problematic, but it seems to work through it for slewing. Plate solving sometimes would abort as well due to the communication issue.
5 years 11 months ago #25056
Attachments:

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

  • Posts: 1119
  • Thank you received: 182
Perhaps a problem with your USB>Serial connector? I have one that also fails to communicate and another one that works fine.
This one works for me. Key to getting it to work was to use the Prolific driver.
www.amazon.com/Sabrent-Converter-Prolifi...=usb+to+serial+cable
5 years 11 months ago #25082

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

Time to create page: 0.420 seconds