Machsupport Forum
Mach Discussion => General Mach Discussion => Topic started by: fixittt on October 05, 2007, 04:20:40 PM
-
I had an issue this morning with my mill missing steps. When I ran a specific code it ran like dog snot. Missed steps sounded ugly ect. I tried running a code I knew that worked and it ran fine. Went back to my other code....... crappy. Rebooted, re-ran.... ugly still.
I noticed that the problem code was 22 + meg in size. changed to peramiters and got it down to 12 meg and now its running fine. My first though was a computer issue so I ran the signal test in mach. No spikes.
Is there an issues with large g-codes? Something I need to know about?
The computer is an AMD 2100+ with 1 gig of DDR ram.
I run lots of large code and would like to head this issue off now, rather then when I need something. I machine wax so I know that its not a material hardness issue. Even when running the code at 50% feedrate the motors stalled and sounded just bad!
Any Ideas?
-
Might be the graphics on your PC choking. What do you use for Graphics? Is it onboard or do you have a graphics card? If so, do you have the specs? The only other thing I can think of right off is something in your file that Mach doesn't like. What did you change to get the file to half size?
Brett
-
the video card is an AGP ATI Radeon 7000 series 32 meg
I re wrote the toolpath with less stepover and changed the actual part so it wasnt so high in Z and lowered the resolution of the part. All these things added up to a G code that was half the original size
-
Have you tried to turn off some of the toolpath screen features and see if it helps?
Brett
-
turn off....... hummm....... I dont really use the visual toolpah screen... let me see if that does it.......
can you tell me what to turn off so I dont screw it up?
-
Just remember what options you have checked in config, toolpath and uncheck all of them.
Brett
-
unchecked them all, and now when I load the 12 meg file I get the watchdog has been triggered.
re ran the driver test and it looks really flat. CPU is regestered at a 1.7 (AMD 2100 +) AMD never could get the numbers right!
-
Try turning the toolpath off via the button on the Diagnostics page. On my version its just above the reset button but could be placed elsewhere depending on version.
Hood
-
Also not sure what you mean regarding AMD andnot getting the numbers right but a 2100+ is at the correct clock when runing at 1733MHz.
Hood