Understanding the Auber EZboil DSPR-320

[Bobby_M]

It's a power limiter that is always in force.

 

[Bobby_M]

To add to that statement though... the power limiter would be more impactful when it's trying to perform a large temp change. When it's in the middle of holding a temp, the algorithm would never actually try to run full or "high" power anyway. For example, if you set mOUT to 50%, if it needs to cycle the element occasionally to top off the temp, it would likely only try pulsing at 10% more or less. That's the beauty of the DSPRs.

 

[nsurround]

It is a little late to ask a question on this thread but when you turn the DSPR320 'off' with your controller setup do you lose the mash step program that have been programed previously? There seems to be nothing in the manual that says anything about this in regards to memory etc.

 

[Bobby_M]

It saves the last program even when the module is powered off.

 

[butterblum]

To add to that statement though... the power limiter would be more impactful when it's trying to perform a large temp change. When it's in the middle of holding a temp, the algorithm would never actually try to run full or "high" power anyway. For example, if you set mOUT to 50%, if it needs to cycle the element occasionally to top off the temp, it would likely only try pulsing at 10% more or less. That's the beauty of the DSPRs.

Right - I only ask because the manual doesn't make it sound like a global variable; the documentation seems to imply that it is explicitly for ramp steps only.

 

[Bobby_M]

Right - I only ask because the manual doesn't make it sound like a global variable; the documentation seems to imply that it is explicitly for ramp steps only.

I went back and read the manual again based on this comment and I wanted to agree with you that it's not very clear what the mOUT actually is. They are very clear about the interaction between bAST and bOUT, though it's way more intuitive in the DSPR120 since ther e is only one mash and one boil mode/target. I suspect enabling the bAST (by filling in something other than zero) in the 320 only functions when a program transitions from a temp target to a boil power target step. If mOUT applies to any ramp between target temps, I think I'd argue that mOUT is essentially a global setting in regards to temperature to temperature ramps and it is ignored if the next step is a boil power step.

The real takeaway that I meant on that last post though is that a user should not be concerned with temp maintain situations because the controller is smart enough to know that turning the element on for more than a couple/several milliseconds is going to overshoot the target. When the SV and PV temps are both 150F, you won't find it trying to hold the heat on for more than a few % no matter what you have mOUT set to.