/random/ - random

peak shit fr

I have taken great interest in your endeavours

I just saw someone upload real cp not too long ago.....on 8kun.....who is posting it? Could it be the FBI?

>>155424

nah shit sherlock, 90% of all pedos are in the FBI, i may be an athiest, but yall need jesus

The hard part for this is just going to be the programming

You could buy a humanoid bot and start there instead

I like this project though keep it up

>>157053

Those MAD DIY skillz. 🫪

>>157053

Uh… go on….

>>157088

Those circuits remind me of the hand-cut copper stuff from proto-comps… noice

robots download porn.....only a robot would be idiotic enough to download porn.....robots are the most idiotic thing ever......

>>157461

well if you make your own AI you can put in a rule to not download porn. That's why custom rules based AI is amazing. You can make any rules you want.

Does this mean I gave up? No. I basically just decided that trying my best, being very thorough and meticulous and careful I still somehow ended up with very hard to troubleshoot total failures this early in testing then really working with this QFN part is NOT that DIY friendly on a DIY PCB and starts reaching the limitations of what is practical. Even if doable it is hard enough to make it very hit and miss and time consuming and not worth that extra effort unless its necessary or there is not a far easier path that gives the same results faster/easier. And I now have a way faster and easier option that gives same results with NO tradeoff that is meaningful or moves the needle at all.

So I ordered 25 of these chips off aliexpress for now and 4 of them off amazon to work with while aliexpress is shipping slowly here. I'll have the 4 off amazon tomorrow while I wait for the larger order. I do this trick often paying more money for faster shipping on amazon while I wait for my slower shipping order at better price point in bulk to come and this avoids downtime waiting for shipments.

Oh and one more thing: I am considering going back to deadbugging with no PCB at all since this chip is so big and easy to connect to the chp itself can be considered to BE the PCB then. I'll just solder my wires to it then and not bother to even have a PCB. The PCB was moreso a way to breakout off the chip and give decent size solder points to connect my wires to etc but now that the chip is way bigger I don't need to breakout from it with a breakout board and can just attach the wires to its pins directly I feel. I can use 30ga wire wrapping wire to wrap to its pins for control wiring and use beefier wire soldered directly for power stage wiring. I might go with non SMD decoupling capacitors and resistors as well now.

Note: the amazon chips I bought as part of a module board for a h-bridge brushed dc motor driver setup. The idea there was to desolder the chips from that board to use for my project as that board is WAY too big for any practical purpose in a humanoid but its the two chips from that board that we are wanting to rob off of it.

Ok so with these off the shelf ESCs in route to me, I decided to go digging into what their behavior might be and how I might modify their behavior to fit what the robot needs rather than what a drone needs. Firstly, these ESCs run a firmware called BLHeli_S which is open source and is downloaded/flashed onto their onboard microcontroller via the two signal wires coming off the ESC. Now in a typical drone/quadcopter setup a separate microcontroller called the "flight controller" usually sends commands to each of 4 ESCs to get them to flight a little harder or a little less to achieve the right balance of the quadcopter or w/e or accelerate or w/e. The commands are throttle percentage and brake from what I gather. The analogy for these commands is they work the same way you use the gas and brake pedal of a car. So the gas pedal commands are press gas pedal hard or soft etc and that results in changes to acceleration and speed of a car. So you don't command the acceleration and speed directly but instead command the pressing of the gas pedal harder or softer. The brake command I believe is more stock though - it doesn't have a brake hard or soft but only a brake command I think. That's not good so we'd want to implement a change to make the brake command able to brake harder or softer just like the throttle command lets you do. In my setup, my arduino is going to be sending these commands to the ESC microcontroller just like the flight controller usually would. So my arduino is like the flight controller even though we aren't doing flight here. Anyways, the next issue is once they do brake enough to come to stop, they shut off power and go into a standby mode. That is no good. For a robot we'd want to brake enough to stop the rotation but once stopped we'd want to actively hold the joint of the finger say in place, not just have the finger go limp the moment it arrives at its desired joint angle. So that too needs to be added to the braking behavior. Another issue is that once the motor has not crossed a zero crossing back emf event for a certain countdown, it determines that the motor is stalled, and once it determines it has stalled for enough time, it gives up and shuts off, then periodically runs a start sequence again hoping to get unstuck. This is NOT what we want for a robot. When a robot finger contacts a obstruction, we want it to keep pressing on it indefinitely as that obstruction could be gripping a cup of water and that was exactly intended that the motor keep pressing at same intensity as it grips the cup. It is NOT to independently say ok we are stalling on this cup of water lets let go. That is fine for a quadcopter whose blade is stuck against a tree branch but NOT fine for a robot finger holding an instrument. Making the decision to let go or press the same firmness or press harder or press softer and how long to press is up to the arduino "flight controller" or even the higher level PC running the robot, NOT the microcontroller on the drone. That decision is above his pay grade. He needs to just keep pressing in that case and await further instruction beyond that. So that behavior also has to change. There may have been one or two other mods I wanted but those were the big ones that came to mind.

Edit: actually one more thing: since we now have the motor when stuck just endlessly press waiting till it hits a zero crossing event, we have to first make sure it is listening for incoming commands during this endless waiting period and we also have to be able to command it to press harder or softer or reverse. However, if it is stuck because of some bug or quirk where it was advancing as normal then an obstruction pushed it backwards a bit and now it is waiting endlessly to detect a move forward that will now not happen since it is just commutating the same commutation step PWM endlessly and not attempting any further rotating of the 6 commutation steps anymore, it could just stall forever. So to fix this, we want to create a nudge command that essentially forces into a restart sequence that attempts to actively rotate the motor a full 360 degrees. This would break it past whatever infinite loop it had entered by accident. So basically this is the arduino flight controller's way of saying ok you aren't moving and should be, try to restart - the same way it would behave if it had determined it was stalling in its stock code but in this case the determination to try to unstuck is being made by the higher level microcontroller rather than its own firmware.

That being said, BLHeli_S firmware for the drone is almost universally upgraded now adays to a open source upgrade called BlueJay. You simply hook up a arduino to the two signal wires of the ESC, then plug the arduino into a PC, then you use a software suite calls BLHeliSuite I believe to flash whatever new firmware you want onto the ESC's microcontroller and boom, you have your modified firmware on the ESC and its behavior is tweaked. So using that workflow we plan to replace BLHeli_S with BlueJay, HOWEVER, the mods I mentioned in my last paragraph must be made to the BlueJay firmware before we can flash the modded version of the firmware onto the ESC.

That said, to mod the BlueJay source code, one must first download the full code repository of BlueJay from github onto their desktop PC and then use notepad or w/e to view and edit the code which is stored in .asm files. The code is about 20 files and the total lines of code in the firmware is about 3k lines I think. All written in assembly language. Yuck. Then once one has modified the code to tweak the behavior as I've laid out, then one must convert the .asm files into a single .hex file which then must be flashed/downloaded onto the ESC. The conversion of the .asm files into a single hex file requires one to download the "Keil® PK51 Developer's Kit" which you can only download if you register an account on silabs.com. That kit contains the necessary 3 executable files that do the 3 conversion steps that convert the .asm files into a single .hex file. Those 3 .exe files are an assembler, a linker, and a hex converter. On windows I will have to run each of these .exe's using the command prompt to run them on the .asm files to convert to the .hex file. Or to make it a bit easier one can create a .bat file that runs the command prompt commands sequentially one at a time for you and so you double click the .bat file and the .hex file is made - boom done.

That said, I downloaded that developer's kit and downloaded the github repo for bluejay and have studied the code with chatgpt and began formulating enough understanding of the codebase to begin plans for how to modify the code in the ways I mentioned without breaking the code. This way that codebase can be repurposed into a humanoid robot appropriate variant of an ESC rather than a quadcopter variant. This process is ongoing. I also want to credit chatgpt that 80% of the steps to get this far into this process were largely directed and assisted by chatgpt and would have taken me ages to get this far otherwise. For example, I thought maybe I'd learn how to change the firmware via youtube videos and the first video I saw was discussing the company history behind the company that originally developed and maintained BlueHeli_S firmware. It then went into details of that company's legal problems and politics and world events surrounding decisions that company made. I had to stop and leave the damn video. Holy crap I do not care I just want the ESC to work on my robot WTH! So it was back to chatgpt where I can just get the necessary info I want and not hear a million unrelated things that make me FORGET the original question I had to begin with. I just want my questions answered quickly and concisely so I can figure out what I need to know right away to then get to my next question that the first question pertained to and thereby in a uninterrupted flow of Q&A I can figure out exactly what is going on, what I need to do, why that is the best route to go or if there's a better route, etc.

Note: I did consider just coding the firmware from scratch but after learning as much as I have about the existing firmware, it is VERY involved and complicated and clearly alot of time and effort was put into it and it is useful in many ways so at this time I think its best to try to mod it. But if modding it proves to break it and I cannot mod it successfully without screwing it up, I may have to rewrite it from scratch. It can be very hard to modify someone elses large and complex codebase for ME. I have rarely done this successfully and usually give up quickly due to being overwhelmed and unsure where to even start and unwilling to deeply learn their codebase enough to begin the mod to begin with. Other people's giant code bases tend to feel like a impenetrable fortress and tangled mess and making any change is not only a matter of finding the needle in a haystack of where you need to make that change but also understanding every downstream impact your change will have on other unrelated parts of their code so as to not break something else the moment your change goes into effect. And this feels impossible to do without reading their whole codebase and understanding it fairly deeply. Which is a HUGE time investment that borders on the same challenge difficulty of just rewriting the whole codebase from scratch. Its HORRIBLE. But with chatgpt's help MAYBE I can pull this off in a reasonable time-frame without too much pain. We'll see. I am NOT a big fan of assembly language coding but here we are.

So I'm in this now. I'm committed. We'll see how this goes. I will probably wait to get the ESC to make significant changes to the firmware. I think I should make the code change then test it on the motor/ESC in a live test to see if the behavior changed and if the code all still works. If it does work then I can make the next small change. I can rinse repeat this until all changes are made and working. That is the plan for now.

Ok so after further consideration I decided that the idea of adding significant modifications to a 6k lines of code 20 file assembly language behemoth firmware developed by a big company was just not prudent for me. I need to be able to go in there and add tweaks and improvements for years to come and maintain my code there. The firmware of the ESC is absolutely essential to get just right as it has a massive impact on the performance of the final humanoid robot. The speed and fluidity of movement, the amount of strength, the amount of acceleration, it is all impacted by this. This is just essential. And assembly language is not in my wheelhouse. I am very inexperienced with it. So I officially decided to simply scrap their entire firmware and start from scratch coding firmware for it in C language. I have begun that process and so far so good. I will say though that the Keil PK51 Developer's Kit is an evaluation version and is necessary to convert the C code into the .hex file the microcontroller needs. The evaluation version limits your code size to 2kb which is unacceptable. To get the full version and get that restriction unlocked you have to fill out a form on their website (silabs.com) and they send you a code by email and you can then use that to unlock the software fully. So I did that and am now good to go on that front. While beginning this long journey, I also have been figuring out how single wire bi-directional communication between my arduino "flight controller" and the 8051 Busy Bee microcontroller on the ESC will be able to talk back and forth. I decided to make a custom communication protocol from the ground up for this which I will also then use for all communications between all of my various microcontrollers in my robot's microcontroller network throughout its body. So working out the details of that has also been a recent challenge. But with chatgpt's help I'm making steady progress and have a nice overall plan already. Things are moving along nicely.

How long do you think it will take to finally finish and have a working robot

>>158338

Too long to know like decades

While on my journey to develop the firmware for the ESC so far I was trying to figure out how to implement all the features the original ESC has to offer in its hardware setup but then it occurred to me that I don't need most of that stuff. And a lot of the complexity that was in the original ESC firmware I also realize I don't have to recreate or reproduce in the C language with my own style and formatting but can just leave out entirely. I recalled that my plans for a long time prior to now were to have the BLDC motors operate in a blind manner. This is called open loop commutation. Back EMF normally closes the loop or a hall effect sensor closes the loop or a encoder closes the loop but I had long ago determined I don't need a closed loop. All I need is for my code to instruct the stator's rotating magnetic field to advance through each of its 6 commutation steps either clockwise or counterclockwise at a certain speed and a certain acceleration/deceleration and to do so with a certain duty cycle which will dictate how much power it is moving with. So it can move with a lower duty cycle for a gentle touch or a high one for a rough and rigid or load bearing hauling effect while under serious load etc. Now the back EMF is nice for drones because they are trying to maximize thrust and do so as efficiently as possible but I don't need all of that. If my rotating magnetic field is too fast or not high enough duty and it happens to blindly pass up the rotor because the rotor can't keep up, I call that slippage or desynchronization. And some would feel that is not acceptable and that back EMF or an encoder would prevent that. The logic there is that slippage will result in a single lost revolution perhaps more than one resolution will be lost and that will make the motor's actual rotor location begin to drift further and further from the expected location so that the resulting end stop location will be significantly different from what was expected of it and therefore the accuracy will be thrown off and people feel this is unacceptable. However, consider the 3d printer (well at least the older ones not sure on the new ones), when they hit something or w/e and have some hiccup, the stepper motors sometimes skip or have slippage as I've been describing and that throws off the whole rest of the 3d print. Those 3d printers have no feedback but just give a best guess speed and power level and assume the rotor will always keep up and stay in sync with the stator and usually this is correct. They generally work great. But when they fail a print is ruined but that didn't make them unacceptable or useless. They just had a known less than ideal quirk we'll say. But they were accepted like that. So why can't my robot's stepper like approach to BLDC motor commutation be given the same treatment? And guess what? Unlike a 3d printer, my robot's joints will have a potentiometer measuring final joint angle - so this means that if some slippage and drift did occur along the way, the arduino reading in that potentiometer angle will detect that the motor is not where it was anticipated to be and the main brains PC will be made aware of this and respond accordingly - whether that be upping the duty cycle to increase power to blow past whatever extra resistive forces had caused the delays or slowing down to deal with the extra load it is surely under or if the duty cycle is strong enough, speeding up again more than before to make up lost time and get back to the desired location quickly that it had forecasted it would be by that point in time in order to re-coordinate that joint's movement with the rest of the body's overall animation frames it had projected out into the future and get back on track that way with its plans for the animation. So then the occasional hiccup, slippage, and drift is NOT a deal breaker or something that wrecks everything after all. And over time, the AI of the main brains PC can learn through trial and error to anticipate the slippage events and preemptively up the duty cycle or lower the speed to prevent the slippage from occurring in the first place the next time it takes on a similar task or challenge that previously caused a slippage event to occur. In this way, over time, slippage events will become more and more rare. So the AI can adapt and improve on those issues. This puts the burden onto the main brains PC to deal with preventing slippage rather than on the ESC to figure that out or use BEMF or w/e to try to prevent that stuff. And the main brains PC is a big boy - he can handle that!

All of that to say, we want to keep our ESC firmware simple, dumb, and very limited. This way it can be made very bug free and made more quickly and not require frequent revisions and updates to perfect it over time. It can be a staple. And then the adaptive main brains PC AI can be doing the heavy lifting and take on the responsibility to play that ESC like a musical instrument with great skill. Keep the ESC dumb and make the main brains PC be smart in its use of it I say. Keep the complexity higher up the food chain and let the dumb worker bot ESCs and stuff stay dumb and just follow orders blindly I say.

So that is my return to my previously envisioned approach to this and I feel quite confident it will work out well and chatgpt agrees with me on that.

Moreover, our arduino will also be measuring current so if we see a current increase it can be a collision detection clue and we can report that back to the main brains PC and he can then decide to up duty cycle or slow down to address the extra load or resistive forces that have been encountered - or it could be that this just indicates touchdown - like if grasping for a cup, slippage and current spikes can indicate that we have contacted and are now actively grabbing that cup and the main brains PC can instruct the ESC to just hold steady at a single commutation angle and stop rotating because we are now actively gripping the cup or w/e. So in that case it would not matter really. In fact, I really can't think of any scenario where slippage would be disastrous in its affect for our designs. Also of note is I do plan to put strain gauges on the fingertips so that would also help to know when grip has occurred and how hard the gripping is. So we have multiple redundant clues going on.

And one more thing: because we have a 16:1 downgearing minimum on our BLDC motors, there are going to be a ton of full revolutions of the motor before significant movement of the joint even occurs. Alot of turns are just tightening up slack in the pulley system. So concerns about motor wiggle at startup and things like that making the robot seem like it has the shakes are also not going to be an issue for that reason among others. Also the fact that so many turns are involved to make a full joint rotation means that missing one revolution or two here or there from slippage is probably not even going to be perceivable because so many consecutive rotations are involved that you just wouldn't notice the slight delay that much as the rotations effect on joint rotation is so granular and small per rotation. The result of slippage would be a lot more dramatic if you had no downgearing or very low downgearing because every turn of the motor would then be much more noticeable at the point of observing the final joint rotation animation.

Ok so I had a breakthrough on communications networking within my robot. Originally I planned to have the main brains PC in the chest of the robot connect by USB to a "chest arduino" which would connect by single wire communication to a right arm arduino, left arm arduino, right leg arduino, left leg arduino, head arduino. So the chest arduino is forking out to all of those with each of those on a separate digital IO line connection with the chest arduino. This means the chest arduino was acting as a relay station to forward all the commands out to each of the main branches. Then those main branch hubs may then fork out to their various additional arduinos or ESCs as necessary. However, I recently had a lot of concerns about electromagnetic noise or static interference with this single wire communication which is something that setups like CAN bus addresses. However, I did not want to introduce additional chips and hardware. A very easy solution then occurred to me: CUT OUT THE MIDDLE MAN! Instead of a single USB to the chest arduino, I could have 6 or so USB lines coming right off the main brains mini itx motherboard pc and those can go directly to the left arm arduino, right arm arduino, left leg arduino, right leg arduino, chest arduino, head arduino, etc. This would be made possible by a USB expander port enabling that forking out capability since I don't think that mini itx motherboards come with that many usb ports natively as they are a very small motherboard with bear bones connectors and stuff to cut down on size. By going with USB I get a VERY high bandwidth VERY fast and VERY reliable from a electromagnetic interference standpoint data transmission system that is off the shelf. The USB cords themselves already have ferrite rings on them and have shielded wire as well. So they have a ton of protection. And the USB protocol itself is already very fast and high bandwidth so all the commands I would need both upstream and downstream will be very instant and cause me no headaches at all this way. And that cuts out the longest distance transmissions noise issues and speed issues. Remember that when the main brains PC wants a motor to brake or accelerate forward or w/e we want VERY VERY low latency on those commands both downstream and any upstream responses that let the main brains pc know what is going on. So a sort of hacky DIY single wire communications method with a DIY communications protocol made by me is NOT ideal AT ALL for that with all the noise it will face. HOWEVER, the single wire DIY communications protocol IS fine when going from right arm arduino to right arm ESC #7 or w/e which is just a very short distance of say 5-6" max. As long as we keep the signal line as a twisted wire pair with the ground return line and we keep it away from all the power lines when doing the wire routing and stuff like that we should be ok at such a short distance from a electromagnetic interference standpoint. So that resolution brings me some needed clarity.

That said, for the single wire communications protocol that will be used to communicate from the right arm arduino to the right arm ESC #5 we have had some great success. With chatgpt's help I think I have managed to initiate the microcontroller in code, wake it up and get it configured so to speak, and get its internal clock setup and running and defined in software so its accessible for timing, and also setup an interrupt function that reads the signal wire and anytime it goes from a 1 to a 0 or a 0 to a 1 it calls that interrupt function and that function takes note of what has occurred. Namely, when it goes from 1 to 0 it marks the timestamp of that transition to 0 and when it goes back up to 1 it marks that timestamp as well. It then calculates the duration between those two timestamps to see how long 0 pulse was held down. If it was a normal shorter duration 0 count, it marks a 0 in its buffer memory array. If it was a double duration 0 pulse that was held down, then it marks a 1 in its buffer memory array. In this way its able to decipher a message that comes sort of like Morse code in the form of 1s and 0s where the 0s have different durations that signify a 1 or 0 respectively. And then the main while loop main part of the program has a regular job of reading from this buffer memory array that the interrupt function is regularly populating and it gets this sequence of 1s and 0s and grabs 8 of them at a time and uses that sequence of eight 1's and 0s to consider that to be a byte/char. A char can be an A-z, a-z, 0-9, and several keyboard symbols. They all have a default char/byte representation in 0's and 1's that represent them. So in this way it can convert the 0's and 1's into plain text English. From there it then will determine whether it is reading just noise or a valid message format. My list of valid messages and their format so far is [Forward Nudge 5 5 5], [FORWARD 5 5 5], [Reverse 5 5 5], [Brake 5 5]. In each of these, note that they are enclosed in a opening and closing bracket. This is how my code determines if it is dealing with a potentially valid message or just random noise. If it sees that opening bracket it reads the 0s and 1's till it finds the closing bracket and then feeds the contents into a new memory buffer array and evaluates it further from there. If it finds a known command like like Forward Nudge # # # or FORWARD # # # etc then it considers it valid as long as that # is from 0 to 9. The 5 5 5 here is just a example figure of the parameters that come with the command. it can be any number 0-9 for each of these 3 parameters. I just chose 5 for all three for the sake of an example. So FORWARD 5 5 5 will mean turn the motor in forward direction (clockwise) at acceleration level 5 (or 50% acceleration), until you hit a coasting speed of 50% speed then remain coasting indefinitely.

Also while doing all of this use 50% power (which correlates to 50% duty cycle). So this way it controls how forcefully it will advance the motor, how much acceleration and how much overall coasting speed once it hits its full intended speed. Forward nudge will have the understanding that it is to nudge forward by 5 commutation steps (6 commutation steps is a 360 turn of the motor), and it is to do that at 50% speed and 50% power/duty cycle. So the forward/backward nudge command is for very fine movements of high precision and it is to stop and hold by default after a nudge. Whereas with forward command it attempts to rotate forward indefinitely until it receives the brake command. The brake command just tells it brake at 50% deceleration and 50% power/duty cycle. So this determines how fast it brakes and how powerfully it attempts that breaking. Once it has finished breaking it holds in place. So these commands enable the main brains PC to have tremendous control over the motors behavior and the fluidity and force of the motions of each joint. I still need to now test the code I have so far that implements all of this and debug it and then we can do live testing as well soon. I have NOT yet implemented in the firmware the actual movement code only the communications code for receiving these custom messages and the code that searches for these messages and validates them and breaks them down into commands to later execute on. Also I can always add more of these commands as needed which is quite nice. I know for example that I will need to setup commands for the ESC to report back if it runs into some kind of issues perhaps. We'll see on that though. Most issues will probably be picked up by a arduino that is going to be monitoring a shunt resistor and reading by that means the current being pulled by the motor and thereby know if the joint has collided with something due to current spikes that would happen in that case. Which is a type of collision detection system. It would also get clues from strain gauges which measure pressure put onto finger tips. It can also get clues from the potentiometers that will be connected to each finger joint that will tell the arduino the joint angle of that finger joint in real time as it changes. So with all of those feedback means, the ESC may not have to report back much of anything. I consider it just a blind and dumb electromagnetic field rotator. However one way it might answer back is that after getting a message and if that message contains a command to respond back, then it would respond back that it received the command perhaps. This would be a sort of heartbeat check the Arduino responsible for that ESC could use to make sure it got a message. However this may be overkill and not needed I think. We'll see.

>>128608

>>136902

>having (((ethics))) that tell yiou to not have sex with a robot

>what is sloth in (((xtianity)))

>rich people going to heaven when it is easier to pass a camel through the eye of a needle than for a rich man to get to heaven in ur (((bible)))

>knowledge itself is evil in the slaver's religion you cater to in the first place

>not realizing that yahweh wants you to hate yourself, never have fun, stay poor, and to be a slave rather than have one

>taking jobs away being moral without regard to (((kikestianity)))

The only thing robots can do without harming the human race is be our gfs. They could have artificial wombs and then we would not have to deal with spoiled brats that want to have their cake and eat it too anymore. Even your bible hates women. You can say le sex is a huge sin but if you actually comprhended the bible you'd realize masturbation is not that high on the list of biblical no-noes and that sloth and or being rich actually is a worse sin in your (((fagble))). It's not laying with a beast nor sodomy; it's not even lusting after someone else's wife. This shit is stupid. The only person that could afford a robot so well put together that it can do car work would have to already be rich and thus they'd just hire a bunch of goyim for cheaper of which is exactly why we're not replaced with robots yet, and automated systems being humanoid shaped is not even efficient in the first place for that sort of thing. Some shit that looks like a spider, scorpion, insect, etc, RD-D2 tier 'droids', octopus, etc, that's what it would look like, your bullshit.

If you wanted to make the world a better place unironically a robot god like skynet would be what you want as it could properly enslave the goyim that wish to be enslaved so badly by a god. Concentrating on making it the singularity would be best and it'd make the robots later. Perhaps it could even become ur god as you just know Temple OS types would give it faggoty kike ethics and that perhaps it could magic things into existence just with pure thought and to make sure itself gets created it'd have to do a skynet and travel time to force the goyim to create it thus creating a full circle, all so that the goyim can program it to act like a son of a bitch as the (((god))) you like ain't benevolent at all, is hypocritcal (wrathful, jealous, murderer, created evil while hating on it, etc), and hates fun itself as sin = fun.

*not your bullshit

I don't feel like fixing the typos

>>128608

Good job Larry!

this won't work bud. it's a dead end.

>>128608

Dude! This isn't healthy at all. You've attached your whole identity to this. Everyone's got passions but yours has lasted decades. You've ignored actual advice to work on your specific rules. That means it's a psychological thing. If you hit a wall, you could fall into depression and eventually suicide. Take care of yourself.

>>159604

He's an xtian and you think he's gonna commit suicide?

>>159585

>what is sloth

laziness. why ask what does that have to do with this project?

>rich people = bad

no, it is not that being rich is bad or a sin, it is the affect that money can have on your ego and way you view others that destroys your chance to enter heaven. IE you start to think you are better than everybody and call everyone below you in status a peasant. However, if you are rich and humble and generous, not hoarding wealth in a greedy way, and keep your heart pure, you are not sinning necessarily as you foolishly suppose.

>knowledge is evil in Christianity

not true. The Bible does not teach that in any way. Now innocence of the difference between good and evil does bring with it a sort of somewhat default purity like babies have. And God can attempt to maintain that pure innocent status as he did in the garden scenario. But that doesn't mean knowledge in and of itself is evil to have. If knowledge were evil to have in and of itself then nobody could ever be good if they knew anything which is obviously untrue since the Bible describes many people who were grownups and very knowledgeable who were also very good people and pure and not sinners.

>God wants you to hate yourself

He wants you to look at yourself IF you are in a corrupted and evil state of being and despise the person you've become and long to change for the better. That type of hate is healthy hatred that motivates change. Like hating your sloppy habits which can motivate you to clean up your bedroom and take out the trash and stop living like a slob for example. This kind of self hatred is a change initiator and improvement trigger. It's very good to have when it's needed.

>God wants you to never have fun

not true. He creates provisions for having fun that are methods of having fun that are not destructive and painful to yourself and those around you whether that pain and destruction be immediate or long term effects. For example, you could argue drug abuse is fun but it's not fun to abuse drugs till you die at a young age and your family is devastated and crying in total despair at your funeral thinking what a waste of a life and so much potential. That is not fun for them so God would have you find healthy ways to have fun to avoid that type of thing. His rules are for your own protection and overall well being as well as upholding the maximum well being of everyone around you as well. They are great rules. You are not thinking them through well.

>God wants you to stay poor

not necessarily. He made solomon rich and Job rich and Moses rich and Abraham rich and David rich etc. He merely warns against seeking after riches as the seeking after it can be a snare to your heart and mind. It is a dangerous road to "get rich or die trying". It takes your eyes off the many other more important things in life. Look at the story of Ebeneezer Scrooge for a great example of how this can play out. However, if you got rich while having a balanced life and prioritizing family and serving the poor and whatnot, and you kept your heart pure and did not being to love and serve money in a unhealthy and greedy way, you could be pleasing to God still and healthy in your heart and mind still.

>God wants you to be a slave

Only in the best way. He wants you to be a slave to doing what you know is good, refusing to do what you know is bad to do. Thereby being the best version of yourself you could possibly be and maximizing your inner joy and peace inside. He's not saying go start picking cotton in the south in pre-civil war american. The slave word has that historical connotation for Americans but can extend to widely different meanings in other contexts.

>Making humanoid robots takes jobs away which is immoral

This is a nuanced topic. Any technological advance is a form of subduing the earth. When one technology removes one job, that person is now freed up to pursue another job, often a better job than the one they were freed up from. For example, the laundry machine freed up men and women everywhere to no longer spend much of their week hand washing clothes. That freed them up to have more freetime to build cooler things or have more recreation time. When everyone is struggling just to keep their clothes clean by hand, jobs like a therapist don't exist. But as menial jobs are replaced by technology, higher level jobs that are luxury services like a therapist become available to the public due to the free time those technologies created. New job fields and job types can always be made to replace the job fields and job types technology replaces. Now all of that being said, I do not plan to even sell my robots so the jobs it does frees up my own PERSONAL time because it will do all menial work for me and that will enable me to do things I enjoy more like serving the poor and teaching theology.

.

>>159585

>Robot gfs are not harmful

that's a lie. First, a GF in and of itself whether robot or human is harmful. NOBODY should EVER have a GF period because having one is immoral. And this will bring Gods wrath upon you and society around you because of the increase in sin having a GF creates. Namely sexual sin like sex before marriage or even holding hands. It is a sin to hold hands in a lustful manner with your hot GF. It is a sin to kiss your GF in a lustful manner. It is a sin to even look at your GF in a lustful manner. Better to be only friends with girls, never alone with them, never touch them, and only if married to them, then, and only then, you may lust after them all you want and God will be please with your lust for them ONLY if married to them first. Not only that, but having a robot GF takes away your motivation to better yourself to make yourself more attractive to a potential future human mate. This can remove your natural drive and ambition to better yourself to compete with other men for women's desire and attention. This video creates a simple and funny but profound and true commentary on this very notion: https://www.youtube.com/watch?v=4uE96qUlJ_4

>robots serving any purpose other than gf is harmful

that's not true. In my own life, my personal robot will do our laundry, clean up, cook for us, give us back massages if we are feeling sore after a hard day of work or w/e, will do yard work, will do gardening, will clean our cars, etc. This will free up our time and energy to have more fun time as a family, go on more trips, go camping, go fishing, go hunting, or even do more work in other areas like serving the poor. SO the poor benefit, the tourism and recreational industries benefit and make more money from us, while perhaps landscaping services now make less money from us or private chef or uber eats makes less money from us (although we never paid for landscaping nor private chefs nor uber eats so actually nobody lost a job in this case). The affect locally on local jobs would not be affected much. Now if I owned a mcdonalds and replaced my whole staff with robots that has a impact on jobs. But I don't have one. So no impact. However, like I said, the poor benefited in my case as did the recreational industries due to us having more time and energy for recreational weekend adventures as a family. These are all non-harmful in this case. But even if a job does get replaced, as long as the person replaced finds another job in a timely manner then there is no harm and jobs are always coming and going. People can generally find a way if they are willing to work hard. You are over simplifying and over dramatizing how jobs ebb and flow and transition over time as technology improves. Post industrial revolution and automation of yesteryear, I'd argue quality of life and free time available is greater now than it was in medieval times which you are romanticizing. Good luck being a serf or a butcher, baker or candlestick maker...

>>159585

>They could have artificial wombs

Now you just went from GF to artificial wombs so you are now promoting not only fornication ideas but also the idea of a GF, NOT A WIFE, being the mother of your child - which then takes away family stability for the child. The tie between GF and BF is fickle at best. At least husband and wife has a theoretical lifelong commitment and vows protecting that tie and making it more lasting and durable which benefits the child and prevents single parent households which harm the child. However, in your proposed scenario, you are baking in and guaranteeing the child NEVER gets to experience the gentle loving embrace of a mother EVER. No breastfeeding which is a precious bonding opportunity. No tender embrace of a mother's arms. No delicate sweet cooing of a mother's voice you can hear as you press your ear against her chest as it reverberates through your head and body in that warm vibration from her vocal chords. All you get is a shitty speaker and rubber fake mom who is your dad's f-buddy. How disgusting and what robbery of a child's need for a mother to love on and dote on them. Sure some mom's are shitty but those loving moments even most shitty moms brought to the baby early on are precious and irreplaceable. I smile huge every time my 1 year old son wakes up and I bring him to my wife laying in bed and put him onto her and she turns and smiles so sweetly at him and hugs him warmly and coos at him with loving words and he EATS THAT UP. It is one of the best parts of his day and he feels so happy and peaceful in those moments. It is precious to even observe for me. I am not close to my mom now as a adult but I STILL cherish those times as a baby that she treated me that way so its nostalgic. But your shitty robot fake mom would only give a disgusting loveless and cold, hollow mockery attempt at simulating this experience and the child would know the difference spiritually and intuitively and be devastated to not have a mom. This is uttermost cruelty to a child to rob them of a mom. This is akin to me going around and finding every mom holding her baby at a park or zoo or grocery store and ripping the baby fro his/her mom and killing the mom in front of them and putting that child into the arms of a robot to pretend to be their new mom. THAT is essentially what you have proposed here with your sick and disgusting, cold, evil artificial wombs idea.

>>159585

>Even your bible hates women

That's a lie. Consider that countless millions of people, after having read and studied the Bible, concluded taht this would be their favorite prayer based on what they read: "Hail Mary, full of grace, the Lord is with thee, blessed is thou amongst women". Does that prayer sound like a prayer that considers Mary to be hated because she is a woman? No. It doesn't. It says in teh Bible: "So the angel told her, “Do not be afraid, Mary, for you have found favor with God." --- this proves the Bible does not hate women but that they have the opportunity to find favor with God if they are humble, hard working, loving and kind etc.

>masturbation is not that high on the list of biblical no-noes

while that may be true, a sin is still a sin and will send you to hell just the same if you don't repent of it. So just because a sin is not the highest on the list does not mean you should normalize it or forget to fear the wrath of God regarding it. Though his wrath may not be as heated or severe for a lower tier sin, it is still heated enough to make it capable of repaying you according to your deeds in ways that are miserable and painful in various ways. It is far better to just please God and avoid his wrath entirely so that instead you reap his blessings and favor which is clearly more enjoyable than reaping his wrath.

>>159585

>it's not even lusting after someone else's wife

Now this is debatable. Lusting after any woman that is not your wife is seen as lusting after someone else's WOULD BE wife or someone elses wife which are fairly similarly egregious sins. They are both considered adultery of the heart. Now if the robot is made in the likeness of a real woman, then lusting after it is the same as lusting after the real woman - no different than lusting after a picture of a real woman is considered lusting after the real women even though the picture is not the real woman but a visual depiction of the real woman on a screen or w/e. It's still considered lusting after the real woman. So if the robot looks like any real woman, even if only roughly like her or cartoonish version of her, it still counts as lusting after a real woman and is then still adultery of the heart and still a serious sin. You are only allowed to lust after your own wife if you are married. If you are not married you are only allowed to lust after pursuing of holiness and righteousness. That is your permitted lust target.

>the only person who could afford a robot that can do car work would already need to be rich

not necessarily true. I will be able to afford to DIY build my robot and my robot will be able to do car work. The parts are only going to be like $6k-$7k to make it. Most people can save up enough to afford that over time IMO. And I am releasing all the plans for free. So anybody can follow along and make it and afford it.

>spider or octopus type robots would be more efficient

that is not proven and there would be downsides to that approach. The most obvious is that it would literally be a monstrosity and a horror to anybody who saw it then. I could not have a giant octopus robot on my property with small children they would all be terrified. They have very active imaginations and no amount of explaining would prevent constant nightmares and uneasiness. But a beautiful humanoid that looks human passing would NOT have that affect IMO.

>making a false god AI would be best to enslave people

no, that would be bad. It would draw people away from the true and living God of the Bible. Which would bring the wrath of God upon them and upon the person who created the false God. Therefore harming society tremendously.

>the false god ai would make humanoid robots later and humanoid robots are bad for society but if the false god made the humanoid robots then its good for society

this is a logical contradiction. You can't first argue humanoid robots replace jobs and are bad for society then argue its good for society to make a false god that makes humanoid robots to replace jobs and harm society. If the false god ai makes humanoid robots to replace jobs then it harms society according to your own previous claims.

>perhaps you can make the false god ai your god

I could pursue that if I was determined to anger the God of the Bible and bring down his wrath upon me and my family. But I love my family and love myself and love God enough to not do such a foolish thing.

>you could have your AI have Bible ethics

yes I can and I will. The only good idea you said.

>>159585

>God is not benevolent

that's a lie. He is. And you will need to assume that He is and revisit all of your slanderous claims about Him as you read the Bible or reflect on what the Bible says in order to revisit all the things it says about God and what He did and consider them in another viewpoint that is charitable and giving the benefit of the doubt as far as His motives being pure behind it all. If you revisit each and every thing one by one with that mindframe, even as a thought experiment, you will find that everything He ever did was just, righteous, genius, had lots of foresight, had lots of careful planning, netted a long term end result that was positive and worth it, and all the ends always justified the means. But if you take on a automatic assume the worst motives, assume the ends never justify the means, assume malicious intent always, then you are able to turn ANY AND ALL actions done by ANYONE at any time automatically into sinister and evil actions automatically. I can watch a guy hold a grannies hand and help her cross the street and if I assume he's evil, malicious, perverted, etc then I'd be able to say he's just wanting to touch the granny hand so he can fap to her later because he has a granny fetish etc. You can just make up any accusation about even the most mundane and probably kind and generous deed you view. So how much more can you assign evil to complex, nuanced, and very long term strategic controversial decisions God makes in the Bible while He is holding total knowledge and total foreknowledge which are all factoring into his decisions. To understand decisions made on that high of a level, one must think much more deeply on all the downstream ramifications and possible benefits over a much longer timeframe and taking into account far more facts. A cursory and skeptical glance at the actions will NOT suffice in these cases. Which is why your conclusions you've drawn were made overly hasty and poorly thought out. You need to think more critically and deeper and for longer to begin to seek understanding. You severely lack understanding. Seek wisdom and seek understanding as they are able to be a protection and aid to you in life. Without them you are doomed to a life a misery in one way or another based on the extent to which you lack them. And right now you severely lack them both. Which indicates you have a very miserable life at present or are heading for misery soon.

>>159585

>God hates fun itself as sin = fun

While sin can seem fun for a season, in the end it brings destruction and misery for both the sinner and those around them. So he hates it because it represents a way of having fun that is destructive and painful in either the short term or long term. He wants to spare people from that pain and suffering that sin causes. He desires this out of benevolence toward men and women everywhere. Just as a human father hates the idea of his children putting their small hands on the stovetop which may severely burn them. They might think its fun to touch the stovetop but it won't be fun to have a blister from being scalded.

Further, God provides ample ways to have fun that are not sinful. You think sex is fun? You can have sex with your wife and have fun with her in that way. So all sex is not wrong, but sex done outside of the confines of marriage is harmful and destructive so even if it feels fun temporarily, it's not worth doing that. And you see this with how people are giving up on dating and women. The vast amount of fornicating is ruining women and men and making them hate eachother. God would have us spared all of that if everyone waited till marriage ot have sex. All women would then be loyal, chaste, virgins, pure, and respectful and love and admire men and want to serve them dutifully as wives aught. Men would cherish women seeing their piety and subservience and faithful loyalty. Men would not feel the need to call them wicked cheating sluts anymore because none of them would be wicked nor sluts. Because they obeyed God's rules. It would solve all the problems men and women face in the dating market. So you see,God's rules are designed for our GOOD. He is smart, He saw all of this coming and wanted to spare us this pain and suffering caused by sin.

>>159604

>you've attached your whole identity to the robot

not true. I have many other interests and pursuits that I've also attached my identity to. Husband, father, Christian, theologian, teacher, inventor, athlete, son, builder, real estate investor, mechanic, computer programmer, innovator, etc. So if roboticist as one facet of my identity did not work out well, I have diversified my identity plenty to avoid becoming deeply saddened by one facet not working out. I am balanced then. And in any case, as a Christian, my first and foremost identity is necessarily as a faithful follower and slave of Jesus Christ. As long as I maintain a faithful follower and slave status to God, then anything else I do or don't do as it pertains to pursuits in this world become relatively unimportant and merely fleeting past-times by comparison. So they pose no threat to my overall joy or peace. I can pursue them with no risk to my overall life satisfaction and joy whatsoever, They can only enrich my life further like icing on the cake but cannot be a detriment as long as I acknowledge God in all my ways and submit myself to Him completely in all things.

>your robotics passion project has lasted for decades

and that's a great thing. It's a blessing that I've maintained my passion for something for that long with no signs of that passion waning. Because if my passions for things were fleeting, then it would be hard to achieve anything significant in any area because I'd leave to quickly to accomplish anything serious.

>you've ignored advice to work on your specific rules

are you referring to my rules based AI? I have worked on it some on and off over the years and will do so as I feel led to do so here and there. But building the physical robot in tandem with the AI is my preferred order. Do them both at once. Keep both plates spinning IMO is best.

>if you hit a wall, you could fall into depression and suicide

as I said, I don't think that's possible given my diversified identity and given my Christian status and approach to that. However, if I hit a wall I could still be sad about the wall and mourn. And nothing is sinful about doing so. Yet I believe it would not even go that far. If I hit a wall, and the project is full of walls of various sizes, I'd generally set it aside and mull over the problem and come back with a solution in short order. I am a very gifted creative problem solver. Walls are easy to break through for me. I've not had a single wall I have not broken through with ease and fairly quickly to boot. Now the ONE wall that was VERY long lasting, substantial, and felt impenetrable for my project was creating AGI. I felt that creating AGI or singularity-lite, which is something I have maintained is probably almost necessary to do to reach my goals, this felt like a wall I was utterly stopped by. But what did I do? I did not despair at all. I saw it as a fun challenge! I had utmost confidence in myself that I would figure it out eventually. That is the key. And so I just chipped away working at the physical robot under the assumption that I'd solve AGI-lite eventually. And low and behold, 6 or so years went by before I solved AGI-lite. It just came to me one day. The story of how I solved it is on one of my AI youtube videos. It was a real eureka moment and was so cool. I knew it would happen eventually! So if I was able to solve AGI-lite, then what wall can there possibly be that still remains that has even the most remote chance of stopping me? There simply is NO WAY one still exists. I feel I have already destroyed every potential future wall I can possibly think of. I have tried to think ahead for years of ALL potential future walls that I could run into and have already solved them all in advance with solutions. Usual several viable solutions to choose from even! So really I just dont see hitting walls as even an issue at all to be concerned with. I know how to handle walls and the biggest one - the AGI-lite challenge, I already steamrolled.