IFD Dimming after Database Update

Just chiming in to say to say that I have this exact same problem. Dimming works as configured/expected until you do a database update. Then it breaks until you just go back into maintenance mode and look at the lighting page. Then it fixes everything back up again until the next database update. I made a video today of me reproducing the issue and will be opening a support case.

AviSteve wrote: I guess I'll wait to see the video, but that's certainly an odd one.  I load databases all the time and haven't noticed such behavior.  Do you both have the same database coverage?

@AViSteve So one thing that came up on the COPA forums the units that are doing this are possibly all using "DimBus" and not "Photocell" for the dimmer, what's your demo unit using?

gremlin wrote: @AViSteve So one thing that came up on the COPA forums the units that are doing this are possibly all using "DimBus" and not "Photocell" for the dimmer, what's your demo unit using?

Edited by AviSteve - 09 Sep 2024 at 9:12am

gremlin wrote: That would be great to test, it does seem to be common, and I much prefer to have control over it and have it match the other instruments as it has since I bought them.

@AviSteve so have you managed to reproduce this in house? It's been several weeks and would at least like to know they have an in house repro of this issue that several of us seem to have with every up date.

Curious @AviSteve... did you try to repro it in a G1/G2 Cirrus using the dimming bus in there?  I am just wondering if perhaps the issue involves a specific kind of dimming circuit... I can repro mine every time I do the DB update... its very reliable in terms of reproduction ability. 

This does happen to me on every single database update at this point in time, and we have enough other people demonstrating it that it should be reproducible.

Hi all, I've been having this same issue for about 1-1.5 years or so as well, requiring me to go into the settings page showing the dim settings to get the settings present their to persist after each database update. For the first 5-6 months I assumed I just had incorrect settings that weren't suited to the proper transition levels, brightness settings or curves, but after a number of us were speaking on the Cirrus forums it appeared that this issue is more widespread than an individual user or two. My settings are perfect with the exception of after I apply a database update. Any guidance on resolution would be much appreciated.

Avicurve had no impact other than the curve wasn’t ideal and was still too bright at night and didn’t provide an even distribution through my dimmer range. I wanted half brightness to be roughly half way through my brightness range rather than being 80% bright. Also I’ve had this behavior with the Mx input settings photo or dimbus. I keep my user settings on dimbus though. FWIW I have 2 user profiles but would be surprised if that had any impact.