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)
On the device page https://artisan-scope.org/devices/meters/
I read that the optically isolated Victor 86B is compatible with Scope,
while others say Scope do not work with USB HID devices, such as the Victor
My Victor 86B shows up in the device manager under USB HID devices in win 7.
In Artisan 2.0.0 Scope config devices is set to Meter/Victor 86B after
which a port config window appears to select a com port.
I have installed the CP210X driver, and would expect a virtual comport to
show up, when the Victor 86B is connected, but that does not seem to happen.
Any suggestions to cure the problem, please let me know.
Alternatively, for two K-type sensors, which optically isolated solution is
the choice for Artisan Scope 2.0.0, please.
Thanks in advance,
I'm planning to control my roaster's burner bythe Artisan's internal PID. I've read the instructions, and it is not clear to me whether a Yocto Tx device (4-20/0-10) can be controlled automatically by the PID?
I recently installed v 2.4.0 and need help setting it up. I followed the
only guide I could find which is archived on the huky forum. Even though
it was written for an earlier version and specific to a different device
(phidget) than the one I'm using (Center 301) I followed as closely as
possible. I started a roast but Artisan didn't show the temps. The
error line says: Serial exception: Unable to open serial port.
Can someone help with this? Is there an up-to-date guide for this version
of artisan? Ideally, I'd love to see a video that steps through the
configuration and expected outcome?
thanks in advance for your help!
Yes, that was it. I’ve always has the DELETE on reset ticked as it was convenient for my process. Knowing the new behavior, I’ll just update my process/steps. Not a problem. Just wanted to check to make sure this was an intentional change. I’m always using the latest Continuous Build so… just want to let folks know what I was seeing.
Thanks for the quick reply!!