Fourdigger

MrPLC Member
  • Content count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Fourdigger

  • Rank
    Hi, I am New!

Profile Information

  • Country United States
  1. Hello I would like to first let everyone know I am new to the world of troubleshooting or programming plc's . What we have is a SLC500 system that is connected to a Panelview 1000 HMI via the DH+ network. The issue we have is the panelview displays a gate that is suppose to be closed at as gate fault. When i connect to the plc the ladder rung shows that the gate is closed. To show various positions of the gate the programmer used N13:70 as gate opened and N13:71 as gate faulted and N13:72 as gate closed. When i checked the logic it showed the bit N13:72 as engaged or true if you will. This logic is in the ladder rung that is labeled PV Status which i take is the status the HMI reads so my question is why does it show GF when it should be reading GC. Ive searched all through the logic and it doesnt appear to be wrong here is the logic the best I can simulate it  ladder 6 rung  53  instruction is  XIC O:13.0/11 and OTE N13:76/0 (Gate Open ) and the branch is XIC I:5.0/11and OTE N13:76/1 (Gate Fault) next branch is XIC N13:3/11 and OTE N13:76/2 (Gate Closed which this section is green or highlighted or true which ever you like) when i looked at the input XIC N13:3/11 this is what I found is that this XIC is on ladder four rung10 and has the following XIC T4:154/DN and branchoff that is XIC I:5.0/11(gate opened)XIC I:6.0/11(gate closed) which these two inputs are false or not lighted the output is OTL N13:3/11 and it is true which makes the previous rung true showing the gate closed. So why is the panelview showing the wrong position. I even went as far as resetting the HMI and the PLC so if anyone has a helpful hint I would greatly appreciate it.
  2.  I am a begiiner at this so please bear with me. Recently we replaced a HMI that had gone out and we upgraded to a fairly newer version our old unit was a PanelView 600 and we upgraded to a PanelView Plus 700. I thought the process was going to be straight forward just swap and go boy was I mistaken not only was the panel a upgrade but we had to get new editing software. So I took the pba. file and converted it to a Factory Talk mer. file I thought I had completed the task after converting the file I got the following messages. Screen 1 - RECEIVING: Message display object will be converted to Multistate Indicator object at (226, 63). Screen 1 - RECEIVING: Message display object will be converted to Multistate Indicator object at (140, 35). Screen 2 - LOAD OUT: Message display object will be converted to Multistate Indicator object at (80, 30). Screen 2 - LOAD OUT: Message display object will be converted to Multistate Indicator object at (226, 0). Screen 2 - LOAD OUT: Message display object will be converted to Multistate Indicator object at (0, 120). Screen 2 - LOAD OUT: Message display object will be converted to Multistate Indicator object at (0, 0). Screen 2 - LOAD OUT: Message display object will be converted to Multistate Indicator object at (300, 120). Screen 2 - LOAD OUT: Message display object will be converted to Multistate Indicator object at (273, 120). So I continued with the file and then I went to the communications section and selected the target area and because we are using DH+ communications we installed a communication module to the panel and installed a resistor  as directed in the AB instructions. Now back to the software I selected the target area and added a driver for the DH+ then selected the DH+ and added another driver this time I selected the SLC 5/04 1747 L541. Then I went to the the shorcut area and added a shortcut to what I believe is the PLC we are connecting to then selected the driver and selected apply then I went and created a runtime application and saved it to a usb device and loaded it on to the panelview plus and when it runs all the tags show a erro such as the picture shows I uploaded I cant decide if it is a missing communication driver or a error in the programming would love to hear your thoughts on the issues. Thanks everyone for any posts you have