IKAWA online profile editor ( with QR codes )

#1: Post by **Esteve** » September 28th, 2023, 5:51 am

With a lot of inspiration from the IKAWA Home - profiles thread I am releasing a beta version of an online tool to create and edit IKAWA profiles. It is mostly what I would have loved from the standard app to have. Open to feedback to add features to make it more useful.

http://www.beandecoder.com

It is by no means finished and before sending a profile to the roaster one should double check it

Some features:
- Start from scratch or import and edit IKAWA profiles from URL
- Works ok on mobile. Best used with a larger screen.
- Compare with previously generated profiles (they get stored locally on your browser)
- Generate IKAWA links for both PRO and HOME versions.
- I hope easy to use
- Parametric profile creation, incorporated GDM528 method as well as a ramp+quadratic
- Provides some statistics based on FC and T. Brown.
- The URL can also be imported to Artisan by selecting device IKAWA and Import IKAWA URL

Screenshoot of the app:

Generated QR codes:

Import to IKAWA home:

Import into PRO:

Artisan import:

#2: Post by **MNate** » September 28th, 2023, 9:23 am

Wait, seriously? That's excellent. I've just given a quick look but I'll definitely give it a go. Thanks for the work and sharing it!

#3: Post by **mathof** » September 28th, 2023, 10:49 am

Esteve wrote:With a lot of inspiration from the IKAWA Home - profiles thread I am releasing a beta version of an online tool to create and edit IKAWA profiles. It is mostly what I would have loved from the standard app to have. Open to feedback to add features to make it more useful.

http://www.beandecoder.com

This is brilliant. I look forward to trying it out. Thank you.

September 28th, 2023, 11:52 am

MNate, Mathof, thanks! Hope you find it useful and please let me know if you find improvements. Not at all a finished "app".

#5: Post by **GDM528** » September 28th, 2023, 3:53 pm

Epic.

You could stop here with a very useful tool as-is, but since you asked:

1) I suggest capping the initial setpoint jump at no shorter than 30 seconds. I found that very occasionally, a very fast initial ramp can flummox the IKAWA's internal PID algorithm, causing it to follow the setpoints, but offset at a much (many 10's of degrees C) lower temperature.

2) Adding a RoR curve to the chart would align well with all the Artisan roast logs I see. Only six setpoints can make it look kinda chunky, unless you straight-line extrapolate from the midpoints between each setpoint.

3) FC temperature is technically the inlet temperature at which FC is observed. Making all temperatures inlet-referred can enable user input first-order correction for environmental conditions and source material. As such, I have at times compared roasts with greens that had different FC thresholds, so you may want to consider the same for your comparison table.

September 29th, 2023, 4:18 am

GDM528 wrote:Epic.

Thanks!

GDM528 wrote: 1) I suggest capping the initial setpoint jump at no shorter than 30 seconds. I found that very occasionally, a very fast initial ramp can flummox the IKAWA's internal PID algorithm, causing it to follow the setpoints, but offset at a much (many 10's of degrees C) lower temperature.

Oh, I have never experienced this wild behaviour on the PID. I think it is better to let it to the user decide, maybe someone has fun abusing the PID. I think it was Robert McKeon that had a cool post making the Decent Espresso do fun stuff with the PID.
Another thing that I have not tested much and it is supported on the PRO but not sure on the HOME, is setting a temperature higher than 50C for time 0. It is not allowed on the Home App, but it is on the PRO. Ikawa has a few home profiles that are generated that way but I have not really tested it, out of caution.

GDM528 wrote: 2) Adding a RoR curve to the chart would align well with all the Artisan roast logs I see. Only six setpoints can make it look kinda chunky, unless you straight-line extrapolate from the midpoints between each setpoint.

Done. Not sure if I did it the best way. I interpolate lineally the points of the profile to generate a profile with more points, then I smoth it over 1 minute then get the ROR.

GDM528 wrote: 3) FC temperature is technically the inlet temperature at which FC is observed. Making all temperatures inlet-referred can enable user input first-order correction for environmental conditions and source material. As such, I have at times compared roasts with greens that had different FC thresholds, so you may want to consider the same for your comparison table.

Do you mean doubling the T FC and T BRN input fields ? That is easy and I could make it such that when you edit the first it copies to the seccond (usual comparison). But if you modifies the second field it dosn't change the first (for the fewer cases where you want to compare different greens).

#7: Post by **viteaux** » September 29th, 2023, 9:56 am

This is so cool, thank you so much Esteve!!!!

#8: Post by **GDM528** » September 29th, 2023, 3:26 pm

Esteve wrote:Do you mean doubling the T FC and T BRN input fields ?

Exactly. Independent thresholds for each roast compared. That will accommodate adjustments based on the particular greens (which could link to your "Coffee Name" entry), and perhaps eventually, environmental effects like ambient humidity and altitude.

It would only take one roasting run to figure out how to 'tune' the thresholds for the particular greens - a pretty low overhead, given the IKAWA's tiny batch size. It'll typically be the same for most greens, but there are some weird ones out there.

#9: Post by **fjen** » October 1st, 2023, 2:26 pm

Amazing!!! Definitely looking forward to try this out today!

#10: Post by **fjen** » October 1st, 2023, 2:48 pm

Was playing around a little bit and I'm super impressed with the functionality already. This beats fiddling with the phone app 10000%.

Since you asked for some feedback [I'm sorry to nit pick but you asked!!!], I have the following suggestions:

Add an
```
alert("Populating profile will clear set points");
```
to the "Populate Profile" button. I didn't know it would clear my temp set points if I had any data in there
Round the values in the chart, right now it seems to go to like 20 sigfigs which isn't super useful and can be a little cluttered
Ability to remove a profile from the compare tab - right now, I can't seem to find a way to get the graph to not compare after I load in something to compare it to.
I wonder if it would be possible to go "backwards" from the statistics to the temperature set points. In other words, instead of specifying the temperature points, specify how long you want each phase to be, FC time, Dry time, etc... and have it work backwards the temperatures.
This would be potentially an entire architecture change, but provide the option to have "user accounts" (tied to GitHub perhaps) where users can save down their profiles in case of a browser data wipe (such as "clear cache"). One of the cool ways I found a site called http://www.keyboard-layout-editor.com/ did it is using GitHub as the Auth provider and saving the raw data to a "Github Snippet" which can act as a very generous text store. That way, there is no true backend to be maintained.