Niko Kivel replied to the topic 'SVD_MathPlugin error' in the forum. 4 weeks ago

Thanks for fixing this in record time.
I wish I could be more of help and fix stuff myself rather than just reporting errors.
best
Niko

Read More...

Niko Kivel thanked Jasem Mutlaq in topic SVD_MathPlugin error 4 weeks ago
Niko Kivel thanked Thomas Stibor in topic SVD_MathPlugin error 4 weeks ago
Niko Kivel created a new topic ' SVD_MathPlugin error' in the forum. 4 weeks ago

Hi all

I just compiled indilib and the eqmod driver on a RPi 3B+.
When starting ` indiserver indi_eqmod_telescope`, I get this error.

Driver indi_eqmod_telescope: EnumeratePlugins - cannot load plugin /libindi_SVD_MathPlugin.so error /libindi_SVD_MathPlugin.so: cannot open shared object file: No such file or directory
I'm sure it's looking in the wrong place, because the fs-root is an unlikely place to find it :)
By linking the actual file to the fs-root it works fine.

best
Niko

Read More...

Niko Kivel replied to the topic 'INDI GPhoto Driver v2.0' in the forum. 4 weeks ago

Hi Jasem

I'm afraid there is still some issue here.
My 7D Mk II is taking couple 100 ms exposures only.

[2018-04-21T21:56:18.106 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] Starting exposure (exptime: 5 secs, mirror lock: 0) "
[2018-04-21T21:56:18.106 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG]   Mutex locked "
[2018-04-21T21:56:18.106 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] Setting radio/menu widget iso: 1 (100) "
[2018-04-21T21:56:18.154 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] Setting new configuration OK. "
[2018-04-21T21:56:18.154 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] Using internal bulb widget:eosremoterelease "
[2018-04-21T21:56:18.154 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] Setting radio/menu widget eosremoterelease: 2 (Press Full) "
[2018-04-21T21:56:18.305 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] Setting new configuration OK. "
[2018-04-21T21:56:18.305 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] Exposure started "
[2018-04-21T21:56:18.305 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] Time left: -5000 ms "
[2018-04-21T21:56:18.305 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] Closing shutter "
[2018-04-21T21:56:18.305 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] Using widget:eosremoterelease "
[2018-04-21T21:56:18.305 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] Setting radio/menu widget eosremoterelease: 4 (Release Full) "
[2018-04-21T21:56:18.334 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] Setting new configuration OK. "
[2018-04-21T21:56:21.963 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] Reading exposure... "
[2018-04-21T21:56:21.964 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] Exposure complete "
[2018-04-21T21:56:29.178 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] File added event completed. "
[2018-04-21T21:56:29.178 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] Downloading image... Name: (capt0000.cr2) Folder: (/) Delete from SD card? (false) "
[2018-04-21T21:56:29.238 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] Could not determine image size (Unspecified error) "
[2018-04-21T21:56:29.238 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] Capture target is INTERNAL RAM. "
[2018-04-21T21:56:29.241 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] Setting radio/menu widget iso: 13 (1600) "
[2018-04-21T21:56:29.293 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] Setting new configuration OK. "
[2018-04-21T21:56:29.293 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] Setting radio/menu widget shutterspeed: 0 (bulb) "
[2018-04-21T21:56:29.319 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] Setting new configuration OK. "
[2018-04-21T21:56:33.090 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] read_libraw: raw_width: 5568 top_margin 38 left_margin 72 first_visible_pixel 211656 "
[2018-04-21T21:56:33.090 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] read_libraw: rawdata.sizes.width: 5496 rawdata.sizes.height 3670 memsize 40340640 bayer_pattern RGGB "
[2018-04-21T21:56:33.152 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] read_libraw: memsize (40340640) naxis (2) w (5496) h (3670) bpp (16) pattern (RGGB) "
[2018-04-21T21:56:33.326 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] Uploading file. Ext: fits, Size: 40345920, sendImage? Yes, saveImage? No "
[2018-04-21T21:56:34.980 CEST DEBG ][           org.kde.kstars.indi] - GPhoto CCD : "[DEBUG] Upload complete "

I did go back to commit #32eed05d833694a56973280a67fbf1bee5967136 to make the cam work again.

best
Niko

Read More...

Niko Kivel thanked Jan in topic QHY183M not detected 2 months ago
Niko Kivel replied to the topic 'QHY183M not detected' in the forum. 2 months ago

Oops, didn't know that, thanks for adding it! :woohoo:
Jan promised me to keep me posted on the development.
anyway, I can't make it run :(
dmesg:

[ 2107.126221] usb 1-1.2: new high-speed USB device number 5 using ehci-pci
[ 2107.235675] usb 1-1.2: New USB device found, idVendor=1618, idProduct=c183
[ 2107.235680] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2107.235684] usb 1-1.2: Product: WestBridge 
[ 2107.235687] usb 1-1.2: Manufacturer: Cypress
[ 2107.235689] usb 1-1.2: SerialNumber: 0000000004BE
[ 2107.458147] usb 1-1.2: USB disconnect, device number 5
[ 2107.682218] usb 1-1.2: new high-speed USB device number 6 using ehci-pci
[ 2107.792222] usb 1-1.2: New USB device found, idVendor=1618, idProduct=c184
[ 2107.792227] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2107.792230] usb 1-1.2: Product: Q183-Cool
[ 2107.792233] usb 1-1.2: Manufacturer: QHYCCD
so, there is a camera detected by the OS ...

indiserver startup:
bigblue@odroid:~$ indiserver -vvv indi_qhy_ccd 
2018-04-01T18:01:54: startup: indiserver -vvv indi_qhy_ccd 
2018-04-01T18:01:54: Driver indi_qhy_ccd: pid=805 rfd=3 wfd=6 efd=7
2018-04-01T18:01:54: listening to port 7624 on fd 4
2018-04-01T18:01:54: Driver indi_qhy_ccd: sending msg copy 1 nq 1:
<getProperties version='1.7'/>

2018-04-01T18:01:54: Driver indi_qhy_ccd: stderr EOF
Child process 805 died
Well, that repeats itself for another 9 times, but fails

and finally qhy_ccd_test:
bigblue@odroid:~$ qhy_ccd_test 
-----------------------------------
2018-04-01 18:03:00:480: qhyccd: cons() start...
-----------------------------------
2018-04-01 18:03:00:493: qhyccd: pthread_mutexattr_init success.
2018-04-01 18:03:00:493: qhyccd: pthread_mutexattr_settype success.
2018-04-01 18:03:00:493: qhyccd: pthread_mutex_init success.
-----------------------------------
2018-04-01 18:03:00:493: qhyccd: cons end...
-----------------------------------
QHY Test CCD using SingleFrameMode, Version: 1.00
SDK resources initialized.
2018-04-01 18:03:00:494: qhyccd: ScanQHYCCD start...
2018-04-01 18:03:00:494: qhyccd: ScanQHYCCD - Total number of USB devices : 10
2018-04-01 18:03:00:494: qhyccd: ScanQHYCCD - New number of QHYCCD devices: 1
2018-04-01 18:03:00:494: qhyccd: ScanQHYCCD - Old number of QHYCCD devices: -1
2018-04-01 18:03:00:494: qhyccd: QHYCCDSeriesMatch: idx 0, pHandle 0x4da768, cydev[0].pid = c184
2018-04-01 18:03:00:494: qhyccd: QHY5IIISeriesMatch(handle: 0x4da768, mainseries: 4044) start...
2018-04-01 18:03:00:496: qhyccd: QHY5IIISeriesMatch retVal: 0, end...
2018-04-01 18:03:00:496: qhyccd: InitQHYCCDClass camtype = 0 idx = 0
2018-04-01 18:03:00:496: Unknown camera type: 0

indilib, git:
bigblue@odroid:~/indi$ git log --pretty=format:"%h - %an, %ar : %s"
1b9b311 - Jasem Mutlaq, 11 hours ago : Do not open shutter in bias frames

hardware, Odroid XU4 with Ubuntu 16.04.4 LTS,
compiled with: gcc version 7.2.0 (Ubuntu/Linaro 7.2.0-1ubuntu1~16.04)

If you guys need any more info, let me know.
Thanks again for the effort
Niko

Read More...

Niko Kivel replied to the topic 'Re:QHY183M not detected' in the forum. 2 months ago

It seems as if they are working on the driver. Last news are now 2 weeks old and the report was something like "I try to do it asap", which is pretty much worthless in terms of a timeline. But, I'm not complaining, I haven't seen the sky in the last 5 month for more than 3 consecutive hours :(

Read More...

Niko Kivel replied to the topic 'Re:V4L2 subframe error with PHD2' in the forum. 2 months ago

I'm looking into it. But it's rather hard for me to get into the code and understand what is done were.
My solution was to comment out the 'return -1;' :), which is fine for me, but defies the point of the entire exercise :)
best
Niko

Read More...

Niko Kivel replied to the topic 'persistent configuration' in the forum. 2 months ago

Thanks Jasem,

I don't know what went wrong with the EQMod save. It now works for the basic/hardware parameters.

What I'm more interested is set-up specific configurations. Such as Aperture for the Canon or 16-bit mode for a v4l2-cam.
To provide an example: I constantly forget to click the 'view finder --> ON' for the canon. Hence, the first auto-focus run fails because the lens wasn't moving.

I guess I look into the 'scripting' and plug something together that sets all the hardware up, or is there a better way?

best Niko

Read More...

Niko Kivel replied to the topic 'V4L2 subframe error with PHD2' in the forum. 2 months ago

So it seems as if PHD2 is always requesting an odd crop window.
One can set a 'search region' in pixel which is uses for the crop window, as 2*search_region+1.

When removing 'return -1;' from v4l2_base.cpp:1706 to allow odd crop windows, PHD is working fine.

I guess this feature is important for something, may I ask was the reason not to allow this in the first place?

I'm not familiar with the code, so it's a bit hard to figure out how this soft-croping works. But I presume a valid approach would be to grab one additional pixel in case of odd pixel count and and crop it in software before shipping?

best
Niko

Read More...

Niko Kivel thanked Eric in topic Re:V4L2 subframe error with PHD2 2 months ago
Niko Kivel replied to the topic 'Re:V4L2 subframe error with PHD2' in the forum. 2 months ago

I'll try with an even crop window, and report back.

Niko

Read More...

Niko Kivel replied to the topic 'persistent configuration' in the forum. 2 months ago

Yup, did that.
Some of the parameters - such as chip size and pixel pitch for the Canon - are saved, but not all. mostly operational parameters are disregarded.
I can understand the philosophy of that, because of the variable nature of such parameters. So a feature request might be to have a separate parameter sets which can be loaded for the entire observatory at start time. E.g. Canon set to F/5.6, guide-cam select 16 bit, full resolution, EQmod guide velocity 0.3, ...

best
Niko

Read More...

Niko Kivel created a new topic ' persistent configuration' in the forum. 2 months ago

Hi, either it's too late or I had to little coffee today, but how can I make settings persistent.

i.e. I want to set the guiding rate to 0.3 for the EQMOD driver. But every time I re-boot it comes up at 0.5

similar with the gphoto2 / Canon driver. Is there a way to toggle 'actions/viewfinder/ON' at connect?

I already logged the XML comms and copy pasted snippets into the configuration file, but it seems that 'load' is followed by a 'save' and all changes vanish. If I put the same snippets in the default config, no changes to the addressed fields can be noticed.

I'm sure there is a way of doing this, but I'm to blunt to figure it :(

best
Niko

Read More...

Niko Kivel created a new topic ' V4L2 subframe error with PHD2' in the forum. 2 months ago

Hey guys

I'm tackling a few long lasting issue which started bothering again. One of those is the inability to use subframes with my set-up.
I have a DMK guiding cam that work perfectly fine, except for the fact that I get an error and garbage data when selecting the subframe option in PHD2.

That's what I get, any ideas what's wrong or what I can do?

DEBUG	1956.299460 sec	: Requested CCD Frame is (1222,830) ( 51 x  51)
INFO	1956.299533 sec	: ERROR (setcroprect): crop width/height must be pair

I presume PHD2 figuers that something went wrong and requests a full frame again. At least some times :)
DEBUG	1952.455501 sec	: Requested CCD Frame is (  0,  0) (2592 x 1944)
DEBUG	1952.457582 sec	: V4L2 base setcroprect 2592x1944 at (0, 0)

Thanks in advance
Niko

Read More...

Niko Kivel replied to the topic 'QHY183M not detected' in the forum. 4 months ago

Thanks for letting me know

Read More...

Niko Kivel replied to the topic 'QHY183M not detected' in the forum. 4 months ago

Hi Jasem

I also bypassed the "85-qhy.rules" to prevent the firmware from been automatically uploaded by udev. I then manually loaded the firmware with `fxload` ... which seems fine to me.

$> fxload -v -t fx3 -I /lib/firmware/qhy/QHY183.img -D /dev/bus/usb/005/003
microcontroller type: fx3
single stage:  load on-chip memory
open RAM image /lib/firmware/qhy/QHY183.img
write on-chip, addr 0x00100 len 4096 (0x1000)
write on-chip, addr 0x01100 len 4096 (0x1000)
write on-chip, addr 0x02100 len  800 (0x0320)
write on-chip, addr 0x40003000 len 4096 (0x1000)
write on-chip, addr 0x40004000 len 4096 (0x1000)
write on-chip, addr 0x40005000 len 4096 (0x1000)
write on-chip, addr 0x40006000 len 4096 (0x1000)
write on-chip, addr 0x40007000 len 4096 (0x1000)
write on-chip, addr 0x40008000 len 4096 (0x1000)
write on-chip, addr 0x40009000 len 4096 (0x1000)
write on-chip, addr 0x4000a000 len 4096 (0x1000)
write on-chip, addr 0x4000b000 len 4096 (0x1000)
write on-chip, addr 0x4000c000 len 4096 (0x1000)
write on-chip, addr 0x4000d000 len 4096 (0x1000)
write on-chip, addr 0x4000e000 len 4096 (0x1000)
write on-chip, addr 0x4000f000 len 4096 (0x1000)
write on-chip, addr 0x40010000 len 4096 (0x1000)
write on-chip, addr 0x40011000 len 4096 (0x1000)
write on-chip, addr 0x40012000 len 4096 (0x1000)
write on-chip, addr 0x40013000 len 4096 (0x1000)
write on-chip, addr 0x40014000 len 4096 (0x1000)
write on-chip, addr 0x40015000 len 4096 (0x1000)
write on-chip, addr 0x40016000 len 4096 (0x1000)
write on-chip, addr 0x40017000 len 4096 (0x1000)
write on-chip, addr 0x40018000 len 4096 (0x1000)
write on-chip, addr 0x40019000 len 4096 (0x1000)
write on-chip, addr 0x4001a000 len 4096 (0x1000)
write on-chip, addr 0x4001b000 len 4096 (0x1000)
write on-chip, addr 0x4001c000 len 4096 (0x1000)
write on-chip, addr 0x4001d000 len 4096 (0x1000)
write on-chip, addr 0x4001e000 len 4096 (0x1000)
write on-chip, addr 0x4001f000 len 4096 (0x1000)
write on-chip, addr 0x40020000 len 4096 (0x1000)
write on-chip, addr 0x40021000 len 4096 (0x1000)
write on-chip, addr 0x40022000 len 4096 (0x1000)
write on-chip, addr 0x40023000 len 2028 (0x07ec)
write on-chip, addr 0x40030000 len 4096 (0x1000)
write on-chip, addr 0x40031000 len 4096 (0x1000)
write on-chip, addr 0x40032000 len   72 (0x0048)
write on-chip, addr 0x40010460 len    0 (0x0000)
... WROTE: 150356 bytes, 40 segments, avg 3758


Read More...

Niko Kivel replied to the topic 'QHY183M not detected' in the forum. 4 months ago

Hi

$> dpkg-query -W fxload
fxload	1.0~201712271246~ubuntu16.04.1


Read More...

Niko Kivel created a new topic ' QHY183M not detected' in the forum. 4 months ago

Hi

I've got a problem with my brand new QHY183M. It recognized by OS (Linux Mint) , but the indiserver (v1.6.3) complains that it can't find a device.

2018-02-03T17:27:02: Driver indi_qhy_ccd: read message    'No QHY cameras detected. Power on?'
[  341.097770] usb 5-1: new high-speed USB device number 3 using xhci_hcd
[  341.298318] usb 5-1: New USB device found, idVendor=1618, idProduct=c183
[  341.298323] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  341.298326] usb 5-1: Product: WestBridge 
[  341.298329] usb 5-1: Manufacturer: Cypress
[  341.298331] usb 5-1: SerialNumber: 0000000004BE
[  341.358081] usb 5-1: USB disconnect, device number 3
[  341.621277] usb 6-1: new SuperSpeed USB device number 2 using xhci_hcd
[  341.638773] usb 6-1: LPM exit latency is zeroed, disabling LPM.
[  341.639635] usb 6-1: New USB device found, idVendor=1618, idProduct=c184
[  341.639639] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  341.639642] usb 6-1: Product: Q183-Cool
[  341.639644] usb 6-1: Manufacturer: QHYCCD

any help very much appreciated

cheers
Niko

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!