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.

BQ78350: SDK to access LABVIEW

Part Number: BQ78350
Other Parts Discussed in Thread: BQSTUDIO

Hello,
customer wants to connect the bq78350-r1 over the SMBUS to Labview. How can we support this requirement?

Regards, Holger

  • Hi Holger,

    Some more information on SMBUS may be found here: www.ti.com/.../slua475.pdf

    A similiar question was asked in this thread. The discussion therein should prove helpful: e2e.ti.com/.../551052

    NI Provides support with respect to I2C in this tutorial here:
    www.ni.com/.../

    and SMBUS with their support hub here:

    https://www.labviewmakerhub.com/forums/viewtopic.php?f=12&t=853

    Sincerely,
    Bryan Kahler

  • Hello Bryan,
    customer uses the USB8451 with Labview but communication is not stable. He can read the voltages but not always.

    He wants to write the config file. Can this also be done with commands with BqStudio? Ha BqStudio a commando interface?

    Regards, Holger
  • Hi Holger,

    It appears in the NI Support forums a customer had a similiar issue and was able to solve the problem by decreasing the SMBUS clock to ~ 50kHz.

    www.labviewmakerhub.com/.../viewtopic.php

    Quoting jerratnz from the post at the link above, "At first, I set up an NI USB-8451 to read information from a smart battery through SMBus. I was able to use an example vi (Gerenal I2C Read.vi) to read info. Below is the FP screenshot. I tried different pull-up resistors, used 5K at the end. Still, at 100kHz, I see intermittent communication issues. It fails 2 or 3 times out of 10 times. Once I lowered the rate to 50kHz it became very reliable."

    Unfortunately, we do not support the NI device, questions with respect to the USB8451 and labview would best be answered by NI support reps.

    Sniffing the transaction from bqStudio + EV2300/2400 and replaying with a MCU may be a possibility.

    I have another option as well that I have e-mailed you about.

    Sincerely,
    Bryan Kahler