I did not manually set them to off, and it does not appear as though your firmware sets them to off once it determines them bad. I realize though, it is still good to check every now and then in case there is a false positive for a bad die or some other extenuating circumstance. Not sure if there is need for action here on your part based on that tidbit which I really should of assessed prior as a matter of practicality.
Yeah, I see the potential confusion .. my github notes show "dead die" handling. I put quotes on it to signify that Im not talking about completely bad dies. Im talking about ones that "go dead" or "sleep" or "drop" while mining. Ill try to make it more clear in my github notes =)
Basically, the initial reason I started coding the firmware was to improve the miners stability. I knew there were many people that had Titans which required power cycling every once in a while because a die would just stop hashing(go dead, sleep or drop - whatever you wanna call it) and my firmware has a way to wake up these dies and get them hashing again without requiring a full, manual power cycle on the whole miner.
Therefore dies that are completely dead(at the hardware level) need to be set to off manually still just like the original firmware =)
But w/ my new release coming out. Any problematic dies whether dead(and not set to OFF) or partially alive(but still cause constant reset triggering) ... will automatically be appended to a list for bypass of health checking. In other words, yes this will help rigs where people havent set completely dead dies to OFF.