Updating to 5.30 another disaster

[suntravel]

the complete installation is in the cnct folder, there will be nothing overwritten if you make a copy and name it cnct506 for example.

I have several versions on my machines from testing. cnct530 cnct532 cnct539 cnct539a ect...

If I want to work with one of these I simply rename cnct to cnct539b and rename cnct539a to cnct.

Super easy.

Uwe

[lavrgs]

the installer makes a backup for you during the install.

This implies a backup is automagically made. If I rename my existing cnct prior to install I assume I would get a fresh install. If I copy the original cnct will the install be different - does It keep VCP data?

[suntravel]

New install will be with new VCP.

If you want to use the old VCP, copy the VCP folder from the backup to the new install.

Uwe

[lavrgs]

To clarify; if there is a working VCP in the current cnct directory, will a new install overwrite it?
What about custom PLC? I use the option to not use a new one. I believe that eliminates any new features that are part of a new PLC.
In my current install - which did not work - I fixed it by copying the old mpu.plc file...I know that's not a proper solution but it got me running...
DATE STAMP 7/22/2025

[suntravel]

To clarify; if there is a working VCP in the current cnct directory, will a new install overwrite it?
What about custom PLC? I use the option to not use a new one. I believe that eliminates any new features that are part of a new PLC.
In my current install - which did not work - I fixed it by copying the old mpu.plc file...I know that's not a proper solution but it got me running...
DATE STAMP 7/22/2025

A new installation will generate a new VCP, if you want to use the old one, copy from backup.

A new installation will compile a new PLC, If you want your old one, copy from backup or compile the latest .scr file.

The SRC files are the same in your 5.06 and 5.30 reports.

If you have used some custom macros, copy them from the backup.

If you want to use new PLC features and keep custom changes, use NP++ with compare plugin, compare and transfer the custom changes to the new PLC, compile and happy machining.

Uwe

[centroid467]

To clarify; if there is a working VCP in the current cnct directory, will a new install overwrite it?
What about custom PLC? I use the option to not use a new one. I believe that eliminates any new features that are part of a new PLC.
In my current install - which did not work - I fixed it by copying the old mpu.plc file...I know that's not a proper solution but it got me running...
DATE STAMP 7/22/2025

You should also bring over the old plcmsg.txt so the messages are correct.

[suntravel]

An other option maybe to hire someone doing the update per TV session...

Uwe

[lavrgs]

If I have to hire someone to update I may as well give up...updating should be like windows...push a button and go.

[suntravel]

If I have to hire someone to update I may as well give up...updating should be like windows...push a button and go.

Did you ever made an update on an industrial CNC machine

One button update will work on full closed systems like Masso or Bambu 3D Printers, but not for open systems you can deeply customize to your individual machine or workflow like Centroid CNC

You have also hired someone for custom changes on your PLC, so hiring someone for an update is not giving up, it is just a decision to spend time to learn how to do it, or skip this and let someone else do the job and spend the time to make parts

Uwe

[Houseman303]

Why isn't it possible to load the old PLC during a software update and only add the new features, which are then compiled automatically? Will it actually be easier if you have to pay for software version 5.40 or higher?