Connect Artisan to Giesen W6A
by 4) Kaffeehaus
Hi all,
I try to connect Artisan 1.3.1 to our Giesen W6A (year of manufacture:
2017) with the Siemens S7-Controller.
Unfortnatly the connect does not run with Error-Msg: S7 Communication Error.
The IP-Adress 192.168.2.180 is definitly correct. We use the
Giesen-Coffeeroaster-Software at this time with this IP-Adress.
I have try both settings for Giesen with the same failure:
- Giesen -> WxA
- Giesen -> WxA+
Does anyone have the same configuration which works?
Or another ideas, why that does not work?
Thanks for your helps...
Kind regards,
Philipp
1 year, 5 months
Artisan and the hottop b-2k+
by Roy Mongiovi
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?
1 year, 6 months
Artisan 1.3 startup takes long on Fedora 28.4
by Dieter Hönigmann
Hello Artisan Linux users,
Upgraded Artisan 1.2 to Artisan 1.3 a week ago on an admittedly old
Lenovo T61p running Fedora 28. Since the upgrade starting Artisan takes
more than a minute. Anyone with experiencing similar problems?
Cheers,
Dieter
--
Dieter Hönigmann
Head Barista & Roast Master
²²Beans Specialty Coffee Lab
__________________________________________________________________
n22 e.U. - Dr Dieter Hönigmann, MSc
Neunkirchner Str 22 - 2700 Wiener Neustadt - Austria - Europe
__________________________________________________________________
t: +43 699 10 887 325 f: +43 2622 34774
m: dieter(a)22beans.at w: 22beans.at fb: facebook.com/n22beans
1 year, 6 months
1.3.0 changes to Phases LCDs - are defaults configurable?
by victory＠mailbox.org
Hi all,
Just did my first roast using 1.3.0 and noticed that the Phases LCDs are
working a little differently.
The release notes say that time-to-DRY and time-to-FC were added, and it
looks like these are now the defaults. I have to right-click on the values
to show when DRY and FC are expected to occur. While I do sometimes like to
see the time-to figure, I'm used to watching for when the events will occur
and would prefer not to have to switch to that view each time I roast.
Also, I think the older versions would switch to %DEV immediately upon 1Cs.
Now it seems that a FC time counter is showed instead, and I have to
left-click on the value to see %DEV (I concede that maybe it does change
automatically and there's a delay that I didn't notice before, and it's just
a coincidence that it changes when I left-click on the value.) Again, the
time since 1Cs is useful sometimes, but I would much prefer to see %DEV as
the default when 1C starts, as in previous versions.
I couldn't find any configuration options for the Phases LCDs, other than to
turn them on and off. Are the default behaviors for the Phases LCDs
configurable? If not, I'd appreciate if we could go back to the old
defaults.
Incidentally, the flyout help on the Phases LCDs says to right-click to
cycle through time, percentage and temp. But the behavior when
right-clicking doesn't correlate with that. It looks like the first box,
DRY% is toggling between % and TEMP and the DRY and FC boxes are toggling
between time-to and when. I think the DRY% box should show a different
header or maybe the % should go away when it shows TEMP, and the flyout help
for the DRY% and DRY/FC boxes should be different. Yet another problem is
that I kept trying to right-click on the headers, which did nothing. Took me
a few tries to realize I had to click on the values. I found the flyouts and
behavior confusing.
Finally, is this the best place to report issues?
Dick Green
1 year, 6 months
