ChromiteBlue.com

some very simple jumpers for Eagle3D, I tend to use a lot of them due to single-sided board restrictions.

the include file, to be placed in “[Eagle3D Root]/povray” and added to “[Eagle3D Root]/povray/user.inc”. see this post for details.
user_jumper.inc

and the associated images (to be placed in “[Eagle3D Root]/ulp/img” to aid in identification, optional):

Zip archive of images

and as requested, a rendered image and an example board:

Example Wire Jumper Board(jumper.brd)

additionally, if the correct user functions can not be found (or you would rather not look for them),
the following lines can be manually added to “EAGLE_ROOT/ulp/3dusrpac.dat”:

05:0:0:0:0:0:0:1:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:USER_WIREJUMPER_05MM(:USER_WIREJUMPER_05MM:
07:0:0:0:0:0:0:1:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:USER_WIREJUMPER_07MM(:USER_WIREJUMPER_07MM:
10:0:0:0:0:0:0:1:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:USER_WIREJUMPER_10MM(:USER_WIREJUMPER_10MM:
12:0:0:0:0:0:0:1:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:USER_WIREJUMPER_12MM(:USER_WIREJUMPER_12MM:
15:0:0:0:0:0:0:1:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:USER_WIREJUMPER_15MM(:USER_WIREJUMPER_15MM:

Update:
The above file is incompatible with newer versions of eagle. If you get errors with user_jumper.inc, try the following file:
user_jumper-54.inc
and adding #include “user_jumper-54.inc” rather than #include “user_jumper.inc” to /povray/user.inc

assuming the Eagle3D directory structure looks as follows:

[Eagle3d Root]
    |- doc
    |- examples
    |- povray
    \- ulp
        \- img

the file “[Eagle3d Root]/povray/user.inc” will contain, by default, nothing.
if the following lines are placed within it (note that the shown filenames are only examples):

#ifndef(__user_inc)
#declare __user_inc = true;

//#include "user_includefile01.inc"
//#include "user_includefile02.inc"

#end

adding new parts is a simple matter of adding the new file to the [Eagle3d Root]/povray/ directory, copying an #include directive, changing the name, and uncommenting it.

in my own installation, I follow the recomended prefix style of filenaming, as do the files available on this site.

additionally, if the current user.inc file is not empty, it can be renamed to “user_orig.inc” or similar, a new user.inc file containing the above added, and the line #include “user_orig.inc” placed within it.

by using the upper four bits as outputs and the lower four bits as inputs, a simple 4×4, 16 button keypad can be connected to a microcontroller.

the first picture shows the state after the “0″ key has been pressed.
the 0×24 corresponds to the “scancode”, the first digit being the column and the second being the row.
to be exact, in binary 0×24 equals 0b00101000, this shows that during the scan, the key in the second column and the fourth row was pressed.

the bracketed values under that are the contents of the key buffer.

 
 
a simple code example for this:

//high bits are columns, low bits are rows
volatile uint8_t scancode = 0x00;
uint8_t i, j;

// set data direction on PORTD
//   pins 8,7,6,5 as output, pins 4,3,2,1 as input
outb(DDRD,  0b11110000);

//loop over pins
for( i=4; i<8; i++ ) {

	// sets outputs low one pin at a time
	//   also enables internal pull-ups on inputs
	outb( PORTD, ~(1<<i) );

	//debounce delay and settling time
	timerPause(5);

	//loop over port positions
	for( j=0; j<4; j++ ) {
		if( bit_is_clear(PIND,j) ) {
			//set scancode
			scancode = (1<<i)|(1<<j);
		}
	}

}

 
 
the “~(1<<n)” is an example of bitshifting, in this case it means “bitshift 1 left “n” times, then invert the result” or if we take n as 3, it would be:
~(1<<3)
after 0 shifts:
~(0b00000001)
after 1 shift:
~(0b00000010)
after 2 shifts:
~(0b00000100)
after 3 shifts:
~(0b00001000)
then inverted:
0b11110111

a slightly more complicated looking example of this is used in the inner loop:
(1<<n)|(1<<m)
or if we take n as 6 and m as 2 it would be:
(0b01000000)|(0b00000100)
and that would resolve to:
0b01000100

this is a rendering of an Eagle3D component in progress, an LCD module that is part of a set of several text-based modules.

as requested, the required files:
HD44780 Based LCD Modules Library (lcdmodules.lbr)
user.inc
user_colors.inc
user_lcd.inc
alphalcd.ttf

the lib file should go in your eagle “lbr” directory, and the inc and ttf files should go in your eagle3D “povray” directory.

a word of warning, thes are in pretty rough shape, but usable.
the include files follow the proposed rules in this post, so if you have made any changes to your user.inc, be sure to merge the files.

alternately, you can simply add the following lines to your user.inc:

#include "user_colors.inc"
#include "user_lcd.inc"

happy designing, and any comments or suggestions are welcome.