8/11/2020 11:47 PM | |
Joined: 10/24/2016 Last visit: 10/12/2021 Posts: 55 Rating: (0) |
Hey there, i'ld like to getting some help in my TIA v15.1 project. I cannot find any solutions to get my reaaally simple code working. The goal is to teach upcoming students in my university of applied sciences the commisioning of the hardware named below. They are supposed to set correct harware configurations like IPs, TOs, telegramms and so on. After doing so i want to start easily and just add one axis (e. q. a speed axis or a positioning axis) 1. SINA_Infeed to witch on the energy -> 2. MC_Power to unlock at least on drive-> after this, if MC_Power.status would get TRUE, i could finally take the next steps and programm some movements But so far i always got stucked at MC_Power, and now even earlier at SINA_Infeed. I cannot overcome the 16#8600 issue. And if i hadn't this failuer, there would be technology alarm 421 / 431 and so on, which are talking to me, that my encoder or encoder communication is broken. But this is not true. If i re-download my regulary programm, besides this studends-teching-project, everything is fine. Might someone of you help me =) ? At this hour, there is no error else in CPU and CU ( as u can see in pic below ), while trying to activate SINA_Infeed. I need to get rid of 16#8600 but cannot handle section 9.1.5 in my hardware is
I uploaded my this project into my dropbox under "KomFö_Test_1" and you should be able to download if you like: https://www.dropbox.com/sh/ipnwphrv06irtth/AAA1PcFkIFbbIAJD3xDzaeoba?dl=0 Many thanks and best regards |
Last edited by: Zottel86 at: 08/11/2020 23:48:03 |
|
8/17/2020 9:28 PM | |
Joined: 10/24/2016 Last visit: 10/12/2021 Posts: 55 Rating: (0) |
Hi Einstein, many thanks 4 ur reply. The last days i spent some time to work on on my testbench. So if i projected the positioning axis only (axis 1) i could control its behavior without any issue. No failures, correct working infeed, speed etc. Today i just wanted to import my 2nd servo drive (same hardware as 1st), but this time as a speed axis. So new TO, e.q. telegramm 3 (32 bit speed value + 1 encoder), some addings in OB's FC aaaaannnnnd nothing is working. Please refer to this project "KomFö_Test_1" in my dropbox [snip] The screenshot near by is displaying my actually issue. If i added the 2nd axis, suddenly MC 421 occures and axis 1 and axis 2 cannot be reached anymore. there are no changes for axis 1. i dont get it. At least MC_Power of axis 1 (positioning axis) is supposed to still working. Edit 1: attach this picture. my preview is displaying, the posted reply is not ... AttachmentFiles.zip (142 Downloads) |
Last edited by: Zottel86 at: 08/17/2020 21:30:18Last edited by: Jen_Moderator at: 08/19/2020 08:28:58Removed link and added files as an attachment. |
|
8/28/2020 11:20 PM | |
Joined: 7/7/2010 Last visit: 10/10/2024 Posts: 15282 Rating: (2426) |
This link may help: https://support.industry.siemens.com/tf//WW/en/posts/problem-related-to-mc-alarm-421-with-using-plc-s7-1500/225163 Also, being a person teaching future engineers, I expected you to find the above link on your own (which you very well may have in the last 10 days). What's the current status of the project, 10 days later? Have you stopped trying simultaneous speed and motion control, and try just enabling 1 axis at a time to see which TO is causing the fault. What fault(s) exist in the CU and drive objects? What fault(s) exist in the PLC diagnostics buffer? Why are there so many implicit datatype conversions in your project? Those implicit conversions can create problems where none should exist, making you look over there---------------> when the problems is really over there <-------------- If it were me, I'd approach it slightly differently.
It may make sense when enabling the infeed, to do that, wait for the proper outputs to turn on, then enable one axis, verify no error, then enable 2nd axis, and verify no error. Same for moving an axis (in a circle over and over, or positioning it). In this controlled startup, you see exactly what causes the fault. When turning on and giving a command to a drive, just do one drive at a time. These guidelines are not given as a design philosophy. Instead, as a way to learn how to use the TO's and Sinamics blocks together to properly perform required tasks. Once the infrastructure is sound and the learning is done, you are welcome to revert back to simultaneous startups and TO activations. For now, limit activities and track block outputs. Use them to your advantage. Ignore them at your own peril!
|