Andrew replied to the topic 'E: Unable to locate package kstars-bleeding' in the forum. 4 days 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. 4 days 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. 4 days 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. 6 days 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. 1 month 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. 1 month 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. 1 month 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 1 month ago
Andrew replied to the topic 'dslr - image info' in the forum. 1 month 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...

Andrew replied to the topic 'dslr - image info' in the forum. 1 month ago

hi jasem, did you ever have luck checking this?

I had similar experience with 60Da. I use SIRIL to process images, it accepts .fits directly but I've always converted from .cr2.
A couple of weeks ago, in an effort to streamline workflow I tried to save some lights and darks directly as .fits which worked fine. However when I came to processing, I found my SIRIL library bias and flats (taken another day as cr2 converted in SIRIL to fits) had different sizes as reported by lhoujin.

I assumed I'd made an error when setting the image frame or it had changed between sessions, normally I just load a saved profile and it works fine for .cr2. since I don't use any EKOS functions to focus or guide with the 60Da .

I tried cropping the files using PyFits to same size but in the end had to scrap this session and decided to return to saving as .cr2 but I'd like to try .fits only workflow again!

Read More...

Andrew replied to the topic 'some thoughts that came up doing native captures...' in the forum. 1 month ago

I agree some form of reduced window size that could be fixed between sessions would be great for native raw dslr.
I think another topic discussed fixing window sizes between sessions so maybe this could be combined?

Read More...

Andrew replied to the topic 'Partial SOLUTION skysensor2000PC -Error reading RA/DEC' in the forum. 2 months ago

it is specific to Skysensor and Lodestar x2 but it is a hardware 'patch' so not sure how you want to handle that, I suppose a note with the skysensor driver and Lodestar x2 page refrerring to this particular pair need a hardware patch on Lodestar x2 outputs and refer to Starlight Xpress?

but I can confirm that guiding does work - I got my first ever 100% Linux image (Ubuntu,INDI/Ekos/Kstars, RaspberryPi and Siril).:)
I'll feedback some minor adjustments for DSLR workflow in seperate subject.

Thanks again
Andrew

Read More...

Andrew replied to the topic 'Ten Steps to Getting Off ASCOM' in the forum. 2 months ago

Thanks Rockstarbill, this is nice summary and pretty much the route I took except I use DSLR as CCD, it will save newcomers hours of fiddling and will make nice posting-.

I wanted to check point eight, para 3, since it relevant to my ongoing struggle to autoguide. I've failed to get RS232 working and finally found a solution this week via ST4. You seem adamant about only ST4 working with LX200 type driver, which is what I've found, did you try it at all?

Read More...

Andrew replied to the topic 'Partial SOLUTION skysensor2000PC -Error reading RA/DEC' in the forum. 2 months ago

UPDATE - with partial solution.:)
with help from Terry at Starlight Xpress we found that the Skysensor2000pc needed a signal input adjustment to work with Lodestar x2.
I can now confirm it works fully enabling me to autoguide via the ST4 port using Lin Guider, openPHD2 and indi (first night RMS 1" in dec and ra over several hours).

I'd still prefer to use the RS232 option but this still fails with the indi lx200ss2000 driver and as far as I can tell this is a bug and not hardware. I'm happy to try to help resolve this if there is a demand.
Andrew.

Read More...

Andrew replied to the topic 'skysensor2000PC -driver query (Error reading RA/DEC not in .log' in the forum. 2 months ago

thanks jasem, I'll test on tuesday night and report back, forecast clear all week here :-)
a couple of users on the ss2k group confirmed they guided with lx200 settings (ascom) so hopefully by reactivating it we should have some success - lets see...

Read More...

Andrew replied to the topic 'skysensor2000PC -driver query (Error reading RA/DEC not in .log' in the forum. 2 months ago

Update - my SS2K autoguider function is broken.

So I'd like to contribute to editing SS2K driver to make it work with pulsedrive commands as it does in ASCOM. I only have limited programming skills (fortran, Basic, Python and script) but I see the ASCOM script is in VB and updated fairly recenty 2013 (LaurieY 6.1.7b github), so if somebody could hint were I could start, with a little help and if there is wider demand we might finish it! what do you think?.

Surely if one of the LX200 drivers is using pulseguide is it not just a case of editing that for differences? I notice I can select either Indi_lx200generic, basic or classic and I think even 16 worked, anyhow all partially worked at least enabling calibration and short guide until mount runs away,

Actually a SS2K pulseguide is might last hope to use INDI since below is my last failed test on the SS2K and ST4 autoguiding:-

Andrew.

ST4 failure confirmed


I opened the SS2K to check the continuity into the back of the RJ12 socket and it seemed to be OK, I mean no pins were electrically disconnected from the solder board.

There it seems the problem is within the SS2K circuit but I don't have the skills to debug that far. Although I assume the circuit is a fairly simple switch type mimicing the N.S.E.W buttons anyhow for now it's broken.

I tested the whole system again - 1st RS232 with Windows/PHD and Astroart using ASCOM drivers works 100% as per last 10 years. Switching to linux on Raspberry Pi or a PC fails on all SW, OpenPHD/Indi drivers and Sx drivers wil only guide in 2 directions. ST4 fails on Windows and Linux it will only guide in 2 directions.

Read More...

Andrew replied to the topic 'skysensor2000PC -driver query (Error reading RA/DEC not in .log' in the forum. 3 months ago

Thanks Camiel,
For the moment, with clear sky, I'm back to Windows/ASCOM system (BYEOS and PHD) which is OK, guides very well but lacks the complete suite that INDI offers. BTW - In this setup SS2K supports pulse-guide via the RS232 using ASCOM driver with PHD.

I tried Lin-Guider and it shows I probably do have an issue with my ST4/Rj12 autoguide cable, I tested with multmeter but cannot find fault. I'll probably invest €20 in professional cable and report back since this combination seems perfect with INDI.

Andrew.

Read More...

Andrew replied to the topic 'skysensor2000PC -driver query (Error reading RA/DEC not in .log' in the forum. 3 months ago

Sorry Jasem I don't have any guiding extras for ss2k, I suppose they could be extracted from ASCOM driver?
Looks clear for tonight so I'll try autoguide ST4 again with a tighened backlash on Dec motor.

Read More...

Andrew replied to the topic 'skysensor2000PC -driver query (Error reading RA/DEC not in .log' in the forum. 3 months ago

thanks everyone,

So if I understand the various inputs here :with my setup using the ss2kpc driver will not work since the controller doesn't accept the commands.The only option for guiding is to use the autoguide ST4 port. I'll try this again next clear night.

But why was a ssk2pc driver created if it cannot guide, what advantage does have over say a LX200 driver?

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!