Hi,
I have a problem in the software ''nRF Connect for Desktop Low Energy Standalone v4.0.4'' with the Server setup.
I use a nRF52840 dongle with the desktop software as a simulated bluetooth device.
In ''Server Setup'', when I create a characteristic with the Property ''Notify'', I can't apply to the device.
When I use the property ''Read'' , it works.
I miss something ?
Hello,
Thank you for the report, I will give this a try myself on Tuesday.
In the meantime, could you clarify if the issue is that when you have both 'read' and 'notify' selected the 'apply to device' button is grayed out?
Does this happen as soon as you select 'notify', regardless of the combination of other options?
Best regards,
Karl
Hi Karl,
The problem is when I try to ''Apply to device". So I did some tests to explain you where could be the problem.
- I created a server setup with 1 service which had 1 characteristic with the property "Read" only. (nrf_case_1.png)
* I can save it and aplied it to the device without problem.
* on the log file, I had the message "INFO Server setup was applied"
- I used the same setup and add the "Notify" property to the last characteristic.
* I could save it without problem.
* I could save the whole server setup without problem.
* When I click to "Apply to device", nothing happen. No message on the log file.
* Sometimes, but I had a message asking to confirm apply the setup (nrf_case_2.png). The dongle reboot and had lost all setup.
Best regards
Alexandre
Karl,
I make another test.
- I close the nRF Connect application.
- I open a new instance of nRF Connect application.
- I connect the nRF52 dongle
- Go to "Server Setup", load my server setup with the notify property.
- I click on "Apply to device" button, and nothing happened. I check the log file but no clue. I attach the log file below.
2023-09-08T14:29:36.437Z DEBUG Application data folder: C:\Users\arault\AppData\Roaming\nrfconnect-bluetooth-low-energy\bundle 2023-09-08T14:29:36.505Z INFO Using nrf-device-lib-js version: 0.4.4 2023-09-08T14:29:36.505Z INFO Using nrf-device-lib version: 0.10.3 2023-09-08T14:29:36.505Z INFO Using nrfjprog DLL version: 10.15.1 2023-09-08T14:29:36.505Z INFO Using JLink version: JLink_V7.92c 2023-09-08T14:29:36.512Z DEBUG App pc-nrfconnect-ble v4.0.4 official 2023-09-08T14:29:36.512Z DEBUG App path: C:\Users\arault\AppData\Local\Programs\nrfconnect-bluetooth-low-energy\resources\app.asar\resources/bundle/ 2023-09-08T14:29:36.512Z DEBUG nRFConnect 4.0.4, required by the app is (^3.8.0) 2023-09-08T14:29:36.513Z DEBUG nRFConnect path: C:\Users\arault\AppData\Local\Programs\nrfconnect-bluetooth-low-energy\resources\app.asar 2023-09-08T14:29:36.513Z DEBUG HomeDir: C:\Users\arault 2023-09-08T14:29:36.513Z DEBUG TmpDir: C:\Users\arault\AppData\Local\Temp 2023-09-08T14:29:36.516Z INFO Installed JLink version does not match the provided version (V7.66a) 2023-09-08T14:29:36.883Z INFO Updated list of uuids with data from https://github.com/NordicSemiconductor/bluetooth-numbers-database/tree/master/v1 2023-09-08T14:29:56.255Z INFO Selected device with s/n EC3A21FAC8EC 2023-09-08T14:29:56.258Z DEBUG Device has DFU trigger interface, the device is in Application mode 2023-09-08T14:29:56.258Z DEBUG Will wait for device EC3A21FAC8EC 2023-09-08T14:29:56.259Z INFO Device setup completed 2023-09-08T14:29:56.260Z INFO Connectivity firmware version: ble-connectivity 4.1.4+Mar-11-2021-08-36-04. SoftDevice API version: 5. Baud rate: 1000000. 2023-09-08T14:29:56.260Z INFO Opening adapter connected to COM9 2023-09-08T14:29:57.187Z INFO Successfully opened COM9. Baud rate: 1000000. Flow control: none. Parity: none. 2023-09-08T14:29:57.187Z DEBUG State change: STATE_START -> STATE_RESET 2023-09-08T14:29:57.187Z DEBUG 1 -> [N/A] type: RESERVED_5 reliable: no seq#:0 ack#:0 payload_length:0 data_integrity:0 err_code:0x0 2023-09-08T14:29:57.188Z INFO Reset performed on adapter COM9 2023-09-08T14:29:57.489Z DEBUG State change: STATE_RESET -> STATE_UNINITIALIZED 2023-09-08T14:29:57.489Z DEBUG 2 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC] 2023-09-08T14:29:57.489Z DEBUG 1/ 0 <- [02 7d ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC_RESP] 2023-09-08T14:29:57.489Z DEBUG State change: STATE_UNINITIALIZED -> STATE_INITIALIZED 2023-09-08T14:29:57.489Z DEBUG 3 -> [03 fc 11 ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0x0 [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]] 2023-09-08T14:29:57.739Z DEBUG 4 -> [03 fc 11 ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0x0 [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]] 2023-09-08T14:29:57.889Z DEBUG 2/ 0 <- [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC] 2023-09-08T14:29:57.889Z DEBUG 5 -> [02 7d ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC_RESP] 2023-09-08T14:29:57.990Z DEBUG 6 -> [03 fc 11 ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0x0 [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]] 2023-09-08T14:29:57.990Z DEBUG 3/ 0 <- [03 fc 11 ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0x0 [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]] 2023-09-08T14:29:57.991Z DEBUG 7 -> [04 7b 11 ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0x0 [CONFIG_RESP [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]] 2023-09-08T14:29:58.241Z DEBUG 8 -> [03 fc 11 ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0x0 [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]] 2023-09-08T14:29:58.241Z DEBUG 4/ 0 <- [04 7b 11 ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0x0 [CONFIG_RESP [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]] 2023-09-08T14:29:58.241Z DEBUG State change: STATE_INITIALIZED -> STATE_ACTIVE 2023-09-08T14:29:58.249Z INFO Adapter connected to COM9 opened 2023-09-08T14:29:58.251Z DEBUG 9 -> [00 69 20 00 00 00 01 01 08 a0 01 ] type: VENDOR_SPECIFIC reliable:yes seq#:0 ack#:0 payload_length:b data_integrity:1 header_checksum:82 err_code:0x0 2023-09-08T14:29:58.251Z DEBUG 5/ 0 <- [N/A] type: ACK reliable: no seq#:0 ack#:1 payload_length:0 data_integrity:0 err_code:0x0 2023-09-08T14:29:58.251Z DEBUG 6/ 0 <- [01 69 00 00 00 00 ] type: VENDOR_SPECIFIC reliable:yes seq#:0 ack#:1 payload_length:6 data_integrity:1 header_checksum:ca err_code:0x0 2023-09-08T14:29:58.251Z DEBUG 10 -> [N/A] type: ACK reliable: no seq#:0 ack#:1 payload_length:0 data_integrity:0 err_code:0x0 2023-09-08T14:29:58.251Z DEBUG 11 -> [00 69 23 00 00 00 01 01 f7 00 ] type: VENDOR_SPECIFIC reliable:yes seq#:1 ack#:1 payload_length:a data_integrity:1 header_checksum:89 err_code:0x0 2023-09-08T14:29:58.251Z DEBUG 7/ 0 <- [N/A] type: ACK reliable: no seq#:0 ack#:2 payload_length:0 data_integrity:0 err_code:0x0 2023-09-08T14:29:58.251Z DEBUG 8/ 0 <- [01 69 00 00 00 00 ] type: VENDOR_SPECIFIC reliable:yes seq#:1 ack#:2 payload_length:6 data_integrity:1 header_checksum:c1 err_code:0x0 2023-09-08T14:29:58.251Z DEBUG 12 -> [N/A] type: ACK reliable: no seq#:0 ack#:2 payload_length:0 data_integrity:0 err_code:0x0 2023-09-08T14:29:58.251Z DEBUG 13 -> [00 69 01 00 00 00 01 0a ] type: VENDOR_SPECIFIC reliable:yes seq#:2 ack#:2 payload_length:8 data_integrity:1 header_checksum:a0 err_code:0x0 2023-09-08T14:29:58.251Z DEBUG 9/ 0 <- [N/A] type: ACK reliable: no seq#:0 ack#:3 payload_length:0 data_integrity:0 err_code:0x0 2023-09-08T14:29:58.251Z DEBUG 10/ 0 <- [01 69 00 00 00 00 ] type: VENDOR_SPECIFIC reliable:yes seq#:2 ack#:3 payload_length:6 data_integrity:1 header_checksum:b8 err_code:0x0 2023-09-08T14:29:58.251Z DEBUG 14 -> [N/A] type: ACK reliable: no seq#:0 ack#:3 payload_length:0 data_integrity:0 err_code:0x0 2023-09-08T14:29:58.251Z DEBUG 15 -> [00 69 40 00 00 00 01 01 07 01 ] type: VENDOR_SPECIFIC reliable:yes seq#:3 ack#:3 payload_length:a data_integrity:1 header_checksum:77 err_code:0x0 2023-09-08T14:29:58.251Z DEBUG 11/ 0 <- [N/A] type: ACK reliable: no seq#:0 ack#:4 payload_length:0 data_integrity:0 err_code:0x0 2023-09-08T14:29:58.251Z DEBUG 12/ 0 <- [01 69 00 00 00 00 ] type: VENDOR_SPECIFIC reliable:yes seq#:3 ack#:4 payload_length:6 data_integrity:1 header_checksum:af err_code:0x0 2023-09-08T14:29:58.251Z DEBUG 16 -> [N/A] type: ACK reliable: no seq#:0 ack#:4 payload_length:0 data_integrity:0 err_code:0x0 2023-09-08T14:29:58.251Z DEBUG 17 -> [00 69 a0 00 00 00 01 00 ] type: VENDOR_SPECIFIC reliable:yes seq#:4 ack#:4 payload_length:8 data_integrity:1 header_checksum:8e err_code:0x0 2023-09-08T14:29:58.251Z DEBUG 13/ 0 <- [N/A] type: ACK reliable: no seq#:0 ack#:5 payload_length:0 data_integrity:0 err_code:0x0 2023-09-08T14:29:58.251Z DEBUG 14/ 0 <- [01 69 00 00 00 00 ] type: VENDOR_SPECIFIC reliable:yes seq#:4 ack#:5 payload_length:6 data_integrity:1 header_checksum:a6 err_code:0x0 2023-09-08T14:29:58.252Z DEBUG 18 -> [N/A] type: ACK reliable: no seq#:0 ack#:5 payload_length:0 data_integrity:0 err_code:0x0 2023-09-08T14:29:58.252Z DEBUG 19 -> [00 69 a1 00 00 00 01 80 05 00 00 ] type: VENDOR_SPECIFIC reliable:yes seq#:5 ack#:5 payload_length:b data_integrity:1 header_checksum:55 err_code:0x0 2023-09-08T14:29:58.252Z DEBUG 15/ 0 <- [N/A] type: ACK reliable: no seq#:0 ack#:6 payload_length:0 data_integrity:0 err_code:0x0 2023-09-08T14:29:58.252Z DEBUG 16/ 0 <- [01 69 00 00 00 00 ] type: VENDOR_SPECIFIC reliable:yes seq#:5 ack#:6 payload_length:6 data_integrity:1 header_checksum:9d err_code:0x0 2023-09-08T14:29:58.252Z DEBUG 20 -> [N/A] type: ACK reliable: no seq#:0 ack#:6 payload_length:0 data_integrity:0 err_code:0x0 2023-09-08T14:29:58.252Z DEBUG 21 -> [00 60 ] type: VENDOR_SPECIFIC reliable:yes seq#:6 ack#:6 payload_length:2 data_integrity:1 header_checksum:dc err_code:0x0 2023-09-08T14:29:58.252Z DEBUG 17/ 0 <- [N/A] type: ACK reliable: no seq#:0 ack#:7 payload_length:0 data_integrity:0 err_code:0x0 2023-09-08T14:29:58.252Z DEBUG 18/ 0 <- [01 60 00 00 00 00 ] type: VENDOR_SPECIFIC reliable:yes seq#:6 ack#:7 payload_length:6 data_integrity:1 header_checksum:94 err_code:0x0 2023-09-08T14:29:58.252Z DEBUG 22 -> [N/A] type: ACK reliable: no seq#:0 ack#:7 payload_length:0 data_integrity:0 err_code:0x0 2023-09-08T14:29:58.255Z DEBUG 23 -> [00 65 01 ] type: VENDOR_SPECIFIC reliable:yes seq#:7 ack#:7 payload_length:3 data_integrity:1 header_checksum:c3 err_code:0x0 2023-09-08T14:29:58.256Z DEBUG 19/ 0 <- [N/A] type: ACK reliable: no seq#:0 ack#:0 payload_length:0 data_integrity:0 err_code:0x0 2023-09-08T14:29:58.256Z DEBUG 20/ 0 <- [01 65 00 00 00 00 09 59 00 a5 00 ] type: VENDOR_SPECIFIC reliable:yes seq#:7 ack#:0 payload_length:b data_integrity:1 header_checksum:7b err_code:0x0 2023-09-08T14:29:58.256Z DEBUG 24 -> [N/A] type: ACK reliable: no seq#:0 ack#:0 payload_length:0 data_integrity:0 err_code:0x0 2023-09-08T14:29:58.256Z DEBUG 25 -> [00 7d 01 f8 00 01 ] type: VENDOR_SPECIFIC reliable:yes seq#:0 ack#:0 payload_length:6 data_integrity:1 header_checksum:d2 err_code:0x0 2023-09-08T14:29:58.257Z DEBUG 21/ 0 <- [N/A] type: ACK reliable: no seq#:0 ack#:1 payload_length:0 data_integrity:0 err_code:0x0 2023-09-08T14:29:58.257Z DEBUG 22/ 0 <- [01 7d 00 00 00 00 01 05 00 6e 52 46 35 78 ] type: VENDOR_SPECIFIC reliable:yes seq#:0 ack#:1 payload_length:e data_integrity:1 header_checksum:4a err_code:0x0 2023-09-08T14:29:58.257Z DEBUG 26 -> [N/A] type: ACK reliable: no seq#:0 ack#:1 payload_length:0 data_integrity:0 err_code:0x0 2023-09-08T14:29:58.257Z DEBUG 27 -> [00 6d 01 ] type: VENDOR_SPECIFIC reliable:yes seq#:1 ack#:1 payload_length:3 data_integrity:1 header_checksum:f9 err_code:0x0 2023-09-08T14:29:58.257Z DEBUG 23/ 0 <- [N/A] type: ACK reliable: no seq#:0 ack#:2 payload_length:0 data_integrity:0 err_code:0x0 2023-09-08T14:29:58.257Z DEBUG 24/ 0 <- [01 6d 00 00 00 00 02 ec c8 fa 21 3a ec ] type: VENDOR_SPECIFIC reliable:yes seq#:1 ack#:2 payload_length:d data_integrity:1 header_checksum:51 err_code:0x0 2023-09-08T14:29:58.258Z DEBUG 28 -> [N/A] type: ACK reliable: no seq#:0 ack#:2 payload_length:0 data_integrity:0 err_code:0x0 2023-09-08T14:29:58.261Z DEBUG SoftDevice BLE stack enabled. 2023-09-08T14:29:59.262Z DEBUG Timeout when waiting for attachment of device with serial number EC3A21FAC8EC 2023-09-08T14:29:59.262Z DEBUG Device did not show up after 3 seconds 2023-09-08T14:30:03.295Z INFO Server setup loaded from D:\VM\nRF\server_mock_v2.ncs.
Hello again,
Thank you for your patience with this - I have been out of office for some time, but now I am back.
From your last log it looks like it loaded your settings correctly and encountered no issue.
Is this still seeing an issue with setting up a characteristic with notifications? Is there still nothing happening when you press 'apply to device'?
I just gave this a try on my end, and everything is working as expected on my end - I set up the same characteristic as you, add 'notify', click apply to device, and it is applied as I would expect.
Best regards,
Karl
Hi Karl,
I still have the problem. The software correctly load the settings but I can't write it in the device. Nothing happen when I click on ''Apply to device''.
I can't explain why you have a different behaviour from me. I try it under linux and I have the same behaviour as under windows.
The difference is we don't have the same bluetooth dongle. May be I have a problem with the firmware or the hardware ?
Best regards,
Alexandre
