DM Loader Issue

[MarkTTU]

When using DM Loader and setting the $ProdcutVersion to "Check" I'm seeing "ProductVersion verified" in the Update Log window in DM Loader even though the version I'm trying to load is different (and older) than the version that's currently in the PLC. DM Loader then continues on to load the older version. Based on the way the documentation reads I was expecting DM Loader to prompt the user with some kind of notification along the lines of "Found version MM.mm.bbbb in the PLC, are you sure you want to overwrite that version with version MM.mm.bbbb?"

Not sure I understand the use case for $ProductVersion... is it simply a repeat of the $ProductID functionality?

[MarkTTU]

One other curiosity question.... why are $ProductID And $ProductVersion hex values, but stored in DINT locations? Makes them a bit cumbersome to work with.

[BobO]

$ProductVersion doesn't appear to be working right. I'll dig some more.

Intention? $ProductID must match to continue and $ProductVersion should warn when trying to downgrade.

As for the format, I guess I could have made it different for $ProductID, but $ProductVersion is using hex nibbles for digits...0x01010003 = 1.1.3. This a very common way of doing versions. Trying to edit that in decimal would be painful...specifically 1642755 = 1.1.3. Setting it from DmD is easy: MOVE 0x01010003 $ProductVersion. To view in Data View, just change the format to hex, and to view the result in a Ladder View, just right click on the field and select hex from the menu.

[BobO]

Actually, it seems to be fine after all. I fat-fingered the version when I entered it. Just make sure that you get it right at both ends, using the proper formatting on the DmD side.

[MarkTTU]

I thought we were on the same page for functionality, glad to know we are 

Hmm.... ok, just tried this again and still not seeing it do what I thought it would do.

In the CPU I have a project with version 0x00030003, used a DM Loader file for version 0x00010060 and got confirmations that $ProductID and $ProductVersion were both verified and then it acted like it was loading a new program. Upon completion the code in the PLC is still version 0x00030003 so it didn't load new ladder, maybe new firmware? I expected it to prompt me and ask if I was sure I wanted to downgrade and then downgrade if I said yes. It didn't prompt/warn and it didn't load the older code either.

If it helps I'm doing all this over Ethernet to the Do-more CPU's built-in Ethernet port.

My dig on the HEX was mostly towards trying to display the version on a touch screen. Wound up just printing to a string and all is good. For the record I'm LOVING the string functions! So powerful and extremely useful!

[MarkTTU]

Correction. It did go ahead and load the old version into the PLC.... too many hours trying to multi-task 

[BobO]

Yeah...but it is broke on the verify. It's comparing the image's ProductVersion to the PLC's ProductID. The pain of reuse by cut and paste. I'll fix and send you an updated copy.

[MarkTTU]

Has anyone told y'all lately that YOU GUYS ROCK! ?

Posted this at 1p, had email from Bob at 7p with an apology and the fix. Seriously? 6hr turnaround? Wish I could get this kind of service from all our suppliers.

Just wanted to say thanks again!

[BobO]

Thanks for the kind words Mark. It was an easy fix.

Hope the utility is working to your liking...you inspired a big bunch of it.

[MAEdwards]

This is why HOST and their staff are amazing.