Starfighter

joined 1 year ago

Why not set up backups for the Proxmox VM and be done with it?

Also makes it easy to add offsite backups via the Proxmox Backup Server in the future.

[–] Starfighter@discuss.tchncs.de 9 points 2 months ago (1 children)

This person had the same issue and they've just logged out and in again

[–] Starfighter@discuss.tchncs.de 8 points 6 months ago

Cushy is an experimental Graphical User Interface (GUI) crate for the Rust programming language. It features a reactive data model and aims to enable easily creating responsive, efficient user interfaces. To enable easy cross-platform development, Cushy uses its own collection of consistently-styled Widgets.

[–] Starfighter@discuss.tchncs.de 5 points 8 months ago

Can't exactly remember which car it was but some of the early and smaller EVs didn't necessarily come with a navigation system. Think along the lines of Chevy Bolt or Nissan Leaf.

[–] Starfighter@discuss.tchncs.de 8 points 8 months ago* (last edited 8 months ago)

Not OSM or Open Source but "A Better Route Planner" (ABRP) was one of the first good EV routing apps and got pretty popular.

Especially early on it was often smarter than the built-in routing systems if the car even had one.

Also available as a website: ABRP

[–] Starfighter@discuss.tchncs.de 11 points 9 months ago (4 children)

Are there any implementations of this out there or is this purely theoretical (at this point in time)?

[–] Starfighter@discuss.tchncs.de 2 points 10 months ago* (last edited 10 months ago)

According to Scott Manley's video on the topic the probes would need to arrive at the correct time in order to form what is effectively a huge phased array antenna.

Only then is the combined transmission power of these tiny probes large enough to be received on earth.

[–] Starfighter@discuss.tchncs.de 2 points 10 months ago* (last edited 10 months ago)

Adding a Turing award to your profile is certainly one way to flesh it out

[–] Starfighter@discuss.tchncs.de 5 points 10 months ago

Typst

You can use their online web-editor (similar to OverLeaf for LaTeX) or download the open-source engine and run it locally (there are extensions available for many text editors).

Compared to LaTeX I find it much more comfortable to work with. It comes with sane, modern defaults and doesn't need any plugins just to generate a (localized) bibliography or include links.

Since Typst is very young compared to LaTeX I'm sure that there are numerous docs / workflows that can't be reproduced at the moment but if you don't need some special feature I'd recommend giving it a shot.

[–] Starfighter@discuss.tchncs.de 1 points 11 months ago* (last edited 11 months ago)

Not a monetary one, no.

* (there might exist some business power tariffs that coincidentally benefit from this but nothing you'd use at home)

[–] Starfighter@discuss.tchncs.de 9 points 1 year ago (1 children)

The development of Piper is being driven by the Home Assistant Project. That probably makes it one of the larger OSS TTS projects. Hope may not be lost yet ;)

[–] Starfighter@discuss.tchncs.de 2 points 1 year ago (1 children)

The main reason for splitting up the relays into two sets is that with 10A traces the connector pins would violate minimum separation distances. I would have to get even larger connectors. The ones in the design have 5 mm pitch.

I'm assuming the original board also did this for the same reason although their board is set up for 8 motors split into sets of 4.

I've also had some trouble sourcing a 10A fuse suited for inductive loads but I'm sure I could find one with some more time.

The whole board is on its own house circuit fused with a 16A breaker.

 

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 ›