The code didn't work on my board. im having the same problem.

That's not enough information for us to help you.

What code? My sample of using A6/A7 on a Uno? Retrolefty's editing of boards.txt? Uploading OptiBoot to a preassembled Nano? Uploading a bootloader to a homemade Nano clone?

What problem? stk500 errors? The PC recognizing the Arduino? Baud rates? Board types?

Does it have to be a L317? How about something like a TLC5916?

I think Pantonvich's recommendations are a more likely solution than an Arduino-based one.

To capture arbitrary MAC addresses you'd need to be able to put the Ethernet card into promiscuous mode and parse the raw packers in your application yourself.

I'm not aware of any WiFi adapters for the Arduino that can do that. The RN-XV definitely can't; it goes so far out of its way to shield you from the lower protocols that you can't even use it to receive arbitrary UDP or multicast packets.

Defining the board as Uno does the trick and lets me upload the sketch.
What I don't understand is that I BURNED the SAME bootloader to both Nanos (mine and the standard). And to the standard, there was no problem and it acted "normally" where mine does not.

Glad you got it working. I'm not sure why there would be a difference if you burned the same bootloader on both boards...unless maybe the burn of the real Nano didn't work so it still has the original Duemilanove bootloader? I can tell you that I've successfully reflashed my Nano 3.0 with OptiBoot and it works fine when I upload sketches to it using "Uno" as the selected board type.

If that is true why does the core's board.txt have an entry for just some boards but not for instance the Uno board?
#nano328.build.variant=eightanaloginputs

I'm not one of the original Arduino development coders so I can't speak to why they wrote it that way.

What I can say is that all eightanaloginputs/pins_arduino.h does is include standard/pins_arduino.h but redefines NUM_ANALOG_INPUTS to be 8 instead of 6.

The only place NUM_ANALOG_INPUTS is used is in in boards.h where it sets TOTAL_ANALOG_PINS, and the only place that's used is in IS_PIN_ANALOG(), which doesn't appear to be used anywhere.

As far as I'm aware the only place where the number of analog pins would be relevant is in analogRead(), and the only thing analogRead() cares about is if you're sending it 0-7 (the analog pins by themselves) or 14-21 (the analog pins' digital pin equivalences).

In any event, this code compiles & uploads fine when the board type is set to "Uno":

Code:

void setup(void) {
    Serial.begin(9600);
    }

void loop(void) {
   Serial.println(analogRead(7));
   delay(250);
   }

but of course it won't actually do anything unless you're using an ATMega328 with A6 & A7.

However he will lose I believe the ability to use the extra 2 analog input pins that the nano's version of the SMD 328p chip has. If he wants those back be has to edit the nano/328 entry in the core's boards.txt file to reflect having the Uno's bootloader name, path, baud rate, fuse bytes, memory size, etc.

No need for anything like that. A6 & A7 are defined in pins_arduino.h, which is common for all "standard" board entries.

The standard Nano you have is using the Duemilanove bootloader, which works at 57600. Even though it's a different form factor, you program it by picking "Duemilanove" from the board type menu.

The Uno uses OptiBoot for its bootloader, which works at 115200 baud. It's the new standard because it's smaller (512 bytes vs about 2K). When you burned your new standalone chip you got OptiBoot.

So, if you treat your new Nano clone as a Uno, everything should work fine.

Good luck!

im always getting a value (with no pins connected what so ever, only usb cable!), and the longer my uno is on with that code, the more the value increases.
How come ?

Noise. You don't have the pin connected to anything, so it's picking up noise.

On Nick Gammon's page see the section "how to get a response from a slave". Specifically the code line

Code:

byte a = SPI.transfer (what);

On the master you call SPI.transfer() to send a byte to the slave, and the function returns the byte coming from the slave.

How do you burn a new bootloader to a chip on a surface mount board such as Nano?

The exact same way. D10 on the Arduino running the bootloader upload script to the reset pin on the Nano, D11 - 13 from the uploader to pins D11 - 13 on the Nano, ground to ground, and 5v to 5v.

RP is correct, the default Nano bootloader is the one from the Duemilanove.

I reflashed my Nano with OptiBoot (the bootloader used on the Uno) and have had no problems. I've now got OptiBoot running on all my boards & standalone chips; now I can leave the board at "Uno" and not have to switch every time I move between projects.

Correct. Stepper motors are current driven. It's very common to drive stepper motors at 12-30 volts when using stepper controllers like the A4988 (used on the Big Easy Driver).

Good luck!

Does the Avaya phone speak Ethernet like a regular client (so it will be on whatever VLAN the switch port defaults to), or does it speak VTP (so it can negotiate which VLAN it will use)?

For the former, you can probably just use plain old DHCP with at most hardcoding a MAC address similar to a phone.

For the latter, I don't know of any Arduino libraries that can use the VLAN trunk protocol so you might have to roll your own. One thing you could do is sniff the packets between a real phone and the switch, then mimic them with your Arduino.

Good luck!

Nick Gammon has an excellent writeup on SPI, including master/slave data exchange, at:

http://www.gammon.com.au/forum/?id=10892

Good luck!

So why is there also sda/scl pins in R3?

The ATMega328 used on the Uno uses A4 & A5 for I2C, so for the Uno they're the same pins.

On the Leonardo, however, the ATMega32U4 uses pins D2 and D3 for I2C. The Due also uses something other than A4/A5.

If a shield needs I2C connectivity and uses A4/A5 it will only work with a Uno (and the older 328/168 boards). If a shield uses the SCL/SDA pins, however, it should work with all the Arduinos (except the old ones, which don't have those pins)

I should look over digikey and mouser more often, but I find them those sites a bit overwhelming.

I agree they can be daunting at first but they're manageable. I much prefer DigiKey's interface; I find it the easiest to use. Many times if I get something from Mouser, Newark, etc. I'll find it on DigiKey then cut & paste the part # at the other sites.

I start by searching for as close to what I need as possible, e.g. "atmega328p-au" or "1/4 watt 10k resistor". This generally does a good job of getting close.

Next I check the "In Stock", "Lead Free", and "RoHS Compliant" boxes and search again; there's usually no point in searching if they don't have it in stock and the other two seem to help whittle things down further.

Next I start going through the search boxes like "packaging" or "height", etc. for things I know I want, e.g. a specific size or footprint and click "apply filters" each time.

When the result list is a reasonable size I sort by "unit price" and buy the cheapest one (unless I know I'll eventually need a lot of the part, in which case I give "quantity available" some weight).

Having said all that, I try to do as CrossRoads says and batch up purchases at one of the Chinese companies; this is usually the overall least expensive option.