Get Connected!

Come and join our community. Expand your network and get to know new people!

Sorry, we currently have no events.
View All Events

The problem comes from udev and its way of mounting dev points.
It is possible to create rules to obtain a static point according to the manufacturer's name
wiki.archlinux.org/title/Udev#Setting_static_device_names

A tutorial made by Indi to create the rules file
www.indilib.org/support/tutorials/157-pe...al-port-mapping.html

It would be interesting to know the identifier of your GPS and the USB/RJ cable of your mount. And check if they are in the rules /lib/udev/rules.d/25-gpsd-usb.rules and /lib/udev/rules.d/69-libftdi.rules
To find them, use the following command as noted in the tutorial

"To find out the serial ID, run the following command against the device node. For example, the find the serial id of the device connected to /dev/ttyUSB0:"

udevadm info -a -n /dev/ttyUSB0 | grep '{serial}' | head -n1

Read More...

After sleeping on the matter, I decided to say, to hell with the GPS. Since I have to enter the time and location every time I start the mount, I could just go with that, and use the "Mount updates KStars" for time and date setting. That would cover most of it. The only thing missing would be updating the system clock. I could live with that.

In any case that would fulfill your first test item. I will send you logs and screenshots. Then I would go back to trying the GPS, both after startup and before, and send those logs and screenshots and the other information you request.

But I am still wondering, what is going on on the system level here? Why doies tthe system decide that /dev/ttyUSB0 is no good, and set up /dev/ttyUSB1 instead? KStars and INDI logs provide no information on that, even at the most verbose level. Something is causing that to happen and I wonder if system logs would record some useful information about this.

Read More...

Something has changed, or I changed something, now sync works on first or second solve, then it breaks, i need to disconnect and then reconnect, to be able to sync.

From sky safari no issues at all, so I would think it is on ekos side

Read More...

I plan to try out with my humble phone camera and share the screen on the laptop where I can run CC :-) Fingers crossed for this weekend

Read More...

Its working
Try again please

stellarmate.com/

Read More...

Steve replied to the topic 'Install "Obsolete" Driver' in the forum. 5 hours 26 minutes ago

I seem to be able to connect with K-stars/Eko. When I try to connect using INDI from PHD2, I get a I get a “Server address is missing or invalid error”.

Steve

Read More...

Hi Steve,

What we are missing to determine the problem are the logs and screenshots, as in your first message.

The ideal would be to first test the mount alone to determine if Ekos likes it and to use it for a few minutes. In the mount connection settings, you should see the name of your mount's driver above the "Port" line instead of the GPS name (like in your image in the first post).

Then, if it works correctly, connect the GPS and observe what is happening in the logs and settings panel.

And finally, if everything goes well so far, restart everything in order to determine which processes are blocking the dev points with the logs, screenshots, versions of Kstars and Indi and copy of your gpsd configuration file.

Read More...

Kurt, I totaly agree with you. Raspberry Pi Camera Module 3 seams to be a great option. But I need something more versatile, USB plug&play. No drivers needed.
That's way I'm looking for UVC compatible cameras.


Read More...

There is a new Raspberry Pi Camera Module 3 available with autofocus and a focus range 5cm to infinite. Should be able to do the job using the python Picamera2 library.

Read More...

Simon replied to the topic 'INDI LibCamera Driver' in the forum. 11 hours 6 minutes ago

Latest version of libcamera INDi driver crashes when I conect Astra_lite to it. Previous version worked OK.
Latest KStars have no problem with it.

Log file in attachement.

Read More...

Book United Flights for Great Getaways
With United Airlines booking, fly affordably & have exclusive experiences. Enjoy comfort, luxury, & budget...
Show more

Book United Flights for Great Getaways

With United Airlines booking, fly affordably & have exclusive experiences. Enjoy comfort, luxury, & budget with reservations on United Airlines.

Steve,

Not sure about the old driver, you can likely compile and install it yourself, but let's see if we can get the V2 driver working for you ... I use it all the time (with my CP3, but I'm sure it was verified to be working with CP4 and CP5).

Can you connect to it with KStars/Ekos? If that shows an issue, can you send a full kstars log of your failed connections (make sure you have verbose logging on and logging for the mount driver checked). The usual issue for things like that it is trying to connect to the wrong port. E.g. if you are using a FTDI cable, you need to make sure you have the right /dev/ttyUSB0 or /dev/ttyUSB1 etc. If you are using ethernet with your CP4, I think there was some network protocol choice. If you don't get it working from that, can you also send screenshots of your INDI mount control tabs (e.g. Main Control and Connection)?

Mike Hanson at Astro-Physics has also verified all this works and can be a resource to help you.

Hy

Read More...

Nope. I spoke too soon. Somehow, in spite of all the changes, /dev/ttyUSB0 still goes away (only /dev/ttyUSB1 remains). Enough. Not going to fight this tonight. Willing to try anything else you might want to recommend another night.

Read More...

Steve created a new topic ' Install "Obsolete" Driver' in the forum. 15 hours 12 minutes ago

I'd like to install an "obsolete" driver. I've had problems connecting to my Astro-Physics GTO CP4 Mach1 with the V2 Astro-Physics mount driver from PHD with INDI but the old GTOCP2 driver, if I recall correctly, used to work for me. Unfortunately that driver is no longer installed when installing INDI. How do I install the old driver?

Read More...

Actually START_DAEMON must be set false from my experiments.

With that, and the chrony stuff, it's all good now.

Read More...