I do not understand how these can not be an issue. The set point of the controller is lost electronically so that the temp starts slowly dropping. At some point, the controller thinks that pellets are not feeding or that the fire has gone out. Either triggers a shut down. The loss of pairing may trigger the loss of temp set point. The restart of the unit in the middle of the run may trigger a flare up due to either pellets being dumped in right before set point loss or being dumped in to regain the temp. All of this depends on the cycle (stage) of the PID and how it averages the temp at a given time. All of this is due to programing of the PID and all of the components that interact with it (app, OS, firmware, motor, sensor, etc.).
That is exactly what happened to me during my last cook: loss of WiFi control —> loss of setpoint —> lowering temp —> low temp warning —> had to re-enter setpoint —> rapid pellet feed —> flare up and overshoot by 100 degrees —> burned food —> manual shutdown —> late dinner —> unhappy wife.
JpsBBQ, neither Dassman5 or myself ever talked about wifi loss. The app on the phone has the ability to control the unit (set temp, shut down, etc.). So they are not independent. Something is causing the controller to lose temp set point and then the PID takes over and stuff happens. What that something is is unknown at this time. It may be part of the app, OS, or firmware that is disrupted by external factors (phone call, text) or internal factors (incorrect loop in the PID). Since others are doing fine, I am sure that Dassman5 and myself have a component that is different from what others have (a different series of chips, converters, etc.). My unit ran much better prior to the recent updates. But which one? When you throw three new factors into the mix all at once, it is hard to run diagnostics. And go backwards to an earlier version.
From my perspective set point drop means a significant deviation from the controller setpoint. In this instance the set point was 375F, but SF temp continued to drop to around 160F, the point at which I received the low-temp warning.
Agreed.
But was there a temp set showing on either the mobile app or the controller screen? In my case, as shown by the images below, the temp set point is lost from the controller (and the app) and you are required to re-enter the desired temp on the controller. The app will not work, just like when you start up. On both the app and the controller, the temp set point is shown by dashes. If you let the unit continue at this point, you end up with low temp warning and a shut down. If you re-enter a temp set point, you may get a flare up with an overshoot on the temp (this depends on how soon you catch it and how far the temp has dropped). What Dassman5 is talking about is what I would consider a problem with programing of the PID, which gets stuck in a downward loop.
In my case the connect app on my phone showed the last temp on the SF control probe as well as the set point before losing the connection, while the temp on the SF continued to show that it was dropping, as confirmed by the ambient air probe I installed on probe port #4. However, when I first manually changed the setpoint to a higher temp, the SF did not react and the temp continued to fall.
I need to do the same.
Unfortunately, I am suffering from COVID-induced belt shrinkage. 
This is going to be a hard thing to troubleshoot.Folks, I hate to drag this up again but I have to report what I see. The kids are coming over tonight and I had a brisket. So, with all of the problems that I have had with the latest string of updates, I was reluctant to put it on. But I did. The SF ran for about 1 1/2 hours before it lost the temp set point again. It displayed on the app and the controller dashes like I have shown before. I happened to be around the house and caught it before the temp had dropped too much. I manually entered the temp on the controller and off we went. I did not get a pellet dump or flare (which had been seen when the temp drops greatly). The SF then ran without a bump for 17 hours straight. It did not even think about doing anything wrong (because I was sleeping with both eyes open).
Obviously, some of us are having unique problems while the majority of you are smoking away. I did not have these kinds of problems until the latest updates. I am beginning to think they may be due to the phone app and phone activity. Because the app can control temp, maybe it is deleting (removing) the temp set point. I do not know but it the problem was solely due to an OS/firmware problem, getting 17 hours of smooth operation might be unlikely.
Maybe I should do the experiment and turn off my phone and just keep cooking.
This stuff is out of my wheelhouse, but could this be an Android thing or is it on both platforms?
Create an account or login to comment
You must be a member in order to leave a comment
Create account
Create an account on our community. It's easy!
Log in
Already have an account? Log in here.
