nRF24LE1 full controller to control devices and sensors reading!!
-
yes of course!
Serial Communication Examples from mysensors "12; 6; 0; 0; 3; 1.4\n"
Serial Communication Examples "1 11 1 205" - that means a command sets the PWM level on 205 on an output of 1 (p0.3). Well to 2 PWM outputs on the radio module: the second is on p0.2 and has an output number 0 (zero).
and thus the executive unit or the unit of sensors consists a tolkor of nRF24LE1 and the battery -
MaksMS the author of homes-smart.ru - http://habrahabr.ru/users/maksms/topics/
I am leave a request for mysensors adoptation on the forum - http://homes-smart.ru/index.php/component/kunena/5-soft/106-konstruktor-besprovodnogo-klienta-na-nrf24le1?limit=6&Itemid=0&start=18#625 -
I explained at his forum as I could. Maybe it would have made a better programmer. I could to translate this into Russian.
By the way, MaxMS developments relating NRF24LE1 are here - https://github.com/maksms/NRF24LE1_client
It would be nice if programmers seeing and correctly put questions. -
As the creator of idea promised, he will make the designer especially for mysensors... if it embodies ideas at least of the elementary sensors and switches, it is enough. Idea to umeslit everything in one le1 to benefit battery life and the size, for example to build in the standard switch of ringing type for switching on or a dimmirovaniye of light in the room or generally the miniature long-living temperature sensor or movements
-
-
@axillent said:
He had replied with request for mysensors protocol specification. Do we have any?
It is probably easiest to have a look at MyMessage/MySensor classes when doing a port. The over-the-air protocol and behavior isn't super complicated.
-
ESP8266 support
http://homes-smart.ru/index.php/oborudovanie/bez-provodov-wi-fi -
The chip looks nice, however, I am a bit concerned about the AES functionality. I find no mention in the datasheet of key storage. I guess they expect the AES key to be stored in flash but if so, there has to be a way of preventing readout of the flash, since AES is a symmetric-key algorithm, so whoever obtains the key, owns the system.
But apart from this, I am all for RF backend encryption. But if it is sloppily implemented then it is useless in my opinion. But perhaps there are fuses in the chip to prevent readout.It would be nice to have a single-board option with both RF and a simple MCU. But 32kB flash would be better. Perhaps they will offer a slightly fatter one soon.
EDIT: The specification for the flash-variant does seem to offer some readback protection, so AES should be ok to use on the platform. However, with 16Kb it will be tricky to squeeze in anything more sophisticated than the simplest form of sketch examples I am afraid. For me, the ideal platform would be something that has at least 32Kb flash, readback protection and AES encryption of RF data. That way, both signing and encryption can be used for really hard-core sensitive nodes.
-
They also make a slightly fatter module with USB: http://www.nordicsemi.com/eng/Products/2.4GHz-RF/nRF24LU1P
This puppy does come in 32Kb flash variant.
