Yesterday, I installed "PowerVision 2.3.11147" configuration tool.Earlier I was using "Murphy Configuration Tool 2.2.10326". When I tried to open and build my .db3 files that were created using "Murphy Configuration Tool 2.2.10326" in "PowerVision 2.3.11147" , I got many errors. By analyzing the errors, I found that the db3 file that I opened in "PowerVision 2.3.11147" has been changed in following aspects -
1. Different state machines having same state names are getting ignored. Similarly the if the db3 filsame name variables are getting ignored.
e.g. If in your db3 file, there is "Init" state in 3-4 different state machines then it considers "Init" name state in only one of the state machines.

2. Many of the expressions written under calculation events are now recognized as invalid in build
e.g. Warning-Error in expression Set ServRemSetValue. Expression is not valid-Expression

and many more.

Can somebody guide me in porting db3 file created using "Murphy Configuration Tool 2.2.10326" to "PowerVision 2.3.11147" format?

Thanks & regards,
Shruti

Hello ShrutiK,

This is a good topic, you and other users will find that the PowerVision Configuration Tool version 2.3 checks for more types of errors during save so it is possible that many errors found in 2.3 already existed in 2.2 but were not detected.

One example is errors inside expressions like calculation events, they were not checked during save in 2.2 but they are checked now during save in 2.3.

Also, you cannot have two variables with the same name or two events with the same name but you should be able to have two states with the same name if they are in different state machines.

Regards,

ksaenz

It seems like just yesterday we went through this with 2.2 (actually it was in March this year).

I have a host of problems trying to open my 2.2 configuration in 2.3, principally, it appears most of the scripting to do screen rotations was eliminated and then broke during the conversion. Confusingly, the screen rotation scripts are vestiges of a function I never used. My config uses 1 screen only, so troubleshooting that functionality is a dead end.

This imported 2.2 config has hundreds of events that are organized differently in the 2.3 base config. Is this another example where it's better to start over with a clean slate?

Attached my event log after validating my configuration.

Thanks for the constant support. 2.3 Looks like another giant leap forward from 2.2. I especially appreciate the copy and paste functionality in the Database since I've discovered we're missing 115 DTCs for our preferred engine. I just wish I could create the tarbal and get the updates out.

Lucian

I'm sorry to hear your having trouble upgrading. We tried very hard to get the upgrade right and make it easy to get to 2.3 which is a large upgrade. The beta cycle found a number of problems that we have corrected but there could still be something we missed of course. I'm not sure exactly what the problem is with your config but send me your configuration and I can take a look. Hopefully its something we can just fix up and get you going.

Also note, as we upgrade the programming environment from release to release we sometimes discover new things that can cause our users trouble. Often this is caused by bugs or behaviors of the previous release. Two common errors that come up in 2.3 are ....invalid expressions and empty values as you are seeing. 2.3 attempts to find these so they can be cleaned up. 2.2 had a few ways where you could create an expression that later became invalid (due to deletes or name changes.) 2.3 catches these with the warning..."Warning-Error in expression" VERY LIKELY you can simply remove these expressions but you should take a look at each one to make sure your not expecting it to work. The same goes for "Warning-On Show Event in advanced event list on page view" These are unmapped view items that 2.2 did not correctly disconnect. Usually this is because an event was deleted. You can either delete the mapping in the advanced view or map it to something.

The other errors, I will have to look at. If you will send me your config (2.2 version and 2.3 version if you want) and maybe some more details on the rotation issues your having i will take a look.

As always, we are commited to helping you upgrade so let me now how I can help best. Feel free to email me directly till we get this all figured out.

How to define user variables in 2.3 ? The database tab in 2.2 had a 'system variables' option which is not there anymore in 2.3