×

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 ?

  • 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 3 months ago #558

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

What INDI & Ekos versions are you using?
10 years 3 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 3 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 3 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 3 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 3 months ago #564

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

  • Posts: 5
  • Thank you received: 0
I had an interesting time with this and Fedora20 last night. This command
echo "199e 8101" | sudo tee /sys/bus/usb/drivers/uvcvideo/new_id did not work on my system. Not only is there no uvcvideo subdirectory, the system would not let root make one (no idea why). I wound up putting new_id in my home directory for the moment. The rest of the commands did work and my DMK21A04.as is up and running under linux. This does need to be posted prominently somewhere. This camera was an 8101 id. Thank you. This is the first success I have had in this long running quest.
I then went after the relabeled Celestron Neximage 5. This is made by IS, and is really a versatile camera. It has 2.2micron pixels and can go from 640x480 up to 2500x1600 or thereabouts. It does 60fps at the lower resolution, and has good quality color. Its product ID is 8207. When I put that number in through the above process I got confusing results but the camera did not work (It was more known to the system though, in that the error messaged no longer said "no /dev/video0".)
I think I found out that there is already a file on my computer that uses that number and am working on the resulting confusion. If I get this one working it would be great, and it needs to be posted somewhere as it is a reasonably priced high quality color camera.
10 years 3 months ago #565

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

  • Posts: 5
  • Thank you received: 0
The Celestron NI5 is the same as the IS DFK72AUCO2. I found directions for making it work under linux at
code.google.com/p/tiscamera/wiki/GettingStartedCMOSUVC

On has to redo the camera's firmware to get it to work, though it is a pretty foolproof method. It save your old firmware as a file, and gives you directions on how to go back. So far the camera works, but does not have all of its resolutions available, and seems to be a bit slower than under its normal operation. A good day's work, but that is pretty much all I know for now. Both cameras are alive under uvc in linux.
10 years 3 months ago #567

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

  • Posts: 20
  • Thank you received: 1
Just a little message to thank you : the udev rules works fine for my DFK23U445 !!
4 years 9 months ago #41278

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

What udev file? If something can be added to INDI to help with this we will add. And are you sure the Celestron NexImager 5 is the same camera? can we then just add an alias for that?
4 years 9 months ago #41292

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

  • Posts: 20
  • Thank you received: 1
Sorry I'm on my smartphone. I don't find the exact reference but...

It is the script that Bilbo was talking about on page 4.
4 years 9 months ago #41293

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

  • Posts: 161
  • Thank you received: 39
Yes. Differently packaged, but the same. For the NI5, it's the dfk72uc02. Here's my NI5 specific stuff, with links (to github instead of google code) that work.

www.indilib.org/forum/ccds-dslrs/3320-ex...eximage-cameras.html

It works pretty well.

Though since I'm thinking about it: Sometimes it shifts for a frame or two from where it should be, which I'm not sure if it's a v4l2 (I haven't observed it do it wit guvcview), long exposures, an INDI problem, a PHD2 problem (I don't think I've seen it using Kstars/Ekos), or a Mini-PC problem (I don't think I've seen it on my laptop, but I'm not certain of that). Like somewhere between 1/4 and 3/4 of the frame is off/wrapped around (and mostly out of guide star detection range, so the next frame or two it picks it up). Has anyone else seen that sort of issue with other tis cameras, or neximage cameras?
4 years 9 months ago #41294

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

Time to create page: 1.244 seconds