PixInsight Forum

PixInsight => Release Information => Topic started by: Juan Conejero on 2016 June 21 05:00:28

Title: INDIClient 1.0.15: New INDIMount Tool
Post by: Juan Conejero on 2016 June 21 05:00:28
Hi all,

Today we have released a new version of the INDIClient PixInsight module: 1.0.15, now available as a regular update for PixInsight 1.8.4 on FreeBSD, Linux, OS X and Windows.

This version comes with an exciting new tool: INDIMount. This tool allows you to control your telescope with features such as online catalog search, GoTo, Slew, Sync and Park functions, high-accuracy mean/apparent coordinate transformations, differential position corrections, fully scriptable process, and more. The new version also includes bug fixes and stability and performance improvements in the rest of INDIClient tools: INDIDeviceController and INDICCDFrame.

(http://forum-images.pixinsight.com/20160621/INDIMount.png)

INDIMount is really straightforward to use, as you can see in the above screenshot. However, there is much more under the surface that what you might expect from the simplicity of its user interface. One of our main goals with the development of these tools is to achieve the highest possible pointing accuracy. While our efforts can be clearly excessive to control small telescopes, they can be quite important for large telescopes and modern high-quality mounts, and are essential for the next generation of tools that we have planned within the INDIClient project. This includes generation and integration of astrometry-based pointing models, among other tasks.

When you search and select an astronomical object with the Online Coordinate Search dialog (see above), INDIMount computes the apparent position including corrections for proper motions (when available), stellar aberration, precession, nutation, and frame bias. The resulting apparent geocentric coordinates populate the coordinate fields on the GoTo section, and are sent to the selected INDI mount device for GoTo and Sync operations. Apparent coordinates are computed using accurate, rigorous algorithms. Our implementation is based on the IAU SOFA software library (http://www.iausofa.org/). In the current implementation we are not computing the corrections for parallax and radial velocity (which are very small in most cases; the largest parallax is smaller than 0.75 arcsec), and we are neglecting the effect of light bending. In the next version we'll include calculation of topocentric coordinates (which can be relevant for observation of near-Earth objects and the Moon), the effect of atmospheric refraction (very important, but neglected in this initial version for simplicity), and calculation of solar system ephemerides (using an integration of JPL development ephemerides with the PixInsight/PCL platform).

(http://forum-images.pixinsight.com/20160621/INDICCDFrame.png)

INDIMount and INDICCDFrame work cooperatively. When you acquire new client-side images and a telescope device is available (see INDICCDFrame's telescope device parameter), it is used to retrieve its current EOD (epoch of date) coordinates just before each exposure. These apparent coordinates are converted to ICRS J2000.0 mean positions by an inverse transformation. Once these coordinates are computed for each acquired image, they are stored as standard XISF properties (Observation:Center:RA and Observation:Center:Dec). For compatibility with legacy applications, as well as with tools and scripts still performing the transition from FITS keywords to XISF properties, the same coordinates replace the OBJCTRA and OBJCTDEC keywords provided by the INDI server.

The main advantages of this process are: (1) we always store mean J2000.0 positions in newly acquired images, which are directly comparable between different images and stellar catalogs, irrespective of the times of observation, and (2) we compute apparent and mean positions using very accurate and rigorous algorithms (IAU 2006 precession/nutation model and a rigorous stellar aberration model). As noted above, this is necessary for the implementation of future tools, including generation of pointing models.

INDIMount also has a very nice feature: differential pointing correction. To use this feature, follow this sequence of operations:

- Point your telescope to a desired location with INDI Mount Controller.

- Acquire an image with INDI CCD Controller.

- Solve the image astrometrically with the ImageSolver script.

- Launch a new instance of INDIMount (you know: INDI Mount Controller, click blue triangle, drag) to the image.

With this sequence, INDIMount will compute the difference between the observation coordinates (where the telescope thinks it's pointing to) and the actual pointing coordinates, then this difference will be applied to move the telescope from its current location. This feature is very useful to perform quick pointing corrections and/or to synchronize your mount at a known location.

Our next goals with the INDIClient project are:

- Improve the INDIMount and INDICCDFrame processes.

- Pointing model generation and integration.

- Autoguiding.

- Autofocus.

So stay tuned! As always, a huge thanks to Klaus Kretzschmar for his work on this project, to Vicent Peris for great development ideas, to the INDI developers for making all of this possible, and to all the users and friends that enthusiastically support us.
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: Buzz on 2016 June 21 07:51:19
Do these developments on INDI signal a departure from further developing PI processing tools? 

To be honest, I'm struggling with this INDI stuff. I have seen it about but never looked into it. I had to Google it and worked out its some form of Linux. I'm not a computer nubie, I have been using and developing computer/microcontroller systems since the days of CP/M. I am more a user than developer these days though, with only small forays into developing ASCOM drivers and utilities to automate my observatory.

Mine is not a professional observatory but it just works, is reliable and I cannot think of any major issues.  I am struggling with the concept of re-inventing the wheel and overcoming all the device interface issues once more .... and for what... to do what I already do today?

It may be exciting and all that - but what is the point?

The target market may be professional users - or those who just like the fun of creating stuff or just refuse to use Win/OSX.

Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: msmythers on 2016 June 21 08:18:09
Chris

You might want to check out this posting. http://pixinsight.com/forum/index.php?topic=9852.msg62410#msg62410 (http://pixinsight.com/forum/index.php?topic=9852.msg62410#msg62410)

Mike
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: Juan Conejero on 2016 June 21 08:54:02
Quote
Do these developments on INDI signal a departure from further developing PI processing tools?

Not at all. Why do you think so?

Quote
It may be exciting and all that - but what is the point?

As exciting as you want it to be. For example, what is the point of the whole PixInsight project? Isn't it a reinvention of the wheel, given that there are so many image processing applications out there? The answer to these questions is simple: we try to do it different, and better.

I'd like to understand exactly why each time we start a new project a lot of people gets invariably scared or annoyed. Please relax. There's no problem here. Hardware control is just another development project in PixInsight.
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: mschuster on 2016 June 21 09:00:53
Hi Juan,

- For GEM, need to set mount flip point to arbitrary (non-meridian) local hour angle. To allow tracking and/or slews into "upside down" position. Required for long-exposure narrow band exposure sequences. Initial exposure may be upside down and later exposures become rightside up, or alternatively initial exposures are rightside up and upside down state occurs towards end of exposure sequence. My current software in use extended to support this.

- For GEM with declination gear backlash, "all" slews need to "approach" target from a specified declination direction (north or south). Current situation: mount polar misaligned slightly so that declination drift is always in one direction, so declination backlash never needs to be unwound during exposure tracking. Initial slew prior to first exposure in sequence needs to result in a backlash unwound state. So slew approach direction is set appropriately based on polar misalignment direction. My current software in use extended to support this.

- Both of these are absolute requirements for me to obtain good tracking and efficient dark time utilization with my Takahashi EM-400 mount.

Thanks,
Mike
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: DrGkill on 2016 June 21 09:13:41
As exciting as you want it to be. For example, what is the point of the whole PixInsight project? Isn't it a reinvention of the wheel, given that there are so many image processing applications out there? The answer to these questions is simple: we try to do it different, and better.

Considering the high quality of your soft and comparing with the development quality of many astro software out there, I have no doubt you'll do better !
For my part, i'll certainly wait for the autoguiding part to be done but I can't wait for it !
Continue to do so neat job ! It's highly appreciated :)

N.B: Lot of my friends says PixInsight is expensive. I always tell them the price is truly cheap regarding the quality and the professionalism of the work you guys do.
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: msmythers on 2016 June 21 09:30:37
I get a kick out of the "PixInsight is expensive" argument that people use. I have one of the simplest setups you can have. A mirrorless camera, memory card, intervalometer, cheap scopes and lenses, a CG-5 and a DIY pier.   I don't guide, I don't use a computer for acquisition at the mount and PixInsight is still less then one tenth my astro equipment budget.


Mike   
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: mar504 on 2016 June 21 10:54:07
Just curious and may be jumping ahead here, but is Pixinsight planning to come up with its own autoguiding solution or interface with existing projects like PHD2 similar to how other acquisition packages do?
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: vicent_peris on 2016 June 21 11:25:10
Just curious and may be jumping ahead here, but is Pixinsight planning to come up with its own autoguiding solution or interface with existing projects like PHD2 similar to how other acquisition packages do?

Hi,

We will do everything on our own. The graphical interface in PixInsight (specially the multiple workspaces) is powerful enough. Forget the idea of having multiple applications running at the same time.


Best regards,
Vicent.
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: Buzz on 2016 June 21 11:34:55

As exciting as you want it to be. For example, what is the point of the whole PixInsight project? Isn't it a reinvention of the wheel, given that there are so many image processing applications out there? The answer to these questions is simple: we try to do it different, and better.

I'd like to understand exactly why each time we start a new project a lot of people gets invariably scared or annoyed. Please relax. There's no problem here. Hardware control is just another development project in PixInsight.

PixInsight does not reinvent the wheel on processing. It is a complete departure in functionality and originality. It is different and better - but takes some time to master.

There is no harm in starting new projects - I have several patents to my name. I'm not scared or annoyed but I'm interested in what the gain is.
Once a user can control their mount, guide and acquire images reliably- what is left to improve upon? As a hobby I recognize that some of the fun stuff is overcoming challenges but really... why would I deliberately set the clock back and go through debugging all over again? I use a NUC with SGP, TSX and PHD2. It just works. I'm sorry, I don't see the satisfaction of trying to squeeze it onto a Raspberry Pi or whatever.

Reading the other post, it seems that ASCOM is still required? Well, if you wanted to break new ground, I would start there. As a concept it is fine but its architecture is showing its age - for example to cope with multiple devices in an imaging array.
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: Nocturnal on 2016 June 21 12:25:15
Hi Juan,

- For GEM, need to set mount flip point to arbitrary (non-meridian) local hour angle. To allow tracking and/or slews into "upside down" position. Required for long-exposure narrow band exposure sequences. Initial exposure may be upside down and later exposures become rightside up, or alternatively initial exposures are rightside up and upside down state occurs towards end of exposure sequence. My current software in use extended to support this.

- For GEM with declination gear backlash, "all" slews need to "approach" target from a specified declination direction (north or south). Current situation: mount polar misaligned slightly so that declination drift is always in one direction, so declination backlash never needs to be unwound during exposure tracking. Initial slew prior to first exposure in sequence needs to result in a backlash unwound state. So slew approach direction is set appropriately based on polar misalignment direction. My current software in use extended to support this.

- Both of these are absolute requirements for me to obtain good tracking and efficient dark time utilization with my Takahashi EM-400 mount.

Thanks,
Mike

Hi Mike,

What software do you use at the moment? I use Chuck's ASCOM driver and I'm not sure it supports what you are describing. In any case, shouldn't your requirements be aimed at the INDI platform at its Temma driver? From what I've read it seems to be a bit underdeveloped at the moment.

Thanks,

   Sander
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: mschuster on 2016 June 21 12:49:34
Sander,

My own. Note Chuck's software does support Tak non-meridian flipping (at my request :-).

Quote
We will do everything on our own.

I need concurrent task execution support. My refocus software runs concurrently to autoguiding, measures a temperature probe mounted on tube, and updates FLI Atlas focuser a few microns at a time depending on temperature change every minute or so based on a calibrated model. Critical for tight stars on 40min Ha FSQ frames in changing ambient conditions at my sites.

Thanks,
Mike
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: vicent_peris on 2016 June 21 12:53:11
Sander,

My own. Note Chuck's software does support Tak non-meridian flipping (at my request :-).

Quote
We will do everything on our own.

I need concurrent task execution support. My refocus software runs concurrently to autoguiding, measures a temperature probe mounted on tube, and updates FLI Atlas focuser a few microns at a time depending on temperature change every minute or so based on a calibrated model. Critical for tight stars on 40min Ha FSQ frames in changing ambient conditions at my sites.

Thanks,
Mike

In the future you'll be able to send commands to a running PixInsight instance through the system shell.

V.
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: vicent_peris on 2016 June 21 12:55:08
Sander,

My own. Note Chuck's software does support Tak non-meridian flipping (at my request :-).

Quote
We will do everything on our own.

I need concurrent task execution support. My refocus software runs concurrently to autoguiding, measures a temperature probe mounted on tube, and updates FLI Atlas focuser a few microns at a time depending on temperature change every minute or so based on a calibrated model. Critical for tight stars on 40min Ha FSQ frames in changing ambient conditions at my sites.

Thanks,
Mike

OTOH, how does your software the concurrent refocus? Based only on temperature? Or by measuring the PSF? Or any other way?
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: Nocturnal on 2016 June 21 13:01:58
Hi Mike,

Yes, you are right of course that the Temma driver has the 'flip' command. I forgot about that.

Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: mschuster on 2016 June 21 13:16:57
Quote
OTOH, how does your software the concurrent refocus? Based only on temperature? Or by measuring the PSF? Or any other way?

Temperature only (i.e. an open loop controller). The temperature/focus drift model is good but not perfect. Refocuser runs for one 40 min exposure and then stops. A normal refocus is done between each exposure. So the refocuser starts from a known good point.

A ~2 micron focuser movement happens whenever temperature has changed 0.05°C which occurs on average every 2 minutes. With the Atlas, small movements help reduce lateral image shift (autoguided out) and improve overall tracking accuracy.

Mike
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: mschuster on 2016 June 21 14:37:15
Quote
Yes, you are right of course that the Temma driver has the 'flip' command. I forgot about that.

No, not a simple flip command, but rather a non-meridian flipping slew.

A normal slew across the meridian will flip a GEM to keep the scope on top. Need a slew where the flip point is the act of crossing any arbitrary local hour angle.

Suppose the flip point is two hours prior to the meridian, the GEM is slewed one hour prior, the scope ends up upside down. Now a small slew is done to target a nearby bright star for focusing purposes, the scope remains upside down (if less than two hours prior). Then a small slew back to the target. The scope remains upside down.

The maximum meridian flipping offset is limited to avoid any chance of crashing. On my setup within two hours is OK.

And to avoid backlash problems, all of these slews need to approach the target from the specified declination direction. This in general may require declination overshoot and backtrack by an amount larger than worst case backlash.

Thanks,
Mike
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: chris.bailey on 2016 June 21 14:41:44
Quote from: Buzz link=topic=9928.msg62949#msg62949 date=1466534095
Reading the other post, it seems that ASCOM is still required?
[/quote

Not true BUT importantly Indi has the ability to control an EQMod mount. It even works with my Bluetooth EQ dongle (under Windows, OSX and/or Linux).

Chris

ps Having Indi Server running on a Pi has a lot of benefit for low power consumption uses such as star parties. I have done a couple of sessions using other Indi Client software using Indi Server on a PI powered by a small phone charger battery (which happily powers it for 24hours).


Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: Nocturnal on 2016 June 21 14:48:28
Quote
Yes, you are right of course that the Temma driver has the 'flip' command. I forgot about that.

No, not a simple flip command, but rather a non-meridian flipping slew.

A normal slew across the meridian will flip a GEM to keep the scope on top. Need a slew where the flip point is the act of crossing any arbitrary local hour angle.

Suppose the flip point is two hours prior to the meridian, the GEM is slewed one hour prior, the scope ends up upside down. Now a small slew is done to target a nearby bright star for focusing purposes, the scope remains upside down (if less than two hours prior). Then a small slew back to the target. The scope remains upside down.

And to avoid backlash problems, all of these slews need to approach the target from the specified declination direction. This in general may require declination overshoot and backtrack by an amount larger than worst case backlash.

Thanks,
Mike

OK, that is useful, thanks. I will read up on how to do this.
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: passer_by on 2016 June 22 07:23:52
Hi!
Excuse for my English.
Use for GoTo in INDIMount online of catalogues strongly narrows possibilities of application INDIMount on the nature.
Whether there is a possibility to make connected catalogues from a hard disk? UCAC4, UCAC3?
Thanks,
Evgeniy
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: NKV on 2016 June 22 19:01:14
GoTo in INDIMount without internet is very important for me.
I use my equipment in mountains where is no any communication. No mobile, no electricity, and internet.
So, i can't use INDIMount. >:D   
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: Juan Conejero on 2016 June 23 00:25:56
Quote
So, i can't use INDIMount. >:D

Well, you _can_ enter equatorial coordinates manually in the GoTo section  8)

Local catalogs will be available in one of the next versions (probably in September). We are working to implement this functionality as soon as possible.
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: DrGkill on 2016 June 23 02:14:09
The thing missing in other product is the ability to take remote control via a true api.
When you're on the field, every Watt count and then a minimal hardware with a low power consumption remote control (phone or tablet) is a must.
If we could have something like that it would be great.

So :
Daemon without graphical interface (running on a Raspberry or Odroid device, controlling the mount)
A client on Android for remote control. (Or just an API allowing us to develop the client)
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: Juan Conejero on 2016 June 23 03:17:06
Quote
Daemon without graphical interface (running on a Raspberry or Odroid device, controlling the mount)

An INDI server on Raspberry is already a reality.

Quote
A client on Android for remote control.

Well, this clearly excludes PixInsight ;) Seriously, an INDI client with the functionality that we are going to implement in PixInsight is only possible on a desktop or laptop machine. I don't think that power consumption is really a problem nowadays. For example, the next generation of MacBook laptops is impressive in this regard. And PixInsight runs nicely on OS X...
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: Oleg Astro on 2016 June 23 04:09:23
We have the list of INDI clients (http://indilib.org/about/clients.html) for Android, Linux and so on.
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: Juan Conejero on 2016 June 23 04:25:22
In the list row for PixInsight, the column "Operating Systems" should be: FreeBSD, Linux, OSX, Windows.

On the other hand, although the PixInsight Core application is proprietary software, the INDIClient module is an open-source project released under a BSD-like license:

https://github.com/PixInsight/PCL/tree/master/src/modules/processes/contrib/kkretzschmar/INDIClient
https://github.com/PixInsight/PCL/blob/master/LICENSE.txt

IMO this is a very important fact that should be mentioned.
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: DrGkill on 2016 June 23 04:33:53
An INDI server on Raspberry is already a reality.

Yes but no descent API out there.

Well, this clearly excludes PixInsight ;) Seriously, an INDI client with the functionality that we are going to implement in PixInsight is only possible on a desktop or laptop machine. I don't think that power consumption is really a problem nowadays. For example, the next generation of MacBook laptops is impressive in this regard. And PixInsight runs nicely on OS X...
The Mac book still consume about 30 to 40W compared to the 2W consumed by an Odroid or a Raspberry, it makes a huge difference.
A Raspberry can be powered during more than 10 hours with a small and light 13AH Li-Ion battery.
Plus the fact the Mac book is very expensive (~$1000-2000) compared to the $30 raspberry. Drive a mount and autoguide doesn't need so much CPU power.
For me bringing a laptop to the field is always a pain in the ass, it's the device consuming 80% of my battery. I really think mount driving and autoguiding could be done much cleverly.

I can't imagine I'm the only one that have had to give up a session because the laptop is gone, and when you live in a city like me and have to do hundreds of kilometer to have a nice sky, an aborted session is more than frustrating.
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: DrGkill on 2016 June 23 04:34:49
We have the list of INDI clients (http://indilib.org/about/clients.html) for Android, Linux and so on.

Thanks !
Just need now autoguiding client. Tryed Starspi but it's not stable at all.
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: Oleg Astro on 2016 June 23 04:38:03
In the list row for PixInsight, the column "Operating Systems" should be: FreeBSD, Linux, OSX, Windows.

On the other hand, although the PixInsight Core application is proprietary software, the INDIClient module is an open-source project released under a BSD-like license:

https://github.com/PixInsight/PCL/tree/master/src/modules/processes/contrib/kkretzschmar/INDIClient
https://github.com/PixInsight/PCL/blob/master/LICENSE.txt

IMO this is a very important fact that should be mentioned.
Ok. No problem.
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: Juan Conejero on 2016 June 23 04:49:15
Thank you, Oleg!
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: Oleg Astro on 2016 June 23 04:50:56
DrGkill,
you can install the Open PHD Guiding (https://github.com/OpenPHDGuiding) and other INDI clients for Linux on your Raspberry Pi or Odroid.
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: Juan Conejero on 2016 June 23 04:59:21
Quote
For me bringing a laptop to the field is always a pain in the ass, it's the device consuming 80% of my battery. I really think mount driving and autoguiding could be done much cleverly.

I understand your power requirements to operate in the field. However, our INDIClient module is an ambitious project. We pursue levels of functionality, flexibility, automation and accuracy that certainly require processing power. On the other hand, INDIClient is a PixInsight module, fully integrated with the PixInsight platform, and PixInsight does not run (and won't run in the foreseeable future) on small portable devices.

Quote
Tryed Starspi but it's not stable at all.
Quote
... and other INDI clients for Linux on your Raspberry Pi or Odroid.

This forum is about PixInsight and this thread is about the development of a PixInsight INDI client module, so let's keep the discussion on-topic as much as possible.
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: Oleg Astro on 2016 June 23 05:13:26
....
This forum is about PixInsight and this thread is about the development of a PixInsight INDI client module, so let's keep the discussion on-topic as much as possible.
Users can find more information about the INDI on its site (http://indilib.org) and forum (http://indilib.org/forum.html).
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: Oleg Astro on 2016 June 23 05:52:18
Hi!
Excuse for my English.
Use for GoTo in INDIMount online of catalogues strongly narrows possibilities of application INDIMount on the nature.
Whether there is a possibility to make connected catalogues from a hard disk? UCAC4, UCAC3?
Thanks,
Evgeniy
Wait...
What problem you want to solve with UCAC catalogs?
Maybe, you need some "handmade" DSO catalog:
Code: [Select]
IC 1396 21h39m36.51s +57°34'28.0" C+N m: 3.50 Dim: 89.0 x 89.0'
M 39 21h32m47.48s +48°30'22.2" OC m: 4.60 Dim: 32.0 x 32.0'
M 52 23h24m56.05s +61°40'23.8" OC m: 6.90 Dim: 13.0 x 13.0'
M 74 01h37m34.83s +15°51'58.7" Gx m: 9.40 Dim: 10.0 x 9.4'
M 110 00h41m17.74s +41°46'22.6" Gx m: 8.10 Dim: 19.5 x 11.5'
M 32 00h43m35.83s +40°57'22.0" Gx m: 8.10 Dim: 8.5 x 6.5'
M 31 00h43m35.88s +41°21'22.0" Gx m: 3.40 Dim:189.0 x 61.0'
Stock 2 02h15m52.95s +59°33'32.3" OC m: 4.40 Dim: 60.0 x 60.0'
M 76 01h43m20.26s +51°39'55.3" Pl m:10.10 Dim:163.0 x107.0"
M 33 01h34m49.48s +30°44'00.4" Gx m: 5.70 Dim: 68.7 x 41.6'
Cr 464 05h14m40.82s +73°59'05.8" OC m: 4.20 Dim:120.0 x120.0'
M 103 01h34m29.80s +60°44'00.6" OC m: 7.40 Dim: 6.0 x 6.0'
M 77 02h43m32.29s +00°03'08.2" Gx m: 8.90 Dim: 7.3 x 6.3'
M 45 03h47m58.49s +24°09'59.1" C+N m: 1.20 Dim:100.0 x100.0'
M 34 02h43m09.48s +42°51'08.6" OC m: 5.20 Dim: 35.0 x 35.0'
Mel 20 03h25m28.51s +49°55'25.3" OC m: 1.20 Dim:185.0 x185.0'
M 79 05h24m52.44s -24°30'09.5" Gb m: 7.70 Dim: 7.8 x 7.8'
M 42 05h36m06.24s -05°22'25.3" C+N m: 4.00 Dim: 90.0 x 60.0'
M 43 05h36m18.29s -05°15'25.6" Nb m: 7.00 Dim: 20.0 x 15.0'
Cr 70 05h36m49.91s -00°59'26.3" OC m: 0.40 Dim:150.0 x150.0'
Cr 69 05h36m00.09s +09°56'34.9" OC m: 2.80 Dim: 65.0 x 65.0'
Sh2-264 05h37m12.12s +10°00'33.2" Nb m: 5.00 Dim: 70.0 x 70.0'
M 78 05h47m38.32s +00°05'18.3" Nb m: 8.00 Dim: 8.0 x 6.0'
M 1 05h35m29.07s +22°01'35.7" Nb m: 8.40 Dim: 8.0 x 4.0'
IC 2602 10h43m29.26s -64°29'09.5" OC m: 1.90 Dim:100.0 x100.0'
IC 2944 11h38m40.16s -63°26'26.3" C+N m: 4.50 Dim: 60.0 x 35.0'
Cr 132 07h16m02.02s -30°42'46.3" OC m: 3.60 Dim: 80.0 x 80.0'
Cr 140 07h25m07.62s -31°52'58.5" OC m: 3.50 Dim: 60.0 x 60.0'
M 41 06h46m42.17s -20°46'05.8" OC m: 4.50 Dim: 38.0 x 38.0'
M 50 07h03m17.18s -08°24'28.8" OC m: 5.90 Dim: 16.0 x 16.0'
M 47 07h37m21.13s -14°31'14.6" OC m: 4.40 Dim: 30.0 x 30.0'
M 46 07h42m33.06s -14°51'21.3" OC m: 6.10 Dim: 27.0 x 27.0'
M 93 07h45m11.61s -23°53'24.8" OC m: 6.20 Dim: 22.0 x 22.0'
M 35 06h09m54.17s +24°20'46.6" OC m: 5.10 Dim: 28.0 x 28.0'
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: DrGkill on 2016 June 23 09:42:52
I understand your power requirements to operate in the field. However, our INDIClient module is an ambitious project. We pursue levels of functionality, flexibility, automation and accuracy that certainly require processing power. On the other hand, INDIClient is a PixInsight module, fully integrated with the PixInsight platform, and PixInsight does not run (and won't run in the foreseeable future) on small portable devices.

I understand I'm not the target of your module, sorry to have bothered you.
But just to say, small portable devices are more and more powerful and are definitely the future. Making things compatible with them (ARM compatible) will be a near future mandatory thing.

This forum is about PixInsight and this thread is about the development of a PixInsight INDI client module, so let's keep the discussion on-topic as much as possible.

Pixinsight is entering in competition with other products. It's positive to compare for making a good product.
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: Juan Conejero on 2016 June 23 13:48:40
Vicent has raised my attention to the UDOO x86 project:

https://www.kickstarter.com/projects/udoo/udoo-x86-the-most-powerful-maker-board-ever

It seems that this device will be able to run PixInsight on Linux without any problem. As soon as we can get one, I'll start making tests. With one of these, you can run an INDI server and PixInsight as a client on the same machine, then connect with a laptop through a wireless network when necessary, just to point the telescope and start an acquisition sequence. Very promising...
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: pfile on 2016 June 23 15:52:05
while nowhere near as cheap, intel is now selling non-atom versions of the compute stick.

having said that i'm running my imaging rig on the atom-based compute stick with no problem. 2GB of ram, 32-bit windows home, ascom, sequence generator pro, astrometry.net, etc. clearly PI won't run on that hardware, but right now i am successfully doing image acquisition with this device. idle consumption: 2W.

rob
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: mcgillca on 2018 April 11 07:41:40
Vicent has raised my attention to the UDOO x86 project:

https://www.kickstarter.com/projects/udoo/udoo-x86-the-most-powerful-maker-board-ever

It seems that this device will be able to run PixInsight on Linux without any problem. As soon as we can get one, I'll start making tests. With one of these, you can run an INDI server and PixInsight as a client on the same machine, then connect with a laptop through a wireless network when necessary, just to point the telescope and start an acquisition sequence. Very promising...

Hi - I got one of these last week. I haven't tried it under the stars yet (weather poor), but I have used it to run The Sky X with simulated mount, camera etc - works very well and takes about 5W - a little more than the 3-4W for the Pi and Odroid XU4, but not signifcantly.

PixInsight seems to run fine - my board is the advanced plus with 4GB and I have an M.2 SSD. Timing a few things it takes about 5 times as long as on my desktop PC, which has a PixInsight benchmark score of about 6000.

I don't plan to use the Indi driver with this (I wrote a couple of X2 drivers so that I could use my equipment with a Pi running TSX), but I do think it would work well with INDI and PixInsight.

Colin
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: kkretzsch on 2018 May 19 10:49:35
Hi Colin,
good to know thanks! Just to clarify, the indiserver itself runs fine even on a raspberry pi 2. If you use a pi with ubuntu mate it is very easy to install and upgrade all the required indi software.

Klaus
Title: Re: INDIClient 1.0.15: New INDIMount Tool
Post by: EastWind on 2018 June 01 21:39:25

I use a 195AH marine battery now and i can run all night and have enough juice to make coffee in the morning.  Seriously if you have power needs, just buy a bigger battery or several of them.

Keep up the great work Juan. I know this will develop over time.  All suggestions should be taken positively.  Everyone has their unique needs and wants and their consideration should be no less than anything else.  :). Maybe someday i can ditch all of these other buggy apps and just use this for all of my needs.

Quote
Daemon without graphical interface (running on a Raspberry or Odroid device, controlling the mount)

An INDI server on Raspberry is already a reality.

Quote
A client on Android for remote control.

Well, this clearly excludes PixInsight ;) Seriously, an INDI client with the functionality that we are going to implement in PixInsight is only possible on a desktop or laptop machine. I don't think that power consumption is really a problem nowadays. For example, the next generation of MacBook laptops is impressive in this regard. And PixInsight runs nicely on OS X...