DDK (Driver Development Kit)

Anonymous
Anonymous
A Driver Development Kit is available for people who wish to write their own native CitectSCADA drivers.

The attached document is the first chapter from the DDK and will provide an overview of what the full DDK contains. Once you have determined if purchasing the DDK is right for you, please contact your local sales channel to do so.

If you have purchased the DDK, please send me a Private Message with the follwoig details and I will enable your access the the Developers Forum.

Order Reference Number
License Key Number
Device/s you wish to write driver/s for
Prefered development environment



David.Sorkovsky
Product Manager
Schneider Electric | Industry Business | SCADA Activity

  • Dear David,

    What is the lates version of DDK? Is there newer version than 6.0?

    Best regards
    Pawel



    mpl
    engineer
    MPL

  • DDKV6 is still the current version.


    David.Sorkovsky
    Product Manager
    Schneider Electric | Industry Business | SCADA Activity
  • Hi,

    Let me know please the status of the present DDK. My detailed questions are listed below as follows:

    1., What is the lates version of Citect DDK? V6.0?

    2., Is it possible the Citect-DDK-Upgrade?

    3., Which programming languages are supported by the latest DDK?

    4., Is the CitectSCADA version V7.2 supported by the latest DDK?


    Best Regards,


    Emőke Keresztesi
    =====================================
    CONTROSYS Engineering Ltd.-Hungarian Citect Distributor
    H-1112 Budapest, Felsőhatár utca. 20.
    Tel. +36 1 248 1416 Fax +36 1 248 1417
    http://www.controsys.hu
    =====================================



    emokekeresztesi
    sales
    CONTROSYS Ltd

  • Hi,

    we have some issues with our driver assembly. The driver is unable to start in an Windows 7 environment. Citect only states the following message, afterwards the IO-Server process crashes with an exception.

    We are using Windows 7 32bit with Citect 7.2.

    Could you give us some information about the following questions:
    1. Is there a possibility to compile the driver with Visual Studio 6, so that it will run under Windows 7?
    2. If not, which Visual Studio Version would you recommend for migration and further driver development?
    3. Is there a workaround to fix this issue without any changes in the driver assembly?

    Thanks so lot.

    Best Regards,
    Manfred Reyzl

    _____________________________________________________________________________________

    Dr. Manfred Reyzl | Reyzl TechnologiesTM | "Nothing is impossible!"® | "Nothing is off-limits!"®
    Phone: +49 8272 99 32 990 | Fax: +49 8272 99 32 996 | PC-Fax: +49 8272 99 32 995
    Site: reyzl.de | Address: Reyzl TechnologiesTM, Ritter-Rehm-Straße 25, 86502 Laugna, Germany



    manfred.reyzl
    Support & Training
    Reyzl Technologies

  • The driver binary needs to be marked as being compatibile with Windows 7. A utility was developed recently to provide third-party driver developers the ability to mark their own drivers as compatible. Important things to note are

    1 - This tool only works on third-party drivers
    2 - This is not a guarantee that the driver will work under Windows 7 but will remove the restriction of blocking loading of the driver. Compatibility is dependant on the implementation of the driver and appropriate testing should be done to ensure Windows 7 compatibility.

    I will post a link to the tool later this afternoon or tomorrow so that it can be downloaded for use.

    Regards

    Carlos



    Sotomayor
    Development Manager
    Schneider Electric

  • How to apply MyTest in DDK for a test of driver customization?

    I copied the compiled dll file to $CITECT_HOME\bin; and add a new line in PROTDIR.dbf; and copy YOK_CXLE.dbf to MYTEST.dbf; and the driver still cannot be found in the protocol list ...



    glmaster
    Dr.
    SAC-METSO

  • glmaster,
    The names of the communication protocols available are stored in HELP.DBF in the BIN directory. Scroll through the file until you reach the section with TYPE = PROTOCOL to see the existing entries.
    If you decide to add your protocol to this file, things to remember are:
    1. HELP.DBF is an indexed file and you will need to reindex it after making any changes.
    2. HELP.DBF and HELP.NDX may be overwritten when a new service pack, hot fix, etc. is applied. As a consequence you will need to reapply your changes afterwards as simply overwiting the files with a backup may remove newly added entries.

    Regards


    Tim



    timhenly
    Technical Specialist
    Schneider Electric Ltd. -Services & Projects

  • Sotomayor;35567 said:

    The driver binary needs to be marked as being compatibile with Windows 7. A utility was developed recently to provide third-party driver developers the ability to mark their own drivers as compatible. Important things to note are

    1 - This tool only works on third-party drivers
    2 - This is not a guarantee that the driver will work under Windows 7 but will remove the restriction of blocking loading of the driver. Compatibility is dependant on the implementation of the driver and appropriate testing should be done to ensure Windows 7 compatibility.

    I will post a link to the tool later this afternoon or tomorrow so that it can be downloaded for use.

    Regards

    Carlos

    I cannot find the link, is it here somewhere or can it be re-posted?

    Thanks,
    Mike



    mrioux
    Application Engineer
    Control Point

  • error message as "re-compile project "often occured during runtime in v6.1.i checked the project,only find the driver snmpii is used,what resons?


    xhui1974
    engineer
    beijing
  • I have a customer who has purchased the DDK. I would like to get a full copy of the DDK_introduction PDF. The form said to send a private message to Dave S. But when I tried, it said that Dave not accepting private messages. Does anyone know how to get a copy?


    kharper
    Citect Engineer
    The Proud Company