re1 to magdeburg status: just did not arrive. not delayed, not cancelled, announcements said it would be there two minutes before arrival - then nothing. just did not appear at the station.
for a place literally full of mirrors, the mirror section of local ikea was surprisingly comfortable.
for a place full of people on a saturday afternoon, the entire ikea was surprisingly comfortable, too.
today was quite literally the first time I completely dropped any pretense of boymoding in public, immediately went for a busy, crowded and inherently overwhelming place with a rather long public transport commute–
and it was fine.
I don’t think it would be possible for me alone to do that so easily, but eileen co-fronted for most of the day and pretty much took over, first deciding to go to the flea market, then doing a completely unplanned “let’s go to ikea and buy some plants” on the way back.
so I went back to fixing an old shelving unit that needs some shelves moved up or down to fit different items, and some mangled/bent sheet metal parts replaced.
employees even at big grocery chains visibly confused by cash and struggling to count coins.
germany:
“was?”
“cash only” signs everywhere.
“sorry, card payments from 10eur only”.
“easy online payments, just provide your online banking login and password to sofort, it’s completely safe and totally does not blatantly violate the terms of agreement you signed with your bank”.
not saying there’s no bigots on fedi, but they’re relatively easy to defederate, whole instances at a time, and they’re not even trying to go for a narrative that frames them as “the” network. or maybe they do, I wouldn’t know, it doesn’t federate over here.
not saying that bsky is all bigots either, but they’re effectively centralized and with that comes some, y’know, responsibility for proper moderation. as long as it’s not an actual network with effective large-scale moderation tools available for the users themselves, it’s on them. and they’re fucking it up.
no, this is not “them just wanting to enjoy their platform the way they like”, for whatever definition of “them”, as long as it includes bigots.
no, “just spend your time and energy blocking bigots one by one” is not the answer, it’s the same sort of shit as twitter after musk.
there’s a few more proposed “solutions” like this, or very perplexed “why don’t you just” questions in this thread already that are likewise not well thought-out to say it lightly, but this will have to suffice as an answer to them:
sometimes there’s a little bit more nuance and reason behind things like this “hate”. such as fundamental differences between the motives of “hate” either side has. try looking for it instead of trivializing and equating them.
I’m truly puzzled to see that coming from someone who just had the entire substack experience.
windows loads the vxworks “driver” which is actually a vxworks bootloader.
vxworks kernel starts booting, preempts win95 kernel and takes over.
vxworks kernel installs its own interrupt service routines.
vxworks finishes booting, then turns windows into its subprocess.
win95 is allowed to finish booting, unaware that it’s no longer really controlling the machine.
from that point on, win95 is handling gui and some pheripherals (disk, network, etc.) and runs the non-realtime parts of control software.
vxworks, meanwhile, runs some of the realtime part of the entire thing, on the same 400mhz celeron. those include motion planning and axis position feedback loops.
the final part of the puzzle is the texas instruments tms320c32 digital signal processor that runs the hard realtime tasks including servo phase waveform generation.
this is not entirely unlike other industrial realtime control systems, but it is admittedly a bit wacky and unique. to the best of my knowledge, this vxworks port was not used by anyone beyond kuka.
the hardware part o this story seems to be mostly done. it powers up and works. I have yet to test the actual servo drive, robot is not even connected at this point, but I'd say we're most of the way there.
00:03 - powerup. 00:07 - low voltage supply status led check. 00:14 - computer starts post sequence. 00:26 - windows 95 starts booting. 00:34 - wait what? yes, wxwrt.vxd. wxworks. 00:40 - at about this point the external monitor starts getting output, as the kvga driver is loaded and enables the vga port, which is normally disabled. 00:50 - windows boots, autostart kicks off kuka software. 01:16 - the control software proper starts up and begins hardware initialization. 01:39 - "download" begins - the digital signal processors on the mfc card are "downloading" firmware. 02:00 - dsps boot, last stage of startup begins. 02:20 - startup complete.
now, this is actually not the correct software for the krc1 control encosure. it's the volkswagen software that was configured for the vkrc1 hardware (see the linked thread). this is why it immediately throws a ton of errors.
ok, let’s give this robot one more try at getting it to work well and be useful.
tl;dr it was originally deployed at a volkswagen factory and came with a customized, volkswagen-specific control cabinet (on the right, the one with “broken robot” poster) which is absolute hell to get to work right standalone, without an external plc controlling it over interbus. hardware is different enough that it can’t be easily converted, software that works with this hardware is heavily stripped down and lacks critical features.
so I finally managed to track down a stock version of the control cabinet. it’s incomplete, but I can do some part swaps to get it to work and it was cheap.
Transfem enby weirdo, neurodivergent, plural system, 34.Co-founder of Warsaw Hackerspace. Hardware/software hacker. Heavy industrial machinery enthusiast.Some posts might be by @erin because "why bother switching accounts when we share the memory stream" or something.:verifiedpansexual: :verifiedenby: :verifiedtrans: :verifiedpolyam_pi: