Is there a way to use higher baud rates than 115200 when working with an xbee? I've been trying to jump up to 230400 but although both xbees are set up for 230400 and "Serial1" is initialized with 230400, the data received is gibberish. This doesn't happen with "Serial" though. When using the USB Serial, it can go to 230400 without a problem.

So Serial1 doesn't seem to go higher than 115200. While Serial doesn't have any problem doing so.

Is this a library issue? Maybe there's a piece of code somewhere capping the baud rate to 115200? Because the ATMega32U4 at 8 MHz should be able to handle all the way up to 1000000 baud rates. My Xbees are capable of baud rates up to 230400.

There is a voltage divider on the output battery voltage before the switch. I noticed this was a comment on the previous model as well, and I believe that means the board will always be drawing current (a bit over 1mA depending on battery level since the total resistance is only 2k!). I understand the desire to measure battery voltage, but I question putting this divider before the switch, since when the switch is off the MCU can't usefully measure the voltage. As for off-board measurement, I feel this might be better implemented with an unpopulated pad so the user can choose to add this measurement before the switch, not as the default state. Can anyone see a danger to removing these resistors/cutting the trace? That's what I plan to do to keep sleep-state current draw to a minimum.

As mentioned in the tutorial, the Arduino add files on do not work for Arduino V1.5. I have fixed this and put up a set of files that work with Arduino V1.5.5

These are available from http://www.forward.com.au/pfod/ArduinoProgramming/FioV3/index.html

It appears that the VBATT_LVL pin is not correctly marked. To monitor the voltage from the battery you will need to use A11. You can use the following formula to determine the actual input voltage.

(sampleValue * (3.3/1024)) * 2

The sample value is the value from the analogRead(A11) call

3.3/1024 obtains the number of mV/step. The DAC is 10 bit, so there are 1024 values available and the processor is operating at 3.3v.

1/2 the input voltage to the divider is sent to the pin per this wiki entry:

http://en.wikipedia.org/wiki/Voltage_divider

So in this case we multiply by 2 to reverse the division.

to use bluetooth module you need to do Serial1.begin NOT Serial.begin this took me forever to figure out

Also how do I monitor the battery status?

I plan to use a wireless charger to charge the LIPO. Is there a way to stop it from switching on while charging?

The Arduino Buying Guide says that this board can be powered from 3.3v to 12v. What pin do I wire to my 12v battery in order to power it?

Hi guys i m not english so if im speak badly so sorry for it.Im coming subject.I have fio v3 and 6 v nimh battery.Can i run it with from JST connector?

Anyone know how to reprogram these remotely using Series 2 XBee? Seen a few people say it's possible, but I can't find any examples anywhere. Any help would be appreciated.

There is a very large solder bridge between the VCC pin and the D- pin on the USB connector on one of my newly arrived Fio boards. Might want to check on quality control.

Hello. Please explain exactly where is the jumper SJ2 to be cut to this damn Fio ceased to kill the batteries from overcharging. Is the jumper near ASO LED?

Can someone update the eagles files of this product on github so they match the files posted here?

Sorry if this is a repost, it didn't appear the first time.

It seem that I brick two FIos v3 only by programming them via USB. It happened to me on two occasion with two different sketch on two different computer. Once the sketch is uploaded, the Fio doesn't excute anything and it never appear to mount via USB. The first time I blame the USB connector but now it seem to be more MCU related. Beside flashing the booloader via ISCP, is there something else I could try?

Hi, I have two Fios v3 that stop mounting USB once I programmed ( flash ) them ( two different program ). It doesn't seem to be the software since uploading them on another board ( Fio ) works fine. It happened on two diffrent computers. It looks like uploading a sketch bricked them since nothing works ( not just USB). Is it something specific to the 32u4 because I never experience something like this on any other arduino board? Beside using ISCP to reflash the MCU, is there something else I could try tro revive those boards?

I love this little board and have used several of them. The only problem I have had is with the micro-USB connector. Its physical connection to the board is just too fragile. I have now had three of them rip off which pretty well ruins the board. This is a particular problem when the fit with the male USB connector seems a little tighter than normal. This has caused me grief with the Sparkfun Cerberus cable. It sure would be great if future versions of the board had a stronger physical connection for the USB. Thanks much.

A 3D Model of this board would be so helpful. The hole locations, connector locations, reset switch and clearance for the XBee board make this board non-trivial to mount/enclose. I tend to use this board for nearly all my projects and I model all my projects in Autodesk Inventor before I build. Consider this a friendly request for a 3D Model.

Shouldn't this be called the Fio Pro? And where is V2?

I don't know if this is anything, but I have been going through the schematics to find where VBATT and USB_VCC get connected when the power switch is turned on. There is a net named RAW on the wire just after the power switch connecting to U6. I cannot find any other instance of RAW on the schematic. Is it possible that the RAW net is connected to USB_VCC? When running of of USB, do you need to turn on the power switch to make the board run? (RAW is after the power switch and would connect to VBATT when the switch is closed). If that's true, then there is a trace conecting from the USB_VCC after S2 going to U6 that needs to be cut. At any rate, somehow USB_VCC connects to VBATT when S2 is closed. The switch connection to U6 needs to be traced back to USB conector pin 1. I'm a litle suspicious of the label CHARGE_STAT. It connects pin 1 of U6 back to PC7 on the Atmega. It's possible that charging status LED D4 is always on if pin PC7 is sinking current. The datasheet talks about the LED resistor connection, or connection to a micro pin using a pullup. They don't talk about connecting both at the same time. Also, there is a labeled wire all by itself on the schematic labeled "CHARGE_STAT" just above the voltage divider. It doesn't seem to be connected to anything. It seems strange. Just wondering if that might be causing problems in the netlist. Sorry for the long post. I have been looking at alot of schematics, checking net lists and reading too many datasheets lately...

Why not just up the resistance on R14 and R15? I've routinely used voltage dividers using 100kohm resistors with other micros. The trick is to bypass R15 with a 0.1 uF capacitor (or maybe 0.01uF) after they are replaced. It's hard to tell from the pictures but they look to be 0805 or possibly 0603 package. Removal is fairly simple. One of my favorite tools, (actually it should be upgraded to my favorite tool) is "Chipquick". It is a very low temp solder that is excellent for removing SMD components. You just melt it onto the SMD solder joints where it mixes with the existing solder to lower its melt temp. Once that is done, all of the solder joints remain liquified long enough to remove the offending component. Then, touch up with flux and desolder braid. After that, pop on the new resistors. That should drop the current consumption to 20 uA. Still not perfect, but a nice improvement.

This design has some serious problems. If a battery is connected with USB connected and the power switch is on then 5 volts is connected to the battery. BAD! The charging LED is always on. BAD! All the LEDS for power, serial in and out are always on, not good for battery power. BAD!

I may have found a very strange bug: printing the result of modding a large number (over 10,000,000) with 1000 concatenated with a string seems to crash the microcontroller. If the number is concatenated with a char, no problem. I don't see this error on a Leonardo, which also uses the 32u4, so it may be a problem with the board definition for the Fio v3. This one was pretty annoying for me, so I hope this helps someone in a similar situation! Here is the code I use to replicate the bug:

uint32_t counter = 9996000L;
const uint8_t millisBtwUpdates = 100;

uint32_t lastWriteTime = 0;

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

void loop() {
  if((counter - lastWriteTime) > millisBtwUpdates) {
    int msecs = counter % 1000L;

    Serial.println(String(counter)+", "+String(msecs));  // causes crash
    //Serial.println(String(counter)+','+String(msecs));  // does not cause crash
    //Serial.println(String(counter)+","+String(msecs));  // does not cause crash

    /*
    // does not cause crash:
    Serial.print(String(counter));
    Serial.print(',');
    Serial.print(msecs);
    Serial.print(',');
    Serial.println(String(msecs));
    Serial.print('\n');
    */

    lastWriteTime = counter;
  }
  ++counter;
  delay(1);
}

My CHG (charge) light is always on, even while running under battery only and when there is no battery. I thought the purpose of the light was to indicate that the battery is being charged. If not, how does it differ from the power light.

FYI: I am not using pin 13

can this fio identify as a different usb device? id like one to show up as a midi device.

Is it possible to use PS dualshock 3 battery for arduino fio v3 ?

Great board with some simple but extremely convenient differences from the original Fio. Even if you don't use XBee this is a great board for sensor networks.

I just question the decision to use a micro-B connector, especially when it's the programming interface. Extremely fragile. They will break at some point.

I have two XBees, each on Fio v3. I've checked over 10 times that I'm using CoolTerm that I've written the correct DL for each. For some reason, when I power up both boards, neither ASO light blinks. Any ideas as to what's going on?

Can I use CoolTerm directly with this board, or do I have to use something like the Explorer?

Can I use a 3.7v 500mAh Li-Poly battery with this?

I have just started with the Fio v3.

I managed to load the Blink example into the board from my Mac but it now seems to "lose" the serial port. I think I could have loaded Blinky with the board set as a Fio not a Fio v3 (Sparkfun library).

I can get the connection back briefly by doing a quick double reset, connecting and uploading but this seems very wrong.

The serial monitor wont work while a program is running.

I read on the site that I might have to reinstall the Bootloader for which I need yet another connector (sigh)

Has anyone else had this happen- am I on the right track with the Bootloader?

Many thanks

What's the pin spacing if I want to solder female headers for jumper cables and breadboards?

What is the purpose of the built in jumper between USB_VCC and RAW? If you plug in a battery, then turn the power switch to on, then plug in a USB cable, 5 volts is dumped onto the battery through F1. My Lipo got to 4.5 volts and started to get warm before I noticed this.

is there any way to turn off all the LEDs on this board? its not so much about power consumption (though i imagine they do consume a measurable amount) its more about LIGHT - i am using this on a breath sensor used in sleep apnea studies and this thing generates so much light that I have had to cover each LED with blu-tack but its hardly professional looking.

Have got two Fio v3 and both are detected by Windows as VID_1B4F&PID_0004 The drivers referenced here does not support this PID.

Could anybody help to find correct drivers?

Device does not work with Windows 7x64. Drivers are not compatible with Win7 & XP and installable as "legasy software" only.

OK, for people having issues with this board running on Windows 7 (and maybe other OS's), here is the problem I was encountering:

When downloading the IDE restarts the board and it goes into bootloader mode. It only spends 8 seconds in bootloader mode before going back to the user program, which wasn't long enough to force Windows to update the driver. The device would disappear before I got far enough to select the driver.

Step 1: Open the .SparkFun ProMicro.inf file in an editor. Add the following two lines to the DeviceList and 64 bit DeviceList:

%DESCRIPTION%=DriverInstall, USB\VID_1B4F&PID_F100

%DESCRIPTION%=DriverInstall, USB\VID_1B4F&PID_F100&MI_00

Step 2: Save the file, open a command prompt (as administrator) and type: set devmgr_show_nonpresent_devices=1

start devmgmt.msc

Step 3: In the View menu, show Hidden Devices. Find the USB IO Device, right click and update driver. Select to open a driver on your computer, then select to browse for a device. Select the driver from Step 1.

Now your device should enumerate and program correctly. Took me a full day of screwing around with it to get this right, SparkFun, please add the device id's to your GIT download.

I used the Fio with an XBee and motor driver chip to quickly prototype a small robot. More details here: http://mechinations.wordpress.com/2013/11/10/robot-prototyping-101/

Are the Status/Charge/RSSI led's different colors? I ask as I'm probably going to light pipe them, and might use just one to cover all three if so.

Has any one successfully uploaded a sketch witlessly over xbee? If so a bit o help would be appreciated, all I get is: "avrdude: error: buffered memory access not supported. Maybe it isn't a butterfly/AVR109 but a AVR910 device?"
i can upload over usb but i would like to do it wireless.

I am fairly new to Arduino development, however I have been able to upload sketches to an Uno and a Micro. Unfortunately I cannot figure out how to upload to the Fio. I keep getting the following error message:

avrdude: stk500_getsync(): not in sync: resp=0x00

if I press the shift button while initiating upload I get: avrdude: usbdev_open(): did not find any USB device "usb"

I have Arduino IDE 1.0.5 running on Windows Vista. I have searched the web and tried a ton of things. I have the right board selected ("Arduino Fio") and I am definitely using the correct serial port.

Any ideas?

Warning!! DO NOT run the standard BLINK example if you have a battery connected to this board. The output of pin 13 is connected to the output of the battery charger chip STAT and THERE IS NO CURRENT LIMITING RESISTOR.

Excessive, damaging, current will flow when one output is high and the other low.

Standard Arduino boards add a current limiting resistor between the two output pins when this situation can occur, such as with the RX serial pin.

I am unable to load the "blink" example on my fio v3. There is no error message, but no blinking though! Is fio v3 compatible with ide 1.0.3? What about Due?

I have put up a tutorial on setting up the RN-42XV bluetooth module and the RN-XV wifi module with this board at http://www.forward.com.au/pfod/ArduinoProgramming/FioV3/index.html

I have an XBee radio that, when plugged into an explorer, is fully functioning. However, when I plug that XBee into my FIO v3, Serial1.available() always evaluates to false. On the FIO v3 I've also soldered an accelerometer in on the GND, 3V3, A1, A2, A3 pins and am able to read those values just fine via analogRead(). Another oddity I noticed is that even when I don't do a Serial.begin() the Serial.println() commands I was using for debugging are still showing up in the IDE's Serial Monitor when the FIO is connected to my machine via USB. Any ideas welcome on where I could be going wrong!

Unfortunately to fit my enclosure I have to remove JST connector, is it easy to desolder it ?

I'm installing the Fiov3 Addon to Arduino IDE 1.5.2. My sketchbook location is /Users/myName/Documents/Arduino. After I extract the zip, should the path be /Users/myName/Documents/Arduino/hardware/Fiov3/boards.txt or should it be /Users/myName/Documents/Arduino/hardware/boards.txt? I tried both but don't have Fio v3 appearing in the Tools->Boards menu. TIA!

I have bought a few Fio v3's from Sparkfun now and wanted to interface it with an SD card and the Roving Network's Wifi card so that I would have a fully portable web server.

I notice that D12 and D13 aren't pinned out and those are the SPI data lines I need to talk to an SD card with Lady Ada's breakout (http://www.adafruit.com/products/254).

Any way to talk SPI off of the Fio v3? Are they exposed somewhere in the X-Bee socket?

Dave

I'm having great difficulties uploading a simple sketch to the Fio v3 and am getting conflicting advice which version of the IDE to use. I think I've now tried every conceivable combination of IDE, Addon etc but still have no luck. The best results seem to be with IDE 1.0.3 and the Addon installed in a directory called "hardware" in the directory of the Sketch, then selecting "Arduino Fio v3 (Leonardo)" from the Board menu. That allows me to compile the sketch without errors and start what seems an upload (observing a few blinks of the RX LED). The upload however hangs and the sketch does not start to run. I've tried pressing the reset button once and twice at various moments (before initiating the upload and after). I now have two boards, one where the ASO LED is blinking (about 3-4 times per second) and another where that is not the case.

I've spend many hours on this now and I'm getting a bit annoyed (as you probably can imagine). Is it really that complicated to program a very simple sketch (the famous LED blink sketch) into an Arduino Fio v3?

I'm using a linux workstation; the USB serial port is always recognised without fail after inserting the USB cable.

Any advice is much appreciated.

For some reason the IDE changed the selected board to Arduino Fio instead Fio v3 (Leonardo) when I was uploading code. Now it doesn't work, it still upload code but doesn't work correctly, plus TX/RX leds doesn't blink in the process... Any solution??

Trying to simply get a WiFly to work with this Fio (V3). It would seem simple serial communications should not be that difficult. I'm evidently making this too hard or missing something fundamental. Here's my simple sketch just to get it to join my network. Any feedback on what I'm doing wrong?

void setup() { Serial.begin(9600); delay(500); Serial.print("$$$"); delay(100); Serial.println("set wlan ssid thisismywlan"); delay(100); Serial.println("set wlan pass thisismypassword"); delay(100); Serial.println("save"); Serial.println("reboot"); }

void loop() {

}

Hi,

I recently bought an Arduino Fio v3 and XBee Series 1 I'm trying to establish 2-way serial communication between the Fio/XBee and another XBee connected to USB Explorer and my MacBookPro.

However so far I'm only able to establish 1-way communication. Meaning I can send commands e.g. 1, 0 to the Fio/XBee and make it switch on/off the onboard LED. However I'm unable to receive any communication back from the Fio/XBee.

TX LED on Fio is always on RX LED on Fio is always off. ASO LED is blinking indicating established connection. RSSI LED lights up when sending commands to the Fio/XBee.

I connected the XBee to another Arduino UNO with regular XBee shield and 2-way communication is possible without any problem. Which made me exclude any setup error on the XBee side.

I configured serial communication on the Fio/Xbee to use Serial1 (which supposedly sends it directly to XBee vs USB). If I use Serial it sends communication back to my Mac via the USB cable which crashes my Mac after a short period of time. Fio is currently powered by either USB to my Mac or external USB power supply.

Any advice would be appreciated.

Best, Daniel

Any idea why using pins D2 and D3 for software serial rx/tx would work just fine on the UNO but aren't working on this v3 Fio? I'm trying to get the Fio to talk to the Atlas pH board. It works fine on the UNO but the pH board doesn't respond to any commands like the UNO does.

Has anybody had any luck installing the new drivers/updates on Mac OSX? I put the folder in the sketchbook folder per the readme.txt file but don't see the new FIO (leonardo) version in the board list. Any suggestions? Thanks.

Love the board. Worked perfect for an art project. This is a really great solution, particularly because of the ability to generate USB keyboard and mouse events. It would be nice to be able to use all 12 analog inputs. One is dedicated to the battery level monitoring. It would also be nice to have examples of using 2 of these and 2 x-bees for the first timers. A simple USB Serial to X-Bee echo program would be useful.

I see more pins on this Fio v3 than on the Arduino Fio. I can't find a definition of which pins are capable of PWM. Can someone help with that please? TIA.

The schematic shows that there is a resistor dividor circuit to monitor the battery voltage from what looks like Analog pin 10. Is this correct, do i just need to set an analog read of pin 10 (which i assume will read that pin 10 not the normal digital 10) to read this voltage?

Did you change any of the contents of the "Arduino Addon and Driver Files" recently (last week)? Magically, I can't upload anymore code to my board. It fails with the same error that's been described when the ProMicro addon stuff was broken (http://arduino.cc/forum/index.php?topic=111213.0). This happens on Windows as well as on Linux.

It's been already working however, so I would exclude the bootloader version as a reason.

I can't track it back to a change in the addon files (no backup of old stuff here). Yet I'm pretty sure I've seen that pins_arduino.h in the prior version had an error in the SPI mapping. The moment I did a fresh Arduino IDE (1.0.3) and addon code install (yesterday) matches pretty much the point where it stopped working.

I was able to upload once to this board, but now it won't even show up as a serial port. What do I do? I think may have used the Arduino Leonardo as the board type instead of the Sparkfun version. Is there a way to recover from this?

I am having trouble getting this to work with XBee XSC S3B on peer-to-peer (transparent mode). The x-power is set to lowest and loopback test with x-ctu showing the chips to be in working order. Any ideas on what might be wrong?

Would you clarify "Fio v3 is not yet compatible with the Arduino v1.0 IDE" I've been using the original Fio with the Arduino IDE and have not had trouble. Is this incompatibility new to this version of the Fio?

NEW FIO! Been waiting for this.