Starfighter

joined 1 year ago
[–] Starfighter@discuss.tchncs.de 4 points 1 month ago* (last edited 1 month ago)

And please don't understand this the wrong way.

Ibis seems like a really cool project but with it being roughly half a year old me and many other people here simply have never heard of it before.

Including even a single short sentence describing what Ibis is in this and future posts helps us find projects that we care about more easily.

And we obviously care about Rust projects, otherwise none of us would be here.

[–] Starfighter@discuss.tchncs.de 4 points 1 month ago (1 children)

Ibis is a federated online encyclopedia similar to Wikipedia.

This should be the first sentence of the post body.

[–] Starfighter@discuss.tchncs.de 3 points 2 months 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 1 points 2 months ago

That's for a single one but at tens of MW even a bunch of satellites isn't going to get solar panels to produce an appreciable amount of power.

This video goes into the details of what kind of performance we can expect from the constellation

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

No the observed power on the ground is on the order of mW/m².

Comparable to moonlight and so far no one has classified that as a weapon.

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

As always with these revolutionary startups, be careful with what you believe:

EEVblog 1637: Solar Freakin' Space Mirrors! - Reflect Orbital DEBUNKED

At least this one is actually possible and doesn't attempt to defy the laws of physics.

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

Also crashes for me with 0.2.1

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

Found this comment with some links. Couldn't find anything from an admin during my short search.

The exact same problem arose for Voyager users in March when Voyager dropped support for Lemmy 0.18.

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

For some people logging out and back in has helped but I've seen multiple beehaw users state that this doesn't work for them.

This seems to be because beehaw is intentionally staying on an old Lemmy version.

Not sure how the Dev wants to handle this since they've got enough work on their hands and this issue should resolve itself once beehaw upgrades.

For now your best bet is to try re-logging and if that doesn't work to roll back to a previous version of Eternity.

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

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

[–] Starfighter@discuss.tchncs.de 1 points 4 months ago

Chevron 7 eingesperrt

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

Always mocking Dr. Daniel Jackson. Poor guy

 

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 ›