CANmonitor is focused primarily on accessand manipulation of CANopen devices objects dictionaries. It uses VCA based CANblaster daemon for physical CAN bus access. TCP connection (CPickle protocol) is used for communication between CANmonitor and CANblaster. This allows to use CANmonitor even from distant location far from industrial plant location. CANopen SDO access state machine is implemented in CANblaster which allows OD access from multiple CANmonitor, QCANalyzer and other tools and control tasks in parallel.

CANmonitor allows even basic listing of raw CAN messages and simple test messages sending.

The submodule holding CANmonitor sources is part of main OrtCAN sources GIT tree. The build is enabled by

CONFIG_OC_CANMONITOR=y

included in the top level config.omk file. Java language development environment and ANT tool are required for CANmonitor build.