# MetroY Pro constantly disconnects via USB/WIFI— rpcServiceMetroX crashes (SIGABRT) with logs **URL:** \ **Category:** Issues\ **Tags:** metroy, metroypro\ **Created:** [March 14, 2026, 2:30pm UTC](https://forum.revopoint3d.com/t/metroy-pro-constantly-disconnects-via-usb-wifi-rpcservicemetrox-crashes-sigabrt-with-logs/42138 "2026-03-14T14:30:45Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Illia](https://avatars.discourse-cdn.com/v4/letter/i/e79b87/32.png) [@Illia](https://forum.revopoint3d.com/u/Illia)\ **Post date:** [March 14, 2026, 2:30pm UTC](https://forum.revopoint3d.com/t/metroy-pro-constantly-disconnects-via-usb-wifi-rpcservicemetrox-crashes-sigabrt-with-logs/42138/1 "2026-03-14T14:30:45Z")
**Device:** Revo MetroY Pro, firmware `v2.8.77.20251209` **OS:** macOS 26.3.1 **App:** RevoMetro (latest) **Connection:** USB/WIFI **Problem** The scanner connects, then disconnects every ~18–20 seconds in a loop. The helper daemon `rpcServiceMetroX` crashes with SIGABRT 17 times in a row. Nothing works — no scanning is possible. * * * **Evidence from sdk.log** The SDK executes a shell command on the scanner via `executLongCmd`: ```auto [SDK TRACE] long cmd: cat /sys/devices/platform/usbdrd/fcc00000.dwc3/udc/fcc00000.dwc3/current_speed > /tmp/webroot/.currentSpeed [SDK TRACE] RPCCleint Req: {"msgId":"setUserData","filePath":"/tmp/.longCmd.sh","valLen":107} ``` First call (15:04:34) returns immediately: ```auto [SDK TRACE] current speed mode : super-speed ``` Second call (~15:04:37) gets no response: ```auto [SDK ERROR] set long cmd shell file failed, 1 [SDK ERROR] try 1 getUserData failed [SDK ERROR] try 2 getUserData failed [SDK ERROR] try 3 getUserData failed [SDK ERROR] get current speed file failed [SDK DEBUG] Certificat camera instance(D25B45909H6Q10L58) disconnect ``` * * * **Evidence from rvScan5.log** After each disconnect, the app reports: ```auto get scanner NTC TEMPERATURE error Scanner offline pause scanner Stream failed, ret=50462722 Connect to scanner failed, error=50462722 ``` This repeats in a cycle every 18–20 seconds. * * * **Evidence from crash report (rpcServiceMetroX-2026-03-14-151847.ips)** ```auto Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 abort() called Crashed Thread: [N] Thread [N] Crashed: 0 libsystem_kernel.dylib __pthread_kill 1 libsystem_pthread.dylib pthread_kill 2 libsystem_c.dylib abort 3 lib3DCamera.dylib (4 frames within lib3DCamera.dylib) ``` Process is translated (Rosetta 2, x86\_64 on Apple Silicon). * * * **Evidence from system launchd log** ```auto rpcServiceMetroX exited due to SIGABRT | sent by rpcServiceMetroX[PID] service has crashed 1 times in a row (last was not dirty) ... service has crashed 17 times in a row (last was not dirty) ``` Each crash interval: ~70 seconds. launchd restarts the helper each time. Why does `executLongCmd` with `cat /sys/devices/platform/usbdrd/fcc00000.dwc3/udc/fcc00000.dwc3/current_speed` cause the scanner to stop responding to all subsequent RPC calls? 1. Is firmware `v2.8.77.20251209` known to have issues with this command on USB 3.0? 2. Is there a previous firmware version available that does not have this issue? 3. Can `rpcServiceMetroX` and `lib3DCamera.dylib` be compiled as arm64 native (currently x86\_64 only, running under Rosetta 2)? ---
**Author:** ![PUTV](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.revopoint3d.com/putv/32/15302_2.png) [@PUTV](https://forum.revopoint3d.com/u/PUTV)\ **Post date:** [March 14, 2026, 3:03pm UTC](https://forum.revopoint3d.com/t/metroy-pro-constantly-disconnects-via-usb-wifi-rpcservicemetrox-crashes-sigabrt-with-logs/42138/2 "2026-03-14T15:03:48Z")
Hi @Illia There are i dated in progress planned for Match addressing the crashing of MetroX However please send email to [customer@revopoint3d.com](mailto:customer@revopoint3d.com) regarding your issues with MetroY Pro , you can include the thread link for a reference in place of type it again. For MetroX you can use Revo Scan 5 MetroX early version of early version of Revo Metro , for MetroY Pro you can also download early version of Revo Metro from the download page , just scroll down the page to access early versions. > [@Illia](#): > > Is firmware `v2.8.77.20251209` known to have issues with this command on USB 3.0? The firmware has no issue but the latest software. > [@Illia](#): > > Is there a previous firmware version available that does not have this issue? Again firmware versions can’t be updated and they are not the problem > [@Illia](#): > > Can `rpcServiceMetroX` and `lib3DCamera.dylib` be compiled as arm64 native (currently x86\_64 only, running under Rosetta 2)? Sadly not at this moment but in the future it will be. ---
**Author:** ![Illia](https://avatars.discourse-cdn.com/v4/letter/i/e79b87/32.png) [@Illia](https://forum.revopoint3d.com/u/Illia)\ **Post date:** [March 14, 2026, 3:34pm UTC](https://forum.revopoint3d.com/t/metroy-pro-constantly-disconnects-via-usb-wifi-rpcservicemetrox-crashes-sigabrt-with-logs/42138/3 "2026-03-14T15:34:01Z")
Hi, Just to clarify again — I have **MetroY Pro** , not MetroX. Please keep this in mind as the issues and fixes may differ between models. I tested with **Revo Metro v5.8.4.31** (older version as suggested) — the issue is **identical**. From `sdk.log` of v5.8.4.31 (SDK V3.2.244): ```auto [SDK TRACE] long cmd: cat /sys/devices/platform/usbdrd/ fcc00000.dwc3/udc/fcc00000.dwc3/current_speed > /tmp/webroot/.currentSpeed [SDK TRACE] RPCCleint Req: setUserData /tmp/.longCmd.sh → success [SDK TRACE] execute cmd: sh /tmp/.longCmd.sh → 5 second timeout → not response → Scanner offline / NTC TEMPERATURE error ``` This `executLongCmd` call is inside `lib3DCamera.dylib` (the SDK library), not just the UI layer. Downgrading RevoMetro software does **not** fix the issue — the bug is in the SDK bundled with all recent versions. Additional problem: after multiple failed connection attempts, the scanner’s internal processes become permanently stuck. The power does **not** fully reset them — even after restarting the scanner it returns `algorithmVersion=v000.0.0.0000` and `RGB exposure = 0`, indicating a degraded internal state. Is there a way to force a full hardware reset? ---
**Author:** ![PUTV](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.revopoint3d.com/putv/32/15302_2.png) [@PUTV](https://forum.revopoint3d.com/u/PUTV)\ **Post date:** [March 14, 2026, 4:31pm UTC](https://forum.revopoint3d.com/t/metroy-pro-constantly-disconnects-via-usb-wifi-rpcservicemetrox-crashes-sigabrt-with-logs/42138/4 "2026-03-14T16:31:13Z")
Hi @Illia Sorry I can’t help you here with your technical issues of the hardware, please contact [customer@revopoint3d.com](mailto:customer@revopoint3d.com) for technical assistance as that is not normal behavior. Things like hardware reset can be only performed by the technician, in most cases that you described the unit will be replaced if it get stuck on reboot.