Just been playing around.

I hooked it up to an GLCD and a TSL230r

Could you use the blink without delay example with an interval generated with the random function?


http://arduino.cc/en/Tutorial/BlinkWithoutDelay

http://arduino.cc/en/Reference/RandomSeed

http://arduino.cc/en/Reference/Random

Is there no optical sensor you could use to control it?

Most have a make/break beam sensor to detect when an object is placed in the schreddar path to provide a signal to turn off/on the blade motor?

It may be very useful for situations like where you want to make a network printer box,

If I could get my hands on one . . . . .

What model Rigol scope did you get?

It is mostly U.S.  time zones. When America wakes up it gets a lot more slow.

Just prior to 8:00 central time and Lunch Central time seems to me to be the worst.

In the middle of the night central time it is pretty quick.

I am not sure if it is bandwidth or just too many hits on the database. I know sometimes it just loads with an internal server error so I suspect too many hits on the database at once.

As I posted prior in the thread.

Its not that you have not documented it. The problem is more information overload. With three threads in the microcontroller section of the forum dealing with the 1284 and 644 chips  and following them all with interest while  I was building the boards I just took the most repeated advice.

In my haste to program and play with the boards I assumed they were all alike. I assumed they all shared the same "Mighty" phrase in the name so I picked up on that to assume they were simular and the bootloaders and files were interchangable.

Now that it has been mentioned in the thread the chances are that fewer people will make the same mistake.

Not that was any ones fault but my own. And it was more a case of information overload than lack of information.

You have to select the bobuino as the board type. It seems to still work but  the pins just do not match the silkscreen with the wrong board type,.

I purchased an avrmkii and to get the drivers to play nice was interesting. I am just playing with AVR's more and more so it made sense to invest in the proper tool. Now that it works and I know what drivers and how to switch so I can make it work in both the IDE and the AVR studio. I wish there was an easy way of doing that but thats not your fault.

The frst one took a couple of hours to bootloiad due to the above reasons but the second one was done in a matter of minutes. 

here are the two I have built so far.

These are cell phone pics so they are not of the best quality.

Thanks.

All embedded.

It will have landed for 7 minutes before they even get a signal. Crazy.

They work in a couple of ways mostly.

One type uses a stepper motor and as you can imagine, by counting the steps it knows what area of the page it is printing at.

Another way is to use a regular motor and a pulse wheel.  By counting the pulses generated by the pulse wheel and an optical sensor it knows its position on the page.

Most times there is a home position sensor at the capping assembly and it counts the steps from that position. It checks home position once in a while depending on the model.  More expesive units may have an optical sensor and a patch on the platen for it to find home position and time the ink drops.  The more expensive the device, the more precise the carriage position and ink drop sensors. Really expensive printers even track the curvature of the platen roller and the curl to the paper and adjust the head height to compensate.

Start from the basics and work up

http://learn.adafruit.com/character-lcds/character-vs-graphical-lcds

Code:

int backLight = 7;    // pin 13 will control the backlight

How does that work? that just confusion to the people that try to help.

That works.

I was selecting the mighty board and the board type instead of the bobduino.

Thanks sir.

What did I do wrong?

I have an LED on D13 silkscreened on the board as well as the "L" led on the board its self.
I am using arduino ide 1.01
I am using the mighty 1284 bootloader with optiboot.

Standard blink sketch does not blink the LED. but if I change it to

/*
  Blink
  Turns on an LED on for one second, then off for one second, repeatedly.
 

Code:

  This example code is in the public domain.
 */
 
// Pin 13 has an LED connected on most Arduino boards.
// give it a name:
int led = 7;

// the setup routine runs once when you press reset:
void setup() {               
  // initialize the digital pin as an output.
  pinMode(led, OUTPUT);     
}

// the loop routine runs over and over again forever:
void loop() {
  digitalWrite(led, HIGH);   // turn the LED on (HIGH is the voltage level)
  delay(1000);               // wait for a second
  digitalWrite(led, LOW);    // turn the LED off by making the voltage LOW
  delay(1000);               // wait for a second
}

An LED on pin 13 and the "L" led blink as I would expect d13 to if I digitalWrite 13 but I am using 7 in the above sketch.

Are the pins different on the DIP version verses the SMD version. Is there another bootloader I should use?

Thanks. It works and I did burn a bootloader. That was a learning experience in and of its self.

Solder bridge / solder flake?