This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DLPNIRNANOEVM: Issue retrieving calibration data using BLE

Prodigy 130 points

Replies: 11

Views: 1112

Part Number: DLPNIRNANOEVM

Hi,

My issue is that I do not undersetand how to retrieve the data using the BLE characteristics. In request , the guide says that I must indicate intent to read without sending any data. I do not understand how to do it.

Thanks 

Brais

11 Replies

  • Hello Brais,

    Could you please clarify what part of the guide you are referring to?

    Thanks,
    Kyle
  • In reply to Kyle Rakos:

    Hi,

    The part that i am talking about is the table J-5 in Section J: Bluetooth Communications

    Thanks 

    Brais

  • In reply to brais.cgaldo:

    Hi,

    More exactly I am talking about GCIS table

    Thanks
    Brais
  • In reply to brais.cgaldo:

    Hi Brais,

    This means that the characteristic contains a byte which is to be written by the external device, but the characteristic contains no data to read. This is made clear in the the table by indicating that Number of Bytes: 1, and only WRITE property is supported.

    Thanks & Regards,
    Hirak.
  • In reply to Hirak Biswas:

    Hi Hirak,

    I am capable to receive the reference data but not the spectrum data. I followed the same proccess but I cannot obtain the spectrum calibration data. It may be a bug into the firmware.

    Thanks

    Brais

  • In reply to brais.cgaldo:

    Hi Hirak,

    The most important issue is that when I write a 5 to manifest the intent to read, occurs a BLE error communication and I am not capable to read the correspondent characteristic.

    Thanks

    Brais

  • In reply to Hirak Biswas:

    Hi Hirak,

    The most important issue is that when I write a 5 to manifest the intent to read, occurs a BLE error communication and I am not notified by the correspondent characteristic.

    Thanks

    Brais
  • In reply to brais.cgaldo:

    Hi Brais,

    It sounds like you are having issues reading the multi-packet information returned from the GCIS service (UUID 0x53455204-444C- 5020-4E49- 52204E616E6F). Is that correct?

    Receiving the spectrum calibration coefficients requires the following steps:

    1. Subscribe to notifications for characteristic UUID 0x4348410E-444C- 5020-4E49- 52204E616E6F
    2. Write to the request characteristic for this data (UUID 0x4348410D-444C- 5020-4E49- 52204E616E6F)

    Here is a log from lightBlue when I executed the previous steps

    12:23:04.960 — Characteristic (4348410D-444C-5020-4E49-52204E616E6F) wrote new value: <00>
    12:23:05.104 — Characteristic (4348410D-444C-5020-4E49-52204E616E6F) read: (null)
    12:23:05.105 — Characteristic (4348410E-444C-5020-4E49-52204E616E6F) notified: <00900000 00>
    12:23:05.106 — Characteristic (4348410E-444C-5020-4E49-52204E616E6F) notified: <0174706c 00480000 00532866 23662329 00030000>
    12:23:05.107 — Characteristic (4348410E-444C-5020-4E49-52204E616E6F) notified: <02000300 000020db 98cc85b8 23c0d704 77fb90dd>
    12:23:05.107 — Characteristic (4348410E-444C-5020-4E49-52204E616E6F) notified: <03af3f51 c94c4a9d 1a17bfa3 d9007989 1d9c404e>
    12:23:05.107 — Characteristic (4348410E-444C-5020-4E49-52204E616E6F) notified: <04bd5dc1 4be6edbf 5cfeba71 252c2fbf 00000000>
    12:23:05.107 — Characteristic (4348410E-444C-5020-4E49-52204E616E6F) notified: <05000000 00000000 00000000 00000000 00000000>
    12:23:05.108 — Characteristic (4348410E-444C-5020-4E49-52204E616E6F) notified: <06000000 00000000 00000000 00000000 00000000>
    12:23:05.108 — Characteristic (4348410E-444C-5020-4E49-52204E616E6F) notified: <07000000 00000000 00000000 00000000 00000000>
    12:23:05.164 — Characteristic (4348410E-444C-5020-4E49-52204E616E6F) notified: <08000000 00000000 00000000>

    This data should be interpreted and repackaged as described in the NIRscan Nano User's Guide table J-9: Bluetooth Multiple Packet Structure. It should then be passed into the appropriate spectrum library function(s) for usage.

    Note that reading many of the calibration and scan data over BLE uses this same construct, with different notification and read-request UUIDs to subscribe and write to.

  • In reply to Eric Pruett:

    Hi Eric,

    No, I do not have any issue reading the information because I do this steps and no data is retrieved from the device. I write a 0x00 in the Request Spectrum Calibration Coefficients Characteristic from GCIS and no information is retrieved. Furthemore, it cause a BLE error communication between my android phone and the NIRSCAN NANO.

    Thanks

    Brais

  • In reply to brais.cgaldo:

    Hi Brais,

    Kindly give us some time, we'll get back to you soon. Your patience is much appreciated.
    Thanks & Regards,
    Hirak.

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.