search

grblHAL / Plugins_laser

grblHAL laser plugins
Other
4 stars 1 forks source link

How to test cluster mode ? #2

Closed drom89 closed 2 years ago

drom89 commented 2 years ago

Hi, i have problem (as always :) ).

So i generate gcode in LB with clusters under Smoothieware device preset, but i cant test it out. LB is not communicating with grbl if i set Smoothieware device.

When i try to load it to iosender, i need to check every row by pressing OK image

[VER:1.1f.20220928:] [OPT:VNMSL,35,1024,3,0] Target buffer size found [AXS:3:XYZ] [NEWOPT:ENUMS,RT+,REBOOT,TC,SED,RTC] [FIRMWARE:grblHAL] [NVS STORAGE:*FLASH] [DRIVER:ESP32] [DRIVER VERSION:220922] [DRIVER OPTIONS:v4.3.4] [BOARD:MKS DLC32 2.0]

drom89 commented 2 years ago

Ok, i just found out, that i can test it with Candle, i will try it out. https://github.com/grblHAL/core/discussions/195

terjeio commented 2 years ago

You have not enabled the cluster plugin...

And you may have to change an option in the plugin if you do not have the latest (beta?) version of LightBurn? The S-values are less than or equal to 0 if you need to do that (it seems so from the error message above).

drom89 commented 2 years ago

You have not enabled the cluster plugin...

Yep i just added #define LB_CLUSTERS_ENABLE 1 to my_machine.h

And you may have to change an option in the plugin if you do not have the latest (beta?) version of LightBurn? The S-values are less than or equal to 0 if you need to do that (it seems so from the error message above).

I have version 1.2.01 latest normal version. will try it out, thanks.

drom89 commented 2 years ago

https://forum.lightburnsoftware.com/t/cluster-mode-for-grblhal/77711

Little bit info from LB staff

It has actually been enabled for the next release (1.2.02) already, and Ortur has added support to it for their firmware, and so has Tim Rothman.

Cluster on G code devices has also been set up to allow up to 16 brightness values per cluster, and it looks for [CLUSTER:xx] as a response to the $I command. If it sees that response, it pulls the number out of the argument there, and uses that as the cluster size, clamped to be a value between 1 and 16.

Oz (Lead Dev/Owner) actually replied to that thread on LaserGRBL’s github - however left the chat once it devolved into implementing full image processing on the controllers