I have seen the videos where a Background profile is loaded. But I haven’t found the blog or other write-ups on how to build the background profile and save it for loading during future roasts.
would you point me to details on how to build a background profile?
For clarity I enclose two screen snapshots of Artisan in two different configurations.
When controlling the La Pavoni & PXG-4 Fuji PID, the Artisan PID also communicates the PID settings to the Fuji and the heating element energy level is increased/decreased to keep the target temp.
When controlling the FZ-94, the Artisan PID is used to increase/decrease the fan/airspeed. No external PID is used, just the frequency drive that controls the airspeed fan and that Artisan knows how to communicate with. This used to be impossible, but Marko worked with Coffee-Tech to enable this new feature also for present and future owners of the roaster.
So yes, Artisan has a built in software PID and if it’s also communicating to an external PID, that works well together.
> Op 23 okt. 2016, om 15:27 heeft Henning Christensen <henningchristensen1(a)gmail.com> het volgende geschreven:
> Hello Frans,
> I just have a short question regarding your post. Does the new beta version have a built in PID or is it a function that activates an external PID regulator.
> I’m roasting on an Artisan 6M using the Artisan software for my records and to help me with the all manual functions.
> Best regards
I just uploaded the third public beta of the upcoming Artisan v1.0.0 to Github.
This one is a quite stable pre-release of the upcoming Artisan v1.0.0 release. Thanks to everyone who provided feedback and suggestions on the previous versions! I'd love to get feedback also on this build just to ensure that things end up in a stable and productive final v1.0.0.
If you install this version and run into problems you can (as with all past and future versions) just uninstall and re-install your previous working build without loosing any of your settings.
• adds SV slider to the Fuji PXG
• adds pyinstaller build setup for Mac OS X
• adds flag to disable/enable the number key shortcuts for switching palettes
• adds MODBUS scanner
• adds Custom Events clustering
• adds flag to automatically open roast properties on CHARGE
• adds Yoctopuce VirtualHub support for acessing remote Yoctopuce devices over the network
• adds automatic unit conversion for Yoctopuce devices
• adds profile C<->F batch conversion
• adds a field for green bean temperature
• adds p-i-d button action
• makes development percentage the default for the phases lcds
• increases resolution for Yoctopuce devices
• fixes Fuji PXG duty internal overflow for values from -3% to 0%
• fixes regression of external and internal TC4 PID hangs introduced in beta2
• fixes regression of low F RoR cut-off introduced in beta2
• fixes handling of external program paths containing accent characters on Windows
• fixes handling of accent characters in autosave path
For full list of changes, fixes and new features of v1.0.0 w.r.t. the previous version see the full release at history https://github.com/artisan-roaster-scope/artisan/blob/master/wiki/ReleaseHi….
The main new features will be described by posts on the Artisan blog soon.
As always, thanks for all that support the development of this software either by giving valuable feedback or by donating via the donation button on the Artisan GitHub home at https://github.com/artisan-roaster-scope/artisan/blob/master/README.md.
Slider changes can generate (custom) events. There are 4 custom events that you can name freely in the first tab of the Events dialog (menu Config >> Events). In the same dialog you can activate a slider per event. If you now move the slider during a recording to a new value, a new such event is generated recording the time and value of that slider along the other data in the profiles.
The visualisation of custom events (during recording and after recording) is controlled by the flag "Events" in the first tab ("Config") of the Events dialog and the "Bars" combo box next to it. With that combo box you can select the visualisation. See https://artisan-roasterscope.blogspot.de/2013/02/events-buttons-and-palette…
> On 17 Oct 2016, at 00:49, Sam <smaca69(a)gmail.com> wrote:
> Is it possible to plot slider values while roasting? I am using the
> slider to set my gas settings during the roast and would like to plot
> those values.
> Artisan-User mailing list
sorry to hear that. The latest beta2 of Artisan v1.0 (online on Github) resolve an issue with the palette that could lead to loosing button definitions. Additionally, the next beta3 will add a flag to deactivate/activate those number key short cuts to switch palettes.
Hope that will help you on this,
> On 06 Oct 2016, at 23:42, George Stimak <elatedmonk(a)gmail.com> wrote:
> I've had this problem for years, but I have custom event buttons on my roast profiles that correspond with different machine changes that the operator does during the roast. If you happen to press any number pad number, those buttons are lost forever. I've tried saving them, creating a profile for them, even loading that profile, but no matter what happens they are lost forever if you ever accidentally press a number key during a roast.
> Can there be in the next release a way to prevent the "pallet" from being changed upon a number press? Or make sure the profile/pallet save/load feature actually works. I can make a video and send it to show how it is gone forever and I have to recreate the custom event buttons every time a key pad number is pressed.
> Or any advice how to prevent this would be amazing. After adding the same event buttons 100+ times, I'm beginning to go crazy.
> Artisan-User mailing list
Which roaster did you buy?
I hope you too will share your reports / blogs / profiles ;-)
In my reports and video from the event I purposely did not record the exact data for the displayed roast and any profile has been moved backwards or forwards in the ‘storyline’ so it does not reflect the actions of the roaster in the footage immediately before/after the profile is shown. This to prevent certain comments / misinterpretations.
On the second day I found the roasting place a little cooler than the first but all roasters used the same bean on the same day, at the same temperature.
TP can be influenced by the amount of heat applied before starting the Artisan recording of probe data, way before charging the beans, so you won’t find that warmup-information in the graphs.
> Op 9 okt. 2016, om 17:49 heeft Philip Hirschy <mmc(a)cableone.net> het volgende geschreven:
> Franz, et.al.
> Since you published the results of last year’s competition I have indeed studied the profiles carefully, and this led my purchase of a roaster. I look forward to the results again.
> One thing that is missing from all of these profiles is the temperature of the beans before charging the roaster. It is the one thing which I have tried to analyse in the data and could not figure out the missing factor. The TP temperatures did not seem to be connected to gas, charge temp. etc. Last year’s winner had a TP temp higher than the others.
> Are all these bean starting at the same room temperature?
> From: artisan-user-bounces(a)lists.einfachkaffee.de <mailto:firstname.lastname@example.org> [mailto:email@example.com <mailto:firstname.lastname@example.org>] On Behalf Of Frans Goddijn
> Sent: Saturday, October 8, 2016 9:41 AM
> To: artisan-user(a)lists.einfachkaffee.de <mailto:email@example.com>
> Subject: [Artisan-user] Artisan used at the 2016 German SCAE roastmaster competition (and other pictures)
> http://kostverlorenvaart.blogspot.nl/2016/10/images-from-german-2016-scae.h… <http://kostverlorenvaart.blogspot.nl/2016/10/images-from-german-2016-scae.h…>