Answered

1.10 Update

Since the 1.10 update release I have had a lot of support calls of g-code files not running correctly plus a number of other issues, soft limit warnings etc etc.These are a result of incorrect post p being used.

So as a heads up to Carveco users, after an update check that your defaulted post p is correct when outputting your toolpaths.

If an update includes new post p's and they are alphabetical higher in the list that your post p then your default post will get moved down in the list resulting in the incorrect post being promulgated in your save toolpath dialogue box.

Gary

0

Comments

4 comments
  • It would be good to have some sort of lock on there so that this may not happen.  I also used to get quite a few calls from people who had just accidentally changed the machine file format and didn't realise.  What do you reckon Gary?

    1
    Comment actions Permalink
  • Leighton I agree, I think that would be helpful. Basically you are setting your post p as a default, then it should remain the default not change especially just because the list of posts had additional ones added to it.

    1
    Comment actions Permalink
  • The way I handle it is to delete all of the post processor (*.con) files that I don't use from C:\Program Files\Carveco\postp.  This has the added benefit of making the list of post processors to choose from much shorter.  That's my two cents anyway.

    0
    Comment actions Permalink
  • Hi Gary,

    A fix for your reported issue has been implemented as part of the Carveco 1.11 Update, released today (January 14, 2020). For details, see the associated release notes on our company website.

    1
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post