×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

DMK41 AU02.AS : How to configure it with INDI ?

I'm not sure I understand the problem, Ekos exposure can be set to any value, you can set it to 0.01 and it would send that over to the INDI driver. What do you mean by not accurate enough?

EDIT: Also Ekos does not record AVI.
Last edit: 10 years 3 months ago by Jasem Mutlaq.
10 years 3 months ago #472

Please Log in or Create an account to join the conversation.

  • Posts: 106
  • Thank you received: 12
I thought I would have the choice between 0.00, 0.50 and 1.00. I just saw that I can write 0.01, 0.02 ... But not below. Impossible to get 1/10000 (0.0001) for example
10 years 3 months ago #473

Please Log in or Create an account to join the conversation.

I changed the decimal precision to 4, so now you can write 0.0001
10 years 3 months ago #474

Please Log in or Create an account to join the conversation.

  • Posts: 106
  • Thank you received: 12
Thank you !

Do you plan to integrate video recording via INDI? Launching V4L2, when I open the window streaming, there is already a "pause" button and a button "capture an image" (with a list of possible formats). It "would suffice" to add a "capture video" button, perhaps with a timer. But I always ask too much! :oops:
10 years 3 months ago #475

Please Log in or Create an account to join the conversation.

There are no plans now to add AVI recording into KStars as it requires a few extra dependencies that I want to avoid for the time being. Maybe in future versions :-)
10 years 3 months ago #476

Please Log in or Create an account to join the conversation.

  • Posts: 106
  • Thank you received: 12
I tried to enter 0.0001 in Ekos (ccd v4l2), it still refuses to go beyond the second decimal
10 years 3 months ago #488

Please Log in or Create an account to join the conversation.

  • Posts: 5
  • Thank you received: 0
Hi,
I am right where you were here. I have a DMK 21AUO4.AS and have never been able to get to work under linux. I clicked on your link, but cannot find a procedure there. I also have a Celestron NI5 which is a rebranded IS camera that I would like to get running under linux. Could you cut and paste the procedure so I can try it?
Thanks,
John
10 years 2 months ago #558

Please Log in or Create an account to join the conversation.

What INDI & Ekos versions are you using?
10 years 2 months ago #559

Please Log in or Create an account to join the conversation.

  • Posts: 5
  • Thank you received: 0
I don't have linux (Fedora 20) recognizing the camera(s) yet. I have installed libindi but barely have a clue as to how to interface anything yet. I know first I need to get the cameras recognized. (on bootup dmesg shows the cameras as correctly identified, but v4l says there is no video device) That is where I am stuck, so I have a way to go. The installed libindi is 0.0.6-6.fc20 for a 64 bit linux machine.
10 years 2 months ago #561

Please Log in or Create an account to join the conversation.

  • Posts: 5
  • Thank you received: 0
I am sorry that was version 0.9.6.6
10 years 2 months ago #562

Please Log in or Create an account to join the conversation.

  • Posts: 106
  • Thank you received: 12
I have a DMK 41AU02.as and I also had never managed to make it work under linux, until I tried the solution described here
posts #12 and #13:
It worked for me. Do not forget to make these files executable!
The following user(s) said Thank You: David
10 years 2 months ago #563

Please Log in or Create an account to join the conversation.

  • Posts: 226
  • Thank you received: 88
Hi,
There may be a small error in the uvc driver as the Imaging Source camera (199e:8101 DFx 21BU04) is listed as being recognized on the uvcvideo site but the idProduct in the linuxtv.org source tree seems to be different (0x8102):
/* The Imaging Source USB CCD cameras */
2433 { .match_flags = USB_DEVICE_ID_MATCH_DEVICE
2434 | USB_DEVICE_ID_MATCH_INT_INFO,
2435 .idVendor = 0x199e,
2436 .idProduct = 0x8102,
2437 .bInterfaceClass = USB_CLASS_VENDOR_SPEC,
2438 .bInterfaceSubClass = 1,
2439 .bInterfaceProtocol = 0 },

You could send a request on the uvcvideo development list for this to be corrected or simply ask them to add
your camera idProduct (0x8101).
Maybe someone from Imaging Source can confirm the idProducts they are using for their uvc capable cameras.
10 years 2 months ago #564

Please Log in or Create an account to join the conversation.

Time to create page: 0.806 seconds