Monday, October 10, 2016
Die Zweite Deutsche SCAE Röstmeisterschaft 2016
Sunday, August 14, 2016
More Alarms
Support for alarms has been around for quite a while and is in heavy use by some. More recently I got asked how to define an alarm that should be triggered 30s after the FCs (First Crack start) event.
FZ-94 (4) – Taking Control
Now that Artisan can talk to the drive controllers, it is not only possible to read the drive speeds, but also to control the drive speeds. However, that needs some further configuration changes on the drive controllers as well as some additional setup on the Artisan side.
Friday, August 12, 2016
FZ-94 (3) – Connecting the Drives
The FZ-94 comes with two Delta VFD-L drive controllers often referred to as frequency drives. One controls the drum speed, the other the air flow via the fan speed. Both are operated manually via a dial. While Artisan can log roasts automatically by reading the three temperature values from the machine via its RS485/MODBUS connection, the drum speed and air flow, both of which have a considerable influence on the resulting roast, have to be manually marked via some user defined buttons or sliders.
Videos: Curve Controlled Roasts with FZ-94 and Artisan
See also: http://kostverlorenvaart.blogspot.nl/2016/08/complete-curve-controlled-coffee-roast.html
The video below may be a little boring for some because I did not cut footage from it to skip any part that may be uneventful. Do slide back and forth at will to see / ignore any part you want.
Saturday, August 6, 2016
FZ-94 (2) – Pushing the Drum Heat Limit Controller
That third MaxWell MTA-48 temperature PID, all the way to the right on the front of the FZ-94, plays a dual role. Besides reporting the actual temperature of the roasting drum, it is wired to control the heaters based on the set temperature limit.
FZ-94 (1) – Bumping up MODBUS
In this first post on an improved FZ-94 setup for Artisan v1.0 we are focusing on the communication between the machine and the software. MODBUS RTU speed in Artisan prior to v1.0 was limited by an issue in an underlying library. That resulted in each request/replay pair to take at least the amount specified by the serial timeout parameter, which defaults to one second.
Subscribe to:
Posts (Atom)