Release Notes __________________________________________________________________________________________________________ Bitte beachten Sie, dass die Release Notes nur in englischer Sprache verfügbar sind. Veuillez faire attention ą ce que les Release Notes sont seulement disponible en anglais. Please note that the release notes are only available in english language. __________________________________________________________________________________________________________ Application: IPEmotion PlugIn IPETRONIK X Last entry: 21.03.2024 Current version: 02.20.01 __________________________________________________________________________________________________________ The distribution of beta versions or release candidates to customers is not enabled without authorization of the management. System requirements: * Screen resolution: min. 1080 x 800 pixel * Processor: min. 2 GHz * RAM: min. 2048 MB * min. IPEmotion 2023 R3.1 Recommended system requirements: * Screen resolution: min. 1920 x 1200 pixel * Processor: min. 3 GHz Multi-Core * RAM: min. 6144 MB * Storage medium type: SSD Supported platforms: * Microsoft Windows 10 (64 Bit operating systems) * Microsoft Windows 11 (64 Bit operating systems) The following software will be installed: * Microsoft Visual C++ 2019 Redistributable * CAN-Server V02.00.07 (x64) - only installed with x64 setup * IPETRONIK PTP Driver V1.6.0.0 The following software is required: * Microsoft .NET 4.6.1 Framework The IPETRONIK X folder must be installed locally. __________________________________________________________________________________________________________ Rights IPEmotion PlugIn IPETRONIK X needs administrator rights during installation. Standard user rights are needed for working with IPEmotion PlugIn IPETRONIK X. __________________________________________________________________________________________________________ Network configuration: Network adapter configuration issues may arise if the measurement platform uses multiple network adapters. We have observed that deactivating the "unnecessary" adapters solves the communication problems with the Mx/Sx devices. Make sure that the network adapter connected to the Mx/Sx devices is correctly configured as DHCP client. ____________________________________________________________________________________________________________ Known limitations of CAN interfaces: ----------------------------------------------------------------- | Interface | | ----------------------------------------------------------------- | IPEcan | Firmware greater than 2.8 required | ----------------------------------------------------------------- ____________________________________________________________________________________________________________ Minimum Device Firmware requirements: ------------------------------------------ | Device | Type | Firmware | ------------------------------------------ | Mx-SENS(2)8 | 911 | 02.20.00 | | Mx-SENS2-4 | 916 | 02.20.01 | | Sx-STG | 920 | 02.20.00 | | Mx-STG2 6 | 912 | 02.20.01 | | Mx-SENS2-4 FAST | 917 | 02.20.00 | ------------------------------------------ | M-THERMO3 16 | 540 | 01.02.54 | ------------------------------------------ | M-SENS2 | 587 | 04.20.60 | | M-SENS2 DSP | 587 | 04.20.60 | | M-SENS2 250Hz | 591 | 04.20.60 | | M-SENS2 250Hz DSP | 591 | 04.20.60 | | M-SENS 8 | 567 | 04.20.60 | | M-SENS 8 DSP | 567 | 04.20.60 | | M-SENS 8plus | 568 | 04.20.60 | | M-SENS 8plus DSP | 568 | 04.20.60 | | M-THERMO2 | 578 | 04.13.00 | | M-THERMO2 HV | 557 | 04.13.00 | | M-THERMO2 u | 579 | 04.13.00 | | M-RTD2 | 581 | 04.10.03 | | M-THERMO 16 | 566 | 04.09.50 | | M-THERMO T | 569 | 04.09.50 | | M-THERMO 16T | 575 | 04.09.50 | | µ-THERMO | 563 | 04.09.50 | | M-CNT2 | 586 | 04.20.00 | | CANpressure | 595 | 04.10.00 | | M-THERMO96 16 | 593 | 01.03.01 | ------------------------------------------ | SIM-STG | 519 | 04.10.00 | ------------------------------------------ | M-SENS | 561 | 04.15.00 | | M-SENS DSP | 561 | 04.15.00 | | M-UNI2 | 584 | 04.13.00 | | M-THERMO | 560 | 04.09.51 | | Mc-THERMO | 573 | 04.09.03 | | M-FRQ | 562 | 04.09.00 | ------------------------------------------ ____________________________________________________________________________________________________________ Windows 7 / How to fix : Windows cannot verify the digital signature for this file The IPETRONIK PTP driver is digital signed with a certificate containing a SHA-2 hashing algorithm. The SHA-2 code signing and verification functionality was not available on windows 7. Microsoft have publish a patch to add this possibility on windows 7 : see: https://technet.microsoft.com/en-us/library/security/3033929 So, if the following error occur by the installation of the X-PI : Windows cannot verify the digital signature for this file Then test if the following security update is installed on the PC : - KB 3035131 - KB 3033929 If there are not installed, please install it manually in the following order : First the KB 3035131 and then the KB 3033929. It can be that the installation of the KB 3035131 say that the patch is already installed(even if it is not occurred by the update list), then install the second patch. And try the installation again. ____________________________________________________________________________________________________________ Windows 7 / How to fix : Windows cannot install the PTP driver silently For a silent installation of the included PTP driver, the following Microsoft Hotfix has to be installed: - KB 2921916 It is important to note, that this hotfix is not distributed automatically by Windows update! Without the hotfix any silent installation might fail on Windows 7. ____________________________________________________________________________________________________________ A parallel operation of the IPEmotion PlugIn IPETRONIK X and IPEmotion PlugIn IPETRONIK CAN is only supported if the CAN device support in the PlugIn IPETRONIK X is deactivated. ____________________________________________________________________________________________________________ Not not all parameters are conserved if detecting CAN devices that have been previously configured with the PlugIn IPETRONIK CAN and vice versa. ____________________________________________________________________________________________________________ CAN devices that are configured with the PlugIn IPETRONIK X cannot be detected with a PlugIn IPETRONIK CAN V01.13.XY and earlier. A minimum PlugIn Version of V01.14.00 (PlugIn IPETRONIK CAN) is required. ____________________________________________________________________________________________________________ Windows 7 x64: This is only an issue of the x86 version of the X-PlugIn on a Windows 7 x64 operation system! If disconnecting an X device (either by removing the ethernet connection or power supply), the notification of a reconnection is no more provided properly by the operation system (to the PlugIn). Thus all following messages concerning connection, disconnection and reconnection of devices on the affected ethernet connector are missing. Only the message regarding the PTP clock not being synchronized is displayed to the user. In this case, any furhter communication with the device(s) is interrupted. This means, that in the case of a lost connection during a running measurement, no values are displayed until the user restarts the measurement including an explicit hardware initialisation previously. The reason of this issue is an error message being returned by an operation system function. There is Microsoft Hotfix KB258857 addressing the underlying problem. Follwoing Hotfix of Microsoft solves the issue: https://support.microsoft.com/en-us/kb/2588507 ____________________________________________________________________________________________________________ Some firewall settings might block the PTP communication. In such situations the PlugIn uses a alternative algorithm to synchronize the measurement between X devices and PC. However this is unaccurate and should be avoided by configuring the firewall in a way to accept PTP communication. ____________________________________________________________________________________________________________ After changing the parameter setting / operation mode between internal and external time synchronisation, the devices MUST be POWERED OFF and ON again. Not repowering the device(s) will lead to data loss. Following list describes some situations, where the device (lightly) might need to be repowered (after hardware intialisation): After switching the setting between internal and external time synchronisation. Using devices the 1st time with IPEmotionRT (by default using external time synchronisation) if they have previously been used with the PC PlugIn (or INCA, ...) (by default using internal time synchronisation). Using devices the 1st time with the PC PlugIn after previously using them with IPEmotionRT. Connecting devices in a system that have different settings If resetting devices with the PC PlugIn or hardware dongle (default is internal time synchronisation) and then connecting the devices to the IPEmotionRT logger (using external time synchronisation) Loading a configuration and adapting the front number to some devices taking out of the shelf (configuraiton and device settings might differ). ____________________________________________________________________________________________________________ Offset Adjustment Definition / IPEbutton support Beginning with V02.14.02, the XPI sotres a different set of parameter values in M / SIM that define the adjustment group. This is required to support IPEbutton. However this means, that in case a offset adjustable device is initialized with and XPI version of V02.14.02 or newer and afterwards read out by an XPI version V02.14.01 or older (or IPEmotionRT 2020 R3.x or older) the information is not properly read back there. In those older versions, the adjustment group have to initialized then again. The other way does work properly (reading out an older defnition with XPI V02.14.02 or newer). ____________________________________________________________________________________________________________ Content The following points describe changes, restrictions and bugs in the corresponding versions: V02.20.01 FixedBug: If a M-SENS3 8 is configured with more than 8 different sample rates, not all channels do send data. Note: If a device chain contains a device, that has been configured with this or newer plugin version, detecint such device chains wiht previous plugIn versions lead to errors during hardware detection or synchronisation. V02.20.00 Removed following EOL devices from the default drop down list: M-UNI2, M-FRQ, M-THERMO 8, Mc-THERMO, M-SENS and M-SENS DSP Permanently removed italian localization Supporting new device M-SENS3 8. CAN Server is updated to V02.00 (x64) which is only available in the x64 setup. Removed following EOL devices from the default drop down list: M-UNI2, M-FRQ, M-THERMO 8, Mc-THERMO, M-SENS and M-SENS DSP Permanently removed italian localization V02.19.04 FixedBug: Parameter changes in fast setup mode are not possible if the device contains a status signal. FixedBug: In some situations, M1/M2 devices are no more responding after firmware updating modules in a module chain (case 73391) V02.19.03 This version is contained only in IPEmoitonRT and not released as separate IPEmoiton PlugIn Support CAN FD configuration for all CAN driver types Hardware detection / synchronization: Write device type in configuration file (needed for iDDS support in IPEmotionRT) V02.19.02 FixedBug: After hardware synchronisation on existing CAN FD systems, devices' status is reported as not available. V02.19.01 Fixed behaviour during hardware synchronisation. For present systems - only the current configuration regarding baud / data rates are taken into account without detection of all rates from the options. - Settings for automatic CAN ID assignment is taken from every system individually instead of using the general options (as is done for new systems. FixedBug: CANdb export of monitoring signals directly after manual cration. FixedBug: Some error messages on identical CAN resources are now displayed after hardware synchronisation. FixedBug: Identical CAN resources message not occurred after synchronization FixedBug: "Interne Gerätetemperatur" des M-THERMO3 16 falsch (zumindest unter IPEmotionRT) V02.19.00 Measurement data output via CAN-FD for the M3 series (support of CAN messages with more than 8 data bytes / CAN data baud rates of 2MBit and 5MBit) Improved support of changing turbines on the M-FLOW Enhanced display of HW/FW version of the M-FLOW Configurable suppression of measurement data output in the SENS modules after start-up / start of measurement Support of PTP synchronization with hardware time stamping at the logger (from X-FW V02.19 and IPEmotionRT 2023 R2 or higher) FixedBug: X-Modules: Inactivating channels reset samplerate, data output to default state FixedBug: IPEmotion PC GUI closes on start "Display" depending on the configuration FixedBug: Avoid unnecessary reboots of the X-Modules Known restrictions: CAN FD baud rates with 250kBit as arbitration baud rate can lead to unstable system behavior in certain cases and should be avoided V02.18.01 Set default value of parameter "Average" (averaging depth) to 20. Added column for averaging depth to channel grid Fixed importing CAN ID blacklist (did not work depending on the used IPEmotion version) Some IPEmotionRT related issues. V02.18.00 Monitoring Signals (M-THERMO3 16) Added terminal pictures and information for X devices (Sx-STG, Mx-STG2 6, Mx-SENS2 8, Mx-SENS2 4, Mx-SENS2 4 FAST) Changed default display fomrat of CAN Id's everywhere to hexadecimal display Display position of M3 devices Wording: Replaced all "Conductor Break Detextion", "Wire break detection" or "Break detection" in captions and hints by "Sensor break detection" FixedBug: Prevent CAN IDs being used by several modules FixedBug: After several aborts of synchronisations in sequence the UI might run into issues. FixedBug: M-Thermo3 16: System LED ist missing, device LED is not correct FixedBug: Disconnecting Ethernet-System while CAN-System is connected causes error FixedBug: Space can be set as channel or device names V02.17.02 - A2L export: Define packed mode as mandatory for signals with sample > than 100 kHz - A2L export: Fixed paramter MAX_DTO to 1466 V02.17.01 - Version being contained in IPEmotionRT V02.17.00 Status LED (channel, device, system) Reset offset adjustment in measurement devices Detection of ethernet adapters with conflicting IP adresses M-THERMO3 16: Display hardware license information PlugIn Options: Compatibility mode for SIM-STG devices A2L export: Exporting to A2l files in non pacekd mode is no more possible if the sample rate of any active channel is grater than 10KHz Added localization ko-KR, zh-CHS FixedBug: STG devices: Offset and reference value are reset to default in model after changing bridge parameters. FixedBug: M-FLOW: If connected via X devices (tunneling), hardware initialization leads to error messages. FixedBug: In some situations large systems might lead to instabilities. FixedBug: Offset value is not reset after changing STG parameters FixedBug: Device and system LED is removed in some conditions. V02.16.03 - Special version being contained in IPEmotionRT V02.16.02 Internal version included in IPEmotion 2022 Rx.y Added localization zh-CHS FixedBug: Don't display messages about connection status of inactive X or M devices Known restrictions: Extrem long system names (longer than 140 bytes - character count depending on contained special or multibyte characters or symbols) might lead to crashes FixedBug: M-FLOW with CAN-Server < V01.22.13: If connected via X devices (tunneling), hardware initialization leads to error messages. Updating CAN-Server to V01.22.13 fixes the issue. V02.16.01 PC version Added localization ko-KR V02.16.00 Internal version included in IPEmotion 2022 R1 Supporting new device M-THERMO3 16. Supporting status LED on channel, device and system node visualizing the current hardware status. Added columns to column grid for displaying current offset and target value of offset adjustment. FixedBug: Provide additional information if offset adjustment is triggered by Hotkey. IPEmotionRT: X-System disconnect message during full post processing is information. V02.15.02 - Added localizations ko-KR, zh-CHS Known restrictions: CSV import cannot distinguish thermocouple types R and S for the M-THERMO2 u. Hence both sensor modes are re-imported as thermocouple tpye S. V02.15.01 - Fixed Fast-Setup processing for Sx-STG V02.15.00 Fast-Setup: Support parameter change during measurement for selected parameters like averaging / sw filtering for X devices Provide offset of ShuntCheck in measurement values if ShuntCheck is triggered by Hotkey (during measurement) Added support for updating firmware of Mx-SENS2 4 FAST Removed support for following devices completely such that they cannot be used with the PlugIn any more: ES313.1, ES314.1, ES321.1, ES322.1, ES341.1 FixedBug: Multiple identical configured Ethernet interfaces in the options lead to duplicated and erroneous systems after hardware detection. FixedBug: Multiple identical configured CAN interfaces in the options lead to duplicated and erroneous systems after hardware detection. FixedBug: Setting the serial number of CAN interfaces in the PlugIn options to 0 causes errors and duplicate systems in hardware synchronisation. (case 56201) FixedBug: A2L Export: Timing properties of signals with sample rates of 40 kHz or 400 kHz are not correct. FixedBug: Provide additional information if offset adjustment is triggered by Hotkey. FixedBug: Disable controls in PlugIn options for configuring hardware detection in detection mode "Enable all" besides the buttons (they are needed for setting the IP address in the devices itself) Known restrictions: CSV import cannot distinguish thermocouple types R and S for the M-THERMO2 u. Hence both sensor modes are re-imported as thermocouple tpye S. V02.14.03 Known restrictions: CSV import cannot distinguish thermocouple types R and S for the M-THERMO2 u and M-THERMO3 16. Hence both sensor modes are re-imported as thermocouple tpye S. V02.14.02 All M / M2 devices with offset adjustment: Changed the stored adjust group setting in the devices (now using the KIMSIM definition again) to support IPEbutton. FixedBug: M-FLOW fluid names / serial number: Replaced ASCII control characters (> 0 ... < 32 and 127) and characters bytes above 127 (e.g. german Umlaute or all characters being on local code pages) by '_' FixedBug: M-THERMO 96: Fixed bug, introduced in V02.14.00, that on a detected device, the channel sample reates cannot be modified. Altough the bug is fixed for future versions, any IPEmotion configuration containing an M-THERMO96 device that had been detected with XPI V02.14.00 or V02.14.01 and stored, will stick to this issue. In thos cases, a manual patching of the configuration would be needed. V02.14.01 Added TEDS support to M-SENS 8 (DSP) and M-SENS 8plus (DSP) devices Warning message if the configuration of a detected channel contains an unsupported data type (that has been changed) FixedBug: Reference value of the offset adjustment is not reset to default after changing physical or sensor ranges. (case 57492) FixedBug: Voltage sensor modes are determined wrong, when importing from CSV. (case 58402) Known restrictions: Multiple identical configured CAN interfaces in the options lead to duplicated and erroneous systems after hardware detection. V02.14.00 Automatically restartt X devices beginning with FW V02.12 if certain parameter have been changed. Display warning message if the manual configured CAN ID is in the range of those being used for device configuration and communication (0x280...0x2FF). Supporting new device M-Flow. FixedBug: Detect if the CANopen PlugIn is active in parallel to ignore certain issues with CANopen devices on CAN busses that might disturb the communication between IPETRONIK devices and PlugIn IPETRONIK X. FixedBug: If sensor mode of any channel is changed, the sensor excitation is not reset to 0V. FixedBug: Mx-SENS2 4 FAST: Fixed wrong filter frequency if aliasing free measurement is configured and sample rate is 200 kHz: SW filter frequency 16666.6 Hz -> 25 kHz Known restrictions: Multiple identical configured CAN interfaces in the options lead to duplicated and erroneous systems after hardware detection. V02.13.02 - Special version being contained in IPEmotionRT V02.13.01 - Special version being contained in IPEmotionRT V02.13.00 - Added Support of Mx-SENS2 4 FAST FixedBug: Check box for configuration of 29 bit identifier is missing for M-THERMO family devices. FixedBug: If aliasing free measurement is configured, the software filter frequency is adapted to the maximum possible value when the sample rate is changed. (case 51089) FixedBug: M-THERMO 96: Wrong default physical unit after changing the sensor mode. FixedBug: In some situations IPEmotion crashes if some PlugIn options are changed after the Firmware update dialog has been opened previously. FixedBug: Display special message, if the software filter frequency range for aliasing free measurement with the current sample rate only a single value instead of a value range. Known restrictions: Multiple identical configured CAN interfaces in the options lead to duplicated and erroneous systems after hardware detection. V02.12.01 - Included Firmware V02.12.06 for Mx-SENS2 4 V02.12.00 - Multipoint scaling in X devices with Firmware V02.12.00 or newer - Store NoValue Value in M- and SIM devices FixedBug: IPEmotion crashes if channel description is too long. FixedBug: In some network configurations, X-Devices are detected but cannot be initialised afterwards. FixedBug: Update version strings after firmware updates (FPGA, Pic, Download Kernel). FixedBug: Null cannot be set as Sensor Min/Max in channel grid. Known restrictions: - M-SENS24 / MultiDAQ: Devices with firmware versions less than V04.10.00, cannot be updated with the X-PlugIn. V02.11.00 Support remote firmware update (IPEmotionRT only) V02.10.01 FixedBug: The update dialog is opened, if one or more MULTIdaq device(s) with firmware version less than V04.10.00 are present in the configuration. FixedBug: If hardware detection is called too short after powering on the devices, some devices measurement is not stopped such that these devices are detected improperly. (case 49154) Known restrictions: X-Devices are sometimes not working after detection if the PC has a further active network interface with a principally matching subnet. If configuring a channel with the scaling calculator in entry mode 'STG', unipolar sensor excitation values are not copied to the channel settings after exiting the scaling calculator. Instead the channels sensor excitation is set to 0V. - MULTIdaq devices require a minimum Firmware version of V04.10.00. Devices with older Firmware lead to a situation, where no connected device is properly detected and must be removed from the measurement setup (hardware). V02.10.00 Added Support of MultiDAQ. A2L Export supporting packed DAQ lists for sample rates greater than 10 kHz (requiring XCP 1.4 on client side). Hint available firmware updates. Don't alter CAN IDs of devices already in the configuration if performing hardware synchronisation. FixedBug: Device baud rate not being displayed in the setup grid. FixedBug: If importing CSV files with device creation, deactivate all channels of automatically created devices (not the initial available) before assigning data. Thus those channels are inactive, that have been created by the PlugIn but have no data been assigned to. FixedBug: A2L export of manually created devices is possible. FixedBug: After loading a CANdb for excluding certain CAN resources while automatic CAN ID assignation is active, conflicting resources are not resolved directly. This might lead to a situation where those channels have an error state set. Known restrictions: - MultiDAQ: After reset to default with the default connector or with the IPETRONIK X-PlugIn the channel and device names of the M-THERMO16 modules are not formatted correctly V02.09.01 Extended Tooltip information describing the known restrictions with changing internal and external time synchronisation. FixedBug: Fixed some de-DE localisation issues. Known restrictions: - After changing the parameter setting / operation mode between internal and external time synchronisation, the devices MUST be POWERED OFF and ON again. Not repowering the device(s) will lead to data loss. V02.09.00 Extended message if unsupported devices are detected. Support licensing of X devices Changed behavior for selecting sensor supply with TEDS sensors. Now always the greatest allowed available supply value is used, that is smaller than or equal to the TEDS nominal value. The hardware filter of X device channels is active by default for all X device types (changes behaviour of Sx-STG and Mx-SENS2 8). Importing sensor excitation is more flexible (if importing a bipolar value on a channel with only unipolar excitations and vice versa). Added the possibility to trigger the offset adjustment by the context menu of channels, devices or systems. Allow to deactivate the default send interval of X systems to support operation with certain devices (e.g. if connected to CAEtec datalog). Support deactivation / determination of internal time synchronisation for X systems to allow the synchronised measurement of multiple devices with an XCP 1.3 compatible master. FixedBug: set the right name and icon for device type 577 FixedBug: In some situations the physical unit is removed after 1st initialisation of a resetted CAN device. V02.08.01 FixedBug: Fixed channel settings after hardware reset if some free 2 point scaling had been configured previously. FixedBug: In some IPEmotion versions, the CANdb for excluding CAN IDs cannot be imported FixedBug: Option "Excluded CAN IDs" is not present in properties window V02.08.00 Removed warning in message window, that CAN devices with firmware versions < V04.00.00 cannot be detected. Added support of M-SENS24 Support new feature 'Ignore frequency drop' FixedBug: SIM-STG: Fixed default bridge type after manual creation to be "Full bridge". FixedBug: Issue with Firmware update if updating more than 2 CAN devices with firmware version smaller than V04.09.xx. FixedBug: Live-Zero adapts all unipolar TEDS detected elements V02.07.02 - added CSV import mode 'Front number' - Fixed bug: Measurement values of an X system might get out of sync if the fallback mechanism for the PTP driver is used. - Fixed bug: Issue with Firmware update if updating more than 2 CAN devices with firmware version smaller than V04.09.xx. V02.07.01 - Added localizations ja-JP, ko-KR, zh-CHS - Only provide english user manual for all languages FixedBug: Program termination during hardware initialisation in some rare situations. V02.07.00 - Support licensing of M-SENS2 (250Hz) devices with TEDS license - Support manual configuration of CAN resources - Added support of M-TDC - Current measuring range 4..20 mA for M-SENS and Mx-SENS2 family - HW detection interruptable - Support updating CAN modules in download kernel mode - Store free 2-point scaling in device (CAN devices only) - Show device count for each system - Fixed bug: If the channel's scaling mode is 'Passive sensors', it's parameter 'sensor excitation' can only be changed via the 'Scaling calculator' (SFB 40596) - Fixed bug: Mx-SENS2 4: Fixed default setting of hardware filter now being active. - Fixed bug: Fixed minimal sample rate of Mx-STG2 6 channels to 100Hz if option 'aliasing free measurement' is active V02.06.00 - PlugIn available for IPEmotion (x64) - Support updating of CAN device firmware in update dialog - Support inidividual sample rates for channels of X devices (all sample rates) - Support all (in IPEmotion) available bridge types in scaling calculator if selecting scaling mode STG - Display X-Link bus load - Display message if device calibration date is approaching - Fixed XML-CANdb export for signals containing VTAB (correction of the xml element 'Descr' into 'Desc'). V02.05.02 - Fixed hardware detection issue with devices having serial number >= 10000 - Fixed issue with CAN baud rate 1MBd (CANserver >= V01.17.03 required) - Fixed issue if importing a write protected CSV file - Fixed issue if importing CSV file with option CSV import mode set to 'Device creation' V02.05.01 - Updated contained X device firmware - Fixed some issue with CANdb export - Improved device detection on ethernet interfaces - Fixed bug with CSV-Import/Export of software filter types. This fixes the incompatibility with the CAN-PlugIn. However, the CSV-Import/Export of the software filter type is no more compatible with XPI V02.03.00 - V02.05.00 - Fixed displayed license information (displaying the wrong lincense for the Mx-STG2 6 in some situations) V02.05.00 - Removed manually configurable signals of X devices. Support automatic configuration of CAN monitoring signals instead by selecting output medium 'Ethernet and CAN'. - Added support of ES314.1 and ES322.1 - Added support of ETH gateway as CAN medium - Support up to 16 CAN interfaces per CAN medium - Support of parameter "Measuring Point Number". The value has no influence on the data acquisition. - Support sensor mode "Thermo element of type E" for "M-THERMO2 u" devices with FirmWare >= V04.08.00 - Fixed issue with channel names of CAN devices being limited to UTF-8 encoded strings with maximum length of 20 bytes (attention: special characters might be longer than 1 byte!). Now the names are allowed to be 32 bytes long (as they are in the IPEmotion PlugIn IPETRONIK CAN). - Added the save of the High Speed Mode on the Sx-STG device, need firmware >= V02.05.00 Known restrictions: - The devices error state is set if a device with FirmWare <= V04.08.00 is initialised having sensor mode "Thermo element of type E" configured after adding it manually (at this time, the devices FirmWare version is unknown in the configuration). - After initialisation of CAN devices, the channel description is limited to a string containing maximum 45 bytes (special characters might require more than one byte per character!). V02.04.00 - Added support for Mx-STG2 6 - M-FRQ/M-CNT2: Allow arbitary setting of parameter hardware filter in the range of 1 .. 30000 Hz (plus 0 for off) - M-FRQ/M-CNT2: Fixed setting / read out of negative threshold values (on and off) - X devices: Fixed displayed IP address of manually added systems and devices - Update device information (of manually added ones) during hardware initialsation / measurement start - After hardware detection, synchronisation and reset, filter settings are adapted if the PlugIn option "aliasing free measurement" is activated. - Fixed issue of some devices with software filter value after hardware reset. - Limit selectable values for parameters sample rate, hardware filter, software filter type and frequency if option 'aliasing free measurement' is active. - Fixed issue that occurred in some situations when closing IPEmotion if the X update has been called previously. - Avoid unspecific error if trying to set unavailable sensor supply after attaching TEDS sensor - Removed button and method (being callable via automation interface) for setting the IP address range of X-Devices form the X-System node to avoid accidental harming device settings. Known restrictions: - SIM-STG: Bridge type is not editable in the channel grid. V02.03.02 - Parallel initialisation of CAN devices which is more than two times faster (with more than ten devices) - Fixed problem with CANdb export after manual configuration - Fixed issue with CANdb / a2l export while measurement is running - Fixed problem with detection of physical range of CANpressure channels - Fixed issue if sensor supply of M-SENS8... Mx-SENS8 or Mx-SENS2-4 has been changed to 0V - X devices: Remove signals if a hardware reset has been done - X devices: NoValues are displayed if a X device is powered off and on again during a running measurement V02.03.01 - Fixed filter settings of devices M-SENS2, M-SENS2 250Hz and ES313.1, if aliasing free measurement is configured in the PlugIn options - Fixed automatic setting of sensor supply for some TEDS sensors - Fixed problem with offset adjustment V02.03.00 - Added support for SIM-STG - Added support for CANpressure - Display CAN bus load Known restrictions: - CAN devices are initialised sequentially on all CAN interface types. This is done for stability reason but also increases initialisation time significantly. - There are some known limitations, if copying systems and devices between the PlugIn IPETRONIK X and PlugIn IPETRONIK CAN. Following operations are working as expected - Select a single system node in one plugin and paste it on a single empty system in the other. All supported devices are created as expected. - Select a single or multiple devices of the same type and paste them on multiple selected devices (identical count) of the same type in the other plugIn. All devices are configured. - Following is known not to work resp. might lead to unexpected results: Select multiple devices of different types and paste them on a list of selected devices. Even if the device count per type in the target plugin is identical to the sources, the result depends on the internal device order in the source and target plugin. Thus some device configuration might be pasted on the wrong device type and thus these are not properly configured. 02.02.01 - Addes support for ES313.1, ES321.1 and ES341.1 FixedBug: Missing TEDS license information in ES313.1 FixedBug: Problem with deleting systems / devices and afterwards undoing the changes FixedBug: Problem with communication after deleting devices from a CAN only system and afterwards doing dry configuration Known restrictions: - Adding devices to a system, that has been restored by the undo function (ctrl-z) or has been created as default system does not work. - If defining systems with 'Use as default' the system and devices can no more be deleted. As workaround, the corresponding templates have to be resetted in the menu 'File -> Administration -> Reset templates' 02.02.00 - Allow setting of alternative IPv4 Address range for X-devices (one range per system) FixedBug: M-SENS2 wrong checksum calculation FixedBug: M-CNT2: Selection of inverted threshold set gate time to maximum and disabled the edit field. FixedBug: M-CNT2: Gate time sets automatic to 42s and is not editable, but frequency timeout mode is not activated FixedBug: Problem with device initialization FixedBug: Sx-STG: wrong source channel FixedBug: Sx-STG with TEDS: In some cases no values are shown after starting the measurement Known restrictions: - If changing the sensor Min/Max of the Sx-STG in the channel grid such that the sensor mode is automatically changed as well (e.g. mode 'Stain gage' to 'Voltage including sensor excitation'), the automatically adapted physical Min/Max is not initialised in the device although it is being displayed in IPEmotion. Workaround: Either do the changes only in the configuration tab page 'Scaling' or first change the sensor mode and afterwards adapt the sensor range. - If defining systems with 'Use as default' the system and devices can no more be deleted. As workaround, the corresponding templates have to be resetted in the menu 'File -> Administration -> Reset templates' - Channel LEDs do not work after loading a saved configuration - A2L export for X system needs connected devices - Only one ETHERNET system can be created manually 02.01.00 - Added support for Mx-SENS2-4 - Display license information for Mx-SENS2-4 - Display license information for M-SENS2 and M-SENS2 250Hz (both with and without DSP) Known restrictions: - If defining systems with 'Use as default' the system and devices can no more be deleted. As workaround, the corresponding templates have to be resetted in the menu 'File -> Administration -> Reset templates' 02.00.02 - Updated IPETRONIK PTP Driver to version V01.05.01 being signed with an alternative certificate such that no user interaction is required if the certificate is installed on the target computer. FixedBug: Silent installation might fail since the IPETRONIK PTP Driver installation requires user interaction on some systems (Windows 7 64bit) if it is not already present on the target computer. 02.00.01 FixedBug: Offset adjust didn't works correct the first time after changing the target value FixedBug: Measurement with new configuration sometimes didn't work correct when initializing first time FixedBug: Changing of the front number manually didn't work FixedBug: Issue with hardware detection (improved stability) Known restrictions: - Flexray-Extender isn't supported with this version - Mx-SENS is reported as Mx-SENS2 8 - M-THERMO, M-THERMO-16, µ-THERMO, M-THERMO-T and M-THERMO-16T aren't identified sporadically. This issue has to be solved in the corresponding FW. Workaround: Switch power of the devices off and on V02.00.00 - Added support for the following IPETRONIK CAN-Devices via CAN or X-Devices: * M-SENS2 * M-SENS2 DSP * M-SENS2 250Hz * M-SENS2 250Hz DSP * M-SENS * M-SENS DSP * M-SENS 8 * M-SENS 8 DSP * M-SENS 8plus * M-SENS 8plus DSP * M-THERMO2 * M-THERMO2 HV * M-THERMO2 u * M-RTD2 * M-UNI2 * Mc-THERMO * M-THERMO * M-THERMO 16 * M-THERMO T * M-THERMO 16T * µ-THERMO * M-CNT2 * M-FRQ For CAN-Devices a FW-Version higher than V04.xx and for X-Devices a FW-Version higher than V02.xx is necessary. - Added support for Offset adjust of the following IPETRONIK CAN-Devices via the IPEmotion Offset- Dialogue with setting of target value and returning result and offset value is supported: * M-SENS2 * M-SENS2 DSP * M-SENS2 250Hz * M-SENS2 250Hz DSP * M-SENS * M-SENS DSP * M-SENS 8 * M-SENS 8 DSP * M-SENS 8plus * M-SENS 8plus DSP - Added support for Mx-SENS2 8 FixedBug: Mx-SENS2 8 is reported as Mx-SENS Known restrictions: - Flexray-Extender isn't supported with this version - Mx-SENS is reported as Mx-SENS2 8 V01.04.03 FixedBug: Initialization of the enhanced synchronization driver also works with UAC activated. FixedBug: 64 bit signal types support added. (case 20671) FixedBug: The remote kernel support has been improved Known restrictions: - The data format of Flexray signals imported from fibex files may not be correctly interpreted. V01.04.02 Added support for the IPEmotion remote kernel. FixedBug: The DAQ list rate defined during an XCP import is used to set the initial signal sample rate. (case 13912) FixedBug: The X device update tool is now compatible with all IPEmotion versions. (case 15764) FixedBug: The import of XCP ECUs on the FlexRay-Extender is limited during import to 1 ECU. (case 15731) FixedBug: The XCP optional commands are taken into account for the FlexRay-Extender FixedBug: The default NoValue setting for protocol signals is +Fullscale V01.04.00 19.04.2013 - A new very precise time synchronisation algorithm makes measurements with mixed X and CAN systems very reliable. This is only supported for Windows Vista upwards. We have found that some firewall programs prevent the driver from working correctly. Make sure to check the driver was initialized correctly in the message window. - Full support for the IPEmotion offset adjust and shuntcheck dialogs. - A new secure device update tool is now integrated in the plugin. Please note that this tool only works with recent firmware versions. ( Mx-SENS V01.02.02, Sx-STG V01.01.03, Flexray-Extender V01.02.04) - Channel LED support added. - Configuration and measurement of the CAN channel output of the Sx-STG and Mx-SENS modules added. - Full Flexray-Extender support added. Cases solved: 9128 V01.03.00 21.06.2012 - Sx-STG TEDS sensor support implemented. - Improved time synchronization for long running measurements Cases solved: 8453, 6665 V01.02.00 06.02.2012 - The offset adjust can now be executed for the whole X-System - Changing a device by using the "Change into" function only supports identical sensor ranges. In other cases the physical range must be manually adapted. - Sx-STG ICP mode support - A2L file export enables using the IPETRONIK devices with other XCP compatible measurement software (CANape and INCA). The A2L file export produces one A2L file for each device as most software don't support importing more than one module from an A2L description file. Exporting the complete X System node will produce a Zip containing all the device descriptions. V01.01.00 05.08.2011 - Only 4 different sample rates can be selected per device. Only 1 sample rate per device is allowed for Sx-STG devices running in "Sample mode" High. - Offset adjusts can be triggered directly through the Mx plugin. - Changing any parameters modifying the measurement line resets the offset adjust value to 0. Modifying the measurement range also resets the offset adjust target to 0. - Exact measurement data synchronicity with other IPEmotion plugins is not guaranteed. Cases solved: 5187, 5381 V01.00.00 Initial release Known restrictions: - When selecting a new sendrate for a channel and 4 different channel sendrate are already configured on the device, other channel samplerates will may be adapted without any warning. - The warning "Device was not connected" is sometimes duplicated.