Skip to content
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

Do not go to rest after job. #10

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

t-oster
Copy link
Contributor

@t-oster t-oster commented Oct 6, 2013

For the requested VisiCut feature (t-oster/VisiCut#176), I need the LAOS to not go to the rest position after finishing a job.
I could add a "move-to 0,0" at the end of a job in software, if I wanted it, so I don't think removing that will cause any harm.
The only difference is, that the "rest-position" in the configfile won't have any use anymore.
What do you think? Do you need the hardware-rest feature?

@peteruithoven
Copy link
Contributor

If we can replicate the functionality in VisiCut I would be fine with removing it. It's nice to have it more to a rest position closer to where you usually work because that saves a lot of time. Usually you'll lasercut top left, while endstops are usually top right.
It's also good to have it not tough the endstops between jobs, because the switch moment might vary slightly.

@pbrier
Copy link
Member

pbrier commented Oct 27, 2013

Rest position should be configured in machine.
The machine should ba able to move to this position by itself.
However: A "direct mode" can be made, that does not go to the end pos after each job.
t.b.d.

@t-oster
Copy link
Contributor Author

t-oster commented Oct 29, 2013

OK. Variant one:

  • go to rest only on "indirect jobs", meaning files with usual lgc file-ending. Direct jobs (e.g. "lgcd"-file endings do not go to rest until the file contains a special simplecode command to go to rest
  • don't distinguish direct and indirect mode in this case. Either the file contains a go-to-rest-Simplecode command or not.

Although the second one will make all old laos-software result in not going to rest, I think it is the more cleaner one, since for the direct-mode a go-to-rest command is needed anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants