Hi everyone,
for learning I set up a basic MechSys_2AxCNCXY and have a simple CNC program running. I also configured some Monitoring Elements and they are working fine except for “Path information”, which outputs 0 for all its attributes.
“Path information” seems to be special, since the “Name of the path in a NC program” has to be provided. I found the AxesGroupFeature Path Definitions, which appears to me like a prerequisite to “Path information”. So I added “Path Definitions” to the axes group and used the name Path1 in both “Path Information” monitoring element and “Path Definition” feature. Still, “Path Information” outputs zero all the time
.
Question 1: Am I missing something? Why does “Path information” not output anything?
Question 2: Monitoring Elements also mentions “Path identification” (not information) but among all “single monitoring elements” this is the only one that AS 6.5 is not listing in the corresponding drop-down in configuration view.
I would appreciate any advice regarding this
.
Best regards
Lukas
Hello,
Question 1 : Am I missing something? Why does “Path information” not output anything?
If you have two PathDefinitions in your AxesGroupFeature PathDefinitions. You can set up the Monitoring Element for the Path Information like i did in the second picture.
Please Check the Logger if there is a Warning or Error about the Monitoring Element.
If you are still don’t see the expected values, we need to see your configuration.
Question 2 : Monitoring Elements also mentions “Path identification ” (not information ) but among all “single monitoring elements” this is the only one that AS 6.5 is not listing in the corresponding drop-down in configuration view.
This is a documentation error. It is still in documentation but it has been removed in transition from MappMotion 4.x to 6.x.
This can be read in this AS-Help Section.
mapp Robotics/CNC
I will create a CASE to let B&R check if this Documentation has to be updated in MappMotion 6.x version.
Greetings
Michael
Thanks Michael!
Quetsion 2: 
Question 1:
This is the axes group feature config, I have just one path Path1, that should be sufficient, right?:
This is my CNC-Prg, should I mention Path1 somewhere?:
%001 (CncProgram)
N10 G90 (absolute coordinates)
N20 F300 (Feed rate in measurement units/min)
N30 G01 X42.0
N40 G04 2
N50 G01 X0.0
N60 G04 2 (dwell time 2s)
And here is the logger, I tried to take care of any warnings before:
Regards
Lukas
Hello,
Did you add the Feature to the AxesGroup?
It has not to be mentioned in the CNC-Program. The System uses the intial Value from this setting. If Standard is selected it is the first Path.
Greetings
Michael
Ideed! I forgot to link the “Path definition” feature to the axes group.
I think I did such mistakes before, so I should have known better
. At the same time this nicely illustrates a paint point I was having with mappMotion so far: Errors in the configuration show up only at runtime (in the logger), if they are reported at all. For a newbie like me, this is rather time consuming. So if B&R finds ways to improve the experience here (for example checks/linting at build time), it will be much appreciated!
Thanks Michael and have nice weekend
Lukas
Hello,
Actualy i am happy that it is such a easy Solution, we all had this situation, missing this reference at a time.
Unfortuatly this can’t be checked by the compiler, because the Feature could only be a template which you would use during runtime. You can imagine to prepare two different sets of PathDefinition. With MC_BR_ProcessConfig you now only have to change the AxesGroup, instead of addtionaly changing the contend of the PathDefinition feature aswell. To allow such use Cases we do not check the references during build.
Greetings
Michael