Release Notes ____________________________________________________________________________________________________________ Bitte beachten Sie, dass die Release Notes nur in englischer Sprache verfuegbar 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 LOG Last entry: 04.02.2021 Current version: 03.65.03 ____________________________________________________________________________________________________________ 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 2018 R2 Recommended system requirements: * Screen resolution: min. 1920 x 1200 pixel * Processor: min. 3 GHz Multi-Core * RAM: min. 6144 MB * Storage medium type: SSD * min. IPEmotion 2018 R2.2 Supported platforms: * Microsoft Windows 10 (32 Bit and 64 Bit operating systems) * Microsoft Windows 8.1 (32 Bit and 64 Bit operating systems) * Microsoft Windows 8 (32 Bit and 64 Bit operating systems) * Microsoft Windows 7 (32 Bit and 64 Bit operating systems) The following software will be installed: * Microsoft Visual C++ 2013 Redistributable ____________________________________________________________________________________________________________ Rights IPEmotion PlugIn IPETRONIK LOG needs administrator rights during installation. Standard user rights are needed for working with IPEmotion PlugIn IPETRONIK LOG. ____________________________________________________________________________________________________________ ATTENTION: Make sure that you always use the PlugIn IPETRONIK LOG with the corresponding version of TESTdrive. Content The following points describe the extensions, changes and exception handlings in the corresponding versions: V03.65.03 FixedBug: Change FLEETlog to M-LOG V3 (case 57094) Known restrictions: Logger PlugIn and X-PlugIn activated in parallel might cause problems V03.65.02 FixedBug: Bit mask optimization with motorola format (case 55209) Known restrictions: Logger PlugIn and X-PlugIn activated in parallel might cause problems V03.65.01 New TESTdrive version FlexRay signals with motorola backward CAN messages with slow sample rates New version of converter tool V03.65.00 64-Bit-Version (without FlexRay-Extender support) Sample Point configuration for CAN and CAN FD Zip split behaviour improved FTP-Upload/Download per FTP GPS course channel WiFi frequency band configuration COMgate/COMgateV3 as separate devices Option for UTF8 encoding in SFTP file names Logger converter tool in logger function menu Known restrictions: Logger PlugIn and X-PlugIn activated in parallel might cause problems V03.64.00 IPElog2 ( 16 CAN-FD, 2 ETH, WAN ) XCPonCAN FD FlexRay signal measurement Known restrictions: Logger PlugIn and X-PlugIn activated in parallel might cause problems V03.63.00 Always online E-Mail box Delete COMgate files after COMgate update FixedBug: A2L export correction (case 39775) FixedBug: Checkbox sizes (case 38000) Known restrictions: Logger PlugIn and X-PlugIn activated in parallel might cause problems V03.62.00 FlexRay Satellites Configure FlexRay Extender initialization Prefix preview for storage groups and classifications Minimum satellite number for GPS FixedBug: Stop trigger correction (case 39777) Known restrictions: Logger PlugIn and X-PlugIn activated in parallel might cause problems V03.61.00 CAN FD Satellites FixedBug: 2 kHz for DAQ lists removed (case 40628) Known restrictions: Logger PlugIn and X-PlugIn activated in parallel might cause problems V03.60.00 openABK buttons openABK DHCP server openABK unique names Known restrictions: Logger PlugIn and X-PlugIn activated in parallel might cause problems V03.59.00 IPElog2 access point functionality IPEwifi3 Transfer categories for FTP server Transfer categories for LOG files XCP wait for DISCONNECT of second tester Optionally use CCP parameters from ECU UDS security access SFTP resume Parallel journal check for SFTP Transmit messages in traffic groups IPElog2 gyro sensor Default values for data transfer parameters adapted Project propertis are no longer stored in mea_conf FixedBug: Rename trigger status at CAN node name change (case 34635) FixedBug: Correction in formula export (case 35571) Known restrictions: Logger PlugIn and X-PlugIn activated in parallel might cause problems V03.58.01 New TESTdrive version V03.58.00 New operations IS_NOVALUE, ANGLE, RADIUS WWH-OBD XCPonTCP Optional CCP command 'START_STOP_ALL' Remote01 and Remote02 for M-LOG V3 and IPElog2 Option for writing channel comments to IPETRONIK CAN devices Software filter frequency list for IPETRONIK CAN channels External storage for video data Insert >= 0.5 comparison for boolean operands in operations Digits after decimal point for web view New OBD-II PIDs CISCO VPN is not supported any more Support file improvement FixedBug: The default column separator of the CSV export has been changed to the separator character being defined in the system controls. To keep backward compatiblity, the hidden option 'separatorCharacterColumn' can be set to ';'. FixedBug: M-VIEWgraph problem with active limits (case 28941) V03.57.03 FixedBug: ODT signal splitting is switched off by default V03.57.02 FixedBug: M-LOG V3 6-2-2 type detection corrected FixedBug: WakeOnCAN timeout for M-LOG V3 was not configurable (case 31728) FixedBug: WakeOnCAN and NML for CAN-1 of IPElog2 V03.57.01 New TESTdrive version V03.57.00 Reset behaviour for formulas (configuration change, acquisition start) Protocol support on USBtoETH adapter Category overview Quickstart mode XCP odt and bit mask optimization CCP bit mask optimization IPElog2 Fixed pool buffer for XCPonFlexRay Additional delays for paralell post processing FixedBug: Missing slow storage rates added (case 29150) FixedBug: Switch off condition for FLEETlog without WakeOnCAN FixedBug: Missing license infos in info dialog (case 28879) FixedBug: Handling for logger without configuration adapted FixedBug: LOG2PC corrections FixedBug: GM LAN default parameters adapted (case 25988) FixedBug: M-LOG naming made consistent V03.56.03 New TESTdrive version V03.56.02 New TESTdrive version V03.56.01 FixedBug: GPS of FLEETlog2 (3 CAN - 1 SW-CAN) did not work V03.56.00 IPEconnect openABK displays More than one CAN send on a connector Event controlled signals for J1939 Quickstart for LIN No value configuration for MEAN operation Arguments for header line of diagnostic files V03.55.01 FixedBug: COM documentation was missing FixedBug: Correction for changing logger types Known restrictions: V03.55.00 No value groups Support for up to 4 usb cameras EPK missmatch behaviour for XCP EPK missmatch behaviour for CCP New status channel for start reason Separate mail addresses for mail groups ECU check for UDS Send category 'Off' Resetting configuration generates configuration with cpu load channel Option to include the serial number in the mcf file name by default (requires IPEmotion >= 2015 R1) User defined diagnostic operations Optional column for SFTP port configuration Automatic quickstart administration Support for FlexRay extender on USBtoETH adapter Optional GPS longitude and latitude channel in rad Use name as prefix for video, audio and classing New Control for CAN IDs Second tester timeout for XCP Second tester timeout for CCP Info mail configuration A2L check for XCP Classifications reworked Status information for changing data transfer configuration properties in the extended properties Power out for M-VIEWfleet display can be defined in the options Preview for storage group prefix Key value pair extensions FixedBug: Correction for CAN resource check FixedBug: Tooltip for overflow bit of IPETRONIK-CAN signals improved (case 17639) FixedBug: Format for diagnostic traces was not syncronized over all diagnostics on the same connector (case 22897) FixedBug: Consider 'Use no value as default value' for default values Known restrictions: Configurations created with older IPEmotion versions can contain VTAB ranges for imported CANdb signals V03.54.02 FixedBug: Device names at IPETRONIK CAN csv import were changed (case 24278) Known restrictions: Configurations created with older IPEmotion versions can contain VTAB ranges for imported CANdb signals V03.54.01 Support for higher resolution for USB video FixedBug: Detection of IPETRONIK CAN devices: Sort devicesby serial numbers FixedBug: csv import for IPETRONIK CAN did not work FixedBug: Job trigger for service sequences are no longer available as they are not allowed FixedBug: Status information for not imported IPETRONIK-CAN signals from csv (case 18052) FixedBug: M-VIEWgraph page switching by DIN FixedBug: Correction for digits for M-VIEWgraph displaying (case 20706) FixedBug: Possibilty to use project property names instead of keys (case 21372) FixedBug: Quickstart flag for ring buffer traffic groups removed as it is not supported (case 21072) V03.54.00 Support for new IPETRONIK CAN devices M-LOG 6 / M-LOG 3-1 Data transfer categories Rescue configuration WakeOnSMS for IPElog Statistic group UTC flag in DAT header Trigger for XCP polling daq lists Use FLEET configuration from IPEmotion as default for FTP Support for reset function Possibilty to deactivate transfer of TSTdrive.zip Overwrite output for diagnostic jobs UDS extensions Time for repeating request configurable XCP polling rate adaption depending on the signal count Multiple polling lists for XCP Distributed bus allocation for XCP polling lists Slow sample rates for XCP polling lists SPN conversion methode for J1939 New FTP features Two step packaging Multi archive mode Protocol status signal for CAN extender Display ranges and number of decimal digits for GPS signals Additional CAN send columns ECU init tries Additional path for user operations Blacklist for providers FixedBug: USB connector for FLEETlog FixedBug: Check max class count of classification (case 19559) FixedBug: Change component corrected FixedBug: OBD signal scaling corrected FixedBug: Config check for ambiguous channel names in formulas (case 18684) FixedBug: No mask and shift for float signals (case 19482) FixedBug: CAN timeout configurable (case 16055) FixedBug: Traffic id trigger message corrected FixedBug: Custom data folder changed (case 18338) FixedBug: Trace mode and trace format only for diagnostics V03.53.03 FLEETlog2 (3 CAN - 1 SW-CAN) Known restrictions: Start bit calculation for UDS acquisition minimal band width for LAN connections Job trigger for service sequences are no longer available as they are not allowed Detection of IPETRONIK CAN devices: Sort devicesby serial numbers csv import for IPETRONIK CAN did not work Correction for KWPonCAN diagnotics and signal acquisition with same ECU Change component corrected Config check for ambiguous channel names in formulas USB connector for FLEETlog OBD trace mode binary removed Correct pooling rate at loading old configurations if rate is too high Check max class count of classification OBD signal scaling corrected Use timeout for connectors is set automatically when using protocols Memory address size for GM-LAN configureable via gui No mask and shift for float signals Restriction for maximal trigger duration Ping for SMTP client CAN timeout configurable Traffic id trigger message corrected Custom data folder changed Trace mode and trace format only for diagnostics V03.53.02 FixedBug: minimal band width for LAN connections (case 19044) Known restrictions: Start bit calculation for UDS acquisition Detection of IPETRONIK CAN devices: Sort devicesby serial numbers OBD trace mode binary removed Correction for KWPonCAN diagnotics and signal acquisition with same ECU USB connector for FLEETlog Correct pooling rate at loading old configurations if rate is too high Change component corrected Check max class count of classification OBD signal scaling corrected Config check for ambiguous channel names in formulas Memory address size for GM-LAN configureable via gui Use timeout for connectors is set automatically when using protocols No mask and shift for float signals Restriction for maximal trigger duration Ping for SMTP client CAN timeout configurable Custom data folder changed Traffic id trigger message corrected Trace mode and trace format only for diagnostics V03.53.01 FixedBug: minimal band width for LAN connections (case 19044) FixedBug: Start bit calculation for UDS acquisition (case 18693) Known restrictions: Correction for KWPonCAN diagnotics and signal acquisition with same ECU Correct pooling rate at loading old configurations if rate is too high OBD trace mode binary removed Use timeout for connectors is set automatically when using protocols Memory address size for GM-LAN configureable via gui Restriction for maximal trigger duration Ping for SMTP client V03.53.00 new LOG2PC Known restrictions: Correct pooling rate at loading old configurations if rate is too high OBD trace mode binary removed Correction for KWPonCAN diagnotics and signal acquisition with same ECU Memory address size for GM-LAN configureable via gui Use timeout for connectors is set automatically when using protocols Ping for SMTP client Restriction for maximal trigger duration S-LOG will be not detected with correct type number V03.52.02 CSV import/ -export for IPETRONIK-CAN CANdb export with ID based message names for IPETRONIK-CAN Possibility to switch off transmission of video extender data to FTP Up to 20 pages for M-VIEWgraph V03.52.01 Correct name adaption at CANdb export PCI2CAN2SWQS/PCI2CAN2SWQSDMA TESTdriveCMD.xml for external storage Correction in match port configuration Only create match port connection if at least one wlan exists V03.52.00 J1939 support FLEETlog2 Extended CAN send configuration Ring buffer traffic groups Softwarefilter for traffic groups Triggercondition for OBD-II Option for automatic CAN ID administration at detection Optional export dialog Operation INT_ADD License infos from license file CAN status channels without CAN workstation WakeUpOnRTC for IPElog Single PID requests for OBD-II Support of hardware syncronisation Status channel for OBD-II processing External storage flags for storage groups OBD request delay StartStop-Event Status signal for supply voltage Status signal for CAPS voltage Status channel for USB video file size Status channel for measurement file number New icons FixedBug: Correct pooling rate at loading old configurations if rate is too high (case 17252) FixedBug: OBD trace mode binary removed FixedBug: Correction for KWPonCAN diagnotics and signal acquisition with same ECU FixedBug: Memory address size for GM-LAN configureable via gui (case 16860) FixedBug: Use timeout for connectors is set automatically when using protocols FixedBug: Ping for SMTP client FixedBug: Restriction for maximal trigger duration Known restrictions: - J1939-SPN-conversion method can actually not be configured, so that only SPN version with value 4 is possible - Configuration of calibration settings for IPETRONIK CAN modules is currently not supported - For error free use of LOG2PC (detection, initialization, XCP-service) under Windows VISTA/7 LOG2PC has to be added as an exception to the firewall: - Online measurement : XCP-Service uses Port 11000 - Module detection : LOG2PC uses port 10000 & 10001 - File transfer : FTP port 20 & 21 - LOG2PC may not work correctly if there is more than one network adapter active - The option 'Cyclical Data Saving' should not be used in CPU intensive configurations - data loss may occur V03.51.02 - new manual - extended comments option for extended signal comments in DAT header - M-VIEWvga error fixed - logger system check option V03.51.01 - set storage rate of storage groups to "From channel" for configuration from versions < 3.51 - set storage rate of stored channels to "Auto" when setting storage rate back to "From channel" - disable wake on can timeout in gui when timeout not used V03.51.00 - restart acquisition after clock setting - show limit configuration in display grids - SC1200 no longer supported - time zone configuration in the logger configuration - protocol - medium selection - additional grid columns - status signal for GPS processing - support for VTABs in CANdb export - information messages if namens have to be adapted at CANdb export - support for signal events - isf files can be protected by zip protection - formula pool usage with the formula editor dialog - NML (no message lost) for IPElog - network card selection in extended options - support for fixed storage rate in storage groups and support of automatic storage rates at sample rates changes - complete support for 64 bit integers - FTP transfer in active and passive mode - new status signal for internal IPElog temperature - traffic groups - internal comment extensions removed - number of traffic id triggers incremented to 6 - minimal band width for modem and wlan - quick start configuration moved to traffic groups - FTP transfer splitted into up and download - mask for CAN messages (J1939) - support for event based storage of CANdb signals - wake on CAN per CAN connector for IPElog - support for cancel button - CAN status signals without CAN workstation - up to 16 CCP/XCP ECUs on one CAN connector - SNTP server name - storage group namens and traffic groups namens can be used as prefix - additional columns in formula parser dialog V03.50.03 * correction for CAN send id administration * correction in XCP service A2L export * use writeable path for extener configuration export * correction for no value of UINT32 signals V03.50.02 * channel references as key/value pairs in DAT header * open boundary classes for classifications * include IPETRONIK-CAN V01.08.01 * auto negation for ethernet of IPElog * channel grid columns for no value settings * complete cross reference for all logger types * video extender 4 as optional component * redundant node at FlexRay extender removed * bug fixes for TESTdrive export * zip slit size correction V03.50.01 * support for M-SENS2 and M-CNT2 * ecu type for XCPonCAN * reference key value pair in DAT header * open boundary classes for classification * auto negation for ETHERNET of IPElog * GPS comments for existing configurations corrected * dbc export of inactive signals removed * dbc export creates a multiplexor signal in the dbc if this is not contained in the message and multiplexed signals are included * correction for signals on M-VIEWgraph after de-/activation * limit violation page of M-VIEWvga is created when loading existing configurations * video extender 4 removed * correction for CAN send multiple selection * correction for channel cross reference of logger formulas * channel grid columns for no value control Known restrictions * Overuse of DAQ-lists between M-LOG and M-LOG Extender is currently not reported to the user * Configuration of calibration settings for IPETRONIK CAN modules is currently not supported * For error free use of LOG2PC (detection, initialization, XCP-service) under Windows VISTA/7 LOG2PC has to be added as an exception to the firewall: * Online measurement : XCP-Service uses Port 11000 * Module detection : LOG2PC uses port 10000 & 10001 * File transfer : FTP port 20 & 21 * LOG2PC may not work correctly if there is more than one network adapter active * LOG2PC with Windows Vista / Windows 7: UAC (User Account Control) has to be set to lowest level or IPEmotion hast to be started with admin privileges * The option 'Cyclical Data Saving' should not be used in CPU intensive configurations - data loss may occur * Support for sampling rates above 1 kHz has been removed V03.50.00 * support for IPElog * local project settings for each logger * configurable delays for remote on and remote off * different init modes for IPETRONIK CAN devices * additional traffic trigger possibilities * mail groups for sending measured values by E-Mail * csv import for storage groups * option for adapting the ECU init timeout * possibility to adapt the order of calculations to the calculation order * preview for M-VIEWgraph display page layout * optional row count for numerical displays of M-VIEWgraph * possibility to increase the emergeny switch-off time by enabling the always ignore remote property * optimized calculations * ODT configuration of XCP service moved to extended properties * additional OBD signals * optional blowfish encryption for TESTdrive data * additional sampling rates for audio acquisition * optional channel grid column for connected storage groups * optional channel grid column for Min-Max-list enabling * adaptable rates for XCP service daq lists * support of VTAB * CAN send message namens and message IDs per signal Known restrictions * Overuse of DAQ-lists between M-LOG and M-LOG Extender is currently not reported to the user * Configuration of calibration settings for IPETRONIK CAN modules is currently not supported * For error free use of LOG2PC (detection, initialization, XCP-service) under Windows VISTA/7 LOG2PC has to be added as an exception to the firewall: * Online measurement : XCP-Service uses Port 11000 * Module detection : LOG2PC uses port 10000 & 10001 * File transfer : FTP port 20 & 21 * LOG2PC may not work correctly if there is more than one network adapter active * LOG2PC with Windows Vista / Windows 7: UAC (User Account Control) has to be set to lowest level or IPEmotion hast to be started with admin privileges * The option 'Cyclical Data Saving' should not be used in CPU intensive configurations - data loss may occur * Support for sampling rates above 1 kHz has been removed V03.23.06 * M-THERMO 2 and M-RTD Known restrictions * start bit of FlexRay signal groups imported with IPEmotion < V01.09.00 might be wrong * Overuse of DAQ-lists between M-LOG and M-LOG Extender is currently not reported to the user * Configuration of calibration settings for IPETRONIK CAN modules is currently not supported * To use the Logger with XCP service it is necessary to set both IP addresses (PC and Logger) either both to DHCP or both to static in the same network area * For error free use of LOG2PC (detection, initialization, XCP-service) under Windows VISTA/7 LOG2PC has to be added as an exception to the firewall: * Online measurement : XCP-Service uses Port 11000 * Module detection : LOG2PC uses port 10000 & 10001 * File transfer : FTP port 20 & 21 * LOG2PC may not work correctly if there is more than one network adapter active * LOG2PC with Windows Vista / Windows 7: UAC (User Account Control) has to be set to lowest level or IPEmotion hast to be started with admin privileges * Channel names inside storage groups, XCP-Service and CAN-Send have to be unique * The option 'Cyclical Data Saving' should not be used in CPU intensive configurations - data loss may occur * Support for sampling rates above 1 kHz has been removed V03.23.04 * corrections for FlexRay signal acquisition * correction for shut down event Known restrictions * start bit of FlexRay signal groups imported with IPEmotion < V01.09.00 might be wrong * Overuse of DAQ-lists between M-LOG and M-LOG Extender is currently not reported to the user * Configuration of calibration settings for IPETRONIK CAN modules is currently not supported * To use the Logger with XCP service it is necessary to set both IP addresses (PC and Logger) either both to DHCP or both to static in the same network area * For error free use of LOG2PC (detection, initialization, XCP-service) under Windows VISTA/7 LOG2PC has to be added as an exception to the firewall: * Online measurement : XCP-Service uses Port 11000 * Module detection : LOG2PC uses port 10000 & 10001 * File transfer : FTP port 20 & 21 * LOG2PC may not work correctly if there is more than one network adapter active * LOG2PC with Windows Vista / Windows 7: UAC (User Account Control) has to be set to lowest level or IPEmotion hast to be started with admin privileges * Channel names inside storage groups, XCP-Service and CAN-Send have to be unique * The option 'Cyclical Data Saving' should not be used in CPU intensive configurations - data loss may occur * Support for sampling rates above 1 kHz has been removed V03.23.03 * support for italian, japanese, korean and chinese language Known restrictions * start bit of FlexRay signal groups imported with IPEmotion < V01.09.00 might be wrong * Overuse of DAQ-lists between M-LOG and M-LOG Extender is currently not reported to the user * Configuration of calibration settings for IPETRONIK CAN modules is currently not supported * To use the Logger with XCP service it is necessary to set both IP addresses (PC and Logger) either both to DHCP or both to static in the same network area * For error free use of LOG2PC (detection, initialization, XCP-service) under Windows VISTA/7 LOG2PC has to be added as an exception to the firewall: * Online measurement : XCP-Service uses Port 11000 * Module detection : LOG2PC uses port 10000 & 10001 * File transfer : FTP port 20 & 21 * LOG2PC may not work correctly if there is more than one network adapter active * LOG2PC with Windows Vista / Windows 7: UAC (User Account Control) has to be set to lowest level or IPEmotion hast to be started with admin privileges * Channel names inside storage groups, XCP-Service and CAN-Send have to be unique * The option 'Cyclical Data Saving' should not be used in CPU intensive configurations - data loss may occur * Support for sampling rates above 1 kHz has been removed V03.23.01 * support for GM-LAN configuration * CANdb signals support CAN-Identifier column * Video-Extender support * new OBD-II signals * use timeout property for ETHERNET connectors * problem with update button for Win 7 - 64-Bit fixed Known restrictions * start bit of FlexRay signal groups imported with IPEmotion < V01.09.00 might be wrong * Overuse of DAQ-lists between M-LOG and M-LOG Extender is currently not reported to the user * Configuration of calibration settings for IPETRONIK CAN modules is currently not supported * To use the Logger with XCP service it is necessary to set both IP addresses (PC and Logger) either both to DHCP or both to static in the same network area * For error free use of LOG2PC (detection, initialization, XCP-service) under Windows VISTA/7 LOG2PC has to be added as an exception to the firewall: * Online measurement : XCP-Service uses Port 11000 * Module detection : LOG2PC uses port 10000 & 10001 * File transfer : FTP port 20 & 21 * LOG2PC may not work correctly if there is more than one network adapter active * LOG2PC with Windows Vista / Windows 7: UAC (User Account Control) has to be set to lowest level or IPEmotion hast to be started with admin privileges * Channel names inside storage groups, XCP-Service and CAN-Send have to be unique * The option 'Cyclical Data Saving' should not be used in CPU intensive configurations - data loss may occur * Support for sampling rates above 1 kHz has been removed V03.23.00 Content The following points describe the extensions, changes and exception handlings in the corresponding versions: * the version number of the CCP protocol is now read from the A2L file and set as protocol property * xml for iPhone is added to mcf * FLEETlog PSA * FLEETlog WAN: LOG2PC and XCP service via WLAN * quickstart configureable per CAN connector * different refresh rates for the different display types * support for IPEmotion output window (hypertermmial functionality) * trigger of type 'stop is inverted start' for ring buffer storage group * quickstart for FLEETlog * support for duplicate channel names * new status signal 'limit violation' * trace mode 'binary' of diagnostics removed * port check of LOG2PC ports in windows firewall * support of xcp polling * option for no value start delay * object names in dialog titles * possibilty to allow other obejcts besides IPETRONIK-CAN on a CAN connector * support of TCPonIXXATFlexRAy * cyclic data saving for FLEETlog * two sample rates for OBD-II * acces point functionality * compression split size configureable * ping parameters configureable * automatic baud rate detection for OBD-II * CAN identifier mode for OBD-II * no configuration export with overloaded daq lists possible * warning at export, if OBD-II with automatic baud rate detection is used together with CANdb or protocol acquisition * name of storage groups time channel configureable * custom channels for OBD-II * possibility to add import files to mcf * traffic filter overview * availability of ccp status channel * preview pictures for trigger modes * Known restrictions * Overuse of DAQ-lists between M-LOG and M-LOG Extender is currently not reported to the user * Configuration of calibration settings for IPETRONIK CAN modules is currently not supported * To use the Logger with XCP service it is necessary to set both IP addresses (PC and Logger) either both to DHCP or both to static in the same network area * For error free use of LOG2PC (detection, initialization, XCP-service) under Windows VISTA/7 LOG2PC has to be added as an exception to the firewall: * Online measurement : XCP-Service uses Port 11000 * Module detection : LOG2PC uses port 10000 & 10001 * File transfer : FTP port 20 & 21 * LOG2PC may not work correctly if there is more than one network adapter active * LOG2PC with Windows Vista / Windows 7: UAC (User Account Control) has to be set to lowest level or IPEmotion hast to be started with admin privileges * Channel names inside storage groups, XCP-Service and CAN-Send have to be unique * The option 'Cyclical Data Saving' should not be used in CPU intensive configurations - data loss may occur * Support for sampling rates above 1 kHz has been removed V03.22.00 Known restrictions * Overuse of DAQ-lists between M-LOG and M-LOG Extender is currently not reported to the user * Configuration of calibration settings for IPETRONIK CAN modules is currently not supported * To use the Logger with XCP service it is necessary to set both IP addresses (PC and Logger) either both to DHCP or both to static in the same network area * For error free use of LOG2PC (detection, initialization, XCP-service) under Windows VISTA/7 LOG2PC has to be added as an exception to the firewall: * Online measurement : XCP-Service uses Port 11000 * Module detection : LOG2PC uses port 10000 & 10001 * File transfer : FTP port 20 & 21 * LOG2PC may not work correctly if there is more than one network adapter active * LOG2PC with Windows Vista / Windows 7: UAC (User Account Control) has to be set to lowest level or IPEmotion hast to be started with admin privileges * Channel names inside storage groups, XCP-Service and CAN-Send have to be unique * The option 'Cyclical Data Saving' should not be used in CPU intensive configurations - data loss may occur * Support for sampling rates above 1 kHz has been removed V03.21.00 Known restrictions * Overuse of DAQ-lists between M-LOG and M-LOG Extender is currently not reported to the user * Configuration of calibration settings for IPETRONIK CAN modules is currently not supported * To use the Logger with XCP service it is necessary to set both IP addresses (PC and Logger) either both to DHCP or both to static in the same network area * For error free use of LOG2PC (detection, initialization, XCP-service) under Windows VISTA/7 LOG2PC has to be added as an exception to the firewall: * Online measurement : XCP-Service uses Port 11000 * Module detection : LOG2PC uses port 10000 & 10001 * File transfer : FTP port 20 & 21 * LOG2PC might crash if you cut the connection of your PC to the network, after a restart of the LOG2PC service it will work again V03.20.00 Known restrictions * Overuse of DAQ-lists between M-LOG and M-LOG Extender is currently not reported to the user * Configuration of calibration settings for IPETRONIK CAN modules is currently not supported * To use the Logger with XCP service it is necessary to set both IP addresses (PC and Logger) either both to DHCP or both to static in the same network area * For error free use of LOG2PC (detection, initialization, XCP-service) under Windows VISTA/7 LOG2PC has to be added as an exception to the firewall * Due to a bug the "Change hardware in..." function should not be used on a logger if you have data transfer configured (bug does only occur if you use IPEmotion V01.03.00) If you must use the "Change hardware in..." function you have to check your data transfer settings before transfering your configuration to the logger * On "Change hardware in..." the property "First CAN ID" of a traffic recording can be lost * Due to a bug you should not use the "Change hardware in..." function in combination with a M-LOG with DIG I/O node * UserOperations (external Dll) do currently not support 64-Bit integer InitParameter * UserOperations (external Dll) with 32-Bit float InitParameter do currently not support entry of decimal numbers via the formula interpreter * Macrorecording of UDS diagnostics properties is not supported with IPEmotion version < V01.05.00 * LOG2PC might crash if you cut the connection of your PC to the network, after a restart of the LOG2PC service it will work again V03.19.00 Known restrictions * Although individual definition of sampling rate for calculations is supported, due to a bug all calculations should be configured with the same sampling rate * KWPonCAN and CCP measurement may not work for some ECU types if you use IPEmotion version <= V01.02.02 * CAN measurement with extended identifiers on M-LOG Extender does only work with TESTdrive >= V03.19.02 * LOG2PC operations (initalization, getting measurement data files, getting logfiles) do not work if you use a M-LOG Extender * For XCPonCAN/XCPonUDP support you will need IPEmotion version >= V01.03.00 * Calculations without channels (i.e. calculations that only use constants) are currently not supported * Operations ASin(), ACos() and Atan() are currently not supported in calculations * NOTB operator is currently not supported in calculations * Use of external Dll's for user-defined calculations are currently not supported * Configuration options for UDS-diagnostics are currently not supported (i.e. trace format) * Use of KWP diagnostics may result in an error while exporting the logger configuration for some ECU types * Overuse of DAQ-lists between M-LOG and M-LOG Extender is currently not reported to the user * Use of array measuring points with protocoll KWPonCAN may result in timeouts * Configuration of calibration settings for IPETRONIK CAN modules is currently not supported * SIM-DMS and SIM-DMS DSP configuration via M-LOG is not supported * For some calculations CAN-send and XCP-service is not working properly * To use the Logger with XCP service it is necessary to set both IP addresses (PC and Logger) either both to DHCP or both to static in the same network area * Detection of Loggers under Windows Vista does only work if user access control is deactivated or IPEmotion is run with administrator rights * For error free use of LOG2PC (detection, initialization, XCP-service) under Windows VISTA/7 LOG2PC has to be added as an exception to the firewall * Trigger conditions should be entered without word wraps V03.18.00 Known restrictions * To use the Logger with XCP service it is necessary to set both IP addresses (PC and Logger) either both to DHCP or both to static in the same network area V01.00.00 Known restrictions * No configuration support for M-VIEWgraph and M-VIEWfleet * No configuration support for Powermanagement * No configuration support for COMgate * No parallel use of LOG2PC service and LOG2PC applet possible