Updating to 5.30 another disaster

[glbreil]

Yeah, I know how to edit and compile it and all that, I am just saying if you have a customized PLC and you want to put those customization in the latest version of the PLC to get all of the new features there is quite a bit more to know than copying a few lines. At least when I compare mine there is. Gary

[lavrgs]

I expected that the new features would be part of an updated X.src file. I just checked my directory, and I don't see a X.src file that didn't exist before. Does that mean I didn't get any of the new features...?
Since I used the "keep current configuration: option as part of the section where a new PLC was asked for Should go and redo that portion >>>AFTER making a report. .Then restore the Report?

[glbreil]

Well I did two different things. Before I ever did the upgrade I ran the installer on another computer and as soon as all the files extracted I aborted the install. Then I took a good look at the .src file in comparison to my own and saw that I probably wasn't going to be combining them anytime soon. When I actually went to the machine computer I ran the whole install, let it complete and then opened the program and did restore report from my previous version. I never really checked to see if I had the new .src file in the machine after that, because I have it on the other computer and that is where I have been doing my comparisons and work thinking about trying to merge the two. I would think if you were keeping the current configuration that would be telling it not to install the new mpu.plc which is the compiled version of the new .src file.

I am no expert, but what I did worked for me, but as I said I wasn't after the new features and did not get them.

[lavrgs]

glbreil The reason I updated was to get the probing correction that you mentioned.
Did you remove the parting tool For the Renishaw probe or was it not there to begin with. My probe attachment has one area I would improve - Mine is in a fixed position so I would move it to allow a larger diameter piece of stock in the spindle. I assume the Renishaw setup swings out of the way and is always attached...?

[glbreil]

Yes, I removed the vertical cutoff slide so the probe arm could swing up over the headstock. It worked fine but I had never used it, I just had a parting tool on the turret.

The arm I used is motorized and I assigned aux buttons to raise and lower it. Gary

[lavrgs]

Back to the 5.30 update - I am not getting a "press cycle start" after MDI commands...when I press cycle start the command works

[CentroidFrog]

I'd like to clarify a couple of things:
1. mpu.plc is the result of compiling the source file (in your case it's "k104766R2.src") which can be seen on the second line of the mpu.plc and the source file can be found in your cnc* folder and your report. mpu.plc should never be directly edited.
2. You're not finding that new source file because you told it not to install one (if I understand properly).
3. If you want any of the source files that can be installed they can be installed using the CNC12 installer or extracted from the CNC12 installer using programs like 7zip.

[lavrgs]

Ok so I could open the .exe file with windup and view the new PLC… how different will it be, it seems like the plc are set up with the stages in an organized progression so when using compare thing align daily well.
If I saved a report and loaded 5.30 fully - with new plc, how would I get my custom PLC back in? My custom vcp has been restored so I assume that will remain…or the skin and aux folder won’t get over written?

I do seem to have some minor issues with MDI…probably by copying the previous mou.plc?

[cnckeith]

compiling a PLC program doesn't overwrite anything to do with the VCP skin/folder

if you had a custom PLC program written for you should get advice from the person that did that work for you. as you seem to be copying files from the old install to the new one without understanding what they are/do which is a sure fire way to dig yourself a big hole.

[lavrgs]

I made the changes to the PLC to overcome the shortcomings of the incomplete plc**. My changes allowed the use of the wmpg to use macro 1 & 2 to open/ close the collet. Not a huge change although other missing info had been added by
Cncsnw to correct other deficiencies.
I’ll take a look at the new plc to see if I can update it to include changes in my current version
**these are the words of another service provider who notes that changes had been started but not finished by the vendor I purchased from