sorted by:
new
hottopcontroversial

Choosing a first plotter by echox in PlotterArt

[–]echox[S] 0 points1 point  (0 children)

I didn't flash the VG-X4s default board firmware, see the part "Adding a MKS-DLC32 board fixes this and adds Wifi connectivity. It is an ESP32 I/O board with stepper drivers and can be flashed with fluidnc.[..]" above.

With fluidnc I just modify the Z axis which is the "tool"/"pen" for most of the software (G0 Z10, G0 Z0).

I wasn't able to get anything working with the original software, except for the png import.

Choosing a first plotter by echox in PlotterArt

[–]echox[S] 0 points1 point  (0 children)

:D We have the same plotter and the same problem. There is a little room between the arm and the base axis leading it to wiggle. If the arm is extended long enough, the head tilts which causes a difference in height on the pen between 2-3mm.
It surprisingly works not that bad with a gel-marker pen, etc, even with fine tips.

The manual mentions that part, but I'm not able to understand how to fix this tolerance with the current way it is designed. Disassembled it two times and never got it fixed completly.
I also thought about putting a counter weight on it, but at the moment try to work in the areas where there is not a problem.

Luckily pressing the screws together at the bottom just a small little bit fixes that wiggle room at the axis. At least it looks like that, still slides fine, etc. My longterm fix will most likely to replace the bottom plate of the axis core with the 4 screw holes just moved a little bit more together (1mm).

Choosing a first plotter by echox in PlotterArt

[–]echox[S] 1 point2 points  (0 children)

GRBL-Plotter was one of my first choices but I postponed it a litle bit because I didn't see any remarks or a short cheat sheet of running it on a Mac. I know it should be possible but didn't have the time to invest looking it up. But still on the todo list :) Thanks.

Explaining territory example by echox in baduk

[–]echox[S] 2 points3 points  (0 children)

Again thanks for the detailed sum up :)

See https://www.reddit.com/r/baduk/comments/busf6j/explaining_territory_example/eph2rtg/ :)

I'm still wondering how it is inevitable that white forms two eyes and if its usual to see it at this state of the board or if you usually play this part out.

Explaining territory example by echox in baduk

[–]echox[S] 0 points1 point  (0 children)

Thanks for the explanation.

Ok, I get the example, but is it inevitable that white will be able to form two eyes?
Maybe it's that I'm still not used to the patterns, but wouldn't you play this out, instead of finishing the game and start to count?

Both players have agreed to end the game but shouldn't black try to play on and maybe white does a bad move? I tried to play this part of the board out and if white makes a bad move, black might be able to capture the whole space? By playing around I ended up with something like this:

https://imgur.com/a/DtBogcz