DM500's NC file problem

dogovietvu

Dear Enjoy_cnc,
My DM500 can't run with small NC file and sometime temporary "death" when run big NC file. Pls show me how to solve it.
Thank you.

enjoy_cnc

Hello there,
I'm sorry to have responded to you so long.
1: If the file size is less than 100K, the file will be scanned for structure before processing. The subroutine number must be 0 or not written.
E.g
O000
G54 G90
G01 XYZ
. . . .
or

G54 G90
G01 XYZ
. . . .

2: What is the version number of your application, you can upgrade to the latest version and try it out, or send the video of the handle freeze problem to youtu and send me a link, thank you

dogovietvu

Hello enjoy_cnc,
My DM500 is run with less than 100K file (not written on subroutine). I was upgrade to 2020-01-07 (94)-eng version but sometime it's still occur freeze problem.
This's the link on youtube: https://youtu.be/c-l4G50wu-w
Thank you.

enjoy_cnc

Hello there
Can you send the processing files and parameters? Let me check your processing code or you can try another U disk and try again.

dogovietvu

Hello enjoy_cnc,
I'm using JDpaint Artform3.5 with my VietVu to export NC file.

enjoy_cnc

Hello there
I tested your processing files and found no stuttering issues;
The possible reasons are as follows:
1: The real-time drawing calculation error is caused by the unknown file size;
Solution:
      First simulate the file and then start processing;
      Turn off the real-time drawing function:
        250: real track paint enable: disable
2: caused by external interference input signal;
        238: IO Filter time: 100 ms

3: U disk read and write problems,
    Replace U disk;

It is recommended to modify the 250 and 238 parameters first and then test!

milawka2222

Also faced with this situation, interference is excluded, U disk is working. After pressing RESET, it was noticed that it reacts to manual movement along the axes but does not respond to automatic commands, for example, to the “ALL GoTo Zero” command, it does not respond and does not execute the command. After a power restart, everything falls into place, everything is executed and the G code is executed without problems. The firmware is the latest version. On old firmware this was not noticed. Please correct this situation as it is not permissible !!!
Moreover, this is not the first case.