HMI - FactoryClient

Knowledge Base

This guide provides a practical reference for powering, connecting, configuring, and troubleshooting a FactoryClient unit. Use it during installation, first-time setup, and incident response to quickly identify common issues and the recommended corrective actions.

Guide area

What it covers

Power and display

Startup, power adapter, LEDs, monitor, HDMI, and DisplayPort checks

Network and server connectivity

IP conflicts, wizard setup validation, ethernet, routing, and port access

Peripherals and recovery

Antennas, Wi-Fi or Bluetooth reception, on-screen keyboard, and reconfiguration access

Use this page when a FactoryClient fails to start, cannot display video, cannot join the network, cannot reach the FactoryBrain server, or needs reconfiguration after deployment.

Quick triage checklist

  • Confirm the unit has power and the front Power LED responds.

  • Check monitor cabling and input source selection.

  • Validate network settings before applying them in the wizard.

  • Verify physical ethernet connectivity and server IP accuracy.

  • Inspect antenna installation for wireless-related issues.

  • Use the keyboard shortcut or GUI path to enter reconfiguration.

  • For production onboarding, submit the required support ticket details.

Power and display issues

FactoryClient unit does not power on

If the unit does not start, begin with the power chain and confirm the hardware is receiving the correct input.

  • Confirm the AC power cord and 12V DC power adapter are properly connected to the rear DC-in jack and a live mains outlet.

  • Press the power switch and verify that the front Power LED illuminates.

  • If the stock adapter is faulty, replace it with a compatible 9V–24V DC power supply equipped with a 5.5 × 2.5 mm DC tip.

  • The default standard power rating is 12V DC with a 5.5 × 2.1 mm connector.

If replacement power hardware is used, verify voltage range and connector compatibility before powering the device.

No video output on connected monitor

If the unit appears powered but nothing is shown on the display, check the video path end to end.

  • Ensure the HDMI cable is securely connected to rear port HDMI 1 or HDMI 2, or use the DisplayPort connection.

  • Verify the external display is powered on and set to the correct input source.

  • Confirm the monitor supports resolutions up to 3840 × 2160 at 30 Hz.

  • Inspect video cables for physical damage, bent pins, or loose seating.

If possible, test with a known-good cable and a different monitor input to isolate whether the issue is the cable, display, or device output.

Network and server connectivity

Network setup failed or IP address collision during wizard setup

During FDOS setup, IP conflicts usually indicate that the selected address is already assigned elsewhere on the network.

  • If the message IP address you want to set for this device is already in use appears in FDOS Step 2, review the entered network parameters and assign a unique, available IP address.

  • Before clicking Apply, verify that Hostname, IP Address, Netmask, and Default Gateway all match the plant network scheme.

Incorrect addressing can prevent both local connectivity and communication with upstream FactoryBrain services, even if the device appears otherwise functional.

FactoryBrain server connection check failed

If the wizard reports a configuration flow error or cannot complete server checks, validate both physical and logical connectivity.

  • If Step 3 returns TCP/452 status - NOT OK or fails ICMP or TCP validation, confirm the ethernet cable is connected to an active network port on the industrial switch.

  • Confirm the Target FB Server IP entered in the setup wizard is accurate.

  • Contact the local IT administrator to verify network routing, default gateway settings, and firewall permission for ICMP, TCP port 443, and TCP port 452.

Check area

What to verify

Why it matters

Physical link

Ethernet cable seated correctly and switch port active

Without link, all higher-level checks will fail

Addressing

Target FB Server IP, device IP, netmask, and gateway are correct

Bad addressing causes unreachable hosts or misrouted traffic

Firewall and routing

ICMP, TCP 443, and TCP 452 permitted across the required path

Server validation depends on these protocols and ports

Wireless, input, and reconfiguration

Weak Wi-Fi signal or Bluetooth beacon reception issues

Wireless performance problems are commonly caused by missing antennas, poor placement, or enclosure shielding.

  • Verify that both RP-SMA antennas from the delivery package are securely screwed onto the rear gold antenna connectors.

  • If the FactoryClient is installed inside an enclosure or in a low-reception area, replace the standard antennas with extended-range antennas using RP-SMA male connectors.

Metal enclosures and dense industrial environments can significantly reduce Wi-Fi and Bluetooth performance even when the device is functioning correctly.

On-Screen Keyboard not opening or typing incorrectly

Keyboard issues can come from launching the wrong keyboard component or from mismatched localization settings.

  • For general OS navigation, click the keyboard icon in the system top panel to open the OS-level On-Screen Keyboard.

  • If running Vision Client Launcher, use the developer-configured Ignition OSK for application text fields.

  • If typed characters do not match the expected layout, verify settings under Step 4: Localization or in Region & Language settings.

Reconfiguration menu will not trigger

If reconfiguration cannot be opened normally, use either the boot-time shortcut or the in-system menu path.

  • Power cycle the unit or perform a system reboot through the GUI menu.

  • During early boot while Loading modules up... appears on screen, press [CTRL] + [ALT] + [SHIFT] + [P] on an external USB keyboard.

  • Alternatively, once fully booted into FDOS, open the App menu in the bottom-left corner and click the Reconfiguration wrench icon.

If the boot-time shortcut is missed, the GUI-based reconfiguration option provides a second path without repeating the full installation procedure.

Production integration and support handoff

Device deployed but pending production integration

After the initial wizard is complete, the device may still require internal enablement before it is fully integrated into production operations.

  • After the wizard configuration reboots into the GUI, open an internal support ticket with Request type: Connect a device.

  • This allows Plantformance to patch the FactoryClient for production integration.

  • Include the engraved device Serial Number, configured IP address, and assigned Hostname in the ticket.

Required ticket detail

Description

Serial Number

Use the engraved hardware serial exactly as shown on the device

IP address

Provide the final configured device IP address

Hostname

Provide the assigned hostname used during setup

FAQ

When should I involve IT?
Involve IT when server checks fail, when routing or gateway settings are uncertain, or when firewall permissions for ICMP, TCP 443, or TCP 452 may be blocking communication.

What is the fastest way to diagnose a blank screen?
First confirm the unit powers on and the LED responds, then validate the monitor input source and test the HDMI or DisplayPort cable connection.

Why would wireless reception be poor even if the device is working?
Missing antennas, loose RP-SMA connections, enclosure shielding, and installation in low-signal areas can all reduce Wi-Fi or Bluetooth performance.

Best practice: Validate power, network cable connection, and switch port activity before moving to software or configuration troubleshooting. These checks resolve many installation and connectivity issues quickly.

Quick reference checklist
  • Confirm the provided USB-C power brick is connected and the power source is active

  • Check the Ethernet RJ45 S/FTP Cat6 cable and switch port status

  • Attach a USB keyboard before attempting initial network configuration

  • Use [CTRL] + [ALT] + [SHIFT] + [P] during Loading modules up... to open network setup

  • Verify IP address, netmask, and gateway match plant network requirements

  • For NFC issues, verify supported badge use and badgeID configuration

  • For barcode issues, confirm scanner settings in Ignition

Last updated: