Skip to main content
Version: Ver.4.10

Troubleshooting

Troubleshooting Signals and Communication Definitions​

SymptomCheck firstDetailed procedure
Target is missing from CatalogCheck Source, search, and the Only selected Set filter.Catalog Screen
An import error occursCheck the target and reason in the Import screen, then review character encoding and the LDF contents.Importing Communication Definitions
No values appear although the signal is in a SetCheck that the Set is Current and that LIN responses are being received.Checking Signal Window Display
CH is UnassignedAssign the LIN CH to use. After manually loading MPXSIG, check CH assignments in other Sets as well.Saving and Loading
Signals on a saved CH are missingIf the status bar shows Signal Set suspended:, reconnect the devices used when saving and select Device → Refresh.Automatically Restoring 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
Received values differ from expectationsCompare the source data's bit positions, byte order, sign, and conversion.Manual Definitions and Conversion Preview
Values appear but no graph is displayedEnable Graph display and assign the signal to the displayed Graph and Area.Assigning Signals to Graphs
No alert occursCheck that the condition is enabled and that its target and duration are correct.Alert Conditions
A signal cannot be selected for a triggerCheck Current Set membership, CH, signal type, and list filters.Signal Trigger
No log is recordedCheck Save Log File, the save destination, Trigger Mode, and the start condition.Trigger Modes
Matched signals is 0Compare the log and definition CH, ID, Direction, and DL.When Analysis Is Unavailable
Catalog cannot be editedCheck whether monitoring or analysis is running.Definition Changes and Reanalysis
A schedule is missing from the candidatesCheck that the Source LDF's Schedule_tables are registered in Catalog.Importing Schedules
Definition changes are not reflected in transmission dataCheck the definition currently in use, ID, DL, and HEX, then select the definition again.Editing Initial Values
Assignments changed after saving or loadingCheck the file format, loaded items, connected CH, and Current Set.Saving and Loading Settings

If You See These Symptoms​

"Device not connected." or "No Device" is shown in windows​

If no recognized unit exists, or only units without registered licenses are recognized, window display changes as follows.

Device not connected. No License

Window behavior is as follows.

WindowNo connected unitConnected unit without registered license
Device WindowNo Device is shown on target channel.Normal screen is shown on target channel.
Trigger WindowIf no units are recognized, Device not connected. is displayed.
If at least one unit is recognized, the display depends on whether a standard license is registered on that unit.
If none of the recognized units has a standard license, No License is displayed.
If at least one recognized unit has a standard license, the normal screen is displayed.
Display Filter WindowDevice not connected. is shown on target channel tab.No License is shown on target channel tab.
Label Filter WindowIf no units are recognized, Device not connected. is displayed.
If at least one unit is recognized, the display depends on whether a standard license is registered on that unit.
If none of the recognized units has a standard license, No License is displayed.
If at least one recognized unit has a standard license, the normal screen is displayed.
Monitor WindowDevice not connected. is shown on target channel tab.No License is shown on target 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.

After starting monitoring, frames are being transmitted/received but nothing is shown in Monitor Window​

  • Check whether filter settings in Display Filter Window are correct.
    When filter display is enabled, the following mark is shown on the target channel tab in Monitor Window.
  • Check whether displayed channel matches the channel of the MicroPeckerX you intend to use.

When stopping monitoring, message "There was no logging data." appears and log file is not saved​

  • In Trigger Window, if Trigger Mode is Triggered or ReTriggered and start trigger is enabled, logging does not start until start-trigger condition is met. Change Trigger Mode to Free Run or review start trigger conditions.

Nothing is shown in Simulation Window​

  • In Device Window, check:
    • MicroPeckerX unit is recognized (if not, click Device Refresh to re-detect).
    • Checkbox on the left of the channel number for the unit you want to use is ON.

"Need Update" is shown even after firmware update is repeated​

Communication fails​

Error frame is not transmitted​

  • For ShortMsg. error or Framing error, you can set byte position where error occurs. Set a byte position within data-length range of transmit frame.
    If byte position is outside data-length range, Error field in Simulation Window frame list is grayed out as below and the error becomes invalid.
Invalid Error Frame

Schedule switching does not behave as expected​

  • Schedule switching occurs only in either of these cases:
    • Transmission of registered frames in currently running schedule completes one cycle.
    • Wakeup is executed after a sleep command is accepted.

Want to load logs captured by MicroPecker Analyzer​

  • In Ch Log tab of Analyze Window, logs from MicroPecker LIN Analyzer can be loaded. See Ch Log Tab Display.
    For details of MicroPecker Analyzer log files, refer to the MicroPecker Analyzer User's Manual.