>>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

While doing some R&D for SPUD's new body paneling I stumbled across a technique to create a humanoid form rather cheaply without the use of a 3d printer... probably about $30 and 2-3 hours assembly time (depending on your skill). I'll post more details once I get the SPUD version complete. It would be a good thing to release with Pringle: not requiring a 3d printer would make Pringle more accessible to a wider scope of Anons, making Pringle a true model T robowaifu :D

>>38947 That sounds awesome, Mechnomancer! Maybe you can do an in-depth detail on this in our Materials & Production bread : ( >>37774 )? Cheers. :^)

>>38947 Is it foam sheets?

While taking a break from perfecting my super duper ultra secret (at least until I post it lol) over 9000 awesome robowaifu body budget -no >>38951 greer not foam sheets unless you really really want to use em- I followed this guide: https://buyzero.de/blogs/news/deepseek-on-raspberry-pi-5-16gb-a-step-by-step-guide-to-local-llm-inference and got a somewhat decent LLM running on a raspberry pi 5 16gb. Depending on the model your results may vary: you will have to explore the ollama models and experiment to see which one is right for you. The attached is a sample response with some statistics and the "thinking" (aka the LLM having an internal monologue) with the deepseek model (default model in the article). I found a model kinda good at doing SPUD's persona without the Deepseek model's gigabrain energy but I forgot which one and am too ̶l̶a̶z̶y̶ busy to check right now. I'll try to swap out SPUD's main computer with the Pi 5 when I replace her eyelid rack (no blinking at the moment oh no!)

>>39206 Good timing lol Now I'm curious to see this new construction method.

>>39206 POTD Nice work, Anon. Really looking forward to your latest advances with dear SPUD. Cheers. :^)

>>39229 Thanks for the update, fren Mechnomancer. Godspeed.

@Mechomancer, you should make an Odysee page and/or Neocities website for your final releases. If it can fit, also use catbox for archival.

>>39234 oh dear looks like my less detailed post about the raspi LLM got restored, kinda puts a little redundancy in the thread. All well. I asked chatgpt how to use the python Ollama library to stream the LLM responses sentence by sentence with the goal to reduce the appearance of latency. To explain further, there will be a pause when the initial request is sent to the LLM and the TTS generates, then while the first sentence is being spoken -aka audio is playing- the raspi will be working on generating the text & audio for the second sentence (if that makes sense). This will (hopefully) eliminate freakishly long pauses if the LLM decides to give the user a paragraph and add the potential to cut off a response between sentences. Still have to actually implement the code but it seems to at least be possible. >>39310 I'll probably have 2 versions for Pringle: basic modular assistant and LLM then just plop the code it on github , because the SPUD line is for hospitality/greeting and not ACKSHUALLY a robowaifu... but I can't control what you decide to do with the code n stuff. ;) Tbh the entire release package probably wouldn't be all that big, maybe if there are some hires .stls but it would probably be all under 100mb.

>>39315 >oh dear looks like my less detailed post about the raspi LLM got restored, kinda puts a little redundancy in the thread. All well. I'll delete that if you want, Mechnomancer? >but it seems to at least be possible. That will be really good news if it's feasible to queue-up a 'train pattern' for responses like that. >Tbh the entire release package probably wouldn't be all that big, maybe if there are some hires .stls but it would probably be all under 100mb. Surprisingly smol to my thinking. GG. Cheers. :^)

>>39318 >I'll delete that if you want, Mechnomancer? Sure yeetus the f̶e̶e̶t̶u̶s̶ postus >Surprisingly smol to my thinking. I mean those are the files I'd have to host. Still would have to install python dependencies (20mb max I think) and the Ollama model (around 4 gigs) but you get those with pip and ollama and I'd provide instructions like article I linked :D

>>39320 Neat! >Ollama Can your arrangement work with llamacpp instead? It's lighter than ollama by all accounts. Plus it's dev community is pretty fiercely working on it atm. I expect it to improve further.

>>39335 >llamacpp Idk, install instructions look less straightforward. I'd have to try it out. This article looks handy tho: https://learn.arm.com/learning-paths/embedded-and-microcontrollers/llama-python-cpu/llama-python-chatbot/ Especially since it has instructions right on it for using llamacpp with python. I think a good idea that before SPUD properly shuts down, I feed the entire conversation (up to 16k tokens, of course) to the Deepseek thinky model to summarize the conversation and modify the base prompt accordingly, that way the character AI will change or "grow" as one talks with it. This would be similar to the function of human sleep. However I'm a while away from doing that as not only am I just barely getting my feet wet into maxxing the Raspberry Pi (found out how to overclock hooray!), but I've been busy with personal matters, as well as touching (and mowing) grass.

>>39387 Nice! I thought of something similar, and your AI summarization will solve the problem I realized of the prompt getting too large over time.

>>39387 >before SPUD properly shuts down, I feed the entire conversation (up to 16k tokens, of course) to the Deepseek thinky model to summarize the conversation and modify the base prompt accordingly That seems like a really good idea if feasible, Mechnomancer. Please keep us up to date on your progress. Thanks for the link resource BTW! Cheers. :^)

Robowaifu v 1.0 "Carry the Workshop Waifu" retrofit is 95% completed. Wiring completely re-done to utilize my Mechduino library. Had to replace a few of the motor drivers, too. Now just need to tweak the back of her skirt (not shown) and fix some issues with her main drive slipping occasionally. She doesn't have voice commands but that is something easily implemented in future. Maybe I'll try to deploy Pringle script on her? idk. She has a lot of empty space inside and -as I mentioned before- a battery pack (UPS) that can give about 7 hours idling time or 2 hours constant driving time. So I can probably have her test things like autonomous navigation and stuff. Gonna move on to some other non-waifu projects (unless you consider the 600lb mek a waifu lmao) before getting SPUD back operational.

>>39656 Nice!