[SELFSOLVED] only garbage in RPF-output after correct levelling run
Posted: Sun Feb 16, 2020 8:13 pm
I did a search here in the forum but didn't find a similar problem and so found no solution.
I'm using a CNC 3020 with LPT-controller input ( https://www.ebay.de/itm/800W-VFD-4-Axis ... 3237924341 ) enhanced by a Mach3-USB-LPT-Converter ( https://www.ebay.de/itm/MACH3-4-Axis-10 ... 3621834110 ) with Mach3 under WindowsXP.
I tried to run a PFG-file generated with AutolevellerAE-0.9.5u2 for the here provided example "spindle.top.etchm3mm.nc". I attached the generated PFG-file below.
The process runs without problems. The spindle was stopping between 0.0 mm and -0.3mm on every test point (the limit was set to -2mm) and the Probe-LED in the Indicator-Window of Mach3 lit on every point. No error message was generated but within the toolpath the program displayed between 4 to 6 yellow dots within the probe area. But the generated RPF-file (also attached) contains an unsorted list of partly identical entries but (like to see) real measured Z-coordinates. So it can't be a problem of coordinate transfer to the variables to the controller.
Does anyone know the reason for such a messed output file after a correct probing run?
I'm using a CNC 3020 with LPT-controller input ( https://www.ebay.de/itm/800W-VFD-4-Axis ... 3237924341 ) enhanced by a Mach3-USB-LPT-Converter ( https://www.ebay.de/itm/MACH3-4-Axis-10 ... 3621834110 ) with Mach3 under WindowsXP.
I tried to run a PFG-file generated with AutolevellerAE-0.9.5u2 for the here provided example "spindle.top.etchm3mm.nc". I attached the generated PFG-file below.
The process runs without problems. The spindle was stopping between 0.0 mm and -0.3mm on every test point (the limit was set to -2mm) and the Probe-LED in the Indicator-Window of Mach3 lit on every point. No error message was generated but within the toolpath the program displayed between 4 to 6 yellow dots within the probe area. But the generated RPF-file (also attached) contains an unsorted list of partly identical entries but (like to see) real measured Z-coordinates. So it can't be a problem of coordinate transfer to the variables to the controller.
Does anyone know the reason for such a messed output file after a correct probing run?