Hello,

Thanks, that's some good info there, I shall check the file first before going for a full re-install.
Only me can work on the observatory, nobody else.

I choose Ubuntu for the PPA, had Debian to start off on that board.

Read More...

This may be due to the change of network devices naming in 18.04 - if you have /etc/network/interfaces with explicit device names and do not have udev rules to rename devices to your names it will fail. I'm just guessing here but it seems plausible to me. Maybe your remote hands can edit the names ?
That is why I never use ubuntu on remote servers without remote console - it is designed for the desktop and bites you in the behind in the worse possible moment.
I would humbly suggest moving to debian - it is a bit harder to set up (no PPA, older packages etc.) but it is worth it at the end - just my HO.

Read More...

You need to rebuild libindi first, then install it. Then after that, build and install QSI.

Read More...

I have posted this on giithub as I have exhausted my knowledge on builds.

Read More...

Kaczorek wrote: Due to increasing security constraints in majority of browsers this issue will persist. To address This ssl will be disabled by default in the new version. I would recommend using a VNC viewer to access Astroberry Server if you have problems with accessing it with a browser.

Firefox seemed to allow successful access to the site after adding an exception for the certificate error. I have my own private Certificate Authority and was able to generate a new certificate that works fine in all browsers. I believe the issue with your certificate is that the CA cert and Web Server cert share the exact same Common Name. This causes the Subject and Issuer fields of the Web Server cert to be the same which should only occur with self-signed root certificates (the CA cert). When a browser sees this, it tries to verify that the digital signature coincides with the Issuer's public key; in this case, it checks against the Web Server's public key instead of the CA's public key, causing it to fail.

I believe that simply adding something like an OU to the Common Name of the Web Server cert will fix this (requires generating new certificate of course).


P.S.
@admins: Speaking of certificates, where is the one for indilib.org???




Read More...

For some reason my second reply didn't get accepted - so I will say it again

Thanks for that I will try that procedure out as it makes perfect sense - thanks - if this reply get shown !!!!!!!

Read More...

Please turn the mount first to the north pole and start the driver. If Kstars is on a mount point other than the North Pole, right-click on the North Pole and select the "Synchronize" command.

Mount information and Kstars location information are now synchronized.

This problem is thought to be due to the fact that the driver does not have the mount synchronization of the home position and alignment information.

Read More...

El Corazon wrote:

xsnrg wrote: Most of the images I have taken using INDI/Ekos are posted under my profile:

indilib.org/support/community/4350-jose-corazon/photos.html

For some reason I don't understand, I seem to be the only one who has discovered that we can post our astrophotos there. It would be great to see others do that as well.

Jo

You told me about this and I have uploaded several pics as well. All taken using Ekos. Some of them with my 71 mm telescope, some of them with my 203 mm telescope. See

www.indilib.org/support/community/4119-w...um.html?albumid=2176

Read More...

I upgraded today to the latest stable KStars and INDI.

The good news is that the driver no longer crashes, after the fixes for the tty_nread changes. So slewing is normal, ...etc.

The bad news: One problem: when starting an Align (1 star or 3 star), the 'Align Process' line does not change to the value returned from :A?#. It still says 'Manual Alignment Process Idle', instead of the return value from said USB command.

Read More...

Hi Thanks for the reply :-

1. Mine points south pole , east pole anything but North
2. Mine is a old SWAZ so no clutches and moving the whole scope/tripod doesn't work on the next slew.
3. As yet I haven't got the Solver to work reliably - online is OK .

Read More...

Strange that the do-release-upgrade script didn’t do its job. Glad to read that you’ve got a backup of the essential stuff though!

Read More...

If you can correct it, please also consider the information on the following link.

Currently, Skywatcher Alt - Az driver thinks that "Park" function and "Unpark" function are not working properly.

I can not use it unless I avoid that part, so I think that people who use this driver for the first time with INDI are confused.

The lack of the most important function is that position information has not been acquired since the mount is not synchronized with the north pole which is the home position when the driver is turned on. Since there is no positioning information, the position information does not operate properly in the initial state.

Since the EQMOD driver has acquired home position synchronization and position information, the parking function functions normally because the mount information is correctly stored.

If the Skywatcher Alt - Az driver can at least synchronize Arctic information which becomes the mount and home position, I think that the problem can be avoided.

Read More...

Thank you for contacting me.

Since my mount is Skywatcher Virtuoso, wifi adapter is required for TCP connection.

I have not received it yet, but the specification of the connection when using the wifi adapter is the same as the Skywatcher AZ GTi mount as long as reading this document.

Watching the log is the same as before Jasem changed the Synscan driver. (Crash with a handshake)

If similar changes have been added to the EQMOD driver and the Skywatcher Alt-Az driver,
I think that all Skywatcher mounts can be connected wirelessly with udp 11880.

Mr. Jasem> When the wireless LAN adapter arrives, I will check the connection with the wireless LAN.
Please add the same change as Synscan driver to EQMOD driver, Skywatcher Alt-Az driver.

I think it's a useful fix for all users who wish to install Skywatcher on Wi-Fi.

Read More...

B-E-A-U-T-I-F-U-L!!!!

Thanks for the feedback. That is actually the reason for your crash and OpenGL is supported in RPI3. What OS are you using? There is a missing installation somewhere there.

Read More...

Set the telescope to the north pole before turning on the driver.

If you turn on the driver and the pointer of the telescope shows a different direction, right click on the North Pole with Kstars and set it with the "sync" command.

Read More...