Niko Kivel replied to the topic 'QHY183M not detected' in the forum. 2 weeks ago

Thanks for letting me know

Read More...

Niko Kivel replied to the topic 'QHY183M not detected' in the forum. 3 weeks 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. 3 weeks 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. 3 weeks 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...

Niko Kivel replied to the topic 'Cannot change Capture Setting' in the forum. 1 month ago

Hi

@OS: KStars/Ekos runs on a Mint Linux and the INDI-server on a debian jessie, hosted on an odroid, compiled form the git repo.

I deleted the gphoto xml in the .indi directory on the INDI-server. That triggered the dialog to come up again and I entered the proper values for the DSLR again. That seemed to solve the problem, but I keep investigating.

cheers
Niko

Read More...

Niko Kivel created a new topic ' Cannot change Capture Setting' in the forum. 1 month ago

Hi

I cannot change my exposure settings in Ekos. Typically I was getting a question every time I opened Ekos about the resolution and pixel size of my EOS 7D Mk II.
Yesterday I made a typo and entered a too small number for W:
Regardless of what I try, I can't enter a number larger than 5000 for the width, which is really annoying since the DSLR has a width of 5496. Any idea where to change this to the real resolution and make it persisted?

cheers
Niko

Read More...

Niko Kivel thanked Csaba Kertesz in topic Problem with EQMod 7 months ago
Niko Kivel replied to the topic 'Problem with EQMod' in the forum. 7 months ago

arghh, that's probably the dumbest rookie mistake one can make.

Now I at least have a proper incentive to build a 1.8 to 3.3 V level shifter to use the GPIO UART :)

Thanks
Niko

Read More...

Niko Kivel replied to the topic 'Problem with EQMod' in the forum. 7 months ago

Hi guys

I'm trying to connect to my EQ6-R whith the EQMod driver via the hand controller.
I run the latest git 7d5271f on an odroid XU4 and use an "pl2303" usb-RS232 converter.
When using

screen /dev/ttyUSB0 9600
I can talk to the mount and issue command and slew it.
However when trying to connect indi I get the following response
2017-08-09T20:00:22: dispatch_command: ":e1", 4 bytes written 
2017-08-09T20:00:22: Connection successful, attempting handshake... 
2017-08-09T20:00:22: Port FD 13 
2017-08-09T20:00:22: Connecting to /dev/ttyUSB0 
2017-08-09T20:00:22: Trying connection to /dev/ttyUSB0 @ 9600 ... 
2017-08-09T20:00:22: Communication with /dev/ttyUSB0 @ 9600 failed. Starting Auto Search... 
2017-08-09T20:00:22: Handshake failed. 
2017-08-09T20:00:22: Error:  -> tty read failed, check connection: Timeout error 
2017-08-09T20:00:07: dispatch_command: ":e1", 4 bytes written 
2017-08-09T20:00:07: Connection successful, attempting handshake... 
2017-08-09T20:00:07: Port FD 12 
2017-08-09T20:00:07: Connecting to /dev/ttyUSB0 

any ideas?

cheers
Niko

Read More...

Niko Kivel replied to the topic 'TIS DMK 23UP031 exposure settings and general config' in the forum. 7 months ago

TallFurryMan wrote: On my DMK changing the gain has a dramatic effect on the dynamic, but it is only 8-bit.

same here, it's just not "gain" but "Gain (dB/1000)". The "Gain" in ekos CDD capture settings has no effect on the image taken.

cheers
Niko

Read More...

Niko Kivel replied to the topic 'TIS DMK 23UP031 exposure settings and general config' in the forum. 7 months ago

Hi Eric

I've found some time for testing this evening.
The camera does recognize the exposure settings send via ekos. I prepared a short sequence with exposures from 0.001 -- 0.060 s and plotted the mean pixel values over the exposure time. To me, it looks reasonably linear which is what I'd expect.

The log file seems to be a little messed up. When triggering an exposure, the log receives data from the previous exposure.
In this case, I took a 1 s exposure before the sequence start. Resulting in:

...
DEBUG	2890.131759 sec	:   Setting Exposure (Absolute) (Exposure (Absolute)) to 10000.000000, ctrl_id = 0x9A0902
...
from the 1 s exposure, followed by
DEBUG	2890.140622 sec	: 0.001-second exposure translates to 10 1/10,000th-second device ticks.
...
DEBUG	2892.939829 sec	: Upload complete
which belongs to the actual exposure.

I noticed that the "Gain" in ekos has no effect on the images, but I have to check that in more details and get back to you.

cheers
Niko

Read More...

Niko Kivel replied to the topic 'TIS DMK 23UP031 exposure settings and general config' in the forum. 7 months ago

Hi Eirc

here the log to prove it really works.
Thanks again
Niko

Read More...

Niko Kivel replied to the topic 'TIS DMK 23UP031 exposure settings and general config' in the forum. 7 months ago

TallFurryMan wrote: EDIT: you may go ahead testing PR #299, I pushed the mentioned fix.


and ... it works !!!!!

Many thanks for this remarkable example of open source software advantages.

cheers
Niko

Read More...

Niko Kivel replied to the topic 'TIS DMK 23UP031 exposure settings and general config' in the forum. 7 months ago

TallFurryMan wrote: In the meantime, have you tried the IC Capture software with your camera? Are you able to change the exposure manually with that software?
-Eric


I did check general functionality with IC Capture last week. I didn't do any in deeps checks, I was happy to get a picture at all :)
I'm on vacation right now and don't a have Windows PC with me, so I can't do anything with IC Capture.

For good measure, I added the output of v4l2-compliance, if it's of no use please disregard.
Niko

Read More...

Niko Kivel replied to the topic 'TIS DMK 23UP031 exposure settings and general config' in the forum. 7 months ago

TallFurryMan wrote: I pushed PR #299, which is an attempt to bypass manual/auto control.


Hi Eric

I fetched PR/299 and made a quick test. The behavior is still the same :(, however, more information ends up in the log-file.
Please let me know if I should run further tests or provide you with more information that might help to solve the issue.
In any case, I'm very impressed to see how fast this is going and that the issue is taken seriously.
Niko

Read More...

Niko Kivel replied to the topic 'TIS DMK 23UP031 exposure settings and general config' in the forum. 7 months ago

Yes, preview makes three attempts to capture a picture.

I was in contact with TIS. They said the camera can only stream, no single frame capability.
Is there a way to still use the cam for guiding? That's what I intended to use it for in the first place.

Niko

Read More...

Niko Kivel replied to the topic 'TIS DMK 23UP031 exposure settings and general config' in the forum. 7 months ago

Hmm, that only happened once. I never saw this behavior later on.

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!