• State Verified Answer
  • Replies 3 replies
  • Subscribers 62 subscribers
  • Views 2269 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 119963
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF Connect PC tool Log File and Maximum Time Interval

User1321

I am using the nRF Connect Tool, everything is working fine (Y) My question is related with the Log file, is there any way to get in the Log File only the data sent through BLE, for example the value or data of an Attribute. Currently when I see the Log file I get type, handle, debug and all other data like this..:

2017-02-23T18:12:46.787Z DEBUG GATTC_EVT_HVX time:2017-02-23T18:12:46.777Z connHandle:0 gattStatus:0 gattStatusName:success errorHandle:0 handle:14 type:1 len:4
2017-02-23T18:12:46.787Z INFO Attribute value changed, handle: 0x0E, value (0x): 04-38-9F-4F
2017-02-23T18:12:46.787Z DEBUG GATTC_EVT_HVX time:2017-02-23T18:12:46.781Z connHandle:0 gattStatus:0 gattStatusName:success errorHandle:0 handle:14 type:1 len:4
2017-02-23T18:12:46.787Z INFO Attribute value changed, handle: 0x0E, value (0x): 04-38-A3-40
2017-02-23T18:12:46.787Z DEBUG GATTC_EVT_HVX time:2017-02-23T18:12:46.785Z connHandle:0 gattStatus:0 gattStatusName:success errorHandle:0 handle:14 type:1 len:4
2017-02-23T18:12:46.788Z INFO Attribute value changed, handle: 0x0E, value (0x): 04-38-A7-31
2017-02-23T18:12:46.789Z DEBUG   197/ 0 <-  [02 39 00 00 00 00 00 00 00 0e 00 01 04 00 04 3a 0d c4 ]
               type:     VENDOR_SPECIFIC reliable:yes seq#:5 ack#:2 payload_length:12 data_integrity:1 header_checksum:fc err_code:0
2017-02-23T18:12:46.789Z DEBUG      198 ->  []
               type:                 ACK reliable: no seq#:0 ack#:6 payload_length:0 data_integrity:0 err_code:0
2017-02-23T18:12:46.796Z DEBUG GATTC_EVT_HVX time:2017-02-23T18:12:46.789Z connHandle:0 gattStatus:0 gattStatusName:success errorHandle:0 handle:14 type:1 len:4
2017-02-23T18:12:46.796Z INFO Attribute value changed, handle: 0x0E, value (0x): 04-3A-0D-C4
2017-02-23T18:12:46.796Z DEBUG GATTC_EVT_HVX time:2017-02-23T18:12:46.793Z connHandle:0 gattStatus:0 gattStatusName:success errorHandle:0 handle:14 type:1 len:4
2017-02-23T18:12:46.796Z INFO Attribute value changed, handle: 0x0E, value (0x): 04-3A-11-B5
2017-02-23T18:12:46.796Z DEBUG   198/ 0 <-  [02 39 00 00 00 00 00 00 00 0e 00 01 04 00 04 3a 11 b5 ]
               type:     VENDOR_SPECIFIC reliable:yes seq#:6 ack#:2 payload_length:12 data_integrity:1 header_checksum:fb err_code:0

etc etc etc... Is there any way to get only the value that is changing or that is received?

Another thing is related with the Time_interval, I have seen that larger is this value, bigger is the throughput, in the specification is says that the maximum is 400ms, can it be larger?? like infinite? I am interested on a high throughput application more than a low energy one.

Thank you in advance!

  • 0

    Hi,

    There is unfortunately no built-in filtering function for the log-file generation. But, many editors have quite powerful filtering mechanisms, so you should be able to filter out the information you want. A start could be to filter out all the lines that don’t have the word INFO, this can easily be achieved using Notepad++’s bookmark mechanism. Excel should also be able to do this.

    What time interval are you referring to? Connection interval? Usually a lower connection interval will result in higher throughput.

  • 0

    Yes, I mean the connection interval, you are right but I have seen on the specification that if we enable the Connection Event Length Extension we could reach a maximum throughput of ~700Kbps with a connection interval of 400ms.

  • 0

    Yes, with Connection Event Length Extension and 400ms connection interval you will have a slightly higher maximum throughput than with a lower connection interval. The reason for this is lower overall packet overhead with the 400ms interval, but with a value above 400ms any further gain is minimal. In addition, if you lose a packet, you will have to wait the whole connection interval before sending the next packet. So for maximum throughput a higher connection interval than 400 ms is not recommended.

Related

core_v2_widget.Hide()