5/28/2018 1:28 PM | |
Joined: 3/14/2008 Last visit: 9/20/2024 Posts: 2095 Rating: (936)
|
Hi, You say use use the MotRevL, but I cannot see since you have used chart in chart. Please open the chart in chart and monitor the MotRevL and post a print screen. It's very likely that the logic inside the chart in chart is preventing the motor from starting. This is a custom made. |
If I could help you, you can use the RATE button. Thank you. |
|
5/28/2018 2:44 PM | |
Joined: 3/14/2008 Last visit: 9/20/2024 Posts: 2095 Rating: (936)
|
Hi engineer cotmac, According to your motor block, the motor is in Manual mode, so the command RevAut cannot be executed, since it requires the motor to be in Automatic mode. But maybe this is because the motor is switched in the meantime? Because in attachment 1 the motor is in automatic, but in second attachment, the motor is in manual... There is also a problem with your feedback, which may explain why the motor does not start. The feedback reverse signal is already present, but no command is given. This is why the motor is in GroupError, which means the motor will not be started. The feedback run signal reverse must be "1" when the motor is started in reverse, not sooner. |
If I could help you, you can use the RATE button. Thank you. |
|
5/29/2018 8:49 AM | |
Joined: 3/14/2008 Last visit: 9/20/2024 Posts: 2095 Rating: (936)
|
Hi, So you have no physical Reverse feedback signal. In that case, you can do as follows: Connect output "Rev" from MotRevL to input "FbkRev". When the motor is started in reverse, it will present the feedback automatically. PS: Why are you using chart-in-chart? This will require a lot more engineering effort->You have to create all inputs and outputs according to the block signals, you have to adjust your block icons in order to work with it... Why don't you make a Process Tag Type or Controle Module Equipment of it? |
If I could help you, you can use the RATE button. Thank you. |
|
5/29/2018 9:31 AM | |
Joined: 3/14/2008 Last visit: 9/20/2024 Posts: 2095 Rating: (936)
|
Hi, Ah ok, the reverse signal is present when FLS is touched. In that case, when FLS touches, you must first give the RevAut command so the motor is started in Reverse, FwdAut must be 0. After RevAut, the FbkRev must be present within the monitoring time. Make sure you do it in this order, otherwise you will get feedback error and the motor won't start. Anyway, when using chart-in-chart, you need to create inputs and outputs. The inputs and outputs are already available at the MotRevL, but you are creating them all over again. If you just copy all the content (all blocks) inside the chart block type and past it in a chart called: MotRevL_Template for instance, you have the exact same situation, but you do not need to configure inputs and outputs.. It's a hell of a job and not necessary as far as the reason you provided...You only have created a nested chart, but it just takes more work. When you have created the MotRevL_Template, you can create a process tag type of it. This means that with the import-export assistant, you can create 10x/100x/1000x MotRevL instances of the chart.Or by using the CMT strategy (which is new as of PCS7 V8.1). CMT are the new concept, which solves the problems of process tag types. You can do bulk engineering with CMT as well, but you will need to use a separate software called Plant Automation Accelerator. You can however copy CMT manually to your project. But, since you have a working project I would suggest you forget the PTT/CMT for now...
|
If I could help you, you can use the RATE button. Thank you. |
|
Follow us on