Vishay microBRICK SIC967EVB-A evaluation board review

View table of contents ...  

RoadTest: Become a Tester of the Vishay microBRICK® Synchronous Buck Regulator EVB

Author: JWx

Creation date:

Evaluation Type: Evaluation Boards

Did you receive all parts the manufacturer stated would be included in the package?: True

What other parts do you consider comparable to this product?: SIC438BEVB-B

What were the biggest problems encountered?: uncommon jumper size, not enough jumpers to set all possible configuration options, design software limitations

Detailed Review:

Introduction

Vishay's microBRICK was awarded "Most Innovative Product" China Artificial Intelligence Innovation Excellence Award in year 2020 for being "compact, easy-to-use and price competitive" solution, offering efficiency up to 95% for point of load (POL) DC/DC conversion. Like the similar microBUCK family, it contains an regulator and two integrated MOSFETs but (unlike the microBUCK) it also contains an integrated inductor. 

Marketing materials (from passive-components.eu portal) contain drawing of it's internal structure

microbrick internal structure

Vishay microBRICK family is advertised as their most integrated solution so far, bringing better efficiency, reliability and decreased size compared to the discrete solutions.

Marketing materials highlight improvements like:

  • operating frequency two times higher than a discrete solution,
  • +7% efficiency gain.
  • lower operating temperature than competing solutions (74°C vs. 99°C),

As microBRICK is described as an improvement to (older) microBUCK family, those two product groups share some common properties, so let's start with a brief comparison.

Vishay microBUCK family (advertised as capable of operating with frequencies up to 1 MHz) is divided into three sub-families, suitable for different usage cases:

  • high input voltage (up to 60 V) SiC46x,
  • low input voltage (up to 28 V) SiC43x,
  • server class hardware (up to 20 V input, embedded PMBus management interface) SiC45x,

similarly, Vishay microBRICK family (advertised as - due to higher integration level and better heat management [employing integrated inductor as an heatsink] - capable of operating up to 1.5 MHz), contain currently three different parts, each for one use case identified for microBUCK:

  • high input voltage (up to 60 V) SiC967,
  • low input voltage (up to 24 V) SiC931,
  • geared to server class hardware (up to 20 V input, integrated PMBus management interface) SiC951,

Both families are supplemented by several evaluation boards - and one of them (SIC967EVB-A) is a subject of the current roadtest. 

Unboxing

Evaluation kit has arrived (somewhat illegally by the way - it was released in error from customs office before clearance, so it is under some sort of correction procedure currently and it's legal status is unclear - thus unexpected delay in the roadtest) in an elegant cardboard box, filled in some sort of hard foam filling with a cut-out for the module.

{gallery}Module unboxing

External view

The box

The filling

Foam filling

top side

Top side view

Bottom side view

Bottom side view

Input and output of the module is terminated using screwed terminals allowing for firm connector placement, which is an important feature, especially when high currents are expected. Evaluation board has several test points prepared and  a configuration of converter parameters is possible using jumpers. 

This fact leads us to the first observation - jumpers are of less common type, with 1.27" pitch  and lower than expected endurance. On the photo below, result of this feature is documented - probably during the transport, PCB entered between layers of foam filling and one jumper slightly bent contacts it was placed over.  So - some care should be exercised when operating jumpers.

bent jumpers

There are also no spare jumpers included (that is less important when standard jumpers are used, but not everyone has spare 1.27" jumpers available) and some configuration options (for example: 12 V output with 1 MHz clock) would need at least one additional jumper above the set included with the board.

Full of surprises

One usually assumes that the schematics of the module corresponds to  the module itself. Well - this case is somewhat different. First indication of that fact was   discovery that the module starts operating at the input voltage much lower than stated in the datasheet, which includes following statement:

Connect to a voltage source: 36 V to 50 V. This reference
board configures 32 V as the minimal value of input voltage
to enable the chip, and 27 V as the input voltage’s
under-voltage lockout (VIN UVLO) voltage.

And - to the surprise - module was enabled at the input voltage below 8 V.

After closer inspection the cause was identified as different than documented value of R5 resistor (10 kΩ instead of expected 2 kΩ), which led to lowering of enable voltage to about 7.5 V and undervoltage protection level to 6.4 V.

Then, additional differences were visually identified (side note - some components are installed with markings visible [and those are probably considered as of interest to the user and meant to be field replaceable if necessary] and others are placed with marked side down; only components with visible markings were checked). 

changes vs documentation

Those differences (marked with red ovals on the schematics) are summarized below.

  • C3 capacitor: 56 μF was installed instead of 120 μF from the datasheet, 
  • R5 resistor: 10 kΩ instead of 2 kΩ,
    R5
  • R10 resistor: 43 kΩ instead of "not populated",
    R10
  • C19 capacitor: 100 μF instead of "not populated",
    C19

Three last changes are particularly interesting. Change of R5 and R10 resistors was probably caused by a desire to prevent user errors - as original board was supposed to be run from at least 32 V and there was option to select "unregulated" output voltage (J1 position 1-2, connected originally to a "not installed" voltage divider resistor R10), there was an easy way to destroy 25 V rated output capacitors. 

After this change:

  • module can be powered by the input voltage < 25 V, protecting the output filter from accidental damage,
  • there is no way of selecting "unregulated" output using a jumper on a unmodified evaluation board,

But the documentation should be updated to reflect those changes.
 

This discovery leads to another interesting topic: output voltage range. Datasheet of SIC967 states that "recommended output voltage" should be in 0.8 V - 15 V range. Evaluation board's datasheet - in turn - contains the following information:

Note
• The output capacitors are rated to 25 V. Should a higher output
voltage be required, the output capacitors should be changed to
ones with an appropriate higher voltage rating

There are two interesting facts in this note: the manufacturer expects the board to be user-modifiable  and that the output voltage can be set to at least 25 V. 

So - why is the recommended output voltage limited to the 15 V? Some answer can be found in microBUCK evaluation board's documentation, where bill of materials includes several positions describing main inductor (L1), with the values described as below: 

  • 1 μH (recommended for Vout = 3.3 V),
  • 2.2 μH (recommended for Vout = 5.0 V),
  • 5.6 μH (recommended for Vout = 12 V),

Taking into consideration that microBRICKs have inductor built-in, some compromise is to be expected.

Then another question arises - what is value of built-in inductor? Datasheet is not providing that answer, in fact it contains some equations (probably ported as-is from microBUCK datasheet) that are using component values not provided by the documentation - like below equation for minimum value of output capacitor that is dependent on the (missing) inductor value

cout equation 

The software

And here enters converter design software provided by the manufacturer. It is called PowerCAD and is advertised as more advanced than the competitor's oferring. Typical session (after accepting a legal disclaimer), starts with selecting a regulator from either microBUCK or microBRICK family. Regulator can be selected by the part number or using some selection criteria

chip selection

then, design parameters can be selected 

parameters

with some more advanced options (like startup voltage and output capacitor types and composition) hidden by default

advanced parameters

For our microBRICK converter, switching frequency can be only selected from the predefined list of:

  • 300 kHz
  • 500 kHz
  • 750 kHz
  • 1000 kHz

This is some limitation compared to microBUCK configuration, when operating frequency can be set "by hand" from the full range of values (like below)

microBUCK freq

Given the fact that the evaluation board's predefined parameters are like below:

ev_predefined_vf

it seems we have  limited cross-section between PowerCAD settings and the board configuration. Fortunately, operating frequency is output voltage dependent (using the equation below)

freq vs vout

so, three positions of the frequency setting switch (J3) translate to much larger set of possible frequencies (especially given the fact that inclusion of R10 resistor gives us another predefined output voltage of 4.2 V).

Next step generates a schematics (like below)

48V to 3.3V

Additional options are available after creating an account - after that we can run simulations

circuit simulation

and calculate expected efficiency, power losses and thermal characteristics (which is advertised as unique to this software)

thermal characteristics

Module evaluation

As we have mentioned earlier, simulation software seems to have limited parameter cross-section with the development board configuration options, so in the first step let's see what can be configured besides settings printed on the board (and in the datasheet).

First - we have another preset output voltage (thanks to including R10 resistor), which is giving us the choice of:

  • 3.3 V
  • 4.2 V (undocumented one)
  • 5 V
  • 12 V

Second - as the operating frequency is output voltage dependent, three choices of J3 jumper translates to the following possible operating frequencies (values also present in PowerCAD are highlighted):

  • 272 kHz (at 3.3 V)
  • 330 kHz (at 3.3 V)
  • 348 kHz (at 4.2 V)
  • 399 kHz (at 3.3 V)
  • 415 kHz (at 5 V)
  • 422 kHz (at 4.2 V)
  • 503 kHz (at 5 V)
  • 511 kHz (at 4.2 V)
  • 609 kHz (at 5 V)
  • 996 kHz (at 12 V)
  • 1200 kHz (at 12 V)
  • 1462 kHz (at 12 V)

Next - to check calculation repeatability and calculate missing values from the datasheet, let's try to calculate inductor value. Using the equations from Analog Devices or Richtek documentation:

ripple equation1

inductor ripple

and simulation output (for various output voltages and operating frequencies), obtained from simulation stage of the PowerCAD (it is worth noting that not only signal values can be calculated, but also more advanced parameters like ripple current value)

12V 1MHz simulation results

gives very similar results of about 3 μH - with most distant calculations being for high frequency (12V/1Mhz and 5V/1MHz) or low output voltage  (1V/300 kHz), which may hint at limited simulation accuracy at edge cases.

Another interesting observation is an output capacitor's value - most simulation results advise at least 10-20 22 μF ceramic capacitor set - which explains addition of 100 μF C19  on the development board:

cout1

cout 20x

The next planned test was an load change response, but the results are probably mostly influenced by the inductance of the load, not the converter behavior. Following plot shows a response to load change from 0 A to 3A and again to 0 A with the board configured for 3.3 V output and 400 kHz frequency.

High amplitude and high frequency ringing was observed (especially during load switch-off), but given it's frequency range (horizontal scale is 200 ns and vertical 2 V) it is most probably caused by the parasitic inductance of the 1 Ω load resistor (selected as metal film instead of wire-wound one to limit the influence of it's impedance but still not good enough it seems).

ringing 

Summary

In my opinion this evaluation board is a low-cost (only slightly more expensive than the converter chip itself) evaluation tool that is greatly expanding the possibilities of testing the converter, beyond current design software capabilities and the available documentation. As a reference design it can be used to test configurations not possible to configure in the software provided.

On the other hand, design software (currently in beta - according to the version identifier displayed) and documentation could be expanded to:

  • more precisely describe the board,
  • allow for more configuration options to be simulated

and the board itself can be modified by using standard jumper size for better endurance.

Another observation is that the some advertised advantages of microBRICK regulator (mainly higher than microBUCK family attainable switching frequency) cannot be currently either simulated or easily set on the evaluation board.

Anonymous
  • Its quite chill , I think instead of seeing this as a competition, roadtest should be seen as a community collaboration where even us the readers also have a role to play, I think that the fact that element14 or more specifically is doing a really nice job selecting the members in RoadTest applications, rotating between new and experienced members.

  • Hello! maybe I was over interpreting the phrase "Based on my understanding of this review it falls below that standard." - but I am not an English speaker after all...

    I think that - after recovering the initial application - my review was probably 80-95% complete according to it (it was really simple - but, it seems, enough to get review of  this ~30$ part). Most pivoting was done about my idea of doing this review - that had to be corrected based on the following events and discoveries.

    Anyway - tanks for constructive criticism (one never knows if the material posted is of good quality without some discussion)

    And many thanks for the support from community members and team - it was really nice and encouraging!

  • The statement "you consider this test substandard" is in error. I cannot find in any of my posts where I indicated the review is substandard. If you are inferring, reviews that deviate from the approval process are substandard, that is not my position either.

    My original post questioned using the simulator as content to create a review. I opened that post with a positive comment on the jumper anomaly. In that same post I looked for clarification. In the response to my post the reviewer explained the delay. The individual discovered the material he/she was going to review was already covered so they pivoted. We would not be having this discussion if the response had indicated there was approval to pivot.

    My position ignores content and focuses on process. Pivoting (i.e. changing to material not part of the application because of some unforeseen reason) from the application submitted, to something the reviewer decides is acceptable, without approval from the review committee, jeopardizes the integrity of RoadTest reviews.

  • I think there is also reputation of the reviewer - not everyone can get high-end power supply to test (for example: I have applied but was not selected Slight smile ), and posting low quality reviews would hurt one's reputation (thus lowering the chance of winning future reviews)...

  • (I have had a test where the vendor was expecting more. I offered to send the components back but didn't hear back after that)

  • Yeah this looks like a disagree point :)

    I would not accept Road Test committee (or vendor) interference. That would be the last test I'd ever do.

    Integrity is maintained through an integer report of an integer reviewer?

  • I respectfully disagree.

    The integrity of RoadTest Reviews is maintained through process.

    A process to apply.

    A process to award.

    A process to deliver.

    A process to change.

    I find it unacceptable for a reviewer to pivot from an application without RoadTest committee approval.

  • The creative power is to the reviewer. And the critique power is to the readers.

    The process is flawed if the reviewer makes the decision on what is an acceptable review.
    I do that for every road test. Even if it is opposite to my application. The bench experience drives the report.

    We 've seen reviews that had little merit. 
    This one has intellect. 
    My review was: "oh, the supplier changed some components vs the documentation".
    This review drills into real-board vs documentation. "Why did they make changes, what to learn from it ..."
    Engineering delight.

  • I agree the review has merit. That is the my contention.

    The process is flawed if the reviewer makes the decision on what is an acceptable review.

    What if the review didn't have merit? Who determine the merit? Do we only call to task reviews that don't have merit?

  • Just step into the author's shoes for 1 second. Please.
    It's an integer and quality-full review.

    What is wrong?

  • My IT Security background makes me a stickler for process. What is appropriate if a person is unable to deliver on the original application review?

    The RoadTest Review is open to abuse if it is acceptable to change from the application plan without some oversight.

    One of the challenges for a RoadTest tester is writing an application. There are E14 Community resources to help with this.

    I take a different route and use AI to write the application. I'm awarded the review knowing I can't deliver on the application. But I really want that free power supply that comes with the review. I pivot and post a revised review siting reasons.

    I feel the application is critical in maintaining the integrity.

  • In this case, it may be good to talk with the road tester. He was hit with legal issues while receiving the kit.

    Also: this is a great road test review, in my (never humble) opinion.

  • I took a look at this review. Over the years of managing the roadtest program, my mindset regarding what's a good review or not has evolved. Some of this evolution has to do with working with the members who do apply. Some may not be experts in a certain area. Some may not always have all the test equipment. And some have their own idea about how to test it.

    But now (almost nine years after taking over the program), I ask myself: Is the review informative? Does the review have value? Does the review give a good overview of the product, which is something that the sponsor values? Did the reviewer work with the documentation and, if so, did he/she find any problems with it?

    I think this review answers yes to those basic questions. I think most reviewers could find something they could have done better if they had a chance to do it again.

    But I appreciate your interest and comments about the roadtest program. I value member feedback. It makes me think now that I guess I need to be more transparent in explaining delays, which many times are caused by health/family/personal issues of the roadtester, which I always accommodate.

    Randall Scasny
    RoadTest Program Manager

  • I see your concerns. But the delay in posting the review I am somewhat responsible for. Basically, I have had a low number of applicants for some of my recent roadtests. When this happens, I have a couple of choices: (1) extend the enrollment period or restart the roadtest, (2) tell our social media team to continue promoting the roadtest (which element14 would pay to do, (3) reach out to members and ask them if they were available to do the roadtest. I am always mindful of the fact that our members have full-time jobs (for the most part) and even some of our retirees are busy people. If a member says he is busy but willing to do it, I will often give him a longer deadline. Off the top of my head, I don't remember the exact details, but I believe he was busy and I offered to extend the deadline if he agreed to the roadtest. In hindsight, I suppose I could have used other options. Hindsight is always 20-20. The roadtester had been communicating to me over the course of the roadtest. 

  • I'm happy to second that - I think the review was a very reasonable adaptation to circumstances. By the time   got his chance three "traditional"  reviews  had been published already. My own review changed direction based on the reality of the parts - I think that's to be expected.

    MK

  •  I would also encourage you to trust  and those who are accountable for the RoadTest Program to manage it.  They are going to be the only ones who will know all the details and any extenuating circumstances.

    Element14 is unique in that it has a culture of civility.  Your comments are atypical for our community and for you.  I hope you are well.

  • Lighten up suggests I'm taking this too seriously or being overly concerned. I was overly concerned at how my comments would be received. The content of the review has merit. I questioned if I should I be critical of the process to get it. Even well-meaning actions can have unintended negative consequences.

  • lighten up,  . This is a valuable road test review.

  • My firm belief is that the review should match the application. Deviating from the application is unfair to those RoadTest candidates that were not selected. Changes to the review submitted in the application should only be at the discretion of the RoadTest committee.

    It sounds like you had some challenges in getting the equipment. I hold you accountable, if you decided to pivot to other objectives after receiving the equipment late.

    I'm thinking the committee that awarded you the RoadTest understood there were other application that had similar objectives. Not being able to make your post before others is not a reason in my mind to pivot.

    If the RoadTest committee was aware of your proposed changes and agreed, than you met the objective of the RoadTest. Finding other things to explore in your RoadTest is great on you. Done without approval is also on you.

    I have always valued the RoadTest program. When my application is successful, I review the objective and do my best to over-deliver on them. I not only want the reader to get something from the review but I want to vendor to get a sense that they got a return on their investment.

    I would like to see successful applications posted as part of a RoadTest. List the candidates that were awarded the RoadTest and their application. It would be a challenge and push insight, if all candidates knew they were all delivering the same test.

  • Sorry to hear that you consider this test substandard. Let me explain to you some of the circumstances that led to the test report in the current form. The delay was caused by the customs issue - board was delivered, unpacked and then I have got information that it was delivered in error before completing of customs procedure; it is now under special correction procedure, that can take months and I am not officially supposed  to use the board in the meantime (but I cannot return it as it was unpacked).

    In the meantime, three other members that were selected to roadtest this module have posted their tests (and as they are all very experienced engineers, those tests were very good and covered most of the topics I have planned to test). As I believe roadtest is more  collaboration exercise (all the team is going to explore different aspects of the product tested) than a competition (everybody is doing the same tests again and again and let's see who is doing them better), I have decided to explore issues in my opinion less explained to this point.

    First one was a documentation issue - Jan  Cumps  have found that one of the resistors was of different  value that on the schematics. I have found several elements that were different in reality than in the docs and offered a possible explanation why. 

    Then there was an  issue of output capacitor bank size. As the documentation is not providing means to calculate it, I had to use the official design tool - and realized that a reference board is an extension of the tool (component parameters cannot be calculated in different way, which I have proven by calculating the value of internal inductance - which is not present in the datasheet, which prevents the use of many standard equations ), and they  aren't very compatible out of the box (board parameters are not fitting simulator settings)