zerbzhang

PPNC downloads and executes the NC file, and executes the first file to make it run normally, the running time is 45 minutes. After modifying, downloading and executing the NC file parameters again, the NC execution line has not completed the current line, but jumped to the next line for execution (two lines of code were executed at the same time), which caused an accident. In the attachment, G01 Z [#301] F0.5 is running, and the trajectory has not been completed. The speed is not the specified speed. G04 X1 has been activated. The trouble is that these two codes run at the same time. When the NC file does not complete the current line and enters the next line for execution, there is another problem with the axis speed setting, which is not what I expected. The motor is in the trajectory I specified, has accelerated to a speed (much greater than the specified F), and then started to decelerate to 0 and completed the trajectory at the same time. I asked all possible questions, but no results. I hope I can get help in the DT community. Due to this problem, the device has stopped functioning.

Jeff, thanks

Jeff, thanks for your reply. I don't know much about gpascii communication, I just started to learn to use Power Pmac. Can you provide some information for my study and reference? Thanks very much for your help.

By writing C language, using the "Command" command to read a configuration file, build and download it. I passed the query command, but the parameter was not assigned correctly. Command("system gpascii -2 -i/win/MYSETUP.txt"); Is this statement wrong? Or is there an introduction document for the API function Command/system gpascii. I need to customize some functions, and I hope the administrator can send me some documents about these introductions. "WRITING C FUNCTIONS AND PROGRAMS IN POWER PMAC" is just an introduction, there is no introduction of functions and commands.

HI, Geoff, I have some doubts about the settings; First of all, the index of the EncTable you defined is 10; but the index of the EncTable selected by your motor is 6? Can this match? Secondly, the data of your motor feedback comes from ECAT's IO data, I guess this is sensor data. Geoff, if it is convenient, attach the complete plan to facilitate our study. EncTable[10].type = 11 // Source register address: Motor control output register (FP) EncTable[10].pEnc = Motor[1].IqCmd.a // Data shifting operation: 5 = left shift this many bits (32 - bits of actual data) // Command output pointer Motor[1].pDac=Sys.pushm // Outer (position) loop position feedback pointer Motor[1].pEnc=EncTable[6].a // Inner (velocity) loop position feedback pointer Motor[1].pEnc2=EncTable[6].a Motor[1].pAbsPos=ECAT[0].IO[4102].Data.a

Eric you are right, I think this is part of the SDK. Because the SDK is not completely open at the moment, I see this MCF Developer's Guide 2.3.pdf document and feel that I can do HMI to solve the problems I am currently facing. This is just my thought. If the NC team does not help, this problem is indeed difficult to solve. I believe that other customers will encounter the same problem. Well this is actually an array issue and not an issue at all once you understand the system. The edits to make this work are on the ppmac side not the HMI side. The file ncinterfacedefinitions.pmh is where the edits take place then all will be write with the world. The axis order has everything to do with how the edits take place. I have run into this many times and very easy to correct. Thank you, I have to re-recognize Power pmac nc, I first try to modify the plc program to achieve the functions I need.

Eric you are right, I think this is part of the SDK. Because the SDK is not completely open at the moment, I see this MCF Developer's Guide 2.3.pdf document and feel that I can do HMI to solve the problems I am currently facing. This is just my thought. If the NC team does not help, this problem is indeed difficult to solve. I believe that other customers will encounter the same problem.

Eric ，thanks very much. Sorry for interrupting you to rest; I can solve this problem by myself. You can help me to consult the CNC team, how to get "MCF Application for Delta Tau (CS).zip". It is mentioned in MCF Developer's Guide 2.3.pdf. I can develop this function myself. Eric, thanks again.

Eric, I'm sorry to tell you that even if the code of G54 is modified, the data entered manually in workoffset. C cannot be set. The terminal correctly displays the data of P903. When I was debugging the program, I inserted a breakpoint in "btnCsSetALL", P900 had the correct "DisplayName", but P903 did not display my C-axis coordinate values. The code in WorkOffsets.xaml.cs has been executed correctly, but the variable is not assigned. What is the reason? At the same time, I found that the code of "Machine.cs" is also running correctly. ""{0}-axis work offset for {1}"" has been loaded successfully. In the MCF framework, P903 is not assigned, and P900-P902 are assigned correctly? If this is the problem, please re-write the assignment code to the variable that I cannot assign, and send me the correct .dll file (I have no permission to modify the MCF framework).

Eric, thanks for your reply. I use the ck3E in the simulation, this should be the B axis. I will modify it according to what you said, or please tell me to modify the g-xx code (should not be all?).

In the process of machining, the position of tool tip should be written into G54. The first problem is that when you press the workoffsets button and then the all button, only X, Y, Z coordinates are written into G54. even if the C button is pressed, the position of C will not be displayed in G54. C; Second, of course, the C coordinates of the tool tip can be manually written into G54.C. then, when the NC program is running, C does not participate in the calculation and does not work. Is this a bug? If so, this error is too low-level. I want to know how to get the coordinates of G54 X Y Z C, and at the same time, it works when running NC program.I have purchased the SDK. You can provide the setup document for me to modify.

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?

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

When power PMAC NC runs NC program, an error "interference move calculation time" is reported? Which document has a detailed introduction?

OK,THANKS

Eric，Appears after scanning the network. Through the help system of IDE, I found the reason for the error. 0x9811002E EC_E_MASTERCORE_INACCESSIBLE Master core not accessible RAS Connection to remote server was terminated or master instance has been stopped on remote side. But I don't understand, where is the root of the mistake? Through the EC engineer of IED V3, I can successfully communicate with the IO module. At this time, I export ei.xml. However, when I import ei.xml into IDE V4 that I am using, ECAT [0] cannot be activated. There are no errors and warnings. Enter $$$* * *, save, as always.

Today, I loaded three ECAT I / O modules. The EC engineer pop-up dialog box prompts: error: Master core not accessible(error code：0x9811002E ) I want to know why this error code appears? Is there a problem with my XML file? IDE output message: ECAT License for I/O only 0 VID=$00000021 PC=$07500354 0:0 PREOP + Slave_001 1 VID=$00000890 PC=$00100368 0:1 PREOP + Slave_002 2 VID=$00000890 PC=$00100750 0:2 PREOP + Slave_003 *** buffer overflow detected ***: /opt/ppmac/EcMasterDemo/EcMasterDemo terminated

I don't think that was necessary. The RMA wasn't either. To get a firmware update, you should email your local support channel, possibly your distributor or OEZ. That being said, your firmware is pretty up to date, I don't think firmware version is the problem. I think you just need a little help setting up your phasing. I will try to address this in the other thread. Eric, thank you so much for your reply. I have applied for Omron to repair 24e3 of power pmac. How long is the repair cycle?

I think you mean Gate3.Chan[j].CountError, but set it equal to 0 in a startup PLC. For these types of questions you should really reach out to your local support channel. If that doesn't work I'm happy to help, I don't want to leave anyone with a PMAC stranded, but please start with them. Thanks for your reply

This is likely unpredictable phasing. What are the values of the following variables? Motor[x].I2tSet Motor[x].PhaseFindingDac Motor[x].PhaseFindingTime Motor[x].AbsPhasePosOffset Motor[x].PhaseFindingDac=200 Motor[x].PhaseFindingTime=10 Motor[x].AbsPhasePosOffset=1877

My firmware version is 2.5.1.7 The machine tool adopts linear motor movement. After ppmac looks for the motor phase, the Open-loop test is passed. Restart at power PMAC, input at terminal #1 $, do the Open-loop test again, and the Open-loop test result will reverse. This problem has been going on for a long time. I checked 120 ° - hall feedback, gate3 [0]. Chan [0]. UVW is correct. This problem still occurs when searching motor phase in multiple positions. Acc24e3 temperature is very high, axle card has been applied for repair. I can't get rid of the Open-loop test problem, which is caused by CPU. I also reorder the power PMAC CPU. I want to upgrade the CPU firmware. Can you tell me the way to upgrade and send the latest firmware to my email?

The firmware version of power CPU with EtherCAT communication is ARM LS1021a？ What is the firmware of POWER PMAC CPU version without EtherCAt communication？

No, this is not normal. The 24E3 should come with a fan meant to be placed just underneath. Is it installed? Is the 24E3 in a cabinet? Does the cabinet have a fan? Thanks for your reply. The electric cabinet has fans. The temperature of other components is normal, including my driver. The power module of power PMAC has a fan, which has been installed correctly, and the CPU temperature is stable at 23-25 ℃. Through reasonable layout of components, the cooling fan of the driver can also cool the power PMAC.

There is another problem: After Power PMAC is started motor [x]. CountError = 1; 24E3 P/N 3-4002A6262-4646-B00 S/N P907081 At present, the problem is that after restarting power PMAC, the Open-loop test direction changes and cannot operate normally. I'm worried that the problem of 24E3 caused the reverse of Open-loop test. The ambient temperature is 18-22 ℃, and the temperature of 24E3 is above 70 ℃ after one hour of startup and operation. For debugging, I have searched for phases in multiple locations, and I have determined that the wiring of hall is shielded. Is it normal for the temperature of 24E3 to exceed 70 ℃? This is what I need to confirm If I can't solve this problem, I can only apply to Omron for repair.

Temperature is over 70 ℃, is it normal for 65536 digital subdivision axle card?