[FR] laser control for the Mega Pro #49

Closed
opened 2021-01-07 17:45:35 -06:00 by hp-pepster · 37 comments
hp-pepster commented 2021-01-07 17:45:35 -06:00 (Migrated from github.com)

Hi,

are there any plans to work on the laser control of the new Mega Pro? If so, how is the progress? I might be of help as I digged a little bit through the source code from Anycubic for the Mega Pro.

Hi, are there any plans to work on the laser control of the new Mega Pro? If so, how is the progress? I might be of help as I digged a little bit through the source code from Anycubic for the Mega Pro.
knutwurst commented 2021-01-08 01:31:55 -06:00 (Migrated from github.com)

Hi,
I don't see any mega pro sourcecode on github fron anycubic. Do you have a link? If so, I'll do my best to implement the laser functionality asap <3

Hi, I don't see any mega pro sourcecode on github fron anycubic. Do you have a link? If so, I'll do my best to implement the laser functionality asap <3
hp-pepster commented 2021-01-08 04:55:28 -06:00 (Migrated from github.com)

It's not on github (yet), but a user posted it on thingiverse. As it's marlin-based, which is GPL3, anycubic has to give out the source. Link to the source: https://www.thingiverse.com/groups/anycubic-i3-mega-pro

The laser-part is very "interesting" implemented. As far as I've seen the relevant parts are in Marlin_main.cpp functions:
void Read_BMP(unsigned char* gray, unsigned int y, unsigned int x)
void Laset_print_picture(void)
void prepare_laser_print()

Maybe something in temperature.cpp is relevant as well.

I tried to describe the functionality as far as I understood it here: https://drucktipps3d.de/forum/topic/steuerung-laser-anycubic-mega-pro/?part=4#postid-131852 . But honestly, the code gave me an headache. Have a look at the Backup-Folder in the source for example :-) , so I might be completely mistaken.

There are some other code parts regarding the laser. One is for a basic gcode-control inline void gcode_G6() and the rest is for the display I think.

As other users mentioned before one has to fake the temp sensor on the nozzle with a resistor, otherwise the printer complains about a strange temperature of 0 °C (see https://drucktipps3d.de/forum/topic/steuerung-laser-anycubic-mega-pro/?part=2#postid-126858 )

Let me know if I can support you. Unfortunately I don't have the Mega Pro yet but I hope to receive it soon.

It's not on github (yet), but a user posted it on thingiverse. As it's marlin-based, which is GPL3, anycubic has to give out the source. Link to the source: https://www.thingiverse.com/groups/anycubic-i3-mega-pro The laser-part is very "interesting" implemented. As far as I've seen the relevant parts are in `Marlin_main.cpp` functions: `void Read_BMP(unsigned char* gray, unsigned int y, unsigned int x)` `void Laset_print_picture(void)` `void prepare_laser_print()` Maybe something in `temperature.cpp` is relevant as well. I tried to describe the functionality as far as I understood it here: https://drucktipps3d.de/forum/topic/steuerung-laser-anycubic-mega-pro/?part=4#postid-131852 . But honestly, the code gave me an headache. Have a look at the Backup-Folder in the source for example :-) , so I might be completely mistaken. There are some other code parts regarding the laser. One is for a basic gcode-control `inline void gcode_G6()` and the rest is for the display I think. As other users mentioned before one has to fake the temp sensor on the nozzle with a resistor, otherwise the printer complains about a strange temperature of 0 °C (see https://drucktipps3d.de/forum/topic/steuerung-laser-anycubic-mega-pro/?part=2#postid-126858 ) Let me know if I can support you. Unfortunately I don't have the Mega Pro yet but I hope to receive it soon.
knutwurst commented 2021-01-08 05:08:26 -06:00 (Migrated from github.com)

Wow! Thank you very much! That's probably the dirtiest and hackiest code I've ever seen but it looks very promising!

I'll dig into it and let you know what I found out so far and if I could implement the laser functionality. Sadly I don't have Mega P to test it :/

Wow! Thank you very much! That's probably the dirtiest and hackiest code I've ever seen but it looks very promising! I'll dig into it and let you know what I found out so far and if I could implement the laser functionality. Sadly I don't have Mega P to test it :/
hp-pepster commented 2021-01-08 05:23:18 -06:00 (Migrated from github.com)

I have to thank you :-)

As soon as I get mine I can test your code.

I have to thank you :-) As soon as I get mine I can test your code.
Wirelessless commented 2021-01-25 07:56:23 -06:00 (Migrated from github.com)

Hi!
Thank you for your hard work!
I just got the Mega Pro with the LCD displaying V1.2.9 firmware and I can confirm that using the G6 command with S1-S100 turns the laser on full power and ignores any power setting (various forums suggest otherwise). I used a GCODE sequence that draws 6 different boxes at different power levels (S1-S10-S20-S30-S40-S50) and all cut the paper in the same way,
I am a little hesitant to keep using it like this as it might affect the lifespan of the laser.
I hope to see laser power support for the Mega Pro in a future release of your firmware.
Please let me know if I there is a release I can test!

Hi! Thank you for your hard work! I just got the Mega Pro with the LCD displaying V1.2.9 firmware and I can confirm that using the G6 command with S1-S100 turns the laser on full power and ignores any power setting (various forums suggest otherwise). I used a GCODE sequence that draws 6 different boxes at different power levels (S1-S10-S20-S30-S40-S50) and all cut the paper in the same way, I am a little hesitant to keep using it like this as it might affect the lifespan of the laser. I hope to see laser power support for the Mega Pro in a future release of your firmware. Please let me know if I there is a release I can test!
sims-60 commented 2021-02-05 04:40:46 -06:00 (Migrated from github.com)

Hi
@knutwurst are there any updates about the Laser?

Hi @knutwurst are there any updates about the Laser?
knutwurst commented 2021-02-18 06:58:30 -06:00 (Migrated from github.com)

Nope. Sorry but I'll update the thread and the readme when it's done.

Nope. Sorry but I'll update the thread and the readme when it's done.
github-actions[bot] commented 2021-03-20 21:09:24 -05:00 (Migrated from github.com)

This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days.

This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days.
0o0will0o0 commented 2021-03-20 21:16:35 -05:00 (Migrated from github.com)

I believe this issue is still relevant and warrants attention due to this firmware being the best alternative I have found in comparison to anycubic's effort for the Ai3M Pro. I believe if piezoelectric leveling and/or laser control functionality is added, it would add immense value to this printer and I'd happily donate more to the project if an update came for these features

I believe this issue is still relevant and warrants attention due to this firmware being the best alternative I have found in comparison to anycubic's effort for the Ai3M Pro. I believe if piezoelectric leveling and/or laser control functionality is added, it would add immense value to this printer and I'd happily donate more to the project if an update came for these features
sims-60 commented 2021-03-27 06:38:51 -05:00 (Migrated from github.com)

hi @knutwurst are there any updates about the laser?

hi @knutwurst are there any updates about the laser?
knutwurst commented 2021-03-27 13:17:38 -05:00 (Migrated from github.com)

HI @sims-60 , thank you very much, but I already have the original MEGA Pro firmware laying around ;)
Take a look at my current sourcecode. The Laser is already prepared ;)

HI @sims-60 , thank you very much, but I already have the original MEGA Pro firmware laying around ;) Take a look at my current sourcecode. The Laser is already prepared ;)
knutwurst commented 2021-03-27 13:23:30 -05:00 (Migrated from github.com)

Thanks a lot. I'll come back to you when I have any updates :)

Thanks a lot. I'll come back to you when I have any updates :)
0o0will0o0 commented 2021-03-27 16:50:28 -05:00 (Migrated from github.com)

Is there any way to get the piezo leveling to function like the original firmware?

Is there any way to get the piezo leveling to function like the original firmware?
hp-pepster commented 2021-04-22 05:21:58 -05:00 (Migrated from github.com)

Hi, my printer also arrived (I guess). As soon as I'm home again I could start testing. @knutwurst Are you planing to work on the laser any time soon? If you are interested I could have a look at you commits regarding the laser and help with some coding.

Hi, my printer also arrived (I guess). As soon as I'm home again I could start testing. @knutwurst Are you planing to work on the laser any time soon? If you are interested I could have a look at you commits regarding the laser and help with some coding.
github-actions[bot] commented 2021-05-23 21:40:42 -05:00 (Migrated from github.com)

This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days.

This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days.
github-actions[bot] commented 2021-06-27 21:10:29 -05:00 (Migrated from github.com)

This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days.

This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days.
knutwurst commented 2021-06-29 01:20:14 -05:00 (Migrated from github.com)

The Chiron Support is finally done and now I'll take a look at the Mega Pro Laser ;)

The Chiron Support is finally done and now I'll take a look at the Mega Pro Laser ;)
InoxDragoon commented 2021-07-10 23:01:20 -05:00 (Migrated from github.com)

I'm also interested in getting the laser to work on Marlin 2.x. I'm planning on upgrading to your firmware soon, so please keep up the good work!

FYI: You can get the laser from Anycubic's website to "upgrade" to a P. the Mega S and the P are the same machine, just the P comes with the Laser.

I'm also interested in getting the laser to work on Marlin 2.x. I'm planning on upgrading to your firmware soon, so please keep up the good work! FYI: You can get the laser from Anycubic's website to "upgrade" to a P. the Mega S and the P are the same machine, just the P comes with the Laser.
github-actions[bot] commented 2021-08-10 21:04:50 -05:00 (Migrated from github.com)

This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days.

This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days.
knutwurst commented 2021-08-16 01:03:34 -05:00 (Migrated from github.com)

Reopened, because it's not done yet ;)

Reopened, because it's not done yet ;)
aman-tiwari commented 2021-08-16 22:29:47 -05:00 (Migrated from github.com)

Hi!
Thank you for your hard work!
I just got the Mega Pro with the LCD displaying V1.2.9 firmware and I can confirm that using the G6 command with S1-S100 turns the laser on full power and ignores any power setting (various forums suggest otherwise). I used a GCODE sequence that draws 6 different boxes at different power levels (S1-S10-S20-S30-S40-S50) and all cut the paper in the same way,
I am a little hesitant to keep using it like this as it might affect the lifespan of the laser.
I hope to see laser power support for the Mega Pro in a future release of your firmware.
Please let me know if I there is a release I can test!

EDIT:
I skimmed the source code, it looks like there is no PWM laser power control in the raster engraving functionality! They use the heater pin to turn on/off the laser, and just stop at each pixel for f(grayscale value of pixel) cycles.
Relevant snippet:

for(j=0;j<x_max;j++)
{
  Read_BMP(&Y,i,x_max-j);
  if( Y>MIN_GRAY_VLAUE&&j!=0 ) 
{								 
    if(Laser_printer_st.pic_x_mirror==1)
    destination[X_AXIS]=x_end+j*Laser_printer_st.pic_pixel_distance;
    else
    destination[X_AXIS]=x_end-j*Laser_printer_st.pic_pixel_distance;									 
    line_to_destination(ftemp);
    set_current_to_destination();
    while (planner.blocks_queued());
    WRITE(HEATER_0_PIN, 1);
  if(Laser_printer_st.pic_vector==0)
  {
    time = Y*Laser_printer_st.pic_laser_time;
    while(time--)
    {
    WRITE(HEATER_0_PIN, 1); 
    }
    WRITE(HEATER_0_PIN, 0);
  }
... some screen stuff

Interestingly, it contains some unfinished code for vector engraving functionality (the above if(Laser_printer_st.pic_vector==0) doesn't have a corresponding else).

Previously below I wrote:

It could be that one of the fan PWM commands is used to control the laser: https://www.youtube.com/watch?v=1cyZCpfglAg, https://marlinfw.org/docs/configuration/laser_spindle.html
I just got my Mega Pro, I'll give some of those sequences a try after I get it set up

> > > Hi! > Thank you for your hard work! > I just got the Mega Pro with the LCD displaying V1.2.9 firmware and I can confirm that using the G6 command with S1-S100 turns the laser on full power and ignores any power setting (various forums suggest otherwise). I used a GCODE sequence that draws 6 different boxes at different power levels (S1-S10-S20-S30-S40-S50) and all cut the paper in the same way, > I am a little hesitant to keep using it like this as it might affect the lifespan of the laser. > I hope to see laser power support for the Mega Pro in a future release of your firmware. > Please let me know if I there is a release I can test! EDIT: I skimmed the source code, it looks like there is no PWM laser power control in the raster engraving functionality! They use the heater pin to turn on/off the laser, and just stop at each pixel for `f(grayscale value of pixel)` cycles. Relevant snippet: ```cpp for(j=0;j<x_max;j++) { Read_BMP(&Y,i,x_max-j); if( Y>MIN_GRAY_VLAUE&&j!=0 ) { if(Laser_printer_st.pic_x_mirror==1) destination[X_AXIS]=x_end+j*Laser_printer_st.pic_pixel_distance; else destination[X_AXIS]=x_end-j*Laser_printer_st.pic_pixel_distance; line_to_destination(ftemp); set_current_to_destination(); while (planner.blocks_queued()); WRITE(HEATER_0_PIN, 1); if(Laser_printer_st.pic_vector==0) { time = Y*Laser_printer_st.pic_laser_time; while(time--) { WRITE(HEATER_0_PIN, 1); } WRITE(HEATER_0_PIN, 0); } ... some screen stuff ``` Interestingly, it contains some unfinished code for vector engraving functionality (the above ` if(Laser_printer_st.pic_vector==0)` doesn't have a corresponding else). Previously below I wrote: >It could be that one of the fan PWM commands is used to control the laser: https://www.youtube.com/watch?v=1cyZCpfglAg, https://marlinfw.org/docs/configuration/laser_spindle.html I just got my Mega Pro, I'll give some of those sequences a try after I get it set up
mlewis-everley commented 2021-08-18 04:58:06 -05:00 (Migrated from github.com)

It's probably not of any help, but I noticed that some commands in marlin support a laser as well (eg: https://marlinfw.org/docs/gcode/M003.html)

I also noticed some other standard commands seem to also support a laser as well.

Just wondering if this is how laser support is intended to be added, or are we still going to have to do the weird BMP thing?

It's probably not of any help, but I noticed that some commands in marlin support a laser as well (eg: https://marlinfw.org/docs/gcode/M003.html) I also noticed some other standard commands seem to also support a laser as well. Just wondering if this is how laser support is intended to be added, or are we still going to have to do the weird BMP thing?
knutwurst commented 2021-09-17 01:54:29 -05:00 (Migrated from github.com)

Unfortunately, since I don't have a laser, I can't test the Marlin features.

Actually, I wanted to recreate exactly the anycubic feature so that the original display would continue to work.

That's why I recreated the auto leveling for the Chiron instead of just using Marlin features.

Unfortunately, since I don't have a laser, I can't test the Marlin features. Actually, I wanted to recreate exactly the anycubic feature so that the original display would continue to work. That's why I recreated the auto leveling for the Chiron instead of just using Marlin features.
stklcode commented 2021-10-02 13:31:01 -05:00 (Migrated from github.com)

I do own a Mega Pro and tried a first step towards the laser.

The wiring is (mis)using the hotend heater pins (A1, A2) for the laser power.

Setting a target temperature results in Error:MINTEMP triggered, system stopped! Heater_ID: 0

Simulating an arbitrary temperature with a resistor between A6/7 (see linked post above) enables laser control with M104 S0 (target temperature 0 = off) and a value greater current temperature enabled the PWM output.
In my case, the simulated temperature is 37.24°C, so with M104 S38 it starts with ~4Hz and ramps up with higher values. S37 or below makes the laser stop.

So with real ugly G-code sequences I was able to do some laser engraving in stock KW 1.3.1 firmware.

That's exactly what's represented in the disabled code fragments, e.g. WRITE(HEATER_0_PIN, 0).


There is obviously some work to do for the code fragments. Reordering and some declarations eventually makes it compiling, but not working.

#if ENABLED(KNUTWURST_MEGA_P)
  #define LASER_FEATURE
  #define SPINDLE_LASER_PWM_PIN HEATER_0_PIN
#endif

results in failing sanity check

Marlin/src/HAL/shared/../../inc/SanityCheck.h:2768:8: error: #error "SPINDLE_LASER_PWM_PIN conflicts with E0_AUTO_FAN_PIN."

Seems obvious, as the pin is used for both functions...

Are there any (unpublished) updates on the laser code fragments to build on or do I have to start off from the current master branch to - maybe - get it working?
(doen't seem to be too complex, but I've never worked with Marlin code til an hour ago)

I do own a Mega Pro and tried a first step towards the laser. The wiring is (mis)using the hotend heater pins (A1, A2) for the laser power. Setting a target temperature results in _Error:MINTEMP triggered, system stopped! Heater_ID: 0_ Simulating an arbitrary temperature with a resistor between A6/7 (see linked post above) enables laser control with `M104 S0` (target temperature 0 = off) and a value greater current temperature enabled the PWM output. In my case, the simulated temperature is 37.24°C, so with ` M104 S38` it starts with ~4Hz and ramps up with higher values. `S37` or below makes the laser stop. So with real ugly G-code sequences I was able to do some laser engraving in stock KW 1.3.1 firmware. That's exactly what's represented in the disabled code fragments, e.g. `WRITE(HEATER_0_PIN, 0)`. ---- There is obviously some work to do for the code fragments. Reordering and some declarations eventually makes it compiling, but not working. ```cpp #if ENABLED(KNUTWURST_MEGA_P) #define LASER_FEATURE #define SPINDLE_LASER_PWM_PIN HEATER_0_PIN #endif ``` results in failing sanity check > Marlin/src/HAL/shared/../../inc/SanityCheck.h:2768:8: error: #error "SPINDLE_LASER_PWM_PIN conflicts with E0_AUTO_FAN_PIN." Seems obvious, as the pin _is_ used for both functions... Are there any (unpublished) updates on the laser code fragments to build on or do I have to start off from the current _master_ branch to - maybe - get it working? (doen't seem to be too complex, but I've never worked with Marlin code til an hour ago)
stklcode commented 2021-10-04 11:35:36 -05:00 (Migrated from github.com)

Update:
Got the laser working with barely minimal changes to my Marlin 2.0.9 branch:
(branch stklcode@feature/laser, commit d63b238a2e)

It's now merged into the master branch: a16109379e

This does not yet feature display support, but it enables Marlin M003 G-Code support M3 S0 to M3 S254. Working nicely on my Mega P.

Unfortunately a trivial backport does not work. Maybe I just missed something or should have reloaded settings... Just spent ~10s of testing with the old branch.

**Update:** Got the laser working with barely minimal changes ~to my Marlin 2.0.9 branch: (branch [stklcode@feature/laser](https://github.com/stklcode/Marlin-2-0-x-Anycubic-i3-MEGA-S/tree/feature/laser), commit https://github.com/stklcode/Marlin-2-0-x-Anycubic-i3-MEGA-S/commit/d63b238a2efdad3b5f2804048687e8fe462941f8)~ It's now merged into the master branch: https://github.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/commit/a16109379e901c2757b616c0b712ad4a5afd08f6 This does not yet feature display support, but it enables Marlin [M003](https://marlinfw.org/docs/gcode/M003.html) G-Code support `M3 S0` to `M3 S254`. Working nicely on my Mega P. Unfortunately a trivial backport does not work. Maybe I just missed something or should have reloaded settings... Just spent ~10s of testing with the old branch.
nilsacht commented 2021-10-29 03:06:56 -05:00 (Migrated from github.com)

Hi,

i own a Mega Pro now for one Week and I am very happy with this firmware. I wanted to test the Laser and found this topic.

Is there any progress in Laser functionality? Is it possible to use the Laser soon? Or is it possible to store my settings (e.g. mesh leveling), install original firmware, laser something, install this firmware and restore my settings?

Thanks.

Hi, i own a Mega Pro now for one Week and I am very happy with this firmware. I wanted to test the Laser and found this topic. Is there any progress in Laser functionality? Is it possible to use the Laser soon? Or is it possible to store my settings (e.g. mesh leveling), install original firmware, laser something, install this firmware and restore my settings? Thanks.
knutwurst commented 2021-10-29 03:08:49 -05:00 (Migrated from github.com)

Hi,
since the original firmware doesn't use the EEPROM at all, you can switch back and forth as you like ;)
Currently there is no progress in the laser development.. sorry :/

Olli

Hi, since the original firmware doesn't use the EEPROM at all, you can switch back and forth as you like ;) Currently there is no progress in the laser development.. sorry :/ Olli
nilsacht commented 2021-10-29 03:14:09 -05:00 (Migrated from github.com)

So i can install the original firmware, use the laser, install your firmware and my mesh leveling is still set up? That would by nice.

So i can install the original firmware, use the laser, install your firmware and my mesh leveling is still set up? That would by nice.
knutwurst commented 2021-10-29 03:16:40 -05:00 (Migrated from github.com)

Yes, that should work.
I do it by myself and also switch to klipper and back to my firmware. The settings are still stored :)

Yes, that should work. I do it by myself and also switch to klipper and back to my firmware. The settings are still stored :)
knutwurst commented 2021-11-02 08:05:33 -05:00 (Migrated from github.com)

Laser Support added in Release 1.4.1 Beta 1

Thank you so much @stklcode !

Laser Support added in [Release 1.4.1 Beta 1](https://github.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/releases) Thank you so much @stklcode !
stklcode commented 2021-11-02 09:05:44 -05:00 (Migrated from github.com)

Is "rudimentary" really the correct term here?

Fair to say, the Anycubic features are not yet supported. This requires some work in the TFT routine, so you can't "print" bitmaps from SD.

But unlike the (misused) G6 command of the stock FW the laser is dimmable with M3. (at least on my printer 1-255 were all the same intensity, so basically it's on/off). Good enough for use with lightburn or similar software in the current state.

So, it's a different implementation.

Is "rudimentary" really the correct term here? Fair to say, the Anycubic features are not yet supported. This requires some work in the TFT routine, so you can't "print" bitmaps from SD. But unlike the (misused) G6 command of the stock FW the laser is dimmable with M3. (at least on my printer 1-255 were all the same intensity, so basically it's on/off). Good enough for use with lightburn or similar software in the current state. So, it's a different implementation.
knutwurst commented 2021-11-02 09:13:19 -05:00 (Migrated from github.com)

Is "rudimentary" really the correct term here?

You're right. Your work makes it possible to use the laser in the first place. Rudimentary was more related to the entire anycubic-related implementation. In the case of the Chiron, I called "can print and level, but the display doesn't work yet" also "rudimentary".

That should in no way reduce the value of your work and I would like to buy you a coffee ;)

> Is "rudimentary" really the correct term here? You're right. Your work makes it possible to use the laser in the first place. Rudimentary was more related to the entire anycubic-related implementation. In the case of the Chiron, I called "can print and level, but the display doesn't work yet" also "rudimentary". That should in no way reduce the value of your work and I would like to buy you a coffee ;)
stklcode commented 2021-11-02 10:08:25 -05:00 (Migrated from github.com)

I am not offended in any way, should have places a 😉 maybe.

Let’s see if we can get the not so straight-forward part for the built-in feature. I’ve seen the code snippets, but focused on the Marlin part to get any light out of it first place.

We should drink the coffee together. Likely never have started playing with the code without your prior work.

I am not offended in any way, should have places a 😉 maybe. Let’s see if we can get the not so straight-forward part for the built-in feature. I’ve seen the code snippets, but focused on the Marlin part to get any light out of it first place. We should drink the coffee together. Likely never have started playing with the code without your prior work.
knutwurst commented 2021-11-02 10:25:06 -05:00 (Migrated from github.com)

The marlin part is a pretty good start and when everything else works, connecting the display shouldn't be a problem. Maybe wen can reuse the anycubic bitmap parsing code to feed the marlin implementation.

The marlin part is a pretty good start and when everything else works, connecting the display shouldn't be a problem. Maybe wen can reuse the anycubic bitmap parsing code to feed the marlin implementation.
stklcode commented 2021-11-03 13:27:02 -05:00 (Migrated from github.com)

Started working on the integration based on the 1.2.9 sources that have been partially ported already: stklcode@feature/anycubic-laser

It compiles, but it completely untested so far. But no need to start from scratch, if anyone wants to join development.

Started working on the integration based on the 1.2.9 sources that have been partially ported already: [stklcode@`feature/anycubic-laser`](https://github.com/stklcode/Marlin-2-0-x-Anycubic-i3-MEGA-S/tree/feature/anycubic-laser) It compiles, but it completely untested so far. But no need to start from scratch, if anyone wants to join development.
github-actions[bot] commented 2021-12-03 20:07:59 -06:00 (Migrated from github.com)

This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days.

This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days.
github-actions[bot] commented 2022-02-07 08:12:47 -06:00 (Migrated from github.com)

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.

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.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wp/Marlin-2-0-x-Anycubic-i3-MEGA-S#49
No description provided.