- modification of the dialog size of the Interactive Generator Block CANopen is possible in docked and undocked state
- configurable block size for SDO block downloads (CANopen node layer)
- support SDO block downloads with flag SizeNotIndicated (CANopen node layer)
- Download communication with e=0 s=0 is supported (CANopen node layer)
- Retransmission in SDO block upload is supported (CANopen node layer)
- Trace window: 447 interpretation if the assigned database is not in the project directory. The interpretation is displayed in the appropriate column if the database is assigned to the CANoe configuration but is not stored in the ProCANopen project directory.
- Trace window: SDO upload possible for objects with index smaller than 0x1000.
CANoe crashes if an object with index smaller 0x1000 was accessed.
- CANopen Generator Block: After a double click the dialog is opened in the system view.
- CANopen Generator Block: No automatic change of the toggle bit for guarding messages. The toggle bit 0 is inserted to the guarding message. If the sequence with the guarding message is executed the toggle bit changes its state internally but the state is not displayed in the sequence.
- CANopen Generator Block: Correct calculation of object indices for decimal display. A decimal object index was interpreted as hexadecimal during a SDO transfer.
- CANopen Generator Block: Correct display of the node-ID.
During the cyclic transmission a wrong node-ID was displayed.
- CANopen Generator Block: Cyclic transmission continues on desktop switch.
The cyclic transmission stops if the user switches to another desktop.
- CANopen Generator Block: Correct chronological order of NMT commands.
If a NMT command was sent to several nodes, the order was incorrect.
- CANopen Node Layer: Correct interpretation of object 0x1F80.
If the NMT Master bit (bit 0) was not set, bit 2 was evaluated however to decide if the device is an auto start device.
- CANopen Node Layer: SDO Client can be used in state "Stopped" only.
If a SDO client was used in state ‘Stopped’, an error code was returned instead executing the command (not allowed in this state).
- CANopen Node Layer: SDO client checks the multiplexer returned in initiate-download-response. No abort-message was sent by the SDO client , if the returned multiplexer in initiate-download-response does not correspond with the given multiplexer in the initiate-download-request. The multiplexer needs to be checked to detect, if the response belongs to the request.
- CANopen Node Layer: SDO upload transfer complies the CANopen protocol if continue bit is set. The SDO client (coUpload) didn’t check the uploaded number of bytes, if the SDO-server finishes the transfer
early than expected by using the continue bit (no more segment to be uploaded).
- CANopen Node Layer: SDO client block download supports re-transmission
SDO client aborts the transfer, if the SDO-server does not acknowledge the sequence number of the last segment.
CANopen Node Layer: Check of the ClientCommandSpecifier during SDO transfers in SDO server. No check of the ClientCommandSpecifier was executed in the SDO server, after a segmented SDO upload or SDO download was initiated.
- CANopen Node Layer: Unexpected abort message after reset removed
If a NMT Reset command was sent to the SDO server directly after a successful SDO block upload, the SDO server sends an abort message.
- CANopen Node Layer: Current transmission continues if a new request is received. A current transmission (SDO block up- and download) was aborted if the SDO server receives a request to initiate a new transmission. The SDO server mustn’t react on every request during a transmission.
- CANopen Node Layer: SDO server (SDO block download) checks the specified data length.
- CANopen Node Layer: The function coTriggerTPDO() returns the correct error code. The wrong error code ‘Invalid PDO’ was returned by the function coTriggerTPDO in these cases:
- PDO configuration has been created statically (not by remote or local SDO accesses).
- The node is not in state ‘Operational’.
- Report names are build on the basis of the test sequence name.
The file name ‘report.txt’ was used per default for the report file during the generation of a test sequence. If a CANoe configuration was generated with more than one test sequence, the report file was overwritten with
each execution of a test sequence. (ProCANopen Test Configurator)
- The (ASCII) logging block is activated if at least one test sequence is contained in the ProCANopen project. (ProCANopen Simulation Generator)
- Dialog settings are stored now. (ProCANopen Test Configurator)
- Warning message on invalid node-ID is displayed now. (ProCANopen Test Configurator)
- Different warning and error messages if the dialog is closed and the same problems are existent are removed. (ProCANopen Test Configurator)
- Test group/function numbering is now correct after rename of a test group (ProCANopen Test Configurator)
- If a test function was deleted the focus got lost. (ProCANopen Test Configurator)