---------> Version 1.14.11 - 08.08.2012

- M-59:	The headline "Defect Sensitivities" has been restored
- M-69: This was not really fixed in the previous version

---------> Version 1.14.10 - 01.08.2012

-JS-89: Spaces in the Job Names are allowed, but has to be forbidden to build up a name just done by spaces. (change of the GUI message 225)
-JR-57: The option of one report for all reels is not in there anymore. Its checkbox has been removed.
-SS-46: The switch to enable/disabel the global locator has been moved from registry into the system setup.
-M-69: Position of the error windows if two printing format are used to acquired the image, fixed.

---------> Version 1.14.9 - 30.07.2012

- DD-10 Fixed a bug in RDC algorithm that caused often the error value of 6.0.

---------> Version 1.14.8 - 25.07.2012

- Bug of "Maintain Job counters" check in the last setup step.

---------> Version 1.14.7 - 24.07.2012

- Bug of narrow lanes. In this case some lanes were not inspected at all and the ones in the overlapping region 
  were displayed as narrower.
- M-51: Wrong or missing indication of defective lane.
- Defect History: when zooming in up to the end the range displayed was brought to very beginning of job
- JS93: Bug in setup step 4 - the borders move slowly to the left side every time you access this step.
- Filtered reading of encoder impulse every 3 seconds to avoid possible collisions

---------> Version 1.14.6 - 12.07.2012

- Bug Fixed: Convertion mm to inches in the static offset between cameras.

---------> Version 1.14.5 - 06.07.2012

- M-54: Sensitivity inibition at the start of control, bug fixed.
- Bug fixed : clicking "No" on question for overwriting Job name, with report stopped and Automatic Report Start 
	deactivated, then clicking "Yes" for overwriting froze the Gui.

---------> Version 1.14.4 - 13.06.2012

- Reel 'index 0' bug fixed
- Potential risk of stopping a running report during a setup fixed.
- New Manual added.

---------> Version 1.14.3 - 19.04.2012

- M-16: Make it visible to the operator that the maximum number of 
        defects is reached by the system and the system has stopped 
	further defect detection.
- M-21: New RegKey "EnableReelNumberChange".
- M-22: Removed Job Name in header.
- M-29: New entry in the translation files for the word "Webshift" so
	in the green field it uses abbreviations.
- S-20: When loading of setup parameters fails, default tolerances are reset
	into the setup parameter structure.
- SS-11: Color buttons which are pressed in medium-dark grey for better feedback.

---------> Version 1.14.2 - 11.04.2012

- Limit of camera resolution if calcualted resolution is lower than
  physical camera resolution at 300m/mins. 
  If camera resolution is set to a lower value than the reference resolution at
  300m/min, band shift correction doesn't work.
  Consequence: max speed setting of 200 and 250m/min become useless.
- S-20: When loading of setup parameters fails, default tolerances are reset into the
         setup parameter structure.
- JS-48: It is not possible any more to overwrite default tolerance settings
         during setup.
- JR-21: It is not possible to display a report any more before having started a 
         report at least once.
- JR-41: A checkbox has been added in "Special functions" to enable automatic report
         start after completion of setup computation. 
         If feature is enabled, report is automatically started on job load.
- S-23: Support for new Chromasens Camera 
 
---------> Version 1.14.1 - 23.03.2012

- Official release of 1.10.35.

---------> Version 1.10.35 - 22.03.2012

- Moved New Reel event at the beginning if the new reel

---------> Version 1.10.34 - 21.03.2012


- Reset of Repeat Number on Job Start without take over data.
- Double entry of Setup completed suppressed.

---------> Version 1.10.33 - 19.03.2012

- Webshift taken off from the Log_Mess files.
- Lenguage for PDFreporter is taken from position 263 in the OCO lenguage file.
- OCO lenguage files added for France, Turkish, Espanol.
- Bug on reel numbering: fixed.
- JR-32Bug on defect entries in the report during too low speed: fixed
- JR-30:Setup interuption entrie is now added to report.
- During the report production events occurred during a control suspention are sorted out.
- JS-31: Now it is possible to set the top margin of the acquired area even in a setup with report restriction

---------> Version 1.10.32 - 08.03.2012

- JS-31: Point b. completed with new radio button management. It is possible to keep
         the distance and the meter counter from previous setup if report is not running.
- Report event on unwinder reel change has been changed to ControlFrozen_UnwinderReelChange
  and ControlReactivated_UnwinderReelChange.
- Report event on new job setup while report is running has been inserted when setup procedure
  is not completed. When the user presses stop, the entry JobSetupCompleted is written into
  the report.


---------> Version 1.10.31 - 06.03.2012

- JS-46: Cancel button has been added to alert box when user opens a new setup procedure
         while the report is still running. Same as JS-31
- SS-25: Message reporting that DD has been frozen for HW input is not displayed as
         pop-up any more but has been moved to notification area.
- JR-23: Print button is not visible any more in the display report dialog.
- JR-16: Scroll buttons have been made invisible in the display report dialog.
- Report: Entries have been adapted to document "Shark4000  PDF- Job Report Things to do"
          Revision: 1.4.
- JR-17: Display of report pause button in inspection mode fixed.
- JR-11: Fixed user buttons freezing on report generation. Same as JR-20.



---------> Version 1.10.30 - 27.02.2012

- M-12:  Defective cluster frame is drawn in blue (RGB(0,0,255)) if the global result for this 
         format is good.
- S-3:   "System stopped because of PCO failure" message has been re-enabled.
- S-6:   Added G11_OCO.exe program icon.
- S-11:  Timestamp in G11_GUI_StartupLog.txt fixed.
- JS-36: Change to message Nr. 490 in gui message files.
- Minimum and maximum values checked for Edge Threshold, Edge Coefficient.
- On tolerance correction by system due to incompatible resolution, displayed values are saved
  on dialog close (OK button).
- On change of max speed on first setup step, default tolerances are reloaded from configuration
  in current job.
- SS-12: If EnableMiniFormatPulse is enabled, FollowFormatPulse is forced to enabled. In the
         configuration dialog the checkbox "Follow format pulse" is greyed out if 
         EnableMiniFormatPulse is enabled.
- SS-15: Input signal should be effect only if the EnableHwControlFreeze is enabled.
- SS-16: HwControlFreezeInput registry key changed to HwControlFreezeInput(Pin#).
- JR-7:  <FormatNumber> report entry has been changed into RepeatNumber and placed between
         DistFromRollEnd and Time tag.
- JR-1:  Removed tags: StructureDefectContrast, SplashDefectContrast, StreakDefectContrast,
         HazingDefectContrast.
- JR-9:  On first open report, the Current reel checkbox is checked.
- JS-31: If the report is running not all the setup settings are available.
- M-15:  Control suspension message display management fixed.
- JR-3:  RunSensitivityPerc tag is there. RunSensitivity tag is inserted too with the value
         of the slider position. 
         PdfReporter (1.7.7) still converts the old slider position and not the percentage
         value.
- Added PdfReporter version 1.7.7 to update package.


  
---------> Version 1.10.29 - 10.02.2012

-JR-7: <FormatNumber> tag added.
- Fixed NotifyGenMess missing for "Control suspended due to HW inhibition".

---------> Version 1.10.28 - 07.02.2012

- GUI: changed NotifyAutorunning (stop automode fixed bug).
- Fixed report entries, rewrite all the element of the header before to push it in the report
- Fixed report entries, WidthDimension is equivalent from LeftBorder (1 Lane) to RightBorder (Last Lane)

- PCO: automatic recognition of camera version by reading a specific tag. Function "GetCmdBuffer" and
  "getCameraVersionData" management of K5_TAG_CONF_HW.
- Registry Key "FinSovr" was deleted and a new key named "Windowsoverlap" with the same meaning
  was inserted under common Registry keys. Its value is now controlled in the function "LoadConfig"
- PCO: Added control in Running on parameter "MaxDiffAggancioAccettabileVert"
- Change in "ValidateToleranceSet" function (min. contrast for Splashes is 20, 
  min. Streaks contrast is 10, min. Hazing contrast is 5)
- New Reg. Key: DoctorStreaksWidth, control the horizontal dimension of the streaks algorithm.
- ONCO: Change in function "DrawErrWindowsNew" to enlarge the error frame in case of 
  Doctor Streaks algorithm.
- PCO: Streaks algorithm changed.
- Speed suspention control popup is showed all the time. 


- HW suspended control.
- Two new reg. key: EnableHWControlFreez, HWControlFreezInput.
- New comment in the report about control suspention.
- Hysteresis applied in the Speed suspetion control and in the Aceleration suspention control.

- JR-1: Sensitivity table entry modifications.
- JR-7: <UseNumber> tag added. 
- SharkLex style buttons.

- JS-14: Green squares are deselected when touchung outside the area
  and the squares.
- JS-26 Job-Number is required to complete the setup procedure. 
  Enable a Pop-up window to avice the user.
- JS-31 Load a new job is no more allowed when a report is running.
  This message is not displayed entering a new setup because
  it is possible to perform another setup while the report is running.
  (this feature has to be descussed).
- JS-33 Message box to leave the setup added.
- JS-34 Fixed the match between area selected and number of the area.
- JS-35 This point need to be discussed more, there are some setup 
  parameters that change from a version to another. It is difficult to 
  set missing parameters in older jobs by default values.
- JS-36: Bug in in2-mm2 conversion and value check fixed in sensitivity
  settings dialog. It is necessary to identify a suitable mesureament unit
  in order to menage square inches for the dimension we use in our
  elaboration.
- JS-38 EnableAutoFormatLenManagement regkey is enabled again

- Exit GUI button removed 
- Substitution of CLOSE button with CANCEL button.
- SS-4 Exit SHARK 4000 entries changed in Exit Application
       Restart SHARK 4000 entries changed in Restart System
- SS-5: If user is logged in as standard user, the Info button that
  displays the life log window is disabled.
- SS-6: If the LoadSetup function fails for any reason, the default 
  tolerances are written into job data to be used for this job. This sets
  the default tolerances for a new job done after a new installation or
  an update in which job data are not compatible with job data coming
  from an older version.
- SS-10: A wrong date of a language file should never happen, but if it 
  happens, it "must" hapen only during installation or update procedure.
  In this case the technichian should manage the situation by fixing 
  the issue redoing the procedure or replacing the files with the 
  right files.

- M-12: lane colors are related to the current result. Light red frame
  is drawn to show the user where the last defect, shown in the upper
  frames, is located.
- M-13: Stop mode button drawn as pressed in when the status is stopped


---------> Version 1.10.27 - 03.01.2012

- JR-1: Sensitivity table entry modifications.
- JR-7: <Repeatnumber> tag added.
- Changed My_Mess*.txt files OCO and GUI
- JR-4: Obsolete tags restored.
- New interface buttons added

---------> Version 1.10.26 - 19.12.2011

- JS-2: Setup step 4: up and down buttons are enabled when entering
  the setup step.
- JS-4: Buttons Edit and OK are not visible any more because not used.
- JS-6: it is not possible any more to dial in the number of vertical
  formats but this parameter is completely managed internaly byt the 
  system.
- JS-9: selecting a lane division line by mouse click, the selected
  lane number is updated in the dialog.
- JS-13: control area catch corners are bigger.
- JS-14: control area catch corners are coloured green if selected.
- JS-15: a cross is added in selected area. The cross becomes green
- JS-16: It is not possible to select area 0 any more.
- JS-19: "Report start Distance" has been changed into "Report start
  length" and the unit has been added in last setup step and report
  window.
- JS-24: edited lane is reset on change of number of lanes.
  if the area is selected for movement.
- JS-25: notes have been added to separate notes file: 
    JS-25-feature_description.txt
- JS-27: on new control area a proposal of new area is done centered
  in the image.

- M-2: separation line has been made of the same thickness of the
  others.
- M-3: the number of digits after the comma for inch values has been
  set to 2.
- M-4: good lanes are coloured green, most defective lane is coloured 
  in bright red and other defective lanes are coloured a little darker
  red. Disabled lanes are coloured grey disabled.
- M-5: the most defective cluster is drawn in light red and maintained
  as long the defective cluster is displayed. Dark rectangles are used
  for other defective lanes/clusters within the same repeat.
- M-6: confirmation dialog is shown and function button doesn't change
  graphic any more.

- S-1: priority settable for both OCO and PCO by registry keys:
  PriorityClass and PriorityClassPCO. 1 is highest priority and 4 il
  lowest (normal).

- SS-1: if system is set to work with inches, values are converted into
  mm and sent.
- SS-7: Manuals are opened by the User Manual button.

- JR-2: Software version is inserted into Generator section within the
  XML file.
- JR-3: Slider values are reported in percentage in new tag
  <RunSensitivityPerc> and the old <RunSensitivity> is not written any
  more.
- JR-4: defect size is not reported any more in the report.
- JR-6: <Type> definition changed to <Type>SHARK 4000</Type>
- JR-8: <ReportVersion> not written any more because useless.

- Window dimension blocked to values 8, 10, 12 
- PdfReporter 1.7.4 version added
- RDC feature inserted; in the G11\DD registry key tree following
  keys have been added:
    - EnableRDC: to enable/disable the feature
    - CorsaX_RDC: runlength in crossweb direction
    - CorsaY_RDC: runlength in web direction
    - FinSovr: percentage of window overlapping
  Following key has been added in the G11 registry key tree:
    - RDC_only_additional: executes RDC only if cluster is defective.

---------> Version 1.10.25 - 01.12.2011

- Additional trace information on PCO restart
- PCO overload message is not displayed ony more. Additional
  entries added to che activity log if the overload occurs.
- The "System stopped because of a PCO failure" message is not
  displayed any more.

---------> Version 1.10.24 - 30.11.2011

- Fixed bug on PCo - Crash during operative mode change.
- Fixed bug on PCo - Memory leak on PCo entering inspection mode.

---------> Version 1.10.23 - 16.11.2011

- Additional activity log entries focused on format pulse management.

---------> Version 1.10.22 - 11.11.2011

- Bug Fixed: Start acquisition - zoom max, restart of acquisition.
- Memory access management in DefectHistory::Lock function.
- Memory access management in storing defect data in defect
  hisotory slot.
- Stearks Algorithm Optimizeds

---------> Version 1.10.21 - 19.10.2011

- Optimized thread handling for multicore PCO.

---------> Version 1.10.20 - 18.10.2011

- Error message on stepping back from setup step 2 to step 1 fixed.
  The error message could also be displayed on acquisition stop.

---------> Version 1.10.19 - 05.10.2011

- Global locator: if a PCO has no consistent fingerprint, it uses the 
  offset value coming from the OCO as global locator offset even if its
  own offset value is computed as reliable.
- Global locator: if the automatic fingerprint runlength reduction feature
  is enabled, only values coming from trustable PCOs can limit the value
  set in configuration. If no PCO is trustable, the minimum runlength 
  value set by registry key AutomaticFingThrMinDistMM is got as global 
  locator runlength value.
- GUI: camConfig.txt configuration file is no longer supported.
  LoadLights feature (reading the light current values on each system
  start) has been suppressed.
  The EasySet configuration menu activation is now managed setting the
  registry key: EnableEasySetSupport.
- Timestamp information in easy set protocol log.

---------> Version 1.10.18 - 23.09.2011

- SaveImage function optimized. It uses less memory in saving images
  to disk.
- Inch display bug in defect history on defect information fixed.

---------> Version 1.10.17 - 19.09.2011

- Stallmanagement bug fixed. Stallmanagement was not enabled when camera
  failed during machine stop phase.
- Delay of 1s between synchronous and asynchronous response to EasyView
  in case of hard token request.

---------> Version 1.10.16 - 24.08.2011

- Token UDP channel: if both systems own the token, a warning message is
  displayed on the GUI. An entry is also reported into the activity log.
  It is possible to enable/disable the display of the message by setting 
  the registry key "easySetHBcheckTokenConflict". If is set to 1, the message
  is displayd, otherwise not.

  !!Note new registry key: easySetHBcheckTokenConflict

- When the wrong message length is read on a token request, the socket is not
  immediately closed, but the TOKEN_DENIED message is sent before closing the
  socket.
- Token status refresh in inspection mode fixed.
- Gui message "The software needs to be restarted" on closing of the special
  functions dialog suppressed.
- Tolerance levels are written in the "RunningJob.txt" file by starting    inspection
  (debug purpose).
- Report total reel number (reel n of n-1) fixed. Wrong reel number assignement in
  function FillReportOverview.
- Gui crash on access of defect history if set in inches and a reel change is 
  displayed, fixed.
- In memory allocation function, deallocation and allocation are threated
  separately in order to avoid failing of allocation on failing of deallocation.
- EasySet message on PCO re-connection fixed if not W&H machine.

---------> Version 1.10.15 - 08.08.2011

- UpdateActiveLanesPcoThread. Deleted redundant instruction.

---------> Version 1.10.14 - 25.07.2011

- Token exchange protocol improvement.

---------> Version 1.10.13 - 25.07.2011

- New UDP control channel integration for token exchange protocol.
- Error Refresh GUI due to token comunication. Fixed.

---------> Version 1.10.12 - 13.07.2011

- New UDP control channel integration for token exchange protocol.
  New registry keys added:
    - easySetHBip: address of the easyset UDP server
    - easySetHBlocalPort: local port for UDP messages
    - easySetHBport: remote port on easyset system to send UDP messages to.
- Median filter on global offset reults can be enabled/disabled by
  registry key. (Key: EnableMedianFilterOnGlobalLocator).

---------> Version 1.10.11 - 22.06.2011

- Previous reel selection in report display fixed.
- When reel report feature is changed, the system prompts the user to restart
  the software to make the changes permanent.

---------> Version 1.10.10 - 30.05.2011

- PDFReporter 1.6.x integration. Inch option was inserted into command
  line.

---------> Version 1.10.9 - 13.05.2011

- Fix of inch indication in opening virtual keyboard in setup step 1.
- Fix of the total acquisition length check in data validation function in setup
  step 1.
- Fix of inch value indication in wrong repeat length notification dialog.
- Data mirroring mismatch on changing light configuration fixed.
- Tolerances dialog supports inches.

---------> Version 1.10.8 - 15.04.2011

- MiniFollowFormatPulse feature.
  New registry keys: 
    EnableMiniFollowFormatpulse: enables the feature.
    MiniFollowFormatpulseRunL_MM: sets the runlength for the fp algorithm.
- Median fingerprint offset computation on PCO side on 5 samples.
- Cameras are switched of and disconnected even if the cameras are not connected.
  Access is requested, if granted lights are switched off and cameras are disconnected
  again.
- Changes in the distance computation in report overview.
- Stall situation in report saving fixed. Pausing the report during defect detection
  and stopping the machine, caused report saving stall if displayed.

---------> Version 1.10.7 - 15.04.2011

- Possible access violation and OCO crash in case of new setup with different number
  of lanes from the old setup and feature "Report Manual Reset (1.10.3)" is disabled.
  If the number of lanes is changed during setup, it is not possible for the user
  to choose to reset the report or not because the report is forced to be reset due
  to the change of numbers of lanes.
- Tolerances edit button disabled when modifying control areas.
- Save setup button in last setup step sometimes greyed out (reported by nyco) fixed.
- Misalignement between golden and defect returning from defect history to automatic
  mode fixed.
- No navigation response by defectNodefet image on first refresh fixed.

---------> Version 1.10.6 - 07.04.2011

- Automatic defect detection Stop/Start during normal working condition
  fixed. Problem due to PCO worker thread synchronization.

---------> Version 1.10.5 - 18.03.2011

- Management of retrun value in setting control sensitivity during
  defect detection.
- Management of swap/unswap failure for internal buffers durin setup
  procedure.
- Defect history action button state managed during modus transition from
  defect history to automatic mode.
- Fixing of cross-web locator threshold management by multiplier 4x of the 
  threshold.

---------> Version 1.10.4 - 07.03.2011

- Quick sensitivity modification dialog box.

---------> Version 1.10.3 - 01.03.2011

- Reverse Web Movement and Mirror Management. (Notice: new regKey RevEncoderOnRevWeb).
- Report Manual Reset.
- Summaryonly Flag for PDF Reporter is Used Only if PerReel Report is FALSE.
- Report Activity Entry Tag Changed From NotActive to Inactive.
- Fixed Top Margin Computation

---------> Version 1.10.2 - 04.02.2011

- PCO worker thread stall management fixed.

---------> Version 1.10.1 - 25.01.2011

- Integration of new VCO software. This feature could be anbled setting
  the registry key EnableViewMonitor to 1. If the value of the key is 0
  the feature is disabled.
- Bugfix for inch value display in defect images during automode.
- Short rolls are sorted out from report. This feature could be enabled setting
  a value greater than 0 for the registry key RollMinDistanceM. If the 
  value of the key is 0 this feature is disabled.
- Navigation in inspection mode and togle between golden and live image
  fixed.
- Support for Spanish language (only GUI).
- Fix of navigation and zooming in AutoMode on first zoom of defect image.


---------> Version 1.9.2 - 23.12.2010

- AMI interface pointer multiple allocation fixed.
- AMI management: the AMI board is no longer inited on software startup.
  Board initialization is carried out on setup procedure start and 
  defect detection start.
  The initialization sequence is as follows:
  - Setting of repeatlenght
  - Board initialization (Backward, Foreward)
  - Setting of the synchronization type (mark....)
- "Save as default" button active for value saving if configuration 
  tolerances values are set.

---------> Version 1.9.1 - 07.12.2010

- MM^2 defect size management:
  - StructureAngCoeff: registry key was added
- Avdanced zoom feature: defect and golden display have 2 states: autozoom and 
  user zoom. The user switches from autozoom to user zoom by increasing the zoom
  factor activating the zoom buttons or navigating within the image by clicking
  on the image display.
  The user can switch back from user mode to auto mode by activating the min zoom
  button. 
  In auto zoom mode the defect is centered on the cluster display.
- Dependency on ICM package number for line delay setting removed.
- ?Bilinear? interpolation algorithm for zooming and resolution adaption.
- Toggle function in running for defect highlighting.
- Warnings if system is running out of disk space.
  Two registry keys have been added: 
    FreeHdSpaceWarningMB: (default 3000MB). If the available disk space is less
                          than the value of this key, a warning is displayed 
                          but it is possible to go on with the setup procedure.
    FreeHdSpaceStopMB:    (default 500MB). If the available disk space is less
                          than the set value, a warning is displayed but it is
                          not possible to carry out the setup procedure.
  The check of disk space availability is performed each time a new setup 
  procedure is started.

---------> Version 1.7.40 - 22.10.2010

- Bugfix: lane disabling after reel change if "enable lanes after reel change" feature is
  enabled.
- Bugfix: additional monitor. Display of black part of the image. PCO misalignement (wrong img
  number) could still occur.
- Check of miniature grey border variable (if < 0 -> set to 0).
- Display of defective cluster in defect history miniature overview.
- Global locator bug on 180 degree rotation fixed. Occurred only if all format impulse werde 
  equal.
- If no PCO is trustable the global offset computed by the OCO and sent to the PCOs for global
  locator feature, is always 0.

---------> Version 1.7.39 - 07.10.2010

- Bugfix: distance display of first reel after setup.
- Exception handling for the RicentraFiguraMatrix function. 
- Feature of correction of image length due to mismatch between real and set format in case of 
  180 degree rotation, disabled.

---------> Version 1.7.38 - 06.10.2010

- Exactly the same version as 1.7.37 but PCO compiled in release version. In 1.7.37 the PCO
  module had been build as debug version.


---------> Version 1.7.37 - 05.10.2010

- Change in fingerprint consistency computation. Even the default value of the registry key
  FingerprintConsistencyThreshold was modified from value 10 to 100.
- Change in the approach of selecting the offset result in case of total fingerprint on PCOs.
  the difference is now influenced by OldFingOffset and the idea is to choose the nearest possible
  offset to the value of OldFingOffset.
- Bugfix of control freezing during mode change (defect history to automatic mode) due to a double 
  call to the modus change function.
- Fix of wrong ip address in connection drawing during PCO connection procedure.


---------> Version 1.7.36 - 24.09.2010

- New approach in global locator algorithm.
  Concept of "trustable" PCOs:
  
  Definitions:
	- consistent fingerprint: a fingerprint is considered consistent if its variability is
	  greater than a set threshold. That means that enough information is present to perform
	  reliable locating.
	- trustable PCO: the locator offset values are managed by the OCO only if a PCO is trustable.
	  A PCO is considered to be trustable if it partecipates to live display, if it partecipates to
	  defect detection and its fingerprint was computed as consistent during setup procedure.
	- global offset: it's the offset value computed by the OCO based on the values trasmitted by the
	  PCOs, sent to the PCOs and used by them as starting point for the next global locator computation.
	  In other words, its the history of all locator result condensed in one result.
	- reliable offset: an offset value is trated as reliable if the reliability value is beneeth a 
	  threshold. This threshold is 
  
  Approach description:
	  There are two different approaches if the follow foramt impulse feature is enabled or not.

	- Follow format impulse feature disabled.
	  In this case each PCO works for its own in computing the global locator. There is no history
	  kept in global locator offset computation.
	  
	- Follow format impulse feature enabled.
	  In this case the offset value resulting from the locator algorithm is sent to the OCO. The OCO
	  selects the most suitable offset value for the locator procedure at next step and sends this
	  value (the same for all PCOs) to the PCOs. The PCOs use this value as starting offset for the 
	  global locator offset computation.
	  
	  - How does the OCO select the most suitable locator offset value for next step.
	    Only values coming from trustable PCOs are managed. If the offset coming from a trustable
		PCO is reliable, its value is inserted into the average array. The most suitable offset value is
		then computed as the average value of the last 15 recorded samples.
		
		Exceptions:
		- The average value queue has not been initialized jet. In this case offset values coming from
		  trustable PCOs are managed even if they are not reliable. The minimum offset is then chosen and
		  the average queue is initialized to the chosen value.
		- Results coming form a total fingerprint: a total fingerprint request causes the averge value 
		  queue to be reset. Following results coming from the PCOs and related to the total fingerprint 
		  are managed and the smalles offset is considered as reliable. The whole average value queue is 
		  then set to this value.

	  - When is a total fingeprint requested by the OCO?
	    - If the last offset values coming from the trusted PCOs are reliable but the difference is greater
		  than half of the global fingerprint runlength.
		- If the last 5 offset results coming from trusted PCOs are not reliable.
		- If only one PCO is trusted and within the last 5 results, the max value and the min value differ 
		  more than half of the global fingerprint runlength.
		  
	  - What happens when after a global fingerprint request?
	    - The next results coming from trusted PCOs are managed only if they're related to a total fingerprint.
		  The minimum offset is then considered as reliable and sent to the PCOs as global offset value. The 
		  average value queue for global offset computation is then initialized to this value.

Notes:
- New registry keys:
    - FingerprintConsistencyThreshold: this key sets the threshold value for fingerprint consistency. 
		A fingerprint is considered as consistent if the value of the variability is greater than 
		the set threshold value.
	- GlobalLocatorInterval: this keys sets the interval in number of results for the global locator
	    offset value recording. 
	- GlobalLocatorSamples: this key sets how many samples in a row have to be recorded once the interval
	    for global locator result recording had expired.
	

---------> Version 1.7.35 - 20.09.2010

- Format length provided to the AMI board changed. The new value is computed by:

		AMI_format_length_value = 4 * Format_length_(mm) / Encoder_resolution_(mm/pulse)

---------> Version 1.7.34 - 16.09.2010

- Fix of PCO number in setup log feature (Sending setup parameters to PCO4 (.\my_module.cpp,2297,GoSetup)).
- Notify of missing gear signal on web start fixed.
- Fix of soft keyboard repaint on window overlay.
- Exception handling is settable by registry key "EnableExceptionHandling"
- Added AMI board management

Notes:
- Following registry keys have been addod for AMI board management:
	AMI_configFilePath: AMI board synchronization file path.
	AMI_direction: sets the direction for AMI configuration [FOREWARD - BACKWARD].
	AMI_enable: enables AMI board support.
	AMI_markType: AMI board synchronization mark type, possible values:
		FREE_MARK, 
		GEAR_ONLY,
		DEFINED_MARK, 
		BST_CLASSIC_MARK,
		AUTO_DETECT_MARK_PATTERN,
		MASCHINE_RESET_WITH_STRETCH_COMPENSATION
	AMI_syncOnMark: AMI synchronization on register mark [0 - 1].
	EnableRewinderMode: for future use to set parameters on the GUI in
		rewinder mode working with the AMI Board.
		
  

---------> Version 1.7.33 - 07.09.2010

- Wrong or missing activation code management. Software needs to be restarted.
- CloseHandle in MyClosePipeClient is now wrapped into a try.catch block.
- Resampling of overviewpicture in defect history fixed.
- Fixed dependency of static offset on speedmode resolution.
- Fixed dependency of static offset on scan direction.
- CResampler::SaveImage has been made safer.
- GetMinitaureForErrWindow has been made safer.


---------> Version 1.7.32 - 20.08.2010

- Exit application button on PCO architecture dialog during PCO conection.
- Setup log feature. A file is written every time a setup is performed. In this file the setup
  activity is traced. The feature can be disabled by the G11\Log\Setup registry key.
- Memory log feature. Memory allocations are written into the activity log file. Entries are
  written only if memory is increased. This feature can be disabled by the G11\Log\Memory
  registry key.
- Registry key related to Easyset protocol tracing has been moved into the G11\Log registry key
  folder. The new key is G11\Log\MachineProtocol. The default value is 1.
- Global locator logging. If the locator result provided by a PCO is not reliable, an entry
  is written into the activity log. To avoid to many entries in the log, a maximum of 100 
  locator entries is written. The counter is reset to 0 when defect detection is stopped and
  started again. This feature can be disabled by setting the registry key G11\Log\GlobalLocator
  to 0.

Notes:
- New registry keys to enable/disable additional log features.
  G11\Log\Setup
  G11\Log\Memory
  G11\Log\MachineProtocol
  G11\Log\GlobalLocator


---------> Version 1.7.31 - 13.08.2010

- Bugfix: zoom feature in 3rd setup step and inspection mode.
- Bugfix: crash on control stop with many defects.
- New registry key for pdf report path. Registry key is ReportPathPDF. Pdf reports generated
by the PDFreporter are stored into the given path.

---------> Version 1.7.30 - 04.08.2010

- Easyset protocol: a double TOKEN_GRANTED was sent to EasySet if cameras were disconnected. Fixed.
Normaly, when a TOKEN_FORCE_REQUEST is received, the Shark answers TOKEN_GRANTED_WAIT if cameras are 
connected and the TOKEN_GRANTED when it got into stopped and disconnected the cameras. If cameras were 
disconnected, the request was directly answered with TOKEN_GRANTED (replacing the TOKEN_GRANTED_WAIT) 
but the TOKEN_GRANTED after camera disconnection was sent too. Therefore the double TOKEN_GRANTED.

Notes:
- New registry key: EnableMachineProtocolDebug.
If this key is set to 1, debug entries of the EsasySet protocol are written into the activity log in
the diagnostic log folder.

---------> Version 1.7.29 - 29.07.2010
- Fixing of wrong defect cluster coordinates in xml report.

---------> Version 1.7.28 - 26.07.2010
- Fixing of aspect ratio computation if crossweb- and webdirection resolutions were different.
This bug became evident only for some format lengths.

---------> Version 1.7.27 - 21.07.2010
- Fixing of live display and result parsing if one PCO was exluded from defect detection on the 
first setup.

---------> Version 1.7.26 - 01.07.2010
- Fixing of DimFin parameter management OCO<->PCO(s)

---------> Version 1.7.25 - 23.06.2010
- Fixing of defect range exlusion feature

---------> Version 1.7.24 - 22.06.2010
- Fixing of report summary display issue
- Password display is crypted