Jump to content

Search the Community

Showing results for tags 'ethernet/ip'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Software & Hardware Discussions
    • LabVIEW General
    • LabVIEW (By Category)
    • Hardware
  • Resources
    • LabVIEW Getting Started
    • OpenG
    • Code Repository (Certified)
    • LAVA Code on LabVIEW Tools Network
    • Code In-Development
  • Community
    • LAVA Lounge
    • LabVIEW Feedback for NI
    • LabVIEW Ecosystem
  • LAVA Site Related
    • Site Feedback & Support
    • Wiki Help

Categories

  • *Uncertified*
  • LabVIEW Tools Network Certified
  • LabVIEW API
    • VI Scripting
    • JKI Right-Click Framework Plugins
    • Quick Drop Plugins
    • XNodes
  • General
  • User Interface
    • X-Controls
  • LabVIEW IDE
    • Custom Probes
  • LabVIEW OOP
  • Database & File IO
  • Machine Vision & Imaging
  • Remote Control, Monitoring and the Internet
  • Hardware

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Personal Website


Company Website


Twitter Name


LinkedIn Profile


Facebook Page


Location


Interests

Found 3 results

  1. Hi Guys, I'm with a trouble here. Recently we started to get our outdated temperature test cabinet to work, and the best way is to upgrade our PLC. But there cames 2 problems, the biggest is the budget, we do not have any money so we have to work with what we already have, and the second, i'm intern here and there is no one from automation to guide or help me. Now lets face the problem. PLC Allen Bradley micrologix 1100 cards: 1762-IQ16 and 1762-IQ8W6 My first thought is to use Labview to control the PLC, as HMI and data-logger without OPC server to simplify the instalation and cost. The communication: this is really where the problems begin. It will be done through Ethernet. I could not manage Ethernet/IP driver to work, nor pcc or CIP message... which is the best way to communicate? CIP Message, OPC, or any other i do not know? Do you guys see any problems to make a dataloger without OPC? Some things I have tryed Implementation of Common industrial Protocol (CIP) via EtherNet [EtherNet/IP (CIP)] https://lavag.org/topic/6104-industrial-ethernet-ethernetip/?page=1 Ethernet/IP Driver for Micrologix 1100 https://decibel.ni.com/content/docs/DOC-13024 EtherNet/IP Driver for Industrial Communication https://decibel.ni.com/content/docs/DOC-4065 Thanks for any help Ricardo PS. Originally posted at: https://decibel.ni.com/content/thread/47497
  2. Hi Guys, I'm with a trouble here. Recently we started to get our outdated temperature test cabinet to work, and the best way is to upgrade our PLC. But there cames 2 problems, the biggest is the budget, we do not have any money so we have to work with what we already have, and the second, i'm intern here and there is no one from automation to guide or help me. Now lets face the problem. PLC Allen Bradley micrologix 1100 cards: 1762-IQ16 and 1762-IQ8W6 My first thought is to use Labview to control the PLC, as HMI and data-logger without OPC server to simplify the instalation and cost. The communication: this is really where the problems begin. It will be done through Ethernet. I could not manage Ethernet/IP driver to work, nor pcc or CIP message... which is the best way to communicate? CIP Message, OPC, or any other i do not know? Do you guys see any problems to make a dataloger without OPC? Some things I have tryed Implementation of Common industrial Protocol (CIP) via EtherNet [EtherNet/IP (CIP)] https://lavag.org/topic/6104-industrial-ethernet-ethernetip/?page=1 Ethernet/IP Driver for Micrologix 1100 https://decibel.ni.com/content/docs/DOC-13024 EtherNet/IP Driver for Industrial Communication https://decibel.ni.com/content/docs/DOC-4065 Thanks for any help Ricardo PS. Originally posted at: https://decibel.ni.com/content/thread/47497
  3. Hi everyone, I've got a problem that I'm desperately in need of assistance. The basic setup is that I've got a SLC5/05 Allan Bradley PLC system communication to a screen (HMI). I've thrown an ethernet switch in between the PLC and screen and everything continues to work correctly. I have then connected a CompactRIO to the switch, which has been setup to 'sniff' the PLC tag packets. This works successfully using the Industrial EtherNet/IP Communications LabVIEW Module. The problem I'm having is on a second set of hardware, where PLC tag reading works on 1 PLC, but not another. I am also physically using a different cRIO, but with the exact same hardware and cRIO image has been copied. The PLC hardware and firmware should also be the same as well. All IP addresses are the same for both systems, and the PLC can be pinged successfully. Actually, as far as I'm concerned it's a duplicate system in every way. I can also tell you that when I request for a PLC tag reading, I get the following error code -251723745. I've spoken to NI who say that this is not a generic LabVIEW error but relates to a PCCC status error whose code is 0xF0. This error is within range used to indicate Object Class Specific errors. However, I don't know enough about AB PLC systems to understand what this means. Is there anyone who can help me? Anyone with similar experiences or troubles with EtherNet/IP protocol using LabVIEW. Thanks. Brenton Lang
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.