[Feature Request] CV Laser Support about ender3v2s1 HOT 17 CLOSED

I think the first modification is to allow Z-Homing without the BL-Toutch and insted use the Z-Linmit switch.

I don't think Z-homing is important for the laser since you need to do it manually depending upon the height of the item that you're cutting/engraving so it definitely shouldn't try to use a limit switch. When homing using the Creality laser firmware it only homes on X/Y.

You're right. At the time writing this, I don't have enough experience with it.
I was thinking the additional Z-end stop is for the Laser Head.
But I'm still working on this.

from ender3v2s1.

Hi @aydevosotros ,
that is right. To save some space, you can disable some UI features.

from ender3v2s1.

Hi, thank you for your feature request. Currently, adding support for the Laser unit to Professional Firmware requires some work and time. I hope that someone can do a pull request adding this feature. I don't have an S1 and not a Laser Engraver to test, so for me it could be a little difficult to give a firmware with the tests that I expect.

from ender3v2s1.

Hi, I try my best to get this done. I Have a S1 and also the CV Laser module. Have you some starting point for me?
I think the first modification is to allow Z-Homing without the BL-Toutch and insted use the Z-Linmit switch.

from ender3v2s1.

The Sources for the official firmware with laser module are here: https://github.com/CrealityOfficial/Ender-3S1/tree/ender-3s1-lasermodel
We must port the Laser code without affecting the core Marlin code.

from ender3v2s1.

Also you can check here: https://github.com/mriscoc/Marlin_Configurations/issues/2

from ender3v2s1.

I will digg deeper in this topic.
Can you explain, how I change the machine type in the Marlin auto build tool?
I think I was building for the wrong Machine.

from ender3v2s1.

I will digg deeper in this topic. Can you explain, how I change the machine type in the Marlin auto build tool? I think I was building for the wrong Machine.

You must copy the correct configuration files, from the Configuration folder to Marlin Folder.

from ender3v2s1.

I see, but what are the diference between the xfer, maple and none?
And also the 256K and 512K?
I build the STM32F103RE_creality (512K) and sucessfully installed to the board.
Now I'am working on the port.
Thanks.

from ender3v2s1.

For the S1 use the STM32F103RC_creality (that depends on the type of chip that your control board has)

from ender3v2s1.

I think the first modification is to allow Z-Homing without the BL-Toutch and insted use the Z-Linmit switch.

I don't think Z-homing is important for the laser since you need to do it manually depending upon the height of the item that you're cutting/engraving so it definitely shouldn't try to use a limit switch. When homing using the Creality laser firmware it only homes on X/Y.

from ender3v2s1.

Hi there! I'd like to deep into the topic. I've been working into porting the code from the original repo but I'm getting this issue when compiling. I don't know if someone can give me a tip for it:

For what I understand it means that the code does not fit into the board memory but it doesn't make much sense for me since I didn't add much code at this point. Am I missing something?

from ender3v2s1.

The STM32F4 boards have a large bootloader, so the program memory space is shorter than others boards.

from ender3v2s1.

I, too, am interested in laser support. What all would have to be removed from the Ender3S1-F4-UBL firmware to make room for laser support? How thin are we on space? Do we have laser code readily able to to be combined into a build?

from ender3v2s1.

Preliminary laser support is being discussed here: #62

from ender3v2s1.

This issue has had no activity in the last 60 days. Please add a reply if you want to keep this issue active, otherwise it will be automatically closed within 10 days.

from ender3v2s1.

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

from ender3v2s1.