Starfighter

joined 2 years ago
[–] [email protected] 3 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

Tire dust, absolutely. Probably even more than ICE cars since EV's are heavier.

But brakes? Yeah no. To get the most range out of your EV you always want to slow down by recuperating/regenerating. The classic brake only gets used at (near) standstill or the occasional hard braking for collision avoidance.

[–] [email protected] 3 points 2 weeks ago

Regardless of the sponsorship in this video, SuperfastMatt's videos are awesome. Really interesting projects delivered with great humor.

[–] [email protected] 2 points 3 weeks ago

I like that they translated the signature

[–] [email protected] 4 points 1 month ago* (last edited 1 month ago) (1 children)

You can boot a live-usb, mount the remaining drive(s) and nixos-enter over like you would if you were installing NixOS for the first time.

This allows you to make changes and build a new generation using the network connection of the live-usb.

[–] [email protected] 6 points 1 month ago* (last edited 1 month ago)

Great video. Something I want to touch on:

He kinda makes the assertion that supply must exceed demand which I guess is ok for most items.

Especially in SA once you leave a surface, demand of most items will plummet close to 0. The only demand will be ship requests and defense stuff.

But I can't count the number of times I had to go back and increase iron plate production, green chips, copper, red chips, etc... It's always the same few items but as your factory grows, demand seems to always beat supply at multiple stages.

In those cases these kinds of balancers will not distribute the little supply evenly, making parts of the factory grind to a halt which is not ideal.

[–] [email protected] 5 points 1 month ago* (last edited 1 month ago)

There are some experimental models made specifically for use with Home Assistant, for example home-llm.

Even though they are tiny 1-3B I've found them to work much better than even 14B general purpose models. Obviously they suck for general purpose questions just by their size alone.

That being said they're still LLMs. I like to keep the "prefer handling commands locally" option turned on and only use the LLM as a fallback.

[–] [email protected] 1 points 1 month ago (1 children)

What card are you using for your room overviews?

[–] [email protected] 8 points 2 months ago* (last edited 2 months ago) (1 children)
[–] [email protected] 3 points 2 months ago

AutoMalls get most of the way there. So I'd guess its mostly combinators of various kinds.

[–] [email protected] 3 points 2 months ago

I've done the same. I put on a single layer of clear coat and it has been perfectly water tight.

[–] [email protected] 34 points 2 months ago* (last edited 2 months ago) (2 children)

The game "Deep Rock Galactic"

Space dwarves (solo or co-op) mining in procedurally generated caves while getting bugged by the local fauna.

There are a few different mission types, four unique classes and a vast weapon upgrade system to explore.

Also features the best (non-voip) communication system ever.

Highly recommend. Rock and Stone!

[–] [email protected] 3 points 3 months ago* (last edited 3 months ago) (1 children)

To expand: Just configure whatever profile you're using (dev, release, ...) to have link time optimization (lto) enabled:

[profile.release]
lto = "fat"

Reference

1
submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/[email protected]
 

Hi, this post is structured similarly to r/PrintedCircuitBoard 's review request format. Since we don't have any PCB communities over here yet, I thought that this might fit in here and can maybe spark some friendly discussion.

This is a relay board controlling electrically driven windows and blinds. For this purpose it has some additional connectors to a weather station, interior sensors and an LCD screen.

It is replacing a ~20 year old board that has started to develop some annoying quirks. I've mostly copied what the original board did and adjusted it for the ESP32. This is not a production board and if all goes well, I will only ever assemble a single one of these.

The primary usage scenario is that the MCU will monitor the weather station and then actuate the motor groups (M1 - M6 connected on J3 - J8) to keep the indoors temperature and humidity in check.

At least during summer time the board will likely run 24/7 and will hopefully be used for a number of years. For maintenance reasons I've tried to keep it simple and the component count low.

Mains power is supplied from J1 and being fed to the motors via the relays. PS1 converts the line voltage to +5V DC for the relay coils and some auxiliary components. The switching regulator U2 steps that down to +3.3V for the MCU U1 and IO Expander U3.

The board size is mostly constrained by the preexisting mounting holes which gives me plenty of space to work with even with just a 2 layer board. The enclosure containing the mounts is installed indoors and is finger-pokey-tight.

Jumper JP1 allows me to supply the MCU devkit daughter board with +5V, should I ever replace it with a different one. Similarly J11 exists for future expansion.

J10 mounts another daughter board (not included in review) facilitating communications with the weather station. Should the station ever need to be replaced I can swap in a new, matching board.

There aren't any high-speed connections on the board. The fastest one is likely the SPI connection to the LCD controller but I can slow it down in firmware if necessary.

Regarding the DNP components: There are only 5 motors installed at the moment so I will cover the sixth slot with a piece of plastic for now. R1 and R2 will only be populated if the 10k pullup resistors integrated into the MCU are insufficient for typical baud rates.

While it is not the first board I've designed, it is the first one carrying mains power (European grid 230V@50Hz). I'm using 2 oz copper to accommodate the motor currents within reasonably wide traces.

In case anyone is interested, it will be running the ESPHome firmware to easily integrate with the Home-Assistant smart home solution. This also pushes firmware maintenance from me onto the ESPHome devs.

3D render from front (no 3D model for relays K** and MCU board; 3D model for J1 and J2 is a stand-in of same outer dimensions): 3D Front

Orthographic view from front: Orthographic Front

Schematic:

Schematic

PCB All layers (For reference: thickest traces are 2.5 mm / ~98.4 mils; thinnest traces are 0.25 mm / ~9.84 mils): All layers

PCB Front layers excluding Silkscreen: Front layers

PCB Back layers + Front Fab layer: Back layers

view more: next ›