BUG Community

Welcome! Log In

Forums Recent Posts

Subscribe to Recent Posts 12,499 posts found

Apr 13, 2010 5:39pm
Medium wwward 8 posts

Topic: Applications / Is BUG right for me?

We got more info.  First, there is an xBee implementation with an insane amount of range – 1 watt in the 900MHz ISM band.  40 miles line of sight.  Not sure what the effective range is inside a building, but probably nontrivial.

Second, Willis and I are looking at a few interesting things along the lines of the control bus effort we discussed earlier.  It’s a side project for us, so we’re not working on it full-time, but it’s interesting work.


Apr 9, 2010 12:57pm
Medium wwward 8 posts

Topic: Java / Seeking advice: Time-sensitive operations when writing Bug App in JVM

Backstory:  I am looking to implement an existing serial protocol decoder using the VonHippel and the Bug.  Ideally, we could accomplish this with a minimum of additional hardware, so bit-banging the pins on the VonHippel (with appropriate passive components hanging from that) would be more desirable than attaching an external microcontroller.  This also opens up the possibility for advanced software signal processing to identify issues with the serial line, perhaps using the ADC to sample the signal and provide user feedback on observed behavior if there is a fault.  An external dedicated MCU would be more difficult to code that sort of exception logic into.

Question:  When tinkering with the VonHippel module using a “blink the LED” sample app, I noticed the timing on the blinking cycles was a little variable, probably due to other processes delaying the execution of the JVM threads.  I’m aware that we’re not dealing with a real-time implementation in the JVM, but I am curious what techniques I could employ to get things to occur “fast enough” to do the work.  The serial line has a peak speed of 79 kbit/sec.  At that speed, you have about 13 microseconds per bit.  Clearly you’ll want to have windows of time long enough to encapsulate a full packet read, which is around 4,000 microseconds long according to the spec.

I have not yet looked to determine if this is feasible with the module hardware or not, but my question isn’t so much about the hardware as the programming practice – how do you write time-sensitive routines within the existing Bug JVM implementation, and if that is not feasible, how do you write them within the existing Bug software stack (native binaries,) and is there a means to offload these operations to another aspect of the Bug where execution time is more reliable?

Thanks for the advice, and the time.




Apr 9, 2010 10:43am
User_img_not_found_03_med michele.bavaro 1 post

Topic: BUGmodules / Bespoke BUG modules


I’m thinking of designing my own mixed signal PCB board with a GPS and Glonass front-end for navigation applications and I have a couple of questions for the BUG labs people.

a) Is the empty BUGlocation case (or any other case, even double sized) for sale, or reproducible with a resonable budget using the mechanical files?

b) What is the communication bandwidth sustainable with the USB2.0 bus? Is at least it more than 10Mbit/sec?

c) Will the interface between BUG base and BUG modules change when the BUGbase2.0 is out?


Thanks a lot in advance,



Apr 9, 2010 10:24am
Medium jconnolly 285 posts

Topic: Applications / Senior Design Project

Super cool, thanks for posting!

Apr 2, 2010 11:40am
User_img_not_found_02_med LLTDL7 2 posts

Topic: Applications / Senior Design Project

Sorry about that… I hope that this works better

ONU SeniorDesign Bug

Apr 2, 2010 10:08am
Medium jconnolly 285 posts

Topic: Applications / Senior Design Project

I’d love to have a look but it looks like our forums software b0rked your link.  Can you paste it again as a link via the little link tool in the post window?

Apr 1, 2010 3:14pm
User_img_not_found_02_med LLTDL7 2 posts

Topic: Applications / Senior Design Project

Last year, my senior design group used the Bug for our project.  We created a camera for geotagging photos as well as tagging them with the compass direction that the picture was taken.  We presented the paper we wrote about it at the ASEE North conference in 2009.  You can see our website about it here:


Any comments would be appreciated.


Apr 1, 2010 2:06pm
Medium GNUtoo 10 posts

Topic: BUGmodules / VonHippel and Keyboard

I had hardware issues like you describe too,

But it could also be something else like:

Dust,preventing the Bug module to connect properly

Bad connection,that is to say the screen is not connected/inserted properly in the bug-base


Apr 1, 2010 12:33am
User_img_not_found_06_med tapratt 7 posts

Topic: BUGmodules / VonHippel and Keyboard

Hi Denis,

Thanks for the help.  I made those changes to my Xserver config and got the keyboard to work on slot 0 a few times.  I’m still having the same problem where I start up my bug and the bug view module doesn’t display anything but the backlight is on, sometimes I can get it to work by removing the module and plugging it back into the slot.  Other times it will display, but I can’t do anything because the touch screen won’t respond.  I checked the conierge log and syslog, but I’m not getting any error messages or anything out of the ordinary.  Kind of sounds like a hardware issue to me, but I had just returned my last bug for the same problem.  What do you think?


Thanks again for the help


Mar 31, 2010 3:16pm
Medium GNUtoo 10 posts

Topic: BUGmodules / VonHippel and Keyboard

hi here’s my config:


. /etc/formfactor/config

# note xinit needs full server path
if [ -f /usr/bin/Xfbdev ]; then
if [ -f /usr/bin/Xepson ]; then
if [ -f /usr/bin/Xorg ]; then
if [ -f /usr/bin/Xomap ]; then

. /etc/profile

export USER=root

ARGS=” -br -pn -hide-cursor -s 0”
ARGS=”$ARGS -mouse tslib”
#ARGS=”$ARGS vt01”

# use ucb 1×00 touchscreen if present
if [ -z ”$TSLIB_TSDEVICE” ] && [ -e /dev/touchscreen/ucb1×00 ]; then
  ARGS=”$ARGS -mouse /dev/touchscreen/ucb1×00”

# use usb mouse if present
# Xorg doesn’t support ”-mouse” option, and uses /dev/input/mice automatically
if [ -z ”$TSLIB_TSDEVICE” ] && [ -e /dev/input/mice ] && [ ”$XSERVER” != “Xorg” ]; then
  ARGS=”$ARGS -mouse /dev/input/mice”