Roaster Not Connected - Linux

Hello RoastWorld - I’m a long-time HotTop roaster, but moved on to the Bullet a week ago, wanting to step up to a model with computer profiling and a bit larger capacity. I’ve done my seasoning roasts plus one, and have been delighted by the range of adjustment available…it will take some getting used to. I’ve also been delighted by the general atmosphere of mutual respect apparent on this forum.

Being a Linux user, I thought that finding a version of software that will work would be the most difficult issue, but my problem seems to be hardware related. I’ve read all the tangentially related items here, but haven’t found an issue exactly like mine.

When I connect the Bullet to a computer by USB, the lsusb command in a terminal appears not to see the Bullet. I’ve tried 5 different cables (for 2 or 3 of them, the micro USB side didn’t seem to seat very deeply). I’ve tried 2 different computers (1 running Mint, the other a simpler/older Ubuntu). I’ve tried all 5 cables on both computers. On both computers, I’ve tried all of the USB ports (2 each) available. Always the lsusb command finds nothing.

Running aillio-ts-2.0.3-x86_64.AppImage (I was hoping it might force the locating of the roaster), I was delighted to find that the software appears to operate (I won’t go into the different things I tried before that particular AppImage), but it shows “Roaster Not Connected” as the status. Is there a way, somehow, tell the Bullet to open up USB communication? Or, might be an actual hardware problem (after all, 2 or 3 of the 5 cables tried feel pretty shaky on the micro USB end of the connection)?

Apologies for a possibly stupid newb question. Thank you.

If you try searching for linux using the magnifying glass icon in the upper right of the screen you’ll find a few threads that mention details about usb connections. Sorry I’m not more of a linux hack to help further.
FWIW, it takes a bit of careful attention to connect the provided cable to the micro usb connector on my bullet too, one of the new V2 batch from SM in March.
Cheers, - Brad

Please search this forum about how to set it up, and maybe try this release instead: 2.5.6

Brad & Jacob,

Thank you for the encouragement to re-read the linux related posts. One of them pointed out that the “STMicroelectronics” in the list resulting from lsusb is the, not entirely expected, designation for the Bullet. So, hooray, I have a connection.

Now I’ll just need to do the udev rules exercise to get running (fingers crossed). Jacob, thanks for the link to 2.5.6. It looks promising.

Kerry

1 Like

Hmmm, thanks to Matthew and tacvbo (and a little review of syntax), I’ve gotten my computers to recognize the Bullet. Still get the “Roaster Not Connected” message from RoasTime.

I will keep fumbling on. dmesg result is:

[11819.695209] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready

[11819.696431] IPv6: ADDRCONF(NETDEV_UP): enp1s0f0: link is not ready

[11820.726907] IPv6: ADDRCONF(NETDEV_UP): enp1s0f0: link is not ready

[15063.784811] usb 3-2: new full-speed USB device number 4 using xhci_hcd

[15063.914800] usb 3-2: New USB device found, idVendor=0483, idProduct=a27e

[15063.914808] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[15063.914813] usb 3-2: Product: Aillio LTD- Bullet R1 ROASTER FS

[15063.914817] usb 3-2: Manufacturer: STMicroelectronics

[15063.914821] usb 3-2: SerialNumber: 000000000200

[15064.177861] cdc_acm 3-2:1.0: ttyACM0: USB ACM device

[15064.178133] usbcore: registered new interface driver cdc_acm

[15064.178136] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

[15156.639726] usb 3-2: USB disconnect, device number 4

[15158.453567] usb 3-1: new full-speed USB device number 5 using xhci_hcd

[15158.583463] usb 3-1: New USB device found, idVendor=0483, idProduct=a27e

[15158.583474] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[15158.583483] usb 3-1: Product: Aillio LTD- Bullet R1 ROASTER FS

[15158.583491] usb 3-1: Manufacturer: STMicroelectronics

[15158.583496] usb 3-1: SerialNumber: 000000000200

[15158.584355] cdc_acm 3-1:1.0: ttyACM0: USB ACM device

[15186.934542] usb 3-1: USB disconnect, device number 5

[15202.257916] usb 3-1: new full-speed USB device number 6 using xhci_hcd

[15202.387723] usb 3-1: New USB device found, idVendor=0483, idProduct=a27e

[15202.387731] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[15202.387736] usb 3-1: Product: Aillio LTD- Bullet R1 ROASTER FS

[15202.387739] usb 3-1: Manufacturer: STMicroelectronics

[15202.387743] usb 3-1: SerialNumber: 000000000200

[15202.388569] cdc_acm 3-1:1.0: ttyACM0: USB ACM device

[15222.317831] usb 3-1: USB disconnect, device number 6

[15223.766099] usb 3-2: new full-speed USB device number 7 using xhci_hcd

[15223.895795] usb 3-2: New USB device found, idVendor=0483, idProduct=a27e

[15223.895802] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[15223.895807] usb 3-2: Product: Aillio LTD- Bullet R1 ROASTER FS

[15223.895810] usb 3-2: Manufacturer: STMicroelectronics

[15223.895814] usb 3-2: SerialNumber: 000000000200

[15223.896496] cdc_acm 3-2:1.0: ttyACM0: USB ACM device

[15253.528777] usb 3-2: USB disconnect, device number 7

[15754.246292] usb 3-2: new full-speed USB device number 8 using xhci_hcd

[15754.376099] usb 3-2: New USB device found, idVendor=0483, idProduct=a27e

[15754.376108] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[15754.376112] usb 3-2: Product: Aillio LTD- Bullet R1 ROASTER FS

[15754.376116] usb 3-2: Manufacturer: STMicroelectronics

[15754.376119] usb 3-2: SerialNumber: 000000000200

[15754.376997] cdc_acm 3-2:1.0: ttyACM0: USB ACM device

Swapped out USB cable, and managed to get rid of the USB disconnect issue. Still no conversation with RoasTime…still ‘Roaster Not Connected.’

No connection between roaster and Artisan either. Message on Artisan is something like ‘AillioR1’ object has no attribute ‘parent pipe’.

New dmesg output:

[ 81.470832] usb 3-1: new full-speed USB device number 2 using xhci_hcd
[ 81.600879] usb 3-1: New USB device found, idVendor=0483, idProduct=a27e
[ 81.600883] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 81.600885] usb 3-1: Product: Aillio LTD- Bullet R1 ROASTER FS
[ 81.600887] usb 3-1: Manufacturer: STMicroelectronics
[ 81.600888] usb 3-1: SerialNumber: 000000000200
[ 81.683427] cdc_acm 3-1:1.0: ttyACM0: USB ACM device
[ 81.683661] usbcore: registered new interface driver cdc_acm
[ 81.683664] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

The SerialNumber appears to be unlikely, but probably not important. Everything else looks reasonable to my untutored eye. Running out of ideas.

Hah - Success…sort of. The driver Linux uses for the Bullet is the cdc_acm driver, written by CCS. On the CCS website, there is a hint that to receive data from the USB device, one must execute (in a terminal) cat /dev/ttyACM0 (the ACMzero, is my specific situation, of course, others will vary). With that process running in a terminal, the Bullet connects with RoasTime.

The big downside to this news is that I will need to run RoasTime as Administrator, which I really don’t want to do. My lesser user(s) can’t run sudo with the right PW. Oh well, maybe there’s a stroke of inspiration in my future.

Glad you got it figured out!
I will ask Matthew about why it needs to run as admin.

Ok, with the help of your post here, I was able to get mine working (without administrator). This is on Ubuntu 20.04, your mileage may vary on other distros.

Step 1, add the following udev rules - edit the file /etc/udev/rules.d/99-aillio.rules and make the contents look like this:

SUBSYSTEM=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="5741", MODE:="0666", GROUP="dialout"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="a27e", MODE:="0666", GROUP="dialout

Step 2: Reload your udev rules:

$ sudo udevadm control --reload-rules

Step 3: Add yourself to the dialout group.

$ sudo usermod -a -G dialout yourusername

Step 4: Log out, and back in.

Step 5: Unplug the usb for the roaster (if it was plugged in) and plug it back into your computer.

Step 6: Start the RoasTime application.

That’s it, you should be good. As far as I can tell, no cat is required. When you first connect the roaster, /dev/ttyACM0 is available with dialout permissions, but when you connect the app, it goes away (not really sure how this works) and something like /dev/bus/usb/001/005 is used instead.

If you are having trouble getting it to work without administrator, launch the app as administrator and let it connect to the roaster. Do something like this in a terminal:

$ sudo lsof | grep -i aillio | grep usb

It should show the usb device it’s using. Then you can type:

$ ls -lh /dev/bus/usb/001/005

It should return something like this:

crw-rw-r-- 1 root dialout 189, 0 Jun 16 15:38 /dev/bus/usb/001/005

If it’s not in the dialout group, something is wrong with your udev rules.

Thanks for this!

Thanks – worked like a charm with Elementary OS (Linux)

Hi everyone. I am still unable to connect the roaster, after trying the various suggestions in this thread. I am hoping these excerpts might assist someone in the community.

uname -a output:

Linux robert-ThinkPad-X131e 4.15.0-144-generic #148-Ubuntu SMP Sat May 8 02:33:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

dmesg:

[106572.236721] usb 3-1: new full-speed USB device number 6 using xhci_hcd
[106572.386438] usb 3-1: New USB device found, idVendor=0483, idProduct=a27e
[106572.386446] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[106572.386449] usb 3-1: Product: Aillio LTD- Bullet R1 ROASTER FS
[106572.386453] usb 3-1: Manufacturer: STMicroelectronics
[106572.386456] usb 3-1: SerialNumber: 000000000200
[106572.387146] cdc_acm 3-1:1.0: ttyACM0: USB ACM device

syslog warning:

Couldn’t create modem for device ‘/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1’: Failed to find primary AT port

Oh and the version of roastime:
Roastime v3.1.8
Cheers,
Robert

Hi Robert, I am using Kubuntu. It looks like you are using straight Ubuntu which should be fine. Clearly your problem is not the USB cable since the OS sees the Bullet. I had this problem with two different laptops and two different Linux distros. Both times, Arolsen’s instructions above solved the problem. If I were you, I would check the steps again. Sorry this is not more definitive. JP

Hi Patrick9724,
Thanks so much for your reply. My laptop is actually running mint 19.1 (but yes, based on Ubuntu). I rechecked my adherence to the instructions - with no joy.
I also came across this usb modem - Connecting a pyboard via USB gives "Could not grab port (tty/ttyACM0)" - Ask Ubuntu
I have disabled the ModemManager.Service and tried again.

Here is the relevant lsusb output:
Bus 001 Device 005: ID 0483:a27e STMicroelectronics
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0483 STMicroelectronics
idProduct 0xa27e
bcdDevice 2.00
iManufacturer 1 STMicroelectronics
iProduct 2 Aillio LTD- Bullet R1 ROASTER FS
iSerial 3 000000000200
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 67
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 2 Abstract (modem)
bInterfaceProtocol 1 AT-commands (v.25ter)
iInterface 0
CDC Header:
bcdCDC 1.10
CDC Call Management:
bmCapabilities 0x00
bDataInterface 1
CDC ACM:
bmCapabilities 0x02
line coding and serial state
CDC Union:
bMasterInterface 0
bSlaveInterface 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 16
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0001
Self Powered


And dmseg:

[ 2.839765] usb 1-1.2: new full-speed USB device number 3 using ehci-pci
[ 2.952568] usb 1-1.2: New USB device found, idVendor=0483, idProduct=a27e
[ 2.952570] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.952572] usb 1-1.2: Product: Aillio LTD- Bullet R1 ROASTER FS
[ 2.952574] usb 1-1.2: Manufacturer: STMicroelectronics
[ 2.952575] usb 1-1.2: SerialNumber: 000000000200
[ 6.306212] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
[ 174.558578] usb 1-1.2: USB disconnect, device number 3
[ 181.049481] usb 1-1.2: new full-speed USB device number 4 using ehci-pci
[ 181.160939] usb 1-1.2: New USB device found, idVendor=0483, idProduct=a27e
[ 181.160946] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 181.160949] usb 1-1.2: Product: Aillio LTD- Bullet R1 ROASTER FS
[ 181.160953] usb 1-1.2: Manufacturer: STMicroelectronics
[ 181.160956] usb 1-1.2: SerialNumber: 000000000200
[ 181.164722] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
[ 272.255212] usb 1-1.2: USB disconnect, device number 4
[ 276.517971] usb 1-1.2: new full-speed USB device number 5 using ehci-pci
[ 276.628415] usb 1-1.2: New USB device found, idVendor=0483, idProduct=a27e
[ 276.628423] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 276.628427] usb 1-1.2: Product: Aillio LTD- Bullet R1 ROASTER FS
[ 276.628430] usb 1-1.2: Manufacturer: STMicroelectronics
[ 276.628433] usb 1-1.2: SerialNumber: 000000000200
[ 276.629030] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device


Am I getting any closer?

In ignorance,
Robert

Sorry to be so late in replying, Robert. Have you tried to change Linux distro?

Worked a treat for me on KDE Neon (Ubuntu based). I had to reboot for changes to make effect.