• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

the technical data of the NIOT-E-TPI51-EN-RE/NFLD state Bluetooth 4.2 support.
However, the RPi 3B with the same RF-Module BCM43438 only has 4.1 support.

Does the NIOT-E-TPI51-EN-RE/NFLD indeed has 4.2 support?

Yes this is correct and is a typo ... data sheet is about to be corrected and technical data on the web site will be updates soon to 4.1.
Thx for the hint anyway.

You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

Just to be clear, it does NOT have 4.2 support?
We definitely need 4.2 support and have just placed an order - which we have to cancel without 4.2 support.
No you have to cancel the order. It has bluetoohth 4.1 support only.

It very latest datasheets like this one here https://www.cypress.com/file/298076/download you find that very latest version of BCM43438 chips are also support BT up to specification 5.1. But this is NOT the version of chip that is populated on NIOT-E-TPI51-EN-RE/NFLD.

The NIOT-E-TPI51-EN-RE/NFLD can support BT 4.1 only.

I am sorry for this confusion and for the circumstances

You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

Ok, thanks for Your response, I will have the order cancelled.

I think it is unusual for new revisions of a chip to support newer BT specifications, such a thing is not usually added under the same chip label.
Are You sure, that it is not just a new firmware?
Well I never tried using a different firmware other than this one here https://github.com/OpenELEC/misc-firmwar...3430A1.hcd for initializing chip. Maybe there is indeed a newer one available somewher else. I am pretty sure you will not find any further information in this local Hilscher forum but more in the official Raspberry Pi forums.

I agree to you that it sounds weird that a chip with the same name just with a new datasheet instantly supports a BT spec of a higher version. I could indeed just a matter of software.

Since the BT chip is empty at boot times, it needs indeed an initialization with a software package using the Linux command "hciattach". Since Hilsher uses the very same schematics as the original Raspberry PI 3B, the Hilscher device will support all BT functions that are supported just by upgrading to a higher firmware version.
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

We updated the web site under www.hilscher to have the typo 4.2 turned into 4.1 right now.
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

Dear Armin,

will this support BLE mesh? i.e multiple client connections?

There is no experience with BT at Hilscher at all. There were no demands for it, so noone can tell. The only thing we can tell is that there are two containers available that enables the onboard BT chip controller with BT 4.1 support:
But these containers are just enabling the BT chip for sending and receiving raw data ... but the applications need to be programmed on top of BT chip for both of the containers to establish a bi-directional communication.

All I can say is that netFIELD Connect gateway uses the same schematics as the Raspberry Pi 3B, so all informations you find on the Internet about meshing for example are also alid for netFIELD connect. For example I found a post of standard Raspberry Pi 3B user https://makersportal.com/blog/2017/12/31...ork-part-1 who wrote that he was doing meshing. But to be honest I do not know if this is valid information and if it works reallly ... I have no experiences at all with BT. Maybe there are other posts on the internet taking care of BT and meshing and multiple connectios.

I am sorry I cannot help more than that.
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

Ok thanks Armin for information.
we will talk with our customer accordingly.


Possibly Related Threads…
Thread Author Replies Views Last Post
  NIOT-E-NPIX-RS485 (Rev2 module) DSongra 6 758 February-3rd-2022, 07:50 AM
Last Post: DSongra

Forum Jump:

Users browsing this thread: 1 Guest(s)