Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: store diodes in the database #18

Open
gituser789 opened this issue Jun 9, 2021 · 2 comments
Open

Feature Request: store diodes in the database #18

gituser789 opened this issue Jun 9, 2021 · 2 comments

Comments

@gituser789
Copy link
Contributor

No description provided.

@tinix84
Copy link

tinix84 commented Jul 11, 2022

The switching model is only Qrr right? Or do you plan more complex measure?
Normally in double pulse test does not make sense to separate the diodes from the mosfet use in the double pulse, why not use a database if couple devices?

@gituser789
Copy link
Contributor Author

The switching model is Qrr and Coss, depending on the device type (PIN-Diode, Schottky, SiC-Diode).

Yes, for DPT it does not make sense to separate diodes from switches, due to the switching behaviour is controlled by r_gate.

Using coupled devices (switch with diode) is a good idea, but there are nearly endless of combinations out there....

All other parameters can be stored as usual

  • Forward characteristics
  • Cooling (r_th, housing area, ...)
  • Metadata (manufacturer, housing, ...)

So, from my point of view, the diode option is interesting to pre-select a diode for conducting losses, and may also for the Coss-losses. Qrr losses are, as you mentioned, tricky to include in the TDB.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants