Hi,

I am working with 1516-3PN PLC. I configure the technology object S200 servi drive. After configuring the technology object, if i made the changes in any DB/FC every time "Changes to the technology object  cannot be applied in RUN" this error came & plc went into stop mode.

What setting I needs to change to resolve this issue.

Hi there,

regarding the overflow message, perhaps the content from this FAQ might be helpfull: https://support.industry.siemens.com/cs/ww/en/view/109973555

And about the "Changes to the technology object  cannot be applied in RUN" message:

If there is a change at any motion technology object (check the icons in the project tree on the left when you're online on the PLC), and the TO is active on the PLC, then you cannot download this change, therefor this message.

If this appears without any difference at a TO, but only with differences at other DBs/FC/whatever, then it might be, that the change done there leads to a change in an instance-DB that inherits an MC_Power instruction of a TO that is currently active. In short: You can also not download a change that affects MC_Power of a currently active TO.
There is also an FAQ about this point, see here for closer details and better explanation: https://support.industry.siemens.com/cs/ww/en/view/109781646

If none of this is the cause, well then we'll have to check closer, I guess. But then my suggestion would be to contact customer support about this. Provide information what you changed and where, provide the project and information about the error that appears, as well as the used versions of TIA Portal and the firmware on the PLC.

Regards,
daviso

Hi,

Thanks for your response daviso

Actually I used 9nos servo drive in my project. All drives connected in IRT mode. Before sync clock time is 1sec I changed the clock time this issue resolved. Remains the logic same only.

Thank you!!

Randomly got issues with getting error message "changes to the technology object cannot be applied in run" after changing TO-objects mechanics and changing the Sync-domains send-clock from 1ms to 4ms fixed this issue.

Very weird that a send-clock issue causes and error like this for the TO-object during load.