You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just encountered a Problem with my GRBL & Universal-G-Code-Sender - Setup:
my gcode had float values with 20 decimal places, resulting in lines longer then GRBL could handle, this made my Machining operation 'bad' without throwing a Error.
It would be very helpfull if the G-Code-Sender had a Option to round the float values that are being sent to the GRBL setting of 'decimal-places' or maybe a fixed number of decimals.
I currently just use the following regex to cut exessive decimals: match:
([xXyYzZfFiIjJ]{1})\s_([-]{0,1})\s_(\d+).(\d{0,4})\d+
replace by:
$1$2$3.$4
The text was updated successfully, but these errors were encountered:
I just encountered a Problem with my GRBL & Universal-G-Code-Sender - Setup:
It would be very helpfull if the G-Code-Sender had a Option to round the float values that are being sent to the GRBL setting of 'decimal-places' or maybe a fixed number of decimals.
I currently just use the following regex to cut exessive decimals:
match:
([xXyYzZfFiIjJ]{1})\s_([-]{0,1})\s_(\d+).(\d{0,4})\d+
replace by:
$1$2$3.$4
The text was updated successfully, but these errors were encountered: