nRF5 action!

rmtucker

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

NeverDie

@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

@NeverDie
Yes checked that and it is using the correct wire.h.

NeverDie

@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

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

@NeverDie they also has started to sell "big" Primo

NeverDie

@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

NeverDie

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

NeverDie

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.

d00616

@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.

rmtucker

@d00616 said in nRF5 Bluetooth action!:

I have used I2C with an display and u8g2 without any problem.

Yes But it seems to have trouble reading sensors.
It has been mentioned on sandeepmistry github.

NeverDie

@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.

d00616

@rmtucker said in nRF5 Bluetooth action!:

@d00616 said in nRF5 Bluetooth action!:

I have used I2C with an display and u8g2 without any problem.

Yes But it seems to have trouble reading sensors.
It has been mentioned on sandeepmistry github.

I have found this issue: https://github.com/sandeepmistry/arduino-nRF5/issues/180

Is this yours?

rmtucker

@d00616
No not mine but that is the issue i was talking about.
When connecting DS3231 RTC i get the same as that guy mentions.
When connecting HTU21D the readings are all over the place.

NeverDie

@NeverDie said in nRF5 Bluetooth action!:

@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.

So, I decided to try running it from a 10F 2.7v supercap and see how long it lasts. It reports its voltage once every 5 minutes. I'm using Domoticz to log the values and graph them.

NeverDie

@d00616 said in nRF5 Bluetooth action!:

@rmtucker said in nRF5 Bluetooth action!:
@d00616 said in nRF5 Bluetooth action!:
I have used I2C with an display and u8g2 without any problem.

Yes But it seems to have trouble reading sensors.
It has been mentioned on sandeepmistry github.
I have found this issue: https://github.com/sandeepmistry/arduino-nRF5/issues/180

Is this yours?

Does it rest entirely on Sandeep's shoulders as to if/when it gets fixed? I'm trying to understand how big/small the workforce is.

NeverDie

@rmtucker said in nRF5 Bluetooth action!:

@d00616
No not mine but that is the issue i was talking about.
When connecting DS3231 RTC i get the same as that guy mentions.
When connecting HTU21D the readings are all over the place.

@scalz Have you encountered any I2C problems in your work on Aeos? I seem to recall you have a TH sensor in it.

rmtucker

@NeverDie
Actually i wonder if development has stopped?
no new commits in three months?

rmtucker

@NeverDie
Trouble is the aeos is using nrf52 not nrf51.

NeverDie

@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).

nRF5 action!

12

11.7k

11.2k

113.0k