💬 MyMultisensors
-
Cool this is the MySensors martial arts corner ;-) I do Tai Chi Chuan and Tai Chi Sword. The latter I started recently but I'm loving it. We learn the complete form but also sword handling and fighting skills.
-
@carlierd
cool :) yep, I miss time too..I'm lucky to have a mookjong near my desk :) so I can make a break when I have a problem in my work! plus our forms don't take lot of place to train, very pratical, when you are in car or waiting somewhere :laughing:@TheoL
very cool, I hope you enjoy too :) int vs ext? sticking vs pushing hand? direct vs circular? which one is better? none lol! almost same goals, personal style, and finally the fun is it's like playing chess! So the boards I design are always routed with 45° or circular route! no right angle route..nonsense ahah! Be like water my friend :blush:Now, sorry guys, don't laugh, that's embarrassing, I have to stop this (interesting) OT :disappointed: I feel like you I could spend my time to talk about this, sport and wellness...but I shoud try to attract openhardware makers than martialart.com !! So what was I saying??? huum..50 years on coincell?.. :blush:
-
@carlierd
the W not the HW. It's because CW is smaller than the W version. They are software compatible.For the pullup, it's a good practice to be sure to have the right level on the CS line. you can forgot it sometimes, but sometimes not having it on each cs line can be source of useless trouble..
-
@carlierd
yes I know..and sure the cs line can be output=high in the setup sketch part...
briefly for spi, you have: mosi (data output of master/mcu), miso (data input), sck (clock sync). and the CS line is active low when you want to select the chip.
So if for any reason, the CS line is in an unknown state (for instance when mcu reset or other case..), that could give some strange working. And again more trouble, if you have other chip sharing the same spi bus, and no pullup on each CS to give a nice voltage level and choose the right chip..Here a nice article: http://www.dorkbotpdx.org/blog/paul/better_spi_bus_design_in_3_steps
-
Will the board be possible to buy assembled?
-
yep, it's planned. I will try to make this option possible.
sorry for delay, I have lot of other things in progress. but it should not take too much time before I give more news. -
I am very happy because the pir circuit trigger very well, I'm rather impressed. Yeah :smiley:
so far, very few tests because I was playing with software on other things but I've tested two different lens as the pir sensor range is mostly dependant of the lens.- 8308 type
http://www.ebay.com/itm/10-Infrared-Sensor-8308-4-mini-White-Fresnel-Lens-body-pyroelectric-PIR-/141271386262
I got a good 3meter range. - 8120 type
http://www.ebay.com/itm/10-PIECE-White-Fresnel-8120-PIR-infrared-mini-sensor-lights-small-Lenses-/141271544319
Is my favorite for the moment. Compact and a good 5meter. I just move a little bit and it trigger.
I will give more results. I'm working on it today ;) I need to boost..tonight no work! it's champions league final :smile:
- 8308 type
-
and the interesting thing is power consumption (pir circuit only) : 1.8uA in sleep mode, 2.5uA active, promising :)
-
still working nice for the moment :) I have modified my schematic a bit, removed few useless things, and improved others for power consumption and a bit of miniaturization ;)
I am working on the software too. to improve power consumption during blindtime etc.
@hek
I'm using pinchange in my sketch, for few pins. Actually it's raw, I did it with raw registers too, but that's not user friendly and I have already seen this question. I'm looking to make it mysensors now. I am using the EnableInterrupt lib.
So if I use the lib with mysensors I get an error "multiple definition of `__vector_2' ". I see that comes from myHwATmega328 part, from "attachinterrupt".What do you think about this:
- a special define like MYS_USE_EXTINT.
- If defined, in myHwATmega328, in the sleep methods we use the EnableInt lib instead of arduino attachinterrupt
- keep the isr routines for int0 and 1 handled as it is
- and for the others isr, in the main sketch so user/I could do what I want in my irq.
something like this in sketch then,
enableInterrupt(PIR_INT_PINH, irq_pirh, RISING); enableInterrupt(PIR_INT_PINL, irq_pirl, RISING);It's roughly explained :) Is it planned or done? Which way do you prefer??
-
Hi.
so it's still a wip but I'm getting close of what I want :)
because using a coincell (without regul) is more tricky. due to internal res of coin cell ;)An example, the PIR circuit was working nice in standalone (without nothing around, it uses 1.6uA in trigger or not). As soon as I added the atmel chip (and nothing more, no radio at all, no i2c..). Bingo, nice to meet you false triggers!!
This was the coincell which was making me a joke lol As soon as atmel woke up I got a cycling false trigger yeah. In fact having atmel internal 8mhz is enough power hungry to make a nice voltage drop and the pir trigger.
So I solved it in sketch, and a bit of hardware too ;)I am curious to know if others people playing with coincell will have long lifetime without some optimizations (hardware and software..).
So now, the actual state for me this week end, is to connect radio and play again. And add some stuff about listenmode and atc to improve overall..
About my previous post about external int, no more problem, I am using raw registers for external int and sleep function. because I need some custom things. Plus, the more libs and features, the less mem I have and I have not so much space...I will need to disable some debugs lol if I want all my sensors, signing, rfm69 with new mode etc..
I'm not really surprised, I was expecting a bit this behaviour, that's why I said this would be a nice sketch challenge :)
-
@NeverDie saying this you're challenging me lol :) more seriously, I have no real issue.
what would you simplify? can't be more simple imho. no regulator, just batt.. I still can use 2xaa/aaa. That would ease a bit. the circuit works fine as expected ;) but that would be less fun without optimizations ;)Things I have thought when I did my choice:
- as the pir analog is sensitive, I wanted no regul for this one. or I would go for a booster and then more hardware debug (I have already a one cell optimized design that I plan to try with this pir, just to know if there will be a rev2 lol..). But that would need more care&filtering with good quality components (shielded inductors, ferrites, capacitors...) to prevent false trigger.
Like this one I did https://forum.mysensors.org/topic/2951/my-mysx-multisensors-board or my ulpnode clone ;) That would be an overall more expensive solution. but with less maintenance and one cell ;) - use 1uA digital PIR...not cheap
- use a better mcu like cc1310 with its power domains and events. but not mysensors/arduino.
- coincell is just for the fun as this design. and like I said I can use 2 lithium or alkaline.
- as the pir analog is sensitive, I wanted no regul for this one. or I would go for a booster and then more hardware debug (I have already a one cell optimized design that I plan to try with this pir, just to know if there will be a rev2 lol..). But that would need more care&filtering with good quality components (shielded inductors, ferrites, capacitors...) to prevent false trigger.
-
Few pics of another board i have just assembled. I have just noticed I didn't show any proof/pics :confused:
Top view
With this lense, I get 5-6m.
Bottom view, with rfm69, coincell holder and AVRSPI/FTDI connector.
I am waiting for rev 1.1 pcb. No big changes, I improved a bit silkscreen, removed the schmitt trigger to save some power and in place i use pinchange int, makes more sense. Few routes and size changed.
Though, 328p is memory limited, I have to disable debug for this one! -
nothing fancy, just wanted to share how this is working as we're all busy..
there is a small problem with my widgets but no matter :blush: I show you what this board outputs if you're curious, and I'm beginning to like this board :heart_eyes:
I will change my dashboard later, it's just for fun.
For power consumption, few reference for sleep time : old VC506 multimeter but working well + uCurrent Gold
- PIR enabled, other sensors+MCU in deep sleep with interrupt on pins : 4-5uA for Varta CR2032 coincell, 3-4uA for 2xAAA Duracell
- PIR enabled, other sensors+MCU in deep sleep with interrupt on pins + WDT enabled : 11uA for the coincell, 8uA for 2xAAA
- PIR enabled, MCU active 1Mhz, other sensors sleeping with interrupt on pins + WDT enabled : 730-740uA for both
not that bad :)
I have an other proto waiting (for fun because i do not really need it lol). it's another version not for coincell, but as thin and much smaller! with ota back. I thought for coincell, ota or chain tx pulse, was a bit too much battery killer..even if CR2450 imho...and with our preferred lib :) there are multiple chain tx for presentation, some signing stuff etc..and you can't pause this to limit internal resisitance of the coincell..The sketch is still in progress. I mean it's working of course, but still looking to improve a bit things..but i can show you the infos and commands which are available for the controller. That should help to save enough power I think:
// For controller. CHILD_ID are presented. CMDID are not presented to not charge radio tx. But are available from controller, using receive() // CHILD NODE ID/CMD ID Description #define CHILD_ID_PIR 1 // PIR sensor #define CHILD_ID_TEMP 2 // Temperature sensor #define CHILD_ID_HUM 3 // Humidity sensor #define CHILD_ID_LIGHT 4 // Ambiant light Child node ID #define CHILD_ID_BATT_SENSOR 5 // Battery voltage, % is reported by sendbattery stuff #define CHILD_ID_RSSI 6 // Radio rssi #define CHILD_ID_DOOR 7 // Door reed switch #define CHILD_ID_PIR_EN 8 // Enable PIR #define CMID_FULL 10 // Command from controller with all params below in one tx. below is more for debug.. #define CMID_PULSES 11 // Command from controller to set PIR number of pulse for windows time #define CMID_WINDOWTIME 12 // Command from controller to set PIR window time #define CMID_BLINDTIME 13 // Command from controller to set PIR blind time #define CMID_CANCELTIME 14 // Command from controller to set PIR cancel time #define CMID_EN_LIGHT 15 // Command from controller to enable Light sensor threshold #define CMID_LIGHT_MODE 16 // Command from controller to set Light sensor special mode (for instance, enable pir at certain light level only...) #define CMID_LIGHT_H 17 // Command from controller to set Light sensor high threshold #define CMID_LIGHT_L 18 // Command from controller to set Light sensor low threshold #define CMID_LIGHT_DELTA 19 // Command from controller to set difference of lux for update controller #define CMID_TRANSMIT_INTERVAL 20 // Command from controller to set time between sensor updates #define CMID_TH_DELTA 21 // Command from controller to set difference of temp/hum for update controller #define CMID_EN_LED 22 // Command from controller to set ledSee you soon :)
