OPC UA Driver

Forum Home Forums Uncategorized Issues OPC UA Driver

Tagged: 

Viewing 15 posts - 1 through 15 (of 16 total)
  • Author
    Posts
  • #5966
    Mikhail
    Moderator

    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.

    #5968
    kumajaya
    Participant

    It’s works! But missing BouncyCastle.Crypto.dll 1.8.4 in your package.

    #5972
    Mikhail
    Moderator

    Thank 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.

    #5980
    Mikhail
    Moderator

    The driver user interface is implemented.

    #9554
    josef.novotny
    Participant

    Hi 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

    #9558
    Mikhail
    Moderator

    Hi,
    What is the driver version?
    Please provide screenshots of the settings and the error message, and communication line log.

    #9559
    josef.novotny
    Participant

    Hy, 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.27

    Screenshots, and XML setting are here.

    Thanks for your reply, Josef

    #9560
    josef.novotny
    Participant

    Hi, 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

    #9561
    Mikhail
    Moderator

    Hi,
    Please try the update.
    Thank you for finding a bug.

    #9578
    josef.novotny
    Participant

    Hello, with new driver working everythink OK.
    Super.
    Thak you veru much, Josef.

    • This reply was modified 6 months, 3 weeks ago by josef.novotny.
    #9584
    Mikhail
    Moderator

    ūüôā

    #9638
    DumortierM
    Participant

    Hello,

    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.

    #9648
    Mikhail
    Moderator

    Hello,

    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.err

    #9668
    DumortierM
    Participant

    Hello,

    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.

    #9670
    Mikhail
    Moderator

    Hello,

    You should open the DLL file properties and unblock the file.

Viewing 15 posts - 1 through 15 (of 16 total)
  • You must be logged in to reply to this topic.