Serial 11520

[Jordan Tucker]

The2018 United States Supreme Court decision in South Dakota v. Wayfair, Inc. has impacted many state nexus laws and sales tax collection requirements. To review these changes, visit our state-by-state guide.

Automating sales tax compliance can help your business keep compliant with changing sales tax laws. AvaTax delivers real-time sales tax rates and uses advanced technology to map rates to exact address locations, based on the latest jurisdiction requirements.

NOTE: The outbreak of COVID-19 (caused by the coronavirus) may have impacted sales tax filing due dates in 11520. Please consult your local tax authority for specific details. For more information, visit our ongoing coverage of the virus and its impact on sales tax compliance.

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.

By connecting to the FioV3 at a baud rate of 1200 and closing the COM port, this will initiate a software reset with the Atmega32U4 just like the Arduino Leonardo (as stated in the Automatic (Software) Reset and Bootloader Initiation for a Leonardo => ) .

The Fio V3 has the capability of measuring the battery voltage of an attached Lipo. There is a resistor divider with two 1k resistors connected to 32U4 pin PD6. PD6 is actually A11 in Arduino. Doing an analog read on A11 will allow you to calculate the voltage remaining in the battery. The reading will be 1/2 of voltage level and you can calculate voltage with a simple equation.

Battery voltage = (analog reading * (3.3/1024)) * 2

Interrupts Atmega32u4's built in CDC driver for USB communication can have timing issues when messing with the watchdog timer, sleep modes, and timer interrupts. I am unsure of how to fix this issue if you continue to use code that interferes with the CDC. I recommend trying a different method than using the interrupt timers.

Wrong Bootloader It's possible to brick your FioV3 if you used the wrong board selection with the wrong frequency. If you upload the wrong frequency, the IC will not be able to understand any new code that is being uploaded. It expects to have code that is compiled for another bootloader, instead of using the 8MHz frequency with the oscillator.

When either of these cases happens, the device manager is not able to recognize the device and is usually seen as an "unknown device" when the microcontroller runs the sketch. There are ways to recover the an Atmega32U4 (i.e. LilyPad Arduino USB - Atmega32U4 board, FioV3 - Atmega32U4, Pro Micro 5V/16Mhz, Pro Micro - 3.3V/8Mhz, etc) if this happens. Check below for more information:

You can try the double reset method by tapping the RST pin to GND twice (since there is no reset button on the board) as explained in the Troubleshooting sections labeled as Reset to Bootloader and How to Revive a "Bricked" Pro Micro => -micro--fio-v3-hookup-guide/troubleshooting-and-faq.

6.) Re-open the Tools>Port menu to view the list of COM ports again to see what the FioV3 enumerates to when its in its bootloader. There is an 8 second window to view the COM port when the board is in bootloader mode.

After selecting the correct board definition and timing the double reset method correctly, I was able to upload successfully. It took me a couple of tries before I could get this right because of the timing. You should not need to go through this recovery procedure for subsequent uploads unless you brick the Atmega32U4 again.

You will need to connect to the same pins to your target device (i.e. LilyPad Arduino - USB, Pro Micro, Fio V3, Makey Makey, or Leonardo). On the Leonardo you can connect it just like the Uno. The LilyPad Arduino - USB has small ICSP pins. I managed to solder wires directly to the pins for access. The Pro Micro does not have an ISP header and the pin numbers are different. Check the tutorial for location of the pins on the programmer. Here are the pins for the FioV3 Board:

3.) ProgramUsing Arduino v1.6+ go under Tools and select the correct programmer (if your programmer uses a COM port select that too), and the correct board (LilyPad Arduino - USB, Pro Micro, FioV3, Makey Makey, or Leonardo). Then select Burn Bootloader. For the Pro Micro, this will use the bootloader in the addon file, so make sure you have the correct addon file installed. You can find the latest board definitions from the SparkFun GitHub Repository [ _Boards ].

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.

I always desolder or cut these resistors, R6 and R7, before using a Fio v3 in a project. This reduces quiescent current to about 70A when the power switch is off.This mod only eliminates the ability to read the battery voltage on analog pin A10 and has no other effects.

I have 2 fio V3 boards, current consumption is roughly 2mA when power switch is off. E.g. it is really unusable with 110mAh battery :(With original FIO the current consumption is 0.0uA when power switch is off.

Sparkfun: I would like to both measure the battery when device is powered and have long battery life when not powered. I guess that it is not possible? Or can some wiring be done with board to get voltage divider after power switch?

The trace between pull-up resistor R14 and VBATT goes next to JP7 which is the external power switch. I think that by cutting pull-up resistor's trace between JP7 and U1 and then connecting the trace to JP7 (to hole which is closer to USB connecter) it should be possible to get both zero power consumption when Fio is switched off and battery level monitoring functionality.

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?

Make sure you have the drivers installed correctly and are using the correct board definition in the Arduino IDE. Also keep in mind there are a few differences in the ATMega32U4 vs the ATMega328, so it might be working just not the way you want it to (one very common thing people run into is that the hardware serial line/ XBee port is on Serial1 not Serial). If you are still having problems email techs...@sparkfun.com

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.

Nope, Pro is the name we use for a slightly stripped down version missing headers and other connectors (like the Arduino Pro, Arduino Pro Mini, Pro Micro and the Mega Pro). This is a new Fio with a different microcontroller. As for the V2, it is right here.

3a8082e126