Showing posts from February, 2013

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

Run Bumblebee on Raspberry Pi boot

In my last post , I showed you how to set up a raspberry pi with BotQueue. This time, I want to show you how to start it on boot. First, let's create an executable script to run bumblebee with a single command. I'm doing this so that if I ever change the directory BotQueue is in, I only have to change one file. So to edit the new executable, run the following command (replacing nano with your text editor of choice. I use vim personally): sudo nano /usr/bin/bumblebee You should be presented with a blank file. Add the following lines to it, before saving and exiting (replacing /home/pi/BotQueue/bumblebee/ with wherever you put bumblebee. Note that you should not use ~, but instead /home/pi/): cd /home/pi/BotQueue/bumblebee/ python After that's saved, you need to allow people to execute it. Type this to get the desired effect: sudo chmod a+x /usr/bin/bumblebee  Of course, you should run "bumblebee" now to see if it worked. Next up, we need to