--------------------------------------------------------------------------------
DeviceNet Master
--------------------------------------------------------------------------------

V2.4.0.0
--------
 - PSDNM-454:  [NXO] Create a new NXO target for rcx V2.1 
 - PSDNM-455:  Invalie use of TLR_BOOLEAN in API Header 
 - PSDNM-459:  DeviceNet Master can not communicate with maximal 63 slaves. 
 - PSDNM-460:  Bitstrobe request dataload is different than the DPM 
 - PSDNM-461:  24V missing status is not updated when master is configured alone on the network.
 - PSDNM-463:  "Controlled by Application" should not be reported as error.

V2.3.20.0
---------
 - PSDNM-459:  DeviceNet Master can not communicate with maximal 63 slaves. 
 - PSDNM-460:  Bitstrobe request dataload is different than the DPM 


V2.3.19.0
---------
 - PSDNM-387:  Unneeded section in DeviceNet Master's Extended Diagnosis. 
 - PSDNM-396:  Firmware can be configured with more than maximum number of cyclic input/output data stated in Protocol API. 
 - PSDNM-402:  MNS led stays green without bus power 
 - PSDNM-404:  LED stays green blinking after 24V removed 
 - PSDNM-410:  Indication of CAN bus off error in DPM is cleared while actual error still exists 
 - PSDNM-418:  Multiple Channel Init interrupt data exchanged when with fragmented output used 
 - PSDNM-419:  Incorrect firmware name and version when master license is missing 
 - PSDNM-424:  No communication error is reported, when there is no data exchange with one of the configured slaves. 
 - PSDNM-428:  Stopping of the master device communication via the DTM's context menu counts as an error in the "General diagnosis". 
 - PSDNM-435:  Incorrect firmware name and version when master license is missing 
 - PSDNM-437:  Support of showing the diagnosis state of a slave. 
 - PSDNM-439:  When downloaded with database with "controlled by application" the ulCommuncationError show TLR_E_APPLICATION_NOT_READY and RCX_COMM_COS_BUS_ON not set 
 - PSDNM-444:  DeviceNet Master get active on bus even if controlled by application 
 - PSDNM-445:  Resets of input from slave to zero about 2 second later als expected when the slave is disconnected from bus. 
 - PSDNM-446:  DeviceNet Master do not show communication error in case of duplicate MAC ID 
 - PSDNM-447:  Cannot set bit-strobed output of the master others than 0 
 - PSDNM-448:  Register Application Request Count is not equal sum of negative und positive confirmations in Application Diagnosis 
 - PSDNM-454:  [NXO] Create a new NXO target for rcx V2.1 
 - PSDNM-455:  Invalie use of TLR_BOOLEAN in API Header 


V2.3.18.0
---------
 - PSDNM-408:  Not initialized data in RCX_GET_DEVICE_INFO_CNF_T after bus scan 
 - PSDNM-411:  DEVNET_FAL_CMD_CLR_CONFIG_REQ does not accept correct packet length 
 - PSDNM-420:  Master channel init does not work when commucation with the slave interrupt by database delete on slave 
 - PSDNM-422:  Deconfiguration possible when 'CONFIG_LOCK' set. 
 - PSDNM-423:  After watchdog timeout occurs TLR_E_WATCHDOG_TIMEOUT is not shown in Communication error 
 - PSDNM-430:  update to rcX v2.1.10.0 and v2.0.8.24 
 - PSDNM-434:  Provide DeviceNet Master Libraries with RCX v2.1.x support 


V2.3.17.0
---------
 - PSDNM-413:  Quick connect does not work with 1791D-16B0 
 - PSDNM-415:  DEVNET_FAL_CMD_REMOTE_SERVICE_REQ fails with timeout 0 


V2.3.16.0
---------
 - PSDNM-409:  Channel Init does not clear packet configuration 
 - PSDNM-412:  Cyclic and Change of State connection fails 


V2.3.15.0
---------
 - PSDNM-406:  DeviceNet Master fails to connect to slaves with cyclic connection consumed size null 


V2.3.14.0
---------
 - PSDNM-397:  DNM device does not send duplicate mac id check on bus when configured with packet as stand alone master (no slave configured) 
 - PSDNM-401:  Master not functional after CAN Bus Off and bus power reset 
 - PSDNM-403:  Wrong response on Firmware identify request 


V2.3.13.0
---------
 - PSDNM-398:  DNM does not show led red when receive DUP MAC after first DUP MAC request sent during reset  process of ID object 
 - PSDNM-399:  DNM shows led green blinking when receive DUP MAC after first DUP MAC request sent during reset process of ID object 
