Dear Artisan user group;
I have received an error I have not seen before using a Mac with the latest solfware : Sierra with a 64 bit system.
We have installed the CP210 driver with our data logger using Omron controls.
Here is a screen shot:
Modbus Error: Read float() hex() argument can't be converted to hex@line 30521
Could it be we have the wrong driver installed?
We use to use the FT232 driver but data driver was upgraded to a new model that has worked with the CP210 driver on most models (this data logger is setup for future use with Bluetooth capabilities)
I'm relatively new to artisan. Been using RoastLogger for years but now that
I have my phidget 1048 I don't need the camera/ocr feature anymore.
I haven't been able to locate the help file or information about the
settings under Config-Device - Phidgets tab. For instance, Async check
boxes, raw data, change etc. I've found everything on the github page, but
maybe I just haven't been successful in pinpointing the proper area to look.
Secondly- I'm roasting on a Diedrich IR-24, which has a thicker J
thermocouple than the one I've hooked up to artisan, which is a K type 1/8in
I purchased here:
The temperatures are around 30 degrees F higher on the thinner K
thermocouple than what the roaster is reporting, even though my
thermocouples in the roaster are mounted next to each other (didn't want to
piggyback on BT of the roaster to phidgets)
Does anyone have any experience in this area? Perhaps the simple fact that
the probe is thinner means the readings will be different, but I do not
know. It would appear that the readings on the roaster are accurate while
the other is much hotter.
Just getting started, and appreciate any guidance.
I have Probat Probatone 5kg roaster and I added ET temp probe with phidget VINT hub + TMP1101 thermocouple adapter. Previously I have configured the roaster with the config->machine->probat->probatone and the BT and dBT displayed fine.
this blog post was very helpful:
I have succeeded to display the ET and BT curves and the LCDs display the correct values for ET, BT, dET and dBT but for some reason artisan doesn't draw live RoR curves during roasting for dBT or dET. It does show them after logging in the summary. I have checked the dET checkboxes from the Config -> Curves dialog.
I did roast before adding the phidgets and had the dBT RoR curve displaying live during roasting without problems.
photos of the settings and also the settings file:
I have tried this both mac and windows and same problem. any ideas what I might be missing?
it has been a while, and I am truly sorry for the lengthy service
interruption. If this mail reaches you — and I do hope it does —
everything is back to normal.
A few notes, though:
- Even though all members with their subscriptions have been kept, your
*optional* account information has been lost. If you wish to use the
web-interface to manage your subscription options, please go to:
Where you can create a new account with the same address of your
existing subscription — you can then conveniently manage it again.
- The archive URL has changed slightly, and is now found on:
But the interface is newer and shinier ^_^.
- A few (~8) messages from the archives have been lost while converting
the archives to a newer format. I do hope they haven’t been important
ones. If you suspect so, please inform me, and I’ll try to dig them up
- The list self-management URL is now:
I’ll also ping marco again so he can update the website.
So with this … happy chatting, always roast something nice ^_^.
Hi Marco, et. al,
This is a long email, I know, but I gots some questions…
I'm hooking up a few Phidget devices that aren't directly supported in
Artisan, but as I understand it, Artisan reads the raw signal, so with
the correct symbolic formula, I should be able to do that… I've read, I
think, all of the blog posts and Home-Barista threads that deal with
setting up custom Phidgets monitoring (re: differential gas (1136),
symbolic formulas for the plotter, and Phidgets and how to use them),
but still feel that I wasn't understanding artisan well enough to
manipulate it to do what I wanted… though it seemed it should
By now, I've think that I've gotten most of this working (or at least
enough of an understanding to get it working), but as I have sort of
worked backwards through trial and error, I want to make sure I actually
am understanding how Artisan handles extra devices - and get correct
info where I've figured wrong.
Some of this stuff may apply to other manufacturers, but I only have
omega and Phidgets hooked to Artisan, so I dunno…
And so you are aware of my set up:
MAC OX 10.14.1
Artisan 1.5 & 1.6 (beta) Both appear to be stable
mac laptop - USB-c (3.1) to USB 2 (mini) to…
- 0 - TMP1101 4x with 2 probes (currently, but intentions to add 2 more)
- 0 - BT
- 1 - ET
- 2 - TC #3
- 1 - HUM1000 - Ambient Humidity & Temp
- 2 - Differential gas pressure 1137 (±7kPa) - gas pressure
- 3 - Rotary Potentiometer 3583_0 (Damper 2 position)
- 4 - Linear Potentiometer 3579 (Damper control position)
Extra Device current set up
However, in order to debug, I have been only hooking up 1-2 items…
mostly the Linear Potentiometer since that was, of the devices that
weren't directly supported, the easiest to hook up & test.
A couple things that I think I know, generally, & hoping for confirmation:
Raw signal means voltage in MV… so since most of the Phidgets read from
0-5V, the readings will be between 0-5000
Artisan has limited signal readings to 1000… so if you just plug in a
device and it's sending a signal over 20%, then it will read -1
Side note: I intend to log this as a bug unless I have this wrong…
unchecking limits in the filter dialog doesn't seem to allow signal
values greater than 1000, either?
In Extra Devices, when selecting a device with multiple ports, such as
the Phidgets HUB0000 IO 01, in sequence, the ports map to the channels 1
& 2 for each Extra Device:
in this example:
port 0 maps to 'Label 1' & '(y1(x))'
port 1 maps to 'Label 2' & '(y2(x))'
When hooking up the 4xTC, and port 0 & 1 map to ET & BT, so then do
ports 2 & 3 mapping to Label 1 & Label 2 in the ED line it's assigned to?
How does this work if BT & ET are acquired through a separate device?
This (mapping) follows for all I/O devices with multiple ports
this would mean, that you can't have two extra devices that are the same
device selection (e.g. 'Phidget HUB0000 IO 23' in extra device 2 & 3
such as shown below). It would only read the first?
or, how does Artisan decide which actual device it is assigning to each
Kind of a follow up to the previous question… what is the criteria for
(Artisan) selecting the correct device from the ED list (popup)≥ it
looks like it assumes the closest to the sensor? so if you select 4xTC
for your thermocouples (with artisan assuming that the first two (ports
0 & 1?) are the BT & ET).
It also seems to be that the devices are calculated/operated in a
cascade… such that in the screen shot above, one or the other (ED 2 or
3) would be cancelled out (?). Not that you would have 2 VINT Hubs, but
how does Artisan handle it if there are 2 4x Thermocouple 4xTC attached?
Granted it's probably an edge case scenario, but I can imaging wanting
more than 4 TC to help determine probe placement…
But… not so edge case, I can imagine adding more than 1 basic 8x voltage
Inputs… granted, there is probably an upper usable limit to what can be
powered over USB…
This might be a dumb question, but what's the difference between using
the Plotter and the assigning a ED to graph on the curve? Particularly
using a virtual device?
Some specific questions:
Can the HUM1000 be brought in here so that it records into the graph. I
assume I can add individual humidity & ambient temp sensors, but…
What is the 'TMP1101 4xTC AT' in the Extra Device list? Is that
Atmospheric Temperature? …and if so, which channel reads which reading
Why would it take roughly 17-20 seconds for Artisan to start showing
readings for an Extra Device?
I'm gonna end this here, cause it's a lot of questions… thanks in
advance for the help
Deft Coffee Roasters | 503.702.1932 | exquisite coffees
Happy New Year, Marko. Back in November you commented that "Delta curves
are only rendered after CHARGE during recording" on home-barista.com. What
was the thought behind this change? I liked to start recording 100 degrees
or so before charge to see the delta curves in the empty roaster as it
heated up. That established a baseline for the noise in my temperature
readings since there is no bean mass variability to deal with. It gave me a
nice idea of how much my readings were bouncing around with my selected