Gcode with "ANaN.0" - missing settings?

primozk · March 13, 2025, 7:17am

Hi, after a while (will be a year probably) i’m again preparing some milling for my cnc.

I generated the gcode and have seen there is the “A” postion as well in the code and in all my code as “ANaN.0”. I wonder is this a valid code or i’m missing some settings for the “A”, or to disable? I did not try the code on the router yet - asking in advance.

G21
G90
G0 X56.5413 Y126.2218 F4000
G0 Z5.0 ANaN.0 F400
G1 Z-0.3236 ANaN.0 F150
G1 X57.1046 Y125.9740 ANaN.0 F1600
G1 X57.6778 Y125.7511 ANaN.0
G1 X58.2601 Y125.5534 ANaN.0

Tnx for the advice

Forecaster · March 13, 2025, 8:01am

Can you export and upload your workspace?

It seems you have a missing or invalid value somewhere that is causing a NaN (Not a Number) error in the coordinate calculation.

TKnapton · March 13, 2025, 11:35am

I’ve been using my CNC router all week, and then today have started having the same problem - despite all settings remaining the same, all my G-code is now being exported with ANaN on every line.

It also stops the code from running.

Forecaster · March 13, 2025, 12:03pm

Could you try reverting to the previous version and exporting the g-code and see if it still happens?

stewart · March 13, 2025, 12:12pm

if you use files --> export to produce a .kmz file and email it to me I can take a look … [ sa at grid dot space ]

primozk · March 13, 2025, 1:11pm

workspace_Vratca_elektrika_vB1(3) (1).kmz (661.2 KB)

Here, the kmz & thanks for looking

stewart · March 13, 2025, 1:13pm

this bug is fixed in production with KM 4.1.4

TKnapton · March 13, 2025, 1:32pm

Works great, thank you.

primozk · March 14, 2025, 6:42am

Same here, thanks for the quick fix Stewart!

Daniel_Roitman · December 22, 2025, 1:16pm

Hi everyone,

I’m new to Kiri:Moto and really excited about using it for my CNC projects, but I’m running into an issue that’s stalling me.

My .mzk file

thanks all

stewart · December 22, 2025, 2:59pm

Hi Daniel,

I’m tracking down a bug in the CPU based contouring code that seems to cause this. In the meantime, please try enabling GPU acceleration since that uses a new code path for contouring that doesn’t have this issue.

Daniel_Roitman · December 22, 2025, 5:16pm

Hi Stewart,

Thank you very much for the information. It solved my problem.