hedidwot

You’ve made my point well.

Absolutely I’ve already learnt it, and I don’t intend to stuff around translating. At first it’s one thing, maybe not cumbersome but then many things become a hassle.

Master and slave are not in and of themselves offensive words. You just assign offence to them, based on certain specific context, again proving my point.

Sometimes it’s not about typing.

In the electronics works the us a serial protocol called SPI Serial Peripheral Interface.

In schematics we might have a micro controller that connects to several sensors or memory chips on a pair of pins, 1 each for transmit and receive.

The micro controller is the master and the common nomenclature for the pin names is MISO and MOSI MasterInSlaveOut and MasterOutSlaveIn.

This overcomes confusion with regard to using things like TXD and RXD.

Wokeness has now suggested a bunch of alternatives.

PICO PeripheralInControllerOut and POCI… are the 2 leading alternatives.

Problem is I now have data sheets and schematics going back to the 1980s

It’s bullshit to me.

Words can have more than one meaning. Context and meaning matter.

I just want design cool electronics.

Yep. There was an assumption 20 years ago when common switches were 100Mbps and running cat5e that you’d have to upgrade cable to get the next speed tier, 1Gbps.

It propagated wildly, but was always incorrect. Cat5e was very much capable of gigabit Ethernet by design.

It was only beyond gig that you’d need cat6, and even then at short lengths 2.5/5/10Gbe has a good chance of working on cat5e anyway (but don’t do it).

High quality cat 5e would have done the job.

Original cables must have been faulty.

From Chinese parts

That’s what anti islanding is.

Prevents power from going into the grid when it’s down.

Way I read it is it puts surplus into the grid to keep you elec bills down.

800 watts isn’t exactly going to set an outlet on fire.

2 is fine.

I know where you’re coming from, I use a closed notebook with external display sometimes.

I might need to be more specific. If the notebook is used as a typical notebook, and one closes it with the intent of putting it to sleep, once sleep has been reached an external mouse should not wake it.

However if you do toggle the power settings to allow the machine to function with the lid closed and/or machine docked then you do want to mouse to wake it keep awake the machine.

Had this issue for years over 2 machines.

One had some shit in the background the prevented standby.

Other was so simple it pissed me off… … the damn mouse jostling around in the laptop bag was walking it up.

I’m still going to point the finger at windows because 1) there should be a better tool for identifying what is keeping a system awake and 2) should be default for a mouse to not wake a portable machine who’s lid is shut.

If it has anti islanding at least it’s unlikely to be a shock hazard.

That said are there any other concerns I’m missing?

My pending or existing projects.

A software defined radio server. Lives up top of an antenna mast running off PoE with an RTL tuner connected.

ADSB receiver, similar to above, but on a fixed frequency.

The above 2 could be virtualised in theory, but there is an advantage in having the cable to the antenna short and thus the sbcs live up antenna masts in an enclosure.

MMDVM hotspot for ham radio (this might not count as it HAS TO use the gpio pins on the pi, this can’t be visualised even with a USB port passed through.

As an audio server that would bitstream 24bit/96kHz to an amp.