@Pollard wrote:Just now circling back on this. I ended up getting a new 32-bit board for my printer that shows up as STMicroelectronics GENERICSTM32F103RC CDC in FS Mode.
I was able to get octoprint working with it just by passing the usb device through and using g host /dev/ttyUSB0 and container /dev/ttyACM0.
** Adding this in here ** Mine quit working recently after an update ran
ls -l /dev/serial/by-id which informed me for whatever reason my host change from /dev/ttyUSB0 to /dev/ttyACM0 so now I haver to put the for the host and container.
Please, forget the recent replies. Wrong way. It doesn't help for the /dev/ttyACM0 issue.
If the symlink /dev/ttyACM0 still is an issue, have a look to the directory content /etc/udev/rules.d/
- there might be a rules configuration file beside the 99-vmware-hotplug.rules file.
Inside such a file, you could find something like KERNEL=="ttyACM", Subsystem, VendorId, ProductID, Symlink, ...
- An usb device attached to the vm should be e.g. /dev/bus/usb/001/003.
To identify the usb device, run e.g. lsusb -D /dev/bus/usb/001/003 . To identify symlink try e.g. ls -l /dev/bus/usb/001 .
- udevadm info /dev/bus/usb/001/003 shows device information from udev database.
udevadm info -q path /dev/bus/usb/001/003 shows the full pci path.
- Files in /etc/modprobe.d/ are used to pass module settings to udev . On ESXi with attached usb devices for a Photon OS vm, see usb.conf entries sequence ohci and uhci .
This is the way.