×

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

Bi-monthly release with minor bug fixes and improvements

Nikon DSLR conflict

  • Posts: 139
  • Thank you received: 31

Replied by Marc on topic Nikon DSLR conflict

Jasem and Jantje:

I have a Nikon D750 and I can assure you absolutely everything works fine. I've put in attachment some screen copies with my settings, if this helps.

On one screen, you can see a red dot facing the definition, this is normal. The screen copy was taken after I used the live stream, so the definition is that of the rear screen.
When you take still images, the definition returns to 6016x4016 and the red dot goes green again.

Jantje, for your third problem (the connection) look for a file /usr/lib/udev/rules.d/99-nikon.rules. it should contain ...

<
ACTION=="add", ATTR{idVendor}=="04b0", RUN+="/bin/sh -c '/bin/echo 256 >/sys/module/usbcore/parameters/usbfs_memory_mb'"
SUBSYSTEMS=="usb", ATTR{idVendor}=="04b0", MODE="0666"
>

... so every one can read and write the device.

The same directory should also contain a 85-disable-dslr-automount.rules with ...

<
# Disable automount by setting envrionment variable for UDISK2.

# Pentax
SUBSYSTEMS=="usb", ATTRS{idVendor}=="25fb", ENV{UDISKS_AUTO}="0"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0a17", ENV{UDISKS_AUTO}="0"

# Canon
SUBSYSTEMS=="usb", ATTRS{idVendor}=="04a9", ENV{UDISKS_AUTO}="0"

# Nikon
SUBSYSTEMS=="usb", ATTRS{idVendor}=="04b0", ENV{UDISKS_AUTO}="0"

# Sony
SUBSYSTEMS=="usb", ATTRS{idVendor}=="054c", ENV{UDISKS_AUTO}="0"
>

... so the device won't be set "busy" when the driver tries to access it.


Jasem, I also have a D3100; it works fine except for the live video, which is not supposed to. The D3100 in a low end Nikon, so it isn't as feature-rich as the high end cameras like the D500 or the D750. Being from the same bloodline, I wouldn't be surprised should your D3500 have the same problem. But I repeat, everything else works fine.

In the live video, it you click the debayer, everything goes boom.

Well, I hope all this helps :)


- Marc


The following user(s) said Thank You: Jan, Harkant singh
Last edit: 4 years 4 months ago by Marc.
4 years 4 months ago #46955

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

  • Posts: 983
  • Thank you received: 375

Replied by Radek Kaczorek on topic Nikon DSLR conflict

I do not use Nikon myself, but I got reports on Nikon D7500 - apparently file format selection is not working properly and whatever you do, you end up with jpeg-fine format. It looks like this behavior id model dependent and is related to libgphoto2 rather than indi driver
4 years 4 months ago #46958

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

  • Posts: 43
  • Thank you received: 4

Replied by Jan on topic Nikon DSLR conflict

@Marc2b - thank you for your support - I am currently shooting with the ZWO ASI294MC PRO and it works perfectly, but if I have more time I will try again with my Nikon D500. ;)
Skywatcher Apo 80/600 EvoStar ED - Skywatcher HEQ-5 Pro SynScan GoTo - ZWO ASI294MC Pro - ( Nikon D500)
4 years 4 months ago #46960

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

  • Posts: 5
  • Thank you received: 0

Replied by Omar on topic Nikon DSLR conflict

Hi Radek

Yes, I can verify that. I have the D7500 and also the D7000 and D750. The 7000 and 750 have no problems: FITS are NEF both save fine upon selection. The D7500 switches to jpeg when RAW is selected. But it actually save FITS just fine.

Omar

Exos2 PMC8, Nikon D7500/D7000, ZWO mini guide camera, StellarMate
4 years 4 months ago #46961

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

  • Posts: 2
  • Thank you received: 0
Hi,
I can confirm the same behavior with the latest Stellarmate (1.4.6) and also with my own MATE based stack which I compiled about a month and a half ago using github versions of INDI but mostly bionic sources for other libraries. It ignores the capture format setting and leaves the camera to FINE after you have unplugged it. Preview and saved image comes as JPEG unless you chose FITS.

In fact FITS doesn't exactly work fine either. It has 8 bits per channel.

Clearly something with that model.

ASIAIR works correctly though and I believe it too has INDI under the hood. However, ASIAIR does not touch the format at all. I know this because it will stick with whatever I have chosen on the camera. So perhaps it is just the "set format" operation that is flawed and a possible workaround would be to disable it completely and just use what the camera has? I will try to see if that is feasible.
4 years 3 months ago #48200

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

Replied by Jasem Mutlaq on topic Nikon DSLR conflict

Hello Dimitris & welcome to INDI forum.

So I took a look again at the driver code and found this tidbit in gphoto_driver.cpp:1058
// Set Format Settings
    if (gphoto->format >= 0)
        gphoto_set_widget_num(gphoto, gphoto->format_widget, gphoto->format);

So it could be here that this is failing for some Nikon models? Can some comment out this code block and compile again? If it was indeed proven to be the culprit, we can figure out a way to add an exception for the affected Nikon models.
4 years 3 months ago #48289

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

  • Posts: 85
  • Thank you received: 9

Replied by Steve Crossman on topic Nikon DSLR conflict

Jasem, this is the same issue I reported to you about 2 months ago with the D7500 where it would switch to JPG fine, which prompted you to get the D3400 for testing.

I found that using NEF + JPEG normal in the camera would enable it to save as NEF. Selecting just NEF would result in it switching back to just JPG fine being saved to the SD card in the camera.

The setting in the INDI control panel would reflect very odd characters.


4 years 3 months ago #48309
Attachments:

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

Replied by Jasem Mutlaq on topic Nikon DSLR conflict

What's the VID:PID of D7500? I think I found the issue in libgphoto2 and working on a fix.
4 years 3 months ago #48381

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

  • Posts: 85
  • Thank you received: 9

Replied by Steve Crossman on topic Nikon DSLR conflict

Where do I find this information?
4 years 3 months ago #48385

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

  • Posts: 1957
  • Thank you received: 420
On Linux: plug it in, open a terminal and type lsusb
On Mac: click the Apple to the top left -> About This Mac -> System Report -> USB
4 years 3 months ago #48389

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

  • Posts: 85
  • Thank you received: 9
4 years 3 months ago #48391
Attachments:

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

Replied by Jasem Mutlaq on topic Nikon DSLR conflict

Thanks, I've pushed a possible fix for this to my own libghoto2 fork here: github.com/knro/libgphoto2

So this requires some knowledge in compiling as this must be compiled and installed first, then indi-gphoto is compiled afterwards and tested. If there is Teamviewer, I can do this remotely.
4 years 3 months ago #48394

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

Time to create page: 4.648 seconds