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

Support for Epilog FUSION #163

Open
drdavide opened this issue Jan 18, 2018 · 4 comments
Open

Support for Epilog FUSION #163

drdavide opened this issue Jan 18, 2018 · 4 comments
Labels
new-lasercutter Support a new lasercutter device

Comments

@drdavide
Copy link

I have read that VisiCut is compatible with Epilog ZING, MINI and HELIX. I want to use LibLaserCut for one of my project. Can I control also Epilog FUSION with VisiCut?

@mgmax
Copy link
Collaborator

mgmax commented Jan 20, 2018

Guessing from the Epilog driver and Job Manager output, and some network traces I could get from a test device, I can say the following:
The Fusion's command set is slightly different from the Helix. Slight modifications to the VisiCut code will be necessary. The eView integrated camera system will be possible somewhat tricky to implement with VisiCam, as it consists of two cameras and has some stupid network protocol.
Here are some scripts I wrote to get this information, and also further notes: https://github.com/mgmax/epilog-fusion-dataformat

I will definitely make all this work if/when we get a Epilog Fusion, which will be within this year with high (but not 100%) probability.

@Nos-
Copy link

Nos- commented Mar 19, 2018

Hi there.

I am using VisiCut with an Epilog Legend LaserCutter - many thanks for making VisiCut by the way.
Now I can make some tests on an Epilog Fusion too. But how to start?
Is the Fusion-series already supported?

@mgmax
Copy link
Collaborator

mgmax commented Mar 19, 2018

Start at the Helix or Legend code (whichever supports autofocus) and compare the output data of the Windows driver (print to file) with that of VisiCut. Then change the VisiCut output (Export Laser file) until it works (in doubt, until it is identical to what the Windows driver creates).

Some notes: https://github.com/mgmax/epilog-fusion-dataformat/blob/master/NOTES.txt
dump raw print to somewhat readable format: https://github.com/mgmax/epilog-fusion-dataformat/blob/master/dump-epilog-raw-print-file.py

@mgmax
Copy link
Collaborator

mgmax commented Sep 23, 2018

As my lab has decided to not buy an Epilog Fusion, I will not work on a driver for this machine.
First, you will need to make all small details work which are different from other machines (focus, specifying speed and power, ...).
Then the main chunk of work will be implementing spline support in LibLaserCut:

  • rewrite ShapeConverter to pass on splines (currently, there the path is converted to polyline with lots of LINETO commands)
  • add some fallback option so that a driver still receives a polyline if it doesn't understand splines
  • use the splines in the Fusion driver and send them to the lasercutter

@mgmax mgmax transferred this issue from t-oster/VisiCut Jul 16, 2020
@mgmax mgmax added the new-lasercutter Support a new lasercutter device label Sep 12, 2021
@mgmax mgmax changed the title Is VisiCut (and LibLaserCut) compatible with laser cutting machine Epilog FUSION? Support for Epilog FUSION Sep 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new-lasercutter Support a new lasercutter device
Projects
None yet
Development

No branches or pull requests

3 participants