News:

  • June 28, 2026, 04:50:10 PM

Login with username, password and session length

Author Topic: Version "Contamination" Question on DmD  (Read 8526 times)

Mike Nash

  • Hero Member
  • *****
  • Posts: 652
Version "Contamination" Question on DmD
« on: September 22, 2017, 11:04:42 AM »
I have Windows set to allow double-clicking on a .dmd project and it opens it in v2.0.3.

Since I have already updated a couple of BRX with an H2 still to go, I would like to change the association to v2.1.0.

If I open older v2.0.3 (or even v1.4.x) with v2.1.0, does it "mess up" those .dmd projects by default, or only if I try to add v2.1.0 specific instructions?

I haven't tried it yet and this would only apply to offline projects.

But of course I would also like to know what to expect going online with an older PLC. (I did this yesterday but was intent on updating the BRX so I didn't pay enough attention to the info presented.)

P.S. Nothing has been "contaminated" as far as I know to this point.

franji1

  • Bit Weenie
  • Host Moderator
  • Hero Member
  • *****
  • Posts: 3827
    • Host Engineering
Re: Version "Contamination" Question on DmD
« Reply #1 on: September 22, 2017, 01:28:25 PM »
Designer 2.1 does passively "upgrade" the project to DmT 2.1.  If you save it to disk with 2.1, it will not be openable with 2.0.3.  If you try to write it to a PLC, it will not download unless the firmware is upgraded to DmT 2.1.

So, if you do NOT upgrade your firmware at this time, you need to open your DmT 2.0 projects using 2.0.3.

Possible alternative scenario
You could open the 2.0 Project in 2.1, do a Save-As to your 2.1 Projects folder, and do some offline work in 2.1.  So you would still have your DmT 2.0 project in your 2.0.3 Projects folder, your PLC would still be running DmT 2.0 with the 2.0.3 Project, but you would have an offline DmT 2.1 project "waiting in the wings" in your 2.1 Projects folder whenever you wanted to download it to a PLC with upgraded firmware with DmT 2.1 firmware.

franji1

  • Bit Weenie
  • Host Moderator
  • Hero Member
  • *****
  • Posts: 3827
    • Host Engineering
Re: Version "Contamination" Question on DmD
« Reply #2 on: September 22, 2017, 01:39:19 PM »
"DmT" means Do-more Technology version.  This is what defines the "contamination" level (your words, not mine  ;D)

We only bump the DmT level when we have to.  If we do, we set the DmT value equal to the Designer version (so far just the first two version level values, e.g. DmT 1.4 or DmT 2.1).

Designer 2.0.1 to 2.0.2 to 2.0.3 did NOT change the DmT level (DmT stayed at DmT 2.0).  Designer 1.4.1 to 1.4.2 to 1.4.3 also did NOT change the DmT level (DmT stayed at DmT 1.4).

Designer 1.3 to 1.4 did (DmT 1.3 to DmT 1.4).
Designer 1.4 to 2.0.x did (DmT 1.4 to DmT 2.0).
Designer 2.0.x to 2.1 did (DmT 2.0 to DmT 2.1).

Mike Nash

  • Hero Member
  • *****
  • Posts: 652
Re: Version "Contamination" Question on DmD
« Reply #3 on: September 22, 2017, 02:25:10 PM »
That's what I figured based on 1.4 to 2.0 and I am good with that. I just didn't want to be merrily looking at old projects and hosing myself. I almost always copy any kind of project to a temporary location to view it, but not everyone (including myself) remembers to do this every time.