💬 Ikea Molgan Hack
-
Hello
I would like to know if the pcb sold its virgin or mount.
Thank you in advance and congratulations for the work done... -
Hello
I would like to know if the pcb sold its virgin or mount.
Thank you in advance and congratulations for the work done...@david-fagotin From what I understand the 10xPCB order is for bare PCB's.
A kit is in preparation from one of out suppliers, but I don't think it'll have the SMD parts mounted.
And ofcourse you can always make a donation to me :+1:http://yveaux.blogspot.nl
-
@david-fagotin From what I understand the 10xPCB order is for bare PCB's.
A kit is in preparation from one of out suppliers, but I don't think it'll have the SMD parts mounted.
And ofcourse you can always make a donation to me :+1:@Yveaux said:
From what I understand the 10xPCB order is for bare PCB's.
A kit is in preparation from one of out suppliers, but I don't think it'll have the SMD parts mounted.
And ofcourse you can always make a donation to meIf your kit goes out soon I will wait and I would give you a donation at that time !:stuck_out_tongue_winking_eye:
-
Some short questions as I will start to assemble one of these very soon. Great work @Yveaux !
- What are the SJ1 and 2 parts on the pcb?Just some measurement points where I can cut the trace?
- Why did you put in the pullup for the CS line on the NRF? Never saw that one before
- The wire to the batterie spring is need to be able to use only 2 batteries for the addon pcb, right?
- But you use 3 batteries and both connection points to the main pcb still?
- Any particular reason why you did not make your pcb bigger so that it reaches the + from the main pcb too?
-
Some short questions as I will start to assemble one of these very soon. Great work @Yveaux !
- What are the SJ1 and 2 parts on the pcb?Just some measurement points where I can cut the trace?
- Why did you put in the pullup for the CS line on the NRF? Never saw that one before
- The wire to the batterie spring is need to be able to use only 2 batteries for the addon pcb, right?
- But you use 3 batteries and both connection points to the main pcb still?
- Any particular reason why you did not make your pcb bigger so that it reaches the + from the main pcb too?
- What are the SJ1 and 2 parts on the pcb?Just some measurement points where I can cut the trace?
The solder jumpers are to support ATmega328PB. You need to open them when mounting an PB version.
- Why did you put in the pullup for the CS line on the NRF? Never saw that one before
Habit ;-) With multiple SPI devices on a bus it's good practise to have a pullup on all of the CS lines. Here it isn't really required though.
- The wire to the batterie spring is need to be able to use only 2 batteries for the addon pcb, right?
Yes, the addon runs on 2xAAA, the PIR on 3xAAA
By powering the addon with 2xAAA it can be powered directly without an extra voltage regulator.- But you use 3 batteries and both connection points to the main pcb still?
The original connection points are still required to power the bottom PIR PCB. Both PCB's share a common ground.
- Any particular reason why you did not make your pcb bigger so that it reaches the + from the main pcb too?
This size I could fit more sub-PCB's in a panelized design for the board house. And, as said, the addon PCB doesn't require the + on the main PCB.
-
This one made it on the Adafruit blog:
Great Success Yveaux !!!
-
This one made it on the Adafruit blog:
Great Success Yveaux !!!
-
I finished my first hacked molgan 2 days ago and it's detecting motion really well (and looks so much better than my custom builds).
So overall I love it but it also seems to have one problem: batteries...I started it about 48h ago and the first reading was 2.119V but within some hours it dropped to 2.072V, though today it climbed back up to 2.096V. Thats still 23mV in ~2 days though.
Is this just the discharge curve and some imprecise readings? @Yveaux Whats the consumption of your modules? -
I finished my first hacked molgan 2 days ago and it's detecting motion really well (and looks so much better than my custom builds).
So overall I love it but it also seems to have one problem: batteries...I started it about 48h ago and the first reading was 2.119V but within some hours it dropped to 2.072V, though today it climbed back up to 2.096V. Thats still 23mV in ~2 days though.
Is this just the discharge curve and some imprecise readings? @Yveaux Whats the consumption of your modules? -
So yesterday my molgan started to constantly trigger, which I think might indicate that the voltage is too low. It has dropped down to 1950mV. I will try it with new batteries later today, but the power consumption still seems to be way too high compared to yours @Yveaux.
I have removed R17 to disable all leds and I have changed the fuses and used your sketch. Any idea what might have gone wrong? -
So yesterday my molgan started to constantly trigger, which I think might indicate that the voltage is too low. It has dropped down to 1950mV. I will try it with new batteries later today, but the power consumption still seems to be way too high compared to yours @Yveaux.
I have removed R17 to disable all leds and I have changed the fuses and used your sketch. Any idea what might have gone wrong? -
@LastSamurai can you measure the consumption of individual parts? E.g. The Molgan hardware, the arduino and the radio?
@Yveaux Ok I will try to do that. I did try other (new) batteries though and got the same values (about 2V strangely). Then it started to continuously trigger. I described the problem here.
It's so frustrating, but something seems to be wrong with my whole network I guess.... -
@Yveaux Ok I will try to do that. I did try other (new) batteries though and got the same values (about 2V strangely). Then it started to continuously trigger. I described the problem here.
It's so frustrating, but something seems to be wrong with my whole network I guess.... -
@LastSamurai how did you measure 2V? Measured with a DMM 2XAAA fresh alkaline batteries should be more in the 3V range. This makes a big difference, as at around 2V the Pir starts to behave weird, as you already experienced.
@Yveaux I used the vcc library to let the atmega328 measure the voltage and send it as a sensor value to my controller. I guess I will have to investigate that too. Measuring the batteries outside the case with a multimeter I got 1.5V for each one (without any load though).
-
PS I just measured with the multimeter and the measurements are strange. The board voltage is at about 2.9V (so more like expected) and reaches the atmega as well as the NRF. Overall voltage is at about 4.8V.
The trigger pad seems to be constantly high though (~2.7V) and the node doesn't seem to show up at the gateway anymore. I guess some serial debugging is needed now. Perhaps some component has died... falsy NRF modules would perhaps explain the errors with my nodes :(PPS now the sensor is sending again (strange). The trigger pad is still constantly high though. I guess I will have to desolder the pcb again to have a look at the PIR pcb. Perhaps somethings wrong there...
-
So I took some measurements and and the molgan pcb on its own works just fine. The mysensors pcb with a stable 3.3V power source worked too. When I wanted to measure the power consumption I realized that a fuse in my multimeter was defect... so I am still waiting for a replacement. Will post an update once its here.
-
Sorry for the spam here but I have the fuse now and have just been measuring the pcbs.
- Molgan PIR pcb: 17mA triggered, 7mA otherwise
- mysensors PCB: 18mA sending, 6uA sleeping
The second one looks fine to me but the molgan pcb draws way to much power for battery usage, right?! @Yveaux did you measure the power consumption of yours? I just realized that I did not change the resistor that controls the trigger time. I thought 30s are fine but that makes it draw more power too...
I will also start to test with the second molgan I bought. Really want this to work ;)
-
Sorry for the spam here but I have the fuse now and have just been measuring the pcbs.
- Molgan PIR pcb: 17mA triggered, 7mA otherwise
- mysensors PCB: 18mA sending, 6uA sleeping
The second one looks fine to me but the molgan pcb draws way to much power for battery usage, right?! @Yveaux did you measure the power consumption of yours? I just realized that I did not change the resistor that controls the trigger time. I thought 30s are fine but that makes it draw more power too...
I will also start to test with the second molgan I bought. Really want this to work ;)
@LastSamurai said in 💬 Ikea Molgan Hack:
Sorry for the spam here but I have the fuse now and have just been measuring the pcbs.
No worries, that's what this thread is for, right? ;-)
The second one looks fine to me but the molgan pcb draws way to much power for battery usage, right?! @Yveaux did you measure the power consumption of yours?
I did measure it (when I found out the power usage was less with the regulator, than without) but I can't seem to find the results anymore...
@dynamite mentioned in this thread "The powerconsumption of the PIR when not triggered is approx. 60 uA and when triggered 160 uA.".I just realized that I did not change the resistor that controls the trigger time. I thought 30s are fine but that makes it draw more power too...
Only marginally I guess, unless it triggers all the time.
I will also start to test with the second molgan I bought. Really want this to work ;)
Please do so, at least for comparison.
-
I measured with the new molgan and got nearly the same results. Perhaps my cheap multimeter isn't accurate enough though.
I moved the mysensor pcb to the new molgan pcb and tried this out. Strange result: at first it only send the initial messages but no triggers. After some minutes the opposite happened: it started to randomly trigger (or at least send them). Then after some more time the random triggers stopped and now its working as intended.
Perhaps it just the setup time of the PIR or the warmer air coming from a heater nearby... I will keep an eye on it the next days. -
Ok I did some more testing and the error seems to be pretty random. Sometimes the PIR works as intended for some time, sometimes it just keeps triggering constantly. I am pretty sure sleeping/waking up or sending the message is somehow influencing the PIR (don't know what else it could be).
Does anyone have an idea how to fix this (some wait() code or some cap somewhere perhaps)?
