02-13-2025 08:52 AM
Hi everyone,
I recently upgraded my LabVIEW project from LabVIEW 2017 to LabVIEW 2024 due to a Windows update. The PC is connected to a cRIO-9030, which is linked to an EtherCAT device with multiple inputs.
In the LabVIEW Project Explorer, I can detect the EtherCAT device, but not all of its sub-items. When I try to deploy the EtherCAT configuration, I get an error stating that I need to import the profiles via the *XML configuration of the MFCs.
However, when I attempt to import the XML profile, I receive the following error:
"NI-Industrial Communications for EtherCAT: The software cannot import the device profile."
I've checked the Industrial Communications for EtherCAT help documentation, but haven’t found a solution.
In addition, I can successfully deploy some sub-devices that do not require an XML configuration, so I don’t believe this is a connection or device detection issue.
Has anyone encountered this issue before or found a workaround? Any help would be greatly appreciated!
02-16-2025 08:15 AM
Do you have the latest Ethercat download (23Q1)? Does the Bit Size match that of your LabVIEW 2024 software? [Note I'm not familiar with Ethercat, so I did some browsing just to see what NI was offering ...].
Bob Schor
02-17-2025 03:22 AM
Regarding bit size: everything seems to be 64bit
My version is 2023Q3-Patch1 (v.23.5.0f113), as it was the latest one in the NI-IndCom for Ethercat
02-18-2025 06:49 AM
Hi
There is an issue with this version. You have to put manually your xml file in the right place :
C:\Program Files\NI\LVAddons\niecat64\1\resource\Framework\Providers\indcomecat\DD\
for Windows and
/var/local/natinst/IndComECAT/DD
for Linux RT
02-20-2025 09:30 AM
Hi, I have also just run into this issue after updating to LabVIEW 2024 Q3. I've manually copied the files over to my RT PXI and the Windows host to the appropriate folders. After doing this I'm still struggling to fully communicate with the EtherCAT master device.
The error in the Deployment Status reads:
"LabVIEW: (Hex 0xFFFEFC65) The configuration for the I/O channel you accessed is not internally consistent due to a pending configuration change. Try to access the channel again after the configuration operation is complete."