• State TI Thinks Resolved
  • Replies 12 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 266 views
  • Users 0 members are here
Support feedback
Options
Options
Related

Original question:

OPT4001DTSEVM: Error Initializing GUI TI-Latte - 0.8.4

OPT4001DTSEVM: GUI doesn't work with OPT3001DTSEVM

Thomas Kratt
Prodigy 10 points
Part Number: OPT4001DTSEVM
Other Parts Discussed in Thread: OPT4001, OPT3001, OPT3001DTSQ1EVM, OPT3001EVM, OPT4001EVM, OPT3004EVM, OPT3004

Tool/software:

I received the OPT3001DTSEVM and encounter the problem that I can't connect to the sensor via the GUI tool like other users already reported.

One user was advised to comment out lines 83-89 in mEVMSelector.py (which apparently didn't work for him) and then he modified the VID and PID values at line 35 of the same file to decimal values (which seemed to help in his case).

As I understand, for OPT3001DTSEVM the same software must be installed than for the OPT4001DTSEVM. So I installed OPT4001DTSEVM_GUI.exe under C:\Latte to avoid permission issues on my W11 PC. But even when running the program as admin, modifications of the mEVMSelector.py can't be saved.

Following log is displayed when starting the GUI with the OPT3001DTSEVM connected (USB ports COM4 and 5 detected):

#======

#Executing .. OPT4001/OPT4001DTS_EVM/devInit.py

#Start Time 2025-10-10 16:40:59.778000

#Error:

# "OPT4001/OPT4001DTS_EVM/devInit.py", line 41, in

# File "C:\Users\thoma\OneDrive\Documents\Texas Instruments\Latte\projects\OPT4001/OPT4001DTS_EVM/mEVMSelector.py", line 83, in __init__

# assert z[2] == '04'

# AssertionError

#

#

#Done executing .. OPT4001/OPT4001DTS_EVM/devInit.py

#End Time 2025-10-10 16:40:59.916000

#Execution Time = 0.137999773026 s

#================ ERRORS:1, WARNINGS:0 ================#

Following popup windows appear when starting the GUI without OPT3001DTSEVM connected:

1. Profile Selected: OPT4001DTS_EVM

2. Connection Problem: OPT4001 Connection Problem

and the log indicates:

#======

#Executing .. OPT4001/OPT4001DTS_EVM/devInit.py

#Start Time 2025-10-10 17:01:28.476000

#Error: 'PySide.QtGui.QWidget.closeEvent' called with wrong argument types: PySide.QtGui.QWidget.closeEvent(Shiboken.ObjectType) Supported signatures: PySide.QtGui.QWidget.closeEvent(PySide.QtGui.QCloseEvent)

# "OPT4001/OPT4001DTS_EVM/devInit.py", line 62, in

# File "core\asterixExecGUI.py", line 1746, in closeEvent

# TypeError: 'PySide.QtGui.QWidget.closeEvent' called with wrong argument types:

# PySide.QtGui.QWidget.closeEvent(Shiboken.ObjectType)

# Supported signatures:

# PySide.QtGui.QWidget.closeEvent(PySide.QtGui.QCloseEvent)

#

#

#Done executing .. OPT4001/OPT4001DTS_EVM/devInit.py

#End Time 2025-10-10 17:04:03.026000

#Execution Time = 154.549999952 s

#================ ERRORS:1, WARNINGS:0 ================#

What needs to be done to be able using the product?

Thanks in advance for your support.

  • 0
    TI__Expert 4710 points

    Hi Thomas, 

    Can you clarify if you are working with OPT3001 or OPT4001, both are mentioned in your post. 

    Thank you, 

    Joseph Scherphorn

  • 0 in reply to Joseph Scherphorn
    Prodigy 10 points

    Hi Joseph,

    As explained, we want to evaluate OPT3001DNPRQ1 and therefore ordered and received OPT3001DTSQ1EVM from Mouser.

    I meanwhile achieved to modify mEVMSelector.py which is located in C:\Users\thoma\OneDrive\Documents\Texas Instruments\Latte\projects\OPT4001\OPT4001DTS_EVM.

    But commenting out lines 83 to 89 and also setting VID and PID values to decimal didn't help.

    Thanks for helping us getting the EVM work.

    Thomas

  • 0 in reply to Thomas Kratt
    Prodigy 10 points

    Hi Joseph,

    As explained, we want to evaluate OPT3001DNPRQ1 and therefore ordered and received OPT3001DTSQ1EVM from Mouser.

    I meanwhile achieved to modify mEVMSelector.py which is located in C:\Users\thoma\OneDrive\Documents\Texas Instruments\Latte\projects\OPT4001\OPT4001DTS_EVM.

    But commenting out lines 83 to 89 and also setting VID and PID values to decimal didn't help.

    Thanks for helping us getting the EVM work.

    Thomas

  • 0 in reply to Thomas Kratt
    TI__Expert 4710 points

    Hi Thomas, 

    You can find the OPT3001 GUI download here:

    SBOC443 Support software | TI.com

    The OPT4001EVM uses a different mother board then the OPT3001EVM.  The OPT4001 GUI does not work with the OPT3001EVM mother board. 

  • 0 in reply to Joseph Scherphorn
    Prodigy 10 points

    Hi Joseph,

    The GUI software you suggest is for the OPT3001EVM (I mistakenly tried it already, before opening this support case) but not for the OPT3001DTSEVM.

    Therefore the GUI software under your indicated link is incompatible.

    The mother board of the OPT3001DTSEVM is completely different and as it seems is identical with the OPT4001DTSEVM except for the plug-in module of the sensor itself.

    I would really appreciate if you could investigate precisely and more in depth in order to help us using the product.

    Thanks in advance for your support.

  • 0 in reply to Thomas Kratt
    Prodigy 10 points

    Hi Joseph,

    Let me apologize for my insisting demand. I actually thought communicating with an employee of TI hosting this case.

    So please ingnore and thanks for your effort in helping me.

    Thomas

  • 0 in reply to Thomas Kratt
    TI__Expert 4710 points

    Hi Thomas, 

    Apologies for the confusion.  Please use the OPT3004EVM GUI which you can download here: 

     OPT3004 data sheet, product information and support | TI.com

    This software will work with the opt3001 without modification. 

    Please also recognize that the OPT3004DTS is what you will need to purchase if you would like to order devices for production post testing. 

    the opt3001DTS is not currently a device that is for sale or in production. The OPT4003DTS is the same as the device you are evaluating. 

    Thank you, 

    Joseph Scherphorn

  • 0 in reply to Joseph Scherphorn
    Prodigy 10 points

    Hi Joseph,

    Thanks for your comprehension.

    Indeed, the GUI software you pointed out and who is aimed for the OPT3004DTS and OPT4003DTS works without any problem and I can now read measurements. What I'm not sure is, if modifications should be made in the defined sensor profile, given that my sensor connected on the EVM is the OPT3001DTS and not the OPT3004DTS. Have you any insight here?

    I actually chose the OPT3001DTS because I opted for an automative grade sensor. Mouser has the OPT3001DNPRQ1 in stock, which seems to be the only available automotive grade sensor regarding OPT300x and OPT400x

    Thanks,

    Thomas

  • 0 in reply to Thomas Kratt
    TI__Expert 4710 points

    Hi Thomas, 

    The OPT3004DTS operates the same as the OPT3001DTS and has same LSB value for the different full-scale ranges of device, So, utilizing the GUI for OPT3004 is completely fine and requires no changes to be used with the OPT3001.

    The qualification of the OPT3001Q1DTS has been sidelined for the immediate future. 

    Why is the DTS package more attractive to your use case than the DNP package?

    Thank you, 

    Joseph Scherphorn

  • 0 in reply to Joseph Scherphorn
    Prodigy 10 points

    Hi Joseph,

    Ok, I understand that selecting the OPT3004 profile in the popup window of the GUI software is fine for operating the OPT3001 and measured values valid.

    I plan to use the DNP package, as it seems that this is the only package available for the automotive qualified variant of the OPT3001. But the EVM itself can't be ordered with the DNP, it comes with the OPT3001DTS.

    Can I still use the EVM containing the DTS to reliably evaluate the DNP variant or not?

    Thanks in advance for your support.

  • 0 in reply to Thomas Kratt
    TI__Expert 4710 points

    Hello Thomas,

    These 2 packages have same behavior and using one to evaluate the other should be fine. Only difference may be slightly different FOV  but this half-power angle for each package should be within ~1 degree of each other. 

    Thank you, 

    Joseph Scherphorn

  • 0 in reply to Joseph Scherphorn
    Prodigy 10 points

    Ok, great, that helps.

    Thanks a lot.