Artisan Modbus Communication Error - Page 2

Discuss roast levels and profiles for espresso, equipment for roasting coffee.
User avatar
CarefreeBuzzBuzz

#11: Post by CarefreeBuzzBuzz »

Well then why are two people having issues after upgrading to Monterey?

And shame on FTDI for not being more clear on their driver page?
Artisan.Plus User-
Artisan Quick Start Guide
http://bit.ly/ArtisanQuickStart

User avatar
MaKoMo

#12: Post by MaKoMo replying to CarefreeBuzzBuzz »

I have no idea. Maybe they installed an FTDI driver before which shadows the system driver and is now incompatible with the updated system, they are not using an FTDI hardware and another driver is incompatible, or it is a permission issue enforced by the new system version. I do not have any FTDI issue on my Monterey system.

User avatar
CarefreeBuzzBuzz

#13: Post by CarefreeBuzzBuzz »

Issue is solved. Is working with the FTDI driver after a Factory Reset. Going to compare the Modbus settings in his old file.
Artisan.Plus User-
Artisan Quick Start Guide
http://bit.ly/ArtisanQuickStart

srosemer

#14: Post by srosemer »

Hi CarefreeBuzz,

I have a USB interface on the back of my roaster (2022 BC 3.5), it's in addition to the wireless dongle and bluetooth connections. The driver I installed was from November 11, 2021, version 1.6 for OS X 11.1 and above.

User avatar
CarefreeBuzzBuzz

#15: Post by CarefreeBuzzBuzz replying to srosemer »


You are going to have to be more specific. Since its a BC that suggests the CP210x.

I don't see a date that you listed here that matches the ones listed -by Silcon labs

You can PM me your contact info and I can see if I can help.
Artisan.Plus User-
Artisan Quick Start Guide
http://bit.ly/ArtisanQuickStart

srosemer

#16: Post by srosemer »

For those who may encounter this problem - check for driver updates, but that may not be necessary if your bluetooth module is in an indeterminate state. Rebooting and powering down and back up often does not resolve this type of issue.

The simplest way to reset the bluetooth module to get it into a known state is by killing the bluetooth daemon. Open a terminal window (you can find the terminal in the Utilities folder of Applications), then type in:

sudo pkill bluetoothd

You will prompted for your password (assuming that you have superuser privileges). Then reboot and reconnect to your MODBUS interface via bluetooth.