-
Notifications
You must be signed in to change notification settings - Fork 74
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
No more "power-on delay" setting? #57
Comments
Same problem for me (as probably any other drawbot user) so +1 |
I think someone implemented that feature in the main branch but I haven't tested it enough to create a new release. If anyone is curious you could try cloning the repo and see if it works for you. Otherwise the older releases are still there. |
Crap I ran into this same issue, was hoping someone had a solution :/ |
Hello, I have just cloned the repository, and put laser.inx laser.py files with latest version of svg_to_gcode: Gcode output sample: M5; M5; G21; G4 P0.5 M5; G1 F3000.0 X42.788652 Y123.524713; M3 S3000; G1 F750.0 X34.239848 Y100.590852; G1 X51.368658 Y100.590852; G1 X42.788652 Y123.524713; G4 P0.5 M5; |
I had this issue too, so I cloned and edited this repo and added the power-on delay setting under "Advanced Settings" |
Hello again!
I use this extension with my 4xiDraw plotter. In my opinion it's the best software option by far.
The problem is that the pen-up/down mechanism is controlled by a micro-servo which is orders of magnitude slower than any laser device. The 0.92 extension had a nice power-on/off delay setting which stopped the carriage, waited for the pen to go up/down and then resumed the walking. Without this setting, this happens:
The dwell time before moving does not fill this condition. It adds the G4 commands in bad places for my situation.
A solution was adding
G4 P0.5
after m3 and m5 commands directly to the code. Gcode doesn't seem to recognize them when I add directly to the Tool Power/Off Command inputs, as they have to go inline in the code.I don't know if this extension is intended for plotter usage, but it fits my needs really well apart from this. Should I suggest a solution and make a pull request?
The text was updated successfully, but these errors were encountered: