AutoGen_2671741

Please Note that the PLC_CRASH is a result of the 3000 NCK alarm note the cause. 

 Hello,

Please refer the attached sheet. (Extracted from Siemens manual)

DB10.DBX56.1 is signal for emergency stop. It is signal to NC from PLC. So when PLC gets crash, it sends signal to NC & 3000 alarm outputs.

According to me, after change in motor with different encoder, motor identification has not been carried out correctly, moreover during diagnosis, NC or PLC data/parameter might have been changed, which has made the work more difficult.

HTH.

Ahh. I stand corrected. Knowing that the motor has been changed with one of a similar type with the exception of the encoder and the fact that I am carrying the 3000 NCK alarm. Where might I begin trouble shooting to find what is holding me up. I'm imagining that if I were a field tech I would have some sort of generic attack plan when it comes to these types of situations. A general guide of sorts. For instance if this were a combustion engine that would not start I know that all I have to do is privide fuel, air, compression and fire. I realize this situation is a bit more complex then that but I'm not necessarily looking for simple just a starting point from which to trouble shoot. The 3000 NCK alarm isn't giving me much to go on or maybe it is and I just cannot see it. Also maybe it would help if someone could tell me how they would go about changing from one motor to another and I could start over from the beginning using their technique.

OK.

Please refer attached sheets which will give detailed information as how to commission Siemens motor & encoder. In drive CLiq Technic motor is identified but encoder needs to be configure.

HTH.

To follow the instruction that you provide I need to reset my NCU & PLC to factory setting to put the system into "Commisionning". This would require that I recommision both PLC and NCU. I have been reading the commisionning manual for my hardware and it has some pre-reqs.

-STEP 7 V5.5 ***I have this downloaded as a 14 day trial***

-STEP 7 Package for NCU7x0 on PG/PC(toolbox) ***I have not been able to locate this software. Any ideas?***

-GSD file ***no idea where to find this or what it is really***

-Compact Flash Card with CNC software. ***This I Have***

-External HMI or commissioning tool on PG/PC for the commissioning of internal HMI. *** It doen't tell me what sotware it is refering to***

Hello,

I suggest you to contact your nearest Siemens service support, since these s/w are not available with you. Even if you procure encoder equivalent to one, it needs to be align/configure. For this also you may need help from Siemens motor division technical support.

So please contact your nearest Siemens service support.

OK, Fine.

But does your company will allow you to keep a CNC machine under brake down for so long time? Step 7 is costly software.

Don't you think, it will be more costlier to keep machine under-brake down?

Instead with field technician/engineer support, the machine could be put back into operation. 

Problem Solved.

After receiving my new encoder I swapped out but still alarms persist. Different alarms but still no function. The encoder was brand new so it was apparent that the issue may not be the encoder. To prove the theory I traded the "X" & "Z" encoders thinking that if it were the encoder the problem would follow it. The problem did not. The alarms remained and after setting the "Z" home ref it was good to go. Next I tested the drive cliq cable trading "X" for "Z". Still the problem remained with "X". This left only the motor SMI, the S120 Drive itself, or the small section of cable inside the motor between the encoder and the SMI. I had an extra motor so I swapped the small section of cable inside the motor. I cycled the power and the axis came alive. I set the home ref and the machine lives once again. So, summory, don't take the alarms that are generated at face value. Check all possible simple possibilities first. My assumption cost me $700 for the new encoder(which was a bargain). Plus through unfortunate tinkering I destroyed the original encoder that in hind sight was a perfectly good encoder.