Besides I did not have 20 lenses registered, it was actually lens 17 which I wanted to register as 18 (due to GAS) that I noticed an issue with option to register the aperture, after which I went in a kind of bug hunt mode. Those 17 lenses are not rare nor expensive.
24/2.8 AIS
28/2.8 AIS
35/2 AIS
50/1.4 AIS
50/1.2 AIS
105/2.5 AIS
50/1.8 AI
50/1.8 E
50/1.8 Pentacon auto
50/1.7 Pentax M
Voigtlander SL2 lenses - 28/40/55/58/90 - these are chipped, but sometimes I want to use them with a dumb adapter as mechanical only. I like the (new?) feature that allows to record the aperture.
So the new lens was a TT Artisan 100/2.8 “Trioplan”
However due to GAS I skipped 17 and entered the new lens in slot 18 with the aforementioned issues.
EDIT: so this does not add up, I actually have 16 lenses.
Hi Vinnie, thanks.
I did so at the same time as reporting the finding here, but I am always cautious - it could be an issue with my camera and not the firmware. Not likely, but having confirmation by someone else would be conclusive evidence. Unconfirmed it could still be an individual problem.
That’s why I also asked about my Voigtlander 55/1.2
Of course this forum is more about creating beautiful images, the latest and greatest and specs - my questions were more fringe.
So you do not have an issue with pos. 18 and 19?
Do you use the Choose aperture to records = on?
The problem is not entering the information in the Non-CPU lens data, it is being able to select and record the correct aperture while taking the photo.
Maybe I should have been more clear with my description.
18 - 50/1.2
19 - 100/2.8
I will get *f2.8 as maximum aperture when using lens 18
When using lens 19 I am not be able to record any aperture, as it is shown as f- - and I can’t change the value with the control dial.
I’ve got a support ticket with Nikon, supposedly after some additional correspondence asking for additional details, including a request to update to the latest firmware, they’re forwarding the report to their support team. Let’s see if they’ll ever send me an update, but in case they do I will share it here.
Guess not many need to use non-CPU lens numbers 18 and 19…
Just a final follow-up.
Nikon were able to confirm the issue and have said they’ll work on a fix in a future firmware update. Of course that is not a guarantee, it probably is very low on the priority list, but I thought it was excellent customer service by Nikon. They asked for details, reported they were able to replicate and even send me an apology for the inconvenience. Again, my main point was to verify the observation wasn’t limited to my camera. It is hardly something that will stand in the way of anything. Long story short IMO a good example of customer support - even without a fix I appreciate the time they gave my report. I’ve always been impressed by the customer support of both Canon and Nikon in my country.
Firmware 3.0 was just released and I found the following fix in the release notes.
• Fixed the following issues:
- The camera displayed the message “The shutter is closed. To start shooting, press the shutter-release button.” in rare circumstances, when single frame shooting was repeated with the monitor closed.
- The [Maximum aperture] values set for [Lens number] at positions 18 and 19 in the non-CPU lens data feature were not correctly applied when shooting.
Again, it was never a huge problem, but it is nice Nikon made an effort to fix this.
Really like the Zf.
rhorta wrote:
I did not expect Nikon to be this fast
Firmware 3.0 was just released and I found the following fix in the release notes.
• Fixed the following issues:
- The camera displayed the message “The shutter is closed. To start shooting, press the shutter-release button.” in rare circumstances, when single frame shooting was repeated with the monitor closed.
- The [Maximum aperture] values set for [Lens number] at positions 18 and 19 in the non-CPU lens data feature were not correctly applied when shooting.
Again, it was never a huge problem, but it is nice Nikon made an effort to fix this.
Really like the Zf....Show more →
rhorta wrote:
Just a final follow-up.
Nikon were able to confirm the issue and have said they’ll work on a fix in a future firmware update. Of course that is not a guarantee, it probably is very low on the priority list, but I thought it was excellent customer service by Nikon. They asked for details, reported they were able to replicate and even send me an apology for the inconvenience. Again, my main point was to verify the observation wasn’t limited to my camera. It is hardly something that will stand in the way of anything. Long story short IMO a good example of customer support - even without a fix I appreciate the time they gave my report. I’ve always been impressed by the customer support of both Canon and Nikon in my country....Show more →
rbromfield wrote:
How do you report a bug to Nikon with evidence?
Describe the problem, they were able to replicate it after some initial correspondence to provide additional details. If they hadn’t resolved it I would still have been positive about the way they treated the report. It is all about priorities, right? I understood up front this was not a show stopper
rhorta wrote:
Describe the problem, they were able to replicate it after some initial correspondence to provide additional details. If they hadn’t resolved it I would still have been positive about the way they treated the report. It is all about priorities, right? I understood up front this was not a show stopper
Did you send the camera in to Nikon service and then provide the evidence once they received the camera?
