Fade In ~ Fade Out Time

[JoeBingo]

REF: DNA 60C on a Cthulhu Sentinel mod ~ only used in Watts mode. 1.8Ω at 7W

First thing I did when I got the mod was download EScribe and start leaning as I went along, how to modify settings to the style I wanted.

No matter if I came up with a custom theme or the default theme that came with the Sentinel, I always changed the active time from the default 30sec to 7sec.

On the same page, I tried to change the fade-in and fade-out time to 0sec but EScribe always defaulted to a minimum value other than zero for each and I would save upload those values.

Over the course of using the Sentinel, I experienced random glitches. A press of the fire button might not actually fire the mod and sometimes I'd press the fire button only to find the device locked.

The random glitches became annoying. I tried over and over, rotating between service packs, my custom theme and the theme that came with the Sentinel.

Each time I tried those things, I always set the active time to 7sec and fade-in and fade-out to as low as EScribe would allow.

The random glitches continued and I became annoyed to the point of taking the Sentinel down to parade rest to see if I could spot an obvious problem with the device itself and found nothing wrong.

I reassembled the Sentinel and still experienced random glitches to the point of almost ready to toss the mod.

For grins and giggles I decided to leave the fade-in value that came with the Sentinel at 1sec. And I changed the fade-out from 2.98sec to 2sec.

That was a couple of days ago and since making that one change to my pattern of settings modifications, I have not experienced any random glitches at all ... knock on wood.

So you tell me, the Sentinel fixed itself? ... taking it apart and putting it back together eventually changed something?

OR ... the screen fade-in and fade-out value had something to do with it?

I can't wrap my head around how those fade-in and fade-out values could impact mod firing and readiness, but there it is.

Those values are the only thing I tired in EScribe when all else failed to correct random glitches.

I'm using the latest service pack, active time is 7sec, Fade-in is 1sec and Fade-out is 2sec. Works every time all the time now.

I guess I could test it and try zeroing out the Fade-in and Fade-out to near zero as I always had previously to see if the glitches return but decline to do so.

Edited 23 hours ago by JoeBingo

[JoeBingo]

Okay, so I'm thinking maybe there's a "never mind" due LOL

I couldn't wrap my head around how a software setting could affect something that seemed hardware related, so I took the Sentinel back apart.

On the back of the fire button was a sticker. A not well centered sticker on the back (inside) of the fire button and similar in diameter as the button.

I took that sticker off and the Sentinel is more clicky now. I think that sticker may have been ever so slightly interfering with the fire micro switch and circular rubber mount around it.

And in doing so, the mod was glitchy. Sometimes not firing and sometimes when I tried to fire, I would find the DNA 60C locked.

The button seems to work better now and my mind is trying to reason why that sticker was on the back of the fire button to begin with.

If I shake the mod deliberately, I can hear a faint rattle.

At first I thought maybe the sticker had some needed insulation value since the button is metal.

But now I think the sticker was a silencer. With the sticker in place, perhaps no rattle when deliberately shaking the mod.

Since shaking the mod is not something I routinely do, it's a non factor, and without the sticker the mod functions well. 

On the other hand if anyone has any anecdotal information they've found with the fade-in and fade-out settings, do chime in. Thank you. 

Edited 21 hours ago by JoeBingo