Topic: mx2 runs dnc with choppy machine movement

By: Tim@map

Posted on: Mar 18 2010 at 12:19:31 AM

I have a 1987 Matsuura 800v with an MX2 control. The sofware works, I tried the block delay at 10, 5 and fast settings. I can not get it lower than 5. The program is a large 3d surfacing program. The problem is that it seems to be reading too slow. The baud rate is set to 4800. The machine movement is choppy and not actually moving at the programmed feed rate. I think this is do to the seemingly slow transfer rate. Any help? I like the software.

By: Support,

Posted on: Mar 18 2010 at 12:58:17 PM

When block delay is fast and block end (CR/LF etc) is set to none, ignore or fast then the software realy ought to be sending data at the full 4800 with no delays.

Are you able to take the baud rate up to 9600 ?

By: Tim@MAP,

Posted on: Mar 18 2010 at 02:49:41 PM

I tried dnc with new settings and the program fed at a even clip. I was at 4800 baud and the machine movement was still choppy. I tried 9600 baud yesterday with old settings and got a overrun alarm. alarm 077 rs232c error (overrun) 10 charactera more have been read in after stop code has been trasmitted through rs232 interface. Is 4800 baud just to slow for surfacing programs?

By: Support,

Posted on: Mar 19 2010 at 12:46:05 PM

If the program gcode is lots of lines for each small movement then the data has to be fed through very quickly although 4800 would often be fast enough. If you have the block delay/block end set to fast and it's still not fast enough then you will need to run at 9600.

But, as you said, 9600 causes the overrun alarm - we can work on that. First thing to do is switch off the Windows FIFO.

Control Panel > System > Hardware > Device manager > Comports

Select the com port > Port Settings > Advanced.

This bring up a window with options for the Com Port FIFO. You don`t need to adjust any other com port settings via this tool, just make sure the FIFO is disabled. (Slide the sliders down to zero and uncheck the checkbox)

Try disabling the FIFO first - and if you still get occasional overruns try increasing the block delay.

Topic: mx2 runs dnc with choppy machine movement

Reply to this topic