Hello All, I accidentally deleted the original post on this, because I thought it was a duplicate. So, I am re-posting it. We are using the OpenBuilds software for the first time. We are experiencing an issue while attempting to perform a diamond-drag engraving. Here is the workflow: 1: Zero the xyz to the NW corner of the 3"x6" workpiece. 2: We import our gcode from Vectric Aspire. 3: Run the job. The problem, is that the actual carving job is only carving an area roughly 3cmx6cm. If we look at the Openbuild control software, the workpiece correctly shows 3x6in. When we press the "check size" button, the spindle moves around a small 3x6cm area, and NOT the 3x6in area. Is there something that we are missing, here? Have you seen issues like this before?
NOTE: Someone had asked me if we were using the OpenBuilds post processor for Vectric. We tried to install the OpenBuilds post processor into Vectric Aspire, but it generated errors and would not install.
Take a screenshot of your Aspire > Help > About window please Also your Post Processors would not be on the DESKTOP: See Where do I look to find the Post Processors folder on my PC?
We extracted the files from the zip and put them into the /documents directory. Then, we used the "install post processor" utility in Aspire and directed it to the files in /documents.
We manually put the files into C:\ProgramData\Vectric\Aspire\V9.5\PostP Then, we re-launched Aspire. It generated the following error, when it re-launched.
Version 9.5 is quite old, your are on v9.510 (from Oct 2018). See Program Updates | Vectric The installable Post files works with Vectric 10.x and newer. Our posts are built into the latest versions (10.5 and 11) You may want to get the latest: Aspire Upgrade Page | Vectric Also, make sure your machine is Calibrated - steps per mm properly set. If you jog an inch (in incremental) does it move an inch?. Wizards and tools > Calibration
We have upgraded to Aspire 11, and the same issue is happening. I do not believe it is a post processor issue.
We figured out the issue. We uploaded new firmware to the controller, and modified the settings using a different controller application. The machine is now working as designed.
