Posts made by rsachoc

@LastSamurai thanks, progress, I'm getting this now, which means it's working! Finally, a working node from a complete rookie like me!

Serial started
Voltage: 3389 mV
Internal temp: 266.00 *C
send: 100-100-0-0 s=255,c=3,t=15,pt=2,l=2,sg=0,st=ok:0
send: 100-100-0-0 s=255,c=0,t=17,pt=0,l=5,sg=0,st=ok:1.5.4
send: 100-100-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=ok:0
read: 0-0-100 s=255,c=3,t=15,pt=0,l=2,sg=0:

sensor started, id=100, parent=0, distance=1
send: 100-100-0-0 s=255,c=3,t=11,pt=0,l=12,sg=0,st=fail:TempHumTest2
send: 100-100-0-0 s=255,c=3,t=12,pt=0,l=12,sg=0,st=fail:1.0 17052016
send: 100-100-0-0 s=0,c=0,t=6,pt=0,l=0,sg=0,st=fail:
send: 100-100-0-0 s=1,c=0,t=7,pt=0,l=0,sg=0,st=fail:
Node and 2 children presented.
T: 998.00
TempDiff :1098.00
send: 100-100-0-0 s=0,c=1,t=0,pt=7,l=5,sg=0,st=fail:998.0
T sent!
H: 118
HumDiff  :218.00
send: 100-100-0-0 s=1,c=1,t=1,pt=2,l=2,sg=0,st=ok:118
H sent!
Battery voltage: 3359 mV
Battery percent: 104 %
send: 100-100-0-0 s=255,c=3,t=0,pt=1,l=1,sg=0,st=ok:104

I think that the readings are not accurate though, not sure why, but I'll have a go at figuring our why anyway!

@LastSamurai I'm having a go as well at updating the .ino file with the different library, but I'm not a coder so I'm "having a hack" - if you have any luck could you post your code?

@GertSanders hmmm I think I'm using that same one as @LastSamurai so I suspect that's the issue? It's the one linked in the first post

I guess if that's the problem it should have been obvious to me, it even says HTU21D on mine! Silly me!

Ok, so I messed up my previous sensor trying to solder the bridge (don't ask...) I have now (I think) soldered it and reconnected it, am now getting the following:

Serial started
Voltage: 3359 mV
send: 132-132-0-0 s=255,c=3,t=15,pt=2,l=2,sg=0,st=fail:0
send: 132-132-0-0 s=255,c=0,t=17,pt=0,l=5,sg=0,st=fail:1.5.4
send: 132-132-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=fail:0
sensor started, id=132, parent=0, distance=1
send: 132-132-0-0 s=255,c=3,t=11,pt=0,l=15,sg=0,st=fail:EgTmpHumBat5min
send: 132-132-0-0 s=255,c=3,t=12,pt=0,l=10,sg=0,st=fail:1.0 151106
send: 132-132-0-0 s=0,c=0,t=6,pt=0,l=0,sg=0,st=fail:
find parent
send: 132-132-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
send: 132-132-0-0 s=1,c=0,t=7,pt=0,l=0,sg=0,st=fail:
Node and 2 children presented.

I'm going to try get everything on a breadboard, but now I see fails, what's that all about?

PS will upload some pics of the soldered bridge...

Tried it this evening, still no luck, let me see what I can get up to over the weekend.

@m26872 thanks! No time tonight, but a job for testing tomorrow.

@m26872 oh! I didn't realise I needed to do that, could that be the problem? Do I just need to fill with solder the bit just below where the DA and "-" is?

Some pictures anyway!

Thanks both, I have the "pre-modded" si7021, so it's the one that should operate at between the 1.9 and 3.3v. I the Arduino I used to burn the Atmega is a knockoff, so it has both 3.3v and 5v. Let me do some research and see if I can test the si7021 using it.

@m26872 thanks, yes, I guessed that something might be wrong with the sensor, I checked continuity between the board and the sensor and all seemed fine.

To test on an Arduino, I've honestly very little clue how to do this. Could I utilise the breadboard and Arduino I used to flash the AtMega?

Maybe I need to add that I'm running the 2.0 MQTT controller? Not sure if that makes a difference? GatewayW5100MQTTClient

Just had a look what's going on on the controller side, this is what I see

0;255;3;0;9;Starting gateway (RNNGA-, 2.0.0-beta)
0;255;3;0;9;Radio init successful.
0;255;3;0;9;Init complete, id=0, parent=0, distance=0
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;read: 132-132-0 s=255,c=3,t=15,pt=2,l=2,sg=0:0
0;255;3;0;9;send: 0-0-132-132 s=255,c=3,t=15,pt=0,l=2,sg=0,st=ok:

0;255;3;0;9;read: 132-132-0 s=255,c=0,t=17,pt=0,l=5,sg=0:1.5.4
0;255;3;0;9;Sending message on topic: mygateway1-out/132/255/0/0/17
0;255;3;0;9;read: 132-132-0 s=255,c=3,t=6,pt=1,l=1,sg=0:0
0;255;3;0;9;Sending message on topic: mygateway1-out/132/255/3/0/6
0;255;3;0;9;read: 132-132-0 s=255,c=3,t=11,pt=0,l=15,sg=0:EgTmpHumBat5min
0;255;3;0;9;Sending message on topic: mygateway1-out/132/255/3/0/11
0;255;3;0;9;read: 132-132-0 s=255,c=3,t=12,pt=0,l=10,sg=0:1.0 151106
0;255;3;0;9;Sending message on topic: mygateway1-out/132/255/3/0/12
0;255;3;0;9;read: 132-132-0 s=0,c=0,t=6,pt=0,l=0,sg=0:
0;255;3;0;9;Sending message on topic: mygateway1-out/132/0/0/0/6
0;255;3;0;9;read: 132-132-0 s=1,c=0,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;Sending message on topic: mygateway1-out/132/1/0/0/7

@m26872 thanks, I've set that, no change even after more than 15seconds and debug set.

Could it be the way I've connected the si7021? I've got it as follows:

1. A4 to SDA
2. A5 to SCL
3. GND to GND
4. VCC to 3.3v

So I think I've finally got everything up and running! This is what I'm getting at the serial monitor in the IDE:

Serial started
Voltage: 3359 mV
send: 132-132-0-0 s=255,c=3,t=15,pt=2,l=2,sg=0,st=ok:0
send: 132-132-0-0 s=255,c=0,t=17,pt=0,l=5,sg=0,st=ok:1.5.4
send: 132-132-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=ok:0
read: 0-0-132 s=255,c=3,t=15,pt=0,l=2,sg=0:

sensor started, id=132, parent=0, distance=1
send: 132-132-0-0 s=255,c=3,t=11,pt=0,l=15,sg=0,st=ok:EgTmpHumBat5min
send: 132-132-0-0 s=255,c=3,t=12,pt=0,l=10,sg=0,st=ok:1.0 151106
send: 132-132-0-0 s=0,c=0,t=6,pt=0,l=0,sg=0,st=ok:
send: 132-132-0-0 s=1,c=0,t=7,pt=0,l=0,sg=0,st=ok:
Node and 2 children presented.

What I'm trying to figure out is where the temp and humidity reading are so I can get them into MQTT/OpenHab. Looking at the output, I can't see which one is the temp, humidity or battery level?

@siod I was in much the same position as you, but the simple suggestion is to use the SI7021, as per this thread. Otherwise, the links in the other thread are for the 5v builds.

@siod my understanding was that the voltage which is provided by the slim node wouldn't be suitable for the DHT11 and DHT22, as they require a minimum of 3.3v. There is some discussion here on the DHT22, which I understand has the same voltage requirements as the DHT11.

I just received my non-3.3v Si7021, and have now updated the lessons learnt post, as this board is tiny and I managed to mess up the soldering completely. Ordered the 3.3 ready version now, another month wait...

It lives! Well the one node I created does at least! I'll troubleshoot it, but the problem was the R1 resistor, which I (noobishly) forgot about! But very pleased, and thanks to m26872 especially and everyone else who helped.

I've updated the lessons learn post too!

@m26872 well that is probably it! I didn't even realise I needed that, oops! Sorry ! Let me try and get one (I think I have some already) and get soldering

OK so I changed the polarity of the 4.7uf capacitor and I'm still receiving the same error. So I built a barebones one without sensor and without NRF. I am still getting the same error when uploading the sketch via the FTDI adaptor. I tried uploading a sketch to a Sensebender I have and it worked fine, so that rules out the FTDI adaptor.

Some pics in case someone can spot something obvious.

http://i.imgur.com/1SV0qO2.jpg

http://i.imgur.com/mUp87hB.jpg

http://i.imgur.com/oCqcDpo.jpg

So I can only think that it must be related to the ATMega bootloader? In the how to burn a bootloader thread, I received the following when trying to burn the bootloader, so I assumed it uploaded correctly?

C:\Users\James\Desktop\RPi Openhab\arduino-1.6.7-windows\hardware\tools\avr/bin/avrdude -CC:\Users\James\Desktop\RPi Openhab\arduino-1.6.7-windows\hardware\tools\avr/etc/avrdude.conf -v -patmega328p -cstk500v1 -PCOM5 -b19200 -e -Ulock:w:0x3F:m -Uefuse:w:0x05:m -Uhfuse:w:0xDE:m -Ulfuse:w:0xFF:m 

avrdude: Version 6.0.1, compiled on Apr 15 2015 at 19:59:58
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2009 Joerg Wunsch

         System wide configuration file is "C:\Users\James\Desktop\RPi Openhab\arduino-1.6.7-windows\hardware\tools\avr/etc/avrdude.conf"

         Using Port                    : COM5
         Using Programmer              : stk500v1
         Overriding Baud Rate          : 19200
         AVR Part                      : ATmega328P
         Chip Erase delay              : 9000 us
         PAGEL                         : PD7
         BS2                           : PC2
         RESET disposition             : dedicated
         RETRY pulse                   : SCK
         serial program mode           : yes
         parallel program mode         : yes
         Timeout                       : 200
         StabDelay                     : 100
         CmdexeDelay                   : 25
         SyncLoops                     : 32
         ByteDelay                     : 0
         PollIndex                     : 3
         PollValue                     : 0x53
         Memory Detail                 :

                                  Block Poll               Page                       Polled
           Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
           ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
           eeprom        65    20     4    0 no       1024    4      0  3600  3600 0xff 0xff
           flash         65     6   128    0 yes     32768  128    256  4500  4500 0xff 0xff
           lfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           hfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           efuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           lock           0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           calibration    0     0     0    0 no          1    0      0     0     0 0x00 0x00
           signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00

         Programmer Type : STK500
         Description     : Atmel STK500 Version 1.x firmware
         Hardware Version: 2
         Firmware Version: 1.18
         Topcard         : Unknown
         Vtarget         : 0.0 V
         Varef           : 0.0 V
         Oscillator      : Off
         SCK period      : 0.1 us

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.02s

avrdude: Device signature = 0x1e950f
avrdude: erasing chip
avrdude: reading input file "0x3F"
avrdude: writing lock (1 bytes):

Writing | ################################################## | 100% 0.01s

avrdude: 1 bytes of lock written
avrdude: verifying lock memory against 0x3F:
avrdude: load data lock data from input file 0x3F:
avrdude: input file 0x3F contains 1 bytes
avrdude: reading on-chip lock data:

C:\Users\James\Desktop\RPi Openhab\arduino-1.6.7-windows\hardware\tools\avr/bin/avrdude -CC:\Users\James\Desktop\RPi Openhab\arduino-1.6.7-windows\hardware\tools\avr/etc/avrdude.conf -v -patmega328p -cstk500v1 -PCOM5 -b19200 -Uflash:w:C:\Users\James\Desktop\RPi Openhab\arduino-1.6.7-windows\hardware\arduino\avr/bootloaders/optiboot/optiboot_atmega328.hex:i -Ulock:w:0x0F:m 
Reading | ################################################## | 100% 0.01s

avrdude: verifying ...
avrdude: 1 bytes of lock verified
avrdude: reading input file "0x05"
avrdude: writing efuse (1 bytes):

Writing | ################################################## | 100% 0.01s

avrdude: 1 bytes of efuse written
avrdude: verifying efuse memory against 0x05:
avrdude: load data efuse data from input file 0x05:
avrdude: input file 0x05 contains 1 bytes
avrdude: reading on-chip efuse data:

Reading | ################################################## | 100% 0.01s

avrdude: verifying ...
avrdude: 1 bytes of efuse verified
avrdude: reading input file "0xDE"
avrdude: writing hfuse (1 bytes):

Writing | ################################################## | 100% 0.01s

avrdude: 1 bytes of hfuse written
avrdude: verifying hfuse memory against 0xDE:
avrdude: load data hfuse data from input file 0xDE:
avrdude: input file 0xDE contains 1 bytes
avrdude: reading on-chip hfuse data:

Reading | ################################################## | 100% 0.01s

avrdude: verifying ...
avrdude: 1 bytes of hfuse verified
avrdude: reading input file "0xFF"
avrdude: writing lfuse (1 bytes):

Writing | ################################################## | 100% 0.01s

avrdude: 1 bytes of lfuse written
avrdude: verifying lfuse memory against 0xFF:
avrdude: load data lfuse data from input file 0xFF:
avrdude: input file 0xFF contains 1 bytes
avrdude: reading on-chip lfuse data:

Reading | ################################################## | 100% 0.01s

avrdude: verifying ...
avrdude: 1 bytes of lfuse verified

avrdude done.  Thank you.


avrdude: Version 6.0.1, compiled on Apr 15 2015 at 19:59:58
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2009 Joerg Wunsch

         System wide configuration file is "C:\Users\James\Desktop\RPi Openhab\arduino-1.6.7-windows\hardware\tools\avr/etc/avrdude.conf"

         Using Port                    : COM5
         Using Programmer              : stk500v1
         Overriding Baud Rate          : 19200
         AVR Part                      : ATmega328P
         Chip Erase delay              : 9000 us
         PAGEL                         : PD7
         BS2                           : PC2
         RESET disposition             : dedicated
         RETRY pulse                   : SCK
         serial program mode           : yes
         parallel program mode         : yes
         Timeout                       : 200
         StabDelay                     : 100
         CmdexeDelay                   : 25
         SyncLoops                     : 32
         ByteDelay                     : 0
         PollIndex                     : 3
         PollValue                     : 0x53
         Memory Detail                 :

                                  Block Poll               Page                       Polled
           Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
           ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
           eeprom        65    20     4    0 no       1024    4      0  3600  3600 0xff 0xff
           flash         65     6   128    0 yes     32768  128    256  4500  4500 0xff 0xff
           lfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           hfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           efuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           lock           0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           calibration    0     0     0    0 no          1    0      0     0     0 0x00 0x00
           signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00

         Programmer Type : STK500
         Description     : Atmel STK500 Version 1.x firmware
         Hardware Version: 2
         Firmware Version: 1.18
         Topcard         : Unknown
         Vtarget         : 0.0 V
         Varef           : 0.0 V
         Oscillator      : Off
         SCK period      : 0.1 us

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.02s

avrdude: Device signature = 0x1e950f
avrdude: NOTE: "flash" memory has been specified, an erase cycle will be performed
         To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file "C:\Users\James\Desktop\RPi Openhab\arduino-1.6.7-windows\hardware\arduino\avr/bootloaders/optiboot/optiboot_atmega328.hex"
avrdude: writing flash (32768 bytes):

Writing | ################################################## | 100% 0.00s

avrdude: 32768 bytes of flash written
avrdude: verifying flash memory against C:\Users\James\Desktop\RPi Openhab\arduino-1.6.7-windows\hardware\arduino\avr/bootloaders/optiboot/optiboot_atmega328.hex:
avrdude: load data flash data from input file C:\Users\James\Desktop\RPi Openhab\arduino-1.6.7-windows\hardware\arduino\avr/bootloaders/optiboot/optiboot_atmega328.hex:
avrdude: input file C:\Users\James\Desktop\RPi Openhab\arduino-1.6.7-windows\hardware\arduino\avr/bootloaders/optiboot/optiboot_atmega328.hex contains 32768 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% -0.00s

avrdude: verifying ...
avrdude: 32768 bytes of flash verified
avrdude: reading input file "0x0F"
avrdude: writing lock (1 bytes):

Writing | ################################################## | 100% 0.02s

avrdude: 1 bytes of lock written
avrdude: verifying lock memory against 0x0F:
avrdude: load data lock data from input file 0x0F:
avrdude: input file 0x0F contains 1 bytes
avrdude: reading on-chip lock data:

Reading | ################################################## | 100% 0.01s

avrdude: verifying ...
avrdude: 1 bytes of lock verified

avrdude done.  Thank you.

Ok so that may be the problem then! Let me solder it the right way and see if that helps otherwise I'm going to create a bare bones slim mode as suggested

edit to confirm the positive leg of the capacitor goes to the positive marked plus sign hole on the board?

Thanks, I haven't actually built a new node, but have been double checking everything on my current node. One thing I wanted to confirm, the 4.7uf capacitor, does the negative leg have to be on the corner of the board, as this is the way I have it currently? I think looking at the board layout in the main slim node thread, it should be the positive leg on the corner and the negative leg on the side of the board (the short side of the board)?

@LastSamurai I've been advised that setting the baud rate in myconfig.h is the correct way to get things working when uploading sketches to the slim node. Don't think it matters when burining the bootloader though.

Hmmm ok, that's what I thought...still no luck, I've modified the boards.txt with the text from the slim node thread, and now it still has the same error message.

To confirm, my FTDI adaptor is attached to the board pins as follows:

FTDI <-> board
GND <-> first pin (i.e bottom left of board when looking at board laying long side horizontal and NRF radio on the other side)
CTS <-> board marked GND
PWR <-> board marked VCC
TXO <-> next up i.e. 4th pin
RXI <-> next up i.e. 5th pin
DTR <-> next up i.e. last pin

Other than that, I guess it may be something wrong with the way I made the board? If so, what's the best way to troubleshoot? Could it be a bad bootloader flash? Is there a way to check if the ATMega has a bootloader?

edit in fact, it could be because I don't have the Si7021 connected? Could this be the reason a sketch is not uploading successfully?

Thanks, I've updated the sketch that I downloaded, also myconfig.h so that should be good. What do I need to select in the Arduino IDE for board type? I searched in the slim node thread and didn't see a reference to any changes?

OK, so it seems that it was because I was using the dev branch that I'm getting that error. I switched over to stable and the sketch compiles, although I do get a warning.

WARNING: Category '' in library UIPEthernet is not valid. Setting to 'Uncategorized'

But I also can't upload the sketch above:

avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x18

I noted above that something needed to be changed in terms of the baud rate, mine is set at 115200 in myconfig.h and I can't seem to find a reference in mysensor.h

Thanks all, I'm sure I will be adding to it, as I'm now trying to compile and upload the sketch. However, I'm getting the following error:

   #error No forward link or gateway feature activated. This means nowhere to send messages! Pretty pointless.

    ^

exit status 1
Error compiling.

I'm using the W5100 MQTT gateway sketch (which I believe is on the development branch), so I'm not sure if that's what's causing the error? I've tried deleting the Arduino IDE, the mysensors development branch from my PC, and reinstalling and redownloading the mysensors dev branch, but the same thing happens?

Some of my tips (noob alert) that I've gathered in my travels so far for this temp Slim node

1. Burn the bootloader onto the ATMega328 first! (here is a guide for Arduino as ISP)
2. Check the capacitor polarity before you solder it (the 4.7uF electrolytic capacitor, the others don't matter)
3. I prefer using strips for the Atmega (see here) as you'll have more clearance for the capacitors which sit underneath (there is a caveat to this however, in that if you're not sure if you've got/burnt a bootloader onto the ATMega, using strips there is no going back, whereas with the chip socket, you can remove the ATMega). Update I think, for me anyway, if you're confident that the ATMega has been bootloaded successfully, I still prefer strips, however if you're unsure what you can do is use the socket and just sit it higher in it's position to get a decent clearance.
4. The bill of materials (BOM) is here and also helps with figuring out which pieces go where
5. Solder the capacitors, wires for Si7021 (with si7021 attached) and FTDI pins to the board first, then the strips + AtMega328p (see below), then the NRF last to the board. I found that the FTDI pins facing straight up were best for the box I was going to put it in
6. Solder the strips to the ATMega first, then to the board
7. Check the size of the box/fitting you are going to mount this in before you do all the above!
8. Check that you are putting the ATMega chip the right way on the board, the notch should be facing the pins for the FTDI.
9. Check continuity of the pins from the ATMega to the board pins underneath, I found the ATMega to strips were the most difficult to solder, and after I tested continuity I found a single pin which didn't have connection, so I added some more solder to this pin.
10. Don't forget the resistor at R1 (I soldered this to the underside of the board, less by choice and more by the fact that I forgot about it, but I guess the preference would be the same side as the capacitors)
11. I strongly advise buying the 3.3v ready si7021 temp sensor (here) as the modification to the 5v version is quite difficult for a newbie (the components are quite small) and you'll probably mess it up like I did.

General soldering tips
12) Practice soldering first, some of the joins are a little challenging and it took me a few attempts to get the hang of it
13) Get a decent size tip, my first was a bit large

@ahmedadelhosni good idea, I hadn't thought of that. I'm going to have to build a slim temp node first, as my current chip is soldered to the board with no bootloader.

C:\Users\James\Desktop\RPi Openhab\arduino-1.6.7-windows\hardware\tools\avr/bin/avrdude -CC:\Users\James\Desktop\RPi Openhab\arduino-1.6.7-windows\hardware\tools\avr/etc/avrdude.conf -v -patmega328p -cstk500v1 -PCOM5 -b19200 -e -Ulock:w:0x3F:m -Uefuse:w:0x05:m -Uhfuse:w:0xDE:m -Ulfuse:w:0xFF:m 

avrdude: Version 6.0.1, compiled on Apr 15 2015 at 19:59:58
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2009 Joerg Wunsch

         System wide configuration file is "C:\Users\James\Desktop\RPi Openhab\arduino-1.6.7-windows\hardware\tools\avr/etc/avrdude.conf"

         Using Port                    : COM5
         Using Programmer              : stk500v1
         Overriding Baud Rate          : 19200
         AVR Part                      : ATmega328P
         Chip Erase delay              : 9000 us
         PAGEL                         : PD7
         BS2                           : PC2
         RESET disposition             : dedicated
         RETRY pulse                   : SCK
         serial program mode           : yes
         parallel program mode         : yes
         Timeout                       : 200
         StabDelay                     : 100
         CmdexeDelay                   : 25
         SyncLoops                     : 32
         ByteDelay                     : 0
         PollIndex                     : 3
         PollValue                     : 0x53
         Memory Detail                 :

                                  Block Poll               Page                       Polled
           Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
           ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
           eeprom        65    20     4    0 no       1024    4      0  3600  3600 0xff 0xff
           flash         65     6   128    0 yes     32768  128    256  4500  4500 0xff 0xff
           lfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           hfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           efuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           lock           0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           calibration    0     0     0    0 no          1    0      0     0     0 0x00 0x00
           signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00

         Programmer Type : STK500
         Description     : Atmel STK500 Version 1.x firmware
         Hardware Version: 2
         Firmware Version: 1.18
         Topcard         : Unknown
         Vtarget         : 0.0 V
         Varef           : 0.0 V
         Oscillator      : Off
         SCK period      : 0.1 us

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.02s

avrdude: Device signature = 0x1e950f
avrdude: erasing chip
avrdude: reading input file "0x3F"
avrdude: writing lock (1 bytes):

Writing | ################################################## | 100% 0.01s

avrdude: 1 bytes of lock written
avrdude: verifying lock memory against 0x3F:
avrdude: load data lock data from input file 0x3F:
avrdude: input file 0x3F contains 1 bytes
avrdude: reading on-chip lock data:

C:\Users\James\Desktop\RPi Openhab\arduino-1.6.7-windows\hardware\tools\avr/bin/avrdude -CC:\Users\James\Desktop\RPi Openhab\arduino-1.6.7-windows\hardware\tools\avr/etc/avrdude.conf -v -patmega328p -cstk500v1 -PCOM5 -b19200 -Uflash:w:C:\Users\James\Desktop\RPi Openhab\arduino-1.6.7-windows\hardware\arduino\avr/bootloaders/optiboot/optiboot_atmega328.hex:i -Ulock:w:0x0F:m 
Reading | ################################################## | 100% 0.01s

avrdude: verifying ...
avrdude: 1 bytes of lock verified
avrdude: reading input file "0x05"
avrdude: writing efuse (1 bytes):

Writing | ################################################## | 100% 0.01s

avrdude: 1 bytes of efuse written
avrdude: verifying efuse memory against 0x05:
avrdude: load data efuse data from input file 0x05:
avrdude: input file 0x05 contains 1 bytes
avrdude: reading on-chip efuse data:

Reading | ################################################## | 100% 0.01s

avrdude: verifying ...
avrdude: 1 bytes of efuse verified
avrdude: reading input file "0xDE"
avrdude: writing hfuse (1 bytes):

Writing | ################################################## | 100% 0.01s

avrdude: 1 bytes of hfuse written
avrdude: verifying hfuse memory against 0xDE:
avrdude: load data hfuse data from input file 0xDE:
avrdude: input file 0xDE contains 1 bytes
avrdude: reading on-chip hfuse data:

Reading | ################################################## | 100% 0.01s

avrdude: verifying ...
avrdude: 1 bytes of hfuse verified
avrdude: reading input file "0xFF"
avrdude: writing lfuse (1 bytes):

Writing | ################################################## | 100% 0.01s

avrdude: 1 bytes of lfuse written
avrdude: verifying lfuse memory against 0xFF:
avrdude: load data lfuse data from input file 0xFF:
avrdude: input file 0xFF contains 1 bytes
avrdude: reading on-chip lfuse data:

Reading | ################################################## | 100% 0.01s

avrdude: verifying ...
avrdude: 1 bytes of lfuse verified

avrdude done.  Thank you.


avrdude: Version 6.0.1, compiled on Apr 15 2015 at 19:59:58
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2009 Joerg Wunsch

         System wide configuration file is "C:\Users\James\Desktop\RPi Openhab\arduino-1.6.7-windows\hardware\tools\avr/etc/avrdude.conf"

         Using Port                    : COM5
         Using Programmer              : stk500v1
         Overriding Baud Rate          : 19200
         AVR Part                      : ATmega328P
         Chip Erase delay              : 9000 us
         PAGEL                         : PD7
         BS2                           : PC2
         RESET disposition             : dedicated
         RETRY pulse                   : SCK
         serial program mode           : yes
         parallel program mode         : yes
         Timeout                       : 200
         StabDelay                     : 100
         CmdexeDelay                   : 25
         SyncLoops                     : 32
         ByteDelay                     : 0
         PollIndex                     : 3
         PollValue                     : 0x53
         Memory Detail                 :

                                  Block Poll               Page                       Polled
           Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
           ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
           eeprom        65    20     4    0 no       1024    4      0  3600  3600 0xff 0xff
           flash         65     6   128    0 yes     32768  128    256  4500  4500 0xff 0xff
           lfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           hfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           efuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           lock           0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           calibration    0     0     0    0 no          1    0      0     0     0 0x00 0x00
           signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00

         Programmer Type : STK500
         Description     : Atmel STK500 Version 1.x firmware
         Hardware Version: 2
         Firmware Version: 1.18
         Topcard         : Unknown
         Vtarget         : 0.0 V
         Varef           : 0.0 V
         Oscillator      : Off
         SCK period      : 0.1 us

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.02s

avrdude: Device signature = 0x1e950f
avrdude: NOTE: "flash" memory has been specified, an erase cycle will be performed
         To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file "C:\Users\James\Desktop\RPi Openhab\arduino-1.6.7-windows\hardware\arduino\avr/bootloaders/optiboot/optiboot_atmega328.hex"
avrdude: writing flash (32768 bytes):

Writing | ################################################## | 100% 0.00s

avrdude: 32768 bytes of flash written
avrdude: verifying flash memory against C:\Users\James\Desktop\RPi Openhab\arduino-1.6.7-windows\hardware\arduino\avr/bootloaders/optiboot/optiboot_atmega328.hex:
avrdude: load data flash data from input file C:\Users\James\Desktop\RPi Openhab\arduino-1.6.7-windows\hardware\arduino\avr/bootloaders/optiboot/optiboot_atmega328.hex:
avrdude: input file C:\Users\James\Desktop\RPi Openhab\arduino-1.6.7-windows\hardware\arduino\avr/bootloaders/optiboot/optiboot_atmega328.hex contains 32768 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% -0.00s

avrdude: verifying ...
avrdude: 32768 bytes of flash verified
avrdude: reading input file "0x0F"
avrdude: writing lock (1 bytes):

Writing | ################################################## | 100% 0.02s

avrdude: 1 bytes of lock written
avrdude: verifying lock memory against 0x0F:
avrdude: load data lock data from input file 0x0F:
avrdude: input file 0x0F contains 1 bytes
avrdude: reading on-chip lock data:

Reading | ################################################## | 100% 0.01s

avrdude: verifying ...
avrdude: 1 bytes of lock verified

avrdude done.  Thank you.

Did I burn the bootloader successfully? The video indicates it should take longer, this literally took less than a second?

@ahmedadelhosni I have some capacitors, but no crystals, so I'm picking a 10mhz and 16mhz up later today. I'll try with just the capacitors first and see how I go.

Thanks!

@ahmedadelhosni thanks! I'm going to grab a 10mhz and 16mhz to test later this evening. Just to confirm from what you've said, I don't need the capacitors? I know in the youtube vid there were capacitors used?

Hi there, and thanks for the tutorial. I'm trying this for the first time (the ATmega is going to be used in a slim temp node), and I'm receiving this message you mentioned:

avrdude: Yikes! Invalid device signature.
Double check connections and try again, or use -F to override

You mention we should try the following:

Maybe your chip is configured to run on an external crystal clock. I tested with two values and it succeeded. I used 10Mhz and 20Mhz as I didn't have 16 Mhz.
Connect the crystal to pin 9 and 10
Note: You won't need the crystal except for the first time as the new bootloader is configured to run on internal 1Mhz or 8Mhz.

I don't quite follow what this means? Do I need a 10mhz, 16mhz or 20mhz crystal attached to the breadboard like you show in the video? If so, is that the only change I would need to make?

FYI I'm using an Arduino clone (Buono uno r3, set at 5V)

@m26872 said:

@rsachoc Why don't you just solder some wires to pins you need ? The "in cicuit serial programming" concept would let you do it with almost anything attached.

I might as well attempt that! I'm waiting for a breadboard, so I'll try and attempt it when that arrives.

Folks, a word of caution, for people that are attempting this for the first time, please burn the bootloader before you solder everything, as silly me, I built the entire thing (without the si7021) and now I'll need to bin it because the ATMega is soldered to the board and I've no way to load the bootloader soldered to the board!

Ah, the life of a newbie

I think what I'll do is once I've actually got a working board, I'll do a newbie writeup so that people don't make the same mistakes as me.

Hi all, again.

I have now successfully built (I think) the slim node, but without the 7021 temp sensor. Because this is the most expensive part of the device and because I find desoldering a challenge, but mainly because I'm waiting for it to arrive from China, can I try and upload the bootloader and sketch without the sensor attached?

If so, I had a couple questions from reading through this thread and the slim node thread. Firstly, uploading the bootloader, can this be done with the FTDI adaptor or do I need to follow the bit described in the slim node thread and attempt it using AVR studio? Secondly, once that is done, is it just a matter of uploading the sketch provided above?

Also, I wanted to confirm a few things on attaching the si7021 temp sensor. From what I can see, SOA (SDA) on the si7021 goes to A4 and SCL goes to A5. Also, GND goes to GND on the board (rightmost set on pins bottom right when FTDI is at the top) and VIN goes to VCC (just next to GND on the board)?

Thanks in advance.

@m26872 no problem, not your fault at all, mine for being a newbie. So much so that my first attempt resulted in me soldering the capacitor to the wrong hole, so I've had to abandon my first attempt. You live, you learn, next time I'll double check.

Thanks, apologies, I really should have looked at my board, I was searching for the answer in the main slim node thread and I think i was looking at older boards and couldn't for the life of me find where C3 is!

Bump, can anyone advise on how I got about finding out where I need to solder the resistors on? So far I've just soldered the 4.7uf capacitor, as can be seen from the pics. But I'm struggling to find out where I need to solder the other capacitor's I have (from the BOM).

@GertSanders indeed they are capacitors (silly me) - apparently they are 0.1uf - the black one I have already soldered is 4.7uf

Progress!

http://imgur.com/zRvXvrN
http://imgur.com/KpB7daz

A question though. To get to this point, I copied the pictures posted above, but where do I now add these resistors?

http://imgur.com/6mKJcgE

Also, if I want to add a 2AA battery cage, where do I connect the red and black wires to?

Thanks! And sorry for the newb questions!

@m26872 thanks, I've now ordered the missing parts, so hopefully once they arrive I'll be good to go.

Thanks! I asked in the main thread, but what ceramic capacitor are you using there? I see the 4.7uf, can you confirm what the other is?

If I get the orange capacitor and the black one, are those the only capacitors I need for a si7021 temp node?

Thanks

Hi all, I'm seeing replies, but I'm not sure if any are aimed at my question? I think not?

OK, so finally I have received most of the parts I need to build a few of these sensors. I want to go with a temp sensor at first, the si7021. So I wanted to check what "other bits" I need (newb alert).

From there, do I need both 1 and 2? If so, what are these?

From here, what are 3 and 4? Do I need both?

Also, depending on the answers above, do I solder to exactly the same pins? Have I missed anything?

Thanks

OK, so I had some success with the Sensebender, it works sometimes and not other times. I've tried connected directly to the laptop (via the FTDI, no battery connected) and sometimes it works, other times it doesn't. Would this bad soldering?

Also, what's the minimum requirements from a voltage perspective? I've got 2 eneloops which delivers around 2.73volts, whereas the laptop measures 3.3v (tested with a voltmeter tester).

An answer, but a new question:

I have setup a MQTT gateway (with NRF2401, Arduno nano clone, W5100 ethernet) - using the W5100 MQTT client sketch (from here), changing the necessary. I can see that this successfully boots and connects to my MQTT server (on a Pi 2 with Openhab).

0;255;3;0;9;Starting gateway (RNNGA-, 2.0.0-beta)
0;255;3;0;9;Radio init successful.
0;255;3;0;9;Init complete, id=0, parent=0, distance=0
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected

I've also successfully flashed the Sensebender .ino (from here), only changing the "//#deine MY_NODE_ID 3" to uncomment (and also correcting the spelling error )

Interestingly (no idea why) before I had loaded the new sketch on the Sensebender, when powering it on via battery I got the LED coming on, now with the new sketch...nothing. I also can't see it connecting to the gateway (should I see something in the serial monitor on the gateway)?

Or could I have a fried radio?

@rsachoc OK answering my own question after a bit of experimentation and research

Do I need to have the Sensebender connected to battery and the FTDI connected to USB at the time I'm uploading the sketch? No
When I upload the sketch, do I need to select Board: Sensebender Micro and Programmer: USBAsp? Yes
Do I need to "Upload" or "Upload via Programmer"? Upload worked for me

Thank you both, I'll get soldering tomorrow - couple more (extremely rookie) questions:

1. Do I need to have the Sensebender connected to battery and the FTDI connected to USB at the time I'm uploading the sketch?
2. When I upload the sketch, do I need to select Board: Sensebender Micro and Programmer: USBAsp?
3. Do I need to "Upload" or "Upload via Programmer"?

OK so I managed to desolder the bridge and put a dab of solder between the other 2 pins, so I think I have a 3.3v FTDI adaptor. However, I was reading here and I think, because I have the NRF2401 connected to my sensebender, that I might have fried it? Thinking 5v would have broken it?

Also, I'm still confused as to how I connect the FTDI adaptor to the sensebender. mfalkvidd mentioned that I need to go "Vcc to Vcc, GND to GND, RxD to TxD and TxD to RxD", howeverthe sensbender pins don't seem to line up this way?

edit just to be clear, the sensebender goes GND GND VCC RXD TXD DTR while the FTDI goes GND DTR RXI TXO PWR CTS GND, so I'm confused how the pins line up, if that makes any sense?

@HenryWhite thanks! I suspect since I've got nothing to lose the best option is to try and desolder/break the current bridge and try and resolder it. Let me have a go and see what happens.

@HenryWhite definitely a solder bridge, see the picture above (http://i.imgur.com/U9eo7Mc.jpg
), that's why I'm not confident I will be able to sucessfully desolder and solder it.

OK! Update. All the bits and pieces arrived, so I've built the gateway (MQTT client, as I already had an Openhab Pi 2 running MQTT) - this appears to work fine, I can see it connects to the MQTT gateway via the serial monitor.

So the next step is getting the SenseBender Micro (with soldered NRF2401 gateway) to connect to the gateway. I initially thought it would "just work" based on what I read, but I understand that this is with either the "standard" ethernet or wireless gateway, as these assign client ID's automatically. So I need to modify the sketch with a fixed client ID and upload it.

Here's where I'm struggling - I bought an FTDI adaptor, which I thought was 5v and 3.3v, but from what I can see it's 5v. I understand that I therefore need to resolder a little resistor (or something) on the board, but this is so tiny it's beyond my current capability. What other options do I have for getting a new sketch onto the Sensebender?

@AWI said:

@m26872 I don't use any I2C pull-ups. All my Si7021/ SHT21 (GY-21) boards include the SDA/SCL pull-ups (and LDO voltage regulator/ level conversion).

@m26872 said:

@AWI
Oops, it makes me worried that I completely forgot that this project was in some test stage. Ldo and everything should probably be bypassed, but I wanted to test it first. Post edited. Thanks for noticing!

And sorry for everyone else if this caused any trouble.

(It also makes me a little worried about that I have too many ongoing projects right now. )

Apologies again, so that I understand it, does that mean when adding the mentioned temp sensor nodes I need additional parts?

@dakky said:

Anyone want to share some photos with sensors assembled?
Any experiences how long this node will last? I have one DHT11 and one BH1750 onboard and will wake up the node every 5-15 Minutes.

Greetings
Dakky

I would like this too please! I'm trying to decide on which node to use as a motion sensor and temp/humidity sensor and would like to understand how I add a temp/humidty sensor to these and also the battery drain. And also, what temp/humidity sensors are we able to use with this node? I guess it ouputs max 3v, so does that mean the DHT11 and DHT22 are not able to be used here? Sorry for the newbie questions, I'm beginning to explore my options in relation to building my initial temp/humidity sensor and then a motion sensor.

edit OK, so based on what m26872 said here (http://forum.mysensors.org/topic/2715/slim-node-as-a-mini-2aa-battery-pir-motion-sensor/5) I think that I can only use Si7021 or HTU21 sensors as this outputs around 3v? From reading the spec sheet of the DHT11 and 22 I see they need 3.7v, so I guess if I want to use those sensors I need this node (http://forum.mysensors.org/topic/486/my-2aa-battery-sensor)?

Thanks! Apologies, I don't think I was clear enough in my question, so I thought I'd make it easier and post some pictures. What I'm trying to make sure I get right is to solder the "pin thingie" onto the FTDI adapter correctly. It came like this:

http://i.imgur.com/U9eo7Mc.jpg

And my sensebender looks like this (hopefully I got that right).

http://i.imgur.com/LJKzuaP.jpg

What I understand I need to do is to solder the "pin thingie" onto the FTDI adapter and then connect this to the sensebender. So which pins on that do I need to solder to, the ones on the outer edge of the circuit board? Also, does it matter which way I solder i.e. which side the "pin thingie" is on the FTDI adapter?

And I have my first question! I wanted to see how to upload firmware/bootloader to the Microbender, but following this (http://www.mysensors.org/hardware/micro#wiring-things-up) I'm unsure what pins I need to connect.

This picture (http://www.mysensors.org/hardware/micro_ftdi.png) shows the FTDI adapter, but it was provided without the pin connector, and I can't see from the picture exactly which pins I need to solder it to. Any guidance appreciated.

I hope it's OK to start a new thread here! I wanted to use it to document my first steps in building some of the mysensors.org hardware, customised to my specific needs.

First, my initial objectives

1. Build the ethernet/MQTT gateway, for which I'm awaiting a few parts
2. Monitor the temperature in several rooms in the house, so that I can add some EQ3-MAX and the cube to control the thermostats
3. Add some motion sensors to supplement what my house alarm does, by monitoring the house
4. Get Owntracks working
5. Get this all integrated with OpenHab running on a pi2
6. Get a tablet wall mounted with the OpenHab GUI

So far, what I've done

1. Built a single Microbender sensor with the NRF2401 radio module
2. Installed and configured OpenHab on the pi2, connecting to the default interface

Next steps

1. Build the ethernet/MQTT gateway once all the parts arrive
2. Get the temp sensor working with it, including adjusting the temp and humidty to display "real" values
3. Look to build the motion sensors, likely basing them on (http://forum.mysensors.org/topic/2715/slim-node-as-a-mini-2aa-battery-pir-motion-sensor)
4. Buy the EQ-MAX stuff and configure OpenHab

That looks good! As a newbie, I'm currently building an ethernet/MQTT gateway, and my intention is to build some battery powered nodes to connect to the gateway. What I had planned on researching is building a combination temp/humidity/sensor node for some of the bedrooms, so I can check what the temperatures are and whether there is someone present, to then switch the radiators on/off.

So my question is this - can you add a DHT11/DHT22 to this with minimal effort?

Thanks!