WinOLS Integration

Allows real time tracing and recording of map positions on any supported ECU.

• UCM100 interface from EVC or OLS1018 plugin
• WinOLS 5.29 or newer
• VehiCAL Logger 3.1 or newer
• Advanced protocol recommended

1. In the Logger options enable WinOLS Integration.
   If you want to have tracing with basic protocol, also enable Send all selected measurements to WinOLS
   
2. In WinOLS configuration, go to Hardware → Visualizer:
   
   • If you are using UCM100, perform the Test+Activation. This will have to be done on every WinOLS start.
   • Select “Third-party-program” in the options.
   • Close the configuration.
3. Open a project and start the Visualizer:
   
4. Connect the visualizer:
   
   • At this point you should get a message in the Logger that WinOLS has connected and WinOLS should also display an active connection.
   • Connect the Logger to ECU and start streaming or logging.
   • If you are using advanced protocol and the axis IDs are assigned in maps, simply switch between maps and WinOLS will request the relevant variables from the logger automatically, and show you the current position in the map.
   • If you do not have axis IDs assigned or you are using basic protocol, you will need to manually select the axis from the list for each map.
     

Enables the WinOLS integration server, and sets a limit for the maximum variables that WinOLS can request outside of the measurement list.
Every time a new map is opened, WinOLS adds the variables it needs into the request list. The Logger checks if these variables are already in the request list.

• If they are, starts sending them to WinOLS.
• If they are not, adds them to a “hidden” list, which can have the maximum configured size (to not slow down the main logging too much), reconfigures the ECU datastream and then starts sending them to WinOLS.

Normally the logger only sends the variables that WinOLS requests. This option forces always sending all the variables in the list. Useful for basic protocols, because the ID's often do not match the actual axis ID's.

Because the WinOLS integration is based on an open pipe where the Logger acts as a server, it is possible to integrate third party tools through the same endpoint.
Please refer to EVC documentation.

Allows immediate writing of changes to the ECU as soon as a value is changed in a map or the hexdump.

• OLS1007 plugin. OLS300 owners automatically have this plugin.
• LIVE license and support in Logger

1. In WinOLS choose your hexdump/project and select Hardware > Simulator > Realtime-Export from the menu bar.
2. Select the output file and configure as the following image (Export on, Checksum off, Swap off):
   
3. Configure VehiCAL Logger to monitor the output file and connect to the ECU.

Allows analysing previously recorded Logger logfiles in WinOLS.

• UCM100 interface from EVC
• Newest WinUCM software

1. Record a datalog, make sure you are logging the axis of the map that interests you.
2. Open the WinUCM software and connect your UCM100 cable.
3. Convert your log file to WinOLS format
   
4. Open a map in WinOLS and make sure that the axis is assigned
   
5. Open the Visualizer (at least one map must be opened)
   
6. Click the open button in the visualizer and select your converted file
   
7. Scroll the log in the visualizer, and you should see the trace
   

If the trace does not show up, you either do not have the axis ID's logged or defined in your map. You can also assign axis ID's manually in the visualizer by clicking the > buttons.