12/2/2015 8:48 AM | |
Posts: 5225 Rating: (1192) |
The S7-1200 does not have what you are looking for (..or it is kept secret from us users). We are forced to use the motion functions that are available. Firmware V4.1.3. with motion control version 5 allows to use the motion control blocks in interrupts - it was a problem before. I however have not yet used the motion control inside the interrupts yet (for the versions mentioned) to be able to tell you more. Also I have not seen formal documents to expand on this information. A work around is to have the motion control trigger a memory bit for the enable instead of the output bit which you would do normally. Then you can have your user program read the memory bit and trigger the output when you choose to. In this way you can have an interrupt force the output off regardless of the enable memory bit. This method's negative - your (open loop) motion control will have wrong positioning information and you will need to do homing. If however you only do [relative] motions with some position trigger sensor, this method may not have a negative side. Alternatively use an external encoder to keep track of the movement. Also see the following information in the FAQ... What are your thoughts on this matter? |
Last edited by: William_B at: 12/2/2015 8:52:19 AMadd link to FAQ Last edited by: William_B at: 12/2/2015 8:53:37 AM |
|
12/2/2015 9:39 AM | |
Posts: 1529 Rating: (202) |
If you've never used a motion controller, the S71200 works great. If you are used to SIMOTION, prepare for some disappointments. |
12/2/2015 9:45 AM | |||
Posts: 5225 Rating: (1192) |
Hi. I have had issue with an application that did not work right. It was with firmware V4.0.x. (motion V4) I have learnt, that there is a 10ms "scan cycle" for the motion control. That meant that up to 20ms delay to commands may apply. You will have to check what applies for motion V5. As to your question - please review
Highlighted: S7-1200 FW V4.1.3 allows to execute motion function blocks in any OB. What has been suggested to you sounds good enough to try out. BUT be sure it is FW4.1.3 on your PLC. Any FW4.x can be upgraded to this version.Please let us know the result. Go well. |
||
This contribution was helpful to1 thankful Users |
12/2/2015 9:45 AM | |
Posts: 95 Rating: (0) |
for sure I am not expected from s7-1200 to act like simotion , its Blasphemy. but to stop within interrupt ........ thanks |
12/3/2015 7:17 PM | |
Posts: 95 Rating: (0) |
ok but the costumer do not want new wiring. its all ways possible to enable the CLR signal of PTO drive , instead of relay . |
12/3/2015 8:41 PM | |
Posts: 95 Rating: (0) |
yes first this is 265 and not 256 . then when trying to activate it , it shows an alarm of HW_ID . |
12/4/2015 1:00 PM | |
Posts: 1529 Rating: (202) |
Write a 0 to "(MC_Power Instance Datablock)".Enable in the interrupt. I learned these tricks from https://support.industry.siemens.com/cs/document/77467940/sinamics-v%3A-controlled-positioning-of-a-v90-with-s7%E2%80%911200-via-the-pulse-direction-interface-with-hmi?dti=0&lc=en-WW which has to be the absolute worst example for starting engineers since ALL of the commands are generated in the HMI writing to the instance datablocks (Oh look how clever we are). |
Last edited by: Jeff Casagrande at: 12/4/2015 1:03:22 PM |
|
12/4/2015 1:27 PM | |
Posts: 5225 Rating: (1192) |
Jeff, this is a brilliant share! I have looked through the provided document quickly and find some descriptions from page 50 that may be helpful. IMO there are much information in this document. I agree with you on the HMI >> DB comment.... if ever you have time - look at the program application for V20 to S7-1200 over Modbus..... ouch! I doubt that the calling of the bit in the interrupt will help.
|
Follow us on