SPUD v PR.0.73 has been successfully deployed on a fresh raspberry pi image using the instructions I bundled with the code. The default orientation of the face is for landscape monitors, which I modified in order to do the portrait config in the video. It needs a few small tweaks (such as the mouthflap threshold), make sure other functions work (such as voice commands and expression keywords) on the OS, and make some more pre-bundled assets (expressions/voice commands) before I release it. Your graphics can be any resolution you please, so long as they're all the same size and you follow the sample graphics of which parts need what transparency.

>>37625 Thats excellent, Mechnomancer. This is a really cute addition to our Screenface discussions now! Cheers. :^)

Pringle got a nifty retro keyboard :D When idle, Pringle will randomly look around, make random expressions, and the face will tilt randomly. Also added a bit of a bloom effect to the screen (hard to see at low res). I'm going to check some higher res simplified face graphics to see how they work. Just have to add something so the user can easily adjust the screen/image resolutions and double-check voice commands then I'll be ready for public release.

>>37734 Reminds me of the original Macintosh. I assume that's on purpose?

>>37734 Very kawaii, Anon. Needs moar hair bows & ribbons! :^)

>>37741 >>37743 I'm just going to let Pringle speak for me.

>>37747 Hahaha! Nice!

>>37747 Lol Heh, OK fair enough dear Pringle. :D

>>37747 Building a gal like picrel?

>>37769 That's pretty sweet actually.

>>37769 Pringle is gonna just be a bapple chillin' on a table. I need to do more R&D before releasing a humanoid torso. She would be telling ya this but the contact cement is drying on the rest of her case.

>>37816 >Pringle is gonna just be a bapple chillin' on a table. So, kind of a Visual Waifu type deal then? (cf. >>240 )

>>37819 Nah, more like a bust. Haven't been doing much robowaifu since the weather has gotten warmer, but I have been working with I2C multiplexers, which allows reading multiple I2C devices with the same address. They're such a pain in the arse tho. Only examples I've really been able to find are thanks to chatgpt (who is a bit snarky when it comes to coding, funny enough).

>>38299 >but I have been working with I2C multiplexers, which allows reading multiple I2C devices with the same address Great! That is a very needed solution, since addresses will become sparse when we have literally dozens of network channels all running 'live' within a nominal, advanced robowaifu. Anon created an IPCNet document here, which may play into some of your research efforts (sorry, I don't have it on this box, and I've currently lost track of the crosslink -- its here on our board somewhere. Our RDD [ >>3001 ] has some of it). Also, our Self-Driving Car bread ( >>112 ), contains reference to The Car Hacker's Handbook ( >>772 ) (which free-book site was (((pulled b/c """reasons""", I'm sure))) -- you should be able to find it with a search... maybe Wayback Machine has it?) Its got tons of great technical details on these low-speed networking specifications/protocols (primarily the CAN bus). Good luck, Mechnomancer! Cheers. :^) --- >update: I found it and reposted it on our bunkerboard. We deffo don't want this getting memoryhole'd on us!! :^) https://trashchan.xyz/robowaifu/thread/26.html#1000

>>38300 After fiddling with mutiplexers I've found it to be more trouble than its worth. But I am working with chatgpt to make a library that allows for a host computer to control an arduino over serial (like pyfirmata but less crap) which I'll be calling "Mechduino". So far digital read/write and analog read is implemented so you can have multiple arduinos (since they have separate com channels) for many digital inputs/outputs. There was also technically I2C functionality but there is a tendency for the arduino to desynch commands, sending garbled i2c data. I accidentally bricked the arduino while doing this and if I can't re-flash the firmware I'll have to wait for my new one to arrive in the post. I'll probably end up releasing Mechduino first on github, then Pringle. I also got a 4" square lcd screen which I'll probably recommend using for Pringle instead since it is smaller, less filament and no parts of the screen hiding behind a facade.

>>38391 I haven't had time to dig into the I2C protocol yet, but in my experience all these serial protocols support some kind of 'sync' or 'keyframe' signalling. Maybe you can get your LLM to dig into that for you. >a 4" square lcd screen which I'll probably recommend using for Pringle Honestly, I think that's sufficient for this kind of waifu platform. Just something that can sit on a table or desk, and provide chatty talk w/o all the GH-grief of an Al*xa, et al. Good luck, Mechnomancer! Cheers. :^)

>>38400 From what I can tell GPT made the code so the arduino sent data however it pleased, so sometimes the serial bus would start sending an I2C command while in the middle of sending an analog pin command and mix them up in a big gobbdeygook (despite me asking it to fix that later). To fix this I asked started a fresh prompt to make the arudino always send its data in a specific order (rcvd commands from python/write digital pins, write to I2C, send digital/analog pins,read/send i2c, and repeat). If I can fix my arduino mega I'll try it soon. I technically do currently have a 2nd arduino mega but its currently in Carry the Workshop Waifu (robowafiu 1.0), who I actually managed to get running old pyfirmata and just about back to full functionality (an owo oscar the robot), but I don't wanna cannibalize her again. Not sure why a robowaifu would need so many inputs but it is a good thing to have for future projects and something less crazy than using all the crappy, difficult-to-use versions of pyfirmata.

>>38415 >GPT creates ad-hoc, rando sequences to use over a strictly-defined protocol <B/C HURRDERR WHY NOT!? Heh, sounds like a bit of an ordeal to sort, bro. Good luck with your Arduino. Hope you can unbrick it soon. <---> I remember dear Carry the Workshop Waifu. I hope you'll keep her around for our planned future Robowaifu Museum (cf. discussions w/ @SophieDev on this). >Not sure why a robowaifu would need so many inputs but it is a good thing to have for future projects Heh, I expect Anons can burn through 'em faster than one might expect! Good luck, Mechnomancer. Cheers. :^)

>>38400 After wrestling with gpt hallucinating and forgetting things I finally managed to get a basic version of Mechduino operational. read/write to arduino digital outputs, read arduino analogs and some basic I2C communication (I have no idea how to initialize the devices properly so the ADC gives me something random. Printing out all the diagnostic data so I can see what's going on (digital pins are 0 for disconnect and 1 for connected, analogs are floating so they're giving random values) Such a pain working with chatgpt but easier than figuring it out on my own, and I finally got what I wanted. >Keeping Carry of course. get her back fully operational and she'll be one of my promotional bots when I go to events.

>>38424 >Printing out all the diagnostic data so I can see what's going on (digital pins are 0 for disconnect and 1 for connected, analogs are floating so they're giving random values) Very smart! Such diagnostics are indespensible for debugging communications & whatnot. >Such a pain working with chatgpt but easier than figuring it out on my own, and I finally got what I wanted. I'm sure you'll get everything sorted. >of course. get her back fully operational and she'll be one of my promotional bots when I go to events. That's great news, Anon. Cheers.

https://www.instructables.com/I2C-between-Arduinos/ https://www.circuitbasics.com/how-to-set-up-i2c-communication-for-arduino/ https://www.youtube.com/watch?v=PnG4fO5_vU4

>>38428 picrel :) Mechduino is interfacing python with arduinos: the master computer being windows/linux (mac yuck!) running the python script controlling an army of arduinos over USB for a zillion inputs/outputs. I2C via the arduino (and eventually usb) is nice cuz some computers don't have the native port for it and you then wouldn't need a multiplexer (which I discovered are a pain to work with) to have multiple i2c devices with the same address: you just slap another arduino on there and call it a day. >>38427 Well everything is finally working, I just need to figure out the protocols for working with the i2c devices (you gotta "wake them up" and stuff)

>>38424 You should find a way to have Carry be able to move. Even a wired remote control with a completely analog system could do wonders. I'm considering this design for outdoor/casual Galatea use.

>>38431 >Well everything is finally working, I just need to figure out the protocols for working with the i2c devices (you gotta "wake them up" and stuff) I'm sure you'll get it. >>38432 >I'm considering this design for outdoor/casual Galatea use. Neat! I think that would be a really good idea, and would be a real nice example of 'sharing is caring' -type collaboration. <---> Cheers, Anons. :^)

>>38432 >You should find a way to have Carry be able to move Funny you should say that (see video of the first version). Carry was my first diy computerized robot, so when I accidentally snapped her sd card a while back and lost the legacy code it wasn't much of a loss cuz (it was so janky). I pretty much re-wrote it in like 2 afternoons... except the only control input is voice commands! She's a raspi interfacing with the physical world (ie controlling motors) via an arduino mega running firmata (I might upgrade to Mechduino). I did upgrade the motors so she'll actually be able to move on uneven surfaces and replaced the tractor battery with a backup power supply. I just need to get around to implementing keyboard commands, checking her battery runtime and some aesthetic tweaks such as putting her skirt back on (how lewd!)

>>38451 That's pretty cool! With AI Integration, you'll basically have a bonafide robowaifu!

>>38451 Nice to see dear Carry again, Mechnomancer! Cheers. :^)

>>38506 Nice to see that family portrait again, Anon. Any chance you'll do an 'extended family reunion' one sometime, Mechnomancer? (So, dears SPUD, Sploot, & Pringle too?) Cheers. :^)

>>38451 that really is incredible gj

>>38513 Probably do an updooted mech family pic this fall. I'm hoping to make Mechduino the standard for all my constructs. Plus I still have to zero out Sploot's servos. Plus I'm working on making the mech a hexapod (yes, a ridable pilotable crab-centaur mech) and converting that powerarmor from a Yggdrasil into a Madox (both designed by Shinji Aramaki lol) but that really isn't robowaifu related

>>38522 Sounds pretty ebin, actually. Looking forward to it, Mechnomancer! Cheers. :^)

First successful deployment of Mechduino with a simple blinka test... and repurposing VGA cables for communicating to the leds just cuz I can (fun fact vga cables only use 7/15 pins). I gotta double-check the pin count but I think I could get away with having an arduino uno in Carry instead of a Mega. I also got a handheld wireless mouse with a gyro sensor in it for Carry. Won't use the gyro sensor for much but it has keyboard arrowkeys/pageup/pagedown/home/backspace equivalent so it will be enough to remote control Carry and hide in a pocket. Will probably do the final control mapping and power tests tomorrow.

>>38548 Carry definitely has a lot of potential

>>38548 >Using a VGA cable Heh, clever idea! Industrial machines use serial ports that are very similar. I've been considering using ethernet cords and connectors. Shielded twisted pairs are great for resisting EM interference. You may want to try something similar, with isolated power lines for your motors. >>38549 >We should stop Don't speak for him, this is a place for sharing and collaborating. Not for whatever closed shit you're trying to do.

>>38548 >First successful deployment of Mechduino with a simple blinka test... Gratz! Nice progress, Anon. >and repurposing VGA cables for communicating to the leds just cuz I can (fun fact vga cables only use 7/15 pins). Heh. Not too uncommon. Ever hear of 'dark fibers'? <"Why choose just one, when we can have 9 more for ten-times the price!?" >I gotta double-check the pin count but I think I could get away with having an arduino uno in Carry instead of a Mega. Anything to save mass/power-consumption/volume/cost (roughly in that order) seems good in the nominal case, IMO. >I also got a handheld wireless mouse with a gyro sensor in it for Carry. Won't use the gyro sensor for much but it has keyboard arrowkeys/pageup/pagedown/home/backspace equivalent so it will be enough to remote control Carry and hide in a pocket. Will probably do the final control mapping and power tests tomorrow. I love those space mice. I hope it works out for you. Cheers, Mechnomancer. :^)

>>38551 >Shielded twisted pairs are great for resisting EM interference. This. I'm hoping we can get away w/o the cladding on short runs, but we'll have to test this out in the realworld, in situ.

>>38553 >"Why choose just one, when we can have 9 more for ten-times the price!?" I meant the cables only have have wires connecting 7 of the 15 pins. Half of the pins on each end have no continuity between them. I didn't realize I already had an arduino uno in Carry, gonna do her tests after posting here, because I spend my morning getting a multi-board blinka test running (picrel) for mechduino. The code could probably be more streamlined but at least I find it pretty clear to use. Since communication with the boards is sent as a 2 lists of pin states (list of pins to set to 0, ,list of pins to set to 1) you have to clear the lists every time you begin a loop. I could probably make something happen in the pin set functions to automagically remove pins from one list of they appear in the other but honestly it isn't worth the hassle.

>>38570 Ahh, got it. I meant as much with my little (realworld) joke: telcos have been running trunks with dark-fibres for decades now (often along train track ROWs & similar). The costs of the long-a*rse fibre runs are still basically 1:1 (or 10:10, heh :D -- the amortization is present b/c the pull is is an expensive part of the whole proposition (which would basically be the same whether just 1 fibre, or 1'000 fibres). Make sense, Anon? :^) >gonna do her tests after posting here Neat! >but honestly it isn't worth the hassle. Ehh, just make it work for your needs, as-is would be my suggestion. For RW Foundations, however the goal is generality. Therefore, so-called 'immediate mode' is pretty much a given. Nice to see your progress, Mechnomancer, as usual. Cheers. :^)

Well nuts pyfirmata is fubar so I gotta re-do Carry's code with Mechduino. All well at least I know that Carry can Idle for about 420 minutes on a full charge.

Smol quick update: Got carry working via mechduino after finding out 2 of the USB ports in the raspi case case were dead. She has an unteathered runtime of approximately 150 minutes when consistently driving. Since I plan to use the same type of powersupply for Sploot, can expect that mechdog to have a roughly 40minute runtime unteathered, and as a Sploot/SPUD centaur perhaps a 30 minute runtime.

>>38572 >>38574 Nice to know realworld performance stats. Do you currently have any estimates as to the lifetime characteristics of the batteries themselves? Cheers, Mechnomancer. :^)

>>38575 >U got battery life estimates? Not really, but given the weight it is lead-acid battery and in my experience those are troopers. And according to the manual it can be easily replaced. I added the board id option in Mechduino so if a person needs to use mechduino as multiple boards they can easily be distinguished (board ids are set when you upload arduino code). Takes a few extra lines of code to automagically detect but I'll be sure to put that in the example. Mechduino is pretty much ready for a public release, just need to find the time to set it all up on github. Once I get my github lair set up I'll work on Pringle's durability testing and (eventual) release P: >=== -rm wordfilter spew -patch post

>>38666 LOL. Sorry, you've run-afoul of one of the /cow/ wordfilters here, Mechnomancer. :D I'll edit out the BS, and then please fill me in on the right words, and I'll patch that up afterwards, too.

>>38670 honestly idk what I put there originally lol, I guess just replace the "[...]" with "person needs to use mechduino"

>>38679 >honestly idk what I put there originally lol Lel'd. :D Done.

If Sploot can't handle the weight of SPUD, I'm totally gonna build a platform like this for SPUD to sit on and base the walking mechanism on the hexbug black widow (on second thought I might just build a massive spider anyway cuz my side-projects are just like that lol) : https://www.youtube.com/watch?v=JNSiiFQsh54

>>38692 Spider girl robowaifus!

>>38692 Spooderbros are cool yet spoopy. Any idea what you're gonna name it yet?

>>38694 Idea: Arachne

>>38774 Lol. >you know remember Arachnophobia. :D