Hi,

I had the same problem for S120 drivers. Actually comunication module was working. When I sent start command it was taken start, but  it was not sending to Feedback Frequency (only 0). Then I removed Communication Module and replace it again. It solved.

Dear sirs

Is there anyone who can solve the problem?

My problem (r2 = 44) exists yet, And I do many things for starting my motor. But every time that I want to start the motor, the switch on inhibited alarm shows.

Power module : 6SL3210-1PE22-7AL0

Controller : 6SL3243-6BB30-1HA3

Motor : Asynchronous 

I also get this error but on a G120C... There is no separate communication module, there is no separate PM/CU... We got this between Christmas and New Year and we changed out the whole unit. Now we got it again on another one.

There is no safety configured nor has it ever been configured in this project. Of course there have not been any STO terminals wired. You should be able to run this FU without safety, right?

I do not understand is this a bug in the firmware or some strange idea of someone. Or maybe a hardware fault..?

And that every-80-hour reset is even more preposterous... To restart your installation every three days?!? Maybe it's configurable... I haven't looked into that but never the less....

nikola_hadjinikolov

I also get this error but on a G120C... There is no separate communication module, there is no separate PM/CU... We got this between Christmas and New Year and we changed out the whole unit. Now we got it again on another one.

There is no safety configured nor has it ever been configured in this project. Of course there have not been any STO terminals wired. You should be able to run this FU without safety, right?

I do not understand is this a bug in the firmware or some strange idea of someone. Or maybe a hardware fault..?

And that every-80-hour reset is even more preposterous... To restart your installation every three days?!? Maybe it's configurable... I haven't looked into that but never the less....

 You can disable the safety, and you if you don't , you can increase the restart monitor to 8000 hours. When you disable the safety functionalities from the drive, remember to save Ram-To-Rom and after that power cycle the drive before the change take affect.

Hati

 

nikola_hadjinikolov

I also get this error but on a G120C... There is no separate communication module, there is no separate PM/CU... We got this between Christmas and New Year and we changed out the whole unit. Now we got it again on another one.

There is no safety configured nor has it ever been configured in this project. Of course there have not been any STO terminals wired. You should be able to run this FU without safety, right?

I do not understand is this a bug in the firmware or some strange idea of someone. Or maybe a hardware fault..?

And that every-80-hour reset is even more preposterous... To restart your installation every three days?!? Maybe it's configurable... I haven't looked into that but never the less....

 You can disable the safety, and you if you don't , you can increase the restart monitor to 8000 hours. When you disable the safety functionalities from the drive, remember to save Ram-To-Rom and after that power cycle the drive before the change take affect.

There is no safety to disable as I already said... It has not been enabled.
The maximum restart monitor time is 9999 hours. And what does this mean? You cannot have plants that run constantly for 400+ days without a stop with a Siemens drive? I strongly doubt that.

Next week I will receive the frequency converters from the client and I will fiddle with them locally. I will enable safety and then try to activate the E-stop and see it if reacts in some way. Maybe update the firmware because it's 4.7.10 currently in the drives.
There MUST be a way to run these drives without safety at all... It has been before and it has to be a way now!

I had the same issue with a Sinamics G120C.

My solution was to wire digital inputs number 4 and 5 with the 24V output of the CU. Commissioning the driver with this inputs as F DI, turn it completely off and then checked that the drive was ready to run. 

After that i started a comissioning wizard turning off the safety integrated, removed the digital inputs wiring, reboot again the whole drive, and the problem was solved.

Edit: (I didn't try but maybe before doing all this, try to reboot the drive)

Hope this helps someone.