×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

I can not connect the EQmod mount .

  • Posts: 326
  • Thank you received: 50
My most recent experiences with KStars 3.5.4 have given me encouragement after several hiccups over the last year. I noticed in most recent updates (Astroberry) some significant further updates to the RPi kernel software packages. My first ‘hiccups’ arrived when the major kernel update from 4.19 to 5.4 arrived a year ago, but I’m hoping the software has settled now.
After recent sudo apt update && sudo apt full-upgrade of two installations, I have EQDirect cable operation of my AZ-EQ5 and AZ-GTi mounts once again. And (fingers crossed for clear skies tonight) the serial interface clashes between the mounts and my Pegasus Pocket Power Box also seem to have settled themselves.
By the way I always use sudo apt full-upgrade these days just in case…….
2 years 8 months ago #74278

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

  • Posts: 16
  • Thank you received: 0
I get this : 
But I use Usb to mini usb cable . Maybe I have to use EQDirect cable ? 
2 years 8 months ago #74281
Attachments:

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

  • Posts: 474
  • Thank you received: 168
You should run command "ps 563" (or the number given by the fuser command) to see the process, ps by itself only gives processes in the current shell.

If your mount has USB port directly (not in the hand controller), that can be used instead of EQDirect cable, but you need to change the baud rate to 115200 from the default 9600 used by regular EQDirect cable. If your hand controller has USB (older Synscan had RJ11 serial port), you can use that with the Synscan driver (not EQMod) as such or you if you select PC Direct mode from the hand controller, you can use EQMod too. So four possibilities:

USB cable to hand controller --> Synscan driver
USB cable to hand controller, controller set to PC Direct mode --> EQMod driver (9600 baud I think)
USB cable directly to mount --> EQMod driver (115200 baud)
EQDirect cable to mount --> EQMod driver (9600 baud)
Last edit: 2 years 8 months ago by Jarno Paananen.
2 years 8 months ago #74282

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

  • Posts: 421
  • Thank you received: 102
lsof /dev/ttyUSB0
is a quicker and easier way to see what process has a file open.

It's possible there's a GPS daemon running trying to find a GPS dongle on the serial port, tying up the port so INDI can't use it.
2 years 8 months ago #74283

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

  • Posts: 16
  • Thank you received: 0
My mistake.  
I will make en old manuel EXOS 1 to diy GO TO with EQdrive controller and 2 steppers . So, is it  not possible to use USB from raspberry pi 4 to usb of the controller ? Here is a picture of controller and the ports:
 
2 years 8 months ago #74285
Attachments:

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

  • Posts: 16
  • Thank you received: 0
 
Ok , It is gpsg. How to stop it or what to do ?
2 years 8 months ago #74287
Attachments:

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

  • Posts: 421
  • Thank you received: 102
Try
sudo systemctl disable gpsd
and reboot, see if that helps.
The following user(s) said Thank You: Georgi Malakov
2 years 8 months ago #74288

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

  • Posts: 474
  • Thank you received: 168
Ah yea, forget what I wrote earlier, that's for normal Synta mounts, not for EQDrive. For EQDrive the USB cable you are using should work fine. I don't know if the baud rate needs to be changed, but first things first. Your problem seems to be that chronyd, which is a NTP server, is trying to use the serial port looking for GPS to get time from. Many GPS dongles use the same USB-serial chip (CP2102) EQDrive uses so it can't really know what device is behind there, but it could also free the port if it can't find a GPS there.

You can stop chronyd by running "sudo systemctl stop chronyd" and try to connect after that. If that helps you can either disable or uninstall chronyd or modify its config so that it doesn't look for the GPS anymore.
The following user(s) said Thank You: Georgi Malakov
Last edit: 2 years 8 months ago by Jarno Paananen. Reason: Typo
2 years 8 months ago #74289

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

  • Posts: 16
  • Thank you received: 0
 
After reboot Ekos is not seeing EQMod mount .
2 years 8 months ago #74290
Attachments:

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

  • Posts: 421
  • Thank you received: 102
Hmm, odd. The EQMod INDI driver might be crashing. We'll need some logs.

Before starting Ekos, click the logs button and enable logging according to the screenshot below.

 

Then start Ekos. Then go back to the logs dialog, and click the "open logs directory" button down at the bottom. That will bring up a file explorer. Upload the log file so we can take a look.

 
Last edit: 2 years 8 months ago by Kevin Ross.
2 years 8 months ago #74291
Attachments:

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

  • Posts: 474
  • Thank you received: 168
It seems the INDI web manager either doesn't start EQMod driver or it crashes, I haven't used the web manager so I don't know if it shows a log somewhere, but you could also try to start the drivers either manually from command line (command "indiserver -v indi_asi_ccd indi_eqmod_telescope") or via KStars/Ekos to see if they show any more debug info why it doesn't start.
Last edit: 2 years 8 months ago by Jarno Paananen.
2 years 8 months ago #74292

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

  • Posts: 16
  • Thank you received: 0
 

File Attachment:

File Name: log_22-28-25.txt
File Size:54 KB

That is the log file.
2 years 8 months ago #74295
Attachments:

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

Moderators: Radek Kaczorek
Time to create page: 1.217 seconds