I have two seperate (.NET) snaps which both need to connect to the same drive via the EAL library. If I install only one of them and uninstall the other, both work fine. However, if I install both of them at the same time, only one of them works and the other throws the exception
2022-10-11T09:08:15Z measurement-module.client: Unhandled exception. EAL.Exceptions.EALException: Ping execution is failed.
2022-10-11T09:08:15Z measurement-module.client: Ping execution is failed.
2022-10-11T09:08:15Z measurement-module.client: ----------------------------------------------------
2022-10-11T09:08:15Z measurement-module.client: ------------------------------
2022-10-11T09:08:15Z measurement-module.client: at EAL.EALConnection.EALConnection.Connect(String ipAddress)
2022-10-11T09:08:15Z measurement-module.client: at Samples.Datalayer.Client.Program.Main(String args)
2022-10-11T09:08:15Z systemd: snap.measurement-module.client.service: Main process exited, code=killed, status=6/ABRT
2022-10-11T09:08:15Z systemd: snap.measurement-module.client.service: Failed with result 'signal'.
Solved! Go to Solution.
To get a better picture, could you please tell what exact components you are using!
The max. connections via S/IP (EAL) to a single drive are limited by 2 at the same time.
This means when you are connected via ctrlX WORKS and your app using EAL at same time, you will not be able to connect with your second app.
I am not running ctrlX WORKS but have attached a screenshot of all installed apps. Is there another app which might cause the issue? "measurement-module" and "excitation-module" are my own snaps with an EAL connection each.
I am using a ctrlX core and I am trying to connect to a "HCS01.1E-W0009-A-02-A-CC-EC-ET-NN-NN-FW". Is this what you meant?
I think what they mean is that you cant connect with ctrlX Drive Engineering and two snap's as that would make up three connections.
And also, it would mean that if you use both EAL connections in the snaps it wont be possible to connect to the drive with ctlrX Drive Engineering.
I don't understand. Am I using ctrlX Drive Engineering and where can I find it?
Thank you very much! I was running IndraWorks and closing itseems to have solved the problem. Strange, that I never experienced this before the core20 update...
Another solution might be to use the Drives App (DCA) on the CORE to map the reachable drives into the datalayer and then use the ctrlX Data Layer .NET API to communicate with the drives. Because the DCA is then the only instance doing IP communcation with the drives, the number of clients is not limited.