I’ve just had a near-failure, because my Nomad tried to machine things at 5000rpm instead of 24000rpm.
This was one of multiple operations in G-Code generated from Fusion 360. Fusion normally sets 5000rpm for ramps, but then follows up with actual milling speed (24k in my case) soon afterwards.
For this one operation, however, my Nomad stuck at 5000, and I frantically rushed to lower the feed speed manually.
Everything went fine for the subsequent two operations, so it looks like the machine “missed” the S24000 command for some reason. How is that possible?
I checked the G-Code and every S5000 command is soon followed by S24000. Here’s an example:
It’s quite unlikely that the machine “missed” a command but not impossible if there are intermittent glitches on the serial line. But I would double-check the Fusion file first, it’s easy to forget to change the default 5000 RPM value. If you create custom tools you can set defaults to higher RPMs
@Julien I agree it is unlikely — I find the whole thing bizarre. That’s why I’m asking here.
I did check the generated G-Code (I can attach it if needed), because a mistake setting up operations is the first thing I thought of. But every S5000 (for ramping) is soon followed by S24000. And my machine clearly tried to perform the entire lengthy operation at 5000.
This happened only once — all my work before and after this was just fine.
I had this happen again and I’d really like to understand why it happens. I understand I can avoid this by setting all my ramp speeds to target speeds, but perhaps this is a debuggable problem?
Here is the complete G-Code. In the “Adaptive14” operation the spindle stayed at 5000rpm. I heard it and managed to save the job by frantically slowing down the feed rate manually. After this operation was completed, the rest of the code was processed normally.
Jan,
Everywhere it did not happen, you declared a spindle direction.(M03) I understand this is how the post is written but what happens if you insert spindle direction after spindle speed in “Adaptive14” ? Does it behave differently? Adaptive15 starts and stays at 24K and did not seem to give you any issue.