Due to some global internet issues outside of our control you may have issues accessing PayPal or using GitHub through our site. Please be patient and hopefully they’ll be up and functioning correctly soon!
Description: The Fio v3 is a new spin on the Arduino Fio hardware powered by the ATmega32U4.Not only is it small and LiPo-ready, it’s a very capable XBee-ready development board.
The JST-connector and 3.3v system voltage make this a great development tool for portable devices, simply plug in a Li-Poly battery and you’re ready to go. Wireless sensor networks and communication are made easy by the on-board XBee socket.
The ATmega32U4, running at 8MHz, makes it possible for you to use the on-board USB jack not only to charge a connected Li-Poly battery but to actually program the device! Because this board uses a similar bootloader to the one on the Pro Micro, you will need to download and install the special software driver below. There’s also a board definition add-on for the Arduino IDE which will add support for this board.
We’ve updated this to the latest version of the 32U4 firmware, see the firmware note in the documents below!
Note: See the GitHub link below for support with the Arduino IDE.
Based on 6 ratings:
5 of 5 found this helpful:
This is a nice board, easy to use and convenient to experiment with due to the USB loader.
Unfortunately, little thought was put into lowering the power consumption, so battery drain is far worse that it could/should be.
I don’t feel like replacing SMT resistors, so that battery sensor alone drains the battery. Add all the bright LEDs and the board is disappointing.
I also had issues reloading the official bootloader.
1 of 1 found this helpful:
I can successfully upload code to the board but the Serial communication does not appear to work. I have worked with many Arduino based boards since v1 or their IDE so I am familiar with how to set the baud rate for both the board and the monitor. I tried different rates too just in case some were not supported ( for whatever reason ). Would love to know if I was just missing something.
UPDATE: Looks like this board uses Serial in a different way, so make sure to read up on Serial1 vs Serial usage as they suggested. Board works as expected using Serial1.
Thanks for your feedback. Because the ATmega32U4 has built in USB, the USB serial line is different than the hardware serial line. For the hardware serial line make sure to use Serial1. If you still have any questions feel free to email email@example.com and they should be able to help you out.
1 of 1 found this helpful:
I am making a remote sensor with an XBee Pro 900 radio, and wanted 3.3V digital outputs without using level shifters. I was using the UNO, but it had 5V outputs, so I went with the Fio V3. This is definitely not as user friendly as the UNO, so I wanted to put some notes here for others and myself.
Obviously, read the hookup portion of this website. This is a different chip than the UNO, it does not use an FTDI USB connection, so you need different drivers.
As stated above, use Serial1 to talk to the XBee
With XBee Pro 900 only, you will need to remove R2 (RSSI) because it pulls this pin low making the XBee Pro 900 not work. Not an issue with other XBees (I think) but Digi decided to change around some pins for the XBee Pro 900.
The USB micro is very finicky. I found that it would re-enumerate while operating (bum-bum sound), not affecting the operation of the board, but obviously something about the communication between computer and board is not well. I also found that my computer would not recognize the device (yes, I had already installed the drivers), and I would go through a dance of resets, exiting Arduino, remove the cable to fix this. The best solution I found was that if I plugged the battery in first, and then the USB micro, the incidence of this problem decreased substantially. It also helped getting away from the “Unknown device” in Device Manager problem. I think powering up the device prior to data is necessary. A good summary of this is in https://forum.sparkfun.com/viewtopic.php?f=32&t=32342. But this leads to the next problem.
The 5V of the USB micro and the LiPo are connected together when the on-board switch is turned on, meaning the LiPo sees the 5V of the USB micro, which is bad for the LiPo. You fix this with remove of the SJ-2 jumper. This is described on this web page “http://www.forward.com.au/pfod/ArduinoProgramming/FioV3/index.html”.
When it works its great because everything I need is integrated, but it doesn’t “just work” like the UNO. I think bringing back the FTDI USB would make this much easier to work with. Sure, it means that this would be a little larger, but I bought this for the integration with the battery charger and the XBee, and it being a little bigger won’t affect my desire for this part.
1 of 1 found this helpful:
One little problem that Chris in Tech Support helped me solve in just a few minutes. Great tech support by the way!
The battery charge light always stays on even with the USB disconnected. The problem appears to be the boot loader is programming pin D13 as an output and leaving it that way. Pin 13 is connected to the charge LED but is designed to be an input so you can read it to determine whether the battery charger IC is charging or not.
If you put this line in your sketch setup() routine it fixes the problem.
I really like this board and I hope it keeps getting updates. I use it with an XBee radios for remote devices. I’ve been using the Seed LiPo Rider Pro for solar charging and it works great.