Pi Innovo's PiSnoop tool has many functions that are useful in typical OpenECU developments. It offers a cost-effective alternative to traditional calibration tools, but its emphasis is more on software development than calibration. Therefore it presents an interface that is part way to a debugger in terms of watch and memory windows, but typically interacts with the ECU via CCP, just like a calibration tool.
A demo version of PiSnoop is available from our website) in which all features may be tried out, but with some limitations on the number or duration of operations. This provides a route to getting up and running right away with OpenECU.
PiSnoop is under continual development, so this manual does not attempt to document how to use it with OpenECU in detail as is done for the other tools below. Instead, see the online help that is included in the PiSnoop installation (including the specific OpenECU application note) for up-to-date guidance. In brief however, capabilities include:
Works with any Vector, Kvaser or PEAK-System (PCAN) CAN interface on Windows XP or higher.
Loads symbols (parameter names, addresses, types and descriptions) from ASAP2 (.a2l) files...
... but can also load symbols from the linker output (.elf) files, giving access to all static
C language objects present including arrays, structure elements, pointers and bitfields, without
needing data dictionary entries. In Simulink builds, this means Real-Time Workshop structures
such as rtDWork and rtB can be explored, making "hidden"
block-related values, present in the autocode, available for debug purposes.
ECU memory access and flash reprogramming via CCP, with seed-key security support and fast DAQ data-logging, which tolerates ECU power cycling.
Reloading symbols and/or reprogramming the ECU after rebuilding is a single-click operation.
Calibration parameter value changes can be uploaded by name to a file, to use for download or flash reprogramming with a different build later.
Watch, map lookup and raw memory windows to view and edit ECU memory or offline file images.
CAN traffic generation and monitoring/logging with .dbc file support for named messages and signals.
ISO 15765-2 (UDS/Keyword Protocol/J1979) and J1939 diagnostic messaging windows.
UDS/Keyword Protocol can be used as an alternative memory access and flash reprogramming protocol, with seed-key security support.
ASAP3 support is provided to enable test automation.
Extensible through plug-in architecture supporting new protocols, hardware interfaces and custom windows.