What did you build today (Pictures) ?

[dbemowsk]

@tbowmo With the 4 recessed indents on the plate, it centers the tool being mounted pretty good. I have printed a number of things with it since the upgrade and haven't had any issues with it yet. The Makerbot Replicator series of printers use a similar way of attaching their Smart Extruder heads with the 4 magnets in the corners.

One difference between the Makerbot extruders and my setup is that the Makerbots put their extruder stepper behind the hot end assembly and that mates to the motor with a castle nut type assembly.

My setup uses a Bowden extruder setup that is mounted at the top of my enclosure.

With no stepper on my hot end, that takes the majority of the weight off of the carriage. This is one of the first tests of the 3D printer head.
3D printing tool test – 02:09
— Dan Bemowski

[tbowmo]

@dbemowsk

One extra question, what type of filament did you use to print the adapter plates in?

[dbemowsk]

@tbowmo All the parts are in PETG. I got the 1kg roll cheap on Amazon for $12 US with prime shipping.

[dbemowsk]

For anyone interested in my 3D printer mod for using different tools, I posted it on thingiverse.
https://www.thingiverse.com/thing:3407486

[acb]

Built a 1284(p) into a 328p Pro Mini footprint. Not sure what to call it, a Pro Mini XL maybe?

I now have x4 the program memory (128K vs. 32K), x4 the EEPROM (4K vs. 1K) and x8 the SRAM (16K vs. 2K) all in a 328p Pro Mini pin-compatible (I think!) footprint of about same size.

I can also run at 20MHz vs. the usual 8MHz provided I’m prepared to run it at 4.5v and above.

Had to sacrifice a few pins and components, but might be able to put various selections back in future revisions. Nothing major (in my opinion) just components associated with the regulator really. I also went for a crystal (not installed yet, on order, LEDs too..) over a resonator - just a personal preference for when timing is critical.

And yes, those are 0402 SMDs. I actually did them by hand (!) with a microscope and a judicious amount of coffee; a fine-point iron, solder wick and flux became my best friends.

So far, I’ve had it working with nRF24s and RFM69s radios, ATSHA for personalization and external flash for FOTA. The DualOptiboot bootloader code and makefile needed a bit of tweaking, but nothing major.

I broke out the JTAG I/F but haven’t played with that yet and also added power pins next to the I2C to make some of the sensor modules (like SI7021) pluggable - see below.

I also want to play with the QTouch library support for built-in capacitive touch buttons, sliders, etc.

Why not just go with an ARM (STM32, SAMD, nRF52)?

I’m working on it! ;o)

Am not wanting to start a(nother) 8-bit vs. 32-bit discussion. I’ve got an AliExpress package of 32-bit MCUs coming (very) slowly to me. When it arrives, I’ll start experimenting and exploring - probably with the nRF52s, since those seem to be the flavor-of-the-month and very capable-looking chips...

But until then, I need more program memory!
(Among other things…)

[alexsh1]

Finally finished building my dual precision voltage reference LTC6655:

[alexsh1]

@acb I have built similar board.

The only downside is the cost and size of Atmega1284p is just so prohibitive. Yet it is 8 bits processor. I have only one fully conpleted board and a few blank pcbs.

[acb]

That looks awesome @alexsh1!

Nicely laid out and cleanly soldered. Was that with an iron or hot air (or both)? Nice clear silk too; I like the power and “signal” symbols. Did you ever try a FOTA update with it? Or a low power/speed profile?

I see you went a bit wider and longer than the standard Pro Mini, (I’m assuming) to get at all the pins and add the extra regulator, LEDs, etc.

I was constrained by needing something that fit the same footprint for existing boards I already had, e.g. other “motherboards” I’d made similar to @sundberg84’s excellent Easy/Newbie PCB or wanting pin-compatibility for stacking boards like the ATSHA+EEPROM+Radio+ICSP one below:

I tried routing with the chip at a 45 degree angle too but couldn’t get a DRC to pass with the pads so close to the PTHs. I may try again with shorter (custom) TQFP pads...

Re: 1284p’s downsides of cost and size.

I know. I ended up justifying it to myself this way:

We can all get cheap 328p Pro Minis from Ali for around $2. The vast majority of my Pro Mini projects are battery powered, so there’s some “labor cost” to disable the power LED and remove the regulator. But regardless, I certainly can’t make myself a low(er) power Pro Mini for $2 - the OSH Park PCB alone is probably close to that.

I think the cheapest I ever got 1284p chips for was around $2.50, again from Ali. My “Pro Mini XL” PCBs were around $1.70 from OSH Park, add a sprinkling of 0402s, etc. and we’re probably at around $5.

I couldn’t find any 1284p-based boards near that price. The closest I got was Kevin’s Mini Duino, which is another lovely looking board, but doesn’t fit my need for a Pro Mini-constrained size and pin-compatibility. Essentially, I was after something close to a drop-in replacement.

So, $2+ versus $5+ for all the benefits (at least as far as I was concerned) listed above? It became a bit of a no-brainer.

And on the low power front, I profiled the MySensors library sleep command on it at around 5uA on 4.5v @ 20MHz using an external full swing, around 4uA on 3v @ 8MHz and around 3uA on 1.8v @ 1MHz Internal RC Osc:

Those numbers are certainly good enough for all my current applications - no pun intended!

But I would like to look at the 32-bit contenders as potential replacements.

I’ve seen nRF52s with 512K for around $2 on Ali, so maybe I’ll try my hand at a Pro Mini nRF52 or something similar eventually. The board above was a fun challenge, and afterall is what this is (mainly) about for me.

[dbemowsk]

@acb Nice pro mini sized 1284 boards. These would work nice in my in-wall OLED scene controller boards. The standard 328 pro minis really limit what I can do with the OLED display when using it with the MySensors library. I could get more use out of the graphics end of the display with something like that.

Do you have these on OpenHardware.io? Can fully functional boards be purchased somewhere? I would be interested in trying a few out if possible.

Kudos on the design.

[acb]

Thanks for the kudos, @dbemowsk. Right back at you for your scene controllers; I’m trying to get into 3D design myself, but can’t justify the time commitment right now.

Re: Do you have these on OpenHardware.io?

No, sorry, that would require me to be far more organized than I am at present!

Maybe if there was enough interest, I could justify putting in the time to clean things up enough to publish… But it is valentines today, so any tinkering will surely be met with an icy stare if I try it tonight!

Re: Can fully functional boards be purchased somewhere? I would be interested in trying a few out if possible.

Really? I’ve never done something like that before. You do realize these are very much “alpha” right? I mean, I’ve tested the majority of the pins, but nothing like proper production hardware verification or anything. Having said that, it’s not like there’s anything complicated going on.

I managed to dig out four spares this afternoon that I’m not using from the last batch I made - how many would you like?

Three have a 1284p attached and one has the regular 1284 - I believe the only difference is the 1284 doesn’t have BOD, but I normally turn that off anyway for a (probably) miniscule power saving. I haven’t installed the crystal oscillator or reset switch yet. I don’t normally do that until I know what the use-case is. I believe I have enough spare 16MHz and 20MHz ones to fit (maybe some 8s) and some SMD reset switches too.

The only other thing would be the bootloader. I could flash the standard MySensors DualOptiboot?

So, if you (or I suppose anyone else for that matter) are interested, just shoot me a chat message via my profile and we can figure things out off-thread, as this is a bit off-topic now.

Thanks again for the interest - even if you don’t buy - made my day!

[kalina]

Some photos of my new device - MDMSPanel "Nextion". I have finished soldering an hour ago)) Next week i will public this project.

[bjacobse]

@kalina
Looks good, however due to EMC I strongly recommend to add a GND groundplane on your PCB. I would myself have TOP layer as +DC and BOT layer as GND, this provide less power "sparks" on the tracks and a "capacitor" effect on whole PCB

https://en.wikipedia.org/wiki/Ground_plane#/media/File:TerraTec_G3_circuit_board_2.jpg

https://www.quora.com/What-is-the-importance-of-a-ground-plane-of-a-PCB?share=1

[mfalkvidd]

@kalina very cool board. Must be your most advanced MySensors board so far?

[kalina]

@mfalkvidd I would to say what this board is the most necessary for me at the moment. I tired of using various gadgets as a control panels for my nodes. Also, i want to try RS-485 in conjunction with MySensors. Next step is add RS-485 to my MDMSGate....

[monte]

@bjacobse to do proper ground and vcc planes you need a 4-layer PCB. Otherwise you won't get much of a difference in terms of EMI. Another way is to have 2 layer board and to have one layer only for ground plane, but that means you have to do all routing on one side, without making lines across your ground plane. Otherwise you decreasing grounding effect on EMI.
More on this topic in this free webinar: https://www.signalintegrityjournal.com/events/54-best-iot-board-design-practices-balancing-density-cost-low-power-and-mixed-signal

[bjacobse]

@monte
Well now Kalina already uses 2 layer PCB, so to improve current 2-layer PCB with ground planes are strongly advised.
Yes 4 layer is naturally much better, but is it needed for a "commodity" device? I think not, and it will increase PCB cost...

If you don't have a GND and power planes, you will most likely have power spikes when an IC needs current, this will introduce a magnetic field that will "disturb" especially sensitive analogue tracks and clock signals

[FotoFieber]

My actual project is a doorbell sensor with additional temperature and humidity sensors. Tried different ways to detect the ring:

• hall sensor (failed)
• microphone (FFT, ongoing research)
• optocoupler to detect the 12V AC -> favorite solution

As I was heavy prototyping, I tried wire wrapping and it is fun:

[alexsh1]

@acb Hot air has been used for soldering the board. I have not tried low power as I did not build this board for a battery sensor. My board has got two LEDs - power and another LED connected to D0 so clearly not very low power. I also have a 16Mhz firmware. I did not have any size limitation either. I have one particular node with a few sensors and with signing I cannot upload the sketch onto ATMEGA328P as it is marginally larger. Having said that I have not spent too much time optimising the sketch. I think that refactoring libraries, you are fine with ATMEGA328P in 98% of all MySensors applications.
BTW - this is not my project. I have followed it https://github.com/peekpt/mightyduino

Re cost. I stopped Ali shopping for ICs and other sensitive components some time ago after purchasing some fake ATMEGA328P and wasting so many hours trying to troubleshoot it. There is a post about it here on MySensors forum. Ever since I order all components on digi-key. 1284p is priced around $5 + 20% VAT. 328P is priced at $1.2 + VAT. However, I can also buy ATSAMD21 for $2.2 + VAT. Do you see my point? 1284p is extremely expensive and yet it is still 8 bit processor. That's why for me it was a one-off board.

Re sleeping
I am using TPL5110 which I built myself (similar to Adafruit one).
Check out sleeping current:

Sadly, I struggled to get some sensors to sleep properly - probably lack of my programming skills - and with a sleeping current being hundreds of uA, I had to resort to this trick. Most of the time, the node sleeps is disconnected from power by TPL5110 then timer is up and it powers up, sends all sensors readings to the GW and then power gets disconnected to the node, only TPL5110 goes to nA sleep. Perfect!

[alexsh1]

@kalina scene controller? I have almost finished mine on Nextion, but do not have time to tidy things up.

[kalina]

@alexsh1 Yes, it will be a scene controller. I also developed nice enclosure with a magnetic mount. In a few days I will share new photos.

[monte]

@bjacobse but it actually seems that he HAS a ground plane on one side of PCB, if you look closer at the third photo

[bjacobse]

@monte I didn't notice this, but you are right, "hidden" LCD

[bjacobse]

@fotofieber
Wirewrapping is an "old" and well proven technology, remember to have extra cable in case you need to re-wire your cables. Not so popular by DIY as tools used to be fairly expensive as it was protected by patents...

[bjacobse]

@bjacobse
Just to add a little more info about adding a GND plane to your PCB
I work in a electronic company, not doing PCB layout there though.
but we have a TV adapter which have 2.4GHz transmitter. and this PCB is GND on both sides and with plenty GND via's (all the small holes) to ensure good grounding

In case you wonder what it is, then it's an Oticon TV adapter 3.0
Clear Opn pairings with TV Adapter 3.0 – 00:34
— Oticon USA, Inc.

[alowhum]

A picture from the touch screen version of the universal 433Mhz signal cloner.

[kalina]

I have finished an enclosure for the my MDMSPanel "Nextion" today.

[alowhum]

Wow, very cool! Can you share a bit more about the project? Is it MySensors based? Is there code available? What does the hardware inside look like? What processor is it base on?

Ah, scrolling up answered some of my questions

[kalina]

@alowhum Yes of course. I am going to publish this project this week.

[dbemowsk]

@kalina Kudos on the case. Is that a case you designed, or is it a prefab case that you bought somewhere? I am assuming that from the markings inside the case that it is a prefab.I do like the design though and love it's underlying project. Is that just a thermostat, or is it a multi option controller?

[kalina]

@dbemowsk Yes, it is a factory case, and before the changing it looked like this :

At the moment this is termostat, but I will not limit myself to this)) The purpose of the panel will be determined by the software project loaded into it. I will describe this in more detail when I publish the project.

[bjacobse]

@kalina
Yes it's very impressing what you have achieved

[dbemowsk]

@kalina I like that case design so much that I may design one like it in OpenSCAD and post it on thingiverse.

[kalina]

@bjacobse said in What did you build today (Pictures) ?:

Yes it's very impressing what you have achieved

Thanks, the project is published already.

https://www.openhardware.io/view/676/MDMSPanel-Nextion

[FotoFieber]

Building a (xenon) flash to notify alarms. Flashes every 5 seconds if activated.

[sundberg84]

[sundberg84]

Today I made a iscp pogo pin adapter... Great for uploading bootloaders.

[berkseo]

Almost finished one of my projects. The test sketch showed that HW works as it should. Now i need to make good software.

Mysensors Plant Watering Sensor on nRF52832 | not just MeSensors :) – 00:28
— Andrew EfektaSB

[Omemanti]

@sundberg84 that board looks nice and crisp

[berkseo]

Birth of water leakage sensor:) on mysensors..
Mysensors | Water leak sensor | 20 years of operation – 01:45
— Andrew EfektaSB

[Omemanti]

After months of slow painstaking work (day job is somewhat busy, o and the kids ) I finally completed my Domoticz server(case) with Dashticz as frontend.

The Endgame; when my new house is finished every room is monitored for motion, RH and Temperature using my MySensors PCB's. (Jung AS500 Node)

Everything is monitored using a raspberry with a MySensors serial gateway (NRF52) and an RFLink controller for my KAKU switches.

To make everything nice and shiny I use Dasticz to interface the data in a proper way using a tablet that somehow will be mounted on a wall or something.

So far the introduction;
To put everything away nice and tidy I used a box to install everything using 2 pieces of din-rail.
It has a 230V inlet that is converted to 5V using an off the shelf (safety sake) MeanWell RS-15-5 converter. This powers everything using a couple of din-Rail terminals.

• Terminal => USB-micro => Raspberry
• Terminal => just a couple of wires => old nrf52 prototype => FTDI => Raspberry
• Raspberry => RF-link (ard. Mega +433mhz)

Since the Raspberry has Wifi no other cable then power is needed to operate

Second part: the 2 screenshots of dasthicsz.

The best part, it took some work, but the WAF incread big time, because everything looks clean

[dbemowsk]

@omemanti Nice DIN rail enclosure.

[Omemanti]

@dbemowsk

If someone would be interested:
Enclosure
Ard. Mega enclosure
Raspberry enclosure

Had to do some modifications for the mega, but the cost of this enclosure was more than worth it.

Hmz.. normaly don't buy stuff at conrad but apparently they have good prices on cases...

[monte]

@omemanti well...enclosure at a price of 3 raspberry pi zero. Good price indeed

[sundberg84]

[Honk]

Nothing fancy. Got my new ts100 today and I pre-soldered some V10 easyPCBs with 3.3v Arduino pro minis.
The iron is pretty good. It is Louis Rossmann approved. Now I need a good 24V power source to drive this thing.

[FotoFieber]

Testing a CCS811 CO2 sensor. It seems to use less power then the MH-Z14A I am using now. The CCS811 may even run on battery. I will compare measurements of these two sensors with a Netatmo sensor. The sensors have to burn in for two days bevore I start the comparison.

The CCS811 breakout board I use hast temp, hum and barometer sensors (and the CO2).

[Nca78]

@fotofieber said in What did you build today (Pictures) ?:

Testing a CCS811 CO2 sensor.

Unfortunately this is not a CO2 sensor. It's only a VOC sensor giving an estimated eCO2 value. It's useful to tell you if your room needs ventilation, but not much more. And as even the VOC part is not calibrated it's only good for relative measurement.
AFAIK the only similar sensors which are calibrated and give absolute values are SGP30 and BME680.
If you want to measure CO2 you need a CO2 sensor and it's going to consume a lot of power, at least too much for a battery powered sensor.

[edit] there's also the MiCS-VZ-89TE TVOC sensor, they claim to have a curve of eCO2 not too far from NDIR sensor in their datasheet. But that datasheet is strangely poor in details, they didn't even put any electrical characteristics...
https://sgx.cdistore.com/datasheets/sgx/MiCS-VZ-89TE_V1.0.pdf

[berkseo]

My battery operated mini touch switch

[berkseo]

[sundberg84]

I don't think I ever managed to get it right the first revision.

[sundberg84]

But it's something...

[Nca78]

@sundberg84 you should print the board on paper, stick it on a piece cardboard and cut. Then check if size is good, you can even put the "big" components on it by sticking the pins through the cardboard to make sure you'll have enough space.

[sundberg84]

@nca78 great tip! But it's more common it's a schematic or footprint error. The outline "should" be the easy part even if I messed up.

[FotoFieber]

@nca78 said in What did you build today (Pictures) ?:

@fotofieber said in What did you build today (Pictures) ?:

Testing a CCS811 CO2 sensor.

Unfortunately this is not a CO2 sensor. It's only a VOC sensor giving an estimated eCO2 value. It's useful to tell you if your room needs ventilation, but not much more. And as even the VOC part is not calibrated it's only good for relative measurement.

My tests will show, how far away I am with this sensor in my indoor usage scenario.

My Netatmo sensors claim to measure CO2 and are battery powered. They seem to calibrate themselves to the lowest level they measure in 24 hours. This behaviour seems to be similar with the CCS811. The Netatmo sensors seem quite close to my MH-Z14A.

In the datasheet for the CCS811 I have read, that you can't use them in your green house, because of its self calibration. Netatmo may have the same restriction too.

AFAIK the only similar sensors which are calibrated and give absolute values are SGP30 and BME680.

I have ordered a SGP30 some days ago and will test it too. The BME680 needs binary code linked which is a no go for me. (As a gift I would take it into my test setup. )

If you want to measure CO2 you need a CO2 sensor and it's going to consume a lot of power, at least too much for a battery powered sensor.

The problem with high power sensors is, that they produce heat, which can make your temperature measurements unusable.

As my CO2 sensors have a color led to show air quality, they are mains powered anyway.

[edit] there's also the MiCS-VZ-89TE TVOC sensor, they claim to have a curve of eCO2 not too far from NDIR sensor in their datasheet. But that datasheet is strangely poor in details, they didn't even put any electrical characteristics...
https://sgx.cdistore.com/datasheets/sgx/MiCS-VZ-89TE_V1.0.pdf

Thank you for the link. I have ordered one for my test setup. They are really expensive, about twice the price of the MH-Z14A, the SGP30 or the CCS811.

Other CO2 sensors I should use in my test setup?

I like the MH-Z14A and depending on my tests may stay with them.

EDIT: ordered a MHZ-19 for the tests

[Nca78]

@fotofieber said in What did you build today (Pictures) ?:

EDIT: ordered a MHZ-19 for the tests

Make sure you order a MHZ-19B, it uses less power and has fixed an autocalibration problem.
SenseAir S8 has a better calibration process using several days, so if you don't ventilate your room during 24h it will not use a wrong reference level and report wrong values.

And about BME680 there are boards on AliExpress with included STM32 Cortex M0+, basically it's the same than the MiCS-VZ-89. Search for GY-MCU680V1.

[FotoFieber]

@nca78 said in What did you build today (Pictures) ?:

And about BME680 there are boards on AliExpress with included STM32 Cortex M0+, basically it's the same than the MiCS-VZ-89. Search for GY-MCU680V1.

Thx, ordered one on aliexpress. Hope I have time to test when they arrive...
EDIT: first results, hope CCS811 will calibrate better in the next two days

[berkseo]

All elements are assembled

Mysensors Capacitive touch glass mini switch on battery (nRF52832) – 01:56
— Andrew EfektaSB

[petewill]

@berkseo nice! What did you use for the capacitive sensor? MPR121?

[Nca78]

@petewill said in What did you build today (Pictures) ?:

@berkseo nice! What did you use for the capacitive sensor? MPR121?

TTP223s in top left and top right corners

@berkseo I'm curious about that, why not use the capacitive touch function of the NRF52832 ?

[berkseo]

@nca78 said in What did you build today (Pictures) ?:

TTP223s in top left and top right corners

yep

[berkseo]

@nca78 said in What did you build today (Pictures) ?:

I'm curious about that, why not use the capacitive touch function of the NRF52832 ?

Ttp223 chips suit me. Very stable stuff. When I tried to do it on amtel328, these mcu also had this feature (almost all mcu have this feature). But it was not very stable. I'm not sure that a stable device using the mcu 52832 would be possible. If there is an example of a stable software implementation, I would be happy to test it, and then it would be clear to do it without external capacitive chips or not.

[mfalkvidd]

My new workbench is coming along nicely.

[mfalkvidd]

Top shelf is for network stuff

[zrom69]

@mfalkvidd good job

[acb]

Continuing along the theme of one of my last projects, I built a nRF52832 into a 328p Pro Mini footprint. Made two versions: One with some edge SMA or U.Fl pads and another with a PCB trace antenna:

I wanted to start getting into using 32-bit microcontrollers (ARM Cortex varieties like nRF5x, SAMDs, STMs, etc.) for some more complex HA and other electronics projects and am trying to ease the learning curve from all my 8-bit ATMEGA experience.

Keeping the 328p pin-compatible footprint and PCB size means I can still reuse most of my other Pro Mini project boards to get going. An added bonus is the nRF52's ability to remap (almost) any pins, which will no doubt come in handy.

They’re both two layer boards and I get pretty decent range out of the PCB trace antenna - ever so slightly better RSSI than EByte’s E73-2G4M04S1B, which was surprising since I didn’t really do anything different (that I’m aware of) and their module is shielded too.

Since there’s no need for a separate nRF24 board and other associated components, like external SRAM or ATSHA, it’ll possibly save me a few $ too! Power pins next to the (remappable) I2C pins make some of the sensor modules (like SI7021) pluggable.

I also gain 16x the program memory (512K vs. 32K) and 8x the speed (64MHz vs. 8MHz) which is no small increment!

Some of the project boards I have made use of the Pro Mini 328p’s FTDI pins, so I added a few components to enable the use of an FTDI programmer with custom DFU serial bootloader.

Basically, a DTR pin toggle from the FTDI will reset the nRF52 into a state where it’ll briefly listen for a new program - similar to Adafruit’s Feather. You can also force that state for a longer period with a combination button press like Nordic and SparkFun’s development boards.

I’m unfamiliar with SWD/JTAG programming/debugging and all things GDB/OCD, so I built myself a black magic probe out of a STM32 blue pill and am going to have a play with all of that, along with VS Code and PlatformIO and probably one or two others.

MySensors nRF52 support worked out of the box (!) - so a huge thanks to all the hard work of the folks round here for getting that up and running. If there’s anything I can help with there, please let me know and if I’m able, I’ll try to take a stab at it (OTA maybe?). Like I said, I’ve got quite a steep learning curve here though.

On the low power end, I added the DCDC components Nordic recommend too and managed to get the MySensors smartSleep() current down to around 0.7uA - as per the datasheet, I think. However, I found that with a couple more code tweaks and grounding the SWDCLK, I would get into the nA region. This seems a bit out of spec to me and perhaps it’s just a measuring error, but it was repeatable and the board still happily sending data/heartbeat again each time it woke up. (It’s fluctuating around 1.6nA below - no sensors connected though, but it’s a start…)

One other project in the back of my mind is using this board as the basis for a quadcopter, but that’ll probably have to wait until the summer holidays…!

[nagelc]

@acb Nice! I have serious board envy. I really like that clip on programmer too.

[monte]

@acb have you written a bootloader yourself, or found already available? Can you tell more about it and a board you using to connect nrf52 to FTDI?
Nice work!

[Fanfan]

Well,in my case, I mounted and tried to fix bugs in my very first design. This is supposed to be a castelizable Sensebender compatible node, embedding NRF24L01+, LED, Temp/Humi/Press sensor, Memory, crypto, with most of the IO exposed. The updated design is online, but still work in progress.
project on OpenHardware

[berkseo]

@acb Wow. Awesome

[berkseo]

My light sensor on the window. Will work as a slave device for the curtain controller.

Mysensors Light sensor (LUX) on nRF52832 | First HW&SW test – 01:46
— Andrew EfektaSB

[sundberg84]

New gateway going live and migrating slowly from Domoticz to Homeassistant. At least to try it.

[acb]

@nagelc Thanks! The clip on programmer is one-part Adafruit’s FTDI “Fiddy” from here, and one-part SparkFun’s old (retired?) 3.3 or 5v selectable FTDI programmer with a custom 3D printed enclosure.

I plan to modify the “Fiddy” design a bit as there were some elements of it that I’ve found a bit frustrating. However, YMMV. Gotta love pogo pins for programming though…

Re: Board envy. Really? Well, if you like, I could do what I did on my last project - which was selling the leftovers. At the moment, I always make more than I need, for testing and some much needed practice with the smaller 0402s. Just send me a chat message if you (or anyone else?) are interested.

[acb]

@monte Re: FTDI Boards & Bootloaders.

I didn’t write the bootloader myself from scratch, but modified and combined various elements from Nordic’s SDK v11 example, SparkFun’s development version and Adafruit’s Feather version.

It was quite a nice learning experience of hacking in bootloader land and dealing with event-driven architectures without any low level debugging skills (yet!) - that’s why I’m now trying to get into SWD/JTAG debugging to make things like this easier.

I certainly don’t understand everything that’s going on, but “loosely” from what I can figure out, it uses Nordic’s proprietary SoftDevice (S132) combined with some custom bootloader code to boot into a predefined state, where it’ll wait for new “image” either over a serial or bluetooth connection.

The new “image” can be either your regular sketch-type code (referred to as the “application”), a new SoftDevice (S212, S332, etc.) and/or even a new bootloader.

Once the new “image” is received and validated by the (existing) bootloader, it is copied to replace the existing “image” parts where necessary and the chip is reset.

Nordic’s pc-nrfutil command line utility handles interfacing with any standard FTDI board over a COM port (mine is an old SparkFun, but any should work) to perform the upload.

In SDK11, there isn’t much in the way of safeguards, but in SDK15 there are things like cryptographic signing, custom initialization packets and protocol buffers, etc.

I did have to make one tweak to the nrfutil Python code, to make it wait a little longer after opening the COM port before sending the DFU initialization packet. This might be unnecessary with optimized bootloader code, I don’t know, since the nRF52832 boots pretty quickly.

I could go on, but I’m still learning myself, and so if you or anyone else has any other questions, comments, suggestions, etc., perhaps we better move them to a new discussion thread? (Just tag me in so I see it…)

Thanks for your interest though!

[acb]

Very nice @Fanfan!

Love the power protections - those would have saved me a few nRF24s in the past!

How have you found the ceramic antennas?

I’ve been wondering whether to add pads to mine for experimenting...

[acb]

Thanks @berkseo!

Have been enjoying your work with nRF52 designs.

Also on my list is trying the built-in capacitive touch capabilities of the chip.

I can @ you if I get anywhere with it - might come in handy for your capacitive touch glass mini switch to save you a few components?

[berkseo]

@acb Of course!!!, ttp 223 gives a reliable result, but if there is an opportunity to make a stable implementation based on the chip itself, then definitely it needs to be done. I would appreciate any help and advice.

[monte]

@acb we can continue discussion in this thread, If you want: https://forum.mysensors.org/topic/6961/nrf5-action/

So as I understand for now you are using native SDK and not using Arduino and mysensors? As far as I know arduino's core for nrf5 has no support for bootloaders, and mysensors conflicts even with softdevice being present on a chip. And it seems that sandeepmistry (author of the core) isn't going to invest his time into writing bootloader and can't use nordic's one because of license. I would like to have a bootloader solely for bluetooth OTA programming for projects beside mysensors. Maybe you could share your work, and/or write some kind of brief tutorial on where to start working on this subject maybe to avoid problems you have already solved? Anyway, great work from you, hope someday we will have mysensors on nrf52 with working OTA.

[fernando alvarez buylla]

well this is my project , right now im using 2 arduino nano with ethernet shield to read 3 lines Voltage on a delta instalation , 3 current sensors of 300amps for a motor , and 1 water pressure ,
all conected to a raspberry pi with domoticz

but yesterday i decide to change all , instead of 2 uno i will use a pro mini with a nrf24
so i desing two pcb

some code

#define MY_NODE_ID 100
#define MY_DEBUG
#define MY_RADIO_NRF24

#include <SPI.h>
#include <MySensors.h>  


#define CHILD_ID_VOLT_1 1
#define CHILD_ID_VOLT_2 2
#define CHILD_ID_VOLT_3 3

#define CHILD_ID_CURRENT_1 4
#define CHILD_ID_CURRENT_2 5
#define CHILD_ID_CURRENT_3 6

#define CHILD_ID_PRESION 7

#define VOLT_SENSOR_ANALOG_PIN_1 0
#define VOLT_SENSOR_ANALOG_PIN_2 1
#define VOLT_SENSOR_ANALOG_PIN_3 2

#define CURRENT_SENSOR_ANALOG_PIN_1 3
#define CURRENT_SENSOR_ANALOG_PIN_2 4
#define CURRENT_SENSOR_ANALOG_PIN_3 5


#define PressPin      A6 



unsigned long SLEEP_TIME = 20000; // Sleep time between reads (in milliseconds)

MyMessage msg(CHILD_ID_VOLT_1, V_VOLTAGE);
MyMessage msg2(CHILD_ID_VOLT_2, V_VOLTAGE);
MyMessage msg3(CHILD_ID_VOLT_3, V_VOLTAGE);

MyMessage msg4(CHILD_ID_CURRENT_1, V_CURRENT);
MyMessage msg5(CHILD_ID_CURRENT_2, V_CURRENT);
MyMessage msg6(CHILD_ID_CURRENT_3, V_CURRENT);

MyMessage pressureMsg(CHILD_ID_PRESION, V_PRESSURE);

float lastVolt1;
float lastVolt2;
float lastVolt3;

float lastCurrent1;
float lastCurrent2;
float lastCurrent3;

float lastPresion;


int pressure = 0;
float PSI = 0;
float PSI_CAL = 2.0;            // Calibration of sensor
int PSImsb = 0;
int PSIr = 0;



void before() {

}


void presentation()
{
 sendSketchInfo("Multisensor", "1.7");  // Send the sketch version information to the gateway and Controller
 present(CHILD_ID_VOLT_1, S_MULTIMETER);   // Register this device as power sensor
 present(CHILD_ID_VOLT_2, S_MULTIMETER);   // Register this device as power sensor
 present(CHILD_ID_VOLT_3, S_MULTIMETER);   // Register this device as power sensor

 present(CHILD_ID_CURRENT_1, S_MULTIMETER);   // Register this device as power sensor
 present(CHILD_ID_CURRENT_2, S_MULTIMETER);   // Register this device as power sensor
 present(CHILD_ID_CURRENT_3, S_MULTIMETER);   // Register this device as power sensor

 present(CHILD_ID_PRESION, S_WATER);   // Register this device as power sensor
 
}


void setup()  
{ 

}

void loop()      
{     
 int Voltaje1 = analogRead(A0);
 int Voltaje2 = analogRead(A1);
 int Voltaje3 = analogRead(A2);

 int Corriente1 = analogRead(A3);
 int Corriente2 = analogRead(A4);
 int Corriente3 = analogRead(A5);

 
 
 float VoltLevel1 = map(Voltaje1,0,1023,0,500);
 float VoltLevel2 = map(Voltaje2,0,1023,0,500);
 float VoltLevel3 = map(Voltaje3,0,1023,0,500);

 float CorrienteLevel1 = map(Corriente1,0,1023,0,200);
 float CorrienteLevel2 = map(Corriente2,0,1023,0,200);
 float CorrienteLevel3 = map(Corriente3,0,1023,0,200);

 
 Serial.print("Voltaje L1: ");
 Serial.println(VoltLevel1);
 Serial.print("Voltaje L2: ");
 Serial.println(VoltLevel2);
 Serial.print("Voltaje L3: ");
 Serial.println(VoltLevel3);


 Serial.print("Corriente L1: ");
 Serial.println(CorrienteLevel1);
 Serial.print("Corriente L2: ");
 Serial.println(CorrienteLevel2);
 Serial.print("Corriente L3: ");
 Serial.println(CorrienteLevel3);

 //sensor de voltaje
 if (VoltLevel1 != lastVolt1) {
     send(msg.set(VoltLevel1, 1));
     lastVolt1 = VoltLevel1;
 }

   if (VoltLevel2 != lastVolt2) {
     send(msg2.set(VoltLevel2, 1));
     lastVolt2 = VoltLevel2;
 }
   if (VoltLevel3 != lastVolt3) {
     send(msg3.set(VoltLevel3, 1));
     lastVolt3 = VoltLevel3;
 }


//sensor de corriente
   if (CorrienteLevel1 != lastCurrent1) {
     send(msg4.set(CorrienteLevel1, 1));
     lastCurrent1 = CorrienteLevel1;
 }
     if (CorrienteLevel2 != lastCurrent2) {
     send(msg5.set(CorrienteLevel2, 1));
     lastCurrent2 = CorrienteLevel2;
 }
     if (CorrienteLevel3 != lastCurrent3) {
     send(msg6.set(CorrienteLevel3, 1));
     lastCurrent3 = CorrienteLevel3;
 }

/* ************************************************ */
   pressure  = analogRead    (PressPin) ;        // junk read
   wait(25);
   
/* • Output: 0.5V – 4.5V linear voltage output. 0 psi outputs 0.5V, 50 psi outputs 2.5V, 100 psi outputs 4.5V 
   0   psi = .33v after scalling 5.0v to 3.3v
   50  psi = 1.65v
   100 psi = 2.97v

   3.3v/1024 = .0032266 volt per bit
*/
   pressure  = analogRead    (PressPin) ;

   if (pressure < 106) pressure = 106;         // this is minimum of .5v
   PSI = (pressure - 106 ) * .1246;            // where did we get this?? was .119904
   PSI = PSI + PSI_CAL;                        // adjustment
   
   PSImsb = PSI * 100;
   PSIr = PSImsb % 100;
   

   send(pressureMsg.set(PSI, 2));            // Send water pressure to gateway

   Serial.print("Presion: ");
   Serial.println(PSI);
   
   wait(200);
   
    // end of if (SLEEP_MODE || (cu

 
 sleep(SLEEP_TIME);
}

havent tested with sensors yet

but looks good so far

[berkseo]

Today, the first sensors of the devices were soldered, the prototypes of which passed long-time tests. Eliminated children's sores. In matt black they are good

[alowhum]

@berkseo whoa, time for a Kickstarter! They look great! Where did you have them made, and what do they cost?

@fernando-alvarez-buylla Always nice to see the Aurora theme being used

[fernando alvarez buylla]

And a few days later my pcb's arrived

Now to test the next version

[berkseo]

Hacking Redmond smart bulb socket RSP-202S

Mysensors | Hacking Redmond smart bulb socket RSP-202S – 02:42
— Andrew EfektaSB

on nRF51822...

[alowhum]

How did you 'hack' it? All I see in the video is you changing a power wire?

[berkseo]

@alowhum I replaced the manufacturer's software with my own.

The device now works on the mysensors network

[alowhum]

@berkseo very cool! How did you do that? Did you just have to connect the serial holes to an ST_LINK adapter or something similar? Was is difficult to open the device? And, most importantly: is your code available somewhere?

[berkseo]

Hacking Redmond SkyPlug RSP-100S

Mysensors | Hacking Redmond SkyPlug RSP-100S – 06:14
— Andrew EfektaSB

[berkseo]

@alowhum Kickstarter? I'm not sure it's time ..The cost of components is approximately $10. PCB made in China, soldered by myself.

[berkseo]

@alowhum Soon I will publish codes and the description of process of dismantling and a firmware. But getting ahead.. it's very simple

[FotoFieber]

Added two other (e)co2 sensors to my test-setup.
Now 3 NDIR and 2 VOC under observation.

[nagelc]

A family member gave me an old lamp with a fancy glass base. Well, I didn't like the lamp, but the base was nice, so I kept it in my basement for a few years. I found it again the other day and decided it needed to become a new type of lamp. I put a 150 LED strip (WS2812B) inside. I have an STM32 Blue Bill and RFM69HCW to run the light patterns and connect to MySensors.
In Domoticz, I have it set up as a dimmer light, but the node just switches patterns depending on what the dimmer level is.
At first, I wrapped the LED strip carefully around a tube that sits in the center of the glass jar, but it didn't look very good. Somehow just spiraling the strip in the bottom of the lamp has a much better effect.
My wife even liked it, so maybe I will put some finishing touches on it and actually use it as a lamp : )

[berkseo]

@berkseo
https://translate.google.ru/translate?hl=&sl=ru&tl=en&u=https%3A%2F%2Fmysku.ru%2Fblog%2Fdiy%2F72557.html

Original (code without Google formatting): https://mysku.ru/blog/diy/72557.html

[berkseo]

Test nRF52840 with Mysensors on Arduino IDE
Mysensors & nRF52840 on Arduino IDE – 01:19
— Andrew EfektaSB

based on source - https://translate.google.ru/translate?sl=ru&tl=en&u=https%3A%2F%2Fmysensors-rus.github.io%2Fnrf52840-The-first-steps%2F

[Fanfan]

Well, Design of an home made electronic kit for my 10yo daughter to teach her by example. on 74HC595 (shift reg), 9 leds, 4 push buttons, some wrapping wire, ... We managed to build it, it works, with some bad contacts, but it works, she enjoyed the thing and the time spent together. Here is the schema and the pictures. I strongly invite parents to build it with their children, easy and fun. !

[bjacobse]

@fanfan
Looks nice, and I love the idea that you spend time and knowledge to your kids
but looking at the current budget it seems that you are above the rated current consumption for the 74HC595, just so you don't wonder in case it burns when several LEDs are ON at the same time

Input clamp current, I IK (V I < 0 or V I > V CC ) ±20 mA
Output clamp current, I OK (V O < 0 or V O > V CC ) ±20 mA
Continuous output current, I O (V O = 0 to V CC ) ±35 mA
Continuous current through V CC or GND ±70 mA

Data from here:
https://www.sparkfun.com/datasheets/IC/SN74HC595.pdf

[berkseo]

@berkseo
https://translate.yandex.ru/translate?url=https%3A%2F%2Fhabr.com%2Fru%2Fpost%2F450860%2F&lang=ru-en

[Hanane Amrani]

@dbemowsk I've been gambling with an Adafruit AudioFX board and cobbled together this annunciator. Eventually it will likely be a MySensors node to play alarms or different sounds. It is using a reasonably-priced transportable speaker to play the sounds. I were given it to work with my doorbell button node today.

[FotoFieber]

Prototyping my netatmo replacement device. It has an led strip that can simulate a lighouse, a rainbow or a fireplace...
(If not used only for fun, it should warn you, if there is too much CO2 in the air.)

[mfalkvidd]

Today I have spent a few hours trying to eradicate the confusion between MySensors' different message acknowledgements. See https://github.com/mysensors/MySensors/issues/1103 and https://forum.mysensors.org/post/34263 for details.

 core/MyGatewayTransport.cpp                |  11 ++++++-----
 core/MyMessage.cpp                         |   8 +++++++-
 core/MyMessage.h                           |  31 ++++++++++++++++++------------
 core/MyOTALogging.cpp                      |   2 +-
 core/MyProtocol.cpp                        |  16 ++++++++--------
 core/MySensorsCore.cpp                     |  41 ++++++++++++++++++++-------------------
 core/MySensorsCore.h                       | 114 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------------------------------------
 core/MySigning.cpp                         |   4 ++--
 core/MySigning.h                           |   2 +-
 core/MyTransport.cpp                       |  20 +++++++++----------
 core/MyTransport.h                         |   4 ++--
 examples/SecureActuator/SecureActuator.ino |   2 +-
 12 files changed, 147 insertions(+), 108 deletions(-)

I have also updated https://www.mysensors.org/download/sensor_api_20 to use echo instead of ack when describing the echo function. That page didn't have information on the return value for send, present, reqestTime, etc so I added info on the return value as well.

Reference: https://github.com/mysensors/MySensors/pull/1292

[mfalkvidd]

When doing the change above, i noticed that after I created https://github.com/mysensors/MySensors/issues/1107 the number of undocumented MySensors keywords has more than doubled!

The plan was to let the MySensors butler check for missing keywords as soon as the few remaining keywords were documented. If I add the check on the existing code, the butler wouldn't allow any commits which would hinder development. But since no-one has documented the missing keywords in over a year, I decided to blacklist the missing keywords and add the check anyway. The new check will give developers a list of new missing keywords, if they add any, so they can be documented.

Reference: https://github.com/mysensors/MySensors/pull/1293

[mfalkvidd]

I've also submitted documentation updates for clarifying MY_RX_MESSAGE_BUFFER_FEATURE limitiation on esp8266 and renaming RadioSetting to TransportSetting for https://www.mysensors.org/apidocs/group__RadioSettingGrpPub.html

References:
https://github.com/mysensors/MySensors/pull/1296
https://github.com/mysensors/MySensors/pull/1295