Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Abnormal error reporting——ppnc
#1
When power PMAC NC runs NC program, an error "interference move calculation time" is reported? Which document has a detailed introduction?
Reply
#2
Where are you getting this error message? I'm not used to seeing it from the Power PMAC NC Software. Are you able to post a screen shot of it?

Does it seem as though it's a particular line of code? If you have the ability to do a "dry run" or run on a virtual machine, can you comment out sections of the code and see if it is being caused by a particular line? If you comment out sections of the G Code starting at the end and working forwards, can you narrow in on a specific section that is causing the problem?
Reply
#3
(06-22-2020, 12:26 PM)AAnikstein Wrote: Where are you getting this error message? I'm not used to seeing it from the Power PMAC NC Software. Are you able to post a screen shot of it?

Does it seem as though it's a particular line of code? If you have the ability to do a "dry run" or run on a virtual machine, can you comment out sections of the code and see if it is being caused by a particular line? If you comment out sections of the G Code starting at the end and working forwards, can you narrow in on a specific section that is causing the problem?

thanks,AAnikstein.
When the NC program runs to line 9, an error is reported.


Attached Files Image(s)
       
Reply
#4
Can you provide a full screenshot of the PMAC NC Software? Particularly the Positions and the sections below that, showing (amongst other things) the G- and M-Codes that may be active at the time where it stops.

Do you have the Power PMAC IDE installed? If so, it may additionally be worth checking the value for Coord[x].ErrorStatus (most likely Coord[1].ErrorStatus if you are unsure), along with looking at the "Global", "Coordinate System", and even "Motor" tabs of the Status Window to see if any specific errors are showing up on one of the relevant pages for your system.
Reply
#5
(06-25-2020, 01:34 PM)AAnikstein Wrote: Can you provide a full screenshot of the PMAC NC Software? Particularly the Positions and the sections below that, showing (amongst other things) the G- and M-Codes that may be active at the time where it stops.

Do you have the Power PMAC IDE installed? If so, it may additionally be worth checking the value for Coord[x].ErrorStatus (most likely Coord[1].ErrorStatus if you are unsure), along with looking at the "Global", "Coordinate System", and even "Motor" tabs of the Status Window to see if any specific errors are showing up on one of the relevant pages for your system.
Thank you, AAnikstein. You are right. It is coord [x]. Errorstatus that causes this problem. Where can I query the information of PPNC alarm information?
Reply
#6
Coord[x].ErrorStatus can signal many different things depending on what value it takes--you can read what each of them means from the "Power PMAC Software Reference Manual" in the File Depot.

That said, though, we may be able to help more with troubleshooting the cause. One of our engineers thinks it may be caused by the fact that you are reversing directions [(10,0,10) -> (20,0,20) -> (30,0,30) -> (0,0,0)]. This may have caused a cutter compensation interference error, which is caused by a move in the opposite direction from the compensation. If this is the case, ErrorStatus would be equal to 10, and it would indicate that performing that move would likely result in an overcut.

Another thought could be that it's caused by some "leftover" active G-Code that may not have been initialized properly. If this is the case, showing all of your active G- and M- codes could give us an idea, in case anything is listed as active that wasn't set from your G-Code. This was why we had asked for a larger screen shot, showing the full PPNC window.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)