CAN Simulation Sequence
In the flow below, solid-line boxes indicate required processing and dashed-line boxes indicate optional processing.
☆ means call multiple times depending on the number of MicroPeckerX units, and ★ means call multiple times depending on the total number of channels in use.
Sequence Table
| # | API | Process | Description |
|---|---|---|---|
| 1 | MPXOpen | Recognize MicroPeckerX units | Connect all target MicroPeckerX units to the PC, then call this API. |
| 2 | MPXCANSetParam | Set communication parameters | Call this API for each channel in use. Parameters can be configured independently per channel. |
| 3 | MPXSetGetLogMode | Set log acquisition mode | Call this API per channel. Mode can be set independently per channel. Channels where this API is not called operate in callback mode. |
| 4 | MPXSetLogCallBack | Set callback function for log acquisition | Call per channel configured for callback mode in #3. Not required for channels configured for log-acquisition API mode. |
| 5 | MPXCANSetSlot | Configure slot information before monitoring | Configure slot information as needed. |
| 6 | MPXMonitorStart | Start monitoring | Call this API for each MicroPeckerX unit in use. For synchronized operation, start all slave-mode units first, then the master-mode unit. |
| 7 | MPXGetLog or MPXCANGetLogEx | Acquire log information | If log-acquisition API mode is set, call periodically per channel. Buffer overrun may occur if logs are not retrieved continuously, but operation is still maintained. Not required in callback mode. |
| 8 | MPXCANChangeSlot or MPXCANSendSlot or MPXCANDirectSend | Change slot configuration during monitoring / request slot transmit / send frame | Change slot settings or transmit data as needed. |
| 9 | MPXMonitorStop | Stop monitoring | Call this API for each unit when stopping monitoring. For multiple units, stop master-mode unit first, then slave-mode units sequentially. |
| 10 | MPXClose | Release MicroPeckerX recognition | Call once to release recognized units. To start monitoring again while keeping recognition, restart from #2. |