• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 205 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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 fails all the time

6278903
Prodigy 10 points
Part Number: DLPNIRNANOEVM

Hi

I bought the DLP NIRNano EVM about a year ago and haven't really used it much.

In the beginning, I could easily scan with the NIRNano, but recently it popped up with a scan error very often. So I decided to update the firmware, but now it is really rare that the device can actually record a spectrum. I get a scan error almost all the time, and occasionally the lamps turn on (but still get a scan error).

I have it connected via USB to a laptop or a desktop computer.

Any suggestions? 

  • 0
    TI__Mastermind 28035 points

    Hello User,

    Do you know what version you used to be on of the nirScan Nano FW? Furthermore, what version did you upgrade to (and of course, what GUI version are you using)?

    Regards,

    Philippe Dollo

  • 0
    Prodigy 10 points

    Hi

    The GUI I upgraded to is v.2.1.0 (TIVA version 2.1.0, DLPC Flash version 2.3.1).

    Unfortunately, I wasn't too aware of the version I upgraded from (I upgraded because it failed the scans only sometimes). But the GUI was 1.1.8 or 1.1.9. TIVA probably 1.1.8, DLPC probably 1.1.0. The spectrum library was also updated from 1.1.3.

    Best,

    Steffen

  • 0 in reply to 6278903
    TI__Genius 9780 points

    Hello Steffen,

    Please try updating the spectrum library (V2.0.3 is now available) and the firmware (V2.0.0 is available) if these are not the versions you are currently using. Additionally, please confirm that all DLLs are in the application folder as described in Section 2.5.1.1 of the User's Guide page 24.

    Please let us know if this corrects your issue.

    Regards,

    Austin