VTVL created a new topic ' A new class of telescope-camera system' in the forum. 3 months ago

Yesterday (9-09-2017) at the AME 2017 in Germany I saw an exhibit of a new type of telescope system. It had no means to use an eyepiece or external camera! Indeed there were no add-ons foreseen for the Stellin system. Only the 80 mm F5 APO lens and a start button are evident. The optical tube is square and sits between a U form body.

The French start-up company VAONIS founder and CEO Cyril Dupuy was able to answer all my questions and had the required features and functions inside the system. See www.vaonis.com/en But he and his technical support were not aware of INDI (Ekos & Kstars etc.) :ohmy: . However they intend to make public the API interface for all software developers.

The system uses a new SONY CMOS imager (3096 x 2080 pixels, A/D converter: 14 bits, Pixel size: 2,4µm x 2,4µm) and has a separate guider chip. The converging beam is brought to focus via a mirror through the tilt axis. A de-rotator device is integrated. I forgot to ask about filters for the monochrome version.

We spoke about the market and applications for such a system. Its price makes it very competitive with conventional GoTo telescopes plus all the add-ons which are needed to achieve a remote control astro-photographic capability. The 80 mm aperture may seem to be limiting but there are already many small automated survey camera systems and observatories for research. The camera is intended to support photometric data acquisition. Maybe you have questions for VAONIS or an application idea ……..

Read More...

VTVL replied to the topic 'INDI Server for Windows' in the forum. 5 months ago

Hi Peter,

The INDI Server for Windows was installed on the 32 bit Win7 laptop, localhost, and successfully tested with the ASCOM driver to connect to the LX200 protocol Littlefoot controller. Last Saturday night we tested it at the club observatory with the FS2 mount controller via a serial port. This worked. First the INDI Server for Windows configuration menu was used. The ASCOM Advanced LX200 option was selected. Also the CCD and Focuser simulators were selected. The option for the FS2 was displayed and selected. This worked.

We then tested the INDI option instead of the ASCOM option.
Again we had the Advanced LX200 and FS2.
Two error messages appeared.
The first said :
Server connected
Der Index war Auserhalb das Arraybereichs ( The index was outside of the array area).

What does that mean?

The second error message that we saw after thring again was:

Server connected
Der zugriff auf den Anschluss COM1 wurde verweigert. ( The access to the COM1 port is denied.)
Server disconnected.

Is this a permission problem? We checked other COM ports.

We will not continue with the 32 bit Win7 as my friend was given a used 64 bit dual core laptop with 250 GB of SSHD. --- Nice.
So the next steps will be to install Ubuntu MATE 17.04 etc. and use the reliable Linux INDI-Ekos-KStars configuration (or CdC 4.1 or HNSKY with INDI which both work ).

-- John

Read More...

VTVL replied to the topic 'INDI Server for Windows' in the forum. 5 months ago

Hello Peter,
So if we just need the INDISERVER to connect CdC to the mount controller via the LX200 protocol and serial/USB port
OR
if we want to connect CdC on a WIN7 32 bit laptop to a remote INDISERVER on an RPI3 which is connected to the LX200 protocol mount controller (using the KStars Lite App on an Android phone)
what should be installed?
Installing the VM 1.6 has been tried. It runs be very sloooowly and probably hangs in the KStars wizard on the 32 bit Win7 PC emulating Linux 64 bit. If it did work I guess that only the KStars in the VM could be used and not a Windoze CdC. Of course CdC for Linux could be installed ......
i.e. is there just a basic INDIserver which can be installed for 32 bit Win7 ?

My friend just called to say that he tried to install the ASCOM driver (: pixelstelescopes.wordpress.com/advanced-lx200/ ) and the LX200 appeared in the options. But he could not get further along. I do not have the details.

If it was my PC I would just run Ubuntu MATE Linux.

-- John

Read More...

VTVL replied to the topic 'INDI Server for Windows' in the forum. 5 months ago

I am working with a friend to use a WIN 7 32 bit laptop. The new 4.1 CdC has a broken LX200 driver so he cannot use the laptop with an FS2 mount controller via the serial port. (This was confirmed by the CdC author.) We are also trying to connect to a Littlefoot mount controller which uses the LX200 command set (and works fine with INDI -Ekos-KStars in Ubuntu on an RPI3 via USB). The Littlefoot has both Serial and USB. So we are trying to use the INDISERVER for Windows. So far we have it connecting to CdC. But the device selection menu of INDIserver for Windows does not include an LX200 (command set) option. We have tried the various "telescopes" listed but there is not successful connection in CdC. Is there a configuration that works to connect to LX200 devices?

Read More...

VTVL replied to the topic 'Indi support for Meade LS (Autostar III) series' in the forum. 8 months ago

Hi,
Did the problem get solved ?

Read More...

VTVL created a new topic ' Arduino Pin Numbers and simple_switcher_sk.XML' in the forum. 9 months ago

If I change the SOCKET "Pin X" number in the XML to 0 or 1 which are Arduino Leonardo outputs, then I get this error message.
2017-02-19T17:57:21: CONNECTED.FIRMATA VERSION:SimpleDigitalFirmata-1A.ino-2.5
2017-02-19T17:57:10: ARDUINO BOARD FAIL TO CONNECT. CHECK PORT NAME
2017-02-19T17:57:09: Port updated.

Why is this edit of the XML not allowed? How can pin 0 an 1 be included as valid ports?

Read More...

VTVL replied to the topic 'Installation problem' in the forum. 10 months ago

With some help from Jasem the problem has been corrected.
$ sudo apt-get install libnova-0.16-0
[sudo] password for VTVL:
Reading package lists... Done
Building dependency tree<br />
Reading state information... Done
E: Unable to locate package libnova-0.16-0
E: Couldn't find any package by glob 'libnova-0.16-0'
E: Couldn't find any package by regex 'libnova-0.16-0'

$ apt-cache policy kstars-bleeding
kstars-bleeding:
Installed: 5:16.12+201702060804~ubuntu16.04.1
Candidate: 5:16.12+201702060804~ubuntu16.04.1
Version table:
*** 5:16.12+201702060804~ubuntu16.04.1 500
500 ppa.launchpad.net/mutlaqja/ppa/ubuntu xenial/main amd64 Packages

What is /usr/lib/x86_64-linux-gnu/libnova*

there is no libnova-0.16.so

you could perhaps fake the library...
sudo cp /usr/lib/x86_64-linux-gnu/libnova-0.14.so.0.0.0 libnova-0.16.so.0.0.0
sudo rm /usr/lib/x86_64-linux-gnu/libnova.s0
sudo ln -s /usr/lib/x86_64-linux-gnu/libnova-0.16.so.0.0.0 /usr/lib/x86_64-linux-gnu/libnova.so

ls libnov*
libnova-0.14.so.0 libnova-0.14.so.0.0.0 libnova-0.16.so.0.0.0 libnova.so

ls -l /usr/lib/x86_64-linux-gnu/libnova.so
lrwxrwxrwx 1 root root 47 Feb 6 14:20 /usr/lib/x86_64-linux-gnu/libnova.so -> /usr/lib/x86_64-linux-gnu/libnova-0.16.so.0.0.0

ldd /usr/bin/kstars | grep nova
libnova-0.16.so.0 => not found

sudo ln -s /usr/lib/x86_64-linux-gnu/libnova-0.16.so.0.0.0 /usr/lib/x86_64-linux-gnu/libnova-0.16.so.0
sudo ldconfig

Ah, now KStars starts....version 2.7.3 as I had before the upgrade to 16.04.1
Thanks

Read More...

VTVL created a new topic ' Installation problem' in the forum. 10 months ago

After a re-installation of Ubuntu MATE 16.04.1 which went well I used the
sudo apt-get install indi-full kstars-bleeding command.
The installation appeared to go well. But when starting kstars from the command line the error message appeared:
kstars: error while loading shared libraries: libnova-0.16.so.0: cannot open shared object file: No such file or directory
The installation report shows:
Setting up libnova-0.14-0:amd64 (0.14.0-2.1) ...

Read More...

VTVL replied to the topic 'KStars-Ekos-INDI upgrade on a 0.5 meter scope' in the forum. 12 months ago

Now I am looking at the control of the PlaneWave focuser.
Here is a link: planewave.com/products-page/general-acce...ocuser/#.WEqqbWeVtaU
Is there an INDI driver for this focuser?

Read More...

VTVL replied to the topic 'KStars-Ekos-INDI upgrade on a 0.5 meter scope' in the forum. 12 months ago

I want to select the indi_lx200fs2 driver for the Astro-Electronics FS2 but it is not listed in the INDI profile editor. The indi_lx200fs2 does exist in the /usr/bin folder.
There is an "Astro Physics" driver listed. Is it wrongly named or is Astro Electronics just not in the list?

Read More...

VTVL replied to the topic 'Developing Driver for Arduino' in the forum. 1 year ago

Progressing:…….
NFocus and Moonlite were examined. MoonLite appears to be easier to adapt to the command set in the arduino. I copied moonLite .cpp and .h and renamed them to arduinoDCfocus (indi_arduinoDC_focus). Using the Cmake procedure as in the tutorials I tested the arduinoDCfocus after editing .h and .cpp. It worked! The arduino focuser responded to many of the basic commands.
Next I want to edit “moonLite” to “arduinoDCfocus”. So I did find and replace.

When debugging the following error message is given.


#include "arduinoDCfocus.h"
#include "indicom.h"
#include <stdio.h>
#include <termios.h>
#include <string.h>
#include <sys/time.h>
#include <unistd.h>
#include <math.h>
#include <memory>
#define ARDUINODCFOCUS_TIMEOUT 3
#define POLLMS 250
std::unique_ptr<arduinoDCfocus> arduinoDCfocus(new arduinoDCfocus());

Issues

/home/john/Projects/indi/libindi/drivers/focuser/arduinoDCfocus.cpp:37: error: expected type-specifier before 'arduinoDCfocus'
std::unique_ptr<arduinoDCfocus> arduinoDCfocus(new arduinoDCfocus());


So I have done some more exploring of the library and I have Googled.

I cannot see why this message occurs. Please help.

Read More...

VTVL replied to the topic 'KStars-Ekos-INDI upgrade on a 0.5 meter scope' in the forum. 1 year ago

The upgrade of the half meter telescope is a growing conversation within the club. Here is some text from a very experienced user of that instrument.
"I am happy to hear about the upcoming project, the future plans and the new job for our 20" Planewave instrument :)
Maybe I can help on questions concerning the normalisation/processing of exoplanet-photo(n)s ...
...and some programming techniques under Linux-Systems.

My idea (not sure if it could help): Have a look at the lazarus cross-compiler-technique, which is able to produce code for Android/Linux/Windows/Mac/Raspberry-Systems without having trouble with the different GUI low-level-interfaces, as they offer a huge object oriented library of already available GUI Interfaces, that can be used by "drag and drop" in a modern IDE.

www.pilotlogic.com/sitejoom/
You can call/bind/implement libraries of other languages too (i.e. your computing algorithms in C).

So you can focus on the algorithms and do not waste your time for GUI.
Example: The popular "cartes du ciel" planetarium software is completely written in lazarus and runs on different platforms and OS's."


So the point of my post here is to invite comment. Clearly there are people within the club with more software experience than myself. Clearly I like Linux-KStars-Ekos-INDI. It would be helpful to have more experienced comment from users of the various potential observatory control solutions.
Oleg's INDI Forum Thread "What can you say about Linux astro software forum? " is appreciated.
As I have been following Jasem's recent announcements and demonstrations including
knro.blogspot.de/2016/10/kstars-270-is-released.html Jasem's Ekosphere , ( and 2.7.1 demo) it appears that the team is catching up on many features and functionality.

Read More...

VTVL created a new topic ' KStars 2.7.1' in the forum. 1 year ago

Installed KStars 2.7.1 and GSC
When using the CCD simulation (and Focuser and Telescope simulations) there is "no WCS info". The path in KStars Ekos configuration says /usr/bin/wcsinfo but it does not exist.
The WCS box is checked.
Also solver: /usr/bin/solve-field is not correct.

When using WebServerManager connection via Tools - Devices localhost works. But disconnecting the devices, stopping the indiserver via WebServiceManager and then trying to start INDI via the Ekos panel fails "INDI Server failed to start: Permission denied".

Read More...

VTVL replied to the topic 'Developing Driver for Arduino' in the forum. 1 year ago

Jasem,
Thanks for the additional video.
Some learning observations with the QT Creater tool:

1)
Cannot configure via QT Tools/Options/ Build & Run the build dirctory WITH the build parameters in the lower field. So it is only home/john/Projects/build/generic-ccd/

2)
kdesudo -c “make install” is not correct for Ubuntu MATE 16.04
apt-get install kdesudo fixes this.

3)
Install the project...
-- Install configuration: "Release"
-- Installing: /usr/local/bin/indi_generic_ccd
Why is the path not /usr/bin for indi_generic_ccd ? I copied the file to the /usr/bin
-- Installing: /usr/share/indi/indi_generic_ccd.xml
This directory is correct.

4)
Debug Monitor Icon near bottom left of QT (above green run button) has indiserver
and indiserver(2) . I do not know why and I do not know how to delete indiserver(2).

I can however start the indiserver and the indi_generic_ccd .
The Run button invokes
/usr/bin/indiserver -v indi_generic_ccd
The snooping is reported in the application output window.
I can then confirm the start of indiserver and the indi_generic_ccd via connect via the Kstars-Tools-Device Manager Client Localhost port 7624. Then I see the panel for the generic_ccd which has Generic_ccd Model 1 and Generic_ccd Model 2.
The INDI Web Manager also works.

Read More...

VTVL created a new topic ' Developing Driver for Arduino' in the forum. 1 year ago

Lacking experienced with the tools; my goal is to produce drivers for some Arduino devices. The first project is a DC motor focuser. I know that there are templates for INDI Arduino drivers but first I must learn how to use the tools.

QtCreator 5.7.0 and related Qt tools are installed. Including Qt5Network. (But not Cmoc and Ctest) on Ubuntu MATE 16.04

Reference:
www.indilib.org/develop/developer-manual...ent-environment.html

So I have ~/Projects/indi directory structure

I also have ~/Projects/training where qt-tutorial-01 is stored. This tutorial gives a very basic grasp of how the Qt tool can be used.

I have read the INDI White Paper so that also teaches a lot.

After several hours of exploration and tests, some questions arise.

Is it possible to have KStars-Ekos using the indiserver etc. on the /Projects/indi/libindi-build path rather than the /usr/bin ? My attempts failed (using the webserver localhost:8264) when I disabled the /usr/bin/indiserver in favour of the /Projects/indi/libindi-build and rebooting….)

If this problem can be solved, then the next issue can be the availability of a “test driver” to add to the list to test in Ekos. I would start with the indi driver tutorial examples. How are these builds to be included in the list categories for device drivers? (Probably via the development environment configuration …..?)

Read More...

VTVL created a new topic ' KStars-Ekos-INDI upgrade on a 0.5 meter scope' in the forum. 1 year ago

Jasem,

I have been watching your YouTube KStars-Ekos-INDI demonstration and nice 4-09-2016 presentation videos. In the last few days I have been preparing a proposal for the steering committee of the local astronomy club which I joined recently (after my professional workload declined). The meeting is tomorrow evening. We have a half meter PlaneWave scope plus a 150 mm APO “guide-scope” on a Knopf GEM rated to 200 kg payload . Some of the members are very accomplished astro-photographers. In recent years the facility has become under-utilised. This can be understood as the observatory is in a relatively remote dark sky location in Germany. The users have had to camp in the building as remote operations are not supported. The proposal is a program to upgrade the dome automation and acquisition to systematically acquire data on exoplanets for AM to PRO support plus the public outreach which is quite well supported by the club.

Obviously, I will be advocating Linux-KStars-Ekos-INDI on RPI3s as an upgrade architecture.

Question: What is the potential for an INDI driver and EKOS support of a spectrograph such as the Shelyak spectrograph Lhires III ? The manufacturer’s web site says that it now supports remote operation.

We may develop some functional requirements for automation with regard to spectroscopy and photometry acquisition in an automated and remotely supervised and observed by members observatory.

Of course there is the Windose – Ascom barrier. I have no idea how much reluctance for change there may be when Linux-INDI is advocated.

– John

Read More...

VTVL created a new topic ' KStars 2.6.0 Planet Center & Track Bug' in the forum. 1 year ago

Hi,
I just allowed an automatic update for Ubuntu MATE 16.04 which included an update of KStars to 2.6.0 (previous version was 2.4.0). I soon discovered that Center & Track or Pointing / Find Object is incorrect for the planets. The RA is wrong by 180 degrees. The DEC is negative. The position of Jupiter or Venus is shown correct but the Center & Track menu command shifts the view to RA 0 and DEC 0 ! For the deep sky objects the function works correctly. For asteroids there is also concern. For example Pallas: Pointing / Find Object did not center on 21h 12m and 5° 20m but rather 12 h and 0 DEC. The coordinates given in the details window were correct but the Center in Map command resulted in 12 h and 0 DEC. The time was set so that the objects would be above the local horizon. The "requested position is below the horizon" message was given.
Also the Moon is not found.
Does anyone else see this behaviour?

regards, John

Read More...

VTVL replied to the topic 'indilx200gps crashed' in the forum. 1 year ago

Jasem,

As per your most recent suggestion "INDI is not installed correctly therefore the driver in not properly linked to the INDI base library. Please reinstall INDI on your maschine."

I did:
~$ sudo apt-get remove indi-full
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
dcraw dkms fliusb-dkms fxload indi-aagcloudwatcher indi-apogee indi-asi
indi-dsi indi-duino indi-eqmod indi-ffmv indi-fishcamp indi-fli indi-gphoto
indi-gpsd indi-maxdomeii indi-mi indi-qhy indi-qsi indi-sbig indi-sx
libapogee3 libboost-regex1.58.0 libfishcamp libfli1 libftdi1 libgps22 libqhy
libqsi7 libsbigudrv2
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
indi-full
0 upgraded, 0 newly installed, 1 to remove and 39 not upgraded.
After this operation, 8,192 B disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 188668 files and directories currently installed.)
Removing indi-full (1.2~201608250622~ubuntu16.04.1) ...
~$ sudo apt autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
dcraw dkms fliusb-dkms fxload indi-aagcloudwatcher indi-apogee indi-asi
indi-dsi indi-duino indi-eqmod indi-ffmv indi-fishcamp indi-fli indi-gphoto
indi-gpsd indi-maxdomeii indi-mi indi-qhy indi-qsi indi-sbig indi-sx
libapogee3 libboost-regex1.58.0 libfishcamp libfli1 libftdi1 libgps22 libqhy
libqsi7 libsbigudrv2
0 upgraded, 0 newly installed, 30 to remove and 15 not upgraded.
After this operation, 16.0 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 188665 files and directories currently installed.)
Removing indi-gphoto (1.4+r2604~201608231213~ubuntu16.04.1) ...
Removing dcraw (9.21-0.2) ...
Removing indi-fli (1.0.0ubuntu3+r2604~201608231222~ubuntu16.04.1) ...
Removing libfli1 (1.8.ubuntu5+r2604~201608231215~ubuntu16.04.1) ...
Removing fliusb-dkms (1.3+r2604~201608231207~ubuntu16.04.1) ...


Deleting module version: 1.3+r2604~201608231207~ubuntu16.04.1
completely from the DKMS tree.
Done.
Removing .....

Then i checked what was left in /usr/bin ---- the indi* files were still there, so I cut them and pasted them into the /home
Same for /usr/share/indi folder.

Then as per indilib.org/download/ubuntu.html
I installed with the commands:
~$ sudo apt-add-repository ppa:mutlaqja/ppa
Latest INDI Library and drivers!
More info: launchpad.net/~mutlaqja/+archive/ubuntu/ppa
Press [ENTER] to continue or ctrl-c to cancel adding it

gpg: keyring ....
OK
~$ sudo apt-get update
..
..
~$ sudo apt-get install indi-full
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
dcraw dkms fliusb-dkms fxload indi-aagcloudwatcher indi-apogee indi-asi
indi-dsi indi-duino indi-eqmod indi-ffmv indi-fishcamp indi-fli indi-gphoto
indi-gpsd indi-maxdomeii indi-mi indi-qhy indi-qsi indi-sbig indi-sx
libapogee3 libboost-regex1.58.0 libfishcamp libfli1 libftdi1 libgps22 libqhy
libqsi7 libsbigudrv2
Suggested packages:
gphoto2 gpsd
The following NEW packages will be installed:
dcraw dkms fliusb-dkms fxload indi-aagcloudwatcher indi-apogee indi-asi
indi-dsi indi-duino indi-eqmod indi-ffmv indi-fishcamp indi-fli indi-full
indi-gphoto indi-gpsd indi-maxdomeii indi-mi indi-qhy indi-qsi indi-sbig
indi-sx libapogee3 libboost-regex1.58.0 libfishcamp libfli1 libftdi1
libgps22 libqhy libqsi7 libsbigudrv2
0 upgraded, 31 newly installed, 0 to remove and 15 not upgraded.
.
.
.
.
In the /usr/bin/
there were only indi files which appear to be third parter.
There was no indiserver or indi_lx*
In the /usr/share/indi folder there were .xml files
Then I used
~$ sudo apt-get install libindi1
This added the indi_lx and other drivers plus the indiserver to /usr/bin
and apparently nothing extra in /usr/share/indi

Then I used the Indi web Manager from my PC to start the indiserver on the RPI3, aligned the LX-90, started KStars on the PC, used Device manager Client to connect to the RPI3. It worked.

CONCLUSION:
on the indilib.org/download/ubuntu.html page where it says:
To Install only INDI Library:

~$ sudo apt-get install libindi1

To Install INDI Library including all 3rd party drivers:

~$ sudo apt-get install indi-full

To install latest Ekos:

~$ sudo apt-get install indi-full kstars-bleeding

It should say:
To Install only INDI Library: FIRST

~$ sudo apt-get install libindi1

To Install INDI Library ONLY 3rd party drivers: SECOND

~$ sudo apt-get install indi-full

To install latest Ekos AND INDI Library AND INDI 3rd party drivers

~$ sudo apt-get install libindi1 indi-full kstars-bleeding

(I have not tested this last command.)

My problems occured because of the misleading instructions which resulted in not installing the indiserver and needed indi_lx200gps driver.

Read More...

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!