Skip to main content
Version: Ver.4.10

Troubleshooting

Checking Signal Features​

SymptomCheck FirstDetailed Instructions
Target item is missing from CatalogSearch, Only selected Set, import source, and import targetsImporting communication definitions
Import errors or garbled textCharacter encoding, Reload, Import Errors details, and the source fileImporting and reimporting
A signal is in the Set but has no valueCurrent Set, reception of actual frames, and Monitor/Values displayChecking the display
CH is UnassignedAssign 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 displayedIf 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 selectedCheck the status bar for partial application of a saved Set or pending synchronization after loading MPXXML.Loading restrictions
Values are incorrectSource frame, ID format, DL, direction, bit positions, Endian, and conversionBus signal definitions
Values are shown but no graph appearsGraph enabled, Graph/Area/axis assignments, and time rangeGraph assignments
Alerts do not appearCondition enabled, usage target, threshold, duration, and missing reception/updatesAlerts
A signal cannot be selected for Signal TriggerCurrent Set, CH, and whether it is a numeric bus signal. Derived and ASCII signals are not supported.Signal Trigger
Logs are not recordedSave Log File, destination, Trigger Mode, start/stop conditions, and waiting stateLogging conditions
Matched signals is 0Log CH, Set membership, Protocol, ID, direction, and data lengthSelecting analysis definitions
Catalog cannot be editedWhether you opened the shared Catalog or the analysis Catalog, and whether monitoring or analysis is runningEditing analysis definitions
Definition changes are not reflected in transmission settingsCatalog 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/loadingSave format and selected items, connected devices, CH in all Sets, and Current SetSaving 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.

GUI No device

Window display behavior is as follows.

WindowNo connected unitConnected unit without license
Device WindowNo Device is shown for the relevant channel.Normal screen is shown for the relevant channel.
Trigger WindowDevice not connected. is shown. note1No License is shown. note2
Display Filter WindowDevice not connected. is shown on the relevant channel tab.No License is shown on the relevant channel tab.
Label Filter WindowDevice not connected. is shown. note1No License is shown. note2
Monitor WindowDevice 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 WindowDevice 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 WindowDevice not connected. is shown on the relevant channel tab.No License is shown on the relevant channel tab.
Analyze WindowNormal 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 Window are correct.
    When filtering is active, a mark like Filter icon 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 Window is Triggered, analysis/log targets are not recognized until start trigger condition is met. Set Trigger Mode to Free Run or 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 when Clock Synchronized is 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 Option dialog, change CAN ID Form to SID/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.