0
Fixed

MD5 running 7.03 turns blank during update

C. Harp 1 month ago in IQANdesign updated by Gustav Widén (System support) 1 day ago 5

We have recently found a big problem when attempting to update an MD5 screens over CANbus or G12’s. 

The firmware will start to send and get roughly 30% complete before the screen goes blank and dark. 

Design shows to still be sending the file but the screen is unresponsive. You can power cycle after this crash and it will show no program message. 

The only way to fix this seems to be with Ethernet connection.  We have had 3 Md5’s now with this same issue and becoming a major problem, as several customers have relied on G12 update support on the field.

Based on my experiences with MD5 displays this is just normal behaviour.

Sending the first program to factory new MD5 via can bus takes about 40 - 60 minutes to be completed and yes the display goes dark until restarting at the end. I haven't tried to use ethernet but I will try if it's faster. 

When sending updated program with the same software version it goes through in seconds.

This is not a factory new unit. This is one that is making a small firmware update jump. Believe 7.03 to 7.05. 

Yes, Ethernet takes only seconds to send firmware updates. 

I believe the symptom has to do with the version 7.03 in the module prior to starting the update. 


There was a problem in 7.03 that could made the MD5 display turn black after a longer period ( >15 min) of inactivity. 

This was fixed in 7.04 but isn't listed in release notes. 

MD5 version 7.05 files are smaller than 7.03 (down to 45 MB from >120 MB), but sending a 45 MB file over 250 kbps CAN is still very slow. 

Ethernet is for sure the best option. 

To make practical use of CAN and G12 for field updates, I think the higher diagnostics CAN speed you can have with 7.05 is necessary. 

Fixed

I changed the title from "MD5 crash during update" to "MD5 running 7.03 turns blank during update".

This problem was fixed in 7.04.