I have had great success getting values read from the unit but have failed to be able to write the set point. Could this be due to the float method of communication?
Also, what would it take to be able to have the same type of controls as the Fuji PXG?
Thanks,
Jeremy
Dear all,
yesterday we uploaded another small bug fix release to GoogleCode.
Besides fixes to small issues that have been reported by users, this release adds the possibility to beep on alarm trigger. It also improves the spike filter as well as the autoCHARGE and autoDROP pattern recognizer. Further, the autosave was change such that if no autosave prefix is specified, but a roast name that is taken as prefix. We hope that this release works as expected for you and is of some help for your roasting.
Happy New Year,
The Artisan Team
Nate,
I guess your device is not directly supported by the FTDI driver on the Mac. A reason might be license restrictions (company payed only for the Windows platform). The FTDI driver checks if your USB2serial device's id is one of the known ones (contained in a list in the driver).
To verify that this is the issue, check if your device is listed in the "System Information" (apple-menu >> About This Mac >> More Info… >> System Report to open the System Profiler; check under Hardware/USB (the device must be connected to be listed!). There should be an entry under "USB 3.0 High-Speed Bus" with an entry like "Model 48SUSBTB-2W" that shows a ProductID and a Vendor ID (e.g. 0xac33 and 0x0856) and a Manufactor (eg. "B&B Electronics).
So if your device is recognized by OS X, but no extra serial device port is generated to be selected within Artisan, the FTDI driver is not "supporting" your productID.
If this is the fact, an approach to add your "product" to the list of the supported ones of the FTDI driver is described here
<http://dfusion.com.au/wiki/tiki-index.php?page=Installing+FTDI+USB+Serial+D…>
Try to follow those steps:
1) Install the latest FTDI VCP driver for Mac OS X (currently v2.2.18) from here
http://www.ftdichip.com/Drivers/VCP.htm
2) Convert the ProductID/VendorID shown by the System Profiler in Hex to decimal idProduct and idVendor.
Open Terminal.app and type (after the # prompt) using the ProductID/VendorID as shown by the System Profiler (without the 0x hex prefix). Eg type for the numbers above:
# dc -e "16i AC33 p 0856 p"
44083
2134
3) Modify the "supported" devices list
Open "/System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/Info.plist" with TextEdit and search for an entry for your device. The following would be the one for the 485USBTB-4W:
<key>485USBTB-4W</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.FTDI.driver.FTDIUSBSerialDriver</string>
<key>IOClass</key>
<string>FTDIUSBSerialDriver</string>
<key>IOProviderClass</key>
<string>IOUSBInterface</string>
<key>bConfigurationValue</key>
<integer>1</integer>
<key>bInterfaceNumber</key>
<integer>0</integer>
<key>idProduct</key>
<integer>44084</integer>
<key>idVendor</key>
<integer>2134</integer>
</dict>
Which is obviously for the 485USBTB-4W device of the same vendor (same vendor id as computed above), however with the product id 44084, not for your product (44083). Now you just have to add a corresponding entry like suggested by that page to get your device being recognized. It should look like this.
<key>485USBTB-2W</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.FTDI.driver.FTDIUSBSerialDriver</string>
<key>IOClass</key>
<string>FTDIUSBSerialDriver</string>
<key>IOProviderClass</key>
<string>IOUSBInterface</string>
<key>bConfigurationValue</key>
<integer>1</integer>
<key>bInterfaceNumber</key>
<integer>0</integer>
<key>idProduct</key>
<integer>44083</integer>
<key>idVendor</key>
<integer>2134</integer>
</dict>
Save the modified Info.plist to your Desktop
4) Modify the FTDI driver
a) Open Terminal.app
b) Change to the Desktop folder where you saved the modified Info.plist of the FTDI driver
# cd Desktop
c) Make a copy of the original configuration file (you will be asked for the admin password)
# sudo cp /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/Info.plist /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/Info.plist.org
d) Install the modified configuration file
# sudo cp Info.plist /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents
# sudo chmod 755 /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/Info.plist
# sudo touch /System/Library/Extensions
e) Reload the driver
Just reboot your Mac
f) Open the Terminal.app again and check if the driver was loaded (connect your device first)
# kextstat | grep FTDI
(this should return something)
g) Check if the serial ports have finally been allocated (with the device connected!)
# ls -las /dev | grep -i usb
(this should list two serial ports one starting with "cu.usbserial-" the other with "tty.usbserial-"
Hope this helps,
Marko
On 14.12.2013, at 18:11, Nate White wrote:
> Hi! I have a new SF6 with Watlow. The Watlow came with a B&B Electronics USB>serial device attached, the appropriate cable, and a CD ROM (which I used to install the drivers). I have Artisan up and running, but I can't figure out how to get them to communicate. I'm not very proficient at this kind of thing; can someone hold my ehand and walk me through configuring Artisan?
>
> Nate
> _______________________________________________
> Artisan-User mailing list
> Artisan-User(a)lists.einfachkaffee.de
> https://lists.mokelbu.de/listinfo/artisan-user
Nate-
I have the exact same setup. Mine was actually the first that they did this with, so Marko did a lot of work to make this happen. Do you have a Mac or Windows?
--
Kyle Iseminger
Flying Baron Roasters :: (720) 384-7811
On Saturday, December 14, 2013 at 10:11 AM, Nate White wrote:
> Hi! I have a new SF6 with Watlow. The Watlow came with a B&B Electronics USB>serial device attached, the appropriate cable, and a CD ROM (which I used to install the drivers). I have Artisan up and running, but I can't figure out how to get them to communicate. I'm not very proficient at this kind of thing; can someone hold my ehand and walk me through configuring Artisan?
>
> Nate
> _______________________________________________
> Artisan-User mailing list
> Artisan-User(a)lists.einfachkaffee.de (mailto:Artisan-User@lists.einfachkaffee.de)
> https://lists.mokelbu.de/listinfo/artisan-user
>
>
Hi! I have a new SF6 with Watlow. The Watlow came with a B&B Electronics
USB>serial device attached, the appropriate cable, and a CD ROM (which I
used to install the drivers). I have Artisan up and running, but I can't
figure out how to get them to communicate. I'm not very proficient at this
kind of thing; can someone hold my ehand and walk me through configuring
Artisan?
Nate
Hi Frei,
On 13.12.2013, at 23:20, Frei Rønningsbakk wrote:
> Hi guys, I'm a pro user of Artisan, using it on my 15kg roaster.
Thanks for using Artisan.
> I have tried to find a way to make a Counter for Development timer, a clock that starts ticking from the moment I hit "First Crack" button. I would really appreciate this function!
First of all, I thought you in Norway can go without FC completely. I added even the option to remove the FCs button for you;)
You need to download v0.7.x that comes with that feature, by default turned off.
Start Artisan, select Config >> Phases and tick "Phases LCDs". Now during recording you will see 3 additional LCDs in the top bar. The first counting time after TP, the second one the time after DRY (once you marked it), and the last one the time after FCs (once you marked it). Before marking DRY or FCs, those two LCDs are predicting the "arrival time" for those events based on the min/max roast phase limits defined in the very same dialog, or, if a background profile is loaded, based on the DRY/FCs event temperatures in that background profile.
> also, I would like to know if someone have been able to read a VFD - Variable Frequency drive, to monitor airflow on my roaster.. Modbus is hard to understand..
I am recording and also controlling my VFD settings via Modbus on my Probat and yes, Modbus is kind of hard to understand as there are several version, implementation and interpretations of that protocol. If you point me to your VFD modbus manual, I could take a look. Essentially, you have to find out the register numbers to set and/or read the speed values and the exact communication parameters.
> Feature request, if I may:
>
> A way to Select a coffee from a prepopulated database, and Select weight, before roast starts - and maybe even a dropdown menu of previous roasts for background roast, when a coffee has been chosen. That would make roast day much more fluent, and easy to compare and evaluate roasts..
Kind of rejected. I started with a profile/greens DB implementation for Artisan and using a prototype thereof, however, that turned into a project that is much larger than Artisan itself. Not sure when I will be finished with this, but I doubt that I will release this for free.
Best,
Marko
PS: Cheers to Tim if you see him around;)
>
> With regards, Frei Roenningsbakk, Norway
> _______________________________________________
> Artisan-User mailing list
> Artisan-User(a)lists.einfachkaffee.de
> https://lists.mokelbu.de/listinfo/artisan-user
Hi guys, I'm a pro user of Artisan, using it on my 15kg roaster. I have
tried to find a way to make a Counter for Development timer, a clock that
starts ticking from the moment I hit "First Crack" button. I would really
appreciate this function!
also, I would like to know if someone have been able to read a VFD -
Variable Frequency drive, to monitor airflow on my roaster.. Modbus is hard
to understand..
Feature request, if I may:
A way to Select a coffee from a prepopulated database, and Select weight,
before roast starts - and maybe even a dropdown menu of previous roasts for
background roast, when a coffee has been chosen. That would make roast day
much more fluent, and easy to compare and evaluate roasts..
With regards, Frei Roenningsbakk, Norway
Artisan v0.7 is now available now from
<http://code.google.com/p/artisan/>
This one comes with
o support for the Phidget 1046/1048 devices
o phases LCDs that eg. show the development time during a roast
o xkcd graph style
o an extended alarm system
o support for the upcoming roast color meter Tonino
Thanks to all users for feedback on previous versions, all beta testers of this version (especially Barrie, Miroslav, Marshall, Frans, Salvas, David, Wa'ill), Ziv for the Hebrew translation and finally to those that already donated to coffee kids.
The Artian team
