@fossiloaklists , this is odd, nevertheless let’s see what’s going on.

Try to connect to the local hotspot, then after it is connected, do a ping to 192.168.4.1

Please attach a screen shot with what you are getting.

Thanks!

Hi guys, sorry for the late reply, I’ve been travelling for most of September,

Please use only the server values, visible on the dashboard or returned by the server API, as those are further compensated to correct issues related to internal heating that affects temperature and humidity readings.

Although all units are calibrated against a common reference, there is a software interface in place that can be used to do additional adjustments where needed. We can apply this to any discrepancies in the returned parameters when compared to other equipment.

Country for E7 and E2 is set to AU.

For the 820000FA, please do a new test for Temperature and Humidity and let me know if you need any offset to be added. Again, make sure you are using the server returned results, not the local json. From you last post the correction would be T:-3.8 and H:+8.83
The CO2 sensor has an autocalibration algorithm, that triggers every 24h. Most likely the readings will be correct.

The VOC AQI algorithm has the purpose of providing comparable readings between the various MOX sensors used in the A3 units. It is very similar to the one developed by Bosch for their BME680 sensor. It uses the last 24hours of VOC raw readings to establish a minimum and a maximum, and then the readings are computed as a percentage scaled on the 0 to 500 interval. If you saw a big change it was due to a new 24hours interval introducing new min / max values to the calculations.

Hi there, and welcome! Go for a few A3 units, they are very cost effective detectors that you can use for your pilot!

Hi @domene, I just fixed it:

The Wifi module was replaced, there’s a new VOC sensor as a little bonus, and the firmware was also upgraded to the latest version. The PM2.5 sensor has also been replaced with a new one.

Will ship it back to you soon,

Radu

Hi Sam, for lowering the frequency there are no issues other than entering the audible spectrum. I can confirm your results here.

Please note that the voltage regulator algorithm thinks that with increased duty cycle there comes increased voltage. If you’re seeing serious swings you might need to change it.

The tubes well shielded by design in regards to RF, but the counter circuit (PCB traces, components) are not. But I don’t think the high voltage inverter is of concern here.

Having two units is definitely the way to go here, and try to get the Ethernet running so you can automate the process.

Good luck!
Radu

Hi @Sam,

Indeed the MPSA42 and the 2.2mH inductor are critical in terms of quality. But I wouldn’t blame the Chinese channels. After all, everything is made there, just be careful when you select the goods and the provider.

Please increase R1 from 100 to 1K and R2 to 47K.

What duty cycle does this give you? NExt try to change the frequency, in inverter.h, in the code. Try to reduce it by 1kHz until down to 10kHz. What do you see?

Here’s a nice chart I made from a similar circuit: https://www.pocketmagic.net/global-radiation-monitoring-network/#131005

Please try the new firmware I sent you before anything else.