Minimal design thoughts

[bjornhallberg]

@tbowmo That was a tad more expensive than you expected I guess? Did Mouser add taxes etc at checkout?

[tbowmo]

@bjornhallberg

Yeah, they added Danish VAT to the order..

Just double checked, it's actually only 154$ (925dkk).. Remembered wrong with the exchange rate when I converted earlier, and just took some numbers from the top of my head. The VAT is around 31$.

But still it's a lot of money, specially this time of year..

[Ivan Z]

If use one-sided mounting and on other side set CR2450 holder. Will get a small deviceю

[tbowmo]

And now the components arrived :d

Just miss one capacitor, which is out of stock at Mouser. Got a notice that they will get it in stok again in March 2015! So I'll have to see if I can find an alternative (It was decoupling for the radio).

Hopefully I get some time off to do the first board friday evening.

[tbowmo]

So, it's time for board mounting..

One advice, DOUBLE CHECK the component orders, and TRIPLE check them.. After I got the shipment from mouser, I discovered, that I accidentally had ordered some capacitors in 0101 housing, instead of 0204.. that's DAMN small components.. And I can't use it.. Well thats about 10$ down the drain.. (It was all the decoupling capacitors for the board).

Also found out that I forgot to order a ~100R resistor for the status LED's.. What a bummer!

So I'll have to see if I can source the components quickly from some friends in the next couple of days

Anyways, pic's from the build:

first depanelling in the "garage"

(And just for the fun of it a picture from the garage.. one of my other projects)

And then to the electronics workshop, mounted the atmega

And with NRF module attached...

[bjornhallberg]

@tbowmo Sorry to hear about your sourcing troubles. Wish there was an easier and cheaper way to source things.

Smart depaneling, I have a saw like that standing around as well. I have used it to cut some aluminium profiles before but never considered it for cutting pcbs. Still, I will continue to try and look into tabs and "mouse bites" to make depaneling a bit easier.

Is that an old Ferguson that you're renovating? Sorry, but I immediately thought of Frank Erichsen

So, no problems hand soldering then? Can you complete the circuit for testing or do the missing components get in the way?

[tbowmo]

@bjornhallberg

Sorry to hear about your sourcing troubles. Wish there was an easier and cheaper way to source things.

I am trying to activate my local nerd network, to see if anyone could get the components within the next couple of days (we are 10-18 nerds having regular meetups, some of them are in the electronics business). One of the nerds have some resistors and caps in 0402, but not exactly the values I want (1uF cap, and 760R resistor if I remember correct)

Smart depaneling, I have a saw like that standing around as well. I have used it to cut some aluminium profiles before but never considered it for cutting pcbs. Still, I will continue to try and look into tabs and "mouse bites" to make depaneling a bit easier.

for the next batch of boards, I might go for easier depanelizing options, with tabs and so on (I got the gerber panelizing tool from http://blog.thisisnotrocketscience.nl/projects/pcb-design-tools/)

So, no problems hand soldering then? Can you complete the circuit for testing or do the missing components get in the way?

I managed the soldering so far.. I must admit that I had forgotten how small 0402 components are But soldering, and double checking everything with a "monocle" to magnify things, it's doable..

Also I have tried to power up the atmel, it seems to be ok, at least I can get the correct device checksum when I use my jtagice3 on it with avrdude. It would just be more fun to have all the correct components mounted, for testing and verification of the board, before I push the next board revision off to China

Is that an old Ferguson that you're renovating? Sorry, but I immediately thought of Frank Erichsen wink

Yeah it's an old fergie TEA-20 from '54, that I'm trying to renovate Not everything should be computers / electronics (Btw. is Frank, or "bonderøven" as he's called in Denmark, also known in Sweden?)

[bjornhallberg]

@tbowmo said:

Yeah it's an old fergie TEA-20 from '54, that I'm trying to renovate Not everything should be computers / electronics (Btw. is Frank, or "bonderøven" as he's called in Denmark, also known in Sweden?)

Yep, bonderøven has been on TV over here for a couple of years now. I think I've seen most episodes. I just love that guy's enthusiasm ... and patience.

[tbowmo]

I succeeded in getting a couple of components more (Only missing a 2.2uF 0603 capacitor, that was out of stock at mouser.)

I have vacation, so in theory I could go to the "man cave" and mount the last couple of components. Only problem is, that I have 2 "tasmanian devils" aged 3 and 5 years running wild at home today, So no possibility to have time for my self

[tbowmo]

A quick christmas status update, finaly got arround to power the first board up, just with basic code (blink an LED to check that it will work).

Used a couple of hours trying to get my LED to blink. all other pins would toggle, but not my LED, until I finaly digged into the datasheet. I had used A6 for the LED, which turns out to be an input pin only, facepalm. So the board already have the first "green wire" patch

Next up is to get serial up and running. before i can start testing temperature / humidity sensor, and radio interface.

[RJ_Make]

@tbowmo Thanks for the update!!

[tbowmo]

And today, radio connection verified, and Si7021 communication is up and running..

Only problem though, is that the Si7021 reports a temperature of 45-50 degrees celcius, where I know it should be closer to 22 degrees..

Also current consumption is rather high at the moment, arround 40mA, It feels like the SI7021 is getting a little bit warmer, than the rest of the components, which (to me) indicates that there is something wrong here.. I accidentially supplied the board with 5V for at test of the internal RC oscilator stability, which is way above the maximum supply voltage of 3.6V. So that might have killed it.

[RJ_Make]

@tbowmo Did you get to do anymore testing?

[tbowmo]

@ServiceXp

In the "lab" at the moment, testing the first prototype build.. I got the humidity / temperature "bug" sorted out. Replaced the Si7021 chip on my board, and the new one responded as expected, at least with correct temperature. (humidity is a bit off, I think.. I don't have another humidity sensor at hand here in the lab, so can't compare it..)

I also got the radio up. I haven't done any distance measurements yet, but I can reach the gw in the main building (6-7m away throug a couple of brick walls). Added a 2.2uF cap to the radio. It's still running off the bench power supply. I don't see any problems at the atmel side of things when radio is transmitting.

I just made a test, supplying the setup with 1.9V, and the GW still received the temperature updates (somehow my humidity readings don't get through to pidome on the GW, so have to check my setsup again).

I'm waiting for a peer review of the pcb layout, before I push the button for the next batch of proto pcb's. btw. on the next prototype build, I have removed the bmp180, but exposed the SDA/SCL pins on a connector, so it can be attached externally..

And here is a small preview of the upcomming board prototype.. I had to make the board 1.5mm wider, to make it fit a multiple of 0.1mil between the pinheaders on each side of the pcb. So it will be more versatile to other people as well.. (if any one should want to build them)

[tbowmo]

small update again

Did a small rangetest, and it seems that the range is equal to my other sensor (based on arduino mini and batteries). Also moved the node to the main builidng, besides the weatherstation that I got for christmas (which have hygrometer buildin). It seems that the humidity level on both my sensor node, and the weatherstation is almost comparable.

[RJ_Make]

@tbowmo That is great news! Did you have any thoughts/plans on packaging these up for DIY kit sales? Did you have a chance to test the EEPROM?

Thanks for the Update!

[tbowmo]

@ServiceXp

Haven't tested the eeprom yet, as I don't have any use for it right now. And also need to verify the 32khz crystal oscillator (currently running on the internal rc oscillator). Come to think about it, I need to think up some scenarios where the crystal could come in handy.

Investigations are undergoing, to make something for the "public". Can't say anymore at the moment

[RJ_Make]

@tbowmo Gotcha, thanks again for all your hard work, for those of us who simply don't have the skill set to create a good pcb, I really appreciate your work.

I'm looking forward to your other MySensors pcb projects...

[tbowmo]

And sensor #2 is build.. This time the radio module is soldered directly to the sensor module, making it a realy small device now..

[tbowmo]

hmm.. Now I've had the two sensors on the table beside each other (sensor #1 and #2).

Temperature is off by 1.6 degrees celcius, and humidity 2% difference. Could be it's the different temperature, that makes the RH calculation differ a bit..

And for some build data.. It took me a good hour to populate all the parts. This one also have the additional eeprom mounted. but still need something for verifying that it works..

[RJ_Make]

@tbowmo what is the margin of error for the sensors?

[RJ_Make]

@tbowmo Oh and is that an hour using hand soldering?

[tbowmo]

@ServiceXp

according to the datasheet the precision on temperature is +/- 0.4 degrees celcius, and +/- 3% RH.

They did however release a new chip revision (Si7021-A20) just after I bought mine (which is A10), they had some problems where the chip didn't enter standby correctly. Maybe that is the problem (also battery drain has been quicker than what I expected on the new node)

and yes, it's about an hour handsoldering things, and also programming the sensor, which also caused some troubles. Had to reprogram a lot of times, because of checksum errors. This could be caused by the fact that I have both eeprom, and nrf24l chip hanging on the SPI bus on the atmega, this is the same bus that is used by my ISP programmer (jtag ice3).

Think I have to get a proper bootloader into the device, so I can use the serialport to download instead.

[tbowmo]

and now the external SPI flash is verified as working, just with a simple program, reading out the manufacturer ID, and writing / reading data to/from the device.

Next step I wanted to get a bootloader working, so I could use standard arduino to download firmware, and also (at some point in time) utilize the flash for OTA updates. However, I can't seem to get bootloader support working..

I have tried to get DualOptiboot from lowpowerlabs working now, with several rebuilds etc., it seems like it is running fine (LED is blinking a couple of times, when it boots) but arduino wont sync to the bootloader, so either it runs on a wrong baudrate, or something else is wrong in the setup. But so far I haven't suceeded in figuring out what it is..

(Anyone else that has some knowledge on bootloaders, that could have an idea to what to look at?)

/ Thomas

[tbowmo]

I am almost ready for a second prototype spin of the PCB, but before doing that I could use some input from the community,

If this board was going into "mass production", is there any features that I should consider adding? Any missing parts? Anything that you think that I have forgotten?

The schematics for revision 2 is a couple of posts back in the thread.

I have considered adding a ATSHA204 for future security purposes, but can't seem to find a suitable spot for it (maybe I'm just too tired to see things clearly at the moment :)).

[boozz]

@tbowmo
Does this link help you? Some explanation on bootloaders and practical stuff to help you burn botloaders on the ao Atmega326...

BR
Boozz

[tbowmo]

@boozz said:

@tbowmo
Does this link help you? Some explanation on bootloaders and practical stuff to help you burn botloaders on the ao Atmega326...

BR
Boozz

I can program a standard arduino bootloader, which works. I just want to use the one from lowpowerlabs, dual optiboot, so i can utilise the external Flash chip. But i Can't get it to work at all.

[boozz]

@tbowmo
Ok, I misinterpreted your question. Can't help you on that one, sorry

[RJ_Make]

@tbowmo said:

I am almost ready for a second prototype spin of the PCB, but before doing that I could use some input from the community,

If this board was going into "mass production", is there any features that I should consider adding? Any missing parts? Anything that you think that I have forgotten?

The schematics for revision 2 is a couple of posts back in the thread.

I have considered adding a ATSHA204 for future security purposes, but can't seem to find a suitable spot for it (maybe I'm just too tired to see things clearly at the moment :)).

I would work on trying to get the ATSHA204 included, even if it means the dims get a little larger. The one thing that I really don't like about MySensors is the lack of any wireless security.. Would love to see this implemented.

[rdevine]

@tbowmo Maybe i missed it but do you have an image with the si7021 attached to the radio and pcb?

[tbowmo]

@rdevine said:

@tbowmo Maybe i missed it but do you have an image with the si7021 attached to the radio and pcb?

Look in post #93 the small white dot on the pcb is the si7021

[tbowmo]

@ServiceXp said:

I would work on trying to get the ATSHA204 included, even if it means the dims get a little larger. The one thing that I really don't like about MySensors is the lack of any wireless security.. Would love to see this implemented.

For one second, I thought you where danish :), as the word "dims" usually refers to a small gadget like device, that you don't have a name for at the moment (or even components, screws, bolts, anything small could be a "dims")

[Tibus]

@tbowmo said:

ATSHA204

This module is verry interesting but how it work? What you have to do in code to make it work, crypting messages,...?

[Dirk_H]

@tbowmo I don't see a Load Capacitor on the crystal. Especially if you need a precise clock you should use some. Have a look at https://www.adafruit.com/blog/2012/01/24/choosing-the-right-crystal-and-caps-for-your-design/ for example about Load Capacitors.

[tbowmo]

@Dirk_H said:

@tbowmo I don't see a Load Capacitor on the crystal. Especially if you need a precise clock you should use some. Have a look at https://www.adafruit.com/blog/2012/01/24/choosing-the-right-crystal-and-caps-for-your-design/ for example about Load Capacitors.

I know that normally the crystal require load capacitors, but for the low freq. oscilator (32Khz) its not necessary (as far as I have read), that's why I omitted them from the design. I'll try and dig out the datasheets when I'm at home and double check things.

[tbowmo]

@Tibus said:

@tbowmo said:

ATSHA204

This module is verry interesting but how it work? What you have to do in code to make it work, crypting messages,...?

There are other threads about the ATSHA204 around in the forum. It's basically just a method for signing messages between units, not encryption. I haven't made any code for it myself, just thinking about implementing it for future plans (and for others to pick up on)

[RJ_Make]

@tbowmo said:

@Tibus said:

@tbowmo said:

ATSHA204

This module is verry interesting but how it work? What you have to do in code to make it work, crypting messages,...?

There are other threads about the ATSHA204 around in the forum. It's basically just a method for signing messages between units, not encryption. I haven't made any code for it myself, just thinking about implementing it for future plans (and for others to pick up on)

Ah but from what I've read it can indeed encrypt the data stream. Did I completely get it wrong?

[tbowmo]

@ServiceXp said:

@tbowmo said:

@Tibus said:

@tbowmo said:

ATSHA204

This module is verry interesting but how it work? What you have to do in code to make it work, crypting messages,...?

There are other threads about the ATSHA204 around in the forum. It's basically just a method for signing messages between units, not encryption. I haven't made any code for it myself, just thinking about implementing it for future plans (and for others to pick up on)

Ah but from what I've read it can indeed encrypt the data stream. Did I completely get it wrong?

It's a crypto authentication device, datasheet is at
http://www.atmel.com/devices/ATSHA204A.aspx

For sensor data it should be enough, it help to prevent replay attacks, so an intruder can't switch of the lights for example, because the attacker don't have the presharred keys available

[daulagari]

It's a crypto authentication device

As discussed in the security thread I think authentication alone can be useful but encryption is providing both security and a reasonable form of authentication so why not go for an encryption IC instead of the ATSHA204A.

Atmel has a nice IC doing AES:

http://www.atmel.com/devices/ATAES132.aspx

A bit larger (8 pins SOIC), but reasonable cheap € 0,782 (@10)

It is also part of CryptoCape, so there should be some software support for it.

[tbowmo]

@daulagari

That chip is still only for authentication, only it's with aes-128 message auth instead of sha 256

Also another thing i noted, is that the supported supply range is from 2.5 to 5v, whereas the atsha204 could operate down to 2.0v.

[daulagari]

That chip is still only for authentication, only it's with aes-128 message auth instead of sha 256

If I have a look at the datasheet I see:

Opcode Name        Description
0x06   Encrypt     Encrypts 16 or 32 bytes of plaintext data provided by the Host.
0x07   Decrypt     Decrypts 16 or 32 bytes of data provided by the Host after verifying the integrity MAC.

So it does encrypt/decrypt.

The CryptoCape board has both ATSHA204A and ATAES132 where the ATAES132 can "Encrypt up to a 32 byte packet at a time with AES-128-CCM"

Not sure if it is handy to have the integrity MAC combined as that does require 16 additional bytes, but that is the same story for SHA-256.

[tbowmo]

Hmm I was tricked by the "crypto-authentication" note on atmel site, so thought it only did auth.

Still, lowest vcc is 2.5v. If they could make a device that could operate down to 1.8v instead instead, it would be more interesting.

[RJ_Make]

@tbowmo Yeah the 2.5v would be a problem, unless we can build an extremely efficient boost...

[tbowmo]

@ServiceXp

Yes, but I am trying to avoid booster circuits at all costs in this design. Also the main function is to collect temperature and humidity values from around the house. So for my part encryption is not a must have for this device.

btw I'm almost there with rerouting rev 2 to make room for the atsha204 (in sot23 housing)

[tbowmo]

Just reading through the datasheet of ATAES132, and realise that I already have support for it on the board. It uses a standard I2C / SPI eeprom footprint, and that is already on the board. So if anyone would like to use it, they only need to replace the flash.

Anyway, I have finished re-routing things.. and the ATSHA204 is now incorporated in the design, so challenge/response authentication could be implemented.

Just need to do the last couple of reviews, before I press the order button for a new set of pcb's

[RJ_Make]

Is it not possible to just encrypt the entire packet with an AES library on both ends?

[Anticimex]

@tbowmo Does your design support both I2C and single-write ATSHA204?

[tbowmo]

@Anticimex

It's single wire atsha204, it's connected to A3. I couldn't fit in the 8 pin variants of the atsha204, so that ruled out the full I2C bus version. It even took me a couple of hours of re-routing to make enough room for the sot23 housing of the ATSHA204.

Anyway, schematic / pcb layouts are as follows

[Anticimex]

@tbowmo Excellent.

[RJ_Make]

@tbowmo Once again,... Well Done!

[tbowmo]

And for the fun of it.. Just made a github repository of the design

https://github.com/tbowmo/MySensorMicro

Just in case anyone would like to have a closer look in eagle.

[RJ_Make]

I wonder what kind of "hit" on battery life authentication/encryption will have?

[Anticimex]

I do not think it is a big issue. Authentication is normally only needed on nodes that have actuators. And this implies that they always have to listen for incoming data and are therefore inherently non-battery friendly The ATSHA has a very low power consumption, so the added cost for message signing procedures is probably negligible compared to the cost of running the radio continuously.

[tbowmo]

Hmm thinking about it, authentication could be valuable on sensors as well.

If you use the sensor readings to control another actuator, then an attacker could send in his own bogus sensor values in order to trigger system events. He does need to know the specifics about your setup though, so the question is if it's affordable to the mischief to do anything like that

[Anticimex]

Yep. This is true, and something I eventually have to add support for.

[tbowmo]

@tbowmo said:

@Dirk_H said:

@tbowmo I don't see a Load Capacitor on the crystal. Especially if you need a precise clock you should use some. Have a look at https://www.adafruit.com/blog/2012/01/24/choosing-the-right-crystal-and-caps-for-your-design/ for example about Load Capacitors.

I know that normally the crystal require load capacitors, but for the low freq. oscilator (32Khz) its not necessary (as far as I have read), that's why I omitted them from the design. I'll try and dig out the datasheets when I'm at home and double check things.

Got around to check up on datasheet for atmel328p, when using lowfrequency oscilator, it has internal load capacitors. If you look at page 33 in the datasheet. So it's not necessary for external capacitors

[tbowmo]

very soon the next prototype pcb revision will be ordered from China. Gonna be exciting. Almost like Christmas, where the kids just wanna open their gifts

[tbowmo]

And pcb's are ordered.. Again, using dirtypcbs.com, for the order..

I have used a panelizer tool from http://blog.thisisnotrocketscience.nl/ to panelize the boards this time, so it should be easier to depanelize it when they get here..

[bjornhallberg]

@tbowmo Looks great!

Haven't actually ordered anything produced by the panelizer yet, but the results look really amazing:

I was planning to finally get around to some boost regulators. But I need to design mine from scratch (these are just scavenged from other places) so they follow the same design guide lines and can be plugged in seamlessly to the main pcb.

Would be great if there were some sort of common design to follow for designing shields and such.

[tbowmo]

As you all probably have noticed, there is an mysensor logo on the boards, that I just ordered..

I have been cooperating with @hek for a while, and this is going to be an "official Mysensor pcb"

We have been in discussions with a vendor in china, for doing SMT assembly as well.. We are currently waiting for the pcb's to arrive and get them populated, to verify that everything is as it should be, before we start up production in China.

For a batch of 100 units, the price is about 13$ per unit, plus shipping/handling fee, this is without any profits to the project

One question though, I made room for an ATSHA204 chip on the board, that could be used for authentication purposes, we want to know if this should be mounted as default on the board, as it will add arround 1$ to the unit price.

Also how many would be interested in ordering one (or 10, 20, 50?) of them? (just so that we get an indication if we should make a batch of 100 units, or 500 units)

[RJ_Make]

@tbowmo

That's 2 questions...

1. Yes, It's worth it to me (Hopefully there will be MySensors software support down the road)
2. I would probably start off with 3 to 5.

Will there be a "kit" price for those who want to populate and reflow themselves?

[Dwalt]

@tbowmo

I would also be interested in at least 5 boards (initially) if they were populated, not ready for smt soldering yet.

[tbowmo]

@ServiceXp said:

@tbowmo

That's 2 questions...

I edited it a couple of times while talking with @hek last evening, so it slipped. Hope you can forgive me

1. Yes, It's worth it to me (Hopefully there will be MySensors software support down the road)
2. I would probably start off with 3 to 5.

Will there be a "kit" price for those who want to populate and reflow themselves?

No kit version, the pcb will be released under oshw so you could order it yourself, and source the components. However my unit price for the initial units will hit 11-12$, so it's only 1 or 2$ extra to get it smt assembled in China.

The more units we can order the cheaper it will become.

[bjornhallberg]

@tbowmo I might be interested in a few, seeing as this PCB has some pretty unique features, but I'm still in the market for a board with an on-board regulator that will give me a bit more flexibility.

The problem (for me) is that while waiting for any official hardware, I've bought a lot of other stuff. I had another 10x Arduino Pro Mini arrive just yesterday for instance. Plus the booster project above. I ordered a couple of hundred brand inductors and capacitors as well as ltc3525 ICs. So basically now I don't have a choice but to go it alone for the most part

What we could need right now is some clear direction, like whether the ATSHA204 is the way to go. Or some common form factor that would allow future shields or whatnot.

Also, for something really small like this, to be put into production, I would have liked to have tried with the "smd / mini nrf24" version that is also available on Ebay, just to keep the size down even further. I just got three of those yesterday and they are indeed very tiny (pin header spacing is 1.27mm). Whether they work ok or not I do not know. I do know that some people on the forum have posted project pictures with these mini nrf24. I guess what I'm saying is that lowpowerlabs already invented the wheel here: http://lowpowerlab.com/moteino/
Would be great to hang a mini nrf24 flat off of the back if at all possible. But given what we know of the nrf24 it would probably blow up in our faces compared to the RFM12B/RFM69 that the moteino uses. Of course, they also use a wire antenna while we still trust the pcb antenna ...

[tbowmo]

@bjornhallberg said:

@tbowmo I might be interested in a few, seeing as this PCB has some pretty unique features, but I'm still in the market for a board with an on-board regulator that will give me a bit more flexibility.

The problem (for me) is that while waiting for any official hardware, I've bought a lot of other stuff. I had another 10x Arduino Pro Mini arrive just yesterday for instance. Plus the booster project above. I ordered a couple of hundred brand inductors and capacitors as well as ltc3525 ICs. So basically now I don't have a choice but to go it alone for the most part

What we could need right now is some clear direction, like whether the ATSHA204 is the way to go. Or some common form factor that would allow future shields or whatnot.

Also, for something really small like this, to be put into production, I would have liked to have tried with the "smd / mini nrf24" version that is also available on Ebay, just to keep the size down even further. I just got three of those yesterday and they are indeed very tiny (pin header spacing is 1.27mm). Whether they work ok or not I do not know. I do know that some people on the forum have posted project pictures with these mini nrf24. I guess what I'm saying is that lowpowerlabs already invented the wheel here: http://lowpowerlab.com/moteino/
Would be great to hang a mini nrf24 flat off of the back if at all possible. But given what we know of the nrf24 it would probably blow up in our faces compared to the RFM12B/RFM69 that the moteino uses. Of course, they also use a wire antenna while we still trust the pcb antenna ...

I forgot about the mini nrf24 modules. But I don't think that we could have squeezed it that much more in size, we could probably save 2-3mm in stack height, but that's about it.

Also, this board was designed from the beginning to be a battery operated node. That is why there is no regulator on board (besides the fact that there is no room for it). I selected the components for their ability to work on low voltages all, except the atsha204, is able to work on a VCC as low as 1.8V)

I have seen lot's of questions asking about battery operation of 3.3V arduino mini pro, with DHT22 sensors attached. People cut LED's and regulators on the arduino, in order to get the power consumption as low as possible. This is where this particular board fits in. It's ready for battery operation, and has the temperature / humidity sensor build in.

It started out because I wanted an "easy" clean option for sensor nodes for my own application, without any wire nests between arduino and nrf24 modules. I hope that it will be useful for others as well, and might be able to get others going with the mysensor project.

For my own part, I could use up to 20 of these, for measuring temperature / humidity in every room in the house (and out side as well)

Btw. all those arduinos you've bought, could be turned into something else

[bjornhallberg]

I snapped some pictures just so everyone can see the difference between the nrf24 modules.


Of course, like I said, I don't even know if the "mini" works in a satisfactory manner. I'm gonna get some smaller pitch headers so I can make a prototype. But the PCB antenna actually seems to be the exact same size so I have high hopes for that aspect at least.

[tbowmo]

@bjornhallberg

The antenna still needs to hang over "free air" (or an unrouted PCB area), this is the area where the logo is located on the current design. It could be moved to the opposite end of the pcb (where the nrf24 pinheader is located).

If we switch to the mini module, then the pinheader for the radio is removed, but then you need a "larger" area where there is no components at all, in order to mount the nrf module flat to the sensor pcb. So in theory it will not be that much smaller, only the pinheader distance between the two pcbs can be removed.. lenght /width will be almost the same, maybe a bit longer as there is not that much room to give, with the current number of components (Si7021, eeprom, atsha204 etc).

[bjornhallberg]

@tbowmo Yeah, you're probably right. It would take some re-design and you might not save all that much space, given all the other components as you say.

Still, it'd be great to achieve something ... flatter ... like:
http://harizanov.com/2014/07/diy-internet-of-things-fire-alarm/
Runs an attiny84 though, but still.

[tbowmo]

@bjornhallberg

Could you measure the mini pcb? the width of the module, and lenght of the area with gnd, and the length of the antenna area (and total length of the module, should be the two lengths added together)

[bjornhallberg]

@tbowmo I found an old post I made here:
http://forum.mysensors.org/topic/413/is-there-a-schematic-of-the-nrf24-board/2
I checked the measurements and they seem right. In addition, the antenna-area is about 8mm long.

[tbowmo]

@bjornhallberg

made a mockup of the nrf24 mini module, and tried to place it on the sensor board.. If I should use it, I have to remove the ISP pinheader from the board, as there is no room for it.

Also, it is filling up almost half the populated pcb area on the sensor board, which means that there is not enough space for the components, and we have to make a bigger pcb, in order to have room for everything.

[bjornhallberg]

@tbowmo Yeah, better to save it for a future project. I mean, there will never be a one size fits all and that is what is so great about MySensors. All the PCBs designed so far have a purpose and a market. And ideally, we'd want a few of each in the sensor network to complement each other.

The reason I brought up the "mini", aside from wanting a flatter sensor node, is that the module seems to be getting more common on Ebay as well as cheaper. I've seen some sellers that sell them for the same price as the regular NRF24 now (in 10pcs). Four months ago, they were rare and many times more expensive. So if they work as advertised they could soon replace the NRF24 module we've all come to use.

In this context, and knowing very little of antennas, it is too bad they don't have a version without the PCB antenna altogether. We could add our own antennas and more easily fit the module on miniscule sensor nodes such as yours.

[tlund]

I would be interested in 5 units. I lean towards including ATSHA204 and smt assembled, but I would buy without and unassembled.

[tbowmo]

@tlund

So you would just buy the PCB, and source all components yourself?

[tlund]

@tbowmo
Sorry I was a bit unclear. I would like to buy all components as a package from you/mysensors. Preferably assembled, but I would also accept if you sell it unassembled (pcb+components). I would rather not have to source the components myself

Btw, have you measured the actual power consumption? Sleep vs temp/hum measurement?

[tbowmo]

@tlund

I haven't measured supply current, as I don't have the equipment to do that. I am looking at getting the uCurrent gold from eevblog, but it's expensive to import it to Denmark.

It will probably not be offered as a kit. Too much work from my/our part

[hek]

@tbowmo said:

uCurrent gold

I can probably test it using mine. Any plans going to Skåne soon

[Alphalove]

Hello, I'd be in for at least 5 assembled boards.

[A Former User]

Soo .. this like a breadmix ? All we have to add is the sensors ?

[tbowmo]

@hek

You already got an ucurrent? I had planned to import an extra one from Australia for you (thought that we might be able to save some $ if we ordered 4-5 units).

But as so many other things i got away from it again

Unfortunately I only come to Copenhagen these days, visiting a client.

[tbowmo]

@JimmyH

There is a temperature / humidity sensor on it already. But more can be added

[hek]

Ok, pushed a product page to the main site just now. Hope the page is selling enough.

http://www.mysensors.org/hardware/micro

[RJ_Make]

"ATSHA204A sot23 footprint on board"

So does that mean this run will not have the ATSHA204A populated?

[tbowmo]

@ServiceXp

We haven't started production yet, I'm still waiting for the latest prototype pcb to arrive from China, before I can make the (hopefully) last prototype before "mass production". Which also means I have to find the atsha204 somewhere, so I can test it.

And yes I know mouser has it, but I don't need that much more from them, so will have to pay a big handling/shipping fee to them

[hek]

@Anticimex , did you have any spare atsha204 left?

[bjornhallberg]

@tbowmo Have you looked on AliExpress. A quick search seems to suggest that could be a viable alternative. Try some different search combinations though ... their search engine sucks. "ATSHA204" wont find "ATSHA204A" for instance when I try.

Wont be quick though, and the Chinese New Year is coming up ...

[Anticimex]

I can part with a SOT23 ATSHA204A if necessary. They can also be sampled from Atmel in small quantities for free (that's what I did).

[hek]

@Anticimex said:

sampled

Do you remember the deliver time on samples?

[Anticimex]

@hek It took three days from order confirmation to shipment notification. I don't recall the transit times but it went out with DHL WW Express so it should be pretty fast. Say 5-10 working days tops.

[tbowmo]

@Anticimex said:

@hek It took three days from order confirmation to shipment notification. I don't recall the transit times but it went out with DHL WW Express so it should be pretty fast. Say 5-10 working days

hmm what is the sample quantity limit?

[Anticimex]

@tbowmo I don't remember. But I got at least three (don't think I requested more since at the time I was not sure it would meet my personal demands, nor if the MySensors community would accept it). Since it is now kind of "official" I guess it has

[tbowmo]

@Anticimex said:

@tbowmo I don't remember. But I got at least three (don't think I requested more since at the time I was not sure it would meet my personal demands, nor if the MySensors community would accept it). Since it is now kind of "official" I guess it has

ok, I'll try and get some samples then.

Has there been any work done to support easy initialization of the keys on new devices?

[Anticimex]

@tbowmo That's already done. Available in development branch. I will update it to support devices without UART in the near future. Check libraries/sha204/examples/sha204_personalizer
Auto-generation of keys is supported as well as manually contributed ones (all devices in the same environment needs to share a key). All necessary personalization for MySensors usage is done (default settings are fine) and locking of both configuration and data sections are suppored (only configuration section is mandatory to lock).

[tbowmo]

@Anticimex

It's wit a separate sketch, right? Can we do anything in the protocol for key initialization? So when a device asks for a node Id it could also get the shared key supplied via radio?

I am thinking about creating a plug and play ready unit, with a preloaded sensor sketch from the factory in China, would be nice if people had an easy method of initializing things without reloading other sketches

[Anticimex]

@tbowmo short answer: no. Sending the key in clear text is out of the question. That is totally not secure. The whole idea with that circuit is that the key is prestored and hidden. Technically it is possible but then one also has to work around the payload size limitation in the rf protocol.

[tbowmo]

@Anticimex

I know that there are some gotcha's with cleartext key transfer.. But I thought thata if output power is set to lowest value in the GW, and key transfers only could be done while in discovery mode. Then the risk of anyone snooping it, is lower..

Going into "easy initialize thinking mode" :d

[Anticimex]

@tbowmo I do understand what you seek. However.

1. If we do accept the added cost in memory use and component cost (and development effort) of using a strong authentication hardware, it makes no sense throwing it all away by implementing its use in an insecure way (although the common man probably won't be able to compromise it).
2. I have already made one big sacrifice in allowing truncated signatures (or we would have to implement a framing protocol for sending >32 byte messages).
3. I am not going to implement a signing scheme which I would be able to hack myself.

Basically, my ambition with the signing is not a "low risk" of hacking. it is a "no" risk of hacking. (with the reservation of the truncated signature as mentioned above). Signatures will be inversely proportional to the complexity of the message. Signature size = 32-7-<payload size>-1 byte. In other words, the maximum possible signature size for a 1-byte message is 23 bytes. But I do think HMAC-256 is still a bitch to hack even if a portion of it is sliced off.

Also, how do you prevent an attacker from issuing its own keys by resetting the HW in some way? And besides, all users have to program their devices for them to do anything at all. Doing the ATSHA204 personalization is a one-time effort, and adds quite little work and I see no reason why it would not be possible to do this by OTA either if one preferred to do that. The configurations and keys are permanently stored on the devie in EEPROM. So the personalization is only executed once on every security-enabled device.
I think we need to save as much space as possible so having all nodes drag around the logic to do key replacement will add a memory cost in itself. And if you take security really seriously, you do want to lock down the fused key as well. Atmel is quite fuzzy about what security can be guaranteed if the data section is not locked so I am not sure if key readout is prevented with data unlocked even if configuration forbids it. The datasheet is not clear on that.

The idea is:
You deploy a gateway that has the ability to sign (and verify) messages. You personalize the ATSHA device on your gateway with some personal secret key. The personalization sketch allows you to randomize that key if desired.
You take the sketch and store the generated key in it and tucks it away. For every node you want to add, you download and execute the personalization once. And then your done with that. It will from there on be able to exchange signed messages with your gateway until you either revoke the key in the gateway (reprogram it if data is unlocked or replace it and change the key in the new device).
In my opinion, a one-time initialization is not that difficult. But perhaps my sketch is complex, I welcome feedback on that topic. I have tried to explain the expected usage in the comments in the sketch header.

My personal opinion on the security matter: We do it properly or we skip it. Every user ultimately decides by them self if they want security in their sensor network. And if they do go for it, it should be trustworthy.

[hek]

Let's continue the discussion in the security thread.

[tbowmo]

@hek
Yes.. forgot about that..

[tbowmo]

sample order is sent for the atsha204 chips.. Hope it will go through at atmel..

I could only order 3 samples in total.. But that should be enough for checking that everything is working, and for sending one off to manufacturer in China.