RT2 will feature ways to automate the roast by temperature in a few releases. This is being worked on now.
If there are specific functions for roast analysis that you feel are useful, please let us know and we will consider to add it.
Thank you. For automating roasts the following would be helpful:
Changes to P,D,F based on
- Temperature trigger (most helpful. This one is the most important. If only one option is available it would be this.)
- Trigger based on Event (YT, FCs, FCe) The trigger can be based on the time of the event or a specific time after the event. ( Second most helpful. )
- Time trigger (least helpful of the 3)
Roast analysis:
- Similar to Artisan/Roast /Properties/General A way to record pre and post weight, volume, density and then derive a roast report similar to Artisan/File/Report/Roast
(Extra requests if possible)
Graph:
- Having x and y reference lines.
- Shading option for FCs to FCe, SCs to SCe
- Predetermined shading option for phases: Drying time (YT), Maillard YT to FCs, FCs to end (similar to Artisan/Config/Phases)
Thank you. The Bullet is a state of the art, incredible roaster! I am looking forward to future RT releases!
2 Likes
Wow! I’ve never used Artisan and I’m just trying to understand RoasTime, so I had no frame of reference for helping with features on RoasTime. But, I like everything that @pnrenton said.
One thing to add, if it’s not there already: editing an existing profile and/or designing one from scratch would be great. That way, you don’t have to record a perfect live performance - you can get close, then tweak it, or simply program it to do what you want.
Now that I think about it, configurable alarms would be great. Like the time or temperature trigger @pnrenton suggested, but tied to a sound file or various prerecorded beep sounds. That would allow, say, one profile to be easily used for various roast levels of the same beans, with prompts or beeps defined for the time or temp of completion for each level.
Thank you celticcupcoffee! Before the Bullet, I roasted on a Hottop and made extensive use of Alarm files. Thank you for mentioning that. That is one more thing that I would put at the top of the list for RT development. Please! Please! have an Alarm file equivalent for RT. Being able to trigger P,D,F events precisely and reliably based on Time, Temp or other events like YT, FCs, FCe, ROR levels enables you to roast with precision and make repeatable roasts. If you find errors in your roast you can make proactive tweaks to the Alarm file and improve the next roast.
As celticcupcoffee says, rather than recording a live performance and using it for "Playback"as is done now, it would be nice to have a program to make a list all of the P,D,F events you want to control for a roast based on the triggers that I have previously listed and then run that program to see the results. Each roast profile could be saved, tweaked and run over and over.
Again, when I roasted with Artisan, the Alarm files were a great way to automate a roast and get reliable, repeatable results. It was one of the greatest items about Artisan. I highly recommend that RT programmers put an Alarm file equivalent high on their development list.
I just noticed v1.6.1 has support for IBTS and v1.5-v2.0 Aillio Roasters.
Has anyone tried the new 1.6.2?
The code change in 1.6.2 was for a Phidgets problem on MacOS - I don’t see anything related to the Bullet there in the change log. So no. Not tried it but no plans to.
Version 1.6.1 is the release that included support for the Bullet with IBTS.
Artisan release excerpt: “Adds support for the… the Aillio R1 v2 firmware incl. the new IBTS IR sensor”.
But, I also saw a statement in their “warnings” list for the Aillio that said you must have the Legacy USB Drivers installed for Artisan to work properly. I don’t know how much of a problem that presents or if it is any problem at all. I just mention it since I saw it on their Supported Machines page for the Bullet:
https://artisan-scope.org/machines/aillio/
If you install the legacy drivers, RT2 won’t connect so you pretty much have to decide which path you want to follow or keep swapping drivers in and out like a Windows maniac…
For now I’m sticking with RT on the Bullet.
I agree Stuart and learned the hard-way today by attempting to follow the path of installing Artisan, the required Legacy USB drivers, etc. Bottom-line, Artisan (for me ) didn’t work with the Aillio Legacy USB Driver and would not recognize the Bullet’s data. But worse than that, I had quite the challenge of restoring the newer Aillio Driver to get my Bullet communicating properly again to RoasTime. 
Messing with the Aillio Drivers can lead down a rat-hole that can take a lot of effort to recover from and I was following the documented processes to do it. It is just not worth it IMO and Artisan (while deep with options) is quite complex. Plus, the Aillio software changes so often, that it begs the question “how often will Artisan not be current with the Bullet’s changes”? Moral of my story, “don’t tinker with that stuff”. 
If you become absurdly familiar with Device Manager you can juggle the drivers in and out but it’s almost easier to have two laptops on hand for Artisan and RT. I’m not sure if the Mac experience would be easier but I have other things for my Mac to do.
I do like having my roast history available in the cloud, non-local although I would appreciate option of not having them shareable by default.
If Aillio can get their version of Alarm events running and replaying by temp I probably wouldn’t look back. Having the banding on the graph or an estimate of when events like drying end, FC and SC might take place based on current projections would seal the deal for me. Being able to export the graph as a PDF would be nice instead of screen grabs or copying a URL but I guess that can also be done via the browser. If there’s a suitable place to post enhancement requests officially please point me in the appropriate direction. 
The only “place” I’ve noticed here in Roast World is the “Feature Suggestions” category. Seems that would be the place (if monitored) to make your “enhancement requests”.
Back to the Aillio Bullet Driver replacement problems and I’m quite familiar with Device Manager. I ran into difficulty in cleanly removing (or replacing) the Aillio Driver (especially the new one). I used every trick that I knew along with the Driver’s Property options to delete a driver. But, the Aillio driver would keep re-emerging in a broken state every time I plugged-in the Bullet’s USB cable.
What finally solved that for me was following a recommendation that Jacob made to another user in a related thread titled " How to do a clean uninstall and install Windows 10?". Jacob commented:
“You try to remove these:
C:\Users\YourUserName\AppData\Local\aillio-ts
C:\Users\YourUserName\AppData\Roaming\RoasTime”
Deleting those two sub-folders in AppData finally killed the zombie Aillio Driver and allowed me to do a fresh installation of the driver from RoasTime. Prior to that, running a fresh installation of RoasTime 2.2.0 was not removing/replacing the previous (broken) driver as it is supposed to do. I knew that RoasTime was skipping the driver replacement because the installation was skipping right over the routines that open in a Command Prompt window to install drivers. Once I followed Jacob’s suggestion, RoasTime returned to doing a normal install routine including driver installation.
Looking at the Artisan source code for the Bullet, I see the following type of information:
AILLIO_VID = 0x0483
AILLIO_PID = 0x5741
AILLIO_PID_REV3 = 0xa27e
...
AILLIO_CMD_HEATER_INCR = [0x34, 0x01, 0xaa, 0xaa]
AILLIO_CMD_HEATER_DECR = [0x34, 0x02, 0xaa, 0xaa]
AILLIO_CMD_FAN_INCR = [0x31, 0x01, 0xaa, 0xaa]
AILLIO_CMD_FAN_DECR = [0x31, 0x02, 0xaa, 0xaa]
...
However, I don’t see settings for AILLIO_CMD_DRUM_INCR and AILLIO_CMD_DRUM_DECR.
Does anyone know why those settings are not included and where one might be able to get them from?
You can contact Marko. He’s the main contact for Artisan.
Rui Paulo appears to be the author of the Aillio Bullet R1 drivers for Artisan. But I haven’t come across a way to contact him directly. So, I was hoping someone here had some understanding of components that run the Bullet and thus could point to the relevant component manufacturer’s specs.
Correct that Marko did no work on the Bullet integration. I would open up an issue report on Github…
Never mind. I now see that there is a slider that controls the drum speed. So, I’ve been able to add buttons to raise and lower the drum rotation.
Hi All, I know this thread is old, but could anyone point me in the direction of finding the Legacy USB Drivers, as I would prefer to use artisan.
There are other threads that discuss this on this forum. Alternatively, you can check out this - Artisan 2.0 and Aillio Bullet R1 V2
I’ve done this recently, and I’ve used https://zadig.akeo.ie to put drivers that will make things work with Artisan
Note: This was done on Windows 10, using the latest version of Artisan and a Bullet R1 v2
I can definitely recommend the use of that ZaDig utillty, especially for those that are wanting to use Artisan.
I’ve been on Artisan 2.5 years and still prefer it to the latest version of RT (which I just had to install). if your Bullet fails (as mine just did), the nice folks at Aillio Support will want to see data from RT. That is completely understandable since they don’t use Artisan and RT gives you an easy method to share test data with Aillio.
So, having a way to cleanly switch from the Legacy USB driver (required for Artisan) to the USB Driver that RT requires is essential. That’s where the ZaDig driver utility comes in handy and makes the process easier to accomplish. 