GUI Application Messages
| Message | Description | Resolution |
|---|---|---|
| A file necessary for startup is lacked. Please reinstall control software. | A required file for startup is missing. Reinstall the control software. | Reinstall the control software to restore the missing runtime files. |
| Buffer Over Run Serial : 13XXXXX - X State : XXX Please re-connect all "MicroPeckerX" and refresh device. | Buffer overrun. Serial number: 13XXXXX - X State: XXX Reconnect every MicroPeckerX unit and refresh the device list. | Contact the manufacturer. |
| Configuration Load Error. Error : XXX | Configuration load error. Error: XXX | Load the correct configuration file. |
| Configuration Load Error. File not exists. | Configuration load error. File not found. | Confirm that the configuration file name is correct. |
| Configuration Load Error. File version is Illegal. | Configuration load error. The file version is invalid. | Load a configuration file saved with a supported version. |
| Configuration Load Error. Folder is not exists. | Configuration load error. Folder not found. | Verify that the configuration file path is correct. |
| Configuration Load Error. Illegal file format. | Configuration load error. Unsupported file format. | Load the configuration file in the correct format. |
| Configuration Save Error. Folder is not exists. | Configuration save error. Folder not found. | Verify that the destination folder path is correct. |
| Currently logging. Are you sure you want to abort? | Logging is in progress. Do you really want to stop? | If you stop logging, the saved files remain but timestamps across channels may no longer align. |
| Currently under monitoring. Are you sure you want to terminate? | Monitoring is in progress. Do you really want to stop? | - |
| Delete layout "XXX"? | Delete layout "XXX"? | - |
| Error of generating log replay buffer. | Failed to create the log replay buffer. | Free sufficient disk space. |
| Failed to ready for log replay thread. | Failed to initialise the log replay thread. | The PC may be low on disk space or memory. Use a machine with higher specifications. |
| Failed to ready for monitor thread. | Failed to initialise the monitor thread. | The PC may be low on disk space or memory. Use a machine with higher specifications. |
| Failed to save the log. | Failed to save the log. | Make sure the destination file is not open in another application. |
| Internal Error Serial : 13XXXXX - X Error Code : XXX State : XXX Please re-connect all "MicroPeckerX" and refresh device. | Internal error. Serial number: 13XXXXX - X Error code: XXX State: XXX Reconnect every MicroPeckerX unit and refresh the device list. | Contact the manufacturer. |
| It failed save error log. | Failed to save the error log. | Make sure the destination file is not open in another application. |
| Layout "XXX" already exists. Overwrite? | Layout "XXX" already exists. Overwrite it? | - |
| Logging canceled. The contents of the log file are not guaranteed. | Logging was cancelled. The contents of the log file are not guaranteed. | If you stop logging, the saved files remain but timestamps across channels may no longer align. |
| MicroPeckerX Communication Error Serial : 13XXXXX - X Error Code : XXX Please re-connect all "MicroPeckerX" and refresh device. | MicroPeckerX communication error. Serial number: 13XXXXX - X Error code: XXX Reconnect every MicroPeckerX unit and refresh the device list. | Contact the manufacturer. |
| ”MicroPeckerX Control Software” is already started. | “MicroPeckerX Control Software” is already running. | The application cannot run multiple instances. |
| MicroPeckerX information acquisition failed. | Failed to retrieve MicroPeckerX information. | Reinstall the control software to restore the missing files. |
| Monitor synchronization error. Check the connection of the synchronous cable. | Monitor synchronisation error. Check the connection of the sync cable. | When you use multiple units, connect the MicroPeckerX devices with the synchronisation cable. |
| No setting information of the connected device. Display the import dialog? | No configuration data was found for the connected device. Open the import dialog? | If the configuration file lacks the connected device information, run the import process. |
| Set layout "XXX" as default? | Set layout "XXX" as the default? | - |
| Setting Error. [Simulation] The file of log replay is not load. Serial : 13XXXXX Ch : X | Setting error. [Simulation] No log replay file has been loaded. Serial number: 13XXXXX Ch: X | Load the log file before you start monitoring. |
| Setting Error. [Trigger] In the ReTriggered mode, must set the start trigger. | Setting error. [Trigger] ReTriggered mode requires a start trigger. | Configure a start trigger when you use ReTriggered mode. |
| Setting Error. The key trigger is duplicated. Key:XXX ChX-X XXX ChX-X XXX | Setting error. The key trigger is duplicated. Key: XXX ChX-X XXX ChX-X XXX | Check for duplicate key triggers and avoid assigning the same key twice. |
| Setting Error. The log folder does not exist. | Setting error. The log folder does not exist. | Verify the log output folder path. |
| The Help file is not found. | The help file was not found. | Reinstall the control software. |
| The log folder number has reached its maximum. | The log folder index has reached its maximum. | Select a different destination folder. |
| There are no logging data. | No logging data was captured. | Check the connections between the MicroPeckerX and the target device. |
| Setting is cleared. Are you sure? | Settings will be cleared. Do you want to continue? | - |
| Delete the display filter? | Delete the display filter? | - |
| Setting is cleared. Are you sure? | Settings will be cleared. Do you want to continue? | - |
| Delete the label filter "XXX"? | Delete the label filter "XXX"? | - |
| Load Error. | Load error. | Confirm that the HEX or binary file is formatted correctly. |
| Event Trigger is not selected. Are you sure to continue? | No event trigger is selected. Continue? | If you send frames in event mode, configure an event trigger first. |
| Log File Header Error. | Log file header error. | Load a log file that uses the correct format. |
| Log file is not found. | Log file not found. | Verify that the file path is correct. |
| Log File Read Error. Line:XXX | Log file read error. Line: XXX | Load a log file that uses the correct format. |
| Setting is cleared. Are you sure? | Settings will be cleared. Do you want to continue? | - |
| The number of maximum transmission logs is exceeded. | The maximum number of transmission log records has been exceeded. | Log replay and burst transmission support up to 1.2 million records. Anything beyond that is discarded. |
| Are you sure to clear list? | Clear the list? | - |
| Failed to save. | Failed to save. | Make sure the destination file is not open in another application. |
| Log File Incompatible Error. | Log file compatibility error. | The Analyze tab cannot open MicroPecker-format logs directly. Load them in the Ch Log tab and merge them there first. |
| Old Format Log Convert Result Chx-x : Valid Log = XXX, Invalid Log = YYY | Old format log conversion result. Chx-x : valid logs = XXX, invalid logs = YYY | Logs that only exist in the MicroPecker format and are unsupported by MicroPeckerX are discarded. Review the invalid logs before using the result. |
| The same Ch can not be specified. | The same channel cannot be specified. | Configure different channels for the gateway source and destination. |
| There are no valid analytical logs. | No valid analysis logs remain. | All entries were filtered out. Review your filter settings. |