I'm relatively new to artisan. Been using RoastLogger for years but now that
I have my phidget 1048 I don't need the camera/ocr feature anymore.
I haven't been able to locate the help file or information about the
settings under Config-Device - Phidgets tab. For instance, Async check
boxes, raw data, change etc. I've found everything on the github page, but
maybe I just haven't been successful in pinpointing the proper area to look.
Secondly- I'm roasting on a Diedrich IR-24, which has a thicker J
thermocouple than the one I've hooked up to artisan, which is a K type 1/8in
I purchased here:
The temperatures are around 30 degrees F higher on the thinner K
thermocouple than what the roaster is reporting, even though my
thermocouples in the roaster are mounted next to each other (didn't want to
piggyback on BT of the roaster to phidgets)
Does anyone have any experience in this area? Perhaps the simple fact that
the probe is thinner means the readings will be different, but I do not
know. It would appear that the readings on the roaster are accurate while
the other is much hotter.
Just getting started, and appreciate any guidance.
I've been using artisan to control my 2k+ since it was released. I just
can't seem to find smoothing parameters that get me a reasonable ROR curve
once beans are added and the ROR decreases. It looks like the top half of a
sin curve. Marko made a posting recently to Home-Barista that blames that
on the fact that resolution of the 2k+ temperature is integer only with no
fraction of a degree. So when the temperature increases by a degree that
translates into a sudden spike in the ROR which artisan smooths into the sin
curve I see. The lower the ROR gets the more pronounced the sin humps get.
So I'm wondering if it's possible to have artisan control the hottop
temperature and fan speed while at the same time using phidgets to report
the temperature? Or do I have to scrap the whole 2k+ stuff and go with
something like the HTC+TC4C?
When opening artisan, the view has sliders hidden. And although I don't
have them set up (and so am only using the pre-defined ones) i see this
is the same for buttons… maybe other items, too
Anyway. Either, is there a way to make them visible when opening the app
through a preference, oy by retaining the state the app was closed in?
My error, probably, but: I was in a hurry, and I clicked 'don't save'
when closing artisan, thinking that because I had autosave on, the file
was already saved… it wasn't. Is the data stored anywhere that there is
any way to recover the last roast data?
artisan v1.2.0 (3)
I am using artisan for batch roasting and want to be able to use it to
compare roasts. I'm visual so using the File/Report/Ranking/Web… is a
good feature. However when opening roasts this way, I am only seeing the
BT (and rate of rise) data, but not the ET readings. The ET data is in
Ideally I would be able to just turn on the BT & ET (and any other
probes with data).
Also, I am not sure why the info coming in is using the template for the
name instead of the file name: In the spreadsheet at the top, for "Nr"
you see are "DEFT_DATE_COUNTRY_Region-GROWER_10K_xxlb_45 " which is
the auto save name template I have set up, I then go back in and rename
to fill in the correct info (actually it would be great if the batch
naming could use the roast properties info when saving the file, but
that is a separate issue). These files have been re-named… so seems that
they should show that rather than the template…
One side issue (small one) that comes from this is it would also be good
to be able to use a short name for identifying the curves: since I use
long file names, the legend at the bottom gets pretty clumsy. Not sure
what the best solution would be here,, A,B,C…?
Screenshot attached, and here is my set up:
Mac OSX 10.13.3 (newer MacBook Pro retina)
Artisan 1.2.0. (3)
Phidgets 1048 with 2 inputs (BT, ET), current driver
Let me know what else you may need to diagnose
Happy to hear that solved it!
I have no idea how the colours may have changed. Did you install a new version of the software? Did you save a recent configuration? If so, did you try loading that previous successful configuration file to see if that would solve it?
> Op 9 mrt. 2018, om 17:08 heeft Brian Højmark Larsen <brian(a)hoejmark.de> het volgende geschreven:
> Hi Frans. You are go(o)d. That seems to be the problem. Black BG, black digits. But did that change by it self?
> HØJMARK ROASTERS
> brian højmark larsen
> schliemannstr. 12 <http://maps.google.com/maps?q=schliemannstr.+12,+10437+berlin&hl=en&cd=1&ei…>
> 10437 berlin <http://maps.google.com/maps?q=schliemannstr.+12,+10437+berlin&hl=en&cd=1&ei…>
> h +49(0)3078085896
> m +49(0)17622230278
> i instagram.com/hoejmark <http://instagram.com/hoejmark>
> w www.hoejmarkroasters.com <http://www.hoejmarkroasters.com/>
>> On 09 Mar 2018, at 15:28, Frans Goddijn <frans(a)goddijn.com <mailto:firstname.lastname@example.org>> wrote:
>> I asked:
>>>> Could you include screen snapshots of the “blank” LCD and of the relevant menus for how it would look?
>> Brian replied:
>>> Op 9 mrt. 2018, om 14:51 heeft Brian Højmark Larsen <brian(a)hoejmark.de <mailto:email@example.com>> het volgende geschreven:
>>> Here is a screen dump showing the blank BT LCD<Capture.PNG>
>> Here is the way you can make the LCD “disappear” m=by making it the same color as the background:
>> The menu:
>> <Schermafbeelding 2018-03-09 om 15.21.41.png>
>> “Disappear act”:
>> <Schermafbeelding 2018-03-09 om 15.21.32.png>
>> Made visible again:
>> <Schermafbeelding 2018-03-09 om 15.19.14.png>
>> Artisan-User mailing list
>> Artisan-User(a)lists.einfachkaffee.de <mailto:Artisan-User@lists.einfachkaffee.de>
>> unsubscribe via https://mailman.ghostdub.de/mailman/listinfo/artisan-user
>> Could you include screen snapshots of the “blank” LCD and of the relevant menus for how it would look?
> Op 9 mrt. 2018, om 14:51 heeft Brian Højmark Larsen <brian(a)hoejmark.de> het volgende geschreven:
> Here is a screen dump showing the blank BT LCD<Capture.PNG>
Here is the way you can make the LCD “disappear” m=by making it the same color as the background:
Made visible again: