Error code 5007 (error ENI file)

[PhiVo]

Hello,

I'm trying to get the PDOs of my Beckhoff cards via EtherCAT to use them in my project. Unfortunately I always get same error message (5007) that there could be an error in the ENI file I created in TwinCAT with all my slaves and couplers. I really don't know the error could be because I just started working with LabVIEW and TwinCAT. Maybe someone here can help with my problem and I attached the VI I'm using and the ENI file as a Word (txt and xml didn't work) file if this helps.

Thanks in advance!

[Bob_Schor]

Error 5007 is a "user-generated" error, which means it may be being created inside one of the VIs you are using.  Unfortunately, I am using LabVIEW 2019, so I cannot "look inside" your attached VI unless you open it and do a "Save for Previous Version", specifying LabVIEW 2019, and attach the 2019 version.  Is this the only VI that you are running?  [The "Generate Error" may be coming for some other VI ...].

Bob Schor

[PhiVo]

Hi Bob,

thanks for the reply. I attached a folder with the VI for LabVIEW 2019 and all the included SubVIs. I hope that it works and can help. I also tried to recreate the error to get the message in which VI the error occured but if I run it now, the PC just shuts down. If I get back to the error message I will send it in here too.

Greetings Phillip

[PhiVo]

Here are a screenshot of the error message and a screenshots of the running VI until the error occurs. As you can see the error happens in the "ECAT Acq Set ENI File" VI which is part of the "ECAT Acq Open Master" VI.

The PC shut down because was still running TwinCAT in the Run Mode😅

[Bob_Schor]

Yes, I can see that the error (a "User Error", 5007, as I believe I mentioned in a previous Reply) is in "ECAT Acq Set ENI File".  If you have the LabVIEW code for this VI, look for the function "Error Cluster from Error Code" function sitting on the Error Line with the number "5007" wired to it, then trace the Error Line backwards and try to determine which previous function or sub-VI did that.  If you do have the source, you could put probes and breakpoints in the ECAT routine and try to find (and possibly cure) the Error.

Bob Schor

[PhiVo]

Unfortunately I cannot look into the code of those VIs because they are provided by Ackermann Automation and so they are secured with a password and I can only open the front panel. But I will try and see if some of your tips can help while I'm waiting for an answer by Ackermann.

Greetings

Phillip

[PhiVo · Accepted solution]

Luckily the error is fixed. There was a problem with the driver which is used for the EtherCAT library. Now all is working as it should.