t-oster / VisiCut

A userfriendly tool to prepare, save and send Jobs to Lasercutters
https://visicut.org
Other
234 stars 115 forks source link

Engraving: Exporting of Laser Code(G-code) does not work when rastering #403

Closed Walkingrobot closed 7 years ago

Walkingrobot commented 7 years ago

I'm having troubles exporting g-code when engraving a job. (File -> export laser code) File is empty. If I use the execute function it does work.

Related to https://github.com/t-oster/VisiCut/issues/335

Using the latest release.

Thanks

t-oster commented 7 years ago

Hi. I tried it with the latest version and exporting of raster-code seems to work. But I tried it with a very small file and it took quite some time. I will look into it, maybe it is too slow for big files. Please try with a small rectangle.

Walkingrobot commented 7 years ago

I used the 20mm rectangle example. Same result.

Tested on: Windows 10, Debian Wheezy Lasercutter driver: Smoothieware Visicut version: 1.7-310 Workflow: 1.) File -> Example -> 20mm_rectangle 2.) Mapping -> engrave everything (Floyd-Steinberg) 3.) Power 20% en speed 100% 4.) File -> Export laser code => This result in gcode file with no rastering G-code, only startup g-codes.

Also tried importing the settings from Berlin fablab and using different laser cutter drivers, same result.

Generated Gcode: test.txt

Thanks !

t-oster commented 7 years ago

Is there any console output if you start visicut from command line?

Iliasb commented 7 years ago

Nothing special: Only this at startup =>

VisiCut.Linux: 1: VisiCut.Linux: Bad substitution VisiCut.Linux: 9: VisiCut.Linux: let: not found

My hack to make it work => pipe the generated output from the "execute button" into a gcode file sh VisiCut.Linux > output.gcode

This does work, but is not usable/user-friendly for most of our hackerspace users.

Thanks

t-oster commented 7 years ago

What is 1.7-310? Should be something like 1.7.9-6x please try with the latest version from http://download.visicut.org/develop

Walkingrobot commented 7 years ago

Fixed in version 1.7.9-6x (Develop branch) Broken in 1.7.310 (Master) ;)

Thanks