Hi Revopoint team,
I’m having trouble getting my POP 4 to connect in WiFi Client mode. Host mode works fine, but Client mode fails to connect under every configuration I’ve tried.
Setup:
- Scanner: POP 4
- Software: Revo Scan 6 (latest version downloaded directly from the official site)
- Computer: Windows PC, WiFi adapter is a Qualcomm FastConnect 7800
- Powering the scanner via the Battery Grip during all WiFi tests (not USB)
What I did:
- Connected the POP 4 via USB, opened Revo Scan 6, went to Settings > Connection Mode, and switched from Host to Client
- Entered network SSID and password, clicked Confirm, and waited for the scanner to reboot (indicator light cycled off then back to solid green)
- Unplugged USB, powered the scanner via the Battery Grip, and waited 60+ seconds for it to associate
Networks tested (all with the scanner set to Client mode with matching credentials each time):
- My main TP-Link Deco mesh network (WPA2-Personal, 2.4GHz) — scanner never appeared in the router’s connected devices list
- A dedicated 2.4GHz IoT network on the same Deco mesh (WPA2, simple SSID/password, no spaces or symbols) — scanner never appeared in the device list
- My phone’s mobile hotspot (simple SSID/password, no symbols) — scanner never appeared in the phone’s connected devices list either
In all three cases, the scanner’s indicator light goes solid green after the reboot, suggesting it thinks it’s powered and ready, but it never actually shows up as a connected client on any of the three separate networks tested. I also tried an open/no-password network via Revo Scan, but the software requires a password field to be filled in for Client mode, so I couldn’t fully rule out an auth-specific issue that way.
This suggests the scanner’s WiFi radio may not be associating with any network at all in Client mode, rather than an issue specific to my home network configuration.
Could you let me know if this is a known issue with the current POP 4 firmware or Revo Scan 6 build, and whether a fix is planned? Happy to provide additional logs, firmware version info, or test further if that would help.
Thanks,
