I'm moving my blogging over to Patreon. You can find me at Jacob Zelten | Patreon
Not that I expect to make money, just that its an easier platform to work with. And who knows how long Blogger will still be around.
For those few that followed me here, be aware that I will be republishing a few of my favorite pieces over there, to get it up and running.
For reasons I won't get into, I searched for information about the meme Don't Create the Torment Nexus. (If you're not familiar, check it out first) on a well-known search engine.
And to my surprise, the search engine came back with a summary of the plot of Don't Create the Torment Nexus.
A book that does not exist.
Here it is, for your enjoyment, and in case you ever get asked to write a book report about it.
"Don't Create the Torment Nexus" is a science fiction novel by Walter Jon Williams. It explores themes of technology, ethics, and societal collapse in a dystopian future.
Technological Caution: The title itself serves as a warning against the potential dangers of unchecked technological advancement.
Dystopian Society: The story is set in a fragmented United States, where state governments impose tariffs, creating a chaotic environment for entrepreneurs and mercenaries.
Character Dynamics: The narrative follows two main characters, Cowboy and Sarah, whose paths intersect in a world driven by profit and violence.
The novel has been noted for its prescient themes, reflecting contemporary issues such as corporate greed and societal fragmentation. It is recognized as one of Williams' best-selling works, appealing to fans of the cyberpunk genre.
The most important thing to know about how DCC works is this: you don't need to know how DCC works. Just as you can drive a car without knowing how an engine works, and use the internet without knowing TCP/IP, the only things you really need to know are how to set up and use DCC - and that's covered in great detail elsewhere on the DCCwiki.
Still here? OK, you really want to know how DCC works. There is a lot of misinformation and misunderstanding about DCC, so we'll take things step by step. If you know much about electronics, some of this will seem very basic. Please bear with it.
DCC is very different from DC. You may have heard the adage "with DC, you control the track; with DCC, you control the locomotives". And that's a very good way to look at it.
With DC, you control the voltage across the two rails of the track - for HO, typically that's between 0V and 14V. The voltage powers the motor, which determines how fast the train runs. And that's it. If you put two trains on the same track they both run (although probably at different speeds depending on the gearing between the motor and the wheels). If you turn the voltage to zero, they both stop.
With DCC, the voltage across the two rails is always 14V (again, assuming HO). Every locomotive on the track is always receiving 14V. The versatility of DCC comes from the fact that every locomotive on the track has a decoder chip - essentially, a tiny computer - inside it that controls the locomotive's speed and other functions such as lights and horn. How fast a locomotive runs is determined by sending a signal from your controller or cab along the rails to that locomotive - and only that locomotive - that is interpreted by the decoder, which in turn determines how much voltage out of the 14V available to it to pass to the motor. In this way, each locomotive can receive a different amount of the available 14V, and therefore each can run at its own speed. Similarly, a different signal instructs the decoder to switch on or off the lights, or sound the horn, and so on.
So what does that signal look like, and how does it go only to the right locomotive?
Since the signal is sent over the rails, it will be seen physically by every locomotive on the rails. (This is much the same as a computer network, such as WiFi.) The signal that is sent out by the controller consists of a sequence of information called a packet. A packet comprises an address and a command. Each decoder chip has it's own address, which is simply a unique identifying number. That number is stored in the Configuration Variables, or CVs, of the decoder, as described elsewhere in the wiki. The address is typically set to 3 at the factory, and normally you'll change it right away to something unique on your layout, such as the road number of the locomotive. Each decoder only responds to the commands that are addressed to it. (If you are familiar with computer networking, you will recognize that this is again very similar: each computer has a unique IP address, and only responds to packets intended for that address.) The command might be an instruction such as "set speed" (and direction, forward or reverse) plus a byte of data to specify the speed, for example "64" if you are using 128 speed steps and want 50% speed. It could also be a command to sound a horn or whistle, or to turn on or off lights, or anything else that particular locomotive is capable of. These commands correspond to the functions available on your decoder chip.
Simply put, this is how DCC can control several locomotives independently on the same track: each decoder only obeys commands that start with its particular address, and ignores commands addressed to other locomotives.
If you only want to know how DCC can control several locomotives on one track, you can stop reading here. But if you want to know more details about what those signals look like electrically, continue reading.
Now comes the part that causes the most confusion about how DCC actually works. Like other computer networks, the DCC signal consists of a binary code, a series of 0s and 1s. On learning this, many people assume that means that the voltage turns off to indicate a 0 and on to indicate a 1.
This is completely incorrect and it's where many online attempts to explain DCC go wrong. The key concept to grasp is that there are lots of ways to indicate 0s and 1s electronically, and On or Off is only one of them.
Probably the simplest scheme to send signals electronically is to have a high voltage for 1 and a low voltage for 0. For example, if you are familiar with Arduino microcontrollers, a voltage of 5V means HIGH, or 1, and a voltage of 0V means LOW, or 0. [Strictly speaking, because electronic circuits are never perfect, the Arduino treats anything above 3.0V as a HIGH and anything below 1.5V as LOW.]
But this is far from the only way to encode 0s and 1s. For example, the memory inside your computer, smartphone, smartwatch, Oura ring, or anything else you own that has a processor inside it, probably uses a type of memory called CMOS. Inside that memory, each bit is represented by a pair of transistors. To store a 1, one of the transistors is On and the other Off. To store a 0, the states of the two transistors are reversed.
This is the key fact about digital signals: a 0 bit in a signal does not necessarily correspond to 0V in a circuit. And with DCC, it definitely doesn't.
As we said earlier, using On and Off for 1 and 0 is a very simple scheme. However, this won't work for controlling our locomotives, for two important reasons. First, recall that the decoder powers the motor by taking 14V from the track, and then providing some fraction of that voltage to the motor according to the speed setting that was sent to it. If the voltage between the rails were set to zero to indicate a 0 bit, then no voltage would be available to the decoder, and the motor would lose power for an instant. If a signal is sent that requires a sequence of zeroes, the motor would lose power throughout that signal. Overall, the power available to the locomotives would drop depending on the number of 0s being transmitted. And obviously that's not good. We want the power to the locomotives to be constant, and therefore we need the voltage to be constant, not On/Off.
Second, an On/Off signal is fine for reading something simple such as a single bit, like the setting of a switch, but it's much harder to use to send a rapid sequence of bits. Suppose the controller sends a signal that is a sequence of 1s, for example to set the speed of a locomotive to 256. It's very hard for a decoder to figure out where one 1 stops and the next one starts, because it would just see a constant 14V (HIGH) signal. In order to know how many 1s were received, it would require very precise timers that are synchronized between the controller and all the locomotives, and that's not practical in this case.
So the designers of DCC used a clever trick for signalling 1s and 0s that solves both problems: it provides constant voltage to the track; and it makes it easy for decoders to detect where one bit ends and the next begins. Instead of signalling 1s and 0s by the level - high or low - of the voltage, DCC signals 1s and 0s by changing the level of the voltage. A change in voltage is much easier for a decoder to detect, and doesn't require synchronized clocks. The clever part is the voltage is always 14V - only the direction of the voltage changes. And the timing of the changes encodes the 1s and 0s.
Let's look at this in specific detail. Imagine you are the engineer in a model locomotive, looking at the track ahead of you. Suppose that the rail on your left is 14V, and the one on your right is 0V. Then, your decoder sees the voltage switch, so that the left rail becomes 0V and the right one 14V. The decoder recognizes this change in voltage direction as the beginning of a bit. A moment later, the voltage switches back again, and the decoder recognizes the end of that bit. That back-and-forth switch is called a pulse. Throughout this process, the voltage is always 14V; as noted above, only the direction changes. (If you like a physical picture, imagine two children playing on a teeter-totter or seesaw: when one end goes up, the other goes down, but the difference in height between the two children is the same either way.)
This is the key concept in understanding how DCC works: DCC indicates 1s and 0s by the length of each pulse.
Specifically, if the pulse is 116 microseconds long, it represents a 0. If it is 58 microseconds long, it represents a 1. And to reiterate, the voltage between the rails is always 14V, never 0V; only the direction changes.
The picture below is widely reproduced, and shows this idea graphically. Unfortunately it can be a bit confusing to interpret. The way to understand it is that when the blue-ish line is above the center black line, the left rail is 14V higher than the right rail, so current flows from left rail to right right. When the blue-ish line is below the center black line, the left rail is 14V lower than the right rail, so current flows from right to left.
[Some people like to think of this as the right rail always being 0V, while the left rail switches between 14V and -14V. In reality, this is exactly the same thing because "voltage" is not an absolute measure, like height above sea level; rather, voltage measures the relative difference between two points in a circuit, like the top and bottom of a waterfall. And the difference from -14 to 0 is the same as the difference from 0 to 14. In both descriptions, the right rail is 14V higher than the left rail, and that's what matters. So you can think of it whichever way works best for you, as long as you remember that there is always a difference of 14V in one direction or the other. If you prefer this viewpoint, the picture is much easier to read: the black line represents the right rail, always at 0V, and the blue-ish line represents the left rail, switching back and forth between 14V and -14V relative to the right rail.]
If you look closely at the picture, you will also notice that earlier I simplified the explanation of a pulse. In reality, a 0 is indicated by setting the voltage in one direction across the rails for a long time (116ms), then in the other direction for the same amount of time, before returning to the original direction, ready to send the next bit. Similarly, each 1 is indicated by a pair of short peaks (58us), one in each direction. (The technical reasons for this redundancy are too detailed to get into here.)
Now you might be wondering, if the voltage is continually switching back and forth, why don't the locomotives just stutter back and forth, instead of running smoothly in one direction? The solution is a component in the decoder called a rectifier, which takes current in either direction as input, and outputs it in a single constant direction. (The same component is what enables a USB adapter to take 110V AC or 220V AC and output 5V DC.)
There are a lot more technical details to DCC signalling if you are interested, for example the precise formats of address and data bytes; and what happens when no commands are being sent. That information can readily be found online, but it isn't necessary to understanding how DCC works.
And there we have it. In summary: DCC delivers a continuous voltage across the rails so that full power is always available to the locomotives. It sends signals by flipping the direction of the voltage. The 1s and 0s are encoded by the timing of the back-and-forth switching, or in other words, the length of the pulses. And those 1s and 0s are interpreted by the decoder chip into addresses and commands.
I just reread Kate Wagner's piece for The Nation, "Liberating Our Homes From the Real Estate–Industrial Complex" that dissects the rise of greige as a decorating theme, and feel like there's another pernicious incentive at work that wasn't mentioned (or if it was mentioned, I missed it and you can ignore the rest of this!). You should read that first for context.
Back? OK.
At the intersection of platformization and houses-as-assets capitalism is the idea that greigifying everything, as well as eliminating taste, also reduces every house to objects that Zillow and Redfin can most easily monetize, by which I mean attributes that can be counted: square footage, number of bedrooms, number of bathrooms, acreage, age, these are all things that the platforms can readily filter and sort on. Those messy, human characteristics like style and sense of space and environment are things Zillow and Redfin don't know how to sort [except in the crudest of ways], so the platforms would like to eliminate them from the equation. Platformization and greigification go hand in glove.
At its crudest, this reduction to lowest common denominators renders houses scattered across a school district as identikit as the apartments in a new block of rentals so that, for the benefit of capitalism, they can be marketed the same way. The goal is to take individually built houses and render them as the output of mass production after the fact.
Now ask yourself who benefits from this. The answer is "people who want to buy houses in large numbers as assets without actually looking at them". In other words, people who want houses to be not merely assets, but *commodities*.
And of course, these are not "people" at all, but investment firms.
Ultimately this is a painful echo of 2008. The original goal of CBOs was to financially commodify mortgages regardless of the underlying properties. Greigification seeks to physically commodify the properties themselves.
p.s. If you're interested in this kind of thing, you should be following Kate's blog, McMansion Hell and her column in The Nation.
Random thought: are we heading for an economy where the 1% and the 99% become completely economically disconnected? They will control AIs* to do mental work and robots to do physical work and massive amounts of wealth, and so they will have nothing we can afford and we will have nothing they want.
January 21: A coalition of eighteen states led by Texas announce their succession from the United States, forming a new country reviving the name The Confederate States of America, or CSA. The Internet is thrown into a frenzy over whether to call them The Confederacy of Dunces or Trumpistan.
January 22: The CSA issues a correction to say that they meant "secession" all along, but a software bug planted in Google Docs in collaboration with Hugo Chavez auto-carroted it.
Later that day a massive convoy of gun-carrying CSA supporters in pickup trucks adorned with Trump 2020 flags arrives at Fort Sumter. Upon arrival they discover that the fort, which has not been an active military installation since 1947, is only accessible by boat. They mill around in confusion for an hour, fire a few shots in the air for the look of the thing, and return home.
January 23: Mexico announces plans for a wall along its border with Texas. So does New Mexico.
January 24: The United States recognizes the CSA and announces the closure of all Federal facilities in the CSA, including research labs, airports and military bases, decimating the economies of many towns. The Federal government also announces that drivers' licenses or other ID from secessionist states will no longer be accepted for any purposes. Many citizens of the CSA are stranded in Federal states, unable to board a plane, rent a car, or buy alcohol or tobacco. The latter causes widespread panic among the CSA refugees.
January 25: Various Federal states announce that cars with plates from the CSA states are no longer legal on their roads and must be registered in a Federal state. Drivers from West Virginia get pulled over in massive numbers in Virginia, Pennsylvania, and Ohio. Unable to pay the fines, their cars are seized and crushed into scrap metal, in most cases significantly increasing their value.
January 31: The Federal government announces that as of February 1, it will no longer pay Medicare claims from the CSA. There is widespread panic among the citizens as they realize that their new government is completely incapable of providing them with diabetes supplies or Hoverounds.
February 1: The CSA states meet in constitutional convention at the Austin Convention Center. They meet in the Starbucks as the Center itself is fully booked between an arms and ammo show and a pharmaceutical sales rep convention. Donald Trump is elected Interim President For Life.
February 10: The other six members of the Colorado River Compact announce the expulsion of Utah and plans to build a canal to divert the river around that state. Desperate, the male citizens of Salt Lake City take to the streets in a massive protest. Since this is Utah, it is the most well-behaved, conservatively dressed street protest in the history of the Americas. The women of Salt Lake City fortify the protesters with huge quantities of green Jello.
February 11: Green Jello shortages across Utah drive panicky protesters back into the streets. There is polite rioting and orderly looting of grocery stores. In desperation, many turn to yellow and red Jello.
February 28: CSA citizens begin to notice that no Federal Social Security payments have been received all month. Unable to pay their rent or afford food, white citizens forage for essential supplies, often liberating them from stores without paying, while black people loot.
March 31: After a month of chaos and disorder, Texas asks to rescind its secession. The Federal government accepts it back under strict conditions regarding the fair conduct of elections.
April (various): One by the one the other CSA states also ask to rejoin the Union. They are all readmitted, except for the Dakotas, which nobody wanted in the first place.
April 30: The CSA is formally disbanded. Donald Trump remains Interim President for Life.
