about syncbuffererror!!!

[Unicornai]

What is the cause of this error, I checked the manual and said that it was Error in synchronous variable assignment buffer, but I don't know what I did to cause this error? Could you please help me take a look

[leandro.martins]

What is the value for Coord[x].ErrorStatus?
Have you changed the Sys.PreCalc default value?

I would have a look at Sys.RtIntPeriod and Coord[x].SegMoveTime as well.

[MoMo]

Please provide a program that can reproduce the error.

[Unicornai]

On 11/17/2024 at 11:01 AM, MoMo said:

Please provide a program that can reproduce the error.

about M1==180000 it will come,the syncbuffererror

error prop.pmc

[MoMo]

1 hour ago, Unicornai said:

about M1==180000 it will come,the syncbuffererror

error prop.pmc 8.41 MB · 0 downloads

Please do not use synchronous M variables as line numbers in Power PMAC.
In Power PMAC, use Coord[x].Nsync to retrieve the line number.
In the program, you need to add N{data} X{data} Y{data}, and be careful not to add a : after N{data}.

Frequent use of synchronous M variable operations may lead to buffer overflow.

Edited November 18 by MoMo

[Unicornai]

because my hmi need Mvariables to mark  How many lines did the NC program run, And then use this line number to show the program on the HMI where it ran to? If this doesn't work, is there any other way to do it?

[leandro.martins]

You can have the M1 pointing to Coord[x].NSync.
 

M1->Coord[1].Nsync

 

[Unicornai]

15 hours ago, leandro.martins said:

你可以让 M1 指向 Coord[x]。NSync 的
 

M1->Coord[1].Nsync

 

So i need send m1->coord[1].nsync to pmac,and then i run this prog it will not appear this error(syncbuffererror)?

[leandro.martins]

[EDIT] Remove ":" after "N{data}", as noted by MoMo.

As MoMo said, you have to substitute M1=={data} by N{data} or your motion program, and this is the probable fix for the issue.
Making M1 point to Coord[x].Nsync is required because your HMI depends on that.

So assuming that the synchronous assignment is the only issue, the error should go away doing theses steps.

Edited November 22 by leandro.martins

[MoMo]

21 hours ago, leandro.martins said:

As MoMo said, you have to substitute M1=={data} by N{data}: or your motion program, and this is the probable fix for the issue.
Making M1 point to Coord[x].Nsync is required because your HMI depends on that.

So assuming that the synchronous assignment is the only issue, the error should go away doing theses steps.

N{data}: do not include :

the line numbers with : are used for jump.