nRF5 action!
-
@rmtucker said in nRF5 Bluetooth action!:
@NeverDie
Trouble is the aeos is using nrf52 not nrf51.At least it would be something, rather than nothing. Wouldn't you rather be on nRF52 anyway? It has advantages. (I say that even though I do have some nRF51's on order, but only just because they're small and cheap).
-
@rmtucker said in nRF5 Bluetooth action!:
@NeverDie
Trouble is the aeos is using nrf52 not nrf51.At least it would be something, rather than nothing. Wouldn't you rather be on nRF52 anyway? It has advantages. (I say that even though I do have some nRF51's on order, but only just because they're small and cheap).
-
@NeverDie
yes but it would take 4-6weeks and i was impatient so thought i would start with what i could get.
But it seems it does not work on either looking at some of the other issues on sandeeps github.@rmtucker
Hmmmm... Maybe this explains why I didn't notice any MySensor's example demo code that used I2C.On the other hand, I wouldn't think the gap can be all that big if d00616 is able to use I2C for display purposes.
Still, that by itself doesn't get you there.
-
@NeverDie
yes but it would take 4-6weeks and i was impatient so thought i would start with what i could get.
But it seems it does not work on either looking at some of the other issues on sandeeps github. -
On the 10F supercap, the infor-link module was losing about 0.025v per hour, and that included it reporting its voltage every 5 minutes. So, I've hooked it up to a mini solar panel now so that the supercap will charge during daytime, and with that it should run in perpetuity. :)
-
On the 10F supercap, the infor-link module was losing about 0.025v per hour, and that included it reporting its voltage every 5 minutes. So, I've hooked it up to a mini solar panel now so that the supercap will charge during daytime, and with that it should run in perpetuity. :)
-
@mfalkvidd said in nRF5 Bluetooth action!:
@NeverDie nice results! What kind of overcharge protection are you using?
A 2.7v LDO. Very low quiescent current of just 1ua.
-
@mfalkvidd said in nRF5 Bluetooth action!:
@NeverDie nice results! What kind of overcharge protection are you using?
A 2.7v LDO. Very low quiescent current of just 1ua.
-
@NeverDie
yes but it would take 4-6weeks and i was impatient so thought i would start with what i could get.
But it seems it does not work on either looking at some of the other issues on sandeeps github.@rmtucker
I notice someone on AliExpress is selling a similar concept for the nRF52832 to what you're using for the nRF51:
https://www.aliexpress.com/item/NRF52832-Development-Board-NRF52832-Test-Board-Bluetooth-BLE4-2/32824948546.html?spm=2114.search0104.3.1.YoEIHi&ws_ab_test=searchweb0_0,searchweb201602_4_10152_10065_10151_10068_10130_5430020_5410020_10307_10137_10060_10155_10154_5370011_10056_10055_10054_10059_100031_10099_5400020_10103_10102_10052_10053_10142_10107_10050_10051_5380020_5390020_10084_10083_10119_10080_10082_10081_10178_10110_10111_10112_10113_10114_10312_10313_10314_10315_10078_10079_10073_10120_5420011,searchweb201603_19,ppcSwitch_4&btsid=abd93cae-a709-47f9-989d-0c52b4cde846&algo_expid=450d3875-3c65-41c4-99a8-0a2b5eb4479e-0&algo_pvid=450d3875-3c65-41c4-99a8-0a2b5eb4479e&transAbTest=ae803_3 -
I did another sleep current measurement, this time on a Ebyte module that I had mounted to one of my breakout boards. The sleep current measured between 8ua and 9ua. However, it would jump considerably higher depending on whether I was moving or otherwise close to it. I got the lower measurements by positioning myself about 6 feet away (further than that and it gets hard to read the multimeter that's connected to the uCurrent Gold). I've never seen this kind of behavior before in anything other than the nrf52832 boards. Very curious. They're acting almost like proximity detectors. I have no idea what to make of it, but I thought I'd report it in case anyone else here is doing measurements too.
Also, I'm going to avoid exposing the IO pins to voltages that approach Vcc in magnitude. Despite what the datasheet says, they don't seem to handle it well.
-
@Mike_Lemo said in nRF5 Bluetooth action!:
Does anybody know why the function tone() doesn't work for the nrf52?
tone() and other things like NFC are implemented with the new Arduino Primo board. There is no MySensors support at the moment because the Primo comes with the SoftDevice which doesn't allow accessing the complete hardware without using the SoftDevice API, which is not implemented.
-
I did another sleep current measurement, this time on a Ebyte module that I had mounted to one of my breakout boards. The sleep current measured between 8ua and 9ua. However, it would jump considerably higher depending on whether I was moving or otherwise close to it. I got the lower measurements by positioning myself about 6 feet away (further than that and it gets hard to read the multimeter that's connected to the uCurrent Gold). I've never seen this kind of behavior before in anything other than the nrf52832 boards. Very curious. They're acting almost like proximity detectors. I have no idea what to make of it, but I thought I'd report it in case anyone else here is doing measurements too.
Also, I'm going to avoid exposing the IO pins to voltages that approach Vcc in magnitude. Despite what the datasheet says, they don't seem to handle it well.
What you using for pcb design?
I would like to design something for the waveshare core board to plug into similar to what you just designed for the nrf52832 modules to adapt to 2.54mm pitch headers.
Similar to what you did here but with two sockets on top for the waveshare board.
https://www.openhardware.io/view/436/nRF52832-Breakout-Board -
What you using for pcb design?
I would like to design something for the waveshare core board to plug into similar to what you just designed for the nrf52832 modules to adapt to 2.54mm pitch headers.
Similar to what you did here but with two sockets on top for the waveshare board.
https://www.openhardware.io/view/436/nRF52832-Breakout-Board@rmtucker said in nRF5 Bluetooth action!:
What you using for pcb design?
Diptrace.
Very easy to learn. Watch this tutorial series, and in a little more than an hour you'll know enough to use it for doing real work: https://www.youtube.com/playlist?list=PLWy-YwxbAu8EkNv6iMsfLeH6Yahcwejwx
-
@rmtucker said in nRF5 Bluetooth action!:
What you using for pcb design?
However, if you have the time to invest, you might want to learn KiCAD instead (http://kicad-pcb.org/). It's open source and free.
My only real concern about Diptrace is that sharing source files is very, very difficult. Eagle is much better for that, it seems. I'm guessing KiCAD is also good with that, but I can't say that I know for sure.
-
@NeverDie in KiCAD format, I suppose :D But even if it's not easy at least anyone can download Kicad and open them to at have a look without beeing block if you have more than two layers, or too big board.
I'm still using Eagle at the moment, it's the most common software but the changes made in what you can do with the free licence + limitation of PCB size are annoying. At some point I'll have to be strong and make the move to KiCAD... -
What you using for pcb design?
I would like to design something for the waveshare core board to plug into similar to what you just designed for the nrf52832 modules to adapt to 2.54mm pitch headers.
Similar to what you did here but with two sockets on top for the waveshare board.
https://www.openhardware.io/view/436/nRF52832-Breakout-Boardbefore you design your own board:
-
before you design your own board:
@Toyman
Yes i am already running that board at the moment.
But that board consumes around 140uA when sleeping.
It must be the extra electronics like the regulator and uart.
even when feeding the core board with 3.3v directly.
When the core board is on its own it only measures 5uA when sleeping.
