2/6/2019 32590 - FactoryTalk View ME to FactoryTalk View SE Conversion - Reproduce some of the common FactoryTalk View ME functionality

FactoryTalk View ME to FactoryTalk View SE Conversion - Reproduce some of the

common FactoryTalk View ME functionality
32590 | Date Created: 08/04/2005 | Last Updated: 12/27/2018
Print
Access Level: TechConnect

Question
How do you convert a FactoryTalk View ME application to FactoryTalk View SE?

Environment
FactoryTalk View Machine Edition
FactoryTalk View Supervisory Edition

Answer
Important - This document will outline how to reproduce some of the common FactoryTalk View ME functionality in a FactoryTalk View
SE application. Once the application has been converted into FactoryTalk View SE (import feature), there are some manual steps
required to ensure that the application maintains similar functionality.

See 46786 - Converting RSView32 or FactoryTalk View ME Projects to FactoryTalk View SE

(//rockwellautomation.custhelp.com/app/answers/detail/a_id/46786) for a guide to using the import.

As FactoryTalk View ME and FactoryTalk View SE differ in their features and objects, some of these workarounds may include different
development methods (i.e. FactoryTalk View SE objects, event detector, derived tags, etc.).

However, the focus has been to reproduce similar runtime functionality.

This document is based on a FactoryTalk View ME application imported into FactoryTalk View SE Local application. For FactoryTalk
View SE Network application - create new HMI Server before you import MED file.

Intended Audience
It is assumed that the user of this document is quite familiar with the runtime functionality of the FactoryTalk View ME application.

It is also assumed that the user is familiar with the editors and Command Wizard of FactoryTalk View SE.

It is also assumed that the user is familiar with the features available in FactoryTalk View ME including FactoryTalk Security
configuration.

Although this document describes some of the steps for workarounds, it is not a complete resource. It is intended to assist the user that
is familiar with FactoryTalk View SE features, but unsure how to apply them for the converted application. If further detail is required,
please refer to the help files or the FactoryTalk Site Edition User's Guide
(http://literature.rockwellautomation.com/idc/groups/literature/documents/um/viewse-um006_-en-e.pdf) Publication Number VIEWSE-
UM006.

RSLinx Enterprise Configuration

In FactoryTalk View ME, there are two tabs in the RSLinx Enterprise configuration Design (Local) and Runtime (Target):

The Design (Local) configuration is unique to a computer (not the application) so it is not part of the import into FactoryTalk View SE.

If the same computer (as used to configure the FactoryTalk View ME application) is used for the FactoryTalk View SE import, the same
device configuration will exist. However, the shortcuts will have to be recreated.

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/32590/p/646/page/1 1/10
2/6/2019 32590 - FactoryTalk View ME to FactoryTalk View SE Conversion - Reproduce some of the common FactoryTalk View ME functionality
The Runtime (Target) configuration corresponds to the runtime computer. The Target configuration is offline to development and is
saved into the FactoryTalk View ME runtime file (.mer).

There is no Target configuration in FactoryTalk View SE, so this is not imported.

Project Settings
Although there is no single equivalent in FactoryTalk View SE to the Project Settings:

These settings can be reproduced.

The FactoryTalk View SE Client configuration will contain most of the Project Settings, except for two Project display size and project
window position.

These features can be configured on a per display basis in FactoryTalk View SE. Right-click on the desired display and select Display
Settings. Configure the display size and location.

If you would like the display to fill the desktop size, be sure to enable the Maximize Window option in the Client configuration. Then,
enable the Size to Main Window at Runtime option on the desired displays.

User Accounts
FactoryTalk View ME and FactoryTalk View SE both include the new feature FactoryTalk Security with some slight differences in how the
functionality is deployed between the two products.

In FactoryTalk View ME the user has the option to generate runtime file (.mer) for previous versions of FactoryTalk View ME (Multi-
Version Support). As a result FactoryTalk View Studio for FactoryTalk View ME has the ability to configure security for both 3.x and
newer versions the product.

Multi-Version Support is not a feature of FactoryTalk View SE and thus there is no option in FactoryTalk View SE to configure 3.x style
security. As a result some of the FactoryTalk Security configuration screens used in FactoryTalk View ME will not contain the 3.x options
when the project is migrated to FactoryTalk View SE.

During the migration from FactoryTalk View ME to a FactoryTalk View SE Stand-alone application FactoryTalk Security user accounts
and user groups remain available as they reside within the FactoryTalk Local Directory and not within each individual FactoryTalk View
ME project.

FactoryTalk Security configuration information is not migrated into the FactoryTalk View SE project. In order to maintain the same
functionality in the FactoryTalk View SE project as users had in FactoryTalk View ME users will have to assigned the traditional A-P
security codes as they had within the FactoryTalk View ME project along with specific permissions to resources within the FactoryTalk
directory that are now available within FactoryTalk Security configuration.

Please refer to the FactoryTalk View SE Help section entitled Setting up Security for specific instructions on setting up FactoryTalk
Security (formerly RSAssetSecurity).

It may be possible that some parts of the FactoryTalk View ME application were configured for use with specific usernames (for
e.g. Visibility animation, based on whether the logged in user equals Admin). If this is the case, any use of the tag System\User must be
replaced by the function CurrentUserName() . The tag System\User is contained within the System folder for migration purposes but is
not used/updated by FactoryTalk View SE.

Diagnostic List Setup

The Diagnostic List Setup is not converted into the FactoryTalk View SE project. This will need to be reconfigured manually.

In FactoryTalk View SE, select Tools-->Diagnostics Setup for configuration of the runtime Diagnostics log.

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/32590/p/646/page/1 2/10
2/6/2019 32590 - FactoryTalk View ME to FactoryTalk View SE Conversion - Reproduce some of the common FactoryTalk View ME functionality
There does not appear to be a method to send the Diagnostic messages to a printer or to automatically open the Diagnostics log viewer
during runtime, based on new activity messages.

However, there are other methods of viewing the activity logs.

1. Create a push button using the AppStart command to open the FactoryTalk Diagnostics Viewer program ("C:\Program
Files\Rockwell Software\FactoryTalk View Enterprise\ActivityLogViewer.exe")
2. Use the activity bar at the bottom of the runtime project (also appears during development). This activity bar can remain open all
the time, and will display activity messages as configured in the Diagnostics List Setup.

Global Connections
There is no equivalent to this editor in FactoryTalk View SE. As such, these settings will not be imported into the FactoryTalk View SE
application.

Refer to the section Monitoring a Tag to Execute an Event on how to reproduce this tag monitoring functionality. The code listed in
that section can be easily modified to set tag values or to execute Macro files.

There is one feature that is hardware specific, and this is the Remote Backlight Intensity property. As this feature applies to only the
PanelView Plus and the VersaView CE terminals, this property has no direct equivalent in FactoryTalk View SE.

Startup
The FactoryTalk View ME Startup settings are not converted into the FactoryTalk View SE application.

These settings can be reconfigured in the FactoryTalk View SE Client configuration. If necessary, create a startup macro in FactoryTalk
View SE to complete other startup tasks, assigning this macro in the Client Configuration.

Tags
The tag database will import into the FactoryTalk View SE application. There should be no required changes to the communications or
tags within the application.

Tag Database
Although the FactoryTalk View ME tag database will be converted during the application import, there are some things to note.

Block Tags are converted, but cannot be edited.

System\User is not available. Replace all instances with the function CurrentUserName() .

Graphics
This section will briefly describe the exceptions for importing FactoryTalk View ME displays into a FactoryTalk View SE application.
Below each topic, a list will describe the change of features in the FactoryTalk View SE application.

Displays
Display Number is not supported
Cannot be Replaced is not supported
Disable Initial Input Focus is not supported
Default displays (ex. [ALARM], [ACTIVITY], and [INFORMATION]) are not imported

Object Features
Caption text does not have word-wrap; A Carriage Return must be added to the caption text
Image Color does not exist in FactoryTalk View SE; set the Pattern Color in the FactoryTalk View SE object

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/32590/p/646/page/1 3/10
2/6/2019 32590 - FactoryTalk View ME to FactoryTalk View SE Conversion - Reproduce some of the common FactoryTalk View ME functionality
Objects Not Imported (no SE equivalent)
Pause
Next Pen
Alarm Acknowledge
Alarm Acknowledge All
Clear Alarm History
Print Alarm History
Alarm Silence
Alarm List
Alarm Status List
Alarm Banner
Alarm Status Mode Button
Clear Alarm Banner
Clear Activity
Clear All Activity
Reset Alarm Status
Print Alarm Status
Silence
Sort Alarms
Diagnostic List
Diagnostic Clear Button
Diagnostic Clear All
Information Acknowledge
Information Message Display
Go To Configure Mode Button
Return To Display (although a button is created, FactoryTalk View SE does not directly support this operation)

String/Numeric Input Box

The major difference between FactoryTalk View ME and FactoryTalk View SE for this object is the visual appearance. To reproduce the
borders offered by the FactoryTalk View ME object you will need to manually create a Panel object behind the FactoryTalk View SE input
box.

Numeric Input Cursor Point converts into a FactoryTalk View SE Numeric Input Box.
Does not import the Number of Input Characters; set the Width property (String).
Does not have Fill Character.
Does not have Optional Expression (for e.g. Used to scale User input).
Does not have Enter Handshaking.
Does not have Image.
Does not have Audio.
Does not have FactoryTalk View ME border properties.

String/Numeric Display
No Border (can manually create a Panel object in FactoryTalk View SE to reproduce the borders)
Displays Decimal points by default for Integers (Numeric)
No word-wrap; must define characters and lines (String)

Display Navigation
Return To button is converted, however it is not functional (no FactoryTalk View SE equivalent). Either delete this object or
configure it to open a specific display.
Close Display button is converted into FactoryTalk View SE (border properties are different)
Display List Selector is identical object as in FactoryTalk View ME.

Trend Display Object

Pause button is not converted into FactoryTalk View SE. To reproduce in FactoryTalk View SE, open the Trend properties dialog
and select the Display tab. Enable Display scrolling mechanism to show the trend control buttons (for e.g.. Pause, scroll, Home,

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/32590/p/646/page/1 4/10
2/6/2019 32590 - FactoryTalk View ME to FactoryTalk View SE Conversion - Reproduce some of the common FactoryTalk View ME functionality
End, etc.).
Next Pen button is not converted into FactoryTalk View SE. To reproduce the functionality in FactoryTalk View SE, open the Trend
properties dialog and select the Display tab. Enable and configure the Line Legend properties.

Advanced Objects
Login and Logout buttons are converted into the FactoryTalk View SE Button object.
Display Print button is converted into the FactoryTalk View SE Button object
Macro button is converted into the FactoryTalk View SE Button object
Shutdown button is converted into the FactoryTalk View SE Button object
GoTo Config Mode button is not converted and is removed. There is no equivalent in FactoryTalk View SE, but a Button object
with the Display Client Close command would be similar.

Key Assignments
These are imported into FactoryTalk View SE as Display Keys.
The imported display keys do not function in SE as they are converted to Invoke commands.
Example: an F2 key assignment in ME becomes an Invoke <objectname>.PressButton() function in SE.
When the display key is pressed in SE, an error similar to the following occurs:
One or more of the names were not know. The returned array of DISPIDs contain DISPID_UNKNOWN for each entry that
corresponds to an unknown name.
To prevent these errors, remove the Display Key assignment.

Libraries
Libraries are specific to the development PC, and the development software (i.e. FactoryTalk View ME or FactoryTalk View SE). As
such, FactoryTalk View ME library displays must be manually imported into FactoryTalk View SE.

One method to manually import a library display is to:

1. Right-click on Libraries in the application tree.

2. Select Add component into Project.
3. Navigate to and select the FactoryTalk View ME library display that you wish to import.

When a FactoryTalk View ME library display is imported, it will convert in the same manner as an application graphic display. Refer to
the above section Displays for information on how the display settings and objects are imported.

Images
The FactoryTalk View ME image files are imported automatically with the application.

Parameters
Parameter files are converted during the application import. These files are the same in FactoryTalk View SE as they are in FactoryTalk
View ME.

Local Messages
Local Message files are converted during the application import. These files are the same in FactoryTalk View SE as they are in
FactoryTalk View ME.

Alarms
FactoryTalk View ME alarms will not import into the FactoryTalk View SE application.

Also, none of the FactoryTalk View ME alarm objects are supported in FactoryTalk View SE.

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/32590/p/646/page/1 5/10
2/6/2019 32590 - FactoryTalk View ME to FactoryTalk View SE Conversion - Reproduce some of the common FactoryTalk View ME functionality
All of the FactoryTalk View ME Alarm objects will have to be manually recreated in FactoryTalk View SE, using the Alarm Summary
object. In FactoryTalk View ME, alarms are based on trigger values and are configured on a per trigger (tag or expression) basis in the
Alarm Setup.

In FactoryTalk View SE, alarms are based on thresholds and are configured on a per tag basis in the Tag Database editor if using HMI
Alarms or by using a Tag Alarm and Event Server, if you plan on using FactoryTalk Alarms and Events

In order to reproduce this functionality in FactoryTalk View SE using HMI Alarms, each alarm message must be configured by using
thresholds in the FactoryTalk View SE Tag Database editor. For a FactoryTalk View SE Application using Alarm and Events, you can set
the threshold under <Alarm and Event Server name> --> Alarm and Event Setup. For details on Alarm and Events Alarms see 51676 -
Using FactoryTalk Alarm and Event Functions in CPR9 (//rockwellautomation.custhelp.com/app/answers/detail/a_id/51676)

Alarm Messages
In order to reproduce the FactoryTalk View ME alarm functionality, an alarm threshold will have to be configured for each alarm
message.

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/32590/p/646/page/1 6/10
2/6/2019 32590 - FactoryTalk View ME to FactoryTalk View SE Conversion - Reproduce some of the common FactoryTalk View ME functionality

To do this with HMI Alarms, create alarm thresholds that are just below and just above the desired
trigger value (ex. Use 1.9 and 2.9 as thresholds for a trigger value of 2).

For Expression Triggers

1. Create a memory tag (to hold the value of the alarm expression)
2. Enable alarming for the tag (Tag Database Editor), and configure the alarm thresholds as
described in the below section For Tag Triggers.
Ex. For expression values of 1, 2, and 3, you could use threshold values of 0.9, 1.9, and
2.9.
3. Open a new/existing Derived Tag file.
4. Select the memory alarm tag created in (1), and add the alarm expression
5. Save and close the derived tag file
6. Create a new Macro that uses the Derived On command to start the Derived Tag file.
7. Assign the macro as the startup macro in the Client Configuration.

For Tag Triggers

1. Open the Tag Database editor, and select the tag that you wish to configure alarming for.
2. Check the box beside the Alarm button, and an alarm dialog will appear.
3. Select Threshold 1, and enter a threshold value slightly less than the intended trigger value.
Ex. For a trigger value of 1, enter 0.9
4. Ensure that the Increasing option is selected and define any of the other alarm options if
desired.
5. Continue to add thresholds for each required trigger value. Ex. For trigger values of 2, 3 & 4
add threshold values of 1.9, 2.9, & 3.9.
6. Once all the thresholds have been defined, add a final threshold that exceeds the last
trigger value. Ex. If the last trigger value is 4, add a threshold of 4.9
7. Change the alarm severity of the last threshold to 8 (lowest severity). Close the alarm
dialog and accept the tag.
8. Open the Alarm Setup editor, and select the Alarm Severities tab.
9. Disable alarm logging for severity 8.

These workarounds will produce the FactoryTalk View ME alarm functionality. However, there are
some things to note about this method:
Only 7 trigger values can be defined for a single tag. A new tag will be necessary in order
to allow for more than 7 trigger values.
Only 7 alarm severities can be used for alarms, as the last one (8) is used for the “closing”
alarm threshold.

With Alarm and Event alarms, you can define Alarms and Messages in the Alarm and Event Setup see 51676 - Using FactoryTalk Alarm
and Event Functions in CPR9 (//rockwellautomation.custhelp.com/app/answers/detail/a_id/51676) for details.

Alarm Setup
The Alarm Setup information is not imported into the FactoryTalk View SE project. This information will need to be manually entered into
the FactoryTalk View SE Alarm setup editor and on a per tag basis under the HMI Tags. Also, any direct reference alarm triggers in
FactoryTalk View ME will need to be recreated as HMI Tags within FactoryTalk View SE.

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/32590/p/646/page/1 7/10
2/6/2019 32590 - FactoryTalk View ME to FactoryTalk View SE Conversion - Reproduce some of the common FactoryTalk View ME functionality
FactoryTalk View SE HMI Alarms does not directly support expression alarms. An equivalent is to create a derived HMI tag from the
FactoryTalk View ME trigger expression and then add alarming to the HMI tag. See Expression Triggers
(/app/answers/detail/a_id/32590/p/646/page/1#expression) above.

FactoryTalk View SE Alarms does not support the Message To Tag functionality from the FactoryTalk View ME Alarm Setup.

Also, some other steps are required if the Alarm display is to be opened based on new alarms.

One option to open the Alarm display automatically is to monitor every alarm tag as described in the below section Monitoring a
Tag to Execute an Event (/app/answers/detail/a_id/32590/p/646/page/1#monitor).
It may be less effort to monitor a single tag and have the programmable logic controller change the tag’s value when an alarm
occurs.

The second solution is only valid if the PLC can easily determine an alarm condition. Otherwise, a combination of both solutions may be
needed.

Monitoring a Tag to Execute an Event

This section describes how to monitor a tag for changes, and then execute events (such as opening a display) based on the tag value.

Adapted from the FactoryTalk View SE User Forum Graphic Displays VBA does not run at client. Written by Marc Semkow. The VBA
code in a graphic provides a means of implementing this functionality. Follow these steps:

1. Using FactoryTalk View Studio, create a screen with a numeric or string display. The tag used in this display object will be what
tells the VBA code which command to execute.
2. From the Edit menu select Display Settings. Change Cache after display to Yes and check Always Updating.
3. After creating the display object, right-click on it (ex. Object name is NumericDisplay1) and select VBA code. This launches the
VBA editor and creates a subroutine called NumericDisplay1_Change
4. Add the following code to the subroutine:

On Error GoTo ObjectErrHandler

Select Case NumericDisplay1.Value
Case Is = 1
ExecuteCommand "display screen1"
Case Is = 2
ExecuteCommand "display screen2"
Case Is = 3
ExecuteCommand "display screen3"
Else
MsgBox NumericDisplay1.Value & " is not one of the tested values."
End Select
Exit Sub
ObjectErrHandler:
MsgBox "There is a problem with the screen selector tag. Verify communications."

When the tag being used in NumericDisplay1is set to the value 1, the first Case condition evaluates true. This executes the display
command and shows the specified screen. The tag could be set by an event, or even in the data table of a PLC.
Also, it is highly recommended that this screen be loaded into memory when the client is launched using the command DISPLAY /ZA .
This will allow the screen to be Cache Display Always Updating, meaning it is run in the background and keep the tags on scan.

Global Objects
The FactoryTalk View ME Global Objects will be imported into the FactoryTalk View SE application.

Language
The FactoryTalk View ME language switching functionality will be imported into the FactoryTalk View SE application.

RecipePlus
https://rockwellautomation.custhelp.com/app/answers/detail/a_id/32590/p/646/page/1 8/10
2/6/2019 32590 - FactoryTalk View ME to FactoryTalk View SE Conversion - Reproduce some of the common FactoryTalk View ME functionality
The FactoryTalk View ME RecipePlus functionality does not exists in FactoryTalk View SE and will not be imported into the FactoryTalk
View SE application.

Symbol Factory
Symbol Factory objects will be imported into the FactoryTalk View SE application.

Color Animation
Shading is a new color animation feature in FactoryTalk View ME version 6.0 and higher. Objects that use this type of animation will be
converted into FactoryTalk View SE with the appropriate shading color animation.

ActiveX Controls
The following ActiveX controls have been added to the FactoryTalk View ME installation package with version 6.0:

Program Launcher
DataStore Plus
Recipe 2 Enhanced
ME IP_Info
Set Bit Cursor Point
MacroTen
Custom String Pop-up Keyboard
Display Control
ME_Email Sender
RSView Web Browser (included in previous versions of FactoryTalk View ME)

These ActiveX Controls will be imported into FactoryTalk View SE in full, including any Connections configured in FactoryTalk View ME.

Program Launcher
DataStore Plus
Set Bit Cursor Point
MacroTen
Custom String
Display Control
RSView Web Browser

The ME_Email Sender, Recipe 2 Enhanced, and ME IP_Info ActiveX controls may convert into FactoryTalk View SE but will not function
properly.

Information
There is no equivalent of the Information Messages in FactoryTalk View SE.

The Information Setup configuration and the Information Messages will not be imported into the FactoryTalk View SE application.

The Information Message files can be manually imported, and the Information messages functionality can be reproduced by creating a
new display.

1. Use Windows Explorer to manually change the extension of the Information Message file from *.ifm to *.loc
2. In the FactoryTalk View SE application, right-click on Local Messages in the application tree. Select Add Component into Project.
3. Navigate to and select the .loc file you modified in step (1).

The Information Setup configuration is not imported into the FactoryTalk View SE application. In order to reproduce this functionality in
FactoryTalk View SE, you will need to perform the following steps.

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/32590/p/646/page/1 9/10
2/6/2019 32590 - FactoryTalk View ME to FactoryTalk View SE Conversion - Reproduce some of the common FactoryTalk View ME functionality
1. Create a display using the Local Message object, and assign the imported Information Message file.
2. Follow the steps in the section Monitoring a Tag to Execute an Event to trigger the Information Message display, based on a tag
(named Value tag in FactoryTalk View ME)

Logic And Control

The FactoryTalk View ME macros will be imported into the FactoryTalk View SE application.

Macros
The FactoryTalk View ME macros will be converted into FactoryTalk View SE macros. Essentially, they are the same with a small syntax
difference. FactoryTalk View ME uses {} around tags names (when necessary) in the Macro file, however FactoryTalk View SE simply
precedes the tag name with the ampersand ‘&’. You will notice this difference in the FactoryTalk View SE macro editor, as it displays the
macro file in the text format (FactoryTalk View ME displays the macro as a spreadsheet).

Data Log
The FactoryTalk View ME data log files will be imported into the FactoryTalk View SE application.

Data Log Models

The data log models will be imported into the FactoryTalk View SE application with the following exceptions:

FactoryTalk View SE Data log model does not have Maximum Data Points setting (Setup tab)

Workaround
In FactoryTalk View SE, use the File Management tab to configure how data log files will be created and deleted (based on time or
event).

Attachments

DISCLAIMER
This 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 11, Edge, Firefox 41, Chrome 46, Safari 9 or newer.

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/32590/p/646/page/1 10/10