Search the Community

Showing results for tags 'panelbuilder'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Found 2 results

  1. Hello, I have a .PBW file in an obsolete PanelView that I need to troubleshoot, but I can't open it.  Called AB TechConnect for support, but tech said it was too archaic and he, essentially, needed to start with a Windows98 machine and PanelBuilder 32 to even begin.  FactoryTalk doesn't know what to do with it.  File is attached.  Any suggestions/assistance is much appreciated ABWWTP.PBW
  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