Hello,
In the PV2.6 release it says that PV750 will not be available but any PV750 opened with 2.6 will be upgraded to PV780....
Once upgraded to PV780 will it still be able to load into an older PV750? Or will I have to keep 2.3 in order to modify programs to be loaded onto PV750s?
Thanks,
Phil
PV2.6 question
- drphil69
- Posts: 139
- Joined: Wed Mar 02, 2011 5:59 pm
- jpratt
- Enovation Controls Development
- Posts: 222
- Joined: Mon Jun 21, 2010 11:18 am
Re: PV2.6 question
2.3 is required to support 750 hardware as much of the new functionality requires a vector processing engine and other features specific to our newer hardware. However, 2.3 will continue to be supported and will get bug fixes as needed for our customers as long as we are producing PV750 hardware.
In addition, you can keep 2.3 and 2.6 side by side on one machine. I often take 2.3 configs into 2.6 simply to use features such as the improved validation which finds many more errors and the enhanced "Find All References" etc.
In addition, you can keep 2.3 and 2.6 side by side on one machine. I often take 2.3 configs into 2.6 simply to use features such as the improved validation which finds many more errors and the enhanced "Find All References" etc.
Jake Pratt
Software Development Manager
Software Development Manager
- drphil69
- Posts: 139
- Joined: Wed Mar 02, 2011 5:59 pm
Re: PV2.6 question
Hello,
If I have a PV750 config written in 2.6 then does that mean I cannot make changes to the code to be used in a PV750? Or can I import it back to 2.3 to make changes?
Thanks,
Phil
If I have a PV750 config written in 2.6 then does that mean I cannot make changes to the code to be used in a PV750? Or can I import it back to 2.3 to make changes?
Thanks,
Phil
- jpratt
- Enovation Controls Development
- Posts: 222
- Joined: Mon Jun 21, 2010 11:18 am
Re: PV2.6 question
Correct. If you have a 2.6 Configuration, its not a 750 configuration. It could be a PV780 or PV450 but logic/support/definitions for 750 are incompatible and not part of the release. There is no method of backgrading a configuration from 2.6 to a prior release.
If you imported it from 2.3, it was upgraded and HEAVILY modified by the upgrade process to be a 780 compatible configuration when you opened it in 2.6 the first time.
If you imported it from 2.3, it was upgraded and HEAVILY modified by the upgrade process to be a 780 compatible configuration when you opened it in 2.6 the first time.
Jake Pratt
Software Development Manager
Software Development Manager