• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 440 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DRV3901-Q1EVM: DRV3901-Q1EVM to drive 4 parallel pyrofuses.

Diego Gil
Prodigy 75 points
Part Number: DRV3901-Q1EVM

Tool/software:

Hello, 

We need to test 4 pyrofuses in parallel and I was wondering what the easiest way is to sync 4 DRV3901 drivers if we had 2 EVMs (2 drivers per EVM).

Could we connect the HW OC pin to the 4 of the drivers?

Regards

Diego

  • 0
    TI__Genius 11761 points

    Hi Diego,

    Thanks for the question.

    As you mentioned we can  short the Trigger pins and drive them together.

    However, you will have challenge to run GUI for both boards together from a single PC. Another way to do would be to short all SPI lines between the two boards and use one of them as a master, We can support up to 4 devices in Addressable SPI and you can change the address from the GUI to keep changing the device to communicate.

    Let me know if this helps

    Also, little curious on how the end system will look like, Do all the 4 pyro fuses needs to trigger together?(or do you want to incorporate delays in between).  I am assuming they are for sperate power paths. 

    Thanks,

    Ibinu

  • 0 in reply to Ibinu Alaudeen Nadeera
    Prodigy 75 points

    Hi Ibinu

    Thanks for the answer!

    Do you think the SPI is fast enough so that it wont impact the timing aspect of the test? Also, wont we also need 2 GUIs even if we have SPI activation?

    Another possibility is to have 2 computers and trigger the 4 pyros with the HW trigger, right?

    Our system has multiple batteries in parallel with a pyrofuse each that need to be triggered simultaneously in case of a short circuit.

    Thanks again,

    Diego

  • 0 in reply to Diego Gil
    TI__Genius 11761 points

    Hi Diego,

    In case you are using single GUI, for the activation, there is a broadcast command available so that all 4 pyros can be triggered together.. So basically you can configure in the pyro fuse in the required state using the GUI( here you will have to write all drivers separately).

    Further you can use either of the options for deployment 

    1.  Using the  HW trigger with same signal going to all drivers
    2. Using SPI with broad cast command.

    Also, I feel it will be okay to use 2 computers is also possible 

    Can you comment on what kind of timing specifications are there in the system.

    Thanks,

    Ibinu

  • 0 in reply to Ibinu Alaudeen Nadeera
    Prodigy 75 points

    so basically, these would be the steps:

       1. connect to the first EVM and configure each of the drivers (pulse config and trigger)

       2. disconnect and connect the second EVM while the first one is still powered on

       3. connect to the second EVM and configure each of the drivers (pulse config and trigger)

       4. Activate common trigger (HW trigger or SPI if the SPI bus is commonized)

    Is this correct?

    Regarding the timing, it feels the SPI would add an unnecessary delay in the activation, since this is SW processed. We are trying to mimic the short circuit behavior in our system, which would be activated by HW trigger.

    //Diego

  • +1 in reply to Diego Gil
    TI__Genius 11761 points

    HI Diego,

    The steps look correct. Noted on the SPI delay part also.

    Let me know in case you are able to test it.

    Thanks,

    Ibinu