@yoonie said:
For the pro mini version, should i create another Openhardware project, or should i put it here, in the already existing project?
Might be better to create a new project as they uses a different set of design files.
Yes. Correct. call BME.begin() every time and the subroutine only at the beginning.
And you are also correct about the library. I use the "blue" lib, from Sparkfun. As i can recall correct (it's been over a year since I built the damn thing) I have tried both, and found the Sparkfun more stable.
And you CAN switch off power for this module, but after conversion it goes to sleep and uses less than 1uA. Hardly worth the effort, because the current can find a way over the data lines, and that's a pain in the behind to solve (I tried!).
Nice project
manufacturers datasheets, RF appnotes etc all mention this, with results for different usecases (like gnd plane size etc). I mentioned it a few times on the forum:
nothing under or near antenna (keep out zone)
their matching circuit, and CE/FCC certif are based on their development boards+their antenna if external, often without enclosure.
there are a very few pcb antennas which are resilient to untuning. ceramic or meandered pcb are usually more compact but less resilient (like when you approach your hand and device suddently has better or worst communication)
once you change any of these parameters (board shape, gnd size, enclosure etc), it breaks FCC, and may need retuning, still you can get useable range.
"ideally" tuning should be done once enclosed for example. manufacturers can't cover all cases.
on my side, I try to follow these rules. and when interested in a design or a device, I check this. Mainly the routing+gnd, antenna choice, keepout zone, and orientation vs my usecase (long range needed or not for example)
