trucknuts

Yea for on-the-go devices I just want to get up to 420F+ from cold as fast as the device can then let it coast and only use preheat on at-home devices. I've played around with replay a bit but never found it useful compared to what TC offers between temp and wattage inputs (at least not in SS). Definitely an under-explored feature for me though so if you have any pointers on better usage of it please do.

Support indicated this was a safety feature when the boost buck overheats. I can't speak to the specific criteria and thresholds used but can say on my board it is indeed components on the top-left overheating. The board could only detect this through an unexpected voltage being produced for a given input so I suspect it's a catch-all error that could be produced a number of different ways. That recording is a Dead Rabbit Pro with 2 x 316L, 4.5mm, 5 wraps of 6 x 0.4x0.1 ribbon, 2 x 28 frames, 38 wrap but I reproduced it on a variety of attys and coils. The cause is a specific temperature condition which is really difficult to reproduce on the standalone board without adding external heat, Too Hot usually gets hit first. In the case though board temps can be barely elevated and this is decently reproducible. The specific cause for me could be different for somebody else but in relation to the Z100C my testing shows it radiates very little heat (especially from the upper-front of the board) so time since prior usage (or charging) has a significant impact. Profile below, at the time of that recording it was 450F and .101 Cold Ohms.

Here is what mine looks like, there is a time gap between the hits (look at vbat jump) as the device is allowed to cool and it's charging during this capture. I already reviewed it with support and verified the cause after pulling the board. What is still a bit of a mystery is why an edge case becomes so pronounced when the board is installed in the Z100C case. Best guess is 75% sandwich case design 25% silicon lottery, the relevant components are operating within specification to the accuracy I can measure.

Can't say whether it's the same issue but on my Z100C charging causes this issue which can persist for up to 30 minutes after charge is stopped. It's a temperature problem on the board that is distinct from the "Too Hot" condition and can present without charging, but the design of this mod causes it to be likely to occur during/after charging.

I ended up doing an RMA on the device (mod not board) and the new one does not have the issue. Can't say what the culprit was but from the perspective of the purchased unit it was some kind of defect.

Yea, I'm on 1.1 SP55.1 INT. This is a 1-day old vendor mod (Hadron Mini) so I guess the retailer is going to be the right channel to address. Interestingly 0.37 coils are working fine so whatever the problem is only affects driving lower resistances. 0.15 ni80 is far within the safe zone going off the 75C and 250C datasheets so sounds like it's just a short straw situation. Only two other posts on the forums sound vaguely similar to this and both of those never answered what their voltages were dropping to.

Phew, that's a relief in the sense that I did not fundamentally misunderstand the DNA board specs. The downside is I definitely have a problem and am fresh out of ideas. Thanks for checking that! In watts profile @50W the 5th fire dropped to 42.5W with the lowest vBatt @3.64v and highest board temp @ 108.9F. Battery is slightly warm (<80F), case is warm (<90F). EScribe shows good voltage so the connection is solid unless there is something happening far faster than the program polling interval. No error or warning messages come up on the display or indicators in EScribe so that should significantly limit the potential conditions...and also possibly make this voodoo/fault territory otherwise there would be some kind of indicator?

Then whenever I think I get the limitation it works different. Just had the same behavior when it hit 112.4F which other times definitely doesn't trigger the lower wattage hit. Feels like there is some other piece of the puzzle going completely over my head.

Yup, as long as the board temp is below 104F when firing everything works perfectly. The hi/low temps of 116F/104F are not always exact but very close. Just did a watts profile @100W and it did 2 normal hits, then 1 at 40W, then waited 35s (until 103.7F) and it hit at 100W again. Alternately if I keep hitting it at 40W after 60s somewhere around 109F it will start hitting at the set power again. Doesn't matter whether it's 50W or 100W (other than how quick the heat builds up), same behavior. Ex. 2@100W, 4@70W, 6@50W before it drops the wattage. It sure looks like it's based on board temperature to me but I can't find any reference to a thermal limit on the board and 47C is a really weird cutoff point.

Longest fire in testing has been 3 seconds but typical is ~1.5s. EDIT: ~60s is the idle time before it resumes normal power levels.

New device today (Hadron Mini) and it's operated like this since first boot. Running SP55.1 and just checked SP46 and the same behavior is experienced. If it is temperature related it occurs at a few degrees lower on 46 than 55.1 (~114F vs ~116F). The mod case heats up to 85F and the battery to 76F but nothing is hot to the touch. Have not checked the board for hotspots so let me know if that is a possible issue (awkward to check but doable). The board temp (from sensor) is ambient +6.5F after 1 hour idle and the room temp (from sensor) values are often are not sane (ambient -10F, ambient +20F, etc.). Nothing else seems notable on the topic of temperature. Have tried Samsung 30T, 40T3, and Molicel P28B with no change between them. Initial screenshots were between a 30T and 40T3. DMing full screenshot of a mostly charged 30T where it does dip very low, but not to cutoff.

In Watt Boost and Watt profiles after several hits the device becomes limited to ~42W. Correlates to board temperature and not getting near cell soft cutoff (2.75). Might be on the wrong track with temperature because it's not the exact same temperature each time and is around the odd figure of 47C. In support of something temperature related if I short fire and keep it above 40C it keeps firing in a restricted wattage for ~60s. If the board temperature drops below 40C before 60s then it fires normally. Any ideas on what is causing this or troubleshooting steps to try? It's 100% consistent to reproduce but the time until it starts firing normally is a bit spotty.