• 10 Posts
  • 1.01K Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle
rss






  • Not OP you are replying to, but make your own library of parts and footprint, and back it up.

    Nothing worst than finding a library online with the part you need only to find that the footprint is not the right one for whatever reason when you ordered the pcb.

    It takes more time, but once you have one or two projects under the belt, you will already have 90% of the parts and only need to do a few parts.

    When doing your own footprints, if you have the part with you, print the new footprint in the original size on a printer, as they will appear on the PCB, and put the part on the footprint to see if it makes sense. You will see right away if you have a glaring issue with the footprint.

    Spend a few hours double, triple checking your PCB design before fab . It takes a lot less time to do that than debugging the hardware. It will reduce your costs, especially as a hobbyist where you aren’t paid by the hour.

    If you need a batch order, order prototypes first. A lower volume first will be a bit more expensive, but buying 50+ borked PCB will be a bitch to fix.



  • I know Rust superficially. I use it to create simple tests for my embedded projects, so mostly just serial terminal with keyboard inputs.

    It works a lot better for me than python because Rust is a lot closer to C than python.

    So I cannot comment on Rust shortcomings. I was interested in knowing for what kind of projects Rust wasn’t good.


  • I am glad for your comment because I work with mcus and embedded solutions in C, so Rust, in that case, wouldn’t be neccesarily safer than C.

    I will have to look into it. I need to do 30h of training every two years, so I will learn Rust regardless, but I was thinking about eventually switching to Rust for embedded projects. Might just keep Rust as my scripting language because it is easier for me than Python