This board supports 3 different radios (beside the onboard WiFi, ESPnow of the ESP32): RFM69, RFM95, CC1101, so it can be used as mySensors gateway, mysensors node, Homematic etc. and it has a mySX connector.
So, while here I've decided to close my TODO list. The revision 1.4 is likely to be the last chapter in this design, and now it can be considered safe to order. It introduces some important final touches to the board, in particular:
The orientation key (diameter 2.1mm) on the board edge. It's located between the Tag-Connect and the board main area, and initially can be used as an eyelet. After the Tag-Connect removal it works as an orientation key for the board.
Full rework of the silk layer. Just to mention few: I hid all designators and decorated the board with eye catchy "52" over the nRF52 MCU, touched the antenna outline, and moved the git hash to the mainland.
Review and cleanup the ground plane. The changes were tiny so it shouldn't detune the antenna, but aesthetics were definitely improved. You may also want to order the board in Afterdark colors now:
Have fun!
@zmatokan said in NModule:
@Nca78 Are you still working on this pcbs? i think it would be great to add a version that supports HiLink 220ac->5dc module on powerboard.
No I'm not working on NModules anymore, I have a few old nodes using atmega/nrf24 but I switched to NRF5 for "basic" nodes now, and to ESP32 for more "advanced" stuff.
NModule was designed for beginner and simple/riskless use, so I don't think adding high voltage option is a great idea, it's better to use an external power supply and connect the output to the powerboard.
I recently build successfully a mysensor node based on an Arduino Uno, a Robolink IR sensor and a Robolink DHT11 sensor. The last two from an Elektor sensor kit ever bought for my son when he was still interested by electronics .
My controller is Home Assistant, so I did a merge of the given MySensors example sketch and the Home Assistant example sketch together with the DHT11 sketch.
The airco is a Samsung one, so in the sketch you will find these defines uncommented. Replace by your airco manufacturer.
People interested in building one, can find my sketch on https://github.com/ericvb/MySensorsArduinoSketches
@ToniA a big thanks for the work to decode all these IR sequences!
@berkseo
Yes, it's available here. The documentation is a little bit scarce I admit but if you understand Apache MyNewt and its build system it should be pretty straightforward theoretically.
I will add more details when I have the time. The code was tested and it's in production. Works without a glitch so far.
You may be unhappy with your circuit at the moment, but to my eyes it looks like you've got some traction and you've made a good start.
@Mishka said in The Harvester: ultimate power supply for the Raybeacon DK:
I haven't bothered to find the low leaking MOSFETs and chose something small, handy to solder, cheap, and in stock. That turns out to be power MOSFETs in PowerPAK SC-70 package from Vishay. The nomenclature is SiAxxxDJ where the xxx is what you may see in the circuitry below. For example, 421 stands for SiA421DJ.
Not sure if what I'm finding out about my Vishay SiRA80DP mosfet might be similar to your Vishay mosfet, but I'll mention it anyway as a possible "heads up": I'm finding evidence of a pretty wide discrepancy between Vishay's SPICE model and what's physically true by measurement. Although I don't yet have a picoammeter (I'll be building one soon) for a more definitive test, I was able to do a relevant measurement with the voltage follower I built (see picture in previous post). The test circuit, to indirectly compare leakage of two different mosfets, was this:
If the mosfets were ideal and there were no leakage in either mosfet, then presumably the voltage measured at VF1 and VF2 would both be 3.3v. But, of course, they're not ideal: simulation shows that VF1 would be 3.12v an VF2 would be 1.59mv. I built the circuit and the actual measurements, taken with my voltage follower and a DMM, were almost the complete opposite: VF1=280mv and VF2=3.01v. i.e. the Vishay mosfet measured as far more leaky than predicted by TINA TI spice simulation of Vishay's SPICE model, and the other N-Channel mosfet (one of two mosfets on Diodes Incorporated DMC2700UDM-7) measured as far less leaky than predicted. It's a very easy test to perform... ahem, that is, if you are in possession of a 10 gigaohm resistor and a buffer (voltage follower) with a picoamp input bias.
Edit1: Come to think of it, a better way to test would be to use no resistor and just measure how much leakage there is with the gate set to GND. The leakage would likely be in the nanoamps, so it could be measured with a uCurrent Gold, or equivalent, which maybe you already have in your possession. Setting the DS voltage to whatever is listed in the datasheet for the leakage value would then give a number that can be directly compared to the leakage entries in the datasheet. Much easier and doesn't require high value resistors or exotic buffers! Obvious in retrospect. May or may not require a picoammeter, depending on the mosfet. To cover all the cases, I'll try these measurements after I build my picoammeter (soon!). I'll be building the inexpensive picoammeter designed and already vetted by an EEVBlog user named "Gyro":
https://www.eevblog.com/forum/beginners/static-control-requirements-for-picoamp-measurements-using-ucurrent-gold/msg3068708/#msg3068708
For anyone interested, you can find photos and all the details here: https://www.eevblog.com/forum/projects/picoammeter-design/msg790045/#msg790045
Rather than reduced to a nice simple PCB, the critical parts are air-wired, which is deemed the superior method according to the op-amp's datasheet. In addition, to better ensure accuracy, the DUT and all the measurement instruments should be enclosed together within conductive shielding as a countermeasure against external interference when measurements are taken.
