Ok so Im still having issues with the new redline elite cnc loosing steps while cutting. Ive talked with both Vectric and Onefinity support teams. The cnc is fully grounded and even added ferrite cores to the signal wires. It also happens with or without dust extraction. At first it was a simple pocket and lost steps on the x axis. Note there was no PP for the redline available on Vectric Aspire V10.5. There was one I seen posted and had to edit it to work. Well it didnt work and the results were the lost steps on the x axis. Through both tech supports I got a revised PP. I tried that. A few times and was able to cut the small pocket correctly. So I tried a more elaborate 3d relief file. This time I lost steps on a different axis, the z axis. It cut deeper as it went across the design. It now takes about 6hrs to run the test carve. Which Ive ran twice now. The second time was just cutting air and no dust extraction. I also did not adjust the speeds while running. Again lost steps on the z axis. Is anyone else running Vectric Aspire V10.5 and having issues? What did you find for a PP to use?
Why do you prefer the 10.5 verses the 12.5? the upgrade might solve all those problems.
Because I dont have the 400 dollars to put into an aspire upgrade that really only change where the buttons are. Ive been using vectric about 13yrs now. It gets old upgrading all the time for little to no improvement in the software. I also have other software licenses that require hundreds of dollars annually. Heck I just paid thousands on new PCs due to windows 10 end of support. It really shouldnt matter which version you use though. No where is it specified this is a must have to use. Youre right in that it might solve the issues it also may not. Vectric has continued support for v10.5. It will get sorted out. Just sucks in the meantime. Also as an early adopter to the Redline series its to be expected to have bugs that need sorted out…
So I am curious
When you see the generated g-code you can see missing positional steps?
If so it’s a post processor issue.
If it’s on the control side then the controller is not reading the file correctly
Id have to look at the code output from each. I know changing the PP only fixed the problem previously and made several successful cuts on the simple pocket. I know after running this much longer code it was off slightly because it got deeper and did not return to zero after it finished. Also I didnt suspect an x or y issue. Its possible there is still an issue with them as well. I marked z and verified that that lost steps as it should have returned to zero position. It was off about 3/16in across an 8in pass. Ive also ran the code itself through a 3rd party software that shows the code itself generating a 3d toolpath render that looked correct. NC viewer… Theres no doubt theres an issue. Where we’re still guessing and testing. How it changed from one PP to the other Im not sure. Vectric said a bunch was cut out from the initial PP. They also took some things out themselves.
Check if its a G90 or G91 code
G90 it says at the top of the file, G17 G20 G90
Ok good
G91 can cause drift
If you think its your version of Vcarve and/or the PP……do you want a gcode file produced from v12.5 to test using the included Onefinity Redline (inch) or (mm) PP?
Im working getting that via tech support thanks.
No problem, in case you arent able to get it the offer stands as I have both and can run it basically whenever.
Still having issues. So I spent the $450 on the 12.5 upgrade. Running a air cut right now with no dust extraction…
Well that was a waste of money because it did not solve the loosing steps. 
Air cut as in the spindle is spinning?
Shut off power to the spindle and air carve again
Trying that now. Ill report back later.
Ok so it ran by itself, in the dark, and nothing else on. No spindle, no extraction. Same file and lost what looks like the same amount of steps. Which is about 3/4in.
Ok good so you have eliminated interference
Have you gone into machine parameters to see if they match
If not maybe a factory reset
They dont match what you have there but yes I set them back to default. I also set the Vectric Aspire up to match the same acceleration settings. Which that might just help with estimated times. Previously and after i started having issues just trying to cut a simple 3in sq pocket about an 1/8in deep. I tried cutting the acceleration in half. It didn’t help. The only thing that helped with that was switching the PP to v12.5 aspire. The additional grounding and ferrite cores didn’t help. So it cut fine after switching the PP. Simple pocket though. I switched to the relief model file. Then instead of the x axis loosing steps it became the z axis. Initially it was an 1/8in. Now its consistently about 3/4in. They’ve upgraded everything on this cnc except the cables. Closed loop stepper motors. Which dont really work. All metal enclosures. Beefed up all axis’s mechanically. Still unshielded un sheathed cables. Lots of guessing and back and forth at this point and a new machine that doesn’t cut what its supposed to. I gotta stop. Im frustrated and not happy at all. Looks like I gotta try sourcing all the parts and wire to try making my own. Im gonna try making a different 3d model to cut. Much smaller to test so it doesn’t take 6hrs to run.
Ok so it sounds like you may have eliminated the stepper motors because if you had a bad stepper it wouldn’t change from one stepper to another unless you had unstable voltage
There’s something wrong with the compiler or the post processor software
Its the same as what others are using though. I dont see other people having issues. Which points back to emi in some way. Again just guessing because you cant really test for it.