Hi All,

I've got a question.
Since I'm experimenting with Ekos on my RPI3 (still in my house), I was wondering if the mount option iEQ45 Pro is also suitable for the older mounts 2013 and later of the iEQ45?

I do have two of them, one with a 8406HC and one with 8407HC. I currently only use the 8407 (the other one is stored somewhere else). I can connect with ekos and can perform goto commands. I do notice that when I do manually movements I need to wait for a couple of seconds before moving again, else it won't move.

Is the iEQ45 Pro connection in Ekos ok? Or are their other specific drivers for 2013 and older mounts (8407 and 8406)?

Kind regards,

Chris.

Does this answer your question? indilib.org/devices/telescopes/ioptron.html

If not, then documentation needs to be updated.

Thanks for the info.
Under the ZEQ25/SmartEQ section I see the iEQ45 EQ/AA and under the section IEQPro/CEM60 I see iEQ45 Pro (Firmware 140807 and later)
iEQ45 Pro AA (Firmware 140807 and later).

The ZEQ25/SmartEQ section doesn't show firmware compatibility, should be nice to put it there, and I think this section should also display the 8407 and 8406 versions in combination with the 2013 and earlier models. But this I don't know .

In Ekos I can connect with iEQ45 Pro || SmartEQ || ZEQ25 || CEM60 || CEM25.
Both sections tell me to install lib-indi1. Is this installed by default? I performed the following commands by setting up the Pi:

sudo apt-add-repository ppa:mutlaqja/ppa
sudo apt-get update
sudo apt-get install indi-full
sudo apt-get install indi-full kstars-bleeding
sudo apt-get install kstars-bleeding-dbg indi-dbg

yes they are supported by default. I don't remember the specific really as I wrote the driver quite a while ago. Let us know if it works with your other mounts and then we can update the info. I can also grant you privileges to edit them as well.

So I need to test them all or just choose iEQ45Pro?
I can do that for sure and post the results. Finaly I can edit the info pages if you can give me the permissions.

Hi Jasem,

I tested my iEQ45 GTN with HC8407 with the following mount options (zeq25, smarteq, cem25, cem60 and ieq45 pro).

Actually none of them works perfect. It look likes the ieq45 Pro has some more functions that work. I started a small table with functions and what works or not per mountconnection, but noticed that writing down my first observations would be enough .

What I noticed is that all options (zeq25, smarteq, cem25, cem60 and ieq45 pro) can connect and perform goto commands.
The zeq25, smarteq, cem25, and cem60 do display the actual ra and dec values, the ieq45 pro does only display zeroes. Moving the mount with the manual move buttons only work with the ieq45 pro option. But after moving one time, it looks like it’s stopping from doing anything. I can hear the motor receives something but doesn’t do anything at the end. Waiting for a while sometimes helps and moving in a direction works again but it’s not stable.

Parking/unparking doesn’t work with one of the mount options.
But I noticed that in the first tab when connectin the mount with the ieq45 pro, the find home position does work. The hand controller displays “zero position” after it went to the home position. Not sure if a park command was sent or the actual “zo zero position”.

It look likes the iEQ45 Pro option is the best since this option can performs most of the commands.
I didn’t test the sync option yet. Uploading images in the solver tab gave me errors..

I’m sure a good mount option to connect with should be possible or maybe there is something I’m doing wrong.

I found this link sourceforge.net/p/indi/bugs/37/ in which you are talking about a real 8406 and 8407 driver..

Hope my mount can be supported.

Kind regards,
Chris.

Thanks Chris for the report. It would be great if you have some programming experience so you can dig in the code and change it & test it immediately to see what works and what doesn't. There are two very different protocols between these mounts, one uses the older LX200-like protocol while the newer mounts use IOptron's own protocol, the ieq45 pro uses the new protocol. When you connect your mount in Windows, what driver do you use? Can you use a general LX200 driver or something specific? For now, just concentrate on the ieq45 pro driver. Next some logs would be useful to find out what's going on. One problem at a time, let's find out why it's displaying zeros for you.

Thanks for your reply.
I do have programming experience. It's a while ago, but programmed in several languages (PHP, .NET VB&C#, objective-c etc.).
Where can I find the logs? Is there some realtime logging available?
I did installed indi-dbg.

Thnx,
Chris.

Hi Jasem.

Already found the logs .
Below the log until from starting indi till connecting the mount. I didn't send any command yet.
In windows I choose the ascom driver "iOptron Ascom driver for 2013 and earlier models".


2017-02-13T13:23:34.898 - DEBG - Welcome to KStars 2.7.3
2017-02-13T13:23:34.909 - DEBG - "Setting clock: UTC: ma feb. 13 12:23:34 2017 GMT JD: 2.457.798,02"
2017-02-13T13:23:34.934 - DEBG - KStars is started in paused state.
2017-02-13T13:23:34.935 - DEBG - "Setting clock: UTC: ma feb. 13 12:23:34 2017 GMT JD: 2.457.798,02"
2017-02-13T13:23:35.167 - DEBG - Opened the DSO Database. Ready!
2017-02-13T13:23:35.672 - DEBG - Opened the User DB. Ready.
2017-02-13T13:23:37.256 - DEBG - Processing "unnamedstars.dat" , HTMesh Level 3
2017-02-13T13:23:37.256 - DEBG - Sky Mesh Size: 512
2017-02-13T13:23:37.440 - DEBG - Loaded DSO catalog file: "unnamedstars.dat"
2017-02-13T13:23:37.442 - DEBG - Processing "deepstars.dat" , HTMesh Level 3
2017-02-13T13:23:37.442 - DEBG - Sky Mesh Size: 512
2017-02-13T13:23:37.443 - DEBG - Loaded DSO catalog file: "deepstars.dat"
2017-02-13T13:23:39.831 - WARN - "Star HD61421 not found."
2017-02-13T13:23:39.844 - WARN - "Star HD10700 not found."
2017-02-13T13:23:39.870 - WARN - "Star HD20794 not found."
2017-02-13T13:23:39.896 - WARN - "Star HD2151 not found."
2017-02-13T13:23:39.929 - WARN - "Star HD190248 not found."
2017-02-13T13:23:39.967 - WARN - "Star HD142860 not found."
2017-02-13T13:23:39.976 - WARN - "Star HD1581 not found."
2017-02-13T13:23:39.977 - WARN - "Star HD1581 not found."
2017-02-13T13:23:39.980 - WARN - "Star HD98230 not found."
2017-02-13T13:23:40.095 - DEBG - File opened: "/home/bergerpi/.local/share/kstars/ngcic.dat"
2017-02-13T13:23:40.096 - DEBG - Loading NGC/IC objects
2017-02-13T13:23:44.517 - DEBG - File opened: "/usr/share/kstars/asteroids.dat"
2017-02-13T13:23:45.933 - DEBG - File opened: "/usr/share/kstars/comets.dat"
2017-02-13T13:23:47.180 - DEBG - No WishList Saved yet
2017-02-13T13:23:49.607 - DEBG - Daylight Saving Time inactive
2017-02-13T13:23:49.608 - DEBG - Next Daylight Savings Time change (Local Time): "zo mrt. 26 02:00:00 2017 GMT"
2017-02-13T13:23:49.615 - DEBG - Next Daylight Savings Time change (UTC): "zo mrt. 26 01:00:00 2017 GMT"
2017-02-13T13:23:50.268 - DEBG - The current Date/Time is: "ma feb. 13 13:23:50 2017 GMT+0100"
2017-02-13T13:23:50.268 - DEBG - glibc >= 2.1 detected. Using GNU extension sincos()
2017-02-13T13:23:50.753 - WARN - "Object named NGC 235 not found"
2017-02-13T13:23:51.773 - WARN - "Object named NGC 526 not found"
2017-02-13T13:23:52.522 - WARN - "Object named NGC 651 not found"
2017-02-13T13:23:54.951 - WARN - "Object named NGC 3314 not found"
2017-02-13T13:23:55.771 - WARN - "Object named NGC 3690 not found"
2017-02-13T13:23:57.599 - WARN - "Object named NGC 6027 not found"
2017-02-13T13:23:59.972 - WARN - "Object named IC 1179 not found"
2017-02-13T13:24:01.985 - DEBG - "Setting clock: UTC: ma feb. 13 12:24:01 2017 GMT JD: 2.457.798,02"
2017-02-13T13:24:02.217 - DEBG - Daylight Saving Time inactive
2017-02-13T13:24:02.218 - DEBG - Next Daylight Savings Time change (Local Time): "zo mrt. 26 02:00:00 2017 GMT"
2017-02-13T13:24:02.218 - DEBG - Next Daylight Savings Time change (UTC): "zo mrt. 26 01:00:00 2017 GMT"
2017-02-13T13:24:02.219 - DEBG - Starting the timer
2017-02-13T13:24:07.883 - DEBG - Ekos: "Starting INDI services..."
2017-02-13T13:24:07.885 - DEBG - INDI: Starting local drivers...
2017-02-13T13:24:08.021 - DEBG - INDI: INDI Server started locally on port 7624
2017-02-13T13:24:08.023 - DEBG - INDIListener: Adding a new client manager to INDI listener..
2017-02-13T13:24:08.023 - DEBG - INDI: Connecting to local INDI server on port 7624 ...
2017-02-13T13:24:08.029 - DEBG - Connection to INDI server is successful
2017-02-13T13:24:08.030 - DEBG - Ekos: "INDI services started on port 7624. Please connect devices."
2017-02-13T13:24:08.058 - DEBG - Received new device iEQ45 Pro
2017-02-13T13:24:08.133 - DEBG - INDI Server: "2017-02-13T12:24:08: startup: /usr/bin/indiserver -v -p 7624 -m 100 -f /tmp/indififoc056f3f5 "
2017-02-13T13:24:08.133 - DEBG - INDI Server: "2017-02-13T12:24:08: listening to port 7624 on fd 3"
2017-02-13T13:24:08.133 - DEBG - INDI Server: "FIFO: start indi_ieq_telescope -n \"iEQ45 Pro\""
2017-02-13T13:24:08.134 - DEBG - INDI Server: "With name: iEQ45 Pro"
2017-02-13T13:24:08.134 - DEBG - INDI Server: "FIFO: Starting driver indi_ieq_telescope"
2017-02-13T13:24:08.134 - DEBG - INDI Server: "2017-02-13T12:24:08: Driver indi_ieq_telescope: pid=27379 rfd=4 wfd=7 efd=8"
2017-02-13T13:24:08.135 - DEBG - INDI Server: "FIFO: start indi_gphoto_ccd -n \"Canon DSLR\""
2017-02-13T13:24:08.135 - DEBG - INDI Server: "With name: Canon DSLR"
2017-02-13T13:24:08.136 - DEBG - INDI Server: "FIFO: Starting driver indi_gphoto_ccd"
2017-02-13T13:24:08.136 - DEBG - INDI Server: "2017-02-13T12:24:08: Driver indi_gphoto_ccd: pid=27381 rfd=5 wfd=10 efd=11"
2017-02-13T13:24:08.136 - DEBG - INDI Server: "FIFO: start indi_qhy_ccd"
2017-02-13T13:24:08.136 - DEBG - INDI Server: "FIFO: Starting driver indi_qhy_ccd"
2017-02-13T13:24:08.137 - DEBG - INDI Server: "2017-02-13T12:24:08: Driver indi_qhy_ccd: pid=27382 rfd=6 wfd=15 efd=16"
2017-02-13T13:24:08.137 - DEBG - INDI Server: "2017-02-13T12:24:08: Client 9: new arrival from 127.0.0.1:51346 - welcome!"
2017-02-13T13:24:08.137 - DEBG - INDI Server: "2017-02-13T12:24:08: Driver indi_ieq_telescope: snooping on GPS Simulator.GEOGRAPHIC_COORD"
2017-02-13T13:24:08.137 - DEBG - INDI Server: "2017-02-13T12:24:08: Driver indi_ieq_telescope: snooping on GPS Simulator.TIME_UTC"
2017-02-13T13:24:08.138 - DEBG - INDI Server: "2017-02-13T12:24:08: Driver indi_ieq_telescope: snooping on Dome Simulator.DOME_PARK"
2017-02-13T13:24:08.138 - DEBG - INDI Server: "2017-02-13T12:24:08: Driver indi_ieq_telescope: snooping on Dome Simulator.DOME_SHUTTER"
2017-02-13T13:24:08.138 - DEBG - INDI Server: "2017-02-13T12:24:08: Driver indi_gphoto_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD"
2017-02-13T13:24:08.138 - DEBG - INDI Server: "2017-02-13T12:24:08: Driver indi_gphoto_ccd: snooping on Telescope Simulator.TELESCOPE_INFO"
2017-02-13T13:24:08.139 - DEBG - INDI Server: "2017-02-13T12:24:08: Driver indi_gphoto_ccd: snooping on CCD Simulator.FILTER_SLOT"
2017-02-13T13:24:08.139 - DEBG - INDI Server: "2017-02-13T12:24:08: Driver indi_gphoto_ccd: snooping on CCD Simulator.FILTER_NAME"
2017-02-13T13:24:08.139 - DEBG - INDI Server: "2017-02-13T12:24:08: Driver indi_gphoto_ccd: snooping on SQM.SKY_QUALITY"
2017-02-13T13:24:08.139 - DEBG - INDI Server: ""
2017-02-13T13:24:08.259 - DEBG - INDIListener: Processing device iEQ45 Pro
2017-02-13T13:24:08.260 - DEBG - Ekos received a new device: iEQ45 Pro
2017-02-13T13:24:08.446 - DEBG - < iEQ45 Pro >: < CONNECTION >
2017-02-13T13:24:08.578 - DEBG - < iEQ45 Pro >: < DRIVER_INFO >
2017-02-13T13:24:08.661 - DEBG - < iEQ45 Pro >: < DEBUG >
2017-02-13T13:24:08.740 - DEBG - < iEQ45 Pro >: < SIMULATION >
2017-02-13T13:24:08.765 - DEBG - < iEQ45 Pro >: < CONFIG_PROCESS >
2017-02-13T13:24:08.770 - DEBG - Received new device Canon DSLR
2017-02-13T13:24:08.789 - DEBG - INDIListener: Processing device Canon DSLR
2017-02-13T13:24:08.789 - DEBG - Ekos received a new device: Canon DSLR
2017-02-13T13:24:08.812 - DEBG - < Canon DSLR >: < CONNECTION >
2017-02-13T13:24:08.860 - DEBG - < Canon DSLR >: < DRIVER_INFO >
2017-02-13T13:24:08.891 - DEBG - < Canon DSLR >: < CONFIG_PROCESS >
2017-02-13T13:24:08.897 - DEBG - < iEQ45 Pro >: < DEVICE_PORT >
2017-02-13T13:24:08.903 - DEBG - < iEQ45 Pro >: < TELESCOPE_BAUD_RATE >
2017-02-13T13:24:08.907 - DEBG - < iEQ45 Pro >: < ACTIVE_DEVICES >
2017-02-13T13:24:08.917 - DEBG - < iEQ45 Pro >: < DOME_POLICY >
2017-02-13T13:24:08.923 - DEBG - < Canon DSLR >: < ACTIVE_DEVICES >
2017-02-13T13:24:08.941 - DEBG - < Canon DSLR >: < DEVICE_PORT >
2017-02-13T13:24:08.966 - DEBG - < Canon DSLR >: < DEBUG >
2017-02-13T13:24:08.971 - DEBG - < Canon DSLR >: < SIMULATION >
2017-02-13T13:24:13.238 - DEBG - Ekos: "Unable to establish:\n+ QHY CCD\nPlease ensure the device is connected and powered on."
2017-02-13T13:24:42.832 - DEBG - iEQ45 Pro : "Telescope is online. "
2017-02-13T13:24:42.833 - DEBG - Ekos: iEQ45 Pro is connected.
2017-02-13T13:24:42.834 - DEBG - Ekos: 1 devices connected out of 2
2017-02-13T13:24:43.028 - DEBG - < iEQ45 Pro >: < ON_COORD_SET >
2017-02-13T13:24:43.113 - DEBG - < iEQ45 Pro >: < EQUATORIAL_EOD_COORD >
2017-02-13T13:24:43.113 - DEBG - Ekos: "iEQ45 Pro is online."
2017-02-13T13:24:43.281 - DEBG - < iEQ45 Pro >: < TELESCOPE_ABORT_MOTION >
2017-02-13T13:24:43.431 - DEBG - < iEQ45 Pro >: < TELESCOPE_MOTION_NS >
2017-02-13T13:24:43.477 - DEBG - < iEQ45 Pro >: < TELESCOPE_MOTION_WE >
2017-02-13T13:24:43.518 - DEBG - < iEQ45 Pro >: < TELESCOPE_SLEW_RATE >
2017-02-13T13:24:43.523 - DEBG - < iEQ45 Pro >: < TIME_UTC >
2017-02-13T13:24:43.575 - DEBG - < iEQ45 Pro >: < GEOGRAPHIC_COORD >
2017-02-13T13:24:43.610 - DEBG - < iEQ45 Pro >: < TELESCOPE_PARK >
2017-02-13T13:24:43.636 - DEBG - < iEQ45 Pro >: < TELESCOPE_PARK_POSITION >
2017-02-13T13:24:43.649 - DEBG - < iEQ45 Pro >: < TELESCOPE_PARK_OPTION >
2017-02-13T13:24:43.659 - DEBG - < iEQ45 Pro >: < TELESCOPE_INFO >
2017-02-13T13:24:43.700 - DEBG - < iEQ45 Pro >: < TARGET_EOD_COORD >
2017-02-13T13:24:43.708 - DEBG - < iEQ45 Pro >: < USEJOYSTICK >
2017-02-13T13:24:43.712 - DEBG - < iEQ45 Pro >: < HOME >
2017-02-13T13:24:43.723 - DEBG - < iEQ45 Pro >: < TELESCOPE_TRACK_RATE >
2017-02-13T13:24:44.064 - DEBG - < iEQ45 Pro >: < CUSTOM_RATE >
2017-02-13T13:24:44.092 - DEBG - < iEQ45 Pro >: < TELESCOPE_TIMED_GUIDE_NS >
2017-02-13T13:24:44.102 - DEBG - < iEQ45 Pro >: < TELESCOPE_TIMED_GUIDE_WE >
2017-02-13T13:24:44.102 - DEBG - Ekos: "Guider port from iEQ45 Pro is ready."
2017-02-13T13:24:44.396 - DEBG - < iEQ45 Pro >: < GUIDE_RATE >
2017-02-13T13:24:44.403 - DEBG - < iEQ45 Pro >: < Firmware Info >
2017-02-13T13:24:44.463 - DEBG - < iEQ45 Pro >: < GPS_STATUS >
2017-02-13T13:24:44.481 - DEBG - < iEQ45 Pro >: < TIME_SOURCE >
2017-02-13T13:24:44.486 - DEBG - < iEQ45 Pro >: < HEMISPHERE >
2017-02-13T13:24:44.501 - DEBG - iEQ45 Pro : "Mount is unparked. "
2017-02-13T13:24:44.514 - DEBG - iEQ45 Pro : "Mount UTC offset is 0.28. UTC time is 2000-07-30T23:42:59 "
2017-02-13T13:24:44.522 - DEBG - iEQ45 Pro : "Loading device configuration... "
2017-02-13T13:24:44.531 - DEBG - iEQ45 Pro : "Site location updated to Lat 51:28:06 - Long 0:00:00 "
2017-02-13T13:24:44.535 - DEBG - Mount: "Telescope info updated successfully."
2017-02-13T13:24:44.550 - DEBG - iEQ45 Pro : "Can only set tracking rate if tracking mode is set to custom. "
2017-02-13T13:24:44.558 - DEBG - iEQ45 Pro : "Device configuration applied. "
2017-02-13T13:24:44.577 - DEBG - iEQ45 Pro : "Time and date updated. "
2017-02-13T13:24:44.585 - DEBG - iEQ45 Pro : "Site location updated to Lat 52:21:00 - Long 4:51:59 "
2017-02-13T13:25:27.021 - DEBG - Reporting new timestep value: 60


Chris

Those are Ekos logs, it's better to look at INDI ieqpro driver logs. Check my signature for more information on logging.

here some logs. i noticed that when I connect the date on mount is set to 2048.
In this log I only connected, changed slew speed to 9 and moved to west a bit.

Hope you can see why RA and DEC remain zeros.

Chris

Could you tell me correct, working driver for Ieq45 with 8406 Hand Controler ?.

Indi version 1.5.0 (Ubuntu Mate on Raspberry Pi 3).