Bug #17
closedVisicut Documentation: YMax definition problem
0%
Description
In the visicut documentation on the LaOS wiki, Ymax is defined in the lower corner. However, in the rest of the LaOS software, Ymax is the lower corner.
Updated by jaap over 12 years ago
Correction: in the rest of the LaOS software, Ymax is the upper corner.
Updated by david over 12 years ago
Is it a documentation issue or a Visicut-wide problem? When sending jobs with Visicut the Y axis is flipped. I haven't been able to get the CUPS driver to work so I can't verify if it has to do with my config.txt or with Visicut.
Updated by Anonymous over 12 years ago
my guess is that it can be solved in the config file: make ysteps positive again and define ymax as very large positive
Updated by david over 12 years ago
That solves the problem in this case, but of course only works if that configuration is used in conjunction with VisiCut.
Updated by peter over 12 years ago
In any case, (0,0) SHOULD BE "lower left corner".
If you send this file:0 0 0
1 10000 20000
You should end up with a diagonal line from the lower left corner,
10mm in X direction (left to right) and 20mm in Y direction (bottom to top). As seen from the
Front of the laser. If the pstoedit driver or visicut thinks otherwise, it's config file should be altered.
There is info on the wiki how to change the pstoedit config. Look for the new "postscript" config file.
Updated by david over 12 years ago
Okay, with the settings that work for Visicut the 0,0 point is in the top left corner. I'll see if there's a way to adjust the Visicut settings.
Updated by peter over 12 years ago
After a discussion with Thomas Oster, we decided to look into this matter after the Laos Workshop.
We will most likely fix the matter in Visicut, and make the LEFT/RIGHT and scale parameter fixed in the visicut driver, so you cannot set them incorrectly
Updated by t-oster about 12 years ago
Hi,
in VisiCut the laos driver is updated to always use the lower-left-corner as (0/0), so the problem should be fixed. Be sure to always set the bed-size correctly.
cheers
T
Updated by axel about 12 years ago
See also [[https://github.com/t-oster/VisiCut/issues/19]] and use latest Visicut version (1.5)
Updated by t-oster about 12 years ago
- Status changed from New to Feedback
- Priority changed from High to Normal
Since the problem should be away with current VisiCut versions, I switched this issue to "feedback". If there is no one having problems in the near future, we might aswell close the thread.
Updated by t-oster almost 12 years ago
- Status changed from Feedback to Closed
Since no one seems to have this issue anymore, I'm closing this bug.