• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 63 subscribers
  • Views 1211 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.

LM25066 PMBus data reading

Winnie Chan94
Intellectual 300 points
Other Parts Discussed in Thread: LM25066

Hi 

I use 16*LM25066 in one board and each device have different address setting.

According to the test, GUI only can read one device, if i want to read another, GUI need to reopen.

I would like to know that can I read the data of all 16 devices at the same time? 

Thanks!

Winnie

  • 0
    TI__Genius 12380 points

    Hi Winnie,

    Please download the latest GUI directly at  --> "Tools & Software".

    You should only need to open the "PI-COMMANDER" software once. Then multiple devices should show up under the "Device Menu", each with a different address. You can then select each device to open up a device configuration GUI for that address.

    So to read 16x devices, you would need to open PI-COMMANDER once, then click each device address and open up 16x different device configuration windows.

    Thanks!

    Alex

  • 0 in reply to Alex Triano
    Intellectual 300 points

    Hi

    i use PI-COMMANDER for LM25066 IV monitor, but the dialogue window which shows communcation error as figure1 below will appear when operation and i found corresponding DAh command on datasheet as figure2, what is the erroe means? or is it a waring ? because SPM-GUI have no similar window when using.

    thanks!

  • 0 in reply to Winnie Chan94
    TI__Genius 12380 points
    Hi Winnie,

    It could be a driver issue. Under the windows start menu, there should be a series of folders for: "Texas Instruments" --> "PI Commander-0.8.x.x" --> "Advanced" --> "FTDI" and then an option to uninstall drivers or install drivers.

    I would recommend first uninstalling the FTDI drivers, then installing the drivers based on that folder.

    I do not know if that will solve this particular issue, but we have seen problems if using an older or newer driver than the GUI was designed for.

    Thanks,
    Alex