Precautions when using the built-in CAN analyzer
•On heavily loaded buses, the CAN analyzer may skip packages. If you need to capture every consecutive package on busy buses you should use an external CAN analyzer.
•The CAN analyzer only captures data when MTune is connected, so it may miss some data just after the ECU is powered up. If you need to capture data when other CAN units are powered up, the ECU should be powered up and MTune being connected before the rest of the system is turned on.
CAN Analyzer
CAN analyzer Enable
Specifies which data to be captured.
•Disabled.
•Enabled, incoming data only - ONLY captures data transmitted from OTHER devices, does NOT capture this MaxxECU messages.
•Enabled, OUTGOING data only - ONLY captures data transmitted from the MaxxECU.
•Enabled, incoming+outgoing data - Captures ALL data on the bus, including MaxxECU own messages.
Note: Disable the analyzer with you don't need it. It can slow down MTune.
Note: Sent data will not be shown when there are no other devices connected to the bus. It will only show successfully sent messages (and that requires another receiver on the bus).
CAN view
Here is an example view with the MaxxECU default CAN output and the Audi S3 1.8T 2003 (ME 7.5) CAN protocol enabled and the sorted by the CAN ID.
Note: Press any other column to sort it in any other way.
Export captured data
By using the Save data button, you are able to save the captured data in the SKV format, which later could be opened in MS Excel / OpenOffice Calc or similar for review.
MaxxECU "alive" CAN message
The 0x321 message is a "hello" message sent from MaxxECU, all the time, always.
