For todays #FreeCADFriday I can show this mockup of a NIM Module made at work.
In the next step, the green PCB will be replaced with a proper one exported from #KiCad so I can make the required modifications/holes in the orange front-plate.
This was made using the assembly workbench - its my first project using assembly in FreeCAD
See https://en.wikipedia.org/wiki/Nuclear_Instrumentation_Module
I know, this is is not the worst footprint that vendors have come up with, but why, what is going on with the TexasInstruments engineers coming up with that?
What is the reasoning behind the chamfers on the exposed pad? And those T-Shapes on Pin 12 and 23?
If it weren't for those rather irrelevant changes to a 'default' footprint, we could generate them with out `no_lead` generator in the kicad library tools.
Related: https://gitlab.com/kicad/libraries/kicad-footprints/-/merge_requests/4703
I am looking for ideas how to impove the pin-stack display in #kicad symbols.
Since version10, we have 'native pin stack'. Which has rendering issues we would like to fix.
The idea is to add settings on how a pin-stack is rendered. One of them being
1st pin-in-stack (number of not shown pins)
Example:
7 (5)
Which obviously is not ideal, because one cannot tell if 7 or 5 is the count without investigating further.
https://gitlab.com/kicad/code/kicad/-/work_items/25099
(Please read the issue first before answering)
New #NameThatWare challenge. I can't tell much on where I took this picture without revealing to much.
I also forgot how this thing is called, but I know what it does :)
Please hide your deductions and guesses behind a CW to not spoil it for others. Googling is fair game.
Please don't just write a single word as answer, instead describe your observations and deductions so we all can learn about electronics.
Autodesk hat auch ein eher schwer zu findendes Dokument mit mehr Details dazu.
Die Website- hat wie nun üblich keinen Support Kontakt, nur einen nutzlosen Chatbot.
Über den bin ich an einen Mitarbeiter gekommen. Der hat ein Ticket aufgemacht, nur mit dem Ziel mit die Richtige eMail Adresse mitzuteilen. Der Support dort hat mir dann nach etwas mehr als einer Woche mit dem Link zu dem .pdf geantwortet.
https://damassets.autodesk.net/content/dam/autodesk/www/pdfs/autodesk-eu-data-act.pdf
Nicht "klar und verständlich" wie es vom Gesetz gefordert ist.
Wer hatte denn den EU-Data-Act auf dem Schirm?
Da ist unter anderem eine Verpflichtung drin das ein SAAS-Anbieter dem Kunden helfen muss auf einen anderen 'gleichwertigen' Service umzuziehen.
Die @BNetzA hat da ne nette Übersicht geschrieben: https://www.bundesnetzagentur.de/DE/Fachthemen/Digitales/DataAct/Hintergrund/3-Anbieter/start.html
Ich hab das mal zum Anlass genommen bei Autodesk ein Ticket aufzumachen und nach der Migration zu "Ondsel Lens / FreeCAD" meiner alten Fusion360 Sachen zu fragen. Ich bin sehr gespannt was als nächstes passiert :)
So sah der Föhn in meinem Hotelzimmer aus.
Ich denke die sollten jährlich geprüft werden.
Das würde bedeuten das vor circa zwei Monaten jemand das Teil DGUV geprüft hat.
Das ein Kabel ohne Vorschädigung innerhalb dieser Zeit so kaputt geht kann ich mir kaum vorstellen.
Oder die haben 2 Jahres Intervall, was ich für nicht korrekt halte.
Please help me find a good symbol-name for those hex spacers. I am obsessed with not using male/female terminology in #kicad library.
The names should be rather short but also descriptive.
I would like to include at least the two types shown in the picture below. Perhaps also the 3rd type that has a stud with outside threads on both ends.
Related: gitlab.com/kicad/libraries/kicad-symbols/-/merge_requests/5594
This unfortunately means that all open merge-requests in the kicad-library-utils repo need to be manually re-opened in the KiLT repo. We could automatically move the open issues though.
The change of the repos name and default branch will also result in confusion and additional work for contributors. I do expect some MRs to be abandoned - above our usual rate.
Earlier today the #kicad library team did merge the 'kicad-library-utils' repository into the 'kicad-footprints-generator' repo. While at it, we also renamed it to 'kicad-library-tools' (KiLT) and changed the default branch to main.
We want a mono-repo for all tooling to simplify maintenance. A few years back we did a similar thing with the 3d-generator.
There still a lot of open tasks. This was just the first step, now the cleanup commences.
Fedi, please do your magic. What type of connector is the on on the left?
Ideally answer with a MPN or datasheet link :)
Do you remember the share pic with the funny and cursed screws? Turns out, people were taking inspiration and are selling them on aliexpress.
I don't know how to feel about this. Right now I am confused.
"Material: Iron" sure gives confidence :)
The #RepairOfTheDay is this Dell Monitor from $work. The user somehow broke the power button. The plastic was bend inelastic (see the white discoloration). And the actual switch was also fucked.
I replaced it with one from my many kits of parts. And to fix the actuator, a random thing from my drawer was superglued to it.
Falls der Mond nachher doch nicht kommt, hat jemand nen anderen guten Plan für diesen Mittwoch Abend? Ka. was ich dann machen würde.
Da ich unsicher bin wie viel ich aus einer solchen Norm zitieren kann ohne in Grund und Boden geklagt zu werden möchte ich nur wenig Text daraus Posten.
Wenn ihr mehr wissen wollt, besorgt euch die Norm über ne Bibliothek und schaut da selbst rein.
---
Zum Abschluss: Sehr spannend finde ich diese Warnung vor Fehlinformationen die sich in Anhang B befindet:
Zusammen mit Freunden haben wir eben mal in die `ISO 12312-2` Norm "Augen- und Gesichtsschutz - Sonnenbrillen und ähnlicher Augenschutz - Teil 2: Filter für die direkte Beobachtung der Sonne" reingeschaut.
Das kann man bei libgen finden :)
Dort gibt es zwei nice Anhänge, einer der explizit Schweißschutzfilter erwähnt, und dann noch AnhangB mit einem Praxisleitfaden.
Quote:
> Filter mit der Schutzstufe W12
sollten ausreichend sein, um das Auge zu schützen...
We did some exploring at #CERN today and found this Hai-Voltage power supply. A great place for #blahaj to sit and take a look at all the humans working on detectors.
We don't quite now how to use it, apparently it does not work. No Hai was supplied by the device.
The humans talked about "backplane" and "branch controller", we don't know how this relates to #blahaj though.
Option 1 (everything 50mil) will satisfy the people that want consistency and the users of autoplace-fields.
But to make the workflow of putting the value/refdes into the symbol body nicer we need to shrink the text (Option 2)
What would be your preferred solution?
Can you think of other solutions?
