MEGSV8x.dll revision history, beginning with 1.13

Version 1.35 17/07/2020
Fixes/updates:
	Memory leak eliminated; leak appeared if GSV86activateExtended failed with wrong ComNo

Version 1.34 22/06/2020
New functions:
	MEgsv86writeBytes (priviledged access only)
Fixes/updates:
	(int flags) of GSV86activateExtended stored
	Simulator for GSV-8 introduced (still _DEBUG only)
	GSV6BTrecover improved (usage not yet recommended)
	
Version 1.33 20/05/2020
Fixes/updates:
	Digital I/O functions: Enabled for GSV-6
	GSV86getAnalogOutType/GSV86setAnalogOutType: Adapted for GSV-6
	GSV86getTXmode(0): Sync-Master/Slave Flag as with GSV-8
	GSV86setValMapping: Improved error-Management
	GSV86MEwriteCal/GSV86readCal: Device communicates different data types: fixed
	GSV86readZeroValue: return value sign-extended with GSV-6
	
Version 1.32 17/03/2020
New functions:
	GSV6BTrecover (usage not yet recommended)
	MEgsv86setSoftwareConfig
Fixes/updates:
	SimulateDfilter: Fix for case: 1st time called & type=FIR
	GSV86getTXmode: detects Sync-Slave also with GSV-6 FW-ver 3.28

Version 1.31 09/03/2020
New functions:
	 GSV86readKeyDebounce @248
	 GSV86writeKeyDebounce @249
	 MEgsv86specialDevMode @250
GSV86getTXmode(Index=0): With GSV-6 it detects Sync-Slave, if available and sets bit 8 accordingly
GSV86writeRTCtime: New Index= -3: Sync with PC time (waits for change in sec), set as UTC

Version 1.30 17/01/2020
New functions:
	GSV86read1wire
	GSV86write1wire
	GSV86read1wireTemperatur
GSV86getModelInfo and GSV86readHWversion also read Version of Co-Processor with GSV-8
GSV86activateExtended: New flag ACTEX_FLAG_REMAP_1458333BAUD=0x20 for "flags": If set and the Bitrate is 1458333 Bits/s,
        the Com-port will be opened with 300 Bits/s instead. The reason is a particular serial-to-Ethernet converter
        "Perle IOLAN SDG1", that in "Full Mode" may not be able to use this special baud rate and can be configured to remap 300 Bits/s
        to the desired 1458333 Bits/s for the GSV-8 device.

Version 1.29
New function:
	GSV86getModelInfo
- Workaround in GSV86writeFTsensorCalArrExt for GSV-8 FW-bug 
- GSV-6BT treatment improved: Model earlier determined in GSV86activateExtended, information saved in
  gsvs[ComNo]->CoMCUver. Model info can be retrieved by GSV86getModelInfo
  Effect: GSV86getInTypeRange an others that call GSV86BTinitConfig execute faster for GSV-6(non-BT)

Version 1.28
- Neu Baud rate 1750000 Bits/s supported
- All Read functions: Read once repeated, if specific error ERR_NO_GSV_ANSWER at previous attempt.
  (before: second try at every error).
- GSV86getAllInTypesRanges: because of GSV-8: Counter-type added new: NUM_INTYPES=8
- GSV86writeFTsensorCalArrExt: NULL-ptr test for MatrixB and FakIdx omitted. Enable set Type & ggf Modelname only

Version 1.27: 11/02/2019
- New error codes: ERR_ACC_RDONLY 0x76 (device)
		ERR_WAIT_CMD_RESSOURCE_TOUT 0x30000069
		ERR_DLL_READTHREAD 0x300000F8
- Improved multi-threading capabilities: Safer if used with several caller threads

Version 1.26:
- Function GSV86getCounterFreqMode / GSV86getCounterFreqMode: New Constants for GSV-8
  - GSV86read: Improved error management
  - GSV86getValObjectInfo: Method updated for new GSV-8 Version 1.44
  
Version 1.25:
New function:
	GSV86readValueString
Functional changes:
	- Function GSV86copyFromSDfile uses GSV86readSDfileExt, if FW-version >=3.20
	- Function GSV86writeRTCtime: If Parameter "ix" is = -2, it waits for the next second of the system time
	  and then writes the new time to the device (v. 1.25.3.xx)
	- With many functions, Parameters of type "int" are checked for being <0; if so: function refused
Fix:
- GSV86BTreadBatteryVoltage: Return value was voltage*1000 or GSV_ERROR. Corrected to standard-errorcode
- GSV86readFTsensorCalArray: Function didn't work properly with newer GSV-6 and parameter SensorSerNo=NULL (ver. 1.25.1.xx)

Version 1.24:
- Long Command response supported, up to 270 Bytes can be read
New function (usable with GSV-6BT from Firmware version 3.20 on):
	GSV86readSDfileExt
	
Version 1.23:
New functions (usable with GSV-8 from Firmware version 1.39 on):
	GSV86writeFTsensorCalArrExt
	GSV86readFTsensorCalArrExt
	GSV86readAutoZeroSetting
	GSV86writeAutoZeroSetting
	GSV86getAutoZeroProperty
	GSV86setAutoZeroProperty
	GSV86readDevCalInfo
	GSV86MEsetDevcalInfo
Functional changes:
	GSV86writeFTsensorFromFile: If sensor *.dat file is for matrix plus (= MatrixB = matrix 2nd order),
	the additional values and the sensor type will be set in the device accordingly, if it supports that.

Version 1.22 (also 1.21.3.xx):
- GSV-6: Functions GSV86setMode,GSV86setFrequency,GSV86loadSettings,GSV86writeAnalogOutOffset
  that require a device reset: StartTX issued, is Tx was started before. Avoids unexpected stopping of
  measuring data stream, which happened before, if TX was permanently (non-volatile) stopped.
- Same with GSV86loadSettings, although pseudo-reset (re-init) performed by device itself
- GSV86MEwriteInputRange: Perform Reset with GSV-6
- GSV86BTinitConfig: Sent to device only it was not sent before, or if GSV86BTexitConfig was sent before
- GSV86BTexitConfig: Only sent to device, if GSV86BTinitConfig was performed before (safer)
- GSV86readSDfile: 2nd try on error at 1st eliminated
- GSV86setLoggerAlarmInterval: Disabled Alarm-Mode with setMode=0

Version 1.21:
GSV-6BT/ITA: SD-card file logger supported

New Command functions:
	 GSV86readRTCtime @220
	 GSV86writeRTCtime @221
	 GSV86readLoggerSettings @222
	 GSV86writeLoggerSettings @223
	 GSV86controlFileLog @224
	 GSV86querySDfileSys @225
	 GSV86openSDfileDir @226
	 GSV86getSDfileInfo @227
	 GSV86readSDfile @228
	 GSV86copyFromSDfile @229
	 GSV86getLoggerAlarmInterval @230
	 GSV86setLoggerAlarmInterval @231
	 GSV86BTgetLoggerInterval @416
	 GSV86BTsetLoggerInterval @417
Functional changes:
	 GSV86getValMapping/GSV86setValMapping usable with (newer) GSV-6 

Version 1.20:
- GSV-6 with multi-axis sensor: several calibration arrays supported
New Command functions:
	GSV86readRawValue
Functional changes:
	- Response timeout changed from 6s to 2s
	- GSV-6: GSV86getCounterFreqMode, GSV86setCounterFreqMode:
		- Reserved parameter CntNo must be=0
		- Flag usage changes (documentation changed only, see header)
With GSV-6: GSV86loadSettings: Functional safety improved
Bugfixes:
	- Bug in Digital Filter functions, which in rare cases lead to wrong results
	- With GSV-6: GSV86MEwriteInputRange
	- GSV86BTgetMaxPower

Version 1.19:
- Dynamic change of number of values in measuring value frame improved and bug-fixed
- GSV86read/writeDeviceHours: Available for GSV-6

Version 1.18:	30/06/2017
- Improved support for GSV-6/ITA device:
  E.g. automatic device reset with the following functions (Firmware version 3.10 and above):
  	GSV86setMode, GSV86setFrequency, GSV86setValMapping, GSV86writeAnalogOutOffset
  
- New Functions:
	GSV86getValMapping, GSV86setValMapping
	GSV86resetDevice
	GSV86getCounterFreqMode, GSV86setCounterFreqMode
  For GSV-6 BT only:
  	GSV86BTinitConfig
 	GSV86BTexitConfig
  	GSV86BTgetMaxPower, GSV86BTsetMaxPower
  	GSV86BTgetBTmode, GSV86BTsetBTmode
  	GSV86BTreadName, GSV86BTwriteName
  	GSV86BTreset
  	GSV86BTgetGSVonOff, GSV86BTsetGSVonOff
  	GSV86BTsetDefault
  	GSV86BTreadBatteryVoltage
  	GSV86BTgetInType, GSV86BTsetInType
  	GSV86BTsetDigitalOut
  	
Version 1.17:
- Supporting GSV-6/ITA device
- Bugfix GSV86triggerValue

Version 1.16:
- New function: GSV86getLastDeviceError
- Revision and reformatted (doxygen) comment in C-Header

Version 1.15:
- Fkt. GSV86changePassword: Length of new password not ignored anymore
- Typo-corrections at two of the error-explanation texts
- Review and update of the C-Header

Version 1.14:
- Bug in unit text array: UnitNo 10 was kg, now correctly: lb

Version 1.13, deployed to GSVmulti v. 1.37 and GSV8terminal.exe Version 1.8
New Fkt:
- GSV86getTEDSactive: determines if TEDS-data were really loaded