From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Beckhoff EK1100 RT-Startup problems
FJohn
Member
04-11-2014 05:34 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hey,
I´ve a problem with Beckhoff coupler EK1100.
When I create a project with RT-Target and EtherCAT Master and Slave the first time everything runs normally (I can read and write all I/O´s at the Beckhoff).
After a couple of restarts the RT can´t establish a connection with the EtherCAT Slave. If I disconnect the plug from the coupler and connects it, nothing happens. But if I disconnect RT and Beckhoff, restart the RT, and connect them after the RT is booted, the EtherCAT will work fine. A few restarts of the RT later, the connection can´t be established again...
Has anyone an idea what the reason could be? I tried deployes and stuff, but the missing connection after restart of RT is still there.
Is it possible that the Scan Engine has a timing problem at startup with Beckhoff EtherCAT coupler?
Thanks in advance
Fabian
OlegS
NI Employee (retired)
04-14-2014 09:00 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hi FJohn,
Which RT-Target do you have and which Version of LabVIEW and EtherCAT Driver do you using?
Also it is not clear to me why you have to restart your RT-Target as often?
And when you restarting the RT-Target do you also restart the Beckhoff EK1100?
When not please try this and give me a short feedback.
Kind Regards,
Oleg, M.Eng | Applications Engineering | National Instruments | NIG |
04-15-2014 03:29 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hi,
I´m using a PC with LabVIEW RT 12.0.0.1 and an EtherCAT compatible Ethernet Adapter. The EtherCAT-Driver version is 2.5.
The Development system is LabVIEW 2012 f3.
For your question "why the RT shall restart so often": I´m wondering, why the RT can´t communicate to the EtherCAT sometimes. If I deliver an automation system, I can´t prevent, that the client will restart the system.... . Therefore the system must restart reliable.
To restart the EK 1100 will have no effect, when communication problems occur. Is it possible, that the scan engine is responsible for the problem (maybe a problem in the order of drivers loaded in "ni-rt.ini", like the serial driver).
Kind Regards,
Fabian
OlegS
NI Employee (retired)
04-15-2014 06:09 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Dear FJohn,
So you aren't using any NI Hardware.
Do you have a cRIO to reproducing this issue with NI Hardware?
Also I would ask you to update your NI EtherCAT Driver to version 2.7 and test if this could solve the issue.
The NI Industrial Communication for EtherCAT 2.7 is the most recent version of the software and the links for the file may not have been uploaded on the ni.com/ site.
And to refer to your question about the scan engine you could try to use the Scan Engine Pallet to reset the scan engine by setting it to Config mode and then again to active.
Kind Regards,
Oleg, M.Eng | Applications Engineering | National Instruments | NIG |
