han replied to the topic 'INDI for accessing astrometric solving (plate solving)' in the forum. 4 months ago

There is no need to upgrade CCDCIEL => ASTAP interface. That works fine. Adding INDI device driver between could add remote solving but there is no need for. Both programs can run locally in one system like PI3 or Linux laptop/desktop. An INDI device will most likely also delay the solving since the file will be transferred as a binary package.

After this discussion, I tend now to leave any INDI device driver development to the developers of Kstars/Ekos or MacOS applications (if they have interest). Introducing ASTAP as solver will beneficial for having an alternative to Astrometry.net and secondly in most cases ASTAP will solve faster if the image center position is known within maybe 10 degrees.

Han

Read More...

han replied to the topic 'INDI for accessing astrometric solving (plate solving)' in the forum. 4 months ago

stash wrote: Could you no "cheat" and just replace the existing platesolver EXE with a script


Now interfacing the stacker that would be another thing - one module I haven't found on Indi - or have I just missed the module ???


Probably a script could work, but there seems no need for, since you can specify path, solver name and parameters in the remote Astrometry.net setup. That is what understand from the screens shots. In principle if the input is a fits file, it would only require the fits file name as parameter. Other details like field of view, initial position will be extracted from the fits file header. So the complete command line could be something like

/opt/astap/astap -f ~/fitsfile.fits

The parameters (binning, search field...) can be configured in the program and will be saved if you leave the program via file, exit.

At the moment, I have no INDI setup (only Windows & ASCOM) so testing using INDI is a little difficult. I could setup my raspberry PI3 but at the moment it is only used as a development tool.

No INDI interface was ever foreseen or planned for the stacker part of the program. The solver engine was developed as an essential part for the stacker. It can be used for mosaic building. Since it works so well a solver command line interface was added to the program.

Han

Read More...

han replied to the topic 'Re:INDI for accessing astrometric solving (plate solving)' in the forum. 4 months ago

That looks like the way to go. One of the outputs of ASTAP is a WCS file (= solved fits file header only) with the solution which should be compatible with Astrometry.net output. Looking around in the forum, the interface looks very compatible:

https://www.indilib.org/media/kunena/attachments/3974/Capturadepantalla2017-10-31alas11.26.55.png

Rather then the path to solve-field you have to enter the path to the astap executable. The parameters are also different.

I'm exclusively programming in Object Pascal, so I have to leave the tweaking of the existing driver "c" code to others.

Local access in Kstars will be more work. There is no astrometry.cfg file.

www.indilib.org/media/kunena/attachments...10-29at2.02.26PM.png

Han

Read More...

han created a new topic ' INDI for accessing astrometric solving (plate solving)' in the forum. 4 months ago

As you maybe know, the ASTAP program is available for Linux (AMD64), Raspberry PI (armhf) and MacOS. Part of the program is an astrometric solver (plate solver). Access is available via the command line . The command line is universal and easy to implement.

At the moment, I'm asking myself, would there be any benefit of implementing an additional INDI interface in ASTAP for accessing the solver.. The number of potential clients will be limited. What you could do is provide a web service similar as nova.astrometry.net but INDI driven. Note that ASTAP is also a viewer and stacking program.

At the moment only CCDCIEL has ASTAP command line interface implemented. I expect one or two Window image acquisition applications to implement the command line interface soon.

Any thoughts on this INDI solver interface? Is an INDI binary transfer fast enough?

Han

Read More...

han replied to the topic 'Astroberry Server' in the forum. 5 months ago

I'm not familiar with PPA, but there is no repository available for updates. Both programs are provided a Debian package for installation at armhf (32 bit). The large star databases (mag 16, mag 17) are also provided as Debian package or zip file. The mag 18 star database is only provided as zip file.

Compiling for arm 64 bit is outstanding, but I had too many problems in setting up the compiler (object pascal, Lazarus/FPC) for 64 bit. That initiative is put on hold. I think 64bit is rare for arm processor systems so has no priority.

If somebody could set up a repository or tell me about an existing which I could use, that would be nice.

The easiest solution would be using the latest Astroberry image with everything installed. That is the core idea. But you have to setup your personal settings again.

Read More...

Tom thanked han in topic Astroberry Server 5 months ago

han replied to the topic 'Astroberry Server' in the forum. 5 months ago

Great!

Note to make CCDciel (imaging) complete you could add ASTAP for Raspberry PI as an astrometric solver/plate solver requiring only about 500 mbytes disk space. This as an alternative to Astrometry.net.

Astrometric solving is very convenient and makes accurate alignment unnecessary. You will find any faint blob with pinpoint accuracy. :)

Read More...

han created a new topic ' HNSKY, INDI client overhauled' in the forum. 8 months ago

FYI, the INDI client of the Hallo Northern Sky (HNSKY) planetarium has been overhauled. Any feedback is welcome

Han


Download at:
www.hnsky.org/software.htm
or very soon from from Ubuntu Astronomy repository.

The INDI client is fully written in Object Pascal (Lazarus/FPC) without any library and available as Pascal source.



Read More...

Jarno Paananen thanked han in topic Driver usb-focus V.3 8 months ago

han replied to the topic 'Driver usb-focus V.3' in the forum. 8 months ago

Here is the link to the USB-Focus ASCOM source code:

https://bitbucket.org/usb-focus/ascom-driver/src/master/

Vincent requested: "Please commit your modifications for the benefit of the community.",so for any suggestion for improvement, please contact him at www.usb-foc.us

The plan was to study it to fix a small timing problem, but due too many other topics this was never completed.

Han

Read More...

han replied to the topic 'Driver usb-focus V.3' in the forum. 8 months ago

That helps. :)

sudo apt-get remove modemmanager

Can this be documented or is it? Will add this to the review.

Now things starting working again including my bluetooth connection. Waisted too much time on this.

I noted that the focus position is not from the focuser but from the software. So it starts at zero.

An other generic remark for INDI is that scan port doesn't detect bluetooth serial ports, so in my case /dev/rfcomm0

Read More...

han replied to the topic 'Driver usb-focus V.3' in the forum. 8 months ago

Note the source code of the ASCOM driver was released a few months ago on request. Will get the link.

This is what I get from driver INDI USB-focus driver v1.0 with an USB connection without any hub:

DEBUG 95.685214 sec : Connecting to /dev/ttyACM0
DEBUG 95.690443 sec : Port FD 4
DEBUG 95.690585 sec : Connection successful, attempting handshake...
DEBUG 95.690639 sec : CMD: SWHOIS.
DEBUG 95.715846 sec : RES: ER=(SWHOIS.
DEBUG 95.741077 sec : CMD: SWHOIS.
ERROR 98.768667 sec : Error reading focuser ID: Timeout error.
INFO 98.768808 sec : Error retreiving data from USB Focus V3, please ensure USB Focus V3 controller is powered and the port is correct.
DEBUG 98.768894 sec : Handshake failed.
WARNING 98.768931 sec : Communication with /dev/ttyACM0 @ 9600 failed. Starting Auto Search...
DEBUG 98.768982 sec : Trying connection to /dev/ttyACM0 @ 9600 ...
DEBUG 98.769021 sec : Connecting to /dev/ttyACM0
DEBUG 98.770617 sec : Port FD 5
DEBUG 98.770764 sec : Connection successful, attempting handshake...
DEBUG 98.770812 sec : CMD: SWHOIS.
ERROR 101.799076 sec : Error reading focuser ID: Timeout error.
INFO 101.799233 sec : Error retreiving data from USB Focus V3, please ensure USB Focus V3 controller is powered and the port is correct.
DEBUG 101.799321 sec : Handshake failed.

Read More...

han replied to the topic 'Driver usb-focus V.3' in the forum. 8 months ago

polakovic wrote: Hi Greg, I made new packages and put them here: http://www.cloudmakers.eu/usbfocus


Hello, this is an old discussion but driver 0.9 from Cloudmakers worked for me, but latest v1.0 not. Version 1.0 can't connect in 99% of the cases.
Version 1.0 was downloaded as indi all drivers.

Port is /dev/ttyACM0 The cloudmakers version 0.9 worked immediately, so I'm happy again, thanks. Same for the Windows drivers under Windows. So I have the impression it is timing problem introduced between version 0.9 and 1.0. See log below. Any idea why?

Han

Version 0.9
Server connected
DEVICE_PORT PORT= /dev/ttyACM0
CONNECTION CONNECT=ON
USB Focus is connected on /dev/ttyACM0.


Version 1.0
Server connected
CONNECTION CONNECT=ON
[ERROR] Error reading focuser ID: Timeout error.
[INFO] Error retreiving data from USB Focus V3, please ensure USB Focus V3 controller is powered and the port is correct.
[WARNING] Communication with /dev/ttyACM0 @ 9600 failed. Starting Auto Search...
[ERROR] Error reading focuser ID: Timeout error.
[INFO] Error retreiving data from USB Focus V3, please ensure USB Focus V3 controller is powered and the port is correct.


Read More...