# Gooser: a 4-in-1 Lepton derivative

**URL:** https://community.simplefoc.com/t/gooser-a-4-in-1-lepton-derivative/5325
**Category:** hardware support
**Created:** [August 15, 2024, 5:20am UTC](https://community.simplefoc.com/t/gooser-a-4-in-1-lepton-derivative/5325 "2024-08-15T05:20:56Z")
**Posts on this page:** 1
**Showing post:** 74

<div class="post-metadata">

### Author: ![Antun\_Skuric](https://community.simplefoc.com/user_avatar/community.simplefoc.com/antun_skuric/32/21_2.png) [@Antun\_Skuric](https://community.simplefoc.com/u/Antun_Skuric)
#### Post date: [March 15, 2025, 9:24am UTC](https://community.simplefoc.com/t/gooser-a-4-in-1-lepton-derivative/5325/74 "2025-03-15T09:24:33Z")

</div>

Hey @dekutree64,

This is very interesting!  
In the first iteration of the DriveShield I’ve started form lepton and used DRV8300 with the SE3082G (its the version v0.1). And I was not able to get them to work at all. My DRV8300 were burning right away. So I figured it’s my ignorance that is causing this and I switched to the more integrated driver DRV8320. This time the current limiting stepped in and the driver was not burned, but I was never able to get any real output from the mosfets.

Once again my ignorance is probably the issue 😃  
But just in case its not I started doubting the mosfets SE2082G. I unsoldered them and tried to trigger them by hand on a breadboard and I was not able to trigger them properly, they kept burning right away. Once when I switched to the discrete mosfets I had no more issues. (more or less the same circuit on the driver side).

So provided that its not the issue of my lack of experience (a big if :D), do you think that it might be a SE2082G batch issue?

---

_[View the full topic](https://community.simplefoc.com/t/gooser-a-4-in-1-lepton-derivative/5325)._
