Suddenly can't set ISO

[catherineryanhyde]

I'm using BN 2.1.2 with a Nikon D810A camera. Just like I've done every clear night for years. Last night all was well. Tonight I can set the number of subs, the exposure time, and the pause, but the ISO setting is frozen at the default, 1600. When I click the down arrow to get the drop-down menu, it either does nothing, or the menu flashes for a fraction of a second. I cannot stress too strongly that I tried it with a different D810A (I have several) and got the same result. So it's not that a setting was somehow changed on the camera. I might have accidentally changed a setting on BN, but I can't imagine what setting. Is there even a setting to lock the ISO on the software? 

[admin]

If the issue persists, got to settings -> advance settings, and delete the cache as astroman suggested in an earlier post. Then restart BYN, and see if this issue is resolved.

[astroman133]

Is the camera in Manual shooting mode?

[astroman133]

It could be that the cached settings have become corrupted. You could try to  Clear Cache Data from the Advanced Settings dialog. Then restart BYN while making sure that the camera is in Manual shooting mode.

[astroman133]

You should also upgrade to BYN 2.1.3. It has some fixes and a new Nikon SDK.

[catherineryanhyde]

17 minutes ago, astroman133 said:

Is the camera in Manual shooting mode?

Yes it is.

[catherineryanhyde]

10 minutes ago, astroman133 said:

You should also upgrade to BYN 2.1.3. It has some fixes and a new Nikon SDK.

Okay, I will. Thanks. I was hoping to salvage the night with an idea but I figured I'd at least have to uninstall and reinstall. To do that I have to drag everything downstairs where I can access my network. But I'll definitely do that (upgrade). Just not tonight.

[astroman133]

Uninstall and reinstall are unlikely to fix a corrupted data file. You should try that suggestion first.

[catherineryanhyde]

1 hour ago, astroman133 said:

Uninstall and reinstall are unlikely to fix a corrupted data file. You should try that suggestion first.

Yes, I will. I just didn't realize there was a newer version until you said so.

[astroman133]

Did our suggestions help to resolve your issue?

[catherineryanhyde]

Just now, astroman133 said:

Did our suggestions help to resolve your issue?

Sorry for the radio silence. I was away yesterday and today, and didn't get a chance to tend to this. Tomorrow morning I'll clear the cache as instructed and update. I'll let you know one way or another how it goes. I really appreciate the attention you've paid to this.

[catherineryanhyde]

11 hours ago, catherineryanhyde said:

Sorry for the radio silence. I was away yesterday and today, and didn't get a chance to tend to this. Tomorrow morning I'll clear the cache as instructed and update. I'll let you know one way or another how it goes. I really appreciate the attention you've paid to this.

 

11 hours ago, astroman133 said:

Did our suggestions help to resolve your issue?

I cleared the cache data and the problem was immediately solved, though I will go on to update to the newest version on general principles. Thank you for your help. I'll remember to try that if there's ever another unexpected glitch.

[astroman133]

Thanks for letting us know.