Kaffelogic community

Hello everyone, first post on this forum here.

Been enjoying my Nano so far. However, ever since updating to the latest firmware (Version 7.13.9.1881) and latest Studio, my roaster has been saving roast levels as some nonsensical float values since 1 Apr. (see screenshot) The roaster will also indicate the same long float value on the console.

The correct values are around 2.9 and 3.0 based on my roast profile's definition of roast levels vis-a-vis drop temperature.

Anyone else having this issue and knows how to resolve it?

My concern would be the roaster's ability to repeat roasts if the roast levels are saved incorrectly.

Any help would be appreciated, thanks!

The fix for this issue is now available for beta testing here: https://drive.google.com/drive/folders/ ... M99T-ccOit

Hi all,
I did my first roast with the new live tracking feature and this latest firmware (KN1007B-7.13.11.1883.rp2040 that I downloaded from the Google drive as per above post). It seemed to work fine for me.

I did four 170gm roasts back to back. I got a fault (see error message in attached photo) at the end of the first batch. I could not clear it without restarting the roaster. It did not give the error on the subsequent three batches. All data in the log files looked correct.

All seemed to work well. It is nice to be able to log the CC and FC on the computer. Really looking forward to being able to get the Wifi module for realtime control of the profile. I am also hoping we will be able to run it on an iPad.

Here is the attachment again, I guess I didn't complete the upload the other day.

Ron in Van wrote: ↑Fri 05 Apr, 2024 12:34 pm Hi all,
I did my first roast with the new live tracking feature and this latest firmware (KN1007B-7.13.11.1883.rp2040 that I downloaded from the Google drive as per above post). It seemed to work fine for me.

I did four 170gm roasts back to back. I got a fault (see error message in attached photo) at the end of the first batch. I could not clear it without restarting the roaster. It did not give the error on the subsequent three batches. All data in the log files looked correct.

All seemed to work well. It is nice to be able to log the CC and FC on the computer. Really looking forward to being able to get the Wifi module for realtime control of the profile. I am also hoping we will be able to run it on an iPad.

You forgot to attach the photo of the error message…

The "Unexpected excep" error can occur in rare cases by chance. If it goes away after power-cycling the roaster, as you have described, then it is safe to ignore it. Action is only required if it occurs persistently.

Got the same fault, im on 7.13.15

What are those rare cases ?

artis wrote: ↑Thu 09 May, 2024 2:32 pm Got the same fault, im on 7.13.15

What are those rare cases ?

Essentially this particular error message means the firmware has crashed and needs to be restarted. As with any software this can happen from time to time without a specific explanation being available. If it becomes a replicable pattern we can investigate and fix, but otherwise on the rare occasion you see this message simply power off and on and keep on roasting.

Hi, In reading this post I'm wondering if the roast was actually affected or if it's just the numbers that you were getting. Thanks

OP here.

My issue has been resolved after updating the firmware to the latest version and I no longer have weird roast levels saved into the logs and previous roasts.

The roast was not actually affected (since I manually stop the roasts), and its just the numbers that were saved into the logs and roaster. It did make it difficult to replicate the same roast (as it is not possible to set the roast level to what was saved) however and made me doubt that the roaster could stop at the same level as the previous roast.

I still get random disconnects, live graph is not usable.
I believe its the reason for uncaught exceptions.

Got another one in the middle of roast while re-pluging cable after disconect.

Any eta for fixes?