Hi there!
I am currently working on my tesla coil which
is almost done. I am using the OneTesla TC design as a reference for my
DRSSTC with primary feedback. The last thing which is missing are IGBTs.
If you look at the OneTesla design, you will observe high frequency
pulses going to the primary (feel free to see http://onetesla.com/). The primary frequency (chosen
with primary capacitor and coil itself) matches the secondary resonance
frequency. This already creates problem, because it is around 230kHz.
This can cause problems later, because of the 340V bus and up to 300A
pulses. This forces us to use IGBT, which usually can switch as fast as
200kHz maximum. There are specified IGBTs for this job, but I not
interested into ISOTOP package IGBTs (or similar high power IGBT and
expensive things) anyways. There is very experienced IGBT, the
FGH60N60SMD out there, which seems to perform just fine up to 300kHz and
can handle presented voltages and current. And that is actually, where
the problem starts. There are so many variations of 60N60 IGBT out
there, please help me. IXGH60N60C3D1 IGW60N60H3 FGA60N65SMD FGH60N60SMD The price really matters for me. If not, I would just
simply pick the FGH version. My question thow is, if there is a difference
between those, maybe, if there is better version of 60N60 IGBT than FGH (like
IXN...). If there is not difference, does it mean that I just pick the
cheapest one and it will work like a charm? Alse, if there is not better
IGBT version of 60N60, I will take the FGH60N60SMD and we will be settled.
Let me know your experience. Thanks
When clicking the "Order at JLCPCB" button after generating the Gerber file, the popup says "Connecting to server..." for about half a second, then it goes away and nothing happens. There are no errors in the Javascript console. There are 2 AJAX calls that happen (save and some Gerber version call) and both return a status of 200. Inspecting the calls show that everything appears successfully.
If I go into the Save API call and look at the returned URL in the JSON object, I can extract the JLCPCB url and manually navigate to it in my browser.
The URL looks like: https://jlcpcb.com/quote/eda?eadLink=2&uuid=XXXX27XXX3ecXXX6995XXX563078XXXX
#Bug Reports#Вчера проверял плату на наличие связей и ошибок DRC ошибок и предупреждений не было, сегодня вечером запускаю проверку DRC (а добавил только текст на шелкографии) выскочило предупреждение что земля не подключена... Только вот найти где она не подключена - нереально .
Вот ссылка на проект:
https://easyeda.com/editor#id=|306666885d4c4d2497a9bc55b351c68a|3322ebc0a33f4fb2911d35178232be23|10f726478f17458595551cb9dc340653
Как найти не подключенную дорожку?
#PCB#Hello!
I was hoping I could get some initial feedback for my first attempt at reproducing a simple LED light bar design.
I created the initial Schematic using generic LEDs and then substituted the Cree XP-E2 packages. I am unsure of whether I have selected those components properly based on the number of DRC conflicts I generate.
I am hoping that the simplicity of this circuit lends itself to few errors with the PCB layout. I used an existing PCB I had on hand, as a guide for the copper areas of the 11 nets. I believe the large copper areas are necessary for Power Integrity in this instance.
https://easyeda.com/darryl.lawler/Light-Curtain
I admit that I have been rather ham handed in my attempt, so please feel free to nit pick. I need the criticism.
Thank you, in advance, for the assistance. Looking forward to building my skillset.
EDIT: I added attached images of the reference PCB to my project page.
#PCB#At the moment if I define in the PCB canvas attributes a default track width, this attribute is lost if the project is closed and reopen. It would be nice if this info could be stored as part of the project info.
Same suggestion for via attributes. For via in particular, it would be nice to be able to specify the attributes in the canvas, like for track width. As explained here, at present the default properties are the ones last edited on a particular via, but, if I do not remember what is the last via created, there is no way to visualize them (of course I can create a dummy via and inspect its properties, but in my opinion it is not a natural way to operate).
#Feature Requests#





