nRF Connect v1.0 Release Candidate

RE: nRF Connect v1.0 Release Candidate

Bjørn Inge — Mon, 11 Jul 2016 09:34:57 GMT

Hi, there will be support for showing text instead of hex. We have preconfigured well known text based characteristics to show as text, but it will also be possible to do this on custom UUIDs.

RE: nRF Connect v1.0 Release Candidate

atune — Mon, 11 Jul 2016 09:30:42 GMT

Will there be a setting to change the value display format from hex to text for example?

RE: nRF Connect v1.0 Release Candidate

Bjørn Inge — Thu, 07 Jul 2016 12:43:46 GMT

Hi, nRF Connect 1.0RC requires DAPLINK on OSX. pc-ble-driver-js can run on Segger J-Link as well.

RE: nRF Connect v1.0 Release Candidate

Kapil Sachdeva — Wed, 29 Jun 2016 19:52:51 GMT

Ok. Thanks for the quick response and clarification.

Just one more clarification :

Is the requirement for mbed DAPLINK firwmare that of nRF Connect tool or the underlying pc-ble-driver-js library that is used by this tool ?

Regards Kapil

RE: nRF Connect v1.0 Release Candidate

Bjørn Inge — Wed, 29 Jun 2016 19:45:24 GMT

Hi,
I'm sorry but the instructions on what workarounds that can be applied are not totally correct. nRF Connect 1.0 RC only supports mbed DAPLINK firmware, not Segger JLink.

In the next release, which will be out within short time, we again support Segger JLink, though still with the requirement to disable MSD feature. Segger JLink will then be the preferred option as that will have firmware programming support in the application.

RE: nRF Connect v1.0 Release Candidate

Kapil Sachdeva — Wed, 29 Jun 2016 15:45:17 GMT

Hi,

Disabled the MSD as recommended to work on OSX but the nrf Connect is still complaining about it. I know it is disabled because I do not see mass storage drive any more.

The message I get is -

"This adapater with SEGGER debug proble or mbed CMSIS Firmware is not supported on OSX"

I am using PCA10040 V 1.1.0 2016.9

I do have the latest connectivity firmware loaded

Please guide

Regards & thanks Kapil

RE: nRF Connect v1.0 Release Candidate

Bjørn Inge — Thu, 16 Jun 2016 09:05:47 GMT

@Nic Secondary services are not supported currently, that is correct. It will not be supported in 1.0 release, but I can add it to the backlog for future releases.

RE: nRF Connect v1.0 Release Candidate

Nic — Wed, 15 Jun 2016 17:19:33 GMT

Secondary services aren't discovered/displayed.

RE: nRF Connect v1.0 Release Candidate

Bjørn Inge — Wed, 15 Jun 2016 10:43:02 GMT

@Adrian
Thanks for the feedback, your request has been noted.

RE: nRF Connect v1.0 Release Candidate

Adrian Eggenberger — Mon, 06 Jun 2016 16:13:56 GMT

Great Tool! Found one small bug i guess. If a device is advertising with some UUID's (type UUID_MORE_AVAILABLE) in the advertising packet and some in the scan response (same type) the tool switches in the presentation of the advertising data between the UUID's of the two packages at random instead of combining them.

RE: nRF Connect v1.0 Release Candidate

Bjørn Inge — Sat, 21 May 2016 07:27:38 GMT

@ta2
You are correct that it is currently not possible to add uuids. I will add it to the wishlist. Thanks for the input.

RE: nRF Connect v1.0 Release Candidate

ta2 — Fri, 20 May 2016 01:55:00 GMT

I don't see anywhere to enter names for my private services and characteristics. (Like I can do with Master Control Panel.)

Am I overlooking it, or can this be placed on the wishlist?

Thanks!

--- tom

RE: nRF Connect v1.0 Release Candidate

Bjørn Inge — Wed, 18 May 2016 10:03:03 GMT

@Johan
Please open an issue in devzone questions so we can give you closer support, this comments field isn't very well suited for issue tracking.

@hawk
There are no current plans to support scripting from within the nRF Connect application, however it is possible to use the underlying API pc-ble-driver js to write scripts. It is currently not ducumented but feel free to check out pc-ble-driver-js on github.

RE: nRF Connect v1.0 Release Candidate

hawk — Tue, 17 May 2016 05:00:26 GMT

Wonderful tools. it can support script control? for example, Can i write some script( users command ) to run some long time test with ble device?

RE: nRF Connect v1.0 Release Candidate

Johan Gasslander — Mon, 16 May 2016 12:51:46 GMT

After following why_do_i_need_a_name's advice with programming with nrfjprog i get the following error

2016-05-16T12:40:30.155Z DEBUG Error: Error occurred opening serial port. (NRF_ERROR_TIMEOUT)
at Adapter.<anonymous> (/.../Downloads/nrf-connect-linux-x64/resources/app/js/actions/adapterActions.js:135:34)
at emitOne (events.js:77:13)
at Adapter.emit (events.js:169:7)
at Adapter._checkAndPropagateError (/.../Downloads/nrf-connect-linux-x64/resources/app/node_modules/pc-ble-driver-js/api/adapter.js:167:18)
at _adapter.open.err (/.../Downloads/nrf-connect-linux-x64/resources/app/node_modules/pc-ble-driver-js/api/adapter.js:264:22)