mappMotion XT in AS6.7 (McPathXT)

[krausertm (Marcel Krausert)]

Hi!

I’m currently trying to user a cutomer transformation with AS6.7 and stuck with the McPathXT. I installed the upgrade and the files are also there:

It obv. tells me in the logger it’s required, but compared to AS4 I can’t configure it, though it’s installed.

Also in the Change Runtime Version dialog there is no dropdown visible for the McPathXT, where as in AS4 there is.

no dropdown for McPathXT

In the Cpu.sw it’s still entered as Binary, but it doesn’t show up in the AS window (in AS4, it does).

In the project .apj I updated the version manually, since it still had 5.24 in there, but that also didn’t make any difference.

Now I’m at my wits end, help appreciated

Best Regards!

[krausertm (Marcel Krausert)]

So I managed to get it running, by manually adding the correct (IA32) McPathXT.br to my logical view and adding it as binary to the Cpu.sw.

No it’s working. Looks to me there’s a bug in AS 6.7.0.187?!

[kovarj (Jaroslav Kovar)]

If you see bug there, please report it to local support team.

[valerio.manenti]

I don’t see that issue on my side:

Ciao
Valerio

[krausertm (Marcel Krausert)]

You mix up quite a lot of stuff there:

1. Screenshot McPathGen
2. Screenshot McProfGen

My actual problem was: McPathXT, emphasis on XT

Best Regards!

[valerio.manenti]

Thanks Marcel,

you have triggered my curiosity…

I’m going to uninstall the standard libraries 6.7.2, 6.8.0 and install only XT versions…we will see

Ciao
Valerio

[valerio.manenti]

mapp Motion XT 6.7.0 (a little bit different, you have 6.7.2), but no issue:

[krausertm (Marcel Krausert)]

@valerio.manenti

ut no issue:

So the problem only exists if you have the normal + the XT version installed probably.

It’s most likely on some backlog already…

Thanks a lot for the follow up!

Best Regards!

[valerio.manenti]

just for sanity check same result with mapp Motion XT 6.8.0

Ciao
Valerio

[valerio.manenti]

@krausertm

It’s most likely on some backlog already…

correct, I see we have a CASE for that:

Problem description

Installation of mappMotion XT technology package is not possible after installation of standard package. The Change Runtime Version dialogue in Automation Studio will not provide McPathXT as option to insert.

Tested with V6.6.1

Containment action(s)

Delete effected TP from AS6 installation folder and install XT package again.

[zbynek_uher]

Hi colleagues! Your discussion here caught my attention, too. Let’s add some internals with experts here, since a content of installed packages or apj files was already investigated by you.

A content (libraries, system modules, version ranges, etc.) of any installed technology package (not only mapp Motion), incl. its title (and a bit more) in the “Change Runtime Versions…” dialog in the Automation Studio, is defined via a file [AS folder]\AS\TechnologyPackages\mappMotion\v.vv.v\ApplicationSettings\TP.cfg.

mappMotion is an exeptional technology package which has its XT and non-XT variants. System module McPathXT is a difference. However TP.cfg must respect that, too.

If one has certain mapp Motion version already installed (let’s say non-XT 6.7.2), and is installing the XT version with the same version number 6.7.2 later, missing folder and files in McPathXT are added, and other files in a tree [AS folder]\AS\TechnologyPackages\mappMotion\6.7.2 are overwritten based on their time stamps. In contrary, if XT was installed first, “additional folders and files” in McPathXT are not deleted. That mechanism ensures the user has the highest functions, no matter in which order it is installed.

I have checked 6.7.2 specifically for time stamps of TP.cfg, and found out that:

• non-XT: 10.4.2026, 11:32
• XT: 10.4.2026, 11:15

This explains your observed behavior, and causes even more unexpected effect that if mapp Motion 6.7.2 non-XT is installed after the XT version, then even though the McPathXT folder remains, a software title is changed from “mapp Motion (XT)” back to simpler “mapp Motion”, and “Advanced” checkbox does not offer McPathXT via the “Change Runtime Versions…” dialog any more.

RnD will fix this. Every good rule needs its exception – this forum is not the bug reporting platform but I take this issue with me. EDIT: Oh, there exists a CASE already.

• Note 1: Only recently generated versions are affected (no excuse)
• Note 2: The mechanism is the same for AS4 and AS6.

Until the fix, Valerio’s containment action (=delete previously installed package first) is the most consistent approach.

[krausertm (Marcel Krausert)]

Hi @zbynek_uher ,

nice to see you’re doing well!

Just to let you know: I installed XT after the normal version! It was also a fresh install of AS6 on this notebook, then mappMotion, then I requested XT and installed it afterwards!

Best Regards!
Marcel

[zbynek_uher]

Hi Marcel. Hello to you, too. A procedure matches. Timestamps I spoke about are the ones from *.exe technology packages, you cannot manipulate them directly. As far as I can see in tests I did, then

• Directories in [AS folder]\AS\TechnologyPackages\ have timestamps according to a time you installed the package
• However files inside derive the “main” timestamp from the technology package itself, so it is a time when our RnD release job really generated the file.

Actually, objects have several timestamps in Windows afaik (created, modified, last accessed) – but that’s too deep in operating systems.

I trust that if anybody installs non-XT 6.7.2, then [AS folder]\AS\TechnologyPackages\mappMotion\6.7.2\ApplicationSettings\TP.cfg has a timestamp 10.4.2026, 11:32. Therefore, this file is not overwritten by TP.cfg from the 6.7.2 XT variant (since this file is seen as 17 minute older: 11:32 vs. 11:15). Not for me only, for everybody.

This is nothing we want our users to think about, for sure. Therefore, we need to guarantee again that TP.cfg XT is newer to TP.cfg non-XT. And if I say “newer”, it means timestamps from the Technology package installer with no relation to who and when installs it.