Forcing Serial device to use the same Serial port

EDIT: Note, that this caused an error that I'm currently trying to work out. I'll remove this once I've figured it out. Basically, it doesn't treat the second device as a serial port.

Note, that I'm currently writing this to use on my Raspberry Pi to make it work better with BotQueue's client software, bumblebee. When you unplug a usb serial device, and plug it back in, the serial port changes.  So, if you have it as /dev/ttyACM0, unplug it and plug it back in, you'll see it's now at /dev/ttyACM1.

Throughout this tutorial, I'm going to use /dev/ttyACM0 since that's the current port of the device I'm trying to get to stay.  Note, that this is a device rename, not a symlink. I'll be using /dev/ttyJasmine for the new port since Jasmine is the name of my printer.

First up, let's find some info about the device:
udevadm info -q property -p $(udevadm info -q path -n /dev/ttyACM0)
It should spit out some info. The line that we need to pay attention to is ID_SERIAL_SHORT.

So in the case of my arduino, (excluding all irrelevant fields):
ID_SERIAL_SHORT=<removed for the blog post>
Now it's time to set up what's called a udev rule.  Run the following command, replacing nano with your editor of choice: (Note, that I chose 45 arbitrarily. Just for fun, you might want to research how the numbering system works)
sudo nano /etc/udev/rules.d/45-serial-devices.rules
Go ahead, and add the following line, replacing the items in < > their appropriate values.  So in my case, I'd replace <SUBSYSTEM> with tty and <ID_SERIAL_SHORT> with the serial device I found earlier. (Note, that this is all one line)
SUBSYSTEMS=="usb", ATTR{serial}=="<ID_SERIAL_SHORT>", NAME="ttyJasmine", GROUP="dialout", MODE="777"
Go ahead and save the file. After a fresh reboot, you should see your device have the name that you assigned to it.  If not, then run the following command to see what the problem might be:
cat /var/log/daemon.log | grep udev
Remember to change your config.json to use the new port if you did this for botqueue.

Comments

Post a Comment

Popular posts from this blog

New paint job and other "minor fixes"

I've always found it interesting how the human brain worked. Recently, I've been playing with  Tailwind CSS  and reading the  Refactoring UI book . One of my longer term projects has been working on BotQueue v2, with all of the fun issues and delays with that. At some point, I realized that I would have to make the site look semi-professional. So I decided to learn how to do some UI stuff which is where that UI book comes in. The same author is also behind Tailwind CSS which is a really nifty utility first CSS framework that I would recommend checking out. What I didn't expect is how doing even a little effort in making the design look good would help my motivation to work on it. I've been focusing on removing blockers recently, and it's fascinating what I find is a blocker. I didn't really expect a little bit of "paint" to go a long way in me working on it. I no longer had the "it's functional, but it's going to suck to make it pretty l
Read more

What it's like working in tech with ADHD

Whoa, it's been almost 3 years since I last update this blog? Geez, what's happened in the interim? Well... A lot. I'm currently coming up on two years as a software developer for Uber, and what a crazy couple of years it's been. I'm not sure why I haven't written in a while. This blog was always designed to describe my adventure, navigating from job to job and what I learned or sharing some perspective that might help others. Today I'm going to share a personal perspective on what it's like working in tech with ADHD (if you couldn't tell from the title). Alright, so first things first, let's define some context. This is as much for you reading this as it is for me writing it. What is ADHD? ADHD stands for Attention Deficit Hyperactivity Disorder. Okay, so that's not very useful is it. I mean there's this ADD thing which is everything minus the hyperactivity. Okay, perfect, that explains it! I have a deficit of attention.... and it
Read more

BotQueue client updates!

It's been only a couple of months since the last software release, but it feels like it has been far too long. Instead of releasing 0.6, I'm releasing 0.5.1 today. There are two reasons for this, which I'll get to in a minute. But first, features! Makerbot support Or at least, mostly Makerbot support. It supports all of the printers that speak s3g/x3g, so no 5th generation (yet). There is also way to slice things. I have a solution for that, it's just somewhat difficult to work with closed source software. For now, you can upload your *3g files and it will run them just fine. It also allows you to upload .makerbot files, but those aren't supported yet. Automatic updates This is something I've wanted to do for a long time, and is the first reason why this only jumped up to 0.5.1. I released version 0.5.0, and in the very next commit, released 0.5.1. This was to test the auto update feature. Every 2 minutes, if your bots are either in idle, error, or offli
Read more