Jump to content



Photo
- - - - -

Factory Talk View Studio verson 5

  • Please log in to reply
9 replies to this topic

#1 BobLfoot

BobLfoot

    The Wizard

  • MrPLC Admin
  • 3161 posts
  • Gender:Male
  • Location:Southern Indiana
  • Country:United States
    United States

Posted 28 October 2010 - 03:23 AM

Our Engineering and Maintenance Departments recently made the jump to Factory Talk View Studio Version 5.

I had an application I had created with RSVIEW Enterprise Version 4 and had saved both the *.mer and *.apa files.

Once I had Studio running I used Application Manager to restore the application {apa file}.

All my screens came in great but the macros won't open or edit.

Is there some trick or am I hosed?
BobLfoot

"Poor Planning on your part does not a crisis on my part make"

#2 fuzzy logic

fuzzy logic

    Sparky

  • MrPLC Member
  • PipPipPip
  • 91 posts
  • Country:Italy
    Italy

Posted 28 October 2010 - 04:34 AM

Did you get errors or just unable to open macro's files ?

Anyway, try to delete the Macros from the converted project (v5), export v4 macros and import to v5 converted project...
See Aid 34941.

Frankly, I've never tried this across two different versions, but give it a try... :lookingaround:

Hope this helps,

- fuzzy logic

Edited by fuzzy logic, 28 October 2010 - 04:35 AM.


#3 BobLfoot

BobLfoot

    The Wizard

  • MrPLC Admin
  • 3161 posts
  • Gender:Male
  • Location:Southern Indiana
  • Country:United States
    United States

Posted 28 October 2010 - 11:26 PM

Did you get errors or just unable to open macro's files ?

Anyway, try to delete the Macros from the converted project (v5), export v4 macros and import to v5 converted project...
See Aid 34941.

Frankly, I've never tried this across two different versions, but give it a try... :lookingaround:

Hope this helps,

- fuzzy logic

Thanks for the suggestions unfortunately exporting macros from v4 is not an option. V4 was uninstalled and the CD's locked in the IT vault before V5 was installed.

Not much better luck with the aid link you gave. RA is refusing my password/username and being really slow about resetting it. What can you expect on graveyard shift I guess.

Post more when I can get into RA site again.
BobLfoot

"Poor Planning on your part does not a crisis on my part make"

#4 Ken Roach

Ken Roach

    Propeller Head

  • MrPLC Member
  • PipPipPipPipPipPip
  • 2264 posts

Posted 28 October 2010 - 11:32 PM

All the technote says is "this should be simple". To wit:

To export macros you need to go to the
C:\Documents and Settings\All Users\Documents\RSView Enterprise\ME\HMI Projects
directory and then go into the folder with your application name on it. Inside of that folder there is a Macros folder. In the macros folder you will see a file name with the extension MCR. This is the macros file you would use to re-import into another application.

To import a macro all you need to do is right click Macros and click the Add component into application button. Then you should be able to browse to the MCR file and import.

Summary: Macros can be exported and imported in the 3.20 and above versions of RSView ME.


#5 BobLfoot

BobLfoot

    The Wizard

  • MrPLC Admin
  • 3161 posts
  • Gender:Male
  • Location:Southern Indiana
  • Country:United States
    United States

Posted 29 October 2010 - 12:05 AM

All the technote says is "this should be simple". To wit:

To export macros you need to go to the
C:\Documents and Settings\All Users\Documents\RSView Enterprise\ME\HMI Projects
directory and then go into the folder with your application name on it. Inside of that folder there is a Macros folder. In the macros folder you will see a file name with the extension MCR. This is the macros file you would use to re-import into another application.

To import a macro all you need to do is right click Macros and click the Add component into application button. Then you should be able to browse to the MCR file and import.

Summary: Macros can be exported and imported in the 3.20 and above versions of RSView ME.

I am getting two messages when I try to open a macro they are as follows;
1. Failed to get Macro file name
2. AOA: AOAInitialize failed

Ken - Why would I need to import macros? shouldn't they be a part of the APA which I restored from?
BobLfoot

"Poor Planning on your part does not a crisis on my part make"

#6 BobLfoot

BobLfoot

    The Wizard

  • MrPLC Admin
  • 3161 posts
  • Gender:Male
  • Location:Southern Indiana
  • Country:United States
    United States

Posted 29 October 2010 - 12:24 AM

Interesting I followed the suggested path {C:\Documents and Settings\All Users\Documents\RSView Enterprise\ME\HMI Projects} looking for macros and this folder doesn't exist.

Now i did find a folder {C:\Documents and Settings\All Users\Shared Documents\RSView Enterprise\ME\HMI Projects} in which there where several *.mcr files.

Opening these with Notepad I found the macros code I now can remember writing.

Copied these mcr files to a backup location and tried importing them several different ways without success.

Strange Thing is macro editor won;t let me ceate a new macro either.
BobLfoot

"Poor Planning on your part does not a crisis on my part make"

#7 Ken Roach

Ken Roach

    Propeller Head

  • MrPLC Member
  • PipPipPipPipPipPip
  • 2264 posts

Posted 29 October 2010 - 12:28 AM

They should have been converted along with the rest of the project; something's broken.

"AOA" is the Add-On Architecture feature of the FTView Studio system; it's how FTView launches sub-features like the Tag Database Editor, the User Accounts Editor, and the RSLinx Enterprise configuration editor, and, evidently, the Macro editor.


Give this a wild shot:


Delete the RDMDATA folder from the restored application.
Reboot the PC and start RSView ME, open a new application and open the Macro Editor.
Close the new application, then open the existing application and your Macro Editor should work.


Can you get to the parameters editor or other simple editors ?


Worst case you might need to do some uninstall/reinstall.

#8 fuzzy logic

fuzzy logic

    Sparky

  • MrPLC Member
  • PipPipPip
  • 91 posts
  • Country:Italy
    Italy

Posted 29 October 2010 - 12:40 AM

Yes, obviously all the components should be in place and work after restoring the .APA file... evidently this is not what is happening there... :disgust:
So I was thinking a re-import of the failing component could help...

Anyway, no trace of this error on macro opening, I've never seen it also... many indications are instead about AOA initialize error, it indicates a file corruption.
Now, it is difficult to find the right to apply in your situation, but I would do as follows:

First, try to make a backup copy of the macros file inside the project folder (.mcr extension), delete the macros from the application inside View Studio, try to re-import the saved macros again in the application as indicated in the technote from Ken, and see if helps.
If not, try the following, one by one:

Browse to the project's cache directory:

C:\Documents and Settings\All Users\Shared Documents\RSView Enterprise\ME\HMI Projects\<your_project>\cache

Delete the RDMDATA folder.
Reboot. Try accessing the macros

If it still errors then exit the application and open a demo. Attempt to open a macro.
If no error occurs then exit Machine Edition and delete the RDMDATA folder for the problem project:

C:\Documents and Settings\All Users\Shared Documents\RSView Enterprise\ME\HMI Projects\<your_project_name>\Cache\RDMDATA

If problem persists, you can use the following work around to import the project into a new copy which will recreate all of the associate files.

* Start a new application -select IMPORT
* select RSView Studio med file , and navigate to the problem project, select .med file , finish .
* The project is recreated and database is OK

If the demo application also errored, then repair FactoryTalk Platform:

Note: Machine Edition install media will be required to accomplish the repair

1. Open Add/Remove Programs
2. Locate FactoryTalk Platform
3. Select it then click the link in the middle: Click Here For Support information
4. Another window will appear. Click the Repair button, lower right.

The following are also useful steps sometimes to cleanup files...

Verify that it is possible to create a new project and compile a runtime from that. If the new project works, manually copy the original project components to the new project.

* HMI tags can be imported using the Tag Import / Export Wizard.
* The following components can be copied from the original project by right-clicking on them in the Application Explorer and selecting Add Component Into Application:
* Displays
o Global Objects
o Libraries
o Images
o Parameters
o Local Messages
o Information Messages
o Macros
o Data Log Models
o RecipePlus Editor
* Alarm configurations can be migrated by opening the original project in Studio, right-clicking on Alarm Setup and selecting the Export option. Once exported, the alarming configuration can be imported by opening the new project and selecting the Import option.
* The following configurations under the System folder will need to be manually re-created:
o Project Settings
o Runtime Security
o Diagnostic List Setup
o Global Connections
o Startup Options
* RSLinx Enterprise shortcuts will need to be re-created

I understand these are just tests and not a direct solution, but in this case it is really difficult to point out what happens exactly.

Hope this will help,

- fuzzy logic

#9 BobLfoot

BobLfoot

    The Wizard

  • MrPLC Admin
  • 3161 posts
  • Gender:Male
  • Location:Southern Indiana
  • Country:United States
    United States

Posted 29 October 2010 - 01:14 AM

Ken and Fuzzy -- Thanks for all the suggestions. My Opinion at this point is I am dealing with a messed up View Install of major proportions. I had two Factory Talk Services Platform 2.10 entries in add/remove programs. One from CPR9 and the other from CPR9 SR2.

Most recent info. Deleted the RDTMDATA folder from the suspect application. Rebooted and tried to create a new app. Creation of an application errored "NewServer Create tag Database Project Creation : Cannot Access the TagDatabase Sybsystem" and "Unable to create HMi Server" .

Think I'll let our local View Engineering guru get View working on this system. Funny thing was v4 ran fine.
BobLfoot

"Poor Planning on your part does not a crisis on my part make"

#10 fuzzy logic

fuzzy logic

    Sparky

  • MrPLC Member
  • PipPipPip
  • 91 posts
  • Country:Italy
    Italy

Posted 29 October 2010 - 01:28 AM

My Opinion at this point is I am dealing with a messed up View Install of major proportions. I had two Factory Talk Services Platform 2.10 entries in add/remove programs. One from CPR9 and the other from CPR9 SR2.



Agree, probably the setup steps haven't been followed correctly, or something have gone wrong during the install process...

Strongly suggest to cleanup everything and re-install. :shrug:

- fuzzy logic




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users