Welcome, Guest
Username: Password: Remember me
25 Jul 2018
Glad to announce of release of INDI Library v1.7.4 on 2018-07-25. A few drivers were added in this release as we continue to improve & stabilize existing drivers.
Read More...
  • Page:
  • 1

TOPIC: Can’t connect to my mount

Can’t connect to my mount 2 weeks 1 day ago #29449

Hi,
I’m new to INDI trying to connect my Mac to my Orion Atlas EQ-G Goto mount.
Unfortunately I had no success so far.

My assumption:
I can connect via EQMod driver directly to the mount or I can use Orion Atlas driver to connect the the mount’s HC

HW in place:
Orion Atlas EQ-G Goto, PL-2303 USB-to-Serial Cable, Shoestring EQDIR

SW in place:
MacOS 10.13, CdC 4.0-3575, INDI Server 2.7.0 (1.7.0), Orion Atlas driver 1.0, EQMod 0.3, PL-2303 driver v1.6.1

HW (Mount, USB2Serial, EQDIR) seems to be OK, as I was able to connect via EQMac to the mount.

Connect attempt via EQMod Mount driver:
Failing very early as the driver shows a yellow status in the INDI server list. EQMod not showing up after hitting „Connect and get device list“ within CdC

Connect attempt via Orion Atlas driver:
Power up of the Mount —> Initialize & Align Mount via HC —> Activate PC Direct Mode in HC —> Connect Mac via USB2Serial and Orion Serial Cable to HC.
Now I get SynScan to select as telescope in CdC. Within INDI GUI the right port is selected /dev/cu.usbserial (also tried with /dev/tty.usbserial…) leaving all options default (for this post I increased debug information) and try to connect:

CONNECTION CONNECT=ON
[DEBUG] Connecting to /dev/cu.usbserial
[DEBUG] Port FD 7
[DEBUG] Connection successful, attempting handshake...
[INFO] Synscan Mount not responding
[DEBUG] Handshake failed.
[WARNING] Communication with /dev/cu.usbserial @ 9600 failed. Starting Auto Search...
[DEBUG] Trying connection to /dev/cu.Bluetooth-Incoming-Port @ 9600 ...
[DEBUG] Connecting to /dev/cu.Bluetooth-Incoming-Port
[DEBUG] Port FD 8
[DEBUG] Connection successful, attempting handshake...
[INFO] Synscan Mount not responding
[DEBUG] Handshake failed.

If I try to connect agin right away I now receive:

CONNECTION CONNECT=ON
[DEBUG] Connecting to /dev/cu.Bluetooth-Incoming-Port
[ERROR] Failed to connect to port (/dev/cu.Bluetooth-Incoming-Port). Error: Port failure Error: Resource busy. Check if device is connected to this port.
[WARNING] Communication with /dev/cu.Bluetooth-Incoming-Port @ 9600 failed. Starting Auto Search...
[DEBUG] Trying connection to /dev/cu.Bluetooth-Incoming-Port @ 9600 ...
[DEBUG] Connecting to /dev/cu.Bluetooth-Incoming-Port
[ERROR] Failed to connect to port (/dev/cu.Bluetooth-Incoming-Port). Error: Port failure Error: Resource busy. Check if device is connected to this port.

It is not trying to connect to usbserial any longer….

I also tried to connect with Orion Atlas driver directly with EQDIR w/o HC, also w/o success.

What am I doing wrong?
Any help appreciated.

Thanks,
David

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

Can’t connect to my mount 2 weeks 1 day ago #29453

Did you download the PL-2303 drivers for Mac from FTDI?

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

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info

Can’t connect to my mount 2 weeks 13 hours ago #29462

First I installed FTDIUSBSerialDriver_v2_4_2 driver but after checking the chip on my USB2Serial via system information I got and installed PL2303_MacOSX_1_6_1_20171018 from Prolific. I removed FTDI driver via pkgutil command / had not even tried with FTDI driver to connect via INDI to the mount.

USB2Serial identifies as:

Produkt-ID: 0x2303
Hersteller-ID: 0x067b (Prolific Technology, Inc.)
Version: 3.00
Geschwindigkeit: Bis zu 12 MBit/s
Hersteller: Prolific Technology Inc.
Standort-ID: 0x00120000 / 13

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

Can’t connect to my mount 2 weeks 9 hours ago #29473

Ok what's the role of the PL2303 cable since you have Shoestring EQDIR cable?

It should be Mac --> EQDIR --> HEQ5 and then you'd use INDI EQMod driver with that.

Try using KStars 2.9.8 to see if this works as well.

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

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info

Can’t connect to my mount 2 weeks 5 hours ago #29483

PL2303 is needed as the Shoestring EQDIR is having a Serial Port on both sides like the attached one

Installed KStars and there I can connect to the mount using the local mode in the device manager.

Now what is missing when trying to connect via CdC?
Not sure if I read somewhere that I need to enter GPS data before being able to connect to the mount via EQMOD. Could the issue be in this area?
Attachments:

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

Can’t connect to my mount 1 week 6 days ago #29489

Not sure, it should work. Maybe post at CdC forum (if there is one)?

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

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info

Can’t connect to my mount 1 week 6 days ago #29495

OK, I played around a little bit more and I guess my issue is with the INDI Server (version or the startup) and not CdC (thou I will try to look in this direction as well)

I started the INDI Server via KStars (Tools -> Device Manager -> Select EQMod -> Run Local) and then I was able to get in the CdC device list EQMod and was also able to connect to / control the mount from CdC.

I can see a difference between the indiserver coming with KStars and coming with INDI Server GUI.
To further analyze I want to start the indi server via cmd line but was not able to:



KStar indi server executable started via:
/Applications/kstars.app/Contents/MacOS/indi/indiserver -v /Applications/kstars.app/Contents/MacOS/indi/indi_eqmod_telescope

2018-09-12T11:00:34: Driver /Applications/kstars.app/Contents/MacOS/indi/indi_eqmod_telescop: pid=4125 rfd=3 wfd=6 efd=7
2018-09-12T11:00:34: listening to port 7624 on fd 4
2018-09-12T11:00:34: Driver /Applications/kstars.app/Contents/MacOS/indi/indi_eqmod_telescop: 2018-09-12T11:00:34: Driver /Applications/kstars.app/Contents/MacOS/indi/indi_eqmod_telescop: execlp: No such file or directory
Child process 4125 died
2018-09-12T11:00:34: Driver /Applications/kstars.app/Contents/MacOS/indi/indi_eqmod_telescop: stderr EOF
2018-09-12T11:00:34: Driver /Applications/kstars.app/Contents/MacOS/indi/indi_eqmod_telescop: restart #1
2018-09-12T11:00:34: Driver /Applications/kstars.app/Contents/MacOS/indi/indi_eqmod_telescop: pid=4126 rfd=0 wfd=6 efd=7
2018-09-12T11:00:34: Driver /Applications/kstars.app/Contents/MacOS/indi/indi_eqmod_telescop: 2018-09-12T11:00:34: Driver /Applications/kstars.app/Contents/MacOS/indi/indi_eqmod_telescop: execlp: No such file or directory
Child process 4126 died
...
2018-09-12T11:00:34: Driver /Applications/kstars.app/Contents/MacOS/indi/indi_eqmod_telescop: Terminated after #10 restarts.
2018-09-12T11:00:34: good bye

The KStars indiserver called w/o any arguments shows the following usage output:

Usage: /Applications/kstars.app/Contents/MacOS/indi/indiserver [options] driver [driver ...]
Purpose: server for local and remote INDI drivers
INDI Library: 1.7.4
Code $Rev$. Protocol 1.7.
....



INDI Server GUI indi server executable started via:

2018-09-12T11:04:56: startup: /Applications/INDI Server.app/Contents/MacOS/indiserver -v /Applications/INDI Server.app/Contents/MacOS/indi_eqmod_telescope
switching stderr to /Users/xyz/Library/Logs/indiserver.log


Logfile contains:

#2018-09-12T11:04:56: listening to port 7624 on fd 3
2018-09-12T11:04:56: open(/tmp/indiserverFIFO): No such file or directory.
2018-09-12T11:04:56: good bye

Creating the FIFO file via mkfifo /tmp/indiserverFIFO did not change anything.
INDI Server GUIs indiserver does not show any usage information if called w/o arguments.



How would I start the INDI Server & EQMod driver manually / which environment settings are needed?

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

Can’t connect to my mount 1 week 4 days ago #29565

2018-09-12T11:00:34: Driver /Applications/kstars.app/Contents/MacOS/indi/indi_eqmod_telescop: 2018-09-12T11:00:34: Driver /Applications/kstars.app/Contents/MacOS/indi/indi_eqmod_telescop: execlp: No such file or directory


What KStars version is this? It's trying to run the wrong driver, it's missing an e at the end. Needs to be indi_eqmod_telescope

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

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info

Can’t connect to my mount 1 week 1 day ago #29623

The installed KStars version is 2.9.8, the INDI Server coming with it identifies as INDI Library 1.7.4 with Code $Rev$. Protocol 1.7.

About the missing ‚e‘, I guess it is only truncated. I was able to start the server with „./indiserver -v ./indi_eqmod_telescope“ from within „/Applications/kstars.app/Contents/MacOS/indi“. If I start it w/o qualifying the path for indi_eqmod_telescope I get the above mentioned error message. The local directory is not configured as path in my environment.

With this I was I’m able to start the INDI Control Panel and connect successfully to the mount.
Still not able to connect afterwards in CdC to the mount but this I will follow up with CdC :-)

But why am I not able to start the server from cmd line with the INDI Server version downloaded from www.cloudmakers.eu/indiserver/ ?

I’m currently trying to setup the environment to build the latest server version myself and maybe being able to debug.
Will report how this goes.

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

  • Page:
  • 1
Time to create page: 0.150 seconds

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!


Gallery

Replica

Why INDI

Replica