Bench rig at school. CPU 1511-1 PN, SINAMICS G120C 0.75 kW on PROFINET, telegram 1, TIA V17. The motor runs from my program, speed changes, all of that works.
Every time I download and the CPU goes to STOP the drive shows F01910 and the fault LED goes red. I acknowledge it on the BOP and it's fine again until the next download.
I put a new PROFINET cable on it first, no change, then one of the lads said the drive config gets corrupted on a download, so I downloaded the drive configuration again and it still faults every time. Not sure now whether the drive is faulty or whether it's the cable, since it only happens on a download when there's a lot of traffic. Could someone explain what I've got wrong?
V17 here too. Does it fault only when the CPU goes to STOP, or also while the CPU is in RUN and you leave it alone for an hour? And post the CPU diagnostics buffer entry from the same time, the exact text.
Only on STOP. In RUN it ran an hour with nothing, so I think it's tied to the STOP. The CPU buffer at that time just says "CPU changes from RUN to STOP mode" and then on the drive "F01910: Fieldbus: setpoint timeout". Screenshot attached.
This is not a fault in the sense of something broken. F01910 means the drive expected a cyclic telegram with a valid setpoint and did not get one within the monitoring time in p2040. When the CPU goes to STOP the controller stops sending valid output data. The timer expires, the drive faults. Correct behaviour. A drive running on its last setpoint with nobody controlling it is worse.
Acknowledge on restart: bit 7 of control word 1, 0x0080, from the PLC, or on the BOP as you do now. Increase p2040 only if the process can tolerate a stale setpoint for that long. Yours cannot need that.
The telegram side of it is written up here: https://plctr.com/utilizing-plc-for-motor-control-and-drive-systems/
So the drive is right and I'm the problem. I was stuck on the cable for two days. Why does the CPU stop sending, though? It's still powered and the PROFINET LEDs are still green.
In STOP the outputs go to their substitute values, and for a PROFINET IO device the output data gets marked invalid. Green LEDs, no valid setpoint. I've left p2040 at default on every machine I've shipped. The fault acknowledge goes in the start sequence in the PLC and nobody sees it.
Understood now. Nothing to fix on the drive, the p2040 monitoring time runs out because the CPU stops sending a valid setpoint, and the drive is supposed to fault on that. I added a rung that pulses bit 7 of the control word on the first cycle after RUN, using the first scan bit, and the fault clears on its own after a download.
What I still don't understand is why it's a fault and not a warning, since nothing is damaged. Thanks gunther, tom.
Losing the master is a fault. A warning would let it keep running.