HP Color LaserJet 4730 HP Color LaserJet 4730mfp - Software Technical Referenc - Page 327

Printer messages during the firmware update, Table, 9 Update messages

Page 327 highlights

Engineering Details The elapsed time for an update depends on the I/O transfer time, as well as the time that it takes for the product to reinitialize. The I/O transfer time depends on a number of things, including the speed of the host computer that is sending the update and the I/O method (parallel or network). The reinitialization time depends on the specific hardware configuration of the product, such as the number of EIO devices installed, the presence of external paper-handling devices, and the amount of memory that is installed. Finally, any print jobs that are ahead of the RFU job in the queue are printed before the update is processed. Use one of the methods described in this manual to update your product firmware. Printer messages during the firmware update The following table lists the causes and results of possible interruptions to the firmware update. Table 7-7 Troubleshooting a firmware update Cause Result The job was cancelled from the control panel. No update has occurred. A break in the I/O stream occurred during send (for example, No update has occurred. the parallel cable was removed). A power cycle occurred during the RECEIVING UPGRADE process. A power cycle occurred during the PERFORMING UPGRADE process. A power cycle occurred during the INITIALIZING process. No update has occurred. No update has occurred. Resend the update through a parallel port. The update has been completed. Print jobs that are sent to the product while an update is in process do not interrupt the update. All HP LaserJet products leave the factory with the most recent firmware version installed. If a remote firmware update fails in a Windows OS, the .RFU file must be resent. For more information, see Table 7-9 Update messages. If a remote firmware update fails in a Macintosh OS, contact support from an HP Customer Care Center. The following table lists possible reasons for the failure of a remote firmware update and the corrective action required for each situation. Table 7-8 Troubleshooting a firmware update failure Reason for firmware update failure The .RFU file is corrupted. The wrong product is contained in the .RFU file. Corrective action The product recognizes that the file is corrupted and rejects the update. Download the file again and send the new file to the product. Download the file from www.hp.com/go/clj4730mfp_firmware. The product recognizes the printer mismatch and rejects the update. Download the correct file and send it to the product. Download the file from www.hp.com/go/ clj4730mfp_firmware. ENWW Remote firmware update 305

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372

The elapsed time for an update depends on the I/O transfer time, as well as the time that it takes for the
product to reinitialize. The I/O transfer time depends on a number of things, including the speed of the
host computer that is sending the update and the I/O method (parallel or network). The reinitialization
time depends on the specific hardware configuration of the product, such as the number of EIO devices
installed, the presence of external paper-handling devices, and the amount of memory that is installed.
Finally, any print jobs that are ahead of the RFU job in the queue are printed before the update is
processed.
Use one of the methods described in this manual to update your product firmware.
Printer messages during the firmware update
The following table lists the causes and results of possible interruptions to the firmware update.
Table 7-7
Troubleshooting a firmware update
Cause
Result
The job was cancelled from the control panel.
No update has occurred.
A break in the I/O stream occurred during send (for example,
the parallel cable was removed).
No update has occurred.
A power cycle occurred during the
RECEIVING UPGRADE
process.
No update has occurred.
A power cycle occurred during the
PERFORMING
UPGRADE
process.
No update has occurred. Resend the update through a parallel
port.
A power cycle occurred during the
INITIALIZING
process.
The update has been completed.
Print jobs that are sent to the product while an update is in process do not interrupt the update.
All HP LaserJet products leave the factory with the most recent firmware version installed. If a remote
firmware update fails in a Windows OS, the .RFU file must be resent. For more information, see
Table
7-9 Update messages
.
If a remote firmware update fails in a Macintosh OS, contact support from an HP Customer Care Center.
The following table lists possible reasons for the failure of a remote firmware update and the corrective
action required for each situation.
Table 7-8
Troubleshooting a firmware update failure
Reason for firmware update failure
Corrective action
The .RFU file is corrupted.
The product recognizes that the file is corrupted and rejects the update. Download
the file again and send the new file to the product. Download the file from
www.hp.com/
go/clj4730mfp_firmware
.
The wrong product is contained in
the .RFU file.
The product recognizes the printer mismatch and rejects the update. Download the
correct file and send it to the product. Download the file from
www.hp.com/
go/
clj4730mfp_firmware
.
ENWW
Remote firmware update
305
Engineering Details