Ticket #1817688

Hello, I have an issue with our VT-X750. I have logs and the dump file. The application fails to reach the main menu upon an apparent communication issue... "Communication error has occurred in equipment operation end sending in the upper-system communication." The below provided is all I have on the issue. OMRON VT-X750 - STARTUP / MAIN MENU FAILURE Technician Evidence Package - Errors, Exceptions, and Startup Trace Equipment Omron VT-X750 Application version VT-X750 software 1.39.4.23; system log version 6.06.00B Reported symptom Warm-up completes, but the visible Main Menu window does not launch. VT-X750x64.exe may remain listed in Task Manager. Evidence supplied XRayTraceLog.log, EventErrorLogE.txt and companion logs, VT-X750x64 crash dumps, WinDbg !analyze -v output 1. Technician summary Confirmed behavior: The application reaches and logs the Main Menu transition after successful initialization/warm-up, but the operator does not receive a visible usable Main Menu. * The GUI is native MFC/C++ code in VT-X750x64.exe; it is not supplied by the Python directory. * On multiple July 20 starts, InitMecha, SelfCheck, and WarmingUp returned Result=1 before the MainMenu log entry. * Immediately after the MainMenu log entry, the software reports that two iBELT output-path settings are not configured. * On two July 20 runs, the software explicitly entered code to show a Link System Communication Error Dialog. * A captured crash run terminated through an unhandled MFC invalid-argument exception, followed by terminate(), abort(), and FAST_FAIL_FATAL_APP_EXIT. * The log entry 'Welcome to MainMenu' confirms entry into Main Menu logic; it does not prove that the window was successfully created, displayed, or made interactive. 2. Latest complete startup sequence The following sequence is copied from XRayTraceLog.log for the July 20 run ending in the Link System communication dialog: 26/07/20 16:30:37.449, 84109,3,NWin.cpp:: [L.8779], < >,LinkSys Start_(Initialize) 26/07/20 16:30:37.449, 84109,3,NWin.cpp:: [L.8781], < >,LinkSys End_(Initialize) 26/07/20 16:31:16.011, 122671,4,MainFrm.cpp:: [L.1125],InitializeMecha:[END] InitMecha Result=1. 26/07/20 16:31:30.594, 137254,4,MainFrm.cpp:: [L.1170],InitializeMecha:[END] SelfCheck Result=1. 26/07/20 16:47:05.822, 1072482,3,CalibrationXray.cpp:: [L.138], < >,LinkSys SendEvent Start_(PassModeStart) 26/07/20 16:47:05.822, 1072482,3,CalibrationXray.cpp:: [L.140], < >,LinkSys SendEvent End_(PassModeStart) 26/07/20 16:47:06.425, 1073085,4,MainFrm.cpp:: [L.1197],InitializeMecha:[END] WarmingUp Result=1. 26/07/20 16:47:06.473, 1073133,4,MainMenuDlg.cpp:: [L.282],+++++Welcome to MainMenu+++++ 26/07/20 16:47:06.483, 1073143,4,MainFrm.cpp:: [L.1520],CMainFrame::CheckOutputPathForiBELT() : iBELT_CONFIG_FOLDER_PATH is not setting. 26/07/20 16:47:06.483, 1073143,4,MainFrm.cpp:: [L.1520],CMainFrame::CheckOutputPathForiBELT() : iBELT_CALIBRATION_FOLDER_PATH is not setting. 26/07/20 16:48:02.979, 1129639,4,LinkSysCommErrDlg.cpp:: [L.112],Show Link System Communication Error Dialog Interpretation: LinkSys initialization returned; mechanism initialization and self-check succeeded; a PassModeStart event was issued; warm-up returned Result=1; Main Menu logic was entered; both iBELT paths were reported missing; approximately 56 seconds later the application requested a Link System Communication Error Dialog. 3. Repeated current-startup warnings and errors Date/time Source Logged condition Relevance 2026-07-20 14:18:21; 14:52:49; 15:09:28; 16:47:06 MainFrm.cpp L.1520 iBELT_CONFIG_FOLDER_PATH is not setting. Missing iBELT configuration-output path. Repeats whenever Main Menu logic is entered. 2026-07-20 14:18:21; 14:52:49; 15:09:28; 16:47:06 MainFrm.cpp L.1520 iBELT_CALIBRATION_FOLDER_PATH is not setting. Missing iBELT calibration-output path. Log does not state that this is fatal. 2026-07-20 16:13:43 LinkSysCommErrDlg.cpp L.112 Show Link System Communication Error Dialog First explicit Link System communication-error-dialog request in the supplied XRayTraceLog. 2026-07-20 16:48:02 LinkSysCommErrDlg.cpp L.112 Show Link System Communication Error Dialog Second explicit request; occurred about 56 seconds after the MainMenu transition. 2026-07-20 07:49:23 EventErrorLogE code 5:5:1:-2 Communication error of Fins command has occurred. Startup communication fault recorded earlier the same day. 2026-07-20 07:49:24 EventErrorLogE code 5:1:3:2928 An error occurred in warming up at system startup. Historical startup failure on the same day; later starts show WarmingUp Result=1. 4. WinDbg exception analysis Dump analyzed: VT-X750x64.exe.3908.dmp (user minidump) Exception: 0xC0000409, fail-fast subcode 0x7 (FAST_FAIL_FATAL_APP_EXIT) Observed cause chain: MFC threw AfxThrowInvalidArgException; the C++ exception was not handled; the runtime called terminate() and abort(). Important qualification: Windows labels 0xC0000409 as a security-check/stack-buffer-overrun class, but the captured stack specifically shows deliberate fail-fast termination after an unhandled MFC invalid-argument exception. The minidump lacks private Omron symbols, so the exact VT-X750 caller could not be resolved. Exception code: 0xC0000409 Fail-fast subcode: 0x7 (FAST_FAIL_FATAL_APP_EXIT) Failure bucket: FAIL_FAST_FATAL_APP_EXIT_c0000409_ucrtbase.dll!abort Call stack: ucrtbase!abort+0x4e ucrtbase!terminate+0x1f VCRUNTIME140_1!FindHandler < __FrameHandler4>+0x45b VCRUNTIME140_1!__InternalCxxFrameHandler < __FrameHandler4>+0x267 VCRUNTIME140_1!_CxxFrameHandler4+0xa9 ntdll!RtlpExecuteHandlerForException+0xf ntdll!RtlDispatchException+0x244 ntdll!RtlRaiseException+0x1d7 KERNELBASE!RaiseException+0x69 VCRUNTIME140!_CxxThrowException+0x90 mfc140u!AfxThrowInvalidArgException+0x21 [unresolved application return address: 0x44a3f0] mfc140u!__afxThreadData 5. Event error history contained in EventErrorLogE.txt The table below consolidates every unique English error message in the supplied event log. Repeated occurrences are shown as a count and date range. This separates historical machine conditions from the current Main Menu visibility problem. Code Message Occurrences First occurrence Last occurrence 5:7:4:26 Air pressure is low. 10 29/09/2025 18:13:31 10/07/2026 08:16:35 6:7:4:25 Emergency stop was made. 2 29/09/2025 18:18:45 10/07/2026 07:49:53 3:7:4:194 Timeout has occurred in unloading. 9 09/10/2025 14:03:39 18/06/2026 13:00:20 3:7:4:200 Error has been detected in left side of PCB Loading/unloading status. 7 14/10/2025 14:48:47 13/07/2026 14:31:34 3:5:1:-11 Timeout has occurred in synchronization processing. 9 14/10/2025 14:50:19 10/07/2026 08:16:28 4:7:4:24 The front upper door is open (or emergency stop has been activated). 8 14/10/2025 14:50:19 10/07/2026 08:16:35 5:1:3:2925 An error occurred in mechanism initialization at system startup. 5 04/02/2026 05:59:26 10/07/2026 08:16:28 4:3:12:-15 Irradiation of X-ray is disabled because the X-ray source is in interlock state. 2 26/02/2026 13:42:53 10/07/2026 10:05:14 5:1:3:2928 An error occurred in warming up at system startup. 3 26/02/2026 13:42:53 20/07/2026 07:49:24 5:1:3:2923 The device is not in the correct status for the command execution. 3 03/06/2026 12:01:12 10/07/2026 10:32:23 5:7:4:17 An EtherCAT communication error has occurred. 1 15/06/2026 08:37:37 15/06/2026 08:37:37 5:7:4:18 An EtherCAT communication error has occurred. 1 15/06/2026 08:37:37 15/06/2026 08:37:37 5:7:4:19 An EtherCAT communication error has occurred. 1 15/06/2026 08:37:37 15/06/2026 08:37:37 5:7:4:20 An EtherCAT communication error has occurred. 1 15/06/2026 08:37:37 15/06/2026 08:37:37 5:7:4:21 An EtherCAT communication error has occurred. 1 15/06/2026 08:37:37 15/06/2026 08:37:37 5:7:4:49 XU axis EtherCAT communication error has occurred. 1 15/06/2026 08:37:37 15/06/2026 08:37:37 5:7:4:65 YU1 axis EtherCAT communication error has occurred. 1 15/06/2026 08:37:37 15/06/2026 08:37:37 5:7:4:69 YU2 axis EtherCAT communication error has occurred. 1 15/06/2026 08:37:37 15/06/2026 08:37:37 5:7:4:81 XL axis EtherCAT communication error has occurred. 1 15/06/2026 08:37:37 15/06/2026 08:37:37 5:7:4:97 YL axis EtherCAT communication error has occurred. 1 15/06/2026 08:37:37 15/06/2026 08:37:37 5:7:4:113 ZA1 axis EtherCAT communication error has occurred. 1 15/06/2026 08:37:37 15/06/2026 08:37:37 5:7:4:117 ZA2 axis EtherCAT communication error has occurred. 1 15/06/2026 08:37:37 15/06/2026 08:37:37 5:7:4:129 RB1 axis EtherCAT communication error has occurred. 1 15/06/2026 08:37:37 15/06/2026 08:37:37 5:7:4:130 RB1 axis motion control function error has occurred. 1 15/06/2026 08:37:37 15/06/2026 08:37:37 5:7:4:133 RB2 axis EtherCAT communication error has occurred. 1 15/06/2026 08:37:37 15/06/2026 08:37:37 5:7:4:134 RB2 axis motion control function error has occurred. 1 15/06/2026 08:37:37 15/06/2026 08:37:37 5:7:4:145 YW1 axis EtherCAT communication error has occurred. 1 15/06/2026 08:37:37 15/06/2026 08:37:37 5:7:4:149 YW2 axis EtherCAT communication error has occurred. 1 15/06/2026 08:37:37 15/06/2026 08:37:37 5:3:12:0 You have sent an invalid command. 1 15/06/2026 08:37:40 15/06/2026 08:37:40 5:3:12:201 Error has occurred in the supply voltage. 1 15/06/2026 08:37:40 15/06/2026 08:37:40 6:7:4:0 System power error has occurred. 1 15/06/2026 08:37:40 15/06/2026 08:37:40 4:7:4:32 The front lower door is open (or emergency stop has been activated). 1 30/06/2026 12:58:03 30/06/2026 12:58:03 4:7:4:33 The rear door is open (or emergency stop has been activated). 1 30/06/2026 12:58:03 30/06/2026 12:58:03 5:5:1:-2 Communication error of Fins command has occurred. 2 16/07/2026 16:20:22 20/07/2026 07:49:23 6. Errors most relevant to the current complaint * Main Menu display failure after successful warm-up: operator observation; not assigned a visible trouble code. * Repeated missing iBELT configuration and calibration folder-path settings during Main Menu entry. * Link System Communication Error Dialog requested but apparently not visible to the operator. * FINS command communication error recorded at startup on July 20. * At least one application run ended in an unhandled MFC invalid-argument exception and fail-fast abort. 7. Questions requested for manufacturer support 1. What subsystem is identified by LinkSys / LinkSysCommErrDlg in VT-X750 software version 1.39.4.23? 2. Can a Link System or upper-system communication failure block, disable, hide, or create a modal dialog over the Main Menu? 3. Where are iBELT_CONFIG_FOLDER_PATH and iBELT_CALIBRATION_FOLDER_PATH configured, and are they required for Main Menu launch? 4. Is there a supported method to disable or bypass LinkSys/iBELT for diagnostic startup? 5. Is there a known defect where MainMenuDlg.cpp logs 'Welcome to MainMenu' but the Main Menu window is not displayed? 6. Can Omron identify the application caller immediately below mfc140u!AfxThrowInvalidArgException using private symbols? 7. Which logs or full-dump capture settings should be used to obtain the internal trouble code when the GUI does not display? 8. Files available to provide * XRayTraceLog.log and all companion system logs * EventErrorLogE.txt (English event history) * VT-X750x64.exe.3908.dmp * VT-X750x64.exe.5464.dmp * WinDbg !analyze -v output from the 3908 dump * Application executable and configuration archives, if permitted by support/security policy -Ben S&K Electronics, Inc. 56301 U.S. Highway 93 Ronan, MT 59864 Phone: [phone], Ext. 2452 Fax: [phone] Email: [email] Website: www.skecorp.com