NUS How complicated can it be...

[Monolit]

Well - Where shall I begin? The more I look around on the web the more confused I get.

I need to create a Connection betwen a PC running Windows 10 and a sensor device server, streaming data back to the PC.

I want to use a simple UART service over BLE. Very much like the old BT 2.0 devices HC05. Providing wireless serial port emulation.

Bluetooth 5 potentially offer more than  1Mbit of data rate over the air, but all third party devices I have found shows rather sluggish performance,

even when using nRF52840, nRF52810 and similar chips that really should deliver more.

RAYTEC and FANSTEL have UART type of modules where no SOC programming is necessary . Just Rx,Tx,RTS,CTS 

But data rate is just 160kbit/s or slightly more. How can that be???  How can they waste all this capacity ???

Now - here comes my real question:

Can I use Nordics UART application NUS to circumvent these speed issues?

How do I set up the NUS communiction parameters without having to deal with SDK, compilers,Debuggers and other stuff that i'd rather not want to deal with.
RAYTEC and FANSTEL offer AT-commands for setup. Does NUS have any similar capabilities?

In other Words - How do I let a Nordig chip act as a wireless Cable. Nothing more , nothing less!

/Per

[Turbo J]

Monolit said:

Providing wireless serial port emulation.

Then I would recommand buying other 3rd party BT classic modules, since you won't get a COM Port for BT LE devices (at least out-of-the box w/o special drivers). These modules are off topic here, unfortunaltely.

[Monolit]

This is not an option for us since we need to be able to reach Three platforms: Windows, Android and Iphone.

The only UART profile for Classic Bluetooth EDR is SPP, which is not supported in an Iphone. 

RTS/CTS handshaking is also an obstacle in many HCxx devices since often a Firmware setting is needed to turn it on.
That parameter cannot be reached from the AT command set.

Current drain is also rather high for HCxx

[Einar Thorsrud]

Hi,

Can I use Nordics UART application NUS to circumvent these speed issues?

Generally a practical bitrate of 160 kbit/s does not sound so bad. Theoretically you should be able to get a higher throughput, but it is affected by many things so it is difficult to say. For instance, the capabilities of mobile phones vary greatly, and many will not be able to achieve a particularly high bitrate over BLE.

How do I set up the NUS communiction parameters without having to deal with SDK, compilers,Debuggers and other stuff that i'd rather not want to deal with.

The SDK provide a NUS peripheral and central example, but that is exactly what it is. It is intended as a starting point so that you can develop your own application. We do not provide a production ready UART over BLE tunneling system (we might have customers who make it and sell it, but I don't know of any such end product).

How do I let a Nordig chip act as a wireless Cable. Nothing more , nothing less!

You develop it

[awneil]

Einar Thorsrud said:

For instance, the capabilities of mobile phones vary greatly, and many will not be able to achieve a particularly high bitrate over BLE

And both Android and iOS put limits on the "acceptable" connection parameters - so that the theoretical limits cannot be reached.

Also remember that a phone is a complex multi-tasking system - so it has to balance its resources amongst all the different tasks, and not let any one "hog" the system. I suspect this has something to do with why, even on the same phone, you can get different connection parameters each time you connect!

Einar Thorsrud said:

You develop it

Or you pay someone to develop it for you ...

[awneil]

It does seem odd that the Bluetooth SIG chose not to include anything like SPP for BLE.