4_SpecJLRPart4_1.2_170927
4_SpecJLRPart4_1.2_170927
4_SpecJLRPart4_1.2_170927
Part 4
Project
JLR using ControlLogix
1
JLR ControlLogix – DCP Specification
Modifications of History of Part4 (CMU)
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
2
JLR ControlLogix – DCP Specification
Contents
Modifications of History of Part4 (CMU)
3
JLR ControlLogix – DCP Specification
Part 4 – CMU
This chapter describes the standard software application of the CMU for a PanelView Plus 7, used as an
operator terminal for the L551 / Darwin project. It is controlled by the DCP standard software in the PLC.
System Memory:
– System: 1 GB
– User 512 MB
Communication:
– Two 10/100Base-T, Auto MDI/MDI-X Ethernet ports RS-232 Interface (upload / download / print).
Connection:
– Connected to a Stratix 5700 managed Ethernet switch located in an A2 panel.
Operating system:
– Windows CE with Extended Features and MS Office Viewers (includes FTP, VNC client server, ActiveX
controls, PDF reader, third-party device support)
4.2 Software
Software packages:
– Developing software: FactoryTalk View Studio for Machine Edition
– Communications software: RSLinx.
Standard CMU:
Each CMU is assigned to one PLC.
In the PLC, the Routine S_VersaView controls the data transfer with the CMU.
Specification of the sequence details displayed:
– Standard application with 30 sequences
– Display of the sequence step (max. 99 steps per sequence)
– 10 fault messages can be displayed at the same time
– PanelView Plus 7 supports up to 10,000 messages per Local Message File
– Display of the general message (1 fault line). Scroll function for up to 10 messages
– Display of the fault type, fault priority, operation modes, central status, sequence status, system
message, pages of the manual functions
– Display of 30 pages / sequence with 20 manual function keys / page, 20 for manual operations and
associated function text and 20 dedicated function keys present on every page
–
CMU Password
On power up the user must set as password,challenge and response to PanelView1
4
JLR ControlLogix – DCP Specification
Part 4 – CMU
Spare
Spare
Spare
NOTE: Access to the different screens and functions is possible from every screen from the dedicated buttons.
5
JLR ControlLogix – DCP Specification
Part 4 – CMU
The Main menu is used as the startup screen from here you can access the following screens by using the
dedicated buttons.
– Piece Counts
– Safety Overview
– User menu
– Online Screen
– Graphic Screen (for complex Stations)
– Active Fault Page (displays the associated manual page with highest priority fault)
– Online menu (sequence menu) via Sequence Selection menu (see chapter 4.2.2 and 4.2.3) and via Page
Selection menu (see chapter 4.2.4).
6
JLR ControlLogix – DCP Specification
Part 4 – CMU
NOTE: The visibility of the sequence selection is controlled by the zzSeq[*].Active flag in the PLC only active
sequences will be displayed
Sequence selection consists of 2 screens to change to DC Online screen:
– Selection of sequences 1 – 15 (screen no. 1 – 15) and displaying the status of sequences 16 - 30.
– Selection of sequences 16 – 30 (screen no. 16 – 30) and displaying the status of sequences 1- 15.
All configured sequences are displayed with sequence text and sequence status (station field).
7
JLR ControlLogix – DCP Specification
Part 4 – CMU
1
2
3
4
13
14 20
15
16
17
22
18
19
21
8
JLR ControlLogix – DCP Specification
Part 4 – CMU
The text for each message is generated from the per sequence document.:
– Step messages (line 2).
– Fault messages (line 4 – 14).
– Text of 30 pages of manual operation (line 16 page text, line 17-19 lamp text).
NOTE: The CMU Online screen number corresponds to the sequence number.
9
JLR ControlLogix – DCP Specification
Part 4 – CMU
The function soft keys located on the CM Online menu are used to select and execute the sequence related
functions, especially manual operations. 600 pushbuttons functions are available, selectable by 30 different
pages.
– SEQ. : Sequence selection and to toggle between the Sequence Selection screens.
– PAGE : Page selection and to toggle between the Page Selection screens.
If the operator presses “PAGE” on a screen the Page Selection screen is shown to choose one of the 30 pages
(15 pages selectable per Page Selection screen) of the current sequence displayed on the DC Online screen.
10
JLR ControlLogix – DCP Specification
Part 4 – CMU
– NOTE: The page titles and pushbuttons are generated from the per sequence sheets. Unused page and
pushbutton text must be deleted. The following pages show examples of the sequence document. The
sequence documents must be modified for the functions in each facility. As much description as possible
should be added to the display. (i.e. robot / station number / model types / sequence releases etc.)
– Examples sheets can be obtained from the Standards and Controls department.
11
JLR ControlLogix – DCP Specification
Part 4 – CMU
Page 4: Tip Dresser add up to 8 robots per sequence over two pages (R1 – R8)
12
JLR ControlLogix – DCP Specification
Part 4 – CMU
Page 5: Tip Dresser add up to 8 robots per sequence over two pages (R1 – R8)
13
JLR ControlLogix – DCP Specification
Part 4 – CMU
14
JLR ControlLogix – DCP Specification
Part 4 – CMU
15
JLR ControlLogix – DCP Specification
Part 4 – CMU
16
JLR ControlLogix – DCP Specification
Part 4 – CMU
17
JLR ControlLogix – DCP Specification
Part 4 – CMU
18
JLR ControlLogix – DCP Specification
Part 4 – CMU
19
JLR ControlLogix – DCP Specification
Part 4 – CMU
The communication between PLC and CMU is checked continuously. If an Fkey is pressed and an error occurs
the status of all Fkeys are reset after a user defined time (default = 2 sec.). The user can configure the time
period in the routine P_VersaViewParameters (should be as low as possible but must be 1.5 sec.).
The CMU blocks the Fkey function if the operator presses more than one Fkey
xx = sequence number
yy = page number
vv = pushbutton: upper line: vv = 1 – 10
lower line: vv = 11 – 20.
– NOTE: All functions must have a manual pushbutton assigned. This includes transition latches and special
functions programmed by the user.
20
JLR ControlLogix – DCP Specification
Part 4 – CMU
The PanelView Plus 7 supports up to 10,000 messages in each of the Local Messages. The user sequence
related data is in the associated Local Messages SeqData01 – SeqData30. The message text number is
independent of the trigger value.
Language 1
Trigger Contents
1 - 3199 Fault Descriptions (Matrix bit 1 - 3199)
3201 Step Counter number
3202 Step counter name
3203 PLC number
3301 - 3399 Step Description ( Step 1 - 99)
3401 - 3430 Page Descriptions ( Page 1 - 30)
4011 - 4310 Lamp Text top line ( 30 sides each with 10 lamps)
5011 - 5310 Push Button text ( 30 pages each with 10 buttons)
6011 - 6310 Lamp Text bottom line ( 30 sides each with 10 lamps)
Language 2
Trigger Contents
7000 - 10199 Fault Descriptions (Matrix bit 1 - 3199)
10201 Step Counter number
10202 Step counter name
10203 PLC number
10301 - 10399 Step Description ( Step 1 - 99)
10401 - 10430 Page Descriptions ( Page 1 - 30)
11011 - 11310 Lamp Text top line ( 30 sides each with 10 lamps)
12011 - 12310 Push Button text ( 30 pages each with 10 buttons)
13011 - 13310 Lamp Text bottom line ( 30 sides each with 10 lamps)
To generate the message data the user must select the language 1 (English) or 2 (Local Language) and press the
Generate VersaView Message File button.
21
JLR ControlLogix – DCP Specification
Part 4 – CMU
If language option 1 is selected the message trigger values will start at 1 if option 2 is selected the message trigger
values will start at 7000.
The generated messages are copied into the clipboard ready to paste into the local Message file for the
corresponding sequence.
NOTE: Do not modify the Layout of the Local Messages. Leave unused messages blank and do not change
the trigger value. Messages must be generated using the macro in the latest sequence document (available
from the JLR Standards and Controls department). It is not permitted to change the text in the Local
Message file. All changes must be generated from the sequence sheet.
22
JLR ControlLogix – DCP Specification
Part 4 – CMU
The user must paste the generated messages from the sequence chart in to the corresponding Local Messages
SeqDataXX.
23
JLR ControlLogix – DCP Specification
Part 4 – CMU
4.2.5 Graphic Display
Each sequence must be assigned to a graphic screen where practically possible. On the Graphic screen the
important state and position of the faulted sequence is displayed and the operator can choose and execute
the relevant sequence functions to fix the fault:
– Sequence description
– Current step
– Highest priority fault message
– States of the sequence and the line
– Fault position and corresponding page
The user must import the relevant picture into the selected graphic display screen.
24
JLR ControlLogix – DCP Specification
Part 4 – CMU
The graphics matrix trigger must be assigned on the sequence sheet and sent to the PLC.
NOTE: The Graphic screen number corresponds to the sequence number. The Graphic uses the same user
data as the corresponding CM online screen.
25
JLR ControlLogix – DCP Specification
Part 4 – CMU
The User screens (screen no. 50 and 100) offer possibilities to design machine specific screens related to
user functions.
The user is responsible for the selection of the user screens, unused preconfigured screens can be removed
from the project. The screens highlighted in yellow must be used for all facilities. Screens highlighted in red
must be used for facilities with robots in addition to the yellow highlighted screens.
26
JLR ControlLogix – DCP Specification
Part 4 – CMU
User Safety Area (screen no. 50) Example
The user must import a suitable picture of the line layout that clearly show the stations, gates and emergency
stop locations. As a minimum, the safety screen should display (via a flashing graphic) the operation of all
safety devices. Additional graphical information can be displayed if it would be beneficial of the JLR
operators.
The user must assign the go to display buttons and the local message titles for the user screens required.
27
JLR ControlLogix – DCP Specification
Part 4 – CMU
User Screen (screen no. 101)
28
JLR ControlLogix – DCP Specification
Part 4 – CMU
Type Flow (screen no. 103)
The user must configure the Type Flow page(s), to show the type in each robot / station. The layout of the
screen should depict the actual layout and flow as closely as possible.
29
JLR ControlLogix – DCP Specification
Part 4 – CMU
The user must configure the User Cycle Time page to show the cycle time in each robot / station. The layout of
the screen should depict the actual layout and flow as closely as possible.
The user must configure the detailed safety page to show All the Safety Area devices programmed. The user
must assign the go to display buttons, screen and local message titles for the safety area functions required
30
JLR ControlLogix – DCP Specification
Part 4 – CMU
Build Indicator (screen no.107) User defined (normally to turn build types on/ off)
Robot Paths (screen no.108) User defined to shown complex / special robot paths
The user must configure a graphic for all the Stratix switches used on the facility.
31
JLR ControlLogix – DCP Specification
Part 4 – CMU
The user must configure the cycle time and local messages for the robot / station. This gives the overall zone
cycle time. (the last 10 times are to be shown).
The user must configure the cycle time and local messages for each robot (the last 10 times are to be shown).
32
JLR ControlLogix – DCP Specification
Part 4 – CMU
The user must configure the cycle time and local messages for each station (the last 10 times are to be shown).
33
JLR ControlLogix – DCP Specification
Part 4 – CMU
The user must configure the Tip Change screens for all welding robots. Screens 132-138 can be used for SA Tip
Change these are user defined.
The user must configure the Tariff screen for each Power Monitoring Unit.
34
JLR ControlLogix – DCP Specification
Part 4 – CMU
The user must configure the Power Monitoring screen for each Power Monitoring Unit.
The user must configure the Power Monitoring Details screen for each Power Monitoring Unit.
35
JLR ControlLogix – DCP Specification
Part 4 – CMU
36
JLR ControlLogix – DCP Specification
Part 4 – CMU
The user must add and configure each detailed safety screen with the correct POP UP graphic and parameters
for all safety devices. Additional navigation buttons must be added if a second screen it required.
37
JLR ControlLogix – DCP Specification
Part 4 – CMU
Local Messages are used to allow language switching. The user must use local messages on any user screens
created.
38
JLR ControlLogix – DCP Specification
Part 4 – CMU
The user must add the CMU title name in the PLC. For each CMU add the Title to the zzVv[*].CMUTitle
Navigation
For each CMU the “CMU_Seq_Page_Scroll” Addon instruction is used in P_VersaviewParameters. The user
needs to add this instruction for all CMU’s on the line.
The user must set the Global connection for each CMU.
39
JLR ControlLogix – DCP Specification
Part 4 – CMU
Global Boarder
For new screens the global border needs to be added and the title parameter inserted.by the user.
Select the border and copy. On the new screen paste the border
CMU Font
The CMU requires the Lucida Console Font to display the messages correctly. If the font is not present on the
CMU the user must load the lucon.ttf file into the c: windows/fonts directory and reboot. The font will be
automatically load from the font directory on restart.
the PLC
40
JLR ControlLogix – DCP Specification
Part 4 – CMU
The table below shown the typical display update time settings. The user must set the required times for new
screens added into the CMU.
41
JLR ControlLogix – DCP Specification