×

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

Bi-monthly release with minor bug fixes and improvements

iOptron SmartEQ pro-Error setting local date/UTC Offset.

  • Posts: 205
  • Thank you received: 19
In case it helps: I was in contact with Ioptron support yesterday, asking about their support of ASCOM/INDI for their CEM120 range. The answer I got was that ASCOM was supported but not INDI, but they were willing to give the command set to a INDI developer. Has anyone tried reaching out to them for this type of documentation?
6 years 3 weeks ago #23924

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

Given the number of IOptron users using INDI drivers, maybe they should pressure iOptron for more support?
6 years 3 weeks ago #23925

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

  • Posts: 205
  • Thank you received: 19
I agree with you. If anyone reading this is in this category, I suggest sending an email to This email address is being protected from spambots. You need JavaScript enabled to view it. to politely request INDI support for your mount. While you are likely to get a response back similar to what I received, perhaps the volume of requests might sway their thinking to helping more.
The following user(s) said Thank You: Jasem Mutlaq, Derek, Jose Corazon
Last edit: 6 years 3 weeks ago by Chris Ryan.
6 years 3 weeks ago #23926

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

  • Posts: 30
  • Thank you received: 5
I will send them a request. Hopefully they will at the very least provide the rs232 command language document for the iOptron smarteq/pro mount.

On a side note, I tested the "cem60" driver, which is actually "indi_ieq_telescope" to the best of my knowledge. And I can say with certainty that the time, date, and coordinates are being updated properly on the HC 8408. I wasn't able to locate the source code for this driver in the indi repo though.

I will be able to perform more in-depth testing this weekend and provide knro a more detailed list of what is working and what is not. To directly answer your question though, another item I observed not working properly is the UTC Offset and local time. Formats below:
:SLHHMMSS# (local time) 
:SGsMMM# (UTC Offset. i.e. -480)

Both commands should return "1".


Kindly,
cl330b
Last edit: 6 years 3 weeks ago by cl330b. Reason: adding additional information
6 years 3 weeks ago #23931

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

So if you use indi_ieq_telescope driver with your mount, everything works? The driver is available here
6 years 2 weeks ago #24001

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

  • Posts: 1119
  • Thank you received: 182
I posted about a similar problem with my SmartEQ Pro before. I am just using the CEM60 driver, I can control the mount fine with that one for all practical purposes, except for parking. That needs to be done manually by telling the mount to go Home, not Park. Another problem is that if you try to change the guide tracking speed to 0.5 x sidereal, the mount will set it to 0.05 and all guiding will fall apart then. Otherwise, no problem. Just use the CEM60 driver.
6 years 2 weeks ago #24029

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

So is the issue with the current SmartEQ driver just the date/time settings? or there are other problems?
6 years 2 weeks ago #24041

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

  • Posts: 1119
  • Thank you received: 182

I can confirm the aberrant behavior re date setting under the iOptron SmartEQ driver. However, as far as I understand it, the iOptron drivers are not controlling the mount, they are programming and controlling the handset. I cannot directly connect the serial cable to the mount, only through the handset, and that is then being reprogrammed during startup by Ekos. So, the handset # is the critical piece of information which driver to use, not the mount. For the iOptron SmartEQs, at least those acquired during the last year, that seems to be #8408.
HC #8408 responds (almost) flawlessly to the iOptron CEM60 driver. No problem with date there, only two minor issues I found for which there are workarounds:
It is not possible to 'Park' the mount, i.e. it slews fine to the Home position, but remains in the Unparked state. Not a major issue as far as I am concerned.
The second concerns sidereal guiding rate. I already pointed that out a few weeks ago. See attached screenshot. The default set of the x sidereal guiding rate is 50.5, obviously way off. However, if you now set it to the proper value of 0.5 using the set button on the right, Indi Control Panel will show the rate as 0.5x, however, the handset will have been reprogrammed to 0.05x, so one power of 10 off, but in RA only, NOT in DEC.
Again, not a major problem for practical purposes, as long as one is aware of it and checks the guiding rate on the HC before starting the night session. Still, it would be nice if that could be fixed, others using iOptron mounts may not notice why their guiding is way off.
Jo
6 years 2 weeks ago #24061
Attachments:

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

  • Posts: 30
  • Thank you received: 5

The only issues I have observed so far are the local time, UTC offset and date settings. I have already posted the proper format for these three changes. I am waiting for an email from iOptron to see if I can obtain the rs232 command list. The correct serial command syntax for the three issues I have observed are below. This format returns "1" for the 8408 HC on all three commands. I don't know if knro plans to work on the ioptron smarteq/pro driver, or create another link to the indi_ieq_telescope for the smartEQ/pro HC. I am willing to continue to test the former until it is functioning properly.

Correct command syntax.
:SCYYMMDD# (date)
:SLHHMMSS# (local time) 
:SGsMMM# (UTC Offset. i.e. -480)

kindly,
cl330b
6 years 2 weeks ago #24087

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

Sorry there is so MUCH to follow up with I can't recall many details, so let's summarize this:
1. With iOptron SmartEQ, you can use the CEM60 driver if you connect directly to the mount bypassing the handset?
2. Parking: What remains in unparked state? The physical mount? or the INDI parked/unparked status? or both? Logs?
3. Ok the code is based on this: www.ioptron.com/v/ASCOM/RS-232_Command_Language2014_V2.0.pdf
Command: “:AG#”
Response: “nnn#”
This command returns the guiding rate n.nn * sidereal rate. The range of n.nn is [0.10, 0.90]

So if hand set guide rate was set to 0.5, then then command should return 050 which then divided by 100 = 0.5x. However, from what you describe above, it seems that was is returned is 505 / 100 = 50.5 which doesn't make sense. Even if divided by 1000 it's not right. Ok, enough speculation. Set it to 0.5 in the handset, then enable logging in INDI driver, and let's see what exactly the mount sends over. Maybe it should be 1000 instead of 100.
Last edit: 6 years 2 weeks ago by Jasem Mutlaq.
6 years 2 weeks ago #24094

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


This is command set for this driver: www.ioptron.us/ASCOM/RS-232_Command_language2013.pdf

It is the same command set for the current driver (indi_lx200_zeq25) that covers ZEQ25, iEQ30, iEQ45, and SmartEQ. There is a space in the commands you mentioned above in the documentation.
6 years 2 weeks ago #24095

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

  • Posts: 30
  • Thank you received: 5
That document isn't accurate. The 8408 HC with SmartEQ pro mount returns "0011". Please see this more updated document which shows the working command syntax for the 8408 HC and SmartEQ pro mount even though it is not listed in the text. The commands in the document from 2014 (V2. 0) are 100% confirmed working properly.

Kindly
cl330b
6 years 2 weeks ago #24103
Attachments:

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

Time to create page: 0.284 seconds