nRF5 action!
-
@toyman said in nRF5 Bluetooth action!:
Yesterday, I 've got a mailing from my components' supplier featuring new type of cells, Li-MnO2. The cell has all the features needed for nRF5:
- 1200mah capacity
- 1.8-3.0v range
- low cost (ca. $3)
- 41,0 x 24,5 x 5,2 dimensions and, importantly
- up to 120mah peak discharge current.
The link to manufacturer:
http://www.fanso-battery.com/Ultra-thin-Li-MnO2-battery-CP502440-3V1200mAh-pd1905.htmlMhmhmh, a disposable battery that you have to solder I can't see it as a good idea for a node...
@nca78 said in nRF5 Bluetooth action!:
@toyman said in nRF5 Bluetooth action!:
Yesterday, I 've got a mailing from my components' supplier featuring new type of cells, Li-MnO2. The cell has all the features needed for nRF5:
- 1200mah capacity
- 1.8-3.0v range
- low cost (ca. $3)
- 41,0 x 24,5 x 5,2 dimensions and, importantly
- up to 120mah peak discharge current.
The link to manufacturer:
http://www.fanso-battery.com/Ultra-thin-Li-MnO2-battery-CP502440-3V1200mAh-pd1905.htmlMhmhmh, a disposable battery that you have to solder I can't see it as a good idea for a node...
well, 1200mah will last AT LEAST for a year (two in real life). I have no issues resoldering 2 joints once a year, given it gives AAA capacity in a much smaller package
-
Speaking of batteries, I found only one proper holder for holding two CR2032's in series:

It turns out you pretty much need the plastic carrier to guarantee that the edge of the button cell doesn't short out against the side of the metal holding bracket. -
Speaking of batteries, I found only one proper holder for holding two CR2032's in series:

It turns out you pretty much need the plastic carrier to guarantee that the edge of the button cell doesn't short out against the side of the metal holding bracket.@neverdie said in nRF5 Bluetooth action!:
Speaking of batteries, I found only one proper holder for holding two CR2032's in series:
There are CR2477 (560mAh) or CR2450 (950mAh) 3V cells. Maybe its's better to handle.
-
Yesterday, I 've got a mailing from my components' supplier featuring new type of cells, Li-MnO2. The cell has all the features needed for nRF5:
- 1200mah capacity
- 1.8-3.0v range
- low cost (ca. $3)
- 41,0 x 24,5 x 5,2 dimensions and, importantly
- up to 120mah peak discharge current.
The link to manufacturer:
http://www.fanso-battery.com/Ultra-thin-Li-MnO2-battery-CP502440-3V1200mAh-pd1905.html@toyman said in nRF5 Bluetooth action!:
41,0 x 24,5 x 5,2 dimensions and, importantly
Footprint seems kinda large, at least for nodes intended to be small. It trades off length in order to get thin. In contrast, a CR123 is shorter (34.5mm), but thicker (17mm), but can deliver 1.5a continuous (which makes it very tempting for powering a PA):
https://www.batteryjunction.com/energizer-cr123a.html
On the other hand, when you add the CR123 holder, the length may be comparable.If you decide to try out the fanso, please do let us know how you like it.
-
@neverdie said in nRF5 Bluetooth action!:
Speaking of batteries, I found only one proper holder for holding two CR2032's in series:
There are CR2477 (560mAh) or CR2450 (950mAh) 3V cells. Maybe its's better to handle.
@d00616 said in nRF5 Bluetooth action!:
There are CR2477 (560mAh) or CR2450 (950mAh) 3V cells. Maybe its's better to handle.
Good point. I think maybe the only actual justified use of two CR2032's in series is to power the AM612, which requires a voltage of at least 2.7v.
-
Did someone get an NRF52 working with an ESP8266(ESP32) and successfully connected it to a controller?
Since my controller is something stuffed away in a closet, Id like to have a gateway that's positioned more centralized. An ESP+NRF52832 would be a lovely cost-efficient solution.
-
Did someone get an NRF52 working with an ESP8266(ESP32) and successfully connected it to a controller?
Since my controller is something stuffed away in a closet, Id like to have a gateway that's positioned more centralized. An ESP+NRF52832 would be a lovely cost-efficient solution.
@omemanti said in nRF5 Bluetooth action!:
Did someone get an NRF52 working with an ESP8266(ESP32) and successfully connected it to a controller?
Yes: https://www.openhardware.io/view/491/PA-LNA-nRF52832-ESP-LINK-Shield-for-Wemos-D1-Mini-ESP8266
Works great! :)
-
@omemanti said in nRF5 Bluetooth action!:
Did someone get an NRF52 working with an ESP8266(ESP32) and successfully connected it to a controller?
Yes: https://www.openhardware.io/view/491/PA-LNA-nRF52832-ESP-LINK-Shield-for-Wemos-D1-Mini-ESP8266
Works great! :)
-
@nagelc No, you want to change the values in the MyBoardNRF5.h file instead. For an example, see the source code in: https://www.openhardware.io/view/499/10-years-wireless-PIR-Sensor-on-just-one-set-of-3-AAs#tabs-source
So, in your case, you'd want:
#define PIN_SERIAL_TX (10)and, to avoid conflicts, make sure that pin P0.10 isn't defined anywhere in the same .h file as something else already. If it is, you may need to change that as well.
-
How can I connect to DEC5 as an I/O when using MyBoardNRF5?
The Ebyte Module Datasheet says: 14 DEC5 Input/Output MCU GPIO to it should be possible?
-
@omemanti Suggest you check the Nordic datasheet on that rather than rely on the Ebyte documentation. IIRC, the DECT pins are not GPIO, but it's worth your double checking the nRF52 datasheet if it's important to you.
@neverdie, Indeed, I checked and it was false. well goes to show that late-night prototyping has some disadvantages, my bad, :)
Deleted Following up question..
DK =>Ebyte module
GND(detect) => GND
SWDIO => SWDIO
SWDCLK => SWCLK
VTG => 3,3V
3,3V => 3,3V
GND =>GND -
Has anyone succeeded in programming the WT51822-S4AT module (the cheapest and tiny nrf51822 module on AliExpress) using NRF52 DK ?
I pulled a lot of hair trying to find out what I did wrong with my board, I soldered an adapter to make sure I didn't have problems with faulty jumper wires etc, I reinstalled JLink and Nordic software, in the end I desoldered everything on my board, then the module itself to program it independantly. It always failed and JLink couldn't connect to it. I tried the other spare one I had, same result. I tried the one I'm sure I managed to program long ago with a jlink clone, always the same result.
Then I tried with an old nrf51822 module I bought long ago on AliExpress, and no problem !Has anyone had similar problems ? Is there something special hardware wise that I should check ?
-
Has anyone succeeded in programming the WT51822-S4AT module (the cheapest and tiny nrf51822 module on AliExpress) using NRF52 DK ?
I pulled a lot of hair trying to find out what I did wrong with my board, I soldered an adapter to make sure I didn't have problems with faulty jumper wires etc, I reinstalled JLink and Nordic software, in the end I desoldered everything on my board, then the module itself to program it independantly. It always failed and JLink couldn't connect to it. I tried the other spare one I had, same result. I tried the one I'm sure I managed to program long ago with a jlink clone, always the same result.
Then I tried with an old nrf51822 module I bought long ago on AliExpress, and no problem !Has anyone had similar problems ? Is there something special hardware wise that I should check ?
@nca78 said in nRF5 Bluetooth action!:
Has anyone succeeded in programming the WT51822-S4AT module (the cheapest and tiny nrf51822 module on AliExpress) using NRF52 DK ?
Yes. Haven't had a problem.
A couple things:
- Are you powering the nRF51 module externally (separate from the nRF52DK)? It's highly advisable that you do, even though by random luck, you can sometimes succeed without it.
- Especially for new, unprogrammed modules, you need to do a bulk erase at the beginning. I do this by the d00616 trick of saying "Burn bootloader" with a null bootloader. The burning bootloader process fails, as expected, but the side-effect is that it does a bulk-erase before failing.
I know you know these things, but sometimes we forget to do what we know.
-
@nca78 said in nRF5 Bluetooth action!:
Has anyone succeeded in programming the WT51822-S4AT module (the cheapest and tiny nrf51822 module on AliExpress) using NRF52 DK ?
Yes. Haven't had a problem.
A couple things:
- Are you powering the nRF51 module externally (separate from the nRF52DK)? It's highly advisable that you do, even though by random luck, you can sometimes succeed without it.
- Especially for new, unprogrammed modules, you need to do a bulk erase at the beginning. I do this by the d00616 trick of saying "Burn bootloader" with a null bootloader. The burning bootloader process fails, as expected, but the side-effect is that it does a bulk-erase before failing.
I know you know these things, but sometimes we forget to do what we know.
@neverdie said in nRF5 Bluetooth action!:
- Especially for new, unprogrammed modules, you need to do a bulk erase at the beginning. I do this by the d00616 trick of saying "Burn bootloader" with a null bootloader. The burning bootloader process fails, as expected, but the side-effect is that it does a bulk-erase before failing.
if bulk erase is needed, then it means it was programmed ;) a fresh new mcu is usually not programmed unless you ask for it to the manufacturer..
Like said above, it could be a problem with module, power issue, usb & cable, dupont cable, jlink, jlink setup, arduino core etc.
-
@nca78 said in nRF5 Bluetooth action!:
Has anyone succeeded in programming the WT51822-S4AT module (the cheapest and tiny nrf51822 module on AliExpress) using NRF52 DK ?
Yes. Haven't had a problem.
A couple things:
- Are you powering the nRF51 module externally (separate from the nRF52DK)? It's highly advisable that you do, even though by random luck, you can sometimes succeed without it.
- Especially for new, unprogrammed modules, you need to do a bulk erase at the beginning. I do this by the d00616 trick of saying "Burn bootloader" with a null bootloader. The burning bootloader process fails, as expected, but the side-effect is that it does a bulk-erase before failing.
I know you know these things, but sometimes we forget to do what we know.
@neverdie said in nRF5 Bluetooth action!:
- Are you powering the nRF51 module externally (separate from the nRF52DK)? It's highly advisable that you do, even though by random luck, you can sometimes succeed without it.
I was at the beginning, but after that I tried with power from the DK. I will try again with external power.
- Especially for new, unprogrammed modules, you need to do a bulk erase at the beginning. I do this by the d00616 trick of saying "Burn bootloader" with a null bootloader. The burning bootloader process fails, as expected, but the side-effect is that it does a bulk-erase before failing.
I can't even reach that step, JLink can't establish the SWD connection so there's no way to erase the chip.
-
@neverdie said in nRF5 Bluetooth action!:
- Are you powering the nRF51 module externally (separate from the nRF52DK)? It's highly advisable that you do, even though by random luck, you can sometimes succeed without it.
I was at the beginning, but after that I tried with power from the DK. I will try again with external power.
- Especially for new, unprogrammed modules, you need to do a bulk erase at the beginning. I do this by the d00616 trick of saying "Burn bootloader" with a null bootloader. The burning bootloader process fails, as expected, but the side-effect is that it does a bulk-erase before failing.
I can't even reach that step, JLink can't establish the SWD connection so there's no way to erase the chip.
@nca78 said in nRF5 Bluetooth action!:
I was at the beginning, but after that I tried with power from the DK. I will try again with external power.
I use a battery pack with a 3.3v regulator as the external power source. Don't just use 2xAA. If the voltage is too low, it will fail to program.
-
@neverdie said in nRF5 Bluetooth action!:
- Especially for new, unprogrammed modules, you need to do a bulk erase at the beginning. I do this by the d00616 trick of saying "Burn bootloader" with a null bootloader. The burning bootloader process fails, as expected, but the side-effect is that it does a bulk-erase before failing.
if bulk erase is needed, then it means it was programmed ;) a fresh new mcu is usually not programmed unless you ask for it to the manufacturer..
Like said above, it could be a problem with module, power issue, usb & cable, dupont cable, jlink, jlink setup, arduino core etc.
@scalz said in nRF5 Bluetooth action!:
if bulk erase is needed, then it means it was programmed a fresh new mcu is usually not programmed unless you ask for it to the manufacturer..
Well, you would think so, and yet it seems I always need to do it anyway on a new module. Go figure.