Troubleshooting

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.

Window behavior is as follows.

Window	No connected unit	Connected unit without registered license
Device Window	No Device is shown on target channel.	Normal screen is shown on target channel.
Trigger Window	If no unit is recognized at all, Device not connected. is shown. If at least one unit is recognized, behavior depends on whether that unit has a standard license.	If all recognized units have no standard license, No License is shown. If at least one unit has standard license, normal screen is shown.
Display Filter Window	Device not connected. is shown on target channel tab.	No License is shown on target channel tab.
Label Filter Window	If no unit is recognized at all, Device not connected. is shown. If at least one unit is recognized, behavior depends on whether that unit has a standard license.	If all recognized units have no standard license, No License is shown. If at least one unit has standard license, normal screen is shown.
Monitor Window	Device 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 Window	Device 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.
Simulation Window	Device not connected. is shown on target channel tab.	No License is shown on target channel tab.
Analyze Window	Normal screen is shown on target channel tab.	Normal screen is shown on target 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 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​

• After firmware update, unplug/replug of the MicroPeckerX unit may be required.
  See How to Update MicroPeckerX Firmware.

Communication fails​

• Check the following:
  • LIN cable is connected correctly (see How to Connect Devices).
  • If multiple MicroPeckerX units are recognized, units are connected by sync cable (see How to Connect Devices).
  • Communication settings such as baudrate are correct (see Communication Settings).

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.

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.