-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Focus value not exported anymore after using execute #213
Comments
Please give all needed details so that someone else can re-create the problem on their PC with just your information.
|
For example, could you upload a ZIP of your settings folder or send screenshots of the relevant parts?
|
Thank you for your answer. |
oops... without even looking at your file, I now remember that I almost fixed that bug two years ago but never found time to finish that... So the issue is in LibLaserCut, the library that provides the laser drivers of VisiCut. Moving the issue over to there. See #177 : We should also add a test against such bugs in LibLaserCut. We already have some tests that check that the content is the same when the same job is sent twice . These were introduced in 8443554 but specifically for the focus we don't do that yet. |
Hi,
We use a lot of thick material so we make the focus on the surface for engraving and have a focus value for each material set to minus half the thickness (for example for 8mm mdf the cut setting has a focus of -4mm)
We generaly export the gcode and send it to the laser cutter via its web interface (it's a Robotseed lasercutter with a smoothieboard). And it works fine.
But to spare some times we also use the "execute" button from visicut to send the gcode directly. This is where we have a strange behavior:
We use visicut 1.9-200 on linux and windows 11 with the same behavior and it's the same on visicut 2.0-4 on linux.
Anybody with the same issue ? Any idea how to solve it ?
Thank you.
The text was updated successfully, but these errors were encountered: