1/3/12 27708 RSVieZ32 Wo VieZ SE ConYeUVion GXidelineV 1/6 UockZellaXWomaWion.cXVWhelp.com/app/anVZeUV/deWail/a_id/27708 RockZell AXWomaWion SXppoUW CenWeU 27708 - RSVieZ32 Wo VieZ SE ConYeUVion GXidelineV AcceVV LeYel: TechConnecW DaWe CUeaWed: 02/18/2004 12:00 AM LaVW UpdaWed: 04/28/2011 02:20 PM I ZoXld like Wo conYeUW m\ RSVieZ32 Wo FacWoU\Talk VieZ SE. Will eYeU\ Wing conYeUW? In moVW caVeV, \oXU applicaWion Zill conYeUW and e[ecXWe VXcceVVfXll\; hoZeYeU, WheUe aUe a handfXl of VieZ32 pUojecW pUopeUWieV WhaW Zill noW diUecWl\ conYeUW Wo VieZ S In addiWion Wo WhiV WechnoWe, Whe folloZing docXmenW iV alVo aYailable fUom Whe RockZell LiWeUaWXUe LibUaU\: RSVieZ32 Wo VieZ SE PUojecW MigUaWion (PDF) WhaW Won'W ConYeUW fUom RSVieZ32 Wo VieZ SE The folloZing objecWV Zon'W conYeUW fUom RSVieZ32 Wo VieZ SE: VBA VBA in VieZ32 iV VeUYeU-baVed; VBA in VieZ SE iV clienW-baVed. See AID 51770 - Sample VBA: E[eUciVe in migUaWing a VieZ32 applicaWion ZiWh VBA Wo VieZSE NaWiYe RSVieZ 32 WUendV Tag moniWoUV E[WeUnal applicaWionV WhaW depend on RSVieZ32 Wo be an OPC oU DDE daWa VeUYeU RSVieZ32 AlaUm SXmmaUieV Command lineV embedded in gUaphicV. FoU a ZoUk-aUoXnd, Vee AID 35209 - HoZ Wo cUeaWe an "embedded command line" in an RSVieZ SE gUaphic) . UVeU accoXnWV cUeaWed in RSVieZ32 Zill noW conYeUW Wo SE XVeU accoXnWV Some RSVieZ32 E[WenVionV RSVieZ 32 SPC - UVe FacWoU\Talk HiVWoUian SE ZiWh VanWagepoinW inVWead. RSVieZ32 MeVVengeU - UVe SpecWeU InVWUXmenWV Win911 inV Wead. Some AcWiYeX conWUolV E[ample: RSVieZ32 TUendX WUappeU. TheVe Zill need Wo be eYalXaWed on an indiYidXal baViV Wo Vee hoZ Whe deViUed fXncWionaliW\ can be achieYed in FacWoU\Talk VieZ SE. CommandV ThaW CannoW Be E[ecXWed fUom an VieZ SE EYenW The folloZing commandV can be e[ecXWed fUom a bXWWon oU command line, bXW noW fUom an VieZ SE eYenW: AboUW Define DiVpla\ DiVpla\ClienWCloVe DiVpla\ClienWOpen DoZnload DoZnloadAll FlXVhCache Help IdenWif\ InYoke Ke\ Ne[WPoViWion Ne[WWindoZ OpenRSLogi[5000 PoViWion PUeYPoViWion PUeYWindoZ PUinWDiVpla\ PXllFoUZaUd PXVhBack RecipeReVWoUe RecipeSaYe ScUeenPUinW SendKe\V SeWFocXV SXppUeVVOff SXppUeVVOffAll Undefine Upload UploadAll MiVcellaneoXV NoWeV 1. While RSVieZ SE haV a "S\VWem\UVeU" Wag, iW iV meUel\ a caUU\-oYeU fUom RSVieZ32 and iV non-fXncWional. UVe Whe CXUUenWUVeUName( ) fXncWion inVWead. 2. CeUWain AcWiYeX conWUolV ma\ noW fXncWion aV Whe\ did in RSVieZ32. TheVe Zill need Wo be eYalXaWed on an indiYidXal baViV. For e[ample: The RecipePUo AcWiYeX conWUol inWeUfaceV diUecWl\ ZiWh Whe RSVieZ32 objecW model and WheUefoUe ZoXld noW ZoUk ZiWh RSVieZ SE.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
1/3/12 27708 RSView32 to View SE Conversion Guidelines
27708 - RSView32 to View SE Conversion GuidelinesAccess Level: TechConnect
Date Created: 02/18/2004 12:00 AM
Last Updated: 04/28/2011 02:20 PM
I would like to convert my RSView32 to FactoryTalk View SE. Will everyting convert?
In most cases, your application will convert and execute successfully; however, there are a handful of View32 project properties that will not directly convert to View SE.
In addition to this technote, the following document is also available from the Rockwell Literature Library:
RSView32 to View SE Project Migration (PDF)
What Won't Convert from RSView32 to View SEThe following objects won't convert from RSView32 to View SE:
VBA
VBA in View32 is server-based; VBA in View SE is client-based.
See AID 51770 - Sample VBA: Exercise in migrating a View32 application with VBA to ViewSE
Native RSView 32 trends
Tag monitors
External applications that depend on RSView32 to be an OPC or DDE data server
RSView32 Alarm Summaries
Command lines embedded in graphics.
For a work-around, see AID 35209 - How to create an "embedded command line" in an RSView SE graphic).
User accounts created in RSView32 will not convert to SE user accounts
Some RSView32 Extensions
RSView 32 SPC - Use FactoryTalk Historian SE with Vantagepoint instead.
RSView32 Messenger - Use Specter Instruments Win911 instead.
Some ActiveX controls
Example: RSView32 TrendX Wrapper.
These will need to be evaluated on an individual basis to see how the desired functionality can be achieved in FactoryTalk View SE.
Commands That Cannot Be Executed from an View SE Event The following commands can be executed from a button or command line, but not from an View SE event:
Abort
Define
Display
DisplayClientClose
DisplayClientOpen
Download
DownloadAll
FlushCache
Help
Identify
Invoke
Key
NextPosition
NextWindow
OpenRSLogix5000
Position
PrevPosition
PrevWindow
PrintDisplay
PullForward
PushBack
RecipeRestore
RecipeSave
ScreenPrint
SendKeys
SetFocus
SuppressOff
SuppressOffAll
Undefine
Upload
UploadAll
Miscellaneous Notes
1. While RSView SE has a "System\User" tag, it is merely a carry-over from RSView32 and is non-functional. Use the CurrentUserName( ) function instead.
2. Certain ActiveX controls may not function as they did in RSView32. These will need to be evaluated on an individual basis.
For example:
The RecipePro ActiveX control interfaces directly with the RSView32 object model and therefore would not work with RSView SE.
1/3/12 27708 RSView32 to View SE Conversion Guidelines
The RSLadder ActiveX control does not depend on the RSView32 object model and therefore would operate in an SE graphic.
For details on RSLadder, see AID 45842 - Will RSLadder5 or RSLadder500 work with RSView SE?
2. RSView SE does support DDE client functionality, but the syntax will be different than in RSView32.
For example:
The RSView32 address RSLinx|MyTopic!'N7:0' would need to be changed to the following:
DDE:RSLinx|MyTopic!N7:
Please note:
DDE: needs to be inserted in front of the address.
There are no quotation marks around N7:0.
3. PLC5/SLC5 status registers must be addressed as S2: instead of simply S:.
For example:
RSLinx|MyTopic!'S:23' would need to be addressed as follows:
DDE:RSLinx|MyTopic!S2:23.
For further details on DDE client connectivity, see the FactoryTalk View Site Edition Users Guide, pub. no. VIEWSE-UM006F-EN-E–August 2010, Appendix B.
Additionally, it may be necessary in some cases to apply the solution from AID 26789 - DDE does not work in RSView SEs.
4. RSView32 introduced a new function, GetDayOfWeek() in version 7.3. While there is no equivalent SE function, a simple work-around is to use the VBA function
"Weekday". For more information on VBA's "Weekday" function, see the VBA help.
All RSView32 and RSView SE CommandsThe following matrix documents all RSView32 and RSView SE commands. Entries in red are commands that do not exist in either RSView32 or RSView SE. The Notes
column provides additional explanation and sometimes workarounds.
RSView SE Commands RSView32 Commands Notes
Abort Abort SE cannot issue Abort from an event
Account Launches User Account editor
Acknowledge Acknowledge
AcknowledgeAll AcknowledgeAll
Activity
ActivityBarOff
ActivityBarOn
ActivityLogSendToOdbc RSView SE 2.10 and earlier had this command. In SE 3.0 andgreater, go to the Tools menu and use D i a g n o s t i c s S e t u p - >
D e s t i n a t i o n S e t u p - > O D B C D a t a b a s e instead.
ActivityOff
ActivityOn
ActivityPrintOff
ActivityPrintOn
ActivityViewer
Alarm
AlarmAcceptEdits Added in CPR7+ to support runtime alarm edits in SE
AlarmEvent AlarmEvent
1/3/12 27708 RSView32 to View SE Conversion Guidelines
Suppressed Launches Suppressed List editor. Use RSView Studio instead.
SuppressOff SuppressOff
SuppressOffAll SuppressOffAll See AID 28274 - The message "The command 'SuppressOffAll' isignored when issued from a HMI Server" appears when used as anaction in an event for an SE HMI Server.. for a workaround
SuppressOn SuppressOn
Toggle Toggle
Undefine Undefine
Upload Upload
UploadAll UploadAll
VBAEdit VBA exists only in RSView graphics. Edit all code in RSView SEgraphics editor.
VBAExec VBA exists only in RSView graphics. Code can be called directlywithin an SE graphic.
DISCLAIMERThis knowledge base web site is intended to provide general technical information on a particular subject or subjects and is not an exhaustive treatment of such subjects.
Accordingly, the information in this web site is not intended to constitute application, design, software or other professional engineering advice or services. Before making
any decision or taking any action, which might affect your equipment, you should consult a qualified professional advisor.
ROCKWELL AUTOMATION DOES NOT WARRANT THE COMPLETENESS, TIMELINESS OR ACCURACY OF ANY OF THE DATA CONTAINED IN THIS WEB SITE AND MAY
MAKE CHANGES THERETO AT ANY TIME IN ITS SOLE DISCRETION WITHOUT NOTICE. FURTHER, ALL INFORMATION CONVEYED HEREBY IS PROVIDED TO USERS
"AS IS." IN NO EVENT SHALL ROCKWELL BE LIABLE FOR ANY DAMAGES OF ANY KIND INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS
PROFIT OR DAMAGE, EVEN IF ROCKWELL AUTOMATION HAVE BEEN ADVISED ON THE POSSIBILITY OF SUCH DAMAGES.
ROCKWELL AUTOMATION DISCLAIMS ALL WARRANTIES WHETHER EXPRESSED OR IMPLIED IN RESPECT OF THE INFORMATION (INCLUDING SOFTWARE)
PROVIDED HEREBY, INCLUDING THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, AND NON-INFRINGEMENT. Note that
certain jurisdictions do not countenance the exclusion of implied warranties; thus, this disclaimer may not apply to you.
This page is best viewed in Internet Explorer 7, Firefox 3.5, Chrome 4, Safari 4 or newer.