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
| # | API | Process | Description |
|---|---|---|---|
| 1 | MPXOpen | Recognize MicroPeckerX | Connect all target MicroPeckerX units to PC first, then call this API once. |
| 2 | MPXCANSetParam | Set communication parameters | Call for each channel in use (parameters can be configured independently per channel). |
| 3 | MPXSetGetLogMode | Set log acquisition mode | Call for each channel in use (mode can be set independently per channel). Channels not configured by this API run in callback mode. |
| 4 | MPXSetLogCallBack | Set callback for log acquisition | Call for each channel set to callback mode in #3 (different callback functions can be set per channel). Not required for channels in log-acquisition API mode. |
| 5 | MPXMonitorStart | Start monitoring | Call 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. |
| 6 | MPXGetLog or MPXCANGetLogEx | Acquire log information | If log-acquisition API mode is set, periodically call this API per channel. If not called, buffer overrun may occur, but operation itself is not affected. Not required in callback mode. |
| 7 | MPXMonitorStop | Stop monitoring | Call 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. |
| 8 | MPXClose | Release MicroPeckerX recognition | Call once to release recognized units. If you want to restart monitoring while still recognized, restart from step #2. |