"Unknown DLL" after upgrade

Forum Home Forums Installation Issues "Unknown DLL" after upgrade

This topic contains 5 replies, has 2 voices, and was last updated by Mikhail Mikhail 4 years, 3 months ago.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #410
    Avatar
    BretLark
    Participant

    Hi Mikhail,

    I have completely removed and re-installed Rapid SCADA due to some issues after the upgrade but even with a clean install the new KpModbus.dll doesn’t appear to be recognised. Also, the Device Libraries is empty so I cannot configure the XML file.

    This is on Windows 10 so I don’t know if something is stopping the DLL from registering. I posted in the other thread as I though it was something I had done wrong but I’m at a loss now as to what is happening.

    Many thanks,
    Bret

    #412
    Mikhail
    Mikhail
    Moderator

    Hi Bret,

    Did you install Rapid SCADA 4 Release 4?
    Please, describe the sequence of your installation and upgrade steps.

    #413
    Mikhail
    Mikhail
    Moderator

    Is there Unblock button in the DLL properties like shown here?

    #416
    Avatar
    BretLark
    Participant

    Hi Mikhail,

    You sir, are a genius! Blocked DLL files have now been unblocked!

    I will configure my connections again.

    Thanks,
    Bret

    #417
    Avatar
    BretLark
    Participant

    Hi Mikhail,

    There seems to be a new problem that I didn’t have previously but it looks like a new feature. With my connections configured as per your previous help and advice all I get in the log file is:

    “2015-09-06 11:04:23 Unable to communicate with the device because connection is not established”

    Under the Communication Line Parameters tab I usually have “Undefined” selected for the channel type and the connection is completed through the Call Number in Request Sequence. If I change this to TCP Client and add the IP address and port I get a connection. The issue here is that I can only have one device per Communication Line as my devices are all on different public ports.

    Has this changed within the software or have I configured something incorrectly?

    Thanks,
    Bret

    #419
    Mikhail
    Mikhail
    Moderator

    Hi Bret,

    Great, you guessed it ) In the new version of SCADA-Communicator device driver DLL is independent of a connection type. Special software layer named Connection channel establishes and manages the connection.

    You tuned up SCADA-Communicator almost correct, but in your case you shouldn’t define IP address in the properties of the connection channel. Do it in Call Number field of a device like before.

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.