Have been dragging my feet and have not upgraded my carbide create V6 (build 648) to V7. Will I be able to assess and use all my old files I designed previously?
It won’t shock anyone to know I haven’t updated motion as well. Just was waiting until after the holidays. Any advice or will anything be lost with either upgrade?
Yes, v6 files should open in v7 — if you find a file which won’t, let us know at support@carbide3d.com and we’ll do our best to look into it.
The new CM adds some nifty features, and the new G-code visualizer has saved me from a couple of moments of panic, so I recommend it — but I can understand wanting to defer it until one isn’t in production mode and facing deadlines.
Thank you very much! I’m going to give it a go then!
@WillAdams can answer this but I think when you open a v6 c2d file you have to save it in v7. The gcode is embedded in the file instead saved as separate gcode files. The newer CM can decrypt the gcode from the v7 c2d file. If you do not have a c3d machine and you have the pro version you can save separate gcode files. If you do not have a pro version then you cannot use the c2d files on 3rd party machines because CM does not work on 3rd party machines.
I have been using the v7 from early beta and I love it.
I too am now looking more seriously into upgrading to v7 and have tried to open some of my v6 files.
Using 743 the toolpaths of my v6 files are not listed, but they are present as they show in the simulation. Obviously this limits the attraction of upgrading. Using 719 they appear as I would have expected (see screenshots). I haven’t gone back to earlier versions yet (I have 726 saved somewhere).
The most recent version is 743:
Please send us any v6 files which don’t open correctly in v7 to support@carbide3d.com and we’ll do our best to look into them w/ you.
If you are running a C3D machine the lack of gcode separate is not a problem. However if you are using a 3rd party machine it is a big deal unless you buy the Pro version. The Pro version allows you to save gcode separate. If you are running a Shapeoko/Nomad there is no need for separate gcode files because it is all encrypted inside the c2d file. The features they have been adding since v6 and on into v7 are very nice and worth the upgrade.
If you are running a 3rd party machine they still have v6 available. Otherwise why not upgrade up to v7 because they are already working on v8, v9,…
I don’t use a Shapeoko but I do like the look of the new 5. I am in Australia and use a locally made and supported brand called BlueCarve.
I will need to get Pro as I obviously need the GCode, but the new features in v7 look quite useful to have.
If you can forgo the v7 features, you can use v6:
Thanks @WillAdams - I use the free v6 now, and it gives me what I currently need. The inability to generate Gcode for non-C3D machines is the sole reason for me not having already moved to v7. This topic has been discussed at length & I understand the need for the company to earn a revenue stream for its support - in return for using the free product, I (& I expect many other freeloaders) have previously contributed here and/or on the Facebook page & hopefully managed to help advance the product or at least help some other users.
It is now up to the non-C3D customer to decide whether V6, V7 Pro, or indeed another company’s product offers the appropriate value for them based on the work that they do - personally, I am not yet decided.
In regards to the issue that I raised, the problem no longer occurs (i.e. I can see the TPs now). I have no idea why this is the case as I did not change anything, but I am now able to commence an evaluation of the new features in v7 to decide whether they would be of value to me for my upcoming projects.
This topic was automatically closed after 30 days. New replies are no longer allowed.
