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

Cutting aluminium is much easier than cutting steel. I am glad that we went for aluminium first for this build

The EU is trying to murder the internet.

Or at least some of the leadership. What the fuck?

https://boingboing.net/2019/02/05/death-sentence-for-the-web.html

@ekaitz_zarraga I can claim almost all of my meetings are client meetings because I work in the same space as Ben who who has a company that works with mine.

Business stuff is just weird. We are three guys working together (my brother works with us also) and there are two companies that work together somehow despite the three of us working together on everything.

My current suspicion about the laser being wonky is that the arm it is mounted on isn't particularly strong. It isn't meant to hold much weight, it was originally holding a pen.

So it can bend just a little bit and that may be enough to throw off the beam angle after it cuts into the material just a little bit.

This is solvable, but may require a new frame.

I can't figure out what our laser is doing. When you start a cut at the surface of some wood quickly it cuts wonderfully with a nice fine line down about 2mm into the wood with 3 to 4 passes. And then it doesn't really cut past that even if you let it go for 20 or 30 passes.

But it won't really cut deeper.

The weird bit is that this seems to be the case when you change the distance between the lens and the wood by up to around 4mm. I have no idea what is going on.

I suspected that the events people wouldn't have any of the support hardware needed for the demo, like cable adaptors and a keyboard and mouse to do the initial setup.

It appears that I was correct. Luckly I got josh to bring all the hardware needed to run the setup. So we get to be the people who actually know what is going on despite everyone else being experienced events people and we are the new guys.

16 positional inputs to a script is too many. Parsing command line input manually isn't terrible for one or two arguments, it becomes unreasonable as that number grows.

So yay argparse.

Never trust other peoples math.

The documentation for the parser I am looking at says 'if you have questions ask AutoDesk'

The current build of from our directly paying job is going to have its first public appearance starting tomorrow and I am not going to be there. Despite trying to never have one person handle a conference again Josh is going alone, but it is just to help setup then he is going home.

So not too bad.

But I am still nervous as fuck.

@ekaitz_zarraga it does look like supporting at least the more basic functions of a gerber file should be pretty straight forward. I will add it to the list.

@ekaitz_zarraga huh, is gerber related to gcode? I haven't really looked into it before.

@ekaitz_zarraga I have support for some gcode, I am not sure how Gerber differs from gcode.

But yeah, it is planned. Part of what I am doing is getting away from gcode because it was designed for when code length and processing were much more limited than they are now.

it looks like what I was missing was that the svg arc paths are made to be consistent with other path elements, not to be understandable.

Which makes sense, but it is still annoying.

Todays plan is to fix the arc handling for SVG parsing with the sinister plotter and add support for DXF files.

2d DXF files are very very simple to convert into strokes for plotters, which is by design, I think that 3d dxf files aren't really any harder to parse, but the sinister plotter is currently only 2d so that will have to wait for latter.

And I think that I am missing something big about how SVGs encode arcs, it seems unnecessarily complicated to me.

@theoutrider I don't think I can argue with that.

@theoutrider I thought it was NSA, but I am not certain.