The SparkFun Qwiic HAT for Raspberry Pi is the quickest and easiest way to enter into SparkFun’s Qwiic ecosystem while still using that Raspberry Pi that you’ve come to know and love. The Qwiic HAT connects the I2C bus (GND, 3.3V, SDA and SCL) on your Raspberry Pi to an array of Qwiic connectors on the HAT. Since the Qwiic system allows for daisy chaining boards with different addresses, you can stack as many sensors as you’d like to create a tower of sensing power!
The Qwiic Pi HAT has four Qwiic connect ports, all on the same I2C bus. In addition, many of the useful GPIO pins on the Raspberry Pi are broken out. This HAT is compatible with any Raspberry Pi that utilizes the standard 2x20 GPIO header. It has been designed to sit to the side of the Pi, allowing it to work conveniently with a Pi Tin enclosure to connect boards to the Qwiic ports.
Note: There is a small silk error that has reversed the SDA and SCL. This is simply a cosmetic mix-up and will not impact any function with this board.
The SparkFun Qwiic Connect System is an ecosystem of I2C sensors, actuators, shields and cables that make prototyping faster and less prone to error. All Qwiic-enabled boards use a common 1mm pitch, 4-pin JST connector. This reduces the amount of required PCB space, and polarized connections mean you can’t hook it up wrong.
If it requires power, you need to know how much, what all the pins do, and how to hook it up. You may need to reference datasheets, schematics, and know the ins and outs of electronics.
Skill Level: Rookie - You may be required to know a bit more about the component, such as orientation, or how to hook it up, in addition to power requirements. You will need to understand polarized components.
See all skill levels
Based on 4 ratings:
1 of 1 found this helpful:
It was a snap to install getting my project up and running in no time. I was able to get any I2C device connected with the purchase of additional wired connectors. I plan to purchase more for other projects.
I had a prototype that was pretty much an unmanageable tangle of "Dupont" wires. The PiHat fixed that and the prototype is running well.
I'll be back for more!
Two small complaints: a) Despite the Sparkfun video saying otherwise, my PiHat had to be installed hanging off the Raspberry Pi. b) Sparkfun's stock seems to be low on several parts and the extra shipping is annoying. The parts arrived quickly, but the cheapskate in me complained about the cost.
I like this hat better than the other PI QWIIC hats because it has additional breakouts for other pins as well. There is just one thing to note however, the i2c pins are miss labeled. SDA and SCL are backwards. I wish the other hats had break outs for other rPI pins as well.
Lets face it - The ENTIRE reason this thing exists is to make it easy to just plug and play some QWIIC devices, and expose some other pins on a header to connect some non-QWIIC devices..
I just wasted about 4 hours troubleshooting my project, which worked when connected to a breadboard, but failed completely when connected through this HAT. Certainly I must have made a mistake in wiring.. check, doublecheck, and only when I went DIRECTLY to test continuity to the GPIO header on the PI did I find out what I now realize another reviewer also mentioned.. A discrepancy in the SPI labels I was trying to hook up a MiFare RFID card reader which wants "SDA" to be connected to pin 24 (https://pimylifeup.com/raspberry-pi-rfid-rc522/) so naturally I connected it to the pin labeled SDA on this hat, but I find that pin 24 is actually connected to CS. I guess now it makes sense, because looking at a generic PI pinout, it does show pin 24 as an SPI chip select. This highlights what I know, but didn't think would come up in this situation - Each pin on a Raspberry pi can have different functions depending on how it's being used. Labeling this hat in this way is misleading, and although it's meant to be useful, it means I had to test continuity for each pin to make sure it was what I thought it was, regardless of the label.
In the next version of the board, I would recommend that instead of the function names, just label the pin numbers on the board, so that people can be SURE of what they're plugging into, and as a matter of fact - Why not just expose all 40 pins again, and let me stack another hat on top of this thing? In the space you have those few specific pins and their labels, you could put a 20x2 header (or just the holes, and let me solder one if I want) and then this thing would be WAY more functional, and the labeling wont be misleading.
I know that it really happened because the author of the MiFare driver decided to use non-standard pins (I guess in order to not interfere with i2c??) but in my hours of troubleshooting, it sure made it frustrating not to just have pin numbers on this board!
FWIW.. Now that I understand it, the board is working great, and I'm sure I'll use it again - I'll just have to reference the label to the pinout diagram (or just reference the schematic) to figure out what pin each header hole is connected to!