Forum Home › Forums › Uncategorized Issues › OPC UA Driver
Tagged: OPC UA
- This topic has 15 replies, 4 voices, and was last updated 2 years, 4 months ago by DumortierM.
-
AuthorPosts
-
September 23, 2019 at 1:00 pm #5966MikhailModerator
Alpha version of OPC UA driver released. Download link.
Currently, the driver does not have a user interface and is configured by editing the configuration file. An example project is contained in the ZIP archive.
If in the process of using you have questions or suggestions, write to this topic.
September 24, 2019 at 2:36 am #5968kumajayaParticipantIt’s works! But missing BouncyCastle.Crypto.dll 1.8.4 in your package.
September 24, 2019 at 6:07 am #5972MikhailModeratorThank you for checking. I added BouncyCastle.Crypto.dll to the ZIP file.
I also tested the driver on Linux. It works but requires an extra step in configuring. If needed, I will describe here.September 27, 2019 at 3:37 pm #5980MikhailModeratorThe driver user interface is implemented.
October 8, 2021 at 1:36 pm #9554josef.novotnyParticipantHi i try added new OPC UA device.
Server browse connect OK to new OPC UA device with this security options…
Security mode – None
Security policy – None
Authentication mode – Username and password
Username – myusername
Password – mypassword
Save configuration, upload config to server, but in line state is Error.
I check again security options in device properties.
Username is lost.
Why?Thanks for your reply, Josef
October 11, 2021 at 1:22 pm #9558MikhailModeratorHi,
What is the driver version?
Please provide screenshots of the settings and the error message, and communication line log.October 12, 2021 at 2:33 pm #9559josef.novotnyParticipantHy, driver version is…
KpOpcUa.dll… 5.0.0.0
Opc.Ua.Client.dll… 1.4.356.27
Opc.Ua.Configuration.dll… 1.4.356.27
Opc.Ua.Core.dll… 1.4.356.27Screenshots, and XML setting are here.
Thanks for your reply, Josef
October 12, 2021 at 9:52 pm #9560josef.novotnyParticipantHi, today i update Rapid Scada from scada_5.8.1_full_en to scada_5.8.3_full_en.
KpOpcUa.dll… 5.0.0.1
But problem is the same as previos post.Thanks for your reply, Josef
October 13, 2021 at 11:10 am #9561October 21, 2021 at 7:35 pm #9578josef.novotnyParticipantHello, with new driver working everythink OK.
Super.
Thak you veru much, Josef.- This reply was modified 2 years, 5 months ago by josef.novotny.
October 22, 2021 at 1:49 pm #9584MikhailModerator🙂
November 10, 2021 at 3:05 pm #9638DumortierMParticipantHello,
Thanks for your answers. I got the same problem as Josef and followed the discussion on this topic. I downloaded the new KpOpcUa.dll (V. 5.0.0.2) but are still unable to access data form the OPC UA server (b.t.w. the server is a Python server I set up myself for educational purpose).
When I try in the line parameters to select the driver and access the properties I got this message :
Error getting device interface type from the library KpOpcUa.dll (… next part is in french and talks about the .NET framwork).Could you help me figure out what happen ?
NB : with the 5.0.0.1 version of the KpOpcUa.dll I was able to read correctly the description of my OPC UA variables.
November 11, 2021 at 11:03 am #9648MikhailModeratorHello,
This error probably means that the driver version is incompatible with Rapid SCADA version.
Please check Communicator and Administrator versions.
Full error message would be useful, it can be copied from C:\SCADA\ScadaAdmin\Log\ScadaAdmin.errNovember 17, 2021 at 12:47 pm #9668DumortierMParticipantHello,
Thanks for your help.
Communicator version : 5.2.1.2 (got it in “Stats” of the communicator)
Administrator version : 5.5.2.2 (got it in “Help”)Here is the error I described before (sorry partially in French)
2021-11-10 16:00:25 <PC_NAME><MyName><EXC> Scada.ScadaException: Error getting device interface type from the library KpOpcUa.dll: Tentative de chargement d’un assembly à partir d’un emplacement réseau qui aurait entraîné l’utilisation de l’assembly en mode Bac à sable (sandbox) dans les versions antérieures du .NET Framework. Cette version du .NET Framework n’activant pas la stratégie CAS par défaut, ce chargement peut être dangereux. Si ce chargement n’est pas destiné à utiliser l’assembly en mode Bac à sable (sandbox), activez le commutateur loadFromRemoteSources. Pour plus d’informations, consultez http://go.microsoft.com/fwlink/?LinkId=155569. —> System.NotSupportedException: Tentative de chargement d’un assembly à partir d’un emplacement réseau qui aurait entraîné l’utilisation de l’assembly en mode Bac à sable (sandbox) dans les versions antérieures du .NET Framework. Cette version du .NET Framework n’activant pas la stratégie CAS par défaut, ce chargement peut être dangereux. Si ce chargement n’est pas destiné à utiliser l’assembly en mode Bac à sable (sandbox), activez le commutateur loadFromRemoteSources. Pour plus d’informations, consultez http://go.microsoft.com/fwlink/?LinkId=155569.
à System.Reflection.RuntimeAssembly.nLoadFile(String path, Evidence evidence)
à System.Reflection.Assembly.LoadFile(String path)
à Scada.Comm.Devices.KPFactory.GetKPViewType(String dllPath)
— Fin de la trace de la pile d’exception interne —
à Scada.Comm.Devices.KPFactory.GetKPViewType(String dllPath)
à Scada.Comm.Shell.Code.CommEnvironment.GetKPView(String dllPath)
à Scada.Comm.Shell.Code.CommEnvironment.GetKPView(String dllPath, Int32 kpNum, KPProperties kpProps)
à Scada.Comm.Shell.Code.CommEnvironment.TryGetKPView(KP kp, Boolean common, SortedList`2 customParams, KPView& kpView, String& errMsg)Thanks for your reply.
November 18, 2021 at 2:10 pm #9670MikhailModeratorHello,
You should open the DLL file properties and unblock the file.
-
AuthorPosts
- You must be logged in to reply to this topic.