Troubleshooting
Checking Signal Features
| Symptom | Check First | Detailed Instructions |
|---|---|---|
| Target item is missing from Catalog | Search, Only selected Set, import source, and import targets | Importing communication definitions |
| Import errors or garbled text | Character encoding, Reload, Import Errors details, and the source file | Importing and reimporting |
| A signal is in the Set but has no value | Current Set, reception of actual frames, and Monitor/Values display | Checking the display |
| CH is Unassigned | Assign the CAN/CAN FD CH to use. After manually loading MPXSIG with Load, check CH assignments in all Sets, not just the current one. | Saving and loading |
| Signals on a saved CH are not displayed | If the status bar shows Signal Set suspended:, reconnect the device used when saving and select Device → Refresh. | Automatic restoration of saved Sets |
| Signal Monitor Setting cannot be selected | Check the status bar for partial application of a saved Set or pending synchronization after loading MPXXML. | Loading restrictions |
| Values are incorrect | Source frame, ID format, DL, direction, bit positions, Endian, and conversion | Bus signal definitions |
| Values are shown but no graph appears | Graph enabled, Graph/Area/axis assignments, and time range | Graph assignments |
| Alerts do not appear | Condition enabled, usage target, threshold, duration, and missing reception/updates | Alerts |
| A signal cannot be selected for Signal Trigger | Current Set, CH, and whether it is a numeric bus signal. Derived and ASCII signals are not supported. | Signal Trigger |
| Logs are not recorded | Save Log File, destination, Trigger Mode, start/stop conditions, and waiting state | Logging conditions |
| Matched signals is 0 | Log CH, Set membership, Protocol, ID, direction, and data length | Selecting analysis definitions |
| Catalog cannot be edited | Whether you opened the shared Catalog or the analysis Catalog, and whether monitoring or analysis is running | Editing analysis definitions |
| Definition changes are not reflected in transmission settings | Catalog definitions and previously applied transmission settings are separate. Apply the definitions again and check the HEX data. | Applying definitions to transmission settings |
| Assignments changed after saving/loading | Save format and selected items, connected devices, CH in all Sets, and Current Set | Saving and loading |
For connection or device problems, also check the symptom-specific sections below.
When This Happens
No MicroPeckerX connected / license not registered
If no unit is connected, or a connected unit has no registered license, window displays change as follows.
Window display behavior is as follows.
| Window | No connected unit | Connected unit without license |
|---|---|---|
| Device Window | No Device is shown for the relevant channel. | Normal screen is shown for the relevant channel. |
| Trigger Window | Device not connected. is shown. note1 | No License is shown. note2 |
| Display Filter Window | Device not connected. is shown on the relevant channel tab. | No License is shown on the relevant channel tab. |
| Label Filter Window | Device not connected. is shown. note1 | No License is shown. note2 |
| Monitor Window | Device not connected. is shown on the relevant channel tab. | No License is shown on the relevant channel tab.If monitor license is registered, normal screen is shown. |
| Each ID Window | Device not connected. is shown on the relevant channel tab. | No License is shown on the relevant channel tab.If monitor license is registered, normal screen is shown. |
| Simulation Window | Device not connected. is shown on the relevant channel tab. | No License is shown on the relevant channel tab. |
| Analyze Window | Normal screen is shown on the relevant channel tab. | Normal screen is shown on the relevant channel tab. |
note1: If any unit is recognized, behavior depends on whether that unit has a standard license.
note2: If a unit with standard license is also recognized, normal screen is shown.
Nothing is displayed in Monitor Window
- Check whether settings in
Display Filter Windoware correct.
When filtering is active, a mark like
is displayed on Monitor Window tabs. - Check whether the displayed channel matches the channel of the MicroPeckerX you want to use.
"There was no corresponding log." appears, Analyze Window is not displayed, or logs are blank
- If Trigger Mode in
Trigger WindowisTriggered, analysis/log targets are not recognized until start trigger condition is met. Set Trigger Mode toFree Runor change start trigger settings.
Nothing is displayed in Simulation Window
- Check whether MicroPeckerX is recognized in
Device Window. - Check whether the checkbox on the left side of the MicroPeckerX you want to use is enabled.
"Need Update" is shown even after repeated device updates
- After updating, unplug/replug may be required.
Communication fails
- Check the following:
- Communication cable connection (see "How to connect devices")
- Sync cable connection when using multiple MicroPeckerX units (see "How to connect devices")
Note: Sync cable is required even whenClock Synchronizedis not checked. - Communication settings such as baud rate (see
Device Window)
Error frame is not transmitted
- For ShortMsg error or Framing error, the error position can be configured. Set error position so it remains within frame DL.
If the position is invalid, the error type is shown in gray.
Event log does not behave as expected
- Another event log that can be established at the same time may exist for the target settings. Recheck event log settings. Later-configured event logs take priority.
Schedule does not behave as expected
- Schedule changes are applied only when the current schedule ends, or when a sleep command is accepted and wake-up is performed.
Want to display CAN extended-format ID split as SID and EID
- In
Optiondialog, changeCAN ID FormtoSID/EID.
Want to load logs captured by MicroPecker Analyzer
- Logs from MicroPecker CAN Analyzer can be loaded (Analyze Window, Ch Log tab only).
However, some logs (such as LIN format logs) cannot be converted. Load results (number of logs converted to MicroPeckerX format and number not converted) are shown in a dialog. For details of MicroPecker Analyzer format logs, refer to the MicroPecker Analyzer User's Manual.