I’m hoping someone here can help me figure this out. I created this file, exported it to an SVG, then set the parameters. It all came out great EXCEPT it is missing the last section of wall. I have no idea why. It shows up fine on the Luban interface. So why doesn’t it print? I’m using an A250. Love it so far, altho I really need the non-existent manual…
it looks like it cut the entire piece of material, is it a scale issue? or was your stock larger and it cut off the area where your last wall would be?
The stock was plenty long to cut the last wall. It cut it off short. The whole piece of stick material was on the bed and I ran the boundary before starting the cut and it was all good.
This is the stock piece it was cut from -
How utterly obnoxous 
this has to be g-code related, it clean cut the edge… either that or something funny with the model itself?
You’ve set your machine as A250 in Luban?
-S
1 Like
The thing is it didn’t etch the brick on the overcut. So it’s like the machine just ignored the last part. So could be the G code, but all the brick is one SVG so why do some and not all. It was 3 svgs overlaid (and don’t get me started on why it won’t import svgs at the right size) - the bricks, the concrete form lines, and the outside boundary. The outside boundary is correct in Luban and is the only one that cuts thru. All the concrete form lines are one file so it should not have cut one but etched all the others.
I never set it for the A250 but it is set for it - I assume by connecting via wifi the machine told it? It says A250 in the upper left corner. The final size of the cut piece is 111mm xx 194mm so it is too big even for the 150 if it was set for that…
It is supposed to be 111.5mm x 228.7mm. I set it up so the 228mm was running parallel to the Y axis.
I’ve been following this topic for awhile and I still don’t understand what’s different. What would help me is your first image with red circles around what’s different between the computer and the result.
So it is. Interesting. Post the gcode.
1 Like
The whole top section is missing. the square cutout is supposed to be 2 rows down from the top, its only one
Here’s the g code -
concrete_52374054.nc (634.8 KB)
Here are the three svgs I composited -
Eyceevk7wpT9RGGJ89FeQECqs.svg)
And the third which didn’t post for some reason.
I used manual and set the laser power and cut and jog speed individually for them. Thern unchecked the auto box in Luban.
I can’t keep all these boxes straight - Luban output the correct gcode, but then it printed wrong. Ignore my last post.
If I scroll about 50% of the way through the file it print looks like so:
It should’ve printed the missing top section about halfway through the print.
The cuts all happen at the end and I don’t even see a cut path that would explain what happened.
Ya, so any thoughts on why it didn’t? I’m baffled. I am loath to waste more material trying it again…
My theory I think is the same place that sdj was heading - the machine hit a limit switch or something and would not physically travel further.
Did you watch any part of this engraving? I guess it spent a lot of time engraving that top line.
Try jogging the machine with the controls to all possible areas on the bed - does it reach them?
There are some cases in which the machine will think it’s smaller than it actually is. For example, if only 3 linear modules respond at startup instead of 5.
Y and Z linear modules are plugged in to splitters right? Next step would be to post the touchscreen log exports so we can see what happens at the machine startup.
I was curious myself about whether or not the tool paths were still going on without cutting, but it wouldnt explain the clean cut off
I will try all this. Thank you for the suggestions. I was not watching the print while it happened - checking in once in a while but mainly watching the computer to track it. And no, unfortunately I don’t remember if it showed it etching the missing part.
I’m headed out to dinner now but I will check later tonight or tomorrow and post. Thank you all for all the help!
1 Like
This design I think would work well as a optical illusion, or maybe an IQ test 
Every time I look at it I see a different number of rows.
Thank you for making me laugh in this annoying time!
1 Like
Maybe if you had combined each thing into a single diagram it would be helpful too, maybe luban is just getting confused and cut off the print due to a layering issue or something
i wonder if running direct from the snapmaker instead of through luban itself would help too