nRF5 action!
-
@rmtucker you could try to just solder 2 tiny wires on top of the board for vcc and gnd pins so you don't mess with the connectors for plugin it back on the main board ?
-
@rmtucker said in nRF5 Bluetooth action!:
The only problem is i can not unplug it from the Ble400 because i have no way of connecting wires to the core board because of the smaller pitch pins.
For the current measurement, just program it with the above sketch on your Waveshare, then unplug your module from the BLE400 board and power it using a GND dupont wire and a Vcc dupont wire connected through your uCurrent Gold, or whatever it is that you're using to measure current. I should think that would work, wouldn't it?
Or do you only have the main board without the smaller plug-in module?
It actually looks like a nice setup.
-
I'll try removing the 32.768Khz crystal from an infor-link module and then re-run the sketch that relies on an external interrupt to wake from sleep. Maybe that will get us closer to the theoretical minimum current of just the nRF52832 chip by itself.
-
@rmtucker said in nRF5 Bluetooth action!:
The only problem is i can not unplug it from the Ble400 because i have no way of connecting wires to the core board because of the smaller pitch pins.
For the current measurement, just program it with the above sketch on your Waveshare, then unplug your module from the BLE400 board and power it using a GND dupont wire and a Vcc dupont wire connected through your uCurrent Gold, or whatever it is that you're using to measure current. I should think that would work, wouldn't it?
Or do you only have the main board without the smaller plug-in module?
It actually looks like a nice setup.
-
@NeverDie
Just a little thought on this and a bit of googling.
Just the system on consumption is 1-2uA without the rtc that is needed for wakeup so i don,t think the figures we are getting are that far away from the spec sheet?@rmtucker said in nRF5 Bluetooth action!:
@NeverDie
Just a little thought on this and a bit of googling.
Just the system on consumption is 1-2uA without the rtc that is needed for wakeup so i don,t think the figures we are getting are that far away from the spec sheet?Agreed. We're in the ballpark.
-
@rmtucker said in nRF5 Bluetooth action!:
@NeverDie
Just a little thought on this and a bit of googling.
Just the system on consumption is 1-2uA without the rtc that is needed for wakeup so i don,t think the figures we are getting are that far away from the spec sheet?Agreed. We're in the ballpark.
-
@NeverDie
400,000 hours on 2xAA if we let it sleep.:smile:
That will do for me!.
Now a little playtime and maybe some range testing.@rmtucker said in nRF5 Bluetooth action!:
@NeverDie
400,000 hours on 2xAA if we let it sleep.:smile:
That will do for me!.
Now a little playtime and maybe some range testing.Yeah, I guess I won't amputate the xtal just yet. It can run for quite a while at 6ua. :)
-
So, just did the experiment, and here are the results. Supplying 3.3v to the Ebyte Module, a voltage of 3.0 volts on A4 yields an analogRead(A4) of 4095. Less voltage on A4 yields a lower number.
So, generalizing, I suspect that the reference voltage for analogRead() is Vcc-0.3.
So, you either know Vcc, because of a voltage regulator or something, or else you must call hwCpuVoltage() to get what it is. Then, subtract 0.3v from that, and that's the reference voltage which corresponds to an analogRead() return value of 4095.
:)
@NeverDie said in nRF5 Bluetooth action!:
So, generalizing, I suspect that the reference voltage for analogRead() is Vcc-0.3.
The internal reference is 0.6V the nRF5 MCU's have an internal programmable divider. With Arduino this divider is programmed to 1/5. If you switch to the external reference the "gain" is 1/4.
I measure with my CDEByte 11-15µA for sleep without interrupt waiting. With a RedBear BLE Nano 2 I have measured 15µA. Both compiled as BLE Nano 2. I have used the VC165 multimeter.
-
@rmtucker said in nRF5 Bluetooth action!:
@NeverDie
400,000 hours on 2xAA if we let it sleep.:smile:
That will do for me!.
Now a little playtime and maybe some range testing.Yeah, I guess I won't amputate the xtal just yet. It can run for quite a while at 6ua. :)
I2c is not working properly either.
Here is a test on a HTU21D sensor.HTU21D-F test Temp: -46.57 Hum: 84.10 Temp: 81.10 Hum: 59.68 Temp: 81.10 Hum: 26.48 Temp: -2.64 Hum: 26.48 Temp: 51.58 Hum: 26.48 Temp: 4.91 Hum: 25.02 Temp: 33.74 Hum: 25.02 Temp: 93.45 Hum: 25.02 Temp: 4.22 Hum: 26.48 Temp: 95.51 Hum: 116.81 Temp: -39.02 Hum: 116.81 Temp: 94.14 Hum: 25.02 Temp: 94.14 Hum: 116.81 Temp: 120.22 Hum: 116.81 Temp: -8.82 Hum: 111.44 Temp: 120.22 Hum: 19.64 Temp: 94.14 Hum: 111.44 Temp: -8.82 Hum: 116.81 Temp: 120.22 Hum: 111.44 Temp: 120.22 Hum: 111.44 Temp: 120.22 Hum: 116.81 Temp: -8.82 Hum: 19.64 Temp: 94.14 Hum: 116.81 Temp: 33.05 Hum: 111.44 Temp: 94.14 Hum: 19.64 Temp: 94.14 Hum: 19.64 Temp: 4.22 Hum: 19.64 Temp: 2.84 Hum: 111.44 Temp: 3.53 Hum: 111.44 Temp: -10.20 Hum: 19.64 -
@rmtucker said in nRF5 Bluetooth action!:
I2c is not working properly either.
Seems like there's more than one library named "Wire" that's floating around at the same time. I wonder if perhaps the compiler is finding the proper Wire library inside Arduino-nRF5? Or maybe it's linking with an unrelated Wire library? To answer that, you could try inserting a Serial.println() into the proper library and see if it fires off when you run your code.
-
@rmtucker said in nRF5 Bluetooth action!:
I2c is not working properly either.
Seems like there's more than one library named "Wire" that's floating around at the same time. I wonder if perhaps the compiler is finding the proper Wire library inside Arduino-nRF5? Or maybe it's linking with an unrelated Wire library? To answer that, you could try inserting a Serial.println() into the proper library and see if it fires off when you run your code.
-
I see that Amazon is selling the Arduino Primo now: https://www.amazon.com/Arduino-A000138-low-power-coin-sized-wearables/dp/B073JN7XXR/ref=sr_1_12?ie=UTF8&qid=1501982634&sr=8-12&keywords=nrf52832
First time I've seen it for sale anywhere.
-
I see that Amazon is selling the Arduino Primo now: https://www.amazon.com/Arduino-A000138-low-power-coin-sized-wearables/dp/B073JN7XXR/ref=sr_1_12?ie=UTF8&qid=1501982634&sr=8-12&keywords=nrf52832
First time I've seen it for sale anywhere.
-
@Toyman said in nRF5 Bluetooth action!:
@NeverDie they also has started to sell "big" Primo
Yeah, the big version has Wi-Fi, so I suspect it's meant to function much like a wireless serial gateway.
For the convenience of other readers here, here's a link:
https://www.amazon.com/Arduino-A000135-featuring-Nordic-processor/dp/B0721P6STJ/ref=sr_1_1?ie=UTF8&qid=1502011422&sr=8-1&keywords=arduino+primo -
Maybe you can get much of the same benefits--but at a lower cost--by combining an nRF5 with an ESP8266. Example:
https://www.openhardware.io/view/443/nRF52832-ESP-LINK-Shield-for-ESP8266-Wemos-D1-Mini -
This is strange: now when I do the timed sleep on the infor-link module, it shows a current drain of about 60ua, whereas yesterday it was around 6ua. Maybe I somehow damaged it by connecting a couple of the input pins (A2 and A4) to Vcc? I wouldn't think so, though, because the datasheet says it should be safe to Vcc + 0.3v.
I have one unused infor-link module left. I'll try wiring it up, but without the input pins this time, and measure it. I'm wondering now whether the sleep current will measure out to be 60ua, or 6ua.
-
@rmtucker
Is there a mysensors demo sketch that involves i2c? I could try it on my end, though I expect I'd probably get the same as you.@NeverDie said in nRF5 Bluetooth action!:
Is there a mysensors demo sketch that involves i2c? I could try it on my end, though I expect I'd probably get the same as you.
I have used I2C with an display and u8g2 without any problem.
@NeverDie said in nRF5 Bluetooth action!:
I have one unused infor-link module left. I'll try wiring it up, but without the input pins this time, and measure it. I'm wondering now whether the sleep current will measure out to be 60ua, or 6ua
With the nRF51 there is an bug, after using the debug interface the current consumption is higher until reset.
-
@NeverDie said in nRF5 Bluetooth action!:
Is there a mysensors demo sketch that involves i2c? I could try it on my end, though I expect I'd probably get the same as you.
I have used I2C with an display and u8g2 without any problem.
@NeverDie said in nRF5 Bluetooth action!:
I have one unused infor-link module left. I'll try wiring it up, but without the input pins this time, and measure it. I'm wondering now whether the sleep current will measure out to be 60ua, or 6ua
With the nRF51 there is an bug, after using the debug interface the current consumption is higher until reset.
-
This is strange: now when I do the timed sleep on the infor-link module, it shows a current drain of about 60ua, whereas yesterday it was around 6ua. Maybe I somehow damaged it by connecting a couple of the input pins (A2 and A4) to Vcc? I wouldn't think so, though, because the datasheet says it should be safe to Vcc + 0.3v.
I have one unused infor-link module left. I'll try wiring it up, but without the input pins this time, and measure it. I'm wondering now whether the sleep current will measure out to be 60ua, or 6ua.
@NeverDie said in nRF5 Bluetooth action!:
This is strange: now when I do the timed sleep on the infor-link module, it shows a current drain of about 60ua, whereas yesterday it was around 6ua. Maybe I somehow damaged it by connecting a couple of the input pins (A2 and A4) to Vcc? I wouldn't think so, though, because the datasheet says it should be safe to Vcc + 0.3v.
I have one unused infor-link module left. I'll try wiring it up, but without the input pins this time, and measure it. I'm wondering now whether the sleep current will measure out to be 60ua, or 6ua.
The answer is.... neither. This time, with a fresh infor-link module, it measured at about 16ua.
However, I'm guessing there's quite a lot of noise involved, because this time I noticed I could change the reading just by moving my hand closer or further away from the infor-link module. So, I may have to scope this to see what's going on.
