💬 Easy/Newbie PCB for MySensors


  • Hardware Contributor

    @mr_sensor said in 💬 Easy/Newbie PCB for MySensors:

    @gohan Not a solder problem I think. This is no short on the board it is just the angel of the picture hiding the gap underneath. 🙂
    tried the same set-up with an other dallas sensor. still the same result.

    Still you should read and watch a few videos on YouTube about how to make good solder joints, because your board is not really pretty at the moment 😉
    It's not difficult to make proper "volcano" shaped solder joints when you have learnt the few tricks you need, and it avoids a lot of hair pulling!



  • @sundberg84 I did measure some things. Also replaced the arduino to be sure that it was working (did nt make a difference)

    I found 3,3 volt between vcc and gnd on the sensor. Also between the data-pin of the sensor and the arduino there is continuity.
    The middle leg on the sensor and GND + VCC on the PCB is not resulting in any continuity(I am not really sure if I did measure it in the right way. It is a bit hard to get gnd + vcc on the multimeter pin together).


  • Mod

    have you tried all your setup on a breadboard?


  • Hardware Contributor

    @mr_sensor - ok, then we can exclude PCB and wiring issues. Next is either software or sensor/pro mini failure. I would re-install the library or try anohter one as first thing to do because you said you have tried another sensor and pro mini right?



  • @sundberg84 I tried with other libraries, without success. Also changed the sensor for a new one, without any success. Only thing that made me wondering, now the sensor is on 3,3 volt? When looking at the net for samples, etc. some of them refer to 5volt? So could that be the problem here? Not providing 5 volt to the sensor?


  • Hardware Contributor

    @mr_sensor - no 3.3v is enough:

    0_1520259286284_05be0ac6-fb03-47f8-9938-df9e8b13b156-image.png

    This is really strange... can you confirm it is the right markings on your TO-92 package (actually a temp sensor)?

    0_1520259592581_a2305f4d-04cd-4a60-8bfb-057e3bbbb4fe-image.png

    You could try changing the pin to exclude a pro mini failure (if you have not swapped that one already)

    #define ONE_WIRE_BUS 3 // Pin where dallase sensor is connected
    #define MAX_ATTACHED_DS18B20 16

    You can also test my Ds18b20 code from here but you need to change from RFM69 radio to Nrf24l01+ radio,
    https://github.com/sundberg84/HomeAutomation/blob/master/Sketches MySensors RFM69 radio/RFM_BeerCooler_Temp/RFM_BeerCooler_Temp.ino

    I would also try a bare pro mini + the temp sensor + resistor on a breadboard powered with 3.3v from ftdi adapter.

    I also need you to doublecheck the resistance on that pull-up resistor:
    0_1520260014260_40ed22d0-e2b3-4a27-8a35-2ce7a9648688-image.png

    Im having a hard time to see the exact colors but it that is Yellow, Brown, Gold, Gold that means you have a 4.1 ohm resistor to VCC which is pretty much a short and might have broken the temp sensor. Use a 10k or 56k.



  • @sundberg84 Coincidentally I yesterday had a FTDI powered 3v3 Pro-Mini hooked to a RJ11 socket to test and retrieve addresses using the OneWire.h from two plugged DS18B20 devices to add to those in the chain here already, the resistor was 4k7. The chain of now 12 devices also uses a 4k7 and continues to work flawlessly.



  • @sundberg84 Ok did try with just the bare pro mini + the temp sensor + resistor on a breadboard powered with 3.3v from ftdi adapter.
    And guess what? Than I get the temperature reading 🙂 So why is it not working on the board than? I Will check the soldering again and see if I can solder a new board.

    Dallas Temperature IC Control Library Demo
    Locating devices...Found 1 devices.
    Parasite power is: OFF
    Device 0 Address: 28FF5849011704D8
    Device 0 Resolution: 9
    Requesting temperatures...DONE
    Temp C: 21.00 Temp F: 69.80
    Requesting temperatures...DONE
    Temp C: 21.00 Temp F: 69.80
    Requesting temperatures...DONE
    Temp C: 21.00 Temp F: 69.80
    Requesting temperatures...DONE
    Temp C: 21.00 Temp F: 69.80
    Requesting temperatures...DONE
    Temp C: 21.00 Temp F: 69.80
    Requesting temperatures...DONE
    Temp C: 21.00 Temp F: 69.80
    Requesting temperatures...DONE ```
    
    So both sensor and arduino are working?

  • Hardware Contributor

    Promising! Then you know that hardware is ok... you just have to continue debugging.
    Use the same hardware and software for the PCB. It should work just fine! (I have several working for years now).



  • Hi All,

    Thanks Sundberg84 for creating a board where I can knock out sensors in the matter of minutes instead of hours. 🙂

    That being said, I actually spent many hours on the weekend trying to get my first board to work so I thought that I'd share so it could benefit others.

    I was setting up a 3v3 board with 2 x AA batteries with the battery pad jumpered and using the 3v3 booster. I triple checked the board for continuity.

    I was suffering from !TSM:FPAR:FAIL messages when firing up the node using the FTDI adaptor. I found that the board didn't work when both the battery and FTDI were supplying power.

    Here are my lessons:

    • You need to have a battery connected. This is required to power the radio, as it radio isn't powered by the FTDI adapter
    • You need to remove power from the FTDI adapter. I couldn't disable power on my FTDI adapter so I had to use jumper wires for CTS, DTR, RXD, TXD, and GND between the adapter and the ProMini.

    Thanks again, and I look forward to knocking out some nodes super quick.

    Cheers,
    Simon.


  • Hardware Contributor

    @dbemowsk what I'm worried about is the booster so close to the radio. What do you think @dbemowsk @scalz @Nca78 ?

    alt text


  • Mod

    how about swapping the Extra and Booster section? It makes it cleaner to connect the extra pins to the pro mini.


  • Hardware Contributor

    @sundberg84 i think you already know the answer 😉 (not great regarding emi radiation for example,especially with cheap regulators and inductors.., one downside of relying on external parts,modules but i know your point it's for noobs..)
    I seem to see another thing for your nrf ant, not sure if your nrf 24 goes outside the pcb,if it doesn't then this means you have gnd pour under the ant, not great too in this case



  • @gohan & @sundberg84 For that matter, what about just swapping the Bat.measurer and the booster. You are going to get interference with the inductor being directly next to the antenna.


  • Hardware Contributor

    Thanks guys! (@scalz @gohan @dbemowsk !)
    I think I will relocate the booster... should have thought about that before.
    The NRF antenna goes outside the PCB just like rev 9 so no ground plain for the antenna in normal cases. I might revert it back to allow the PCB to be in range for all directions. Good point.

    I will start with to swap extra and booster to get as much space in between the antenna and inductor.


  • Hardware Contributor

    Something like this...

    0_1521917114887_7092eb47-33ac-4a9c-baf9-c3fd3cd5c658-image.png



  • Would something like this be possible? It would give users that little bit of extra room in the proto area.
    0_1521918858785_911e7f1a-5943-4a40-a49c-e99853681070-image.png


  • Hardware Contributor

    Hi all!

    This has now been update to Rev 10.
    New revision has been sent to PCB manufacturer but It will take some days for them to update their Gerber. (When you order, make sure it says M.Rev 6!

    0_1528107591933_8daa3f55-a3e9-456a-86fe-cbb70d43c8fd-image.png

    Openhardware page has been updated, let me know if you find anything strange.

    RFM69 version will be updated soon as well.



  • Can you please share design of version 9 of the Easy PCB NRF24 edition. I bought 10 pieces a while ago but just decided to use couple. Thank you.


  • Hardware Contributor

    @apl2017 what kind of info are you looking for ? Schematics ?

    0_1528351654852_Rev9 Schem.jpg



  • Just schematic and board layout, exactly what you placed, if possible in a bit better resolution. Thanks a lot!


  • Hardware Contributor

    @apl2017 traveling for my work until next week but will post then.



  • @sundberg84 I just finished my first battery sensor node based on the Easy PCB Rev 9. I have two questions i hope you can help me with:

    The first is about the battery measurement. Because i didn't have a 0.1 uf lying around i used an 0.2 uf capacitor. I am using the following script to measure the battery.

    //=========================
    // BATTERY VOLTAGE DIVIDER SETUP
    // 1M, 470K divider across battery and using internal ADC ref of 1.1V
    // Sense point is bypassed with 0.1 uF cap to reduce noise at that point
    // ((1e6+470e3)/470e3)*1.1 = Vmax = 3.44 Volts
    // 3.44/1023 = Volts per bit = 0.003363075
    #define VBAT_PER_BITS 0.003363075  
    #define VMIN 1.9                                  //  Vmin (radio Min Volt)=1.9V (564v)
    #define VMAX 3.0                                  //  Vmax = (2xAA bat)=3.0V (892v)
    int batteryPcnt = 0;                              // Calc value for battery %
    int batLoop = 0;                                  // Loop to help calc average
    int batArray[3];                                  // Array to store value for average calc.
    int BATTERY_SENSE_PIN = A0;                       // select the input pin for the battery sense point
    //=========================   
    
    
       // Calculate the battery in %
       float Vbat  = sensorValue * VBAT_PER_BITS;
       int batteryPcnt = static_cast<int>(((Vbat-VMIN)/(VMAX-VMIN))*100.);
       Serial.print("Battery percent: "); Serial.print(batteryPcnt); Serial.println(" %");  
    

    Do i need to change anything in the formula? Because i getting reading around the 130%

    Requesting temperature...DONE
    Temperatuur : 26.62 Degrees C
    11935 TSF:MSG:SEND,25-25-0-0,s=5,c=1,t=0,pt=7,l=5,sg=0,ft=0,st=OK:26.6
    Battery percent: 131 %
    Battery Voltage: 3.35 V
    Sleep...
    12945 MCO:SLP:MS=900000,SMS=0,I1=0,M1=1,I2=254,M2=1
    12955 TSF:TDI:TSL
    
    

    If i use the following method:

    //----
       // 1M, 470K divider across battery and using internal ADC ref of 1.1V
       // Sense point is bypassed with 0.1 uF cap to reduce noise at that point
       // ((1e6+470e3)/470e3)*1.1 = Vmax = 3.44 Volts
       // 3.44/1023 = Volts per bit = 0.003363075
       float batteryV  = sensorValue * 0.003363075;
       int batteryPcntNEW = sensorValue / 10;
    
       Serial.print("Battery percent: ");
       Serial.print(batteryPcntNEW);
       Serial.println(" %");
    //----
    

    I am getting: (this is expected, because batteries are new)

    Battery percent: 99 %
    Sleep...
    12945 MCO:SLP:MS=900000,SMS=0,I1=0,M1=1,I2=254,M2=1
    12955 TSF:TDI:TSL
    
    

    My second question is about casing: any tips on which case to use which fit your board and a battery pack? and is as small as possible? Do you perhaps have links of your favourite (Chinese) sellers?


  • Hardware Contributor

    @mister_ik said in 💬 Easy/Newbie PCB for MySensors:

    @sundberg84 I just finished my first battery sensor node based on the Easy PCB Rev 9. I have two questions i hope you can help me with:

    The first is about the battery measurement. Because i didn't have a 0.1 uf lying around i used an 0.2 uf capacitor. I am using the following script to measure the battery.

    Do i need to change anything in the formula? Because i getting reading around the 130%

    Hello, this is normal as your maximum voltage is set at 3V, while initial voltage of an alkaline AA/AAA cell can be a bit over 1.6V. But voltage will quickly drop toward 1.5V (much faster than remaining capacity), so the best instead of changing the maximum voltage is to check the value of batteryPcnt and if it's over 100, just set it to 100.
    Make sure the VBAT_PER_BITS makes you read a voltage that matches the voltage you read with your multimeter, else fix it. Each Atmega is different so you need to calibrate each board.

    For the capacitor it's not a problem, it's just made to stabilize the voltage as it's very sensible to electrical noise. Twice the value will be good enough for this job 🙂


  • Hardware Contributor

    @Nca78 thanks for the help/answer. 😀 About the case I'm using some plastic electronic cases from my hardware shop but @ openhardware you will find some links to 3d projects.

    Let us know @Mister_ik if you need anything else.



  • No sign of the new revision yet:

    0_1528708713299_3aff98ea-8698-4521-8901-7093de8edb7e-image.png


  • Hardware Contributor

    @mickecarlsson - not on the RFM69 version, no. PCBway has updated the NRF24 version so a good sign.
    Something went wrong with the update of the RFM69 version so I had to activate it 21hours ago:

    0_1528709688387_8c18a333-5e8f-4f63-8fd5-be26c87c4b18-image.png

    Lets hope PCBway picks this up today.



  • @sundberg84
    OK, good news. I will check it tomorrow and hopefully order a batch (or two).



  • Still no rev 6 on itead or pcbway for rfm69 version 😞


  • Hardware Contributor

    @mickecarlsson no something went wrong so Rev 5 is ok to order! This is easy rev 10!



  • Hello @sundberg84

    What if feeding a Pro Mini 3.3V (EasyPCB Nrf24l01+ edition rev 10) with regulated power on RAW. (I have 5 VDC). I guess I can feed the radio via the VCC terminal instead of using an external voltage regulator. Can the EasyPCB be used in such a setup?

    Edit: To answer my own question. I should RTFM 👊

    It states clearly that:

    "(If you are using regulated 3.3v, use 5v instructions but skip the voltage regulator and bypass this with a jumper between Vin and Vout"

    Thanks anyway!



  • This post is deleted!


  • @รอเร-อ I have a similar need, but not exactly the same.
    My power route is:
    18650 Lipo (2.7 - 4.2 V) -> TP4056 (charger) -> Booster (5V) -> Raw pin of pro mini 3.3V -> Vcc of pro mini 3.3V -> Radio (NRF24)

    In my case the easy newbie pcb is not directly suitable because the Vout of the Booster is connected to Vcc instead of raw.

    So my idea is to use a modified version of the easy newbie pcb with the schematic posted here
    in order to have more flexibility in the power options.

    Actually I don't have the skills to design a pcb, but maybe, if the idea is good, someone else could design it.

    This schematic is compatible with all the power options actually supported by the easy newbie pcb, and supports also new possibility, simply changing a couple of jumpers


  • Hardware Contributor

    Hello @franz-unix, can't you just bend the output pin of the booster at 90° and solder a wire from it to the raw pin ?



  • @nca78 Yes it should work.

    If I connect the output of the tp4056 to the gnd and reg input of the screw terminal of the easy newbie pcb and then I run a wire from the Vout of the booster to the raw input of the screw terminal, the final result is also quite clean and it is not necessary to solder the wire directly on the pro mini.

    I think that, in this case, the reg jumper must be NOT shortened.



  • Hi,

    I ordered 10 PCBs using "Order from PCBWay" button. It only asked me about PayPal card and din't require any registration on PCBWay. So, everything looks good, PayPal transaction is completed. Can somebody tell me please how can I track it? Probably I'm missing tracking option somewhere... Thank you!

    P.S.
    Cant wait to try it out. 🙂


  • Hardware Contributor

    @zelen I'm not sure. You didn't receive any email? I normally get a email once they are finished and shipped with tracking.



  • This post is deleted!


  • @sundberg84 thank you for clarification. I expected email right after making an order. So, I will wait for finishing production and shipment.



  • I use some of old rev8 boards. I have noticed that I use a ceramic capacitor instead of an electric capacitor compared to the images for the battery measurement. Does it matter? Or should I replace the ceramic capacitor (104) with an electric capacitor?


  • Hardware Contributor

    @harrdy should work just fine.


  • Mod

    @harrdy remember to take a few readings and average out the battery value



  • Hello @sundberg84, I would like to buy the Easy/Newbie PCB for MySensors but I have a few questions
    I want to use it the 5V Arduino Pro mini not the 3V version
    I also want to use the battery monitor
    Is it ok or should I modify "something"
    Also all the pcbs have the battery "expansion: or not?
    Thanks, Emmanuel


  • Mod

    Why would you want to use the 5v arduino on batteries?


  • Hardware Contributor

    @manos

    I want to use it the 5V Arduino Pro mini not the 3V version

    Then you need to use the nrf24l01+ version, that works fine - the RFM69 version needs a 3.3v Pro Mini only.

    I also want to use the battery monitor

    As @gohan said - don't use batteries on a 5v node. Use a 3.3v because it will use up your batteries very quickly. See the guides i have on openhardware for different modes on my PCB.

    Is it ok or should I modify "something"
    Also all the pcbs have the battery "expansion: or not?

    "something" is hard to understand, you can modify i many different ways depending on what you want to do. All the basic "modifications" can be found if you read the project page on openhardware.io



  • @sundberg84 thanks for your response
    If I don't care about battery consumption can I still view and use the battery monitor to be alarmed when battery is empty?


  • Hardware Contributor

    @manos yes you can.



  • This post is deleted!


  • Hello @sundberg84. I watched your video 9+ 'MySensors Battery Node 2xAA - EasyPCB (Nrf24l01+)and Temp Sensor' . I have two questions about this video:

    • I noticed you connected the tempsensor to the extra prototype part of the board, but i could not see in the video how you connected signal pin of the sensor to the arduino.
    • you added a resistor to D5 Temp/Hum, but you did not add the sensor to the mysX2.4 part of the board. Why is that?

  • Hardware Contributor

    @mister_ik said in 💬 Easy/Newbie PCB for MySensors:

    Hello @sundberg84. I watched your video 9+ 'MySensors Battery Node 2xAA - EasyPCB (Nrf24l01+)and Temp Sensor' . I have two questions about this video:

    • I noticed you connected the tempsensor to the extra prototype part of the board, but i could not see in the video how you connected signal pin of the sensor to the arduino.
    • you added a resistor to D5 Temp/Hum, but you did not add the sensor to the mysX2.4 part of the board. Why is that?

    I connect it on the back with a normal wire to D5 resistor input. So both of your observations above are correct.



  • @sundberg84 yes i thought so, but i want to make sure. I have some Rev 10 boards and i was working on a node for my bathroom with a DHT11 sensor. I had some problems with it, therefore watching your video. But it looks like the step up booster was not working correctly. Unfortunately removing the booster i damaged the board because with a new booster the arduino won't get power any more. So this board only works without the booster (and reg jumper connected). Any idea how long this setup (with removed led on arduino) will last on batteries?


  • Hardware Contributor

    @mister_ik - well, 2-4 weeks more or less unless you reprogram the fuses and bootloader.



  • @sundberg84 ooh that is not very long ..i hoped for a couple of months....but then I should consider this board as depreciated and build a new one and use this for development. Thanks for your reaction.


  • Hardware Contributor

    @mister_ik you can always use wired to repair the damaged tracks.



  • @sundberg84, thanks so much for this board, I bought 10 of them. This has made my sensor projects much easier and they look better too! I think I will get some of the RFM69 version next.

    I have a lot of gel lead acid batteries (the 7.2AH type often used in UPSs), and I have been running an earlier prototype off that. I have now just changed over to your board and this is how I modified it to work the way I wanted:

    • Cut the track circled
    • Hard wired from the regulator side of the battery jumper to VCC on the Pro Mini
    • Bridged the booster In to Out
    • Changed the battery measuring resistors to 12k/180k for greater range

    This enabled me to run the board off 12V, keep an eye on the battery voltage, and run the rest from the LE33 regulator. It seems to be managing so far, with 3 x DS18B20 temperature sensors. I'm monitoring the fridge outside, inside and freezer temperatures with this module.

    0_1540535341222_combined board mods 3V3 Reg_20181026_170050.jpg



  • This post is deleted!

  • Hardware Contributor

    @ajay100 - Hi!
    Really nice to see you found your way of using my PCB, its just the way I want it 🙂
    I tried to follow along here, are you using the LEd33 to convert 12v to 3.3v? I guess you tried RAW and the voltage regulator on your pro mini and found out it was bad due to cheap clones?

    If you cut the trace just above the volt.reg and put a jumper from REG to Vin on the Volt reg, and added a jumper from Bat (top) to Reg (top) you would also feed everything with whatever comes out from the LE33.

    0_1540545775768_55d6843d-eb8d-4902-940b-d16101885538-image.png (I think)



  • @sundberg84, I've just tried it and that is a better solution than mine for running everything from the LE33. Thanks for taking the time to work that out!

    Cheers - Andrew



  • Hey @sundberg84 I just saw the new rev.10, congratulations on the upgrade!
    I still have a bunch of rev 9, do you happen to have images/manual for previous version somewhere? link or a pdf?
    Thanks!


  • Hardware Contributor

    @dakipro - sorry, everything was saved here on oh.
    Is there something special you need? I can maybe send it to you, like schematics or what are you looking for?


  • Admin

    Zip files with old revisions get stored on openhardware.io but is not exposed in any good way for the end user today. They're only accessible for the manufacturers.

    I will see if I can show it somehow. Maybe a new tab on the project page listing old revisions with download links.


  • Admin



  • Thank you @hek , I think this might be useful feature
    I however do not see any data in there, is it something for project owner to allow?
    I tried both as guest and as logged inn, I do see the rows, but no data in fields, screenshot:

    0_1542407389061_Screenshot 2018-11-16 23.28.04.png

    @sundberg84 nothing special about now, I figured it out based on older projects. But since I still have about dosen of boards, I will probably need documentation few years from now, so was just hoping to have it somewhere easily available 🙂 Like a downloaded pdf or something


  • Admin

    Thanks for reporting @dakipro. It seems to have been a caching issue in the service. Should not appear again.



  • Me too i still have a bunch of rev 9. Where can i have all the old informations for this rev? I need to see the old webpage with instructions. Thank you !



  • Thanks @hek it is certainly helpful. However the most powerful information is actually in the description page, about how to use the board, how to wire it up for different use cases etc. I suppose a previous version of the information tab is not available?
    If it could be archived (maybe even linked somewhere) it would be really helpful!


  • Admin

    The documentation at the time of the created revision is actually included in the zip as README.md (markdown).
    You should be able to view the file properly formatted in an md-editor or online using I.e.. https://dillinger.io/

    Uploaded images was never included in the revision dumps unfortunately.



  • Ooops, my bad then 😞 I was pretty sure I checked readme.md file, but apparently I got confused.
    Thanks a million!



  • I am also looking for documentation for Rev. 9 that I purchased. The link with revisions that was provided: https://www.openhardware.io/view/4/EasyNewbie-PCB-for-MySensors#tabs-revisions
    lists revisions 1-7, but not 9. All I need is readable schematic and PCB layout in PDF. Thanks.


  • Mod

    @apl2017 I don't know where the revision numbering comes from, but I believe the rev9 you are talking about is called rev5 on the revisions tab.

    Rev 10 was created 2018-06-04. That date matches with rev6 on the revisions tab.

    Perhaps @sundberg84 knows why there are two sets of revision numbers?



  • What software was used to develop this board? My latest KiCad does not read schematic from Rev. 5 ZIP file. All I need is a simple PDF...


  • Hardware Contributor

    @apl2017 - Rev 10 = Kicad, but all below is Eagles.

    This is Rev 9, Nrf24l01+

    0_1546847202029_Rev9 Schem.jpg

    @mfalkvidd - the rev tab in openhardware is the revision for the manufacturer. This doesnt match, because it starts at 0 and ticks up. If you have a board with rev 1 but make a small change without updating the revision number but still wants to upgrade it to the pcb manufacturer you need a new revision for them... so thats causes the confusion. But i think @hek named it M.Rev (Manufacturer revision) to try to keep them apart.



  • Sorry to bother you again (3rd time), still waiting for readable PDF of Rev. 9 schematic and board layout. Thank you


  • Hardware Contributor

    @apl2017 - why pdf? The image above is just as good? It wont present any other info?
    The reason why I ask is that I dont have eagles installed anymore... so its a bit of hassle for me.



  • sundberg84 Don't bother, I went through the hassle, downloaded Eagle and created readable PDF



  • @apl2017 care to share? 🙂



  • Hey, @sundberg84 , I am trying to order the rfm69 version from ITEAD and their M.Rev1 file I downloaded looks to be your v9. Can you upload the v10 to them so I may place an order?



  • Hello, i have built my first sensor based on your PCB. I am of course in learning mode so it refuses to work so far. it is motion detector. I suspect a problem on the radio nrf24 but does not know how to monitor the node with Arduino IDE serial monitor. If i connect the board to the USB the radio is not powered (built the node on battery). and if i connect the battery i have no access to serial monitor. I am afraid to connect both the USB and the batteries and burn the all thing...
    so far i know radio receives power/ PIR receives 3.3 Volts (have configured the PIR to 3.3)/ arduino mini pro led comes on with battery connected.
    Any advice would be really welcome.



  • The radio is only powered by the battery, the battery must be connected to test. Connect both the usb (set to 3.3v) and the battery, no damage will be caused by this.



  • Thanks Stephen. connected both and i can now see what is going on 🙂


  • Hardware Contributor

    @ElCheekytico - I dont know why they wont update to rev 10. I have uploaded the new revision to openhardware... nothing else I can do, sorry.


  • Hardware Contributor

    @pierre1410 - I would suggest you connect the battery, and then the usb/ftdi cable, but only GND, TX and RX fro the usb connection. This will have the node running on the batteries VCC and get you closer to the real deal. Using VCC from the usb adapter might be higher VCC than the batteries, and in worst case scenario it works great with that connected but not when you deploy and only use battery power.



  • @sundberg84 that is exactly what i experienced. thanks for the tip. struggling in fact to have my PIR sensor running on 3.3V. when i connect to the pin on the right of the board (3rd from top).. Arduino IDE serial terminal does not outcome any coherent information.


  • Hardware Contributor

    @pierre1410 ok - well not to get your hopes down but a motion detector on batteries are one of the harder builds. If you are using a booster with the batteries it's harder due to false triggers from the booster noice. Also I believe the quality of your motion detector module determine if it's possible..I've had detectors running fine on 3.3v but several which didn't.



  • Hello, Is there a way to solder a DC-DC booster 3.3V to 5V directly onto the Easy PCB or should it be connected separately to power a PIR for instance? and would that really prevent using 2xAA batteries to power the all thing? have tried to step down the PIR to work at 3.3V but it was not conclusive. Thanks a lot.


  • Hardware Contributor

    @pierre1410 - you can always use the prototyping area for a 3.3 to 5v booster but... booster + PIR might cause false triggers, so choose your booster wisely.



  • @sundberg84, had to migrate my gateway to Ethernet in the meantime but now I am on the PIR/ battery case. i have my booster to 5V in.. will post the results of it...


  • Mod

    @pierre1410 why do you need 5v? There are pir sensors working at 3v and you can even modify the standard pir sensor to work at 3v



  • Hello

    I think there is a mistake in your code (on github) to mesure battery.
    The array have 4 values, but you divide by 3. So you get to high result.
    https://github.com/sundberg84/HomeAutomation/blob/master/BatteryMeasurer/BatteryMeasurer.ino
    On line 77

    Everything else is ok in my case 🙂 the board works well with 2 battery AA, and 47uF cap (not with 4.7uF) .


  • Mod

    Nice catch @barrydou

    The bat array is declared to hold 3 elements

    int batArray[3];
    

    but then 4 values are fetched

    batteryPcnt = (batArray[0] + batArray[1] + batArray[2] + batArray[3]);
    

    batArray[3] is outside of the array, so the ram here could hold any value.

    The code should probably be changed to this

    batteryPcnt = (batArray[0] + batArray[1] + batArray[2]);
    


  • @mfalkvidd : I think you have to change the condition in if too :

    if (batLoop > 1) {
    

    With that, batLoop = 2 when entering in the if (so the 3 values of the array are filled : 0, 1, 2), calculating the average and reseting the batLoop to 0.
    If not modify, the array will be set with batArray[3] just before entering the

    if (batLoop > 2) {
    

    Other way is to set the batArray size to 4 values, and divide by 4 (I'm actually trying that).


  • Hardware Contributor

    @barrydou @mfalkvidd - thanks.
    Wouldnt it be easiest to just "+ batArray[3]" so it is

    batteryPcnt = (batArray[0] + batArray[1] + batArray[2]
    

    the declaration = 3 elements
    batterypct = 3 elements
    batloop > 2 should be correct (0,1 and 2)

    I dont think the code has made any faulty readings since the declaration is only for 3 elements, making batArray[3] never used? (Or always been 0). The batteryPcnt is then divived by 3.


  • Mod

    @sundberg84 batloop > 2 is incorrect, since that means batloop==3 and the code above has just written outside the array, corrupting whatever happened to be there.


  • Hardware Contributor

    We must be ordering EasyPCB alof from PCBway since they used it as an example board for this youtuber:

    PCBWay Circuit Boards - 2 Minute Review📦🛠🔎 – 02:57
    — MKme Lab


  • Hardware Contributor

    @sundberg84 haha gorgeous, I think they only sent open hardware boards, and ran some batches from boards available on openhardware, as except the perfboards they send as free gifts the other real PCBs are MySWeMosIRShield by @emc2 and the RollerShutterNode by @Scalz

    https://www.openhardware.io/view/385/MySWeMosIRShield-IR-blaster-shield-for-WeMos-D1
    https://www.openhardware.io/view/22/Roller-Shutter-Node


  • Hardware Contributor

    Looks nice in red 😉



  • hello, i have a stupid question... on the 3 rows below VCC and GD on your prototyping area; are the rows connected horizontally like a breadboard? thanks


  • Hardware Contributor

    @pierre1410 - no stupid questions, simple answer though, no 🙂

    0_1552248309070_ca19349e-433c-4891-99bc-739fc3c19668-image.png



  • Hello Sundberg84 et al,
    I purchased Easy Newbie PCB (Rev 10) with the hope of jumping into the IoT rave... I tried to create the Gateway - and it works perfectly. I also found and created an advanced Water Sprinkler MyS project by Pete and Co!... that also worked perfectly.

    However, I cant seem to get simpler beginner sketches to work with EasyNewbie. I have soldered the need components (the regulated version). I plan to connect to a 4 relay module, but for now, I am simulating the relay with a simple LED attached to D2. I have uploaded the following sketch which was originally written for version 1.0 MySensors - but have been corrected using guidelines I found for converting 1.0 - 2.0 version. but still no cheese - the controller (Domoticz) displays the Node, but not the complete child nodes, - the LED connected to pin D2 (or D3, D5..) on the Easy Newbie doesn't light up even when I toggle the switches and devices on controller. Don't know what I might be doing wrong, please help.

    // Example sketch showing how to control physical relays. 
    // This example will remember relay state even after power failure.
    
    // Enable debug prints
    #define MY_DEBUG
    
    // Enable and select radio type attached
    #define MY_RADIO_NRF24
    
    #define MY_NODE_ID 4  // Set this to fix your Radio ID or use AUTO or 1
    #define MY_REGISTRATION_FEATURE // Forece registration
    #define MY_REGISTRATION_RETRIES 5
    
    #include <Wire.h>
    #include <TimeLib.h>
    #include <SPI.h>
    #include <MySensors.h>
    #include <LCD.h>
    #include <LiquidCrystal.h>
    #include <LiquidCrystal_I2C.h>
    
    // For Debug
    #ifdef DEBUG_ON
    #define DEBUG_PRINT(x)   Serial.print(x)
    #define DEBUG_PRINTLN(x) Serial.println(x)
    #else
    #define DEBUG_PRINT(x)
    #define DEBUG_PRINTLN(x)
    #define SERIAL_START(x)
    #endif
    
    //#define RELAY_1  2  // Arduino Digital I/O pin number for first relay (second on pin+1 etc)
    #define RELAY_PIN 3
    #define NUMBER_OF_RELAYS 4 // Total number of attached relays
    #define RELAY_ON 0  // GPIO value to write to turn on attached relay
    #define RELAY_OFF 1 // GPIO value to write to turn off attached relay
    #define SKETCH_NAME "Base Relay Node"
    #define SKETCH_VERSION "0.1.2"
    #define CHILD_ID 0
    
    MyMessage msg(1,V_LIGHT);
    
    //void before()
    void setup()
    {
    
      for (int sensor=1, pin=RELAY_PIN; sensor<=NUMBER_OF_RELAYS; sensor++, pin++) {
        // Then set relay pins in output mode
        pinMode(pin, OUTPUT);
        // Set relay to last known state (using eeprom storage)
        digitalWrite(pin, loadState(sensor)?RELAY_ON:RELAY_OFF);
      }
    }
    
    void presentation() { 
      sendSketchInfo(SKETCH_NAME, SKETCH_VERSION);
    
      // Fetch relay status
      for (int sensor=1, pin=RELAY_PIN; sensor<=NUMBER_OF_RELAYS; sensor++, pin++) {
        // Register all sensors to gw (they will be created as child devices)
        //    present(sensor, S_BINARY);
        present(sensor, S_LIGHT);
     
        // Then set relay pins in output mode
        pinMode(pin, OUTPUT);   
        // Set relay to last known state (using eeprom storage) 
        boolean savedState = loadState(sensor);
        digitalWrite(pin, savedState?RELAY_ON:RELAY_OFF);
        send(msg.set(savedState? 1 : 0));
      }
          DEBUG_PRINTLN(F("Sensor Presentation Complete"));
    }
    void loop() 
    {
      // Alway process incoming messages whenever possible
      // Sleep until interrupt comes in on motion sensor. Send update every two minute.
    //  sleep(digitalPinToInterrupt(DIGITAL_INPUT_SENSOR), CHANGE, SLEEP_TIME);
    
    //      update Relays;
      for (int sensor=1, pin=RELAY_PIN; sensor<=NUMBER_OF_RELAYS; sensor++, pin++) {
        // Register all sensors to gw (they will be created as child devices)
        //    present(sensor, S_BINARY);
    send(msg.set(sensor).set(false), false);
    wait(50);
    
    }
    }
    void incomingMessage(const MyMessage &message)
    {
      // We only expect one type of message from controller. But we better check anyway.
      if (msg.type==V_STATUS) {
        // Change relay state
        digitalWrite(msg.sensor-1+RELAY_PIN, msg.getBool()?RELAY_ON:RELAY_OFF);
        // Store state in eeprom
        saveState(msg.sensor, msg.getBool());
        // Write some debug info
        Serial.print("Incoming change for sensor:");
        Serial.print(msg.sensor);
        Serial.print(", New status: ");
        Serial.println(msg.getBool());
      }  
    }
    

  • Hardware Contributor

    @eme - hi!
    Im very sorry, code is not my strong side.
    Do you think its a problem with the hardware?
    Do you have any logs?


 

264
Online

8.9k
Users

9.6k
Topics

100.8k
Posts