Skip to main content
Version: 4.00

CAN Monitoring Sequence

In the flow below, solid-line boxes indicate required processing, and dashed-line boxes indicate optional processing. ☆ means call multiple times based on number of MicroPeckerX units, and ★ means call multiple times based on total number of channels in use.

Sequence Table​

#APIProcessDescription
1MPXOpenRecognize MicroPeckerXConnect all target MicroPeckerX units to PC first, then call this API once.
2MPXCANSetParamSet communication parametersCall for each channel in use (parameters can be configured independently per channel).
3MPXSetGetLogModeSet log acquisition modeCall for each channel in use (mode can be set independently per channel).
Channels where this API is not called operate in log acquisition API mode.
4MPXMonitorStartStart monitoringCall for each MicroPeckerX unit in use.
For synchronized operation of multiple units, start monitoring on all slave-mode units first, then on the master-mode unit.
5MPXGetLog
or
MPXCANGetLogEx
Acquire log informationPeriodically call this API for each CH to acquire log information.
If log information is not acquired for an extended period, a buffer overrun occurs, but operation itself is not affected.
6MPXMonitorStopStop monitoringCall at stop timing for each MicroPeckerX unit in use.
When multiple units are running, stop the master-mode unit first, then stop slave-mode units sequentially.
7MPXCloseRelease MicroPeckerX recognitionCall once to release recognized units.
If you want to restart monitoring while still recognized, restart from step #2.