Design Raspberry Pi "Hat" Printed Circuit Board (PCB) for Sensors

[keenanjohnson]

A big way to drive the cost of the Frog down is to design a custom circuit board that contains some of the electronics, instead of buying multiple dev boards. We should explore this option :)

[keenanjohnson]

@lwbantoto has been taking the lead on this, so assigning this task to him :)

[daveb377]

Is this a Pi-Had or a PCB for the compute module?

[lwbantoto]

@daveb377 it's a Pi-Hat! It will be a stackable PCB

[daveb377]

SO a Pi Hat with a Sensiron sensor and a barometer? What else needs to be on there? Battery Interface/Solar power panel hookup?

[keenanjohnson]

Probably eventually a battery / solar hookup, but we'll need to figure out how to reduce the power consumption from the processor before that makes sense due to the lack of a sleep mode in the Raspberry Pi.

Yes the session sensor, barometer, and a GPS sensor are the intent for this hat.

[daveb377]

I spent 20 minutes looking for a Pi hat with those sensors with no success. I'll take a look at a board design, it doesn't look too difficult, although I might have some Pi related questions. First I need to out a Kicad problem with another project, it might be a week or two.

[keenanjohnson]

Sounds good! Reach out with any questions!

[daveb377]

@keenanjohnson - What sort of requirements are there on the CO2 sensor? The Sensirioin part is fairly large and expensive, and I'm wondering if there's a smaller part that would work? I'm trying to fit everything onto a Pi uHat for the Pi Zero, and it looks like it will all fit.

[keenanjohnson]

Hey @daveb377 we don't have any hard requirements on the Sensiroin sensor persay as we're still trying to identify the exact requirements from the data scientists. However, here are the loose requirement set:

• Humidity and temperature measurement ( The sensirion part includes an on board temperature and humidity sensor which is really important for the data analysis).
• A CO2 PPM accuracy of +/-30 PPM
• Good temperature stability
• NDIR sensing technology

If there is another part that fufils these requirements at a lower cost / size, I'm definitely open to it, but haven't found it yet.

It's great that you are helping to tackle this, but here's a few other key pieces of information for you that might make the Hat concept obsolete.
1 - We've switched in the BOM to the Raspberry Pi 4 CM4 module which includes a much higher gain antenna given I had some wifi connection issues with the small on PCB antennae on the Raspberry Pi Zero. So if we stick with the Hat format, we should probably size it for a normal raspberry pi.
2 - In another task, we've been working on a new enclosure concept to 3D print the full enclosure. Right now our concept has trended towards placing the sensors in a different enclosure section than the Pi, so I'm not if the hat concept really makes sense anymore? I'm open to people's opinions on this :). It would certainly make the whole package smaller if we did pursue it :)

[lwbantoto]

@keenanjohnson Are we satisfied with the humidity and temperature measurements from the Sensirioin part? Perhaps we should add our own temp sensors (thermistor) and humidity sensors on-board.

[keenanjohnson]

They seem reasonably good and I've been told that Sensirion makes the best in class humidity sensors. I'm open to other options though if we feel there is a real advantage to another sensor combination.

[lwbantoto]

For our application, redundant sensors is unnecessary right?

…

On Thu, Sep 23, 2021 at 9:33 PM Keenan Johnson ***@***.***> wrote: They seem reasonably good and I've been told that Sensirion makes the best in class humidity sensors. I'm open to other options though if we feel there is a real advantage to another sensor combination. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#22 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABXHIJFSUI36CJQJPYLVMGDUDPIPTANCNFSM5COSV2LQ> .

[keenanjohnson]

If it's free or very low cost it doesn't hurt I think, but I definitely don't think it's necessary here. For temperature we already have two temperature readings: from the barometer and from the SCD30. On Thu, Sep 23, 2021 at 7:53 PM Lance Bantoto ***@***.***> wrote:

…

For our application, redundant sensors is unnecessary right? On Thu, Sep 23, 2021 at 9:33 PM Keenan Johnson ***@***.***> wrote: > They seem reasonably good and I've been told that Sensirion makes the best > in class humidity sensors. I'm open to other options though if we feel > there is a real advantage to another sensor combination. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > < #22 (comment) >, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/ABXHIJFSUI36CJQJPYLVMGDUDPIPTANCNFSM5COSV2LQ > > . > — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#22 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AATQ3FW4OZAFWCY234H7CJTUDPR3BANCNFSM5COSV2LQ> .

[daveb377]

From a $$ point of view, the Sensirion is fairly expensive and large, $67.27/each at Digikey, so it's pricy compared to the Sensirion SCD41, which is $37.10/each at Mouser. I'll compare the specs for the two.

I'll also price out the various Raspberry Pi options. From an assembly point of view, fewer wires and interconnects to make is much easier to assemble and build, and causes fewer issues down the road, so it's for sure a better option if you plan to build more than 10 or 20 of these.

[keenanjohnson]

Yeah I definitely agree that a hat form factor would be nice for assembly :).

Looking forward to your comparison! I do still think the hat form factor makes sense :)

[daveb377]

@eren-rudy That's a nice summary. I copied that into the compute options spreadsheet, I hope you don't mind. I can remove it you want.

The CM4 has a unique connector that's not compatible with the other Pi's, which have a common connector. The CM4 is expensive, and focused for high volume industrial users, so I suspect it's harder to find. It would make for a smaller sensor I think but less each to source.

It sounds like adding a GPS receiver to the sensor would be helpful from a wiring point of view.

[keenanjohnson]

@eren-rudy yes we're considering moving the sensors for a few reasons:

• Moving the sensors away from the main processor reduces any thermal coupling between the sensor and the processor
• Moving the sensors, allows us to seal part of the enclosure providing better environmental protection for the more sensitive electronics (processors)

These two reasons would seemingly lead us away from a raspberry pi hat format. However, I do see the benefits of standardizing on a form factor. I think what might be the best compromise is to stick with a standard connector like QWIIC which some of our sensors already use.

The mechanical design is still a prototype though, and it's not certain if we "need" to decouple the compute from the sensors. What do you all think?

[eren-rudy]

@daveb377 No worries, its nice to have everything consolidated.

Yeah I think I agree that the larger hat form factor makes sense for standardization and sourcing flexibility.

@keenanjohnson Thanks for the clarification, that makes a lot of sense to me!

I don't really see too much strong reason for single-board consolidation, at least for now. Maybe someday, if there was high enough volume, it would be advantageous to have everything on one PCB to drive costs down (reduce wiring, connectors, and assembly complexity). For now, I think it makes sense to explore multiple avenues to see what works? I'm sure we could find ways to study the effects of those two reasons (thermal coupling and environmental protection of sensitive circuits), but perhaps that is a larger conversation that we can have elsewhere.

[daveb377]

Hmm. A QWIC interface might be very interesting. Have to look into that.
As far as the rational for a custom board, it would certainly make assembly easier, and cables are a continual problem area. Getting boards build in small quantity is surprisingly inexpensive now, Parts availability is probably more of an issue.

[keenanjohnson]

Yeah I would be curious if we can achieve a cost savings vs buying the individual boards for each sensor!

[daveb377]

Added details on the Raspberry power and interfaces, here's an editable link https://docs.google.com/spreadsheets/d/1TGryxRZgJ1XtoPHgSFU0XBkzrDwEvxxF2vDguaEpcZk/edit?usp=sharing
I think the HAT (40 pin connector) is possibly the most straightforward approach. I'm not sure how you'd make a board outline for both yet, but I'm sure it's pretty manageable. I suspect that a single board would be less expensive than buying multiple eval boards.

[daveb377]

Not sure this is legible, but here's a first cut at a dedicated Pi Hat. I've got the two sensors plus a GPS receiver with an integrated antenna.
My next step is to see about adding a battery management/Solar cell controller, but I need to do a little research on this first.

[keenanjohnson]

Wow this is great @daveb377! Do you have parts list you've chosen for the above?

[daveb377]

Here's a CSV in HTML, just to confuse things. I'm kind of surprised I can past something from Excel into here. Anyway, this uses the same environmental sensors as the original ribbit. I added a different GPS receiver, which has an embedded antenna, eliminating that pain point. I haven't scrubbbed for parts availability, but will look at JLCPCB to build them, but they may not have the sensors, so that would need to be hand soldered down.

JLCPCB sends fairly cheap fabricated PCB's from China, and they have a set of "house" parts, which also might be worth looking at.
`

<style> </style>

Ref	Value	Footprint	Datasheet	Manufacturer	Vendor
C1	0.1 uF	Capacitor_SMD:C_0603_1608Metric	~
C2	0.1 uF	Capacitor_SMD:C_0603_1608Metric	~
C3	0.1 uF	Capacitor_SMD:C_0603_1608Metric	~
D1	LED_RGB	LED_SMD:LED_RGB_Cree-PLCC-6_6x5mm_P2.1mm	~
J2	RPi_GPIO	RPi_Hat:Pin_Header_Straight_2x20
R1	10k0	Resistor_SMD:R_0603_1608Metric	~
R2	DNP	Resistor_SMD:R_0603_1608Metric	~
R3	10k0	Resistor_SMD:R_0603_1608Metric	~
R4	330	Resistor_SMD:R_0603_1608Metric	~
R5	330	Resistor_SMD:R_0603_1608Metric	~
R6	330	Resistor_SMD:R_0603_1608Metric	~
R7	0	Resistor_SMD:R_0603_1608Metric	~
R8	0	Resistor_SMD:R_0603_1608Metric	~
U1	DPS310	Phase0:XDCR_DPS310
U2	SCD30	Phase0:MODULE_SCD30
U3	L80-R	Phase0:XCVR_L80-R	https://www.quectel.com/UploadImage/Downlad/Quectel_L80-R_Hardware_Design_V1.2.pdf

`

[keenanjohnson]

Thanks @daveb377 ! I'll take a look soon!

[lwbantoto]

Hi @daveb377! Your schematic is a great start. A few nits:

• Are there I2C pullup resistors on the RPi?
• I would personally add another decoupling capacitor to U1 and U3 such that each IC's power pin has a dedicated cap.
• I'd also add bulk capacitance on this PCB. It'd be good to have three to five 1206 10uF 10V ceramics onboard.
• Can you please add the rated voltage and package (0402/0603/etc) to each capacitor? 10V is sufficient.
• Can you please add the package and tolerance for each resistor?
• The schematic can be cleaned up by using power ports and net labels. Please name the 3.3V rail P3V3.
• Did you create each of these part symbols yourself? The symbols could use a lot of work and can make the wiring cleaner (the location of ground pins in particular). I can take care of this
• I feel that we need more test points on key signals: I2C, 3.3V, GND
• Please remove the 4-wire intersection above U3
• Does U3's /RESET pin require a pullup?
• We should minimize the number of components and BOM lines as much as possible.
• The 10K pullup for U1's CSB pin can be removed
• The pulldown for U1's SDD pin can be removed
• The pulldown for U2's SEL pin can be removed

[daveb377]

Hi @daveb377! Your schematic is a great start. A few nits:

* Are there I2C pullup resistors on the RPi?

Good Question, on my list to check.

* I would personally add another decoupling capacitor to U1 and U3 such that each IC's power pin has a dedicated cap.

* I'd also add bulk capacitance on this PCB. It'd be good to have three to five 1206 10uF 10V ceramics onboard.

My next step with this is to look at adding a solar Charger/Battery bank to provide power without a wall plug. Part of that will be taking a better look at the power supply bypassing

* Can you please add the rated voltage and package (0402/0603/etc) to each capacitor? 10V is sufficient.

Will do, once I pick caps. 10V might be iffy with ceramics with high dielectric constants, they've got a capacitance loss as the DC voltage goes up.

* Can you please add the package and tolerance for each resistor?

Not picked yet. Probably 0603 1%, although I was going to look at the JLCPCB house parts.

* The schematic can be cleaned up by using power ports and net labels. Please name the 3.3V rail **P3V3**.

No. I hate schematics that rely on net labels, I find them difficult to track signal flow.

* Did you create each of these part symbols yourself? The symbols could use a lot of work and can make the wiring cleaner (the location of ground pins in particular). I can take care of this

The components came from SnapEDA. I'm lazy. I should probably figure out how to upload all this to Github. I'm using KiCAD 5.99, so something to figure out. Need to make sure the parts libraries are included.

* I feel that we need more test points on key signals: I2C, 3.3V, GND

Can't hurt.

* Please remove the 4-wire intersection above U3

Done

* Does U3's /RESET pin require a pullup?

Good question. I had to register for quectel to get the HW docs, waiting to get approved

* We should minimize the number of components and BOM lines as much as possible.

0603 resistors cost ~ 0

* The 10K pullup for U1's CSB pin can be removed

I'll change to DNP

* The pulldown for U1's SDD pin can be removed

That's a DNP

* The pulldown for U2's SEL pin can be removed

I'll change to DNP.

[keenanjohnson]

Hey all! Great collaboration here! Seems like a lot of the nitpicks probably aren't high value to discuss until we have a properly finished design that we can do a real design review on :).

[daveb377]

So time to pivot to a Beaglebone design? No worries, it's easy to do. I wonder if we can build a WiFi node on the Beaglebone?

[keenanjohnson]

At least in the short term, we've pivoted to a Beaglebone Black design until Raspberry Pis are readily purchasable (I'm told this will most likely be about 6 months from now).

Given that and the current mechanical design, I'm really not sure if this is a priority because the optimal mechanical design orients the computer board in a non-optimal way for a hat format. I think what might be the best compromise is to stick with a standard connector like QWIIC which some of our sensors already use.

It's up to you whether you would like to continue work on this or not @daveb377! I don't think it's a priority, but I'm sure we can figure out a way to use it if it exists in the future!

[daveb377]

Sounds good. I'll come back in a while to see what's going on.