Yes we are also considering the ESP32 and looking for ways to make the PCB compatible also for the Wemos Mini ESP32 version.
We do like the ESP8266 as it has been proven extremely reliable (more so than the ESP32) and thus think it is a good idea to continue using it.
However, the ESP8266 also has limitations, e.g. no additional hw serial pins etc.
We can consider placeholders for other sensors. Please post what sensors you normally use.
As for other sensors, I only started exploring the microelectronics and air quality worlds when I stumbled upon the DIY kit so I do not have any other sensors as of now. However, I was at least considering to look at some of the Bosch BME sensors. They seem more expensive but maybe they are of interest to some people around here. Plus at least for Europe they seem easy to source.
I like what I see, as Ibhm has covered in detail.
One idea: have you considered mounting the PM2.5 sensor entirely off-board, i.e. on the case rather than on the PCB. Since it’s wired in with cabling anyway, it doesn’t need to be on-PCB. Of course that then changes the kit to almost require the case. Or maybe two variants, one with this PCB, case sold separately, and one with the smaller/different PCB but case included? It would muddy the “product line”, I guess.
Also, can you include a zoomed-out pic where we can see where the display would be visible on the complete assembly? It’s kinda unclear with the current pictures.
I strongly agree with Ibhm regarding power plug and cable. Maybe a USB cable, but I wouldn’t include the wall wart/power plug for the reasons mentioned.
Here is a picture of the front:
It includes an optional LED Strip that shines through the enclosure and could be added relatively easily.
@klausman What would be the advantage to not mount the PMS sensor on the PCB? Would you still put the PMS inside the enclosure? To be honest I do not really understand the reasoning behind your comment.
What would be the advantage to not mount the PMS sensor on the PCB? Would you still put the PMS inside the enclosure? To be honest I do not really understand the reasoning behind your comment.
The idea being that if the PCB is a (relatively) good heat conductor, having no contact with it at all would be even better than spacing things out. Not sure if the case itself would carry heat just as well as the PCB does.
I like the new kit except it looks like the breakouts from the original board are gone. I did notice the additional I2Cs breakouts on the upper left.
For my builds I have been using a SGP30, and for the specific sensor I’m using (Adafruit STEMMA SGP30), I’ve actually had to use jumpers because it’s not pin compatible with the board. I used this because there’s a regulator on board and the data sheet for the SGP sensor says it needs1.8V. Not all of the pin compatible breakouts have this regulator/shifter. (I burned the original one I sourced.)
With regards to the mounting location of the SHT sensor, I saw the results from forum user @ttielemans , and intended on removing the SHT sensor entirely. I’ll be replacing the PMS5003 with the PMS5003T.
I like the idea of optionally including an enclosure, if that is what you are suggesting. I used a 3rd party 3d printer and would rather have contributed the £ to you. Luckily I live where there are plenty of choices but many people would have less or no choice.
Looks good, one other item that I think needs addressing are power requirements. I’ve seen many issues raised on the message board about inconsistent or irregular readings, and alot of this stems from insufficient power being fed into the unit. I personally experienced this until eventually upgrading to a higher quality 5v power supply. I would recommend making this an optional add on.
As someone who does not have a 3d printer, I would be someone who would be interested in one of the new enclosures.
Any chance the LED strip can be populated with square or rectangular LEDs, so the bar-style display can appear more ‘fluid’ (or is that entirely up to the constructor)?
Adding my vote against bundling USB cables or power supplies with the kit, but of course they’d be welcome as an optional add-on.
Does the new PCB address the issue with the AG using IO pin D4 and flashing the on-board LED intermittently?
- G.
As someone that just built one of the current DIY kits I have a few comments.
I like the idea of a better case. I was unable to get a good print for the temperature sensor extension.
I like that the components will not need to be stacked.
I did like the breakout holes on the older board, but they didn’t have proper spacing, so the headers included in the kit could not be used.
I tried the SPG30, but had problems getting readings from it (as others have mentioned in the forum). I swapped it for a Bosch BME688 (adafruit module) which seems to work fine.
From the pictures, there don’t seem to be vents on the sides where the CO2 sensor goes. Cross air flow might be nice and not really impact the case look (maybe your engineering has shown it not necessary).
I would like the LED lights/bar to either be optional or software controlled so it can be turned off. Personally I think the OLED communicates enough without being distracting.
Looks good.
Good points with the breakout pins and proper spacing.
Our enclosure was designed to create a chimney air flow in order to get the most accurate readings at the bottom of the enclosure where the temperature sensor is located. We experienced with side vents but that did not bring any additional benefits.
We also looked at the BME680 but found it to substantially overstate the temperature. Did you compare your readings to a reference thermometer?
One other small bit of feedback, is it perhaps possible to design the board with onboard temp, humidity, and VOC? As in actually part of the main board instead of using modular sensors?
I know that means assembly then becomes just the Wemos, LCD, and PMS.
I’m also aware that removes the ability to change the sensors easily, and may conflict with the idea of “DIY”, so perhaps a bit controversial, but if the sensors were positioned for accuracy perhaps people wouldn’t be interested in using different kinds of sensors if the readings from the onboard sensors “just work “
@brianFromNyc I used the PMS5003T on my build which also measures temperature and humudity. The PMS5003ST can measure temperature, humidity and VOC. The only “issue” is the price. The cheapest I could find, was maore than double the price of the PMS5003. The PMS5003T is slightly more expensive but cheaper than the PMS5003+SHT31.
I am running with both the SHT30 and the BME688. Here are some comparisons:
2 days
1 hour
I have not compared these values to a reference thermometer yet.
The BME688 values are using the “compensated” temp and humidity values. I haven’t looked at the “raw” output yet.
Another question regarding the new enclosure just popped up in my head:
Do the (two horizontal) mounting holes of the new case by any chance have the same spacing as the current case? This would prevent me and others from having to drill new holes for a wall mount. I realize that this might not be a big deal for some people but since I currently live in a rented apartment with no clue about what’s inside the walls, I try to keep my drilling activities minimal.
It looks like the BME is consistently higher than the SHT which is similar to our observation. It would be great to see the comparison to a reference thermometer if available.
it will have different spacing but the new enclosure should fit above European and US junction boxes and the spacing of the screws should just fit to these junction boxes.
Mounting the SHT and TVOC sensors directly would probably not make much difference from soldering a module on the same spot. However it is something we look into in case we will offer a pre assembled kit.
I can’t speak for all users, but personally I use AirGradient so I can get data into Prometheus. The DIY portion for me is because it’s the cheapest way, and I have the skills for both programming the Arduino and soldering the kit.
If there was an affordable way to get accurate air quality data into Prometheus, for instance a preassembed Wemos or Lolin D1 with accurate sensors, I would use that instead. Bonus points if it functions as a Prometheus metrics endpoint without me having to flash it.
I like the look and the optional headers for other sensors. I’m on board!
