• State Not Answered
  • Replies 3 replies
  • Subscribers 91 subscribers
  • Views 758 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 286484
Options

Cannot scan for devices with windows app and USB840X

Tito Sanchez

I am trying to scan for BLE devices in my area, but when I connect to the USB840XZ with the windows development tool the "Start Scan" button is not active.  There are some error messages on the log window.  

2022-03-24T22:14:21.519Z INFO Device closed.
2022-03-24T22:14:27.820Z INFO Selected device with s/n F99EF4F75577
2022-03-24T22:14:27.824Z INFO Device setup completed
2022-03-24T22:14:27.824Z INFO Connectivity firmware version: ble-connectivity 4.1.4+Mar-11-2021-08-36-04. SoftDevice API version: 5. Baud rate: 1000000.
2022-03-24T22:14:27.825Z INFO Opening adapter connected to COM7
2022-03-24T22:14:28.768Z INFO Successfully opened COM7. Baud rate: 1000000. Flow control: none. Parity: none.
2022-03-24T22:14:28.769Z DEBUG State change: STATE_START -> STATE_RESET
2022-03-24T22:14:28.769Z DEBUG 1 -> [N/A] type: RESERVED_5 reliable: no seq#:0 ack#:0 payload_length:0 data_integrity:0 err_code:0x0
2022-03-24T22:14:28.770Z INFO Reset performed on adapter COM7
2022-03-24T22:14:29.069Z DEBUG State change: STATE_RESET -> STATE_UNINITIALIZED
2022-03-24T22:14:29.070Z DEBUG 2 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2022-03-24T22:14:29.324Z DEBUG 3 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2022-03-24T22:14:29.579Z DEBUG 4 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2022-03-24T22:14:29.832Z DEBUG 5 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2022-03-24T22:14:30.087Z DEBUG 6 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2022-03-24T22:14:30.340Z DEBUG 7 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2022-03-24T22:14:30.593Z DEBUG State change: STATE_UNINITIALIZED -> STATE_NO_RESPONSE
2022-03-24T22:14:30.593Z ERROR Received status with code 0 PKT_SEND_MAX_RETRIES_REACHED, message: 'No response from device. Tried to send packet 6 times.'
2022-03-24T22:14:31.778Z DEBUG serial port read on port COM7 aborted.
2022-03-24T22:14:31.784Z ERROR Error occured when opening port. Errorcode: NRF_ERROR_TIMEOUT (0xd)

I can connect to the USB840X with the android app and send data through the comport.  So it appears the USB840X is not completely dead.  Do I need a different firmware installed?

Parents
  • 0

    Hi,

    Are you trying to use the USB840XZ with nRF Connect for desktop Bluetooth, or are you using a dongle or DK from nordic with nRF Connect for Desktop, trying to communicate via bluetooth with the USB840XZ?

    I ask because the nRF Connect for Desktop is only supports our DKs and dongles out of the box, and the connectivity firmware targets the boards uses on those. I do not know the details of the USB840XZ HW, but it is not obvious that our connectivity firmware will work on that even if it i nRF52840 based (could use different pins connected to button(s) and LEDs, different (or not) LFXO, and so on. So if you want to use the USB840XZ you need to build a connectivity firmware that is made for that board. Note that this will not be directly supported by us, but it is possible.

Reply
  • 0

    Hi,

    Are you trying to use the USB840XZ with nRF Connect for desktop Bluetooth, or are you using a dongle or DK from nordic with nRF Connect for Desktop, trying to communicate via bluetooth with the USB840XZ?

    I ask because the nRF Connect for Desktop is only supports our DKs and dongles out of the box, and the connectivity firmware targets the boards uses on those. I do not know the details of the USB840XZ HW, but it is not obvious that our connectivity firmware will work on that even if it i nRF52840 based (could use different pins connected to button(s) and LEDs, different (or not) LFXO, and so on. So if you want to use the USB840XZ you need to build a connectivity firmware that is made for that board. Note that this will not be directly supported by us, but it is possible.

Children
  • 0 in reply to Einar Thorsrud

    Hello Einar,

    Thank you for the info.  I was trying to use nRF Connect with the USB840XZ, that is unfortunate that it will not work with nRF connect.  I was not envisioning developing firmware for this, I was hoping for an off the shelf solution.  Is there not just a AT command firmware to allow me to use this dongle?

  • 0 in reply to Tito Sanchez

    Hi,

    Tito Sanchez said:
    I was trying to use nRF Connect with the USB840XZ, that is unfortunate that it will not work with nRF connect.  I was not envisioning developing firmware for this, I was hoping for an off the shelf solution.

    I see. In that case I recommend you buy a DK or dongle from us. The nRF52840 dongle is a low cost device specifically indented for use with nRF Connect for desktop.

    Tito Sanchez said:
    Is there not just a AT command firmware to allow me to use this dongle?

    We do not provide AT command firmware. I know some module manufacturer do, for instance U-blox. You would have to obtain it from them though, and I assume it can only be used with modules they provide.

Related
Terms of service