[Feature Request] Creality K1 Max Lidar support

[mwLabs-eu]

Hi,

just got my new printer, using Orca Slicer on it is working fine. But is it also possible to use the Lidar from it for flow calibration? When using Creality Slicer it prints 4 zig-zag lines and scans. Can't find anything similar in Orca Slicer.

If it's not available, is there any chance, this can be implemented in the future?

Thanks for helping :)

[Myklt8]

AI camera support as well

[Ltek]

put [Feature Request] on the thread title

[mwLabs-eu]

Done 👍🏻

[squimito]

I also would like these features if possible

[LightningShark25]

Would also like to know if this is doable.
I'm running root access on k1 max. I'm not understanding where the limitation imposed by creality is - that feature only works with Creality Print - but why...? If anyone understands the mechanism on the interaction I'd be curious to understand it. It might help those looking at the feature

[Ltek]

according to this Creality post is maybe be accessible to Orca in the next FW update... https://www.reddit.com/r/crealityk1/comments/18wlsr7/upcoming_firmware_for_k1k1maxk1c/

[LightningShark25]

Thanks @Ltek that looks promising!
Do we think that feature will need to be added to the implementation of Orca to take advantage?
I'm not clear where the functionality is coded - is it a gcode macro that requires calling from the slicer perhaps?

[Ltek]

@SoftFever you aware of this announcement by Creality?

[Myklt8]

I can confirm that you can send the file from Orca to the K1 and then print with calibration from the printer screen... although it overrides KAMP. Now we just need to be able to activate it directly from the slicer

[Ltek]

I think we want KAMP to run before Lidar runs its calibration.

[virology2407]

The new firmware 1.3.3.5 was released today, and it specifically indicates lidar support for Orca. Would be nice to see the feature implemented.

[SaturnsVoid]

The LiDAR functions can only be used from the printers screen, You have to enable them in the Camera Settings, then when you go to print you have to print from the printers screen and make sure to enable the "Calibration" option. The features seem to be coded into the OS of the printer, can't seem to make it call it from gcode, it seems to overide the "START_PRINT" macro too.

[Ltek]

Creality made a point to tell everyone that FW 1.3.3.5 exposes LiDAR to Orca, Cura, etc... it likely does.

[Myklt8]

It does work, but you have to download and initiate the print from the screen. What people want is an option like creality slicer has for 1 click printing with the calibration (if you want it)

[virology2407]

@SaturnsVoid The panel does indeed support files sliced with Orca. In previous versions of the firmware, it would display an error code saying the LiDAR function (or motion advance, whatever it is Creality brands it as) wasn't supported for the file. That's one piece of the puzzle.

The missing piece, and the request here, is to be able to trigger the process from Orca. Creality Print has an option to calibrate the printer that triggers this process remotely. What I've been doing as a workaround is slicing in Orca, uploading the GCODE, and triggering the print from Creality Print with the calibrate option enabled. I'd like to be able to drop Creality Print completely.

[dwaite]

Creality expanded compatibility with third party sliced G-Code (and kinda comically fixed some support in Creality Print). They didn't add anything to trigger LIDAR or AI Camera features via Klipper/G-Code. When you submit a print through one of the official mechanisms, it coordinates running those features outside Klipper, I believe modifying the G-Code just enough to make it work (e.g. adding a stop after the first layer completes)

[kanishk619]

Since I wasn't able to find anything regarding this, I did my own digging and found that you can connect to port 9999 with websocket and trigger print with AI support. Upload the file to printer and then trigger using below command.

echo '{"method":"set","params":{"opGcodeFile":"printprt:/usr/data/printer_data/gcodes/filename_to_be_printed.gcode","enableSelfTest":1,"aiPausePrint":1,"aiDetection":1,"aiFirstFloor":1,"aiSw":1}}' | ./websocat.x86_64-unknown-linux-musl ws://printer.ip.address:9999

Please note that this is on my rooted K1 Max using guilouz script.
This works well with KAMP as well but need slicer start gcode changes like below

M140 S0
M104 S0
RESPOND TYPE=command MSG="Starting Adaptive Bed Mesh..."
BED_MESH_CLEAR
BED_MESH_CALIBRATE
BED_MESH_PROFILE SAVE=adaptive
BED_MESH_PROFILE LOAD=adaptive
START_PRINT EXTRUDER_TEMP=[nozzle_temperature_initial_layer] BED_TEMP=[bed_temperature_initial_layer_single]

Hope to see this added to Orca 😃

[Thrashin]

@kanishk619
I don't really understand the steps on how to enable this feature without touching the screen do you think you could explain a little more im a noobie when it comes to web sockets, and Ip and other coding things. im good with technology just not that good. if possible could you maybe make a video on the steps you took, because orca slicer team hasn't taken any steps into integrating this into orca. secondly does this solution make it automatically use the lidar when i click print and upload or do i have to enter the name of the file in web sockets every time.

[Ltek]

If Orca added this K series owners would be in love with Orca

[virology2407]

This is a huge find. Hopefully the Orca team can implement this. 

On June 28, 2024, GitHub ***@***.***> wrote: Since I wasn't able to find anything regarding this, I did my own digging and found that you can connect to port 9999 with websocket and trigger print with AI support. Upload the file to printer and then trigger using below command. echo '{"method":"set","params":{"opGcodeFile":"printprt:/usr/data/printer_data/gcodes/filename_to_be_printed.gcode","enableSelfTest":1,"aiPausePrint":1,"aiDetection":1,"aiFirstFloor":1,"aiSw":1}}' | ./websocat.x86_64-unknown-linux-musl ws://printer.ip.address:9999 Hope to see this added to Orca 😃

— Reply to this email directly, view it on GitHub <#3125 (comment)- 9904487>, or unsubscribe <https://github.com/notifications/unsubscribe- auth/ARDKQF3JE55QDWIPPBSNRTLZJVH2NAVCNFSM6AAAAABAVSXSRCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSMBUGQ4DO>. You are receiving this because you commented.Message ID: ***@***.***>

[dwaite]

Since this was originally opened, the Creality Print 5.x code base was released which is partially based on Orca. Have any interested parties evaluated the feasibility of a backport?