Andrew replied to the topic 'Image geometry different when using native versus fits?' in the forum. 2 weeks ago

Hi Jasem, Magnus,
This looks like same libraw bug (see indilib.org/forum/ccds-dslrs/1895-dslr-i....html?start=12#16190 ) that I stumbled upon a year ago.
I can verify from this weeks session it is still present i.e. with Canon 60Da some FITs files (bias and flat) have different dimensions to lights 5202 vs 5184 and makes processing a mess.
I can understand a longstanding bug in libraw, but why does it impact say bias and not light exposures from INDI?

If we want to stay only with FITs workflow is the subframe workaround i.e. add 5202-5184 = 18 still the only option?
Andrew

Read More...

Andrew replied to the topic 'Did EKOS guider option 'via' change?' in the forum. 2 weeks ago

Just to reconfirm that all working fine - first time use of internal guide 'via' lodestar worked all night.
Option Via skysensor also available , I'll test tomorrow.

Read More...

Andrew replied to the topic 'Did EKOS guider option 'via' change?' in the forum. 3 weeks ago

hello Jasem,
I upgraded to latest versions on server and client and can see indi-sx is 1.12-20180203 for example.
But I still cannot select 'skysensor' using the 'via' field in the EKOS guider options, it remains as just one choice 'SX CCD Lodestar'.
I assume that I should be able to choose to guide via RS232 or ST4 right?
I see Skysensor is online and I can use INDI control panel to Motion Control the scope so the RS232 is working.
Let me know if you need some logs.
Andrew

Read More...

Andrew replied to the topic 'Did EKOS guider option 'via' change?' in the forum. 3 weeks ago

Well jasem, I'm not sure who disabled but you re-enabled it , see #15105. Hopefully I can try the new ppa tomorrow and I'll feedback.
Andrew


indilib.org/forum/mounts/1821-skysensor2....html?start=12#15105

Read More...

Andrew replied to the topic 'Did EKOS guider option 'via' change?' in the forum. 4 weeks ago

Thanks Jasem, will check, maybe by this weekend and happy to find that issue.

While I have your ear - in the past when we looked at these Skysensor driver issues you mentioned that pulse driving had been deactivated, you switched it back along with a precision parameter too. Could you just double check and reconfirm that it is still enabled?

Read More...

Andrew replied to the topic 'Did EKOS guider option 'via' change?' in the forum. 4 weeks ago

Thanks rlancaste, that is clear and understood regarding PHD. Can't wait to see it in action.

Read More...

Andrew replied to the topic 'Did EKOS guider option 'via' change?' in the forum. 4 weeks ago

I think I saw some of your work PHD output in EKOS, it looked very nice since the graphics needed some work, but I didn't see it yet working.:-( , hopefully I will soon and can contribute some feedback.

My previous issues were from a year ago, Jan 2017, and were specific to using PHD and the Skysensor in serial (RS232) mode, PHD setup with no 'on-camera' setting so that SX CCD as guider and mount as Skysensor. But actually I had same problem with 'internal' guider. I still suspect the skysensor driver has minor bug in guiding.
The link I gave ( www.indilib.org/forum/mounts/1821-skysen...dec-not-in-logs.html ) is the whole debug story.

I keep sane because I can still switch back to windows/ASCOM without touching the system and happily guide BUT INDI/EKOS is a better system overall.

Read More...

Andrew replied to the topic 'Did EKOS guider option 'via' change?' in the forum. 4 weeks ago

Thanks for looking Jasem, the problem is that there is no selection, the box is pre-filled with SX CCD and no selection is proposed.
I know in the past I could select either SX CCD or Skysensor.

Read More...

Andrew replied to the topic 'Did EKOS guider option 'via' change?' in the forum. 4 weeks ago

Well I did select "Guiding:Internal" in the Profile editor, saved and connected as usual. Normally this would be set to PHD.
I double checked just now to see if the setting was saved, it is. I did log the whole session, would that be useful?

Read More...

Andrew created a new topic ' Did EKOS guider option 'via' change?' in the forum. 4 weeks ago

I had some problems again guiding via ST-4 using PHD2 and lin_guider from Raspberrypi (setup below).

ITrying to debug decided to try the serial cable using EKOS 'intrernal guide' knowing that II never resolved the issues last year (link below).

However I couldn't get to testing because I cannot choose 'via' option in the EKOS guide tab, I want

'via : SKYSENSOR'

It will only allow me to set:-

'via : SX CCD LODESTAR'

The skysensor loads in EKOS correctly and I can move the mount via EKOS mount control. I've set the skysensor to 'guider OFF' and even pulled the ST-4 cable out. I see in the EKOS log screen that ' Guider port from SX CCD LodeStar is ready'

Am I missing something or is this option no longer available i.e. guide via serial cable?

Thanks
Andrew


setup Jan 18
========================
Client side
Ubuntu 17.10 (linux 4.13.0.32)
Kstar 2.9.2 Kstars-bleeding 5:17.12
Libindi1 1.6.3

Server via wifi Raspberrypi 2 - Ubuntu 16.04 powered USB hub
Libindi 1.6.3
indi-gphoto 1.6
indi-sx 1.12

(sudo indiserver -vvv indi_gphoto_ccd indi_sx_ccd indi_lx200ss2000p)

Orion Optics 200mm F/4 SN with GP-DX mount
Skysensor2000pc, RS232 serial/USB FTDI converter
Canon 60Da
Vixen 60mm F/7
Lodestar x2 autoguide custom ST-4 cable into SS2k


old issue last year:
www.indilib.org/forum/mounts/1821-skysen...dec-not-in-logs.html

Read More...

Andrew replied to the topic 'E: Unable to locate package kstars-bleeding' in the forum. 9 months ago

solved in the end by forcing overwrite

dpkg -i --force-overwrite /var/cache/apt/archives/libindi1_1.4.1+r3091~201705210923~ubuntu16.10.1_amd64.deb

thanks oir support and development

Read More...

Andrew replied to the topic 'E: Unable to locate package kstars-bleeding' in the forum. 9 months ago

hi jasem, i tried all purges including your combination and with synaptic package manager but still get a loop, which made me think it was still an issue rather then my linux skills. I still get a conflict between libindi1 and libindidriver

sudo apt-get purge libindi1 indi-bin libindidriver1
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'libindi1' is not installed, so not removed
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies.
indi-aagcloudwatcher : Depends: libindi1 but it is not going to be installed
indi-apogee : Depends: libindi1 but it is not going to be installed
indi-asi : Depends: libindi1 but it is not going to be installed
indi-dsi : Depends: libindi1 but it is not going to be installed
indi-duino : Depends: libindi1 but it is not going to be installed
indi-eqmod : Depends: libindi1 but it is not going to be installed
indi-ffmv : Depends: libindi1 but it is not going to be installed
indi-fishcamp : Depends: libindi1 but it is not going to be installed
indi-fli : Depends: libindi1 but it is not going to be installed
indi-full : Depends: libindi1 (>= 1.2) but it is not going to be installed
Depends: indi-bin (>= 1.2) but it is not going to be installed
indi-gphoto : Depends: libindi1 but it is not going to be installed
indi-gpsd : Depends: libindi1 but it is not going to be installed
indi-maxdomeii : Depends: libindi1 but it is not going to be installed
indi-mi : Depends: libindi1 but it is not going to be installed
indi-nexstarevo : Depends: libindi1 but it is not going to be installed
indi-qhy : Depends: libindi1 but it is not going to be installed
indi-qsi : Depends: libindi1 but it is not going to be installed
indi-sbig : Depends: libindi1 but it is not going to be installed
indi-sx : Depends: libindi1 but it is not going to be installed
kstars-bleeding : Depends: libindi1 but it is not going to be installed
Depends: indi-bin but it is not going to be installed
libindi-dev : Depends: libindi1 (= 1.4.1+r3089~201705200923~ubuntu16.10.1) but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (

Read More...

Andrew replied to the topic 'E: Unable to locate package kstars-bleeding' in the forum. 9 months ago

tested with Ubuntu 16.10, Kstars runs but I still see a dependency error libindi1, not sure if it's my setup or more generic:-

sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
libindi1
The following NEW packages will be installed
libindi1
0 to upgrade, 1 to newly install, 0 to remove and 9 not to upgrade.
24 not fully installed or removed.
Need to get 0 B/254 kB of archives.
After this operation, 903 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 449237 files and directories currently installed.)
Preparing to unpack .../libindi1_1.4.1+r3089~201705200923~ubuntu16.10.1_amd64.deb ...
Unpacking libindi1:amd64 (1.4.1+r3089~201705200923~ubuntu16.10.1) ...
dpkg: error processing archive /var/cache/apt/archives/libindi1_1.4.1+r3089~201705200923~ubuntu16.10.1_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libindidriver.so.1', which is also in package libindidriver1:amd64 1.2.0-2~ubuntu2
Errors were encountered while processing:
/var/cache/apt/archives/libindi1_1.4.1+r3089~201705200923~ubuntu16.10.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Read More...

Andrew replied to the topic 'E: Unable to locate package kstars-bleeding' in the forum. 9 months ago

I just got same with ubuntu 16.10, unable to locate kstars-bleeding. Seems a fix is required in latest updates.

Read More...

Andrew replied to the topic 'dslr - image info' in the forum. 10 months ago

sorry forgot the exiftool comand is
$ exiftool -CameraTemperature /home/andrew/Pictures/indi/Light/*.cr2

Read More...

Andrew replied to the topic 'dslr - image info' in the forum. 10 months ago

I confirmed a session recording as FITs and adjustig the first image (discarded) manually set at 5184x3456. Its a bit fiddly and I'm sure I'll forget sometime but it does work.

Also Jasem, just a note about the Canon camera temperature record it is readily extracted using the exiftool (by P Harvey). I've used it in a Raspberry Pi project to manipulate EXIf data sets to great effect. I did a quick test on the FITs data but it didn't work, however it quicly extracted my last CR2 session, see below. Thus for me a quick script and file rename inserting the temperature is fine but maybe you can find a way to incorporate into the EKOS flle save routing.

I suppose it's valid for all Canon EOS and although not super accurate (measures digic chip temp?) it does enable some classification and is certainly relatively stable, these below were recorded at ambient 4-5C with 1 minute cool/dither.

======== /home/andrew/Pictures/indi/Light/IC446_Light_240_secs_2017-03-24T21-20-15_001.cr2
Camera Temperature : 8 C
======== /home/andrew/Pictures/indi/Light/Light_001.cr2
Camera Temperature : 8 C
======== /home/andrew/Pictures/indi/Light/Light_002.cr2
Camera Temperature : 10 C
======== /home/andrew/Pictures/indi/Light/Light_003.cr2
Camera Temperature : 10 C
======== /home/andrew/Pictures/indi/Light/Light_004.cr2
Camera Temperature : 11 C
======== /home/andrew/Pictures/indi/Light/Light_005.cr2
Camera Temperature : 12 C
======== /home/andrew/Pictures/indi/Light/Light_006.cr2
Camera Temperature : 13 C
======== /home/andrew/Pictures/indi/Light/Light_007.cr2
Camera Temperature : 13 C
======== /home/andrew/Pictures/indi/Light/Light_008.cr2
Camera Temperature : 11 C
======== /home/andrew/Pictures/indi/Light/m44-dith_Light_120_secs_2017-03-24T23-21-40_001.cr2
Camera Temperature : 8 C
======== /home/andrew/Pictures/indi/Light/m44-dith_Light_120_secs_2017-03-24T23-24-26_002.cr2
Camera Temperature : 10 C
======== /home/andrew/Pictures/indi/Light/m44-dith_Light_120_secs_2017-03-24T23-27-20_003.cr2
Camera Temperature : 10 C
======== /home/andrew/Pictures/indi/Light/M44_Light_120_secs_2017-03-24T21-49-46_001.cr2
Camera Temperature : 8 C
======== /home/andrew/Pictures/indi/Light/M44_Light_120_secs_2017-03-24T21-58-08_002.cr2
Camera Temperature : 9 C
======== /home/andrew/Pictures/indi/Light/M44_Light_120_secs_2017-03-24T22-03-35_003.cr2
Camera Temperature : 9 C
======== /home/andrew/Pictures/indi/Light/m51_Light_120_secs_2017-04-23T00-06-04_001.cr2
Camera Temperature : 9 C
16 image files read

Read More...

Andrew created a new topic ' Parking scope without Park capability (LX200 & Skysensor)' in the forum. 10 months ago

For remote sessions it would be useful to be able to park a LX200 type mount like I've seen in Jasem's EKOS schedule demos, not at least this is useful for setting-up for making flats. However I believe my mount (SS2K) and most LX200 types don't have a "Park button" command built-in.

I've see there are a few tricks that involve passing dummy signals like ":Q#" (Quit) or switching to Land "#:AL#" that may work. Before digging deeper would a Python script be the best way to implement this i.e.running a script in EKOS in Sheduler or after imaging in File Settings?

Read More...

Jasem Mutlaq thanked Andrew in topic dslr - image info 10 months ago
Andrew replied to the topic 'dslr - image info' in the forum. 10 months ago

I tried another .fits only session last night it made 20+ images overnight Lights + Darks in .fits with 5184x3456, I didn't really touch anything - strange.
This morning I tried some bias frames and saw immediately EKOS fields change to 5202x3456, then no matter what I did in either INDI or EKOS it retained this, I tried setting each image size in INDI to the smaller frame, I tried setting offsets in both INDI and EKOS which didn't work as expected, each time the exposure would reset to the larger frame size.I even tried setting Native transport in INDI and left is FITs in EKOS.

In my workflow, and when I first noticed this issue, the Lights and Darks were OK just like this session (5184x3456) but bias and flats effected by larger frame size. so it seems it is capable of retaining the smaller frames! I start every session with INDI Capture Format to 'normal JPEG' since it speeds downloads for framing (set EKOS Format to Native. The result is a 5184x3456 image Preview, then by switching in INDI to RAW capture and in EKOS to FITS it retains a 5184x3456 FITs image.

It's an ugly workaround and when I tried to repeat it this morning it failed so I'll move back to Native CR2 since this is not a big issue really, but more importantly I think for DSLR workflow are the following issues which I notice every session:-
a. Bias setting min 0.001 : cannot set it lower i.e to 1/8000 (0.000125)
b. File name suffix for exposure is always '_0_' for sub-second frames (Flats and Bias) : is useful to see file list with exposures i.e. target_000125s_
c. Temperature in filename - from exif data, I mentioned this in wishlist for 2017 but thought it fits well here too but I recognise it is probably I much larger edit than the other 2 items.

thanks, Andrew.

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!