Contact
Download
New features:
- In the Device Access dialogue data files can be downloaded or uploaded to/from domain objects via a symbolic dialog.
- Mapping objects defined in DS-413 profile are supported when storing the configuration in the network (concise data). The SDO order for writing mappable objects follows the rules defined in DS301. This order is also kept when accessing those objects via the dialogue Device Access.
Resolved issues :
- If object "Number of mapped objects" (sub index 0) of a mapping object was less than the real number of sub objects, all existing sub objects were handled in operations like an SDO access. Now, only the number of objects indicated in sub object 0 will be handled, even if more sub objects exist.
- If more than one SDO actions are executed (e.g. writing a structured object), ProCANopen/CANsetter stops the whole sequence if at least one SDO timeout occurs. In former version ProCANopen was waiting for all SDO timeouts.
- If invalid bit combinations are used for the value of object 0x1F80 or sub objects of 0x1F81, no automatic corrections are made by ProCANopen/CANsetter anymore (test purposes).
- If a node cannot be heartbeat consumer, heartbeat producer or both (the corresponding objects are not defined in the EDS), the related UI controls are deactivated.
- The object "Number of mapped objects" (sub index 0) is adapted if an object was added/removed to a PDO via the PDO list.
- Object entry "HighLimit" is evaluated when ProCANopen is automatically creating the mapping entries.
- Invalid concise download: If the value 0 was assigned to a mapping parameter object (except sub index 0) this value is written within the concise data. If the master wants to configure the assigned slaves during the boot-up, the configuration fails because 0 is not a valid entry for a mapping parameter objects.