RE: Oh no we're skewed! Prusa Mini edition.
Honestly I'm thinking of sending the Mini+ back. I have a XY skew which is a pain to fix and I fear will be back with time.
Really this should be fixed through software/firmware.
Yeah, It might have been smart for me to follow other designs on the labels. They don't necessarily match up with other calculators.
RE: Oh no we're skewed! Prusa Mini edition.
hello, i used goskew with prusasclicer for a mini+ and i notice in the gcode file anomalies on thumbnails after processing in goskew. i guess you have to remove the thumbnails in prusasclicer?
for example :
; generated by PrusaSlicer 2.5.0+win64 on 2023-02-03 at 12:40:34 UTC
; thumbnail begin 220x124 11772
; h786ZPQNCVG1lMaIqJq5zqTEX7.000uqFAoc78mbVY0.000DaAUcq8GzDB3nQiUnFmCvlWboX7.000uNk+paElUEX7.000Y0.000
; nspOi3VXUiQ2GToNFkuo/MtM4DDWOEyn7eQ+OaoKFqegp5Y+1jyWBj22VTboDj5rrHvYBzXVIvtdpJ
I've also noticed this, but haven't had time to fix it. As far as I've seen it doesn't effect the print, only the preview image.
I've made an issue for it, so I'll take a look when I can. Should be a pretty easy fix.
RE: Oh no we're skewed! Prusa Mini edition.
Thanks Kranex
i examine your code
I thinks two solutions
- modify regex (add space after ] ' -> gmatch, _ := regexp.MatchString(`G[0-1] `, line)
- testing the first char of each line -> for i, line := range lines {
if first char not equal ';'
gmatch, _ := regexp.MatchString(`G[0-1] `, line)
if gmatch {
blablabla
as I don't know 'go' I modified the regex and after compilation it seems fine
RE: Oh no we're skewed! Prusa Mini edition.
After playing with this for a while I came to a realization. The problem isn't skew, or at least not what Marlin calls skew. Skew is consistent. You can measure and compensate for it. The mini has what you might call 'swing'. Dial it in before a print and it will be changing with almost every layer. I ended up giving mine away; I can't use it to make mechanical or matching parts so it's no good to me. I thought about machining a couple aluminum parts to reduce the swing but even ignoring the swing I have better printers and the person I gave it to had no printer. It will do random toys downloaded from Thingiverse but beyond that it's pretty bad.
RE: Oh no we're skewed! Prusa Mini edition.
Thanks Kranex
i examine your code
I thinks two solutions
- modify regex (add space after ] ' -> gmatch, _ := regexp.MatchString(`G[0-1] `, line)
- testing the first char of each line -> for i, line := range lines {
if first char not equal ';'
gmatch, _ := regexp.MatchString(`G[0-1] `, line)
if gmatch {
blablabla
as I don't know 'go' I modified the regex and after compilation it seems fine
Fixed it in the latest version, took longer than expected as it kept slipping my mind.
In the end I decided to go with:
^\s*G[1-2]
To the best of my knowledge, at least out of a slicer, gcode is always one instruction per-line and that line always begins with the instruction.
Conditionals would be an exception to this rule, but I highly doubt that translation gcode that would require skewing would be in conditional logic.
To really do this properly I'd have to upgrade goskew to parse gcode into an AST and manipulate it that way. There's libraries for it but I don't think
it's enough of an issue to deserve the effort.
RE: Oh no we're skewed! Prusa Mini edition.
Hi
Just wondering is the XY skew generally the same on mini (printed Y front/back) mini+ (injected moulded Y front/back) ?
RE:
Guys I've been trying to correct my mini for months, besides making many upgrades(extruder and heat-break Bondtech) I decided to square the machine as much as possible.My mini suffers from a tilt of the XY axis, toward the board and not toward the display as usually happens(see orange arrow):
The deviation is small, and I could not correct it in any way.
Mounting the pgooch designed shims beside the buddy in my case makes the problem worse, because my axis has to be shifted counterclockwise.
The only possible way to be perfect was to screw the top screw of the box buddy to the aluminum profile:
But leave the two side screws unscrewed.
This is because screwing those screws brings the box closer to the aluminum bar and inevitably shifts the y-axis clockwise.
So however the printer becomes very unstable, I could try to print a new box buddy mo I would then have to disassemble the whole machine without the confidence to solve.
I came across this thread by chance and saw the solution created by goskew.I printed the calibration triangle and got the following measurements:
SX:99.48
DX: 99,86
Base: 99.86
I then reworked the gcode with the command:
goskew tri 99.86 99.48 99.86 -o caliangle-skewed.gcode caliangle.gcode
I printed the modified gcode and obtained the following measurements:
SX:99.76
DX: 99,76
Base: 100.00
Is it normal to get these measurements? I don't understand why the base is longer. I have the impression that the script just reversed things.
RE: Oh no we're skewed! Prusa Mini edition.
Hey guys!
I found this thread from the YouTube video and the GitHub repo.
Of course I have been suffering the same issues as all of us MINI'ers. Thanks for sharing all this it really helped me to identify that was my XZ misalignment which was making the issues.
Checking possible solutions I came across this model and this, so I decided to combine both to help myself with the calibration.
I hope it is helpful for somebody else.
RE: Oh no we're skewed! Prusa Mini edition.
Re. Carlo
my mini (printed Y front/back) had a 10% XY skew after alot of measurement, it was my Y axis (if you have a long enough Machinist Square) mine was of buy 1,1mm
so if you have the mini with the printed Y fornt/back it can be the same issue
