--------------------------------------------------------------------------------
PROFIBUS Slave
--------------------------------------------------------------------------------

V2.9.0.1
--------
 - PSDPS-470:  Stack is at unexpected state after fast BusOff, BusOn sequence 


V2.9.0.0
--------
 - PSDPS-182:  Duplicate use of error codes 
 - PSDPS-313:  Add new error codes for APS/FSPMS reset pending 
 - PSDPS-348:  Get_Cfg reports some cfg data while stack are unconfigured 
 - PSDPS-350:  Bus ON is not set on sending a PROFIBUS_FSPMS_INIT_MS0_REQ. 
 - PSDPS-357:  NJ 10 fails on high DPV1 Read/Write load 
 - PSDPS-361:  Boot Medium bit's are incorrectly set for HXNX50 
 - PSDPS-369:  set network state to Offline after watchdog error 
 - PSDPS-411:  Improve error code handling in PROFIBUS_APS_SET_CONFIGURATION_REQ 
 - PSDPS-446:  NCF_Communicating Bit is not cleared synchronous when process data is unvalid  
 - PSDPS-447:  Setting of 'No_Alarm_Supported' flag at set configuration request does not reject configured alarms 
 - PSDPS-455:  NXLOM SharedMemory example contains wrong comment regarding module configuration 
 - PSDPS-458:  Invalid use of TLR_BOOLEAN in API Header 
 - PSDPS-462:  PROFIBUS_APS_WARMSTART_PRM_REQ is no longer supported 
 - PSDPS-464:  Transmission type is not set at RCX_GET_DPM_IO_INFO_REQ 
 - PSDPS-465:  update to rcX V2.1.11.9 and V2.0.8.32 
 - PSDPS-467:  [NJ100] Rotary switch evaluation not working as expected 


V2.8.1.0
--------
 - PSDPS-445:  On a disturbed bus multiple PROFIBUS_FSPMS_CMD_CHECK_USER_PRM_IND are send 
 - PSDPS-448:  configuring more than 244 I/O modules may crash firmware 
 - PSDPS-449:  Pending alarm may be overwritten from diagnosis 
 - PSDPS-450:  Diagnosis request is signalled without new diagnosis in buffer 
 - PSDPS-451:  Alarm specifier is wrong on slow bus cycles if more than one is triggered in a short time 
 - PSDPS-452:  No alarm sequence possible after master configured slave without alarm sequence 
 - PSDPS-453:  feature: Implement a mechanism to read out some parameters from the stack 
 - PSDPS-454:  Global Control Clear does not update SAP 57 ReadOutput 
 - PSDPS-465:  update to rcX V2.1.11.9 and V2.0.8.32 


V2.8.0.2
--------
 - PSDPS-452:  No alarm sequence possible after master configured slave without alarm sequence 


V2.8.0.1
--------
 - PSDPS-454:  Global Control Clear does not update SAP 57 ReadOutput 


V2.8.0.0
--------
 - PSDPS-438:  General Diagnostic is not displayed at SYCON.net 
 - PSDPS-439:  Update Profibus DL V2.1.7.0 
 - PSDPS-440:  Fileheader reports old/wrong module information 
 - PSDPS-442:  Slave responds with "NotSupported" instead "PrmRequest" 
 - PSDPS-444:  Extended Status block - mixed data length information 


V2.7.12.0
---------
 - PSDPS-442:  Slave responds with "NotSupported" instead "PrmRequest" 
 - PSDPS-444:  Extended Status block - mixed data length information 


V2.7.11.0
---------
 - PSDPS-438:  General Diagnostic is not displayed at SYCON.net 
 - PSDPS-439:  Update Profibus DL V2.1.7.0 
 - PSDPS-440:  Fileheader reports old/wrong module information 


V2.7.9.0
--------
 - PSDPS-227:  DMA shall not started with 0 length 
 - PSDPS-326:  New configuration pending flag is always set. 
 - PSDPS-347:  fClearFlag not set when data is cleared 
 - PSDPS-349:  No validation of bSlaveAddr variable in the PROFIBUS_FSPMS_INIT_MS0_REQ available. 
 - PSDPS-362:  ulHWFeatures value depends of stack state 
 - PSDPS-372:  Missing bCfgLen validation leads to crash 
 - PSDPS-373:  missing SIF cfg data validation 
 - PSDPS-375:  Error counter are incremented by 2 for cable disconnecion 
 - PSDPS-376:  fNewFlag remains set when no connection with master 
 - PSDPS-378:  SIMATIC module diagnostic shows incorrect HW revision for CIFX 
 - PSDPS-422:  WRMSTRT_FLG_NO_ALARM_SUPP requires Alarm_Sequence_Mode_Count=32 
 - PSDPS-424:  update to V2.1.11.0 
 - PSDPS-434:  Change LED for slave at clear state 
 - PSDPS-435:  If no additional user parameter are configured accept 7 octett SetPrm 


V2.7.8.0
--------
 - PSDPS-418:  On bus cycle times < 300s the FSPMS fails to send state_changed_ind and does not stop DL-task 
 - PSDPS-419:  Wrong validation state of output data between FSPMS and AP task 
 - PSDPS-420:  Init_Ms0_req reference->reads uninitialized pointer 
 - PSDPS-421:  Update ProfibusDL to V2.1.6.0 


V2.7.7.0
--------
 - PSDPS-413:  update to ProfibusDL V2.1.5.0 
 - PSDPS-414:  update to rcX v2.1.10.0 and v2.0.8.24 


V2.7.6.0
--------
 - PSDPS-405:  cyclic I/O connection is rejected when less than 5 bytes parameter data are used at GSD 
 - PSDPS-406:  receiving invalid SetSlaveAdr profibus telegram (length < 4 bytes) leads to undefinded stack behaviour 


V2.7.5.0
--------
 - PSDPS-401:  COMM_COS_READY and COM_COS_RUN bit not correctly handled on channel init 
 - PSDPS-402:  I&M handling for slot != 0 no longer working after cable reconnect 
 - PSDPS-404:  I&M 0 states that I&M is implemented according withdrawn I&M specification v1.2 


V2.7.3.0
--------
 - PSDPS-396:  Support of netRAPID 


V2.7.2.0
--------
 - PSDPS-275:  With existing config.nxd SetConfig is accepted but not used 
 - PSDPS-384:  [netX51], [netX10]: Wrong file header 
 - PSDPS-385:  [cifX]: Firmware does not start due to wrong HW option in FileHeader 
 - PSDPS-387:  Set Config are accepted when should not 
 - PSDPS-390:  NJ100 device not recognized correctly by Network Scan 
 - PSDPS-392:  [netX51], [netX52]: Firmware does not start 
 - PSDPS-394:  Firmware sometimes stuck after channel init 


V2.7.1.0
--------
 - PSDPS-370:  wrong alarmhandling if master sends unexpected alarm ack after configure prior data exchange 
 - PSDPS-379:  Support IO-Link call in FSPMS-Task 
 - PSDPS-382:  add netX52 XIP support 


V2.6.6.0
--------
 - PSDPS-358:  [NXHX - 50]  - Firmware blocks right after FW download 


V2.6.5.0
--------
 - PSDPS-328:  [NXHX 50] - COM LED not functional 
 - PSDPS-329:  loadable Firmware can not be opened with Tag List Editor 
 - PSDPS-331:  COM port does not work on NETX51 target. 
 - PSDPS-332:  ERR Led state is not correct in case of watchdog error 
 - PSDPS-333:  ERR led state are incorrect in case of wrong configuration 
 - PSDPS-334:  [cifX]: specific inibatch cfg can block firmware 
 - PSDPS-341:  Configuration failed when application controlled startup is selected in warmstart param 
 - PSDPS-354:  update Profibus HAL to Version 1.5.1 
 - PSDPS-356:  [netX500]: Firmware header contains wrong chip type entry 


V2.6.4.0
--------
 - PSDPS-351:  I&M functions doesn't handle >state conflict< correct and accepts every I&M index to be written 
 - PSDPS-352:  Slave adoption by Class 2 master does not work. 
 - PSDPS-353:  Wrong communication state if master changes bus modes: operate -> clear -> stop -> clear 
