--------------------------------------------------------------------------------
PROFINET IO-Controller V3
--------------------------------------------------------------------------------

V3.2.0.0
--------
 - PSPNMV3-232:  Feature: Add support for Read/Write record services with up to 16588 byte record length 
 - PSPNMV3-289:  Feature: Add API to configure which IP to use for AR (given by engineering or found in network) 
 - PSPNMV3-294:  extend configuration API to contain the calculated values for IsoM IO Controller application 
 - PSPNMV3-295:  Implement mechanism to indicate / receive remanent data to / from host application 
 - PSPNMV3-296:  wrong NameOfStation assigned automatically 
 - PSPNMV3-304:  legacy busscan not working as expected (returns last device found in the network twice) 
 - PSPNMV3-305:  configured firmware where configuration contains no IO Devices reports Connection timeout error 
 - PSPNMV3-307:  add API to read out the whole firmware configuration (including DPM layout) 
 - PSPNMV3-309:  Submodule after plug not parameterized 
 - PSPNMV3-310:  Reject invalid MRP Domain name setting 
 - PSPNMV3-311:  PPM active after RTA error PDU 
 - PSPNMV3-314:  Feature: Add API to modify automatic alarm handling independend from configuration 
 - PSPNMV3-316:  implement check of MRP Manager License Bit in SecMem and error handling in case of missing license 
 - PSPNMV3-320:  RPC trigger index is read during AR establishment even for legacy startup 
 - PSPNMV3-322:  wrong coded DCP Identify Request sent after configuration 
 - PSPNMV3-325:  MasterStatusBlock SlaveState is not handled correctly 
 - PSPNMV3-328:  Session monitoring not activated for Legacy Startup Mode 
 - PSPNMV3-331:  Controller generates unexpected Multiple Write request 
 - PSPNMV3-334:  Multiple write request with wrong sequence number when FSU enabled 
 - PSPNMV3-335:  Invalid OrderId reported 
 - PSPNMV3-336:  Wrong error returned when DCP DeviceInitiative requested. 
 - PSPNMV3-337:  Add check for mixed multiple interface mode 
 - PSPNMV3-338:  update several external components (e.g. several Toolboxes) 
 - PSPNMV3-340:  in case no port offers 100MBit/s FullDuplex no AR shall be established 
 - PSPNMV3-341:  invalid (old) IO Data sent to network after configuration is changed 
 - PSPNMV3-344:  In case a DPM Watchdogerror occurrs this is not always reported in DPM ulCommunicationError 
 - PSPNMV3-345:  IP configuration fault is not detected 
 - PSPNMV3-347:  Update PSDCERPC to V5.1.0.1 
 - PSPNMV3-349:  Negative fragmented packet status may be ignored by the firmware 
 - PSPNMV3-351:  update to PN Core 1.4.0.2 
 - PSPNMV3-352:  Feature: Add API for application to be able to modify VendorID and DeviceID 
 - PSPNMV3-363:  Configuration error set at runtime 
 - PSPNMV3-364:  add a new flag that is set in case a submodule with diagnosis is reported in ModuleDiffBlock 
 - PSPNMV3-367:  BF LED behavior wrong in case of Bus OFF 
 - PSPNMV3-368:  Garbage data delivered by Get Logbook Service 
 - PSPNMV3-372:  ulDiagFlags in service RCX_GET_SLAVE_CONN_INFO_REQ are not updated for all possible failures of configured IO Device 
 - PSPNMV3-373:  Connection via USB or UART unstable 
 - PSPNMV3-375:  Update to PSDRVETH V1.3.0.1 
 - PSPNMV3-378:  Introduce timeout for IRT startup 
 - PSPNMV3-380:  Legacy implicit read request does not work 
 - PSPNMV3-383:  Update to PSPNCORE V1.4.0.3 
 - PSPNMV3-386:  Update external PSLWIP to V3.2.0.3 
 - PSPNMV3-387:  Update PSDCERPC to V5.1.0.3 


V3.1.1.0
--------
 - PSPNMV3-196:  Integrate MRP Manager 
 - PSPNMV3-276:  Update to LwIP V3.1.0.2 
 - PSPNMV3-278:  Invalid NameOfStation in PNIO_APCTL_CMD_DCP_IDENT_IND (Legacy Bus Scan) 
 - PSPNMV3-279:  Address conflict detection not working as expected 
 - PSPNMV3-281:  AR resource deadlock when RPC Release.req not responded by device 
 - PSPNMV3-282:  Hilscher netIdent protocol not active 
 - PSPNMV3-283:  Adapt to PSPNCORE diagnosis database changes 
 - PSPNMV3-285:  Feature: Add API to be able to use IO Devices with Isochroneous Mode 
 - PSPNMV3-286:  Feature: Add local Profinet IO Controller cycle counter to DPM Input area 
 - PSPNMV3-292:  Multiple interface mode not implemented 
 - PSPNMV3-297:  Update to LLDP V5.0.17.0 
 - PSPNMV3-302:  Update Profinet Core to V1.3.1.0 


V3.1.0.1
--------
 - PSPNMV3-273:  Update to Profinet Core V1.3.0.2 
 - PSPNMV3-276:  Update to LwIP V3.1.0.2 
 - PSPNMV3-278:  Invalid NameOfStation in PNIO_APCTL_CMD_DCP_IDENT_IND (Legacy Bus Scan) 
 - PSPNMV3-279:  Address conflict detection not working as expected 
 - PSPNMV3-281:  AR resource deadlock when RPC Release.req not responded by device 


V3.1.0.0
--------
 - PSPNMV3-228:  add possibility for application to get information if IO Controller locally has a diagnosis (e.g. wrong neighbor is detected) 
 - PSPNMV3-233:  No RPC Release Service used when connection is terminated 
 - PSPNMV3-239:  add API for Supervisor DA AR 
 - PSPNMV3-250:  Confirmation for Bus on is delayed 
 - PSPNMV3-257:  Firmware crash/unresponsible when using xChannelBusState and xChannelReset 
 - PSPNMV3-262:  DCERPC Transfer Status ignored. 
 - PSPNMV3-264:  AR deadlock if DCERPC transfer error occurs in RPCConnect.req() 
 - PSPNMV3-265:  Invalid source mac address in application DCP services 
 - PSPNMV3-266:  Invalid DA-AR IP configuration accepted 
 - PSPNMV3-267:  Invalid values for Name of Station accepted by Establish DA-AR Service 
 - PSPNMV3-268:  Multiple Diagnosis Data in one Alarm are not supported 
 - PSPNMV3-269:   MauType Difference Mode activated if PDPortDataCheck configured 
 - PSPNMV3-271:  Portsubmodules with more than one digit not supported. 
 - PSPNMV3-274:  [comX100]: UART not working 
 - PSPNMV3-275:  [NJ100]: UART not working 
 - PSPNMV3-277:  Socket Api headers not distributed 


V3.0.81.0
---------
 - PSPNMV3-264:  AR deadlock if DCERPC transfer error occurs in RPCConnect.req() 
 - PSPNMV3-265:  Invalid source mac address in application DCP services 
 - PSPNMV3-266:  Invalid DA-AR IP configuration accepted 
 - PSPNMV3-267:  Invalid values for Name of Station accepted by Establish DA-AR Service 
 - PSPNMV3-268:  Multiple Diagnosis Data in one Alarm are not supported 
 - PSPNMV3-269:   MauType Difference Mode activated if PDPortDataCheck configured 
 - PSPNMV3-271:  Portsubmodules with more than one digit not supported. 
 - PSPNMV3-274:  [comX100]: UART not working 
 - PSPNMV3-275:  [NJ100]: UART not working 
 - PSPNMV3-277:  Socket Api headers not distributed 


V3.0.80.0
---------
 - PSPNMV3-228:  add possibility for application to get information if IO Controller locally has a diagnosis (e.g. wrong neighbor is detected) 
 - PSPNMV3-233:  No RPC Release Service used when connection is terminated 
 - PSPNMV3-239:  add API for Supervisor DA AR 
 - PSPNMV3-250:  Confirmation for Bus on is delayed 
 - PSPNMV3-257:  Firmware crash/unresponsible when using xChannelBusState and xChannelReset 
 - PSPNMV3-262:  DCERPC Transfer Status ignored. 


V3.0.60.0
---------
 - PSPNMV3-217:  add support for LinkStatus Indication 
 - PSPNMV3-219:  IRT operation not possible in several scenarios 
 - PSPNMV3-221:  feature: Add API to set the Version numbers (to avoid invalid numbers in SNMP) 


V3.0.50.0
---------
 - PSPNMV3-192:  RPC connection monitoring is active also legacy startup 
 - PSPNMV3-194:  reject configuration if IRT legacy startup and advanced startup is mixed 
 - PSPNMV3-195:  reject configuration with unsupported IRT requirements 
 - PSPNMV3-207:  add support of field "ulDiagFlags" in RCX_PACKET_GET_SLAVE_CONN_INFO_CNF_T 
 - PSPNMV3-208:  Multiple Write not functional 
 - PSPNMV3-209:  change handling of ulCommunicationState to match the new definition 


V3.0.40.0
---------
 - PSPNMV3-176:  DPM is uninitilized which leads to uninitilized data on the bus 
 - PSPNMV3-178:  Sycon.net does not show availability of any IO data (RCX_GET_DPM_IO_INFO_REQ not handled) 
 - PSPNMV3-185:  update to rcX V2.1.11.6 
 - PSPNMV3-187:  Firmware stalled on high network alarm load 


V3.0.30_MS_IRT
--------------
 - PSPNMV3-27:  Application Interface Inconsistencies 


V3.0.6_MS_RT_stable_250us
-------------------------
 - PSPNMV3-7:  Alarm Error Pdu not handled 
 - PSPNMV3-25:  CPM Startup/Watchdog not properly handled 
