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: Scan config Problem

Part Number: DLPNIRNANOEVM
Other Parts Discussed in Thread: DLPC350, DLPC150

Hi, I'm using the DLPNIRSCANNANO (GUI v2.0.2, DLPR150PROM 2.0.0) from some months and it has worked well.  

Now it has a problem, when I start the GUI an error message appear:

I click OK and then another error appear:

I click OK and the GUI is opened. 

When i try to set the Scan Config from the GUI, the library is empty:

I think that there is a problem with the Scan Configuration saved on the device.

I tried to update the TIVA firmware and the DLPR150PROM but it dosen't work.

Could you suggest a solution to this problem? Is it possible to restore the Scan Config on the device?

Thanks in advance

Best regards

Nicola

  • Nicola,

    It looks like somehow the memory got cleared on your device. Did something happen prior to this error? Do you know what might have caused it?

    Are you able to define a new scan configuration and copy it to the Nano?

    When you say that updating the PROM and the Tiva FW "don't work" can you describe what that means in a little more detail?

    Thank you,
    Paul
  • Hi Paul,

    I'm using the UART comunication to manage the NIRScan. The problem happens when I used the UART togheter with the USB (the USB is used to comunicate with the PC). Could be it  the reason of the problem?

    Now I have defined a new scan configuration and I have copied it to the Nano. I have partially solved the problem. The Nano works with the external button and with the UART comunication, I'm able to see the data on the SD card.

    I have a problem with the GUI when I try to perform a Scan through it:

      

    Is it required a particular scan configuration in order to allow the plot on the GUI?

    Thanks in advance

    Nicola

  • Hi Nicola,

    In general, there is no specific configuration required by the GUI for it to interpret the data. Because your Nano didn't have any of the default scans saved in memory (Column 1 and Hadamard 1), I'm going to guess that the factory reference data was also erased from the system and so you're seeing this error because it has no reference data to calculate with. Take a new reference scan and store it on your unit to see if that solves this issue.

    In the screenshot you attached, was that a scan taken with USB and without the UART connected?

    Are you still unable to update the tiva software and DLPC350 DLPC150 firmware?

    -Paul

  • I stored the new reference and now it works. The screenshot is acquired during a scan taken with USB and without the UART connected.
    From the GUI I can update only firmware of TIVA and dlpc150, not dlpc350(it is not installed on the NIRScanNANO). Do you have any suggestion to solve the problem of the conflict between the UART and the USB comunication?

    Thanks in advance

    Nicola
  • Typo on my part - you are correct, it's the DLPC150.

    For clarification - what is the issue that happens with the UART and USB connected at the same time? You're unable to scan?

    -Paul
  • Hi Paul, when I connect at the same time the UART and USB there is a problem with Scan. It means that when i try to perform a scan through the USB or the UART the orange led starts to flash and the Scan is not performed.

    Thanks

    Nicola

  • Hi Nicola,

    Let me look into this. We don't normally use both at the same time - I'm not sure what the code is set up to handle.

    -Paul
  • Nicola,

    What is your application that you are trying to use USB and UART simultaneously?

    Thanks,
    Paul
  • Hi Nicola,

    I looked into the interfaces and generally we just want users to be communicating via USB or UART, not both. It is possible to use both, but the code only has one command handler and therefore timing is quite important. You'd need to make sure that all commands are completely finished before sending another command on the other interface. Conflicts can occur and cause issues like the type you're seeing.

    Best,
    Paul