#<holes> = 3 - Unexpected behaviour

Hi all,

We are seeing some unexpected behaviour on our plasma cutter. I have attached the config settings file and a G-code program which behaves strangely. (We do see similar behaviour with other programs as well, but it a bit unpredictable.)

Let me try to explain what happens : When the first 2 slots are cut the torch moves to the first outside contour. During cutting that contour the velocity doesn't exceed 1700mm/min, which is 60% of the material feedrate (2815mm/min). But when it rounds the 4th (last corner) and enters the straight line all the sudden the velocity is at 100%, 2815mm/min. It does this on all 4 outside contours.

My best guess is that it has something to do with the M67 commands which QtPlasmaC adds, but why it is not consistent is beyond my expertise or comprehension. Anybody with thoughts ?

Cheers, Peter

 

Just to add to the previous : when I use conversational to generate the same contour the sudden feedrate change at the last straight line doesn't occur. But when I add "#<holes> = 3" to the conversational program the velocity is simply 60% of the feedrate all around the contour. Got me stumped.

Hi Phil,

I increased the MAX_ACCELERATION values but no difference, same behaviour.

Cheers, Peter

Hi Phil,

I can only get this far, see screenshot attached. No menu opening up to pick a sim configuration ?

Hi Phil,

Somehow I have a sim configuration, but it throws an error on opening, see image attached. Sorry, I have no experience with sim configurations at all

Hi Phil,

It seems having to do with missing "M190" and this section in the ini file :
[RS274NGC]
RS274NGC_STARTUP_CODE = G21 G40 G49 G80 G90 G92.1 G94 G97 M52P1
PARAMETER_FILE = metric_parameters.txt
SUBROUTINE_PATH = ./:../../nc_files
USER_M_PATH = ./:../../nc_files/plasmac/m_files

But that's as far as I can get ?