wotalota created a new topic ' Kstars startup failure' in the forum. 4 weeks ago

Running KStars 3.4.3 stable, ubuntu 20.04, Intel NUC
It has been happening on my system for a long time.
Sometimes KStars crashes during initial startup it seems happen around the time 6 of the 9 top level Ekos icons have been displayed. Retry a time or two and it will get through the startup and run okay so it has not been a big issue.
Ran it today using ekos-debugger and got the attached files.
 

Read More...

wotalota replied to the topic 'New stable version?' in the forum. 1 month ago

Nice.
It gives a list of what is on hold. I added libindi-*

Read More...

It used to be that Launchpad would build the packages immediately, or with little delay. But unfortunately, this free service has been degrading as of late. The only way to reliably do this is by a private PPA server, but that would cost quite a bit in terms of setup and maintenance. Perhaps we can come up with a way to cover the costs for such PPA.

If funding a server is needed I'd suggest a new entry to give the issue some visibility. Assuming it goes ahead something prominent on the web page to show progress towards a goal. It does not make sense for a project like this to be struggling for the wont of a server.
 

Read More...

I purged the nightly install and installed the stable release, now the cameras are working. I wonder if I had just reinstalled the nightly would that have also cleaned things up. Anyway, happy to see stable had been updated with fixes I did not know that was being done.
 

Read More...

After following the earlier suggestion:
(reverse-i-search)`rein': sudo apt-get update && sudo apt-get -y install --reinstall libasi

I am showing the same:
root@:~# apt list libasi*
libasi/focal,now 1.17~202106152146~ubuntu20.04.1 amd64 [installed]

And no change with:
/usr/lib/x86_64-linux-gnu/libASICamera2.so.1.18

Read More...

If it can be reproduced how would you go about debugging? Is there associated INDI driver like code that could be instrumented is it all in the ASI library/

Read More...

The driver crashes consistently here but not until a connect is attempted.
I deleted the .xml config file and it crashes before a default one can be created.
Only have the one library effective and it has been in place since before the weekend nightly update.
-rw-r--r-- 1 root root 2352608 Jun 15 17:46 /usr/lib/x86_64-linux-gnu/libASICamera2.so.1.18
With the build problems being discussed in other threads perhaps we are getting partial updates?

Read More...

After updating the nightly Saturday and Sunday cannot connect to the ASI driver.
When staring the driver using indiserver and using remote from Ekos, it runs but
the connect fails.After updating the nightly Saturday and Sunday cannot connect to the ASI driver.
When staring the driver using indiserver and using remote from Ekos, it runs but
the connect fails.
Ubuntu 20.04 Intel x86-64.

Ubuntu 20.04 Intel x86-64.



 

Read More...

Installed the nightly and get a much improved initial setup. No longer losing the Park To attribute each time, the write fields appear to have been removed from the Site Management tab. Assume the save under the Options tab is serving all the needs but did not need to use it each startup. Started up a few times and just needed to use the cold start button to get the Parked status.

Read More...

Thanks that helps to clarify things. I went to look closer intending to use serial/by-id but after reconnecting the serial port could not reproduce the problem.

Read More...

For a couple of years I have been using an Arduino to control a rolloff roof. The Arduino runs
24x7. Recently it has been causing problems. The problem is when Ekos is first used things work as
expected.  If Ekos is stopped and restarted it can not connect to the Arduino and produces the
error message about making sure the device is connected to that port. The only way I found to get
it to reconnect is to reboot the system and start again.

On that second attempted start of Ekos the roof driver and the port /dev/ttyACM1 appears normal and
the Arduino is listening for a connection. The appearance of the INDI USB connection in Ekos
has changed from what was previously /dev/ttyACM1 to Arduino_LLC_Arduino_Due-iF00 as show in the
attached screen shot.   

Unlike most Arduino models the Due has 2 USB connections so normally I would see /dev/ttyACM0 and
/dev/ttyACM1 connections.  ttyACM0 is the programming port and is not involved with Ekos
funcionality. The ACM0 Arduino port can use the Arduino console for diagnostic purposes while
the ACM1 port is in use for INDI communications. Today I found that unplugging the programming port
USB cable which Ekos should be unaware of changes the situation. What was /dev/ttyACM1 now becomes
/dev/ttyACM0 of course, the unusual naming in the INDI panel remains as it was with the
LLC-Arduino style identifier.  Without the second port Ekos can now be restarted without requiring
a reboot.

Does anyone know if the diiferent USB identifiers in the INDI panel is due to a Linux or INDI
modification? It is not a naming convention I am familiar with and what if any impact it will have
when returning to using the logical name of /dev/roofCtrl in the udev rules file.

Any suggestions for linux USB related commands that might expose differences from when it does and
does not work?

I have not explored whether adding an second Arduino of the same model will introduce a similar
issue.

 

Read More...

wotalota replied to the topic 'KStars for Ubuntu 21.04' in the forum. 1 month ago

Should be fine. This will show which repository you have installed:
sudo apt policy | grep ppa

Expect to see ppa:mutlaqja/ppa or the nightly.

I follow the directions at:
indilib.org/forum/general/210-howto-buil...st-libindi-ekos.html

Read More...

wotalota replied to the topic 'Davis Vantage Vue & INDI' in the forum. 2 months ago

Is there a Davis user group forum or testing tools on their site?

Read More...