Skip to main content

CAN Monitoring Sequence

In each flow below, solid-line boxes indicate required processing, and dashed-line boxes indicate optional processing. ☆ means the API is called multiple times according to the number of MicroPeckerX units used, and ★ means the API is called multiple times according to the total number of MicroPeckerX CHs used.

Sequence Table​

#APIProcessDescription
1MPXOpenRecognize MicroPeckerX unitsConnect all target MicroPeckerX units to the PC first, then call this API once.
2MPXCANSetParamSet communication parametersCall this API for each CH in use (communication parameters can be configured independently for each CH).
3MPXSetGetLogModeSet log acquisition modeCall this API for each CH in use (log acquisition mode can be configured independently for each CH).
A CH for which this API is not called operates in log-acquisition API mode.
4MPXMonitorStartStart monitoringCall this API for each MicroPeckerX unit in use.
When operating multiple MicroPeckerX units synchronously, start monitoring for all MicroPeckerX units operating in slave mode, and then start monitoring for the MicroPeckerX unit operating in master mode.
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 this API for each MicroPeckerX unit in use at the timing when monitoring is stopped.
When multiple MicroPeckerX units are operating, stop monitoring for the MicroPeckerX unit operating in master mode first, and then stop monitoring for the MicroPeckerX units operating in slave mode sequentially.
7MPXCloseRelease MicroPeckerX recognitionCall this API once to release recognition of recognized MicroPeckerX units.
To start monitoring again while MicroPeckerX units remain recognized, restart processing from #2.