nRF5 action!
-
I found it on some modules from Sunfounder on red PCB but they have fake nrf24 chip and still performed bad but a little better than the other chinese clones (range 7 meters indoor instead of 5)
@gohan said in Minimalist SAMD21 TQFP32 Pro Mini:
I found it on some modules from Sunfounder on red PCB but they have fake nrf24 chip and still performed bad but a little better than the other chinese clones (range 7 meters indoor instead of 5)
Interestingly, the antenna on the DK is sort-of hockey stick shaped. I guess they didn't need to compress it, since the board is so large anyway.
-
@Nca78
You're right. Especially after outfitting the atmega328p with an RTC, the cost is more of a wash. I think the RFM still wins on range, but maybe the 832 will be "good enough"...@NeverDie said in Minimalist SAMD21 TQFP32 Pro Mini:
You're right. Especially after outfitting the atmega328p with an RTC, the cost is more of a wash. I think the RFM still wins on range, but maybe the 832 will be "good enough"...
The question is, when 832 modules are available. After announcing the nRF52832 with its preview DK, I have waited from 06/2015 to 08/2016 until modules are available for an acceptable price at aliexpress or ebay.
I think the atmega is a slow 8-bit MCU with less RAM. The limited RAM requires to transmit additional nonce packages, when signing is enabled. SoftSigning hashing is 76 times faster. A faster CPU allows to shorten the active time:
- atmega328 14000µs
- nRF51 1739µS
- ESP8266 380µS
- nRF52 183µS
The NRF24 has problems with clones, range and the limitation of packages to 32 bytes. The nRF52 allows to change the packet format to support >32 bytes packages.
At the moment sleep modes are only implemented for 328 and nRF5.
OTA updates are available for 328 and ESP8266. For nRF5 it requires to implement a boot loader. The internal flash should have enough capacity to store a simple bootloader and a firmware update.
If you plan to do a lot of writes into EEPROM the 328 has a real EEPROM. The SAMD requires an external EEPROM, the nRF5/Teensy/STM32F emulating the eeprom in Flash. The nRF5 is using the NVM driver, which allows much more writes to the emulated EEPROM. The price for NVM is some time for log cleaning after some hundreds writes.
IMHO the best MCU for creating new battery powered sensors is the nRF5 stating with a ~3€ board, if required in combination with RFM modules.
@NeverDie said in Minimalist SAMD21 TQFP32 Pro Mini:
I'm guessing that if I were to desolder the rFM52832 from the DK, then I could use the DK to program other chips using the SW pins by using the J-link that's part of the board.
I think it's simpler to use one of the ST-LINK v2 clones. The DK board should be good for development, debugging and current measurement.
-
@NeverDie said in Minimalist SAMD21 TQFP32 Pro Mini:
You're right. Especially after outfitting the atmega328p with an RTC, the cost is more of a wash. I think the RFM still wins on range, but maybe the 832 will be "good enough"...
The question is, when 832 modules are available. After announcing the nRF52832 with its preview DK, I have waited from 06/2015 to 08/2016 until modules are available for an acceptable price at aliexpress or ebay.
I think the atmega is a slow 8-bit MCU with less RAM. The limited RAM requires to transmit additional nonce packages, when signing is enabled. SoftSigning hashing is 76 times faster. A faster CPU allows to shorten the active time:
- atmega328 14000µs
- nRF51 1739µS
- ESP8266 380µS
- nRF52 183µS
The NRF24 has problems with clones, range and the limitation of packages to 32 bytes. The nRF52 allows to change the packet format to support >32 bytes packages.
At the moment sleep modes are only implemented for 328 and nRF5.
OTA updates are available for 328 and ESP8266. For nRF5 it requires to implement a boot loader. The internal flash should have enough capacity to store a simple bootloader and a firmware update.
If you plan to do a lot of writes into EEPROM the 328 has a real EEPROM. The SAMD requires an external EEPROM, the nRF5/Teensy/STM32F emulating the eeprom in Flash. The nRF5 is using the NVM driver, which allows much more writes to the emulated EEPROM. The price for NVM is some time for log cleaning after some hundreds writes.
IMHO the best MCU for creating new battery powered sensors is the nRF5 stating with a ~3€ board, if required in combination with RFM modules.
@NeverDie said in Minimalist SAMD21 TQFP32 Pro Mini:
I'm guessing that if I were to desolder the rFM52832 from the DK, then I could use the DK to program other chips using the SW pins by using the J-link that's part of the board.
I think it's simpler to use one of the ST-LINK v2 clones. The DK board should be good for development, debugging and current measurement.
@d00616 said in Minimalist SAMD21 TQFP32 Pro Mini:
I think it's simpler to use one of the ST-LINK v2 clones. The DK board should be good for development, debugging and current measurement.
What exactly do I need to do to get it work? I tried it from Windows, and failed. I seem to recall you said you got it to work from Linux after changing a definition. Would you mind showing the steps, or providing a link on how to do that?
-
@NeverDie said in Minimalist SAMD21 TQFP32 Pro Mini:
You're right. Especially after outfitting the atmega328p with an RTC, the cost is more of a wash. I think the RFM still wins on range, but maybe the 832 will be "good enough"...
The question is, when 832 modules are available. After announcing the nRF52832 with its preview DK, I have waited from 06/2015 to 08/2016 until modules are available for an acceptable price at aliexpress or ebay.
I think the atmega is a slow 8-bit MCU with less RAM. The limited RAM requires to transmit additional nonce packages, when signing is enabled. SoftSigning hashing is 76 times faster. A faster CPU allows to shorten the active time:
- atmega328 14000µs
- nRF51 1739µS
- ESP8266 380µS
- nRF52 183µS
The NRF24 has problems with clones, range and the limitation of packages to 32 bytes. The nRF52 allows to change the packet format to support >32 bytes packages.
At the moment sleep modes are only implemented for 328 and nRF5.
OTA updates are available for 328 and ESP8266. For nRF5 it requires to implement a boot loader. The internal flash should have enough capacity to store a simple bootloader and a firmware update.
If you plan to do a lot of writes into EEPROM the 328 has a real EEPROM. The SAMD requires an external EEPROM, the nRF5/Teensy/STM32F emulating the eeprom in Flash. The nRF5 is using the NVM driver, which allows much more writes to the emulated EEPROM. The price for NVM is some time for log cleaning after some hundreds writes.
IMHO the best MCU for creating new battery powered sensors is the nRF5 stating with a ~3€ board, if required in combination with RFM modules.
@NeverDie said in Minimalist SAMD21 TQFP32 Pro Mini:
I'm guessing that if I were to desolder the rFM52832 from the DK, then I could use the DK to program other chips using the SW pins by using the J-link that's part of the board.
I think it's simpler to use one of the ST-LINK v2 clones. The DK board should be good for development, debugging and current measurement.
@d00616 said in Minimalist SAMD21 TQFP32 Pro Mini:
IMHO the best MCU for creating new battery powered sensors is the nRF5 stating with a ~3€ board, if required in combination with RFM modules.
The board you linked to is an nRF51. Which do you prefer? nRF51 or nRF52?
-
Looks as though the nRF52832 beats the nRF51832 on Rx sensitivity at 1mbps. The nRF51832 is:
• -90 dBm at 1 Mbps
versus -93dBm at 1Mbps for the nRF52832.On the other hand, the nRF51832 has -96dBm receive sensitivity at 250kbps, and the nRF52832 appears to lack that mode altogether. So, in a way, that make sthe nRF51832 seem a bit more attractive on range, even if one has to pay a price on bitrate.
-
@d00616 said in Minimalist SAMD21 TQFP32 Pro Mini:
IMHO the best MCU for creating new battery powered sensors is the nRF5 stating with a ~3€ board, if required in combination with RFM modules.
The board you linked to is an nRF51. Which do you prefer? nRF51 or nRF52?
@d00616 Now that you mention it, that board you linked to ( https://www.aliexpress.com/item/BLE4-0-Bluetooth-2-4GHz-Wireless-Module-NRF51822-Board-Core51822-B/32633417101.html?spm=2114.search0104.3.18.Q9naea&ws_ab_test=searchweb0_0,searchweb201602_5_10152_10065_10151_10068_10130_10084_10083_10119_10080_10082_10081_10110_10178_10136_10137_10111_10060_10112_10113_10155_10114_5360016_10154_438_10056_10055_10054_10182_10059_100031_10099_10078_10079_10103_10073_10102_10120_10189_10052_10053_10142_10107_10050_10051,searchweb201603_5,ppcSwitch_4&btsid=f45d662b-6a09-4449-9bee-1ea58d9beab8&algo_expid=53f99b5d-bb10-4b34-a548-2a3e4c0cd96e-2&algo_pvid=53f99b5d-bb10-4b34-a548-2a3e4c0cd96e ) would be an interesting way to control an RFM69, especially if it could do an OTA sketch uploade. Can it?
-
@d00616 said in Minimalist SAMD21 TQFP32 Pro Mini:
IMHO the best MCU for creating new battery powered sensors is the nRF5 stating with a ~3€ board, if required in combination with RFM modules.
The board you linked to is an nRF51. Which do you prefer? nRF51 or nRF52?
@NeverDie said in Minimalist SAMD21 TQFP32 Pro Mini:
The board you linked to is an nRF51. Which do you prefer? nRF51 or nRF52?
I prefer to use nRF52 controllers when the price doesn't matter.
@NeverDie said in Minimalist SAMD21 TQFP32 Pro Mini:
Now that you mention it, that board you linked to would be an interesting way to control an RFM69, especially if it could do an OTA sketch uploade. Can it?
OTA sketch upload is on my todo list, but not at the first position ;-)
-
Looks as though the nRF52832 beats the nRF51832 on Rx sensitivity at 1mbps. The nRF51832 is:
• -90 dBm at 1 Mbps
versus -93dBm at 1Mbps for the nRF52832.On the other hand, the nRF51832 has -96dBm receive sensitivity at 250kbps, and the nRF52832 appears to lack that mode altogether. So, in a way, that make sthe nRF51832 seem a bit more attractive on range, even if one has to pay a price on bitrate.
@NeverDie said in Minimalist SAMD21 TQFP32 Pro Mini:
On the other hand, the nRF51832 has -96dBm receive sensitivity at 250kbps, and the nRF52832 appears to lack that mode altogether.
The 250kbps mode is working with the nRF5232 but this was the last chip supporting this mode.
-
This module is interesting because it looks as though it would be relatively easy to attach to most simple sensor projects:
https://www.aliexpress.com/store/product/NRF52832-Bluetooth-4-2-module-Bluetooth-5-program-PCBA-serial-transmission-cost-effective/1383441_32818791344.html -
I found some useful connectors:
1.27mm pitch seems to be what's most common with nRF52 stuff.
-
@gohan said in Minimalist SAMD21 TQFP32 Pro Mini:
what would you use those connectors for?
The J-Tag ones for connecting a J-tag programmer to an nRF5 board (e.g. the adafruit one has holes for such a 2x5 connector already on its PCB).
The 1.27mm headers I think I might use for connecting some of the small nRF5 boards which have 1.27mm pitch through-holes onto some prototypes rather than just soldering them down. That way I can easily move them to the next version of the prototype without creating a lot of desoldering work.
I've ordered all of the above earlier today. I'm just providing the links in case others may want to do the same.
-
This module is interesting because it looks as though it would be relatively easy to attach to most simple sensor projects:
https://www.aliexpress.com/store/product/NRF52832-Bluetooth-4-2-module-Bluetooth-5-program-PCBA-serial-transmission-cost-effective/1383441_32818791344.html@NeverDie Thanks for the nrf link, but I liked the units with coin cell better. I purchased 2.
-
@NeverDie Thanks for the nrf link, but I liked the units with coin cell better. I purchased 2.
-
@NeverDie Thanks for the nrf link, but I liked the units with coin cell better. I purchased 2.
@Terrence said in Minimalist SAMD21 TQFP32 Pro Mini:
@NeverDie Thanks for the nrf link, but I liked the units with coin cell better. I purchased 2.
This module looks great. Both oscillators and the inductor is placed ob board. But the SWDIO and SDCLK are not connected. You can only flash via OTA update. Don't flash MySensors until you have moved the used Flash by NVM driver. The NVM would overwrite the DFU bootloader. It's possible that the nRF5 code needs changes to support running on an nRF5 with Softdevice.
@scalz is playing/plans to play with Nordics OTA update.
-
A couple more interesting finds.
-
This one is small but includes a PA, so you can allegedly get 20dBm+ in TX:
https://www.aliexpress.com/item/PTR5618PA-Nordic-nRF52832-Module-PA-module-BLE-4-0-Module-Free-shipping/32761051086.html?spm=2114.search0104.3.9.W4RMn3&ws_ab_test=searchweb0_0,searchweb201602_5_10152_10065_10151_10068_10130_9947_10084_10083_10119_10080_10082_10081_10136_10110_10178_10137_10111_10060_10112_10113_10155_10114_10154_438_10056_10055_10054_10182_10059_100031_10099_10078_10079_10103_10073_10102_10120_5360020_10189_10052_10053_10142_10107_10050_10051-9947,searchweb201603_5,ppcSwitch_4&btsid=66711830-6dac-41e4-9674-fe24475ac9f5&algo_expid=4a176404-eb42-4313-9eae-531e59e60ccf-1&algo_pvid=4a176404-eb42-4313-9eae-531e59e60ccf -
This one allegedly includes not only a PA, but an LNA too:
https://www.aliexpress.com/item/nRF52832-LNA-PA-Range-Extension-EV-Board-best-sol-for-the-coming-Bluetooth-5-0-and/32778491443.html?spm=2114.search0104.3.2.W4RMn3&ws_ab_test=searchweb0_0,searchweb201602_5_10152_10065_10151_10068_10130_9947_10084_10083_10119_10080_10082_10081_10136_10110_10178_10137_10111_10060_10112_10113_10155_10114_10154_438_10056_10055_10054_10182_10059_100031_10099_10078_10079_10103_10073_10102_10120_5360020_10189_10052_10053_10142_10107_10050_10051-9947,searchweb201603_5,ppcSwitch_4&btsid=66711830-6dac-41e4-9674-fe24475ac9f5&algo_expid=4a176404-eb42-4313-9eae-531e59e60ccf-0&algo_pvid=4a176404-eb42-4313-9eae-531e59e60ccf
Awfully expensive though.
-
-
Attractive form factor, but I believe that it's just a beacon. If not, how do you connect it to anything?
-
@Terrence said in Minimalist SAMD21 TQFP32 Pro Mini:
@NeverDie Thanks for the nrf link, but I liked the units with coin cell better. I purchased 2.
This module looks great. Both oscillators and the inductor is placed ob board. But the SWDIO and SDCLK are not connected. You can only flash via OTA update. Don't flash MySensors until you have moved the used Flash by NVM driver. The NVM would overwrite the DFU bootloader. It's possible that the nRF5 code needs changes to support running on an nRF5 with Softdevice.
@scalz is playing/plans to play with Nordics OTA update.
-
Lastly, I'm quite intrigued by this one, which is an nRF51832, because it is only 11.4mmx9.5mm in size:
https://www.aliexpress.com/store/product/PTR5528-Fingertip-size-nRF51822-Module-Ultra-Low-Power-Bluetooth-4-0-Low-Energy-RF-Module-Free/130096_1705429590.html?spm=2114.12010108.0.0.TRBTKqHas anyone seen anything else which is that small or even smaller?
