md5 stuck sending firmware

What CAN to USB adapter are you using? We've had past issues with our Kvaser Adapters taking upwards of 24 hours to push the initial firmware. Have you tried pushing a program with IQANRun? You may need to Assign the Display to ID 0, every program needs a headmaster assigned. Also If you are pushing a new version of 7 that is a different version than what is currently on the display, it takes well over an hour on the initial push.

Tried both Kvaser and PEAK adapters, display ID = 0 and current firmware version is 7.02 on the display.

Made another attempt using a PEAK adapter, IQANdesign version 7.02 to flash just the MD5-5 display, waited over an hour and no success. On the display it shows 'Receiving baseline...' and progress upto 14 before it turns off (it takes around 20 minutes), did not cancel the flash and kept it going for another hour.

Is there a document or method that mentions how to conduct the initial flash?

I've tried this with a Kvaser, Ixxat, and Parker's G11 adapter and had similar results with a MD5-8. The first time I tried to send it a program out of the box it spent the first 20 minutes receiving a baseline to around 25% before the screen went completely black. The flashing process on the computer did not error and seemed to be continuing, so I let it be. The Flashes completed around 2 - 3 hours later, and new programs sent later to the same module went much quicker, without the screen going black, even when moving between different IQANDesign versions. I used 7.04 and 7.05 for these tests.

I'd love to know if there is a proper way to send that initial flash as making the space to flash a 3-hour update to every new display is going to be rough.

Ethernet is the fastest method to update.Updating over CAN has taken over 1 1/2 hours to update an MD5 from 7.05 to 7.06. Using Ethernet directly on the MD5 takes minutes.

The change to the high density Molex connector on the MD5s makes Ethernet a little more difficult than it was on the MD4s with the nice M12 connectors (yes I know Parker sells the M12 to Molex socket cable harness, but that is unquestionably not as convenient or reliable as having the M12s in from factory).

Updating firmware on multi-master systems is also still a pain, since you can only connect to one master at a time over Ethernet and the other master(s) then receive the firmware and application updates over the CAN diagnostic bus. I've found it better in a lot of cases to disconnect the other masters in the system and then update firmware one module at a time over Ethernet and then a system wide update with all modules on-line once I know all the modules are on the same firmware. Painful, but still much quicker than the CAN bus routing is in a lot of cases.

Thank you all for responding.

Using PEAK (over CAN) the following flashes of the MD5-5 was carried out:

'-initial flash - IQANdesign v7.02 takes ~3 hours

'-2nd flash - IQANdesign 7.02->v7.05 takes ~30 minutes

'-3rd flash - IQANdesign 7.05-> v7.06 takes ~1 hour (major upgrade, you cannot revert back to anything <v7.06)