inmysocks (version: awoo) @inmysocks@awoo.space

So now I have time when I can't really do much work. We need the CNC to make the prototypes for the new laser cutter so we can test that out, but because the one motor has a bent shaft we have to wait for the new motor hardware which isn't going to be here until Tuesday at the earliest.

So PHD work I guess. I should get my doctorate at some point.

and the problem was, of course, both loose belts and a bent motor shaft.

Fucking hell.

At least replacement motors are much cheaper.

@ekaitz_zarraga I will. I need to start trying for things like that.

@envgen the only places I ever found were local bead stores.

After a quick inspection the motors aren't visibly bent, and the belts are certainly looser on one side than on the other. So I am hoping that is the problem. Either way it is a tomorrow jed problem, it is time for today jed to go home and eat.

Well, the problem wasn't just the speed. It is not moving the same distance on the y axis as it is on the x axis so everything is slightly stretched on the y axis.

There was a crash the other day which may have messed up some of the belts, or worst case bent a shaft of one of the motors, which would be a pain to fix. And kinda expensive.

@lyliawisteria@octodon.social it doesn't look like it. At least no machinists that are also good at UI and UX.

My secret is that I work with someone who has about 20 years of UX experience who yells at me when I should be doing better.

@lyliawisteria@octodon.social bCNC mostly has that, but it doesn't have a very good interface and almost everything it does could be automated better. I am writing a program that does at least the simpler things much easier. Simpler at the moment is 2d cuts that only have an up and down height. I am going to extend it to 2.5d stuff after I get it working nicely

now it says the total time is 16 minutes...

Go home bCNC, you're drunk.

now the total time estimate has dropped down to 40 minutes. I am not sure why bCNC has such a hard time estimating how long things will take, gcode is designed to have pretty exact timing.

I think that the CNC machine was moving too fast and that is why circles were coming out weird. At least I hope that is the problem, otherwise I didn't tighten everything down correctly or somehow the frame has gotten skewed somehow.

But the cut, instead of taking about 15 minutes, is now going to take a bit over an hour. I may have lowered the speed more than I thought.

Every time I remember that npm is VC funded I wonder how long we have to wait to just burn everything down.

People > we should have a plugin library that is easier to use and can be updated remotely
Me > Ok, here is a plugin library that is easy to use and can be updated remotely
> .... crickets ....

later

People > we should have a plugin library that is easier to use and can be updated remotely
Me > ARGH

@envgen tropical weather is coming!

My changes to droppy were merged into master. I think that this is the first time I have had a pull request accepted in a repo where I don't know the owner

The CNC machine was mean to me today. By which I mean I kept messing up and forgetting steps when trying to use the CNC machine today.

I am getting used to using my own software which has much more reasonable settings than bCNC. I don't like bCNC and once it is production ready Sinister Plotter will be a better option.

It doesn't do well with CNC machines yet, I need to do some work on how it generates gcode for them.

I have modified droppy to play well with other applications on the same server that also use web socket connections.

I feel accomplished.

@jk there are also hamburgers, but that part is incidental to the gigantic dome.