Jump to content

Search the Community

Showing results for tags 'ethercat crio 9039'.



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
    • GCentral
    • 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 1 result

  1. hi, We are trying to connect a third party EtherCAT slave device to our cRIO 9039, which is configured as an etherCAT master. Problems arise when we try to activate the scan engine of the cRIO. The following error message appears: (see attached). Therefore the scan engine is pretty much stuck in its 'Init' state and the cRIO is unable to communicate I/O data. We have been able to resolve the issue by replacing the cRIO 9039 with a Beckhoff PLC, suggesting that the third party hardware and .XML file are not at fault. Other things we tried to solve the problem include: install the correct Labview version (2018 SP1), device drivers (NI RIO 18.5) and industrial communication EtherCAT package (18.5). Unfortunately this did not resolve the issue. All suggestions are much appreciated! 😄
×
×
  • Create New...

Important Information

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