Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 97 views

    Read Me

    Uploaded by

    Anonymous 4KVQOT5jeH
    The document summarizes changes between CoDeSys compiler versions 3.4.0.0 and 3.4.1.0, including: 1) Checksums are now calculated differently for STRING and WSTRING types, which may require reinitializing variables or cause linker errors. 2) The library manager categorization has been reorganized, with some libraries now having new successor versions. 3) The Peak PCAN-USB driver has been updated to a new API version, requiring installation of new device drivers and DLL files. 4) The CAN block driver now uses block transfer by default for better performance.

    Copyright:

    © All Rights Reserved
    Download as RTF, PDF, TXT or read online from Scribd

    Read Me

    Uploaded by

    Anonymous 4KVQOT5jeH
    97 views3 pages
    The document summarizes changes between CoDeSys compiler versions 3.4.0.0 and 3.4.1.0, including: 1) Checksums are now calculated differently for STRING and WSTRING types, which may require reinitializing variables or cause linker errors. 2) The library manager categorization has been reorganized, with some libraries now having new successor versions. 3) The Peak PCAN-USB driver has been updated to a new API version, requiring installation of new device drivers and DLL files. 4) The CAN block driver now uses block transfer by default for better performance.

    Original Title

    ReadMe.rtf

    Copyright

    © © All Rights Reserved

    Available Formats

    RTF, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document summarizes changes between CoDeSys compiler versions 3.4.0.0 and 3.4.1.0, including: 1) Checksums are now calculated differently for STRING and WSTRING types, which may require reinitializing variables or cause linker errors. 2) The library manager categorization has been reorganized, with some libraries now having new successor versions. 3) The Peak PCAN-USB driver has been updated to a new API version, requiring installation of new device drivers and DLL files. 4) The CAN block driver now uses block transfer by default for better performance.

    Copyright:

    © All Rights Reserved
    Download as RTF, PDF, TXT or read online from Scribd
    Download as rtf, pdf, or txt
    97 views3 pages

    Read Me

    Uploaded by

    Anonymous 4KVQOT5jeH
    The document summarizes changes between CoDeSys compiler versions 3.4.0.0 and 3.4.1.0, including: 1) Checksums are now calculated differently for STRING and WSTRING types, which may require reinitializing variables or cause linker errors. 2) The library manager categorization has been reorganized, with some libraries now having new successor versions. 3) The Peak PCAN-USB driver has been updated to a new API version, requiring installation of new device drivers and DLL files. 4) The CAN block driver now uses block transfer by default for better performance.

    Copyright:

    © All Rights Reserved
    Download as RTF, PDF, TXT or read online from Scribd
    Download as rtf, pdf, or txt
    You are on page 1of 3

    Very important information:

    Checksum for STRING and WSTRING types (CDS-13642):


    The problem is a wrongly calculated checksum for STRING and WSTRING types with a defined length.
    With compiler version >= 3.4.1.0 we calculate a different checksum, i.e the programmer may be asked to
    initialise persistent variables even if they did not change.
    The same checksum is also used for identifying functions in the runtime system. If you have functions with
    inputs or outputs of type string with a defined length like STRING(40) introduced with version 3.4.0.0, you
    will receive an unexpected linker error on the attempt to use the function with compiler version 3.4.1.0.

    Library Management
    Usability reasons forced a rigorous clean-up of the category “Application->Common” of the library
    manager.
    Only the libraries “Standard”, “Standard64” and “Util” are still members of this category.
    All other end user related libraries are now grouped in so-called container libraries and organized in a new
    category named “UseCases”.

    For some interface libraries, this version of CoDeSys introduces a successor library.
    Please use this new version for your current development.

    DataServer Interfaces 2 -> DataServer Interfaces 3


    IIecVarAccess 5 -> IIecVarAccess 6
    Monitoring Interfaces 2 -> Monitoring Interfaces 3
    SysTypes -> ISysTypes

    The versions of CoDeSys libraries implementing specific features based on these interface libraries must
    be consistent within one application: Either all library versions must be 3.4.1.0 or all from the old versions.
    This affects libraries inserted as system libraries as well as libraries inserted as user libraries.

    Libraries commonly used in projects and affected by this change are:


    All visualization libraries
    TraceManager
    DataServer
    Standard Monitoring Dataserver Driver
    IecVarAccess
    RecipeManagement

    Peak PCAN-USB (CmpPUSBCanDrv):


    IMPORTANT: The CmpPUSBCanDrv component now uses the new API of PEAK (version 2.x). Please
    note that you have to install the most recent driver and Pcan_Usb.dll from PEAK to make the new driver
    work. For this purpose, download the most recent PeakOEM driver from the PEAK website
    (http://www.peak-system.com/fileadmin/media/files/usb.zip) and install it. Furthermore copy the new
    Pcan_usb.dll (V2.0.3.0 or higher; also contained in the PeakOEM driver package) to
    C:\Windows\System32\ or to your GatewayPLC folder.
    CAN Blockdriver:
    BlkDrvCanClient and BlkDrvCanServer now use the “CANopen Block Transfer protocol” for better
    performance. If you want to switch back to segmented transfer you can deactivate the Block Transfer in
    the configuration file of the gateway (set 0.Blocktransfer to 0). With the new setting
    MaxSegmentsPerCycle (CmpCAASdoClient and CmpCAASdoServer; see new configuration files) you
    can limit the number of segments transferred per cycle when block transfer is active.

    License management in runtime system:


    Some features now require a valid license for the runtime system. For all license-requiring functions of
    CoDeSys a license test is executed, which can only be passed by V3.4 runtime systems and higher.
    As a consequence, runtimes older than V3.4 cannot be used together with certain features (visualization,
    fieldbusses, SM, FDT) >= V3.4.

    In these cases the user has three options:


    - keep using the old features (e.g. a VisuProfile < V3.4)
    - use an updated runtime or firmware where available
    - request a license file from your hardware vendor

    Upgrading an existing project:


    When a project created with an older version is loaded in V3.4 for the first time, some checks are
    performed and the user can then either upgrade the project or keep it compatible.
    IMPORTANT: In order to be able to login with an old project without online change or download, no
    updates should be performed!
    - Storage format: Projects older than V3.3 cannot be saved with their original storage format and must be
    updated to the V3.4 storage format. For all other projects, the user may choose to keep the compatible
    format (possible drawback: new features cannot be stored and may be lost) or to update to the most
    current storage format, which cannot be read by previous versions.
    - Project environment: If more current versions of the compiler, visualization profiles etc. are available,
    the user is prompted to update the respective feature. All libraries the user explicitly added to the project
    are also checked for a more current version. If such a version is available, the user can update the library.
    All these checks are only performed the first time the project is loaded with CoDeSys V3.4. If desired,
    such checks may be repeated later on by selecting ProjectProject Environment from the menu after the
    project has been loaded.
    The RTC-functions from SysTime have been moved to a new library SysTimeRTC. For projects using
    one of the RTC functions, it may be necessary to include this new library. However, we strongly
    discourage the usage of the Sys libraries and recommend the appropriate CAA libraries instead – CAA
    Tick, CAA TickUtil and CAA DTUtil in this case.

    CNC editor:
    1) Answer yes when asked if you want to upgrade the storage format for the project.
    2) For each CNC object in the project, acknowledge the error message "Object reference not set to
    an instance of an object" by pressing "OK".
    3) For each application that contains CNC objects: right click on the application in the "Devices" tree,
    select "Add object" from the context menu and select "CNC settings", followed by "Open" in the
    dialog.
    4) Adapt the CNC settings (especially the path pre-processors) as needed for the project.
    Note: these settings were formerly configured in the project settings.
    OPC server
    The values of the ini file entries ´logfilter=´ in the ini files created for the OPC server before version 3.4
    have to be corrected for the OPC server 3.4.
    Valid values for the OPC server 3.4 are
     15, generate standard log entries. (formerly 10)
     47, generate standard log entries plus additional entries. (formerly -47)
     63, generate standard log entries plus additional entries plus debug entries. (formerly -1)

    You might also like