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.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to communicate with slave ethercat Stober SD6 with cRIO9040 as ethercat Master / ESI file type

Hello everyone,

 

I am using cRIO-9040 as Ethercat Master and Stober SD6 as ethercat slave. I am able to import le ESI xml file and see the slave and his associated variables in the Labview project. I have been able to put the slave in operional mode from Labview whithout any error too.

 

But then, when i try to communicate with the slave by reading or writting some variable, i get an error : code -66208, and the error message isn't very helpful. 

Did anyone had the same problem ?

 

I have another question : I generate the ESI xml associated with the Stober SD6 ethercat slave by using the DriveControlSuite software and by doing it, i can choose the module of the ESI file (CiA, Drive Based (Basic configuration, or custom (when some variable has been added or deleted for the ethercat com)), and i can choose all of them (the 3) to export the ESI file.

 

Then, if i use Twincat to import this ESI file i created, i can again choose the type i want to import (CiA, Drive Based or custom). In Labview project, i don't have any possible choise when importing the ESI file, why ? is it possible somehow to choose the type when importing ESI file in Labview ?

 

You will find attached some screens to illustrate this subject.

Thank you,

François

0 Kudos
Message 1 of 3
(1,059 Views)

Hello François,

 

How did you put the slave in to operational mode?

__________________________________________
The best way to thank, is to give KUDOS
0 Kudos
Message 2 of 3
(977 Views)

Hello,

 

thank you for you answer. First i connected the cRIO, then added the master and slave in Labview project and i deployed all variables. The slave switched to operationnal mode and i have been able to switch the scan mode to active mode.

 

I have solved my problem : it was due to the ESI file format. The one created from the Stober DriveControlSuite software contained some "modules" in it, and maybe it's not well managed when imported in Labview.

 

So i imported this ESI file in Twincat and then exported a new one which doesn't contain any "modules" part.

 

This way, the slave variable have been autodetected when i imported the slave in Labview, which wasn't the case before.

 

I hope maybe this can help others in the same case.

Message 3 of 3
(972 Views)