cl330b replied to the topic 'EQ6R-Pro & Indi' in the forum. 3 months ago

Hello Lead_weight,

Did you purchase this mount? If so, were you able to find a suitable driver? I am also considering purchasing this mount. Thanks.

Kindly
cl330b

Read More...

cl330b replied to the topic 'iOptron SmartEQ pro-Error setting local date/UTC Offset.' in the forum. 6 months ago

I am interested but could only work on it sporadically at this point.

cl330b

Read More...

cl330b replied to the topic 'iOptron SmartEQ pro-Error setting local date/UTC Offset.' in the forum. 6 months ago

knro wrote: I'm writing a new driver for firmware version 20170101 or higher, including CEM120. So update your firmware to this or later and use the new driver once released.
Also, I really need the documentation part.


Please see link below. Hope the link works, I'm posting from my mobile device. please let me know if I can answer any questions.

Docs

Read More...

cl330b replied to the topic 'iOptron SmartEQ pro-Error setting local date/UTC Offset.' in the forum. 6 months ago

The guide rate command response is different for a CEM60 with a firmware version of 20171001 and later. This explains the issue El Corazon is facing. For CEM60 the response should be:

Command: “:AG#”
Response: “nnnn#”
This command gets the right ascension guiding rate and the declination guiding rate.
The first 2 “nn” stands for the right ascension guiding rate 0.nn * sidereal rate. The last 2 “nn” stands 
for the declination guiding rate 0.nn * sidereal rate.
Note: Valid range of guiding rate of right ascension is [0.01, 0.90] * sidereal rate, and valid
range of guiding rate of declination is [0.10, 0.99] * sidereal rate. This command only available 
in equatorial mounts.

I will provide logs as soon as I can. I also have figured out the SmartEQ Pro (original post) issue. There is a third product, the SmartEQ Pro+. This product uses the same command set as the CEM60, but does not share the same command set as the SmartEQ, nor the SmartEQ Pro. I can link to references shortly...

Kindly
cl330b

Read More...

cl330b replied to the topic 'iOptron SmartEQ pro-Error setting local date/UTC Offset.' in the forum. 7 months ago

I am currently in communications with ioptron support regarding this topic. The command set syntax can vary per mount even if each mount has an 8408 HC. They directed me to a link with command sets for their mounts and this raised further questions. I will provide any further useful information supplied to me. I will also try my best to provide screenshots as soon as I can.

Read More...

cl330b replied to the topic 'iOptron SmartEQ pro-Error setting local date/UTC Offset.' in the forum. 7 months ago

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

Read More...

cl330b replied to the topic 'iOptron SmartEQ pro-Error setting local date/UTC Offset.' in the forum. 7 months ago

knro wrote: So is the issue with the current SmartEQ driver just the date/time settings? or there are other problems?


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

Read More...

cl330b replied to the topic 'iOptron SmartEQ pro-Error setting local date/UTC Offset.' in the forum. 7 months ago

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.

Kindly,
cl330b

Read More...

cl330b replied to the topic 'iOptron SmartEQ pro-Error setting local date/UTC Offset.' in the forum. 7 months ago

Hello knro,

I found in my testing that the issue is formatting of the time/date. For example, I receive a response of "1" when I send command

:SCYYMMDD#
to the mount, which is the proper response. There is no response when I send
:SC 03/04/18#
.

Here is the output of my serial session:
:V#
v1.00#
:MountInfo#
0011
:SC180306#
1
:FW1#
170518170518#
:FW2#
161028161028#

I was able to locate an iOptron® Mount RS-232 Command Language document from 2014. It doesn't apply to the iOptron SmartEQ/pro, but the command format is correct. All commands I tested (which wasn't all of them) provided the proper response from the mount and the changes were reflected on the HC. I'm certain you are familiar with this document so I haven't included it.

I host my own Gitlab server so I am familiar with git, I would offer to make the changes myself but have limited time right now. I would however LOVE to contribute in the near future. Is there any other info I can provide at this time?

Thank you kindly,
cl330b

Read More...

cl330b created a new topic ' lx200_zeq25-Error setting local date/Error setting UTC Offset' in the forum. 7 months ago

Good afternoon,

Details:
iOptron SmartEQ Pro (Go2Nova 8408).
gpsd: 3.15 (revision 3.15-2build1).
Ubuntu 16.04 LTS (Kernel 4.13.0-36-generic).
Kstars Version 2.9.3
indi version 1.6.0
ekos version ??

I am running into an issue with setting the time and date on the HC using ekos and GPSD. GPSD is functioning properly in ekos which is great. I have built a GPS reciever using the MTK3339 chipset. I have used this chipset in other projects and have had no issues with it. In my case here, i can say with a great level of confidence that the GPS is functioning properly.

The trouble I am having is that when I connect to the mount in ekos, the time and date on the HC change to "2096-29-04 00:01:00". The functionality of the mount appers to be working properly, I can slew, etc. I have briefly visited indi's github page in an attempt to troubleshoot the issue myself because I believe the issue may only a simple time/date format issue. At least upon initial thoughts on the matter. I have been attempting to find a mount driver that updates the HC time/date properly but have been unable (including the iOptron SmartEQ, the GotoNova 8400 kit, and the lx200_zeq). I have visited the indi Github page in an attempt to diff a working driver but have this issue no matter what I select for the mount.

My first question is: Has anyone else run into this issue with the iOptron Smarteq Pro with 8408 HC? I believe the only difference between the SmartEQ and the Pro is the material the internal gears are manufactured with (metal vs. plastic). I may however be incorrect on this point as well.

Second question: Is the lx200_zeq the proper selection? Based on a post I read a while back, I have been led to believe that several selections are the same, if not, very similar.

Attached is a log file I dumped earlier today in an attempt to resolve the issue on my own. I am hoping for a nudge in the right direction. Any suggestions are appreciated. Thank you in advance.

Kindly,
cl330b

My background (if it matters):
Electronic Engineering background, long time devout Linux enthusiast, c programming experience, over 20 years of hands on electronics experience, currently I install and troubleshoot elevators.

Read More...

Login



3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!