Going from V4.62 to V4.82 PROBLEM

[cnckeith]

[ShawnM]

let me know if you want to see any thing else on this screen. we will get this running for the v4.99 rev5 beta build.
we still are working on v4.99 rev4 everyday, we should have something soon to publish for public beta use/testing.

Can you add the drive configuration xml file? I have a custom one that is saved in resources\wizard\saved\drives. This is saved in the report.zip file and can also make the setup go a lot faster my simply importing this XML fil back into CNC12. I don't know if others "export" this XML file for their own setup or not but they should as it helps setup the drive, input and outputs much faster.

yep! thanks for the reminder ..will do.

Awesome, thank you.

Will it be possible to save the "profile manager" in the plasma version? I've created many custom profiles just for holes from the existing profiles. For example I take the Steel-65A-.5 profile and copy it and make is Steel-65A-.5-Holes and then modify the feed rate to about 60% of the book number. I prefer to do this rather than adjust the feedrate override on the VCP as adjusting the feedrate override also slows down the touch off speed by 60%. When I have to cut 600 holes this saves me a lot of time just waiting for the touch off cycle.

[Sword]

For quick access of previously used MDI entries, I'll often grab a copy of .mdihistory as well.

[lavrgs]

<snip>
Can you add the drive configuration xml file? I have a custom one that is saved in resources\wizard\saved\drives. This is saved in the report.zip file and can also make the setup go a lot faster my simply importing this XML fil back into CNC12. I don't know if others "export" this XML file for their own setup or not but they should as it helps setup the drive, input and outputs much faster.

I use a drive called DYN4_DB25,xml. I think it came from Centroid - it was part of a solution to my noise issues with the DMM drives. Is this a "standard"? I t was one of those items I had to go find during the update process.
The other area that I would like to see improvement is the transfer of wizard inputs. The current method of taking screen shots is pretty clunky...Is there a file that represents the Wizard config?

[cnckeith]

<snip>
Can you add the drive configuration xml file? I have a custom one that is saved in resources\wizard\saved\drives. This is saved in the report.zip file and can also make the setup go a lot faster my simply importing this XML fil back into CNC12. I don't know if others "export" this XML file for their own setup or not but they should as it helps setup the drive, input and outputs much faster.

I use a drive called DYN4_DB25,xml. I think it came from Centroid - it was part of a solution to my noise issues with the DMM drives. Is this a "standard"? I t was one of those items I had to go find during the update process. < DNY4 DB25 is standard and included with the latest version, not sure why you didn't see it.>

The other area that I would like to see improvement is the transfer of wizard inputs. The current method of taking screen shots is pretty clunky...Is there a file that represents the Wizard config? < thats what i outlined above.>

[cnckeith]

Awesome, thank you.

Will it be possible to save the "profile manager" in the plasma version? I've created many custom profiles just for holes from the existing profiles. For example I take the Steel-65A-.5 profile and copy it and make is Steel-65A-.5-Holes and then modify the feed rate to about 60% of the book number. I prefer to do this rather than adjust the feedrate override on the VCP as adjusting the feedrate override also slows down the touch off speed by 60%. When I have to cut 600 holes this saves me a lot of time just waiting for the touch off cycle.

Yes, that is in the works for v5.0

till then just copy over any of your custom profiles from the old folder to the new one and they automatically show up in the profile manager. nice that we did it that way!

[ShawnM]

Awesome, thank you.

Will it be possible to save the "profile manager" in the plasma version? I've created many custom profiles just for holes from the existing profiles. For example I take the Steel-65A-.5 profile and copy it and make is Steel-65A-.5-Holes and then modify the feed rate to about 60% of the book number. I prefer to do this rather than adjust the feedrate override on the VCP as adjusting the feedrate override also slows down the touch off speed by 60%. When I have to cut 600 holes this saves me a lot of time just waiting for the touch off cycle.

Yes, that is in the works for v5.0

till then just copy over any of your custom profiles from the old folder to the new one and they automatically show up in the profile manager. nice that we did it that way!

Yes, you guys are awesome. I've been doing that already when I update the plasma.

[lavrgs]

Rather start a new thread I will ask here first . I want to clear the error files...it appears that msg_log.txt gets overwritten on start up. I originally renamed it and a new one was created, but what about msg_cnt.txt? It seems to come from some register that has accumulated the errors.
I ask here because I was getting some ethernet communication errors and wanted to see if I could count them after the fix, Which in my case seemed to be grounding the shield of the cable that supplies the signal for the touch probe.

[cnckeith]

it doesn't get overwritten, if you move it, rename it or delete it, cnc12 creates a new one so it doesn't crash due to a missing file.

msg_cnct.txt is just the tabulation file keeping track of the number of same messages issued.

[FlySox]

<snip> Can you tell me what file stores the return positions and origins?<snip>

I'd like to know this too. Just upgraded from 4.62 to 4.82 and lost my G28s & G30s across multiple WCSs (mostly the location of my tool setter). I can re-create them, but it'd be nice to know what file this lives in for future upgrades.

Excited to hear about the "restore from report.zip" functionality. Should make the upgrade process a lot less painful and trouble-free (I will not miss screen-shotting wizard screens and restoring them by hand each time or copying over my VCP file & new/modified macros, offset libraries, etc, etc).