power steering fill machines - ps.nafta.extra.fcagroup.com

Manufacturing Engineering

General Assembly

ICT LAUNCH MANAGEMENT PLANT FLOOR DEVICE STANDARD

(MEGA.ICT-8519-04_A.01)

Power Steering Fill Machines

ICT Requirements

ICT LAUNCH MANAGEMENT

NAFTA Region PLANT FLOOR DEVICE STANDARD

Power Steering Fill MACHINES

(FCA US LLC ICT Requirements)

Owner: ICT Launch Management of 15 Revision: 2.4

Document: Power Steering Fill ICT Standard Revised: 05/08/2019

Power Steering ITM Standard Rev 2.4(MEGA.ICT-8519-04_A.01).Docx PROPRIETARY

Document Number: APGL14701

1) OVERVIEW

This document summarizes the current ICT requirements for new Machines to be purchased

and installed in Fiat Chrysler Automobiles (FCA) US LLC Assembly Plants.

This document is managed by the ICT Assembly System Launch Management Group

(ASLM) of FCA US LLC. For the latest version of this document, please contact a member

of this group.

Please refer to the latest Corporate Controls Standards (previously known as the BOIG; Book

of Implementation Guidelines) for specific controls information.

Deviations to equipment from this document must be approved through the launch deviation

process.

2) SCOPE

This document applies to new equipment built from 12/1/2003 forward. It does not imply that

any existing equipment shall be modified to meet these requirements. It can be used as a

reference for existing equipment that is being refurbished.

3) OPERATION OF EQUIPMENT

QAS operation guideline (Refer to ICT documentation for additional requirements)

1) A standard Fill machine is CLx based

2) A single Ethernet connection is required, 2 communications ports will be utilized, one for

solicited PFS data, the second for unsolicited QAS downloads.

3) QAS will be utilized to deliver style information to the processor.

4) Limit switches will be used by the OEM to track the position of their fill heads

5) The operation shall not be performed without a known valid VIN number

6) Pass/Fail fields should default to a Z (bypass) at the start of a cycle. As each test or function

is executed, the appropriate Pass or Fail should be entered in the correct field.

7) A Handheld scanner is required for backup; Hand scanned data will override all VIN's

currently in the machine.

8) Utilize a Panel view to allow the operator to correct failed read conditions; this Panel view

will allow the operator to enter the correct VIN number, hand scanning should be performed

prior to going to Panel-view and inputting manually the VIN

Fixed Scanner Operation (Refer to ICT documentation for additional requirements)









1) A standard Fill machine is CLx based

2) A fixed barcode scanner shall be used to identify the Vehicle Identification Number (VIN).

3) Fixed scanner operations will request Style information from AVI utilizing the PFCS

Ethernet network (DCM network connection not required).

4) Utilize a limit switch, beyond which the incoming VIN number scanned by the fixed reader

is buffered until the current operation is complete.

5) Have a handheld scanner for backup purposes.

6) Utilize a Panel view to allow the operator to correct failed read conditions, this Panel view

will allow the operator to enter the correct VIN number, hand scanning be performed prior

to going to Panel-view and inputting manually the VIN

7) Hand scanning operations will request Style information through PFCS to AVI.

8) Hand scanned data will override all VIN's currently in the machine.

9) Send the VIN number to PFS along with the process data in the format specified below.

10) The operation shall not be performed without a known valid VIN number.

11) Pass/Fail fields should default to a Z (bypass) at the start of a cycle. As each test or function

is executed, the appropriate Pass or Fail should be entered in the correct field

4) GENERAL PROCESS FLOW

This is a general process flow from the ICT perspective:

1. Vehicle enters station

2. Limit switch signals the PLC to turn barcode scanner on

3. Scanner reads VIN into PLC

4. PLC turns scanner off

5. PLC Requests style information from AVI

6. Equipment signals to operator IF valid style information have NOT been read

7. If no information received,

a. Operator scans using handheld barcode reader.

b. Equipment requests style information from Broadcast through PFCS (this is a backup

path for style information).

8. Operator connects equipment to vehicle.

9. If a valid VIN is identified, and style information is received, the Operator performs the

machine function.









5) AVI (AUTOMATIC VEHICLE IDENTIFICATION)

If a scanner is used in the system, then AVI standards apply, specifically to hardware model

numbers and the requirement for items such as beam control and stack lights.

Refer to BOIG documents 14.1.1, 14.2.2 (PLC-5 implementations) or 14.3.2 (CLx

implementations), and 14.2.3 (PLC-5 implementations) or 14.3.3 (CLx implementations), for

detailed AVI Reader Implementation information.

If the system is CLx based:

1) A Barcode reader requires an ICT Clx processor in slot 9. AVI and PFCS drivers

will be installed in this processor.

2) A QAS download with no barcode reader will require that PFCS drivers are installed

in the OEM processor and no ICT CLX is required.

3) A QAS Download will require a handheld scanner as a backup.

6) FIS (FACTORY INFORMATION SYSTEM)

This equipment is required to connect to FIS for diagnostic and production information

reporting. Use the following bitmap to configure the equipment for FIS reporting.

POWER STEERING BITMAP Word[Bit

Number] DINT state_code TEXT

0[02-15] FAULTED GLx WRONGPROGRAM DOWNLOADED

0[16-31] FAULTED GLx MODULE FAULT

1[00-09] FAULTED Ipxx POWER CB NOT ON

1[10-12] POWER OFF DIAGNOSTIC POWER OFF

1[13-15] POWER OFF CONTROL POWER OFF

1[16-31] POWER OFF E-STOP PUSHED/SAFETY PINS PULLED

2[00-15] FAULTED E-STOP /C-STOP /SAFETY PINS FAULT

2[16-19] PROD STOP CYCLE STOP

2[20-31] SPARES SPARES

3[00-10] FAULTED I/O RACK FAULT









3[11-31] FAULTED MRS SAFETY FAULT

4[00-09] POWER OFF MASTE RRESET REQUIRED

4[10-13] OUT OF AUTO CYCLE ENABLE RESET REQUIRED

4[14-18] OUT OF AUTO FAULT RESET REQUIRED

4[19-25] OUT OF AUTO NOT READYFOR AUTO

4[26-31] OUT OF AUTO WAITING FORSTARTUP

5[00-01] OUT OF AUTO NO MODE SELECTED

5[02-12] OUT OF AUTO MACHINE MODES "MANUAL/ CALIBRATEMODE/ MAINTENANCE MODE/ NO MODE….etc"

5[13-14] BYPASS BYPASS MODE

5[15-16] BYPASS ADAPTOR REMOVED PHOTO-EYE BYPASSED

5[17-22] IDLE IN IDLE STATE

5[23-27] FAULTED MOTOR OFF

5[28-29] FAULTED AIR OFF

5[30-31] FAULTED FLUID OFF

6[00-09] FAULTED FILL MOTOR OVERLOAD TRIPPED

6[10-31] FAULTED TANK xx OVERFILL FAULT

7[00-09] FAULTED VALVE O/L TRIPPED FAULT

7[10-16] FAULTED VOLUME TRANSDUCER FAULT

7[17-31] FAULTED VOLUME SENSOR FAULT

8[00-16] FAULTED VACUUM TRANSDRE FAULT

8[17-31] MAINT. ASSIST TANK xx OVERFILL FAULT

9[00-09] FAULTED BOOSTER EXTEND/EXTRACT FAULT

9[10-15] FAULTED ADAPTER CLAMP PRESS LOW

9[16-25] FAULTED ABS CPU FAULTS


10[00-31] MAINT. ASSIST TANK xx LOW FAULT

11[00-15] FAULTED VACUUM SENSOR FAULT

11[16-31] SPARES VACUUM FAULTS/ALARMS

12[00-15] FAULTED PRESSURE SENSOR FAULT

12[16-31] FAULTED FILLOVER-PRESSURE FAULT










14[00-15] FAULTED xxxNxx SHORTED SOLENOID FAULT

14[16-31] FAULTED xxxNxx OPENSOLENOID FAULT

15[00-31] FAULTED DNETNODE xx FAULT

16/17[0-31] FAULTED PFCS FAULTS

EX. MAINT. ASSIST PFCS DRIVER'S FAULTS

EX. MAINT. ASSIST PFCS SOL.RESPONSE ERROR

EX. MAINT. ASSIST PFCS SOL.MESSAGE ERROR

EX. MAINT. ASSIST PFCS SOL. MESSAGE RESP. TIMEOUT

EX. MAINT. ASSIST PFCS UNSOL. RESPONSE ERROR

EX. MAINT. ASSIST PFCS UNSOL. MESSAGE ERROR

EX. MAINT. ASSIST PFCS UNSOL. MESSAGE RESP. TIMEOUT

EX. MAINT. ASSIST PFCS NOCLIENT COMM DETECTED

EX. MAINT. ASSIST PFCS ETHERNET SLOT ERROR

EX. MAINT. ASSIST PFCS ETHERNET WCC IP ERROR

EX. MAINT. ASSIST PFCS UNDEFINED STYLE RECEIVED

18[00-31] FAULTED E-NET COMMLOST TO CLX(xxx) FAULTS

19[00-10] ALARM STYLE CHANGED MANUALLY

19[11-15] FAULTED HMIxx COMMUNICATION LOST

19[16-19] STARVED BLOCKEDUP STREAM

19[20-23] BLOCKED DOWN BLOCKED DOWNSTREAM

19[24-31] ALARM PROCESSOR's ALARMS/CLx BATTERYLOW,….,etc

20[00-15] FAULTED MODULES FAULTS


21[00-31] QUALITY ALERT CYCLES FAULTS

EX. QUALITY ALERT ADAPTOR VACUUM TEST CYCLE FAULT

EX. QUALITY ALERT INITIAL PRES. CHECK CYCLE FAULT

EX. QUALITY ALERT POWER STEERING OVERALL TEST (P)ass/(F)ail

EX. QUALITY ALERT VACUUM LARGE LEAK CYCLE FAULT

EX. QUALITY ALERT VACUUM SMALL LEAK CYCLE FAULT

EX. QUALITY ALERT FINAL VACUUM CYCLE FAULT

EX. QUALITY ALERT VACUUM LEAK DECAY CYCLE FAULT

EX. QUALITY ALERT FILL ABORT CYCLE FAULT









EX. QUALITY ALERT FILL TIME EXCEEDED CYCLE FAULT

EX. QUALITY ALERT STABALIZE TEAT (P)ass/(F)ail/(Z)NO TEST

EX. QUALITY ALERT PRESSURE TOLERANCE ALARMS

EX. QUALITY ALERT AIR PRESSURIZATION TEST(P)ass/(F)ail/(Z)NO TEST

EX. QUALITY ALERT FILL OVERPRESSURE CYCLE FAULT

EX. QUALITY ALERT FILL VOL.< MINIMUM CYCLE FAULT

EX. QUALITY ALERT/FAULTED PREMATURE PRESSURE FAULT

EX. QUALITY ALERT/FAULTED HIGH CAR PRESSURE FAULT

EX. QUALITY ALERT FILL VOL.> MAXIMUM CYCLE FAULT

22[00-01] MAINT. ASSIST PARAMETER CHANGES ADJUSTMENT/MODIFICATION

22[02-03] MAINT. ASSIST FLUID FILL PASS/FAIL-QUALITY ALERT

22[04-05] MAINT. ASSIST PARAMETER SCREEN NOTIFICATION/CHANGES USED BY PASSxxx

22[06-07] MAINT. ASSIST NOTIFICATION PASS. CHANGED

22[08-09] MAINT. ASSIST TIME COUNTER EXCEEDED LIMIT -MAINT. ACTIVITY

22[10-13] MAINT. ASSIST CALIBRATION CHECK/VERIFICATION VALUES CHANGED

22[14-15] MAINT. ASSIST FLUID PRESSURE SUPPLIES LOW-"UNDER SET POINT"

22[16-17] MAINT. ASSIST PORTABLE PUMPING STATION TOTES LOW

22[18-19] MAINT. ASSIST PORTABLE PUMPING STATION TOTES EMPTY

22[20-31] MAINT. ASSIST SPARES

23[00-31] POWER OFF/FAULTED/ALARM CIRCUIT BREAKERS/FUSES ALARMS

24[00-31] FAULTED SPARES

25[00-31] FAULTED SPARES

7) PFCS (PLANT FLOOR COMMUNIATIONS SYSTEM)

The device shall conform to PFCS Vendor Specifications:

1. The connection to PFCS shall be made via Ethernet (TCP/IP). (Must be made through a

dedicated NIC, not through a switch or router internal to the machine)

2. Have a unique IP address assigned by the plant.

3. Have a unique Machine ID(s) and DCNO Port(s) assigned by the Plant ICT group.









4. Use PFCS group-certified communication software (a combination of the hardware,

firmware and software). No device will be connected to the FCA US LLC network until

this certification process has been completed.

5. If operation requires unsolicited data downloads from PFCS (QAS), it must receive this

download on a separate port. One port sends data to PFS and VIN requests to AVI, the

other port receives unsolicited QAS VIN and Style data.

6. Utilize the USD communications driver.









8) PFS (PERFORMANCE FEEDBACK SYSTEM)

Every machine will be tested at the OEM's facility for its ability to communicate to PFS

before delivery to the assembly plant. Please contact your ICT ASLM representative for more

information.

DATA FORMAT

Start End Length Description Format

1 4 4 Machine ID, PC01, etc.

5 7 3 Ack/Nak Area (spaces)

8 13 6 Message Sequence Number (refer to PFCS vendor specs)

14 17 4 Request Type (0002)

18 21 4 Data Byte Count (position 22 to the end, exclude <CR>)

22 25 4 Number Of Records In Block (0001)

26 27 2 Filler Spaces

28 33 6 Last 6 Of VIN

34 39 6 Last 6 Of Track Number If VIN Is Zero

40 51 12 Date and Time (YYMMDDHHMMSS)

52 52 1 Power Steering Overall Test (P)ass/(F)ail (P/F)

53 55 3 Vacuum Value @ 3 Seconds (mmHg) (xxx)






71 73 3 Evacuation Time To Achieve 15 mmHg (xx.x)

74 74 1 Large Leak Test (P)ass/(F)ail/(Z)No Test (P/F/Z)

75 77 3 Large Leak Value (mmHg) (xxx)

78 80 3 Large Leak High Tolerance(mmHg) (xxx)

81 83 3 Large Leak Low Tolerance (mmHg) (xxx)

84 84 1 Final Vacuum 1 Test (P)ass/(F)ail/(Z)No Test (P/F/Z)

85 87 3 Final Vacuum 1 Value (mmHg) (xx.x)









88 90 3 Final Vacuum 1 High Tolerance (xx.x)

91 93 3 Final Vacuum 1 Low Tolerance (xx.x)

94 96 3 Final Vacuum 1 Test Time (Sec) (xx.x)

97 97 1 Vacuum Leak Decay Test (P)ass/(F)ail/(Z)No Test (P/F/Z)

98 100 3 Vacuum Leak Decay Value (mmHg) (xx.x)

101 103 3 Vacuum Leak Decay High Tolerance (xx.x)

104 106 3 Vacuum Leak Decay Low Tolerance (xx.x)

107 109 3 Vacuum Decay Value @ 1 Sec (mmHg) (xx.x)



116 118 3 Vacuum 2 Time Set Point (Sec) (xx.x)

119 121 3

Vacuum 2 level (mmHg) (actual vacuum achieved @ end of

V2) (xx.x)

122 125 4 Flowrate (Liters/min) (x.xxx)

126 129 4 Clamp Pressure (If Available) (xxxx)

130 130 1 Final Fill Volume (P)ass/(F)ail/(Z)No Test (P/F/Z)

131 134 4 Final Fill Volume Value (mL) (xxxx)

135 138 4 Final Fill Volume High Tolerance (xxxx)

139 142 4 Final Fill Volume Low Tolerance (xxxx)

143 143 1 Final Fill Time (P)ass/(F)ail/(Z)No Test (P/F/Z)

144 146 3 Final Fill Time Value (Sec) (xx.x)

147 149 3 Final Fill Time High Tolerance (xx.x)

150 152 3 Final Fill Time Low Tolerance (xx.x)

153 153 1 Final Fill Pressure (P)ass/(F)ail/(Z)No Test (P/F/Z)

154 156 3 Final Fill Pressure Value (psi) (xx.x)

157 159 3 Final Fill Pressure High Tolerance (xx.x)

160 162 3 Final Fill Pressure Low Tolerance (xx.x)

163 166 4 Overall Cycle Time (Sec) (xxx.x)

167 167 1 Fault During Cycle (Y)es/(N)o (Y/N)

168 170 3 Fault Code (xxx)

171 171 1 (V)olume Fill Or (P)ressure Fill (V/P)









172 172 1 Console Number (1,2,3) or (A,B,C) (x)

173 173 1 Operator Abort During Cycle (P)ass/(F)ail (P/F)

174 174 1 Late Start (Past Start Zone) (Y)es/(N)o (Y/N)

175 175 1 End of Travel Actuated During Cycle (Y)es/(N)o (Y/N)

176 176 1 (H)and Scanner/(M)anual VIN entry/(Q)as (x)

177 178 2 Internal Program Style Selected (xx)

179 180 2 Broadcast/QAS Download Style Received (xx)









9) ACCEPTANCE CRITERIA

QAS DOWNLOAD

QAS Downloads will be sent unsolicited on the machine ID ending with a letter (example:

PF0A). A handheld scanner shall be used as a backup device should QAS not be functioning.

The handheld scanner will make its request, and gets its reply, on the machine ID ending with

a number (example: PF01).

This is a sample QAS style download for a Power Steering fill machine:

Start End Len Field Name Description

1 4 4 Machine ID’s: PF0A, PF0B…

5 7 3 Spaces

8 13 6 Message Sequence Number Refer to PFCS vendor specs

14 17 4 0003

18 21 4 Data byte count Position 22 to end, exclude <cr>

22 23 2 Aa Broadcast Message Type Code

24 25 2

Bc

B=Model year

C=plant code

26 31 6 Last 6 of the VIN

32 41 8 Label Barcode

42 43 2 Vehicles status

44 49 6 Track Sequence number

50 51 2

Style download to device 00 – Invalid style

01-89 plant specific engine type

90 No Op condition









10) ACCEPTANCE CRITERIA

This is a summary of the ICT acceptance criteria required of the vendor; please refer to the

FCA Do’s and Don’ts for more detail.

1. PFCS certification must be completed before:

The device can be attached to the plant network

PFS data certification can be conducted

2. PFS certification must be complete before the device ships to the plant.

3. AVI standard point certification must be followed if an AVI barcode reader is used;

this includes testing at the OEM prior to equipment shipping.

4. FIS certification is required.

5. The following line items are examples of what must be tracked in the OEM timeline:

1. ICT Hardware Design

2. ICT Software Design

3. ICT Communications Testing At FCA US LLC (PFCS)

4. ICT System Testing At OEM (PFS Functionality)

5. ICT System Testing at FCA US LLC Assembly Plant









Document Revisions

Doc.

Rev.

Date

Doc.

Rev.

Number

Doc. Rev.

Description

Page No.

Revised

11/12/03 1.0 Initial Draft N/A

12/09/03 1.1 Expand BOIG 1

Remove reference to Broadcast 3.7

Add statement about default PFS string values 3.10

Remove reference to Broadcast 4.8.b

Reorganize PFS Data, group Pass/Fail Fields 8

Add Operator Abort Field 8

Add End of Travel Abort Field 8

Acceptance criteria clarified 10.5

2/09/09 1.2 Removed all references to ‘Daimler’ & ‘DCX’ Header, All

12/4/05 1.3 Revise PFS data field to match process spec 8

7/9/05 1.4 Modified PFS data string to match current process

specs

8

Added QAS wording 3

Added QAS wording 3

10/6/05 1.5 Remove requirements for additional CLx processor

when working with QAS

3

2/27/07 1.6 Note that hand scanner is required for backup to QAS 3.6

Add Clx details to hardware 5.1

4/6/07 1.7 Delete diagram 9

Add QAS download information 9

Add direction for PFS values in the volume fill field

when this is a pressure fill

8

2/09/09 1.1 Removed all references to ‘Daimler’ & ‘DCX’ Header, All

Change ITM to ICT All









Doc.

Rev.

Date

Doc.

Rev.

Number

Doc. Rev.

Description

Page No.

Revised

02/01/17 2.0 Converted to New MEGA form All

Added FCA Logo Header

Reorganize PFS Data, group Pass/Fail Fields 8

04/12/17 2.1 Updated PFS Data String 8

Change Chrysler to FCA US LLC All

Added step 3 in section 7 7

07/11/17 2.2 Added FIS bit map 6



power steering fill machines - ps.nafta.extra.fcagroup.com

Documents