HMI - FactoryClient

Testing functionalities

This guide provides a practical end-to-end process for validating a FactoryClient after installation, power events, hardware replacement, or connectivity issues. It covers startup behavior, display verification, network testing, wireless signal checks, input devices, runtime deployment, and the network reconfiguration shortcut.

Use this page as a field reference when commissioning a new unit, troubleshooting a failed connection, or confirming that a replacement device is ready for production use.

Purpose and Scope

The FactoryClient is typically validated by confirming that the hardware powers on correctly, the FDOS setup wizard displays properly, network paths to the target FactoryBrain server are reachable, required peripherals respond, and the selected runtime application starts automatically after reboot.

A successful validation should confirm both local functionality and upstream connectivity. In practice, this means the unit must not only boot and display correctly, but also pass the required protocol checks to the target server and launch the correct industrial application.

Expected outcome: The device powers on, displays the FDOS interface, passes connection checks for ICMP 0/8, TCP/443, and TCP/452, accepts user input, and automatically launches the configured runtime application after reboot.

Functional Test Procedure

1. Power and standby functionality

Begin by validating basic power behavior before testing any software or connectivity feature.

  • Press the front power switch to power on the FactoryClient and verify that the Power LED turns on.

  • If the installed power adapter is suspected to be faulty, test with a compatible 9V–24V DC input adapter using a 5.5 × 2.5 mm connector.

  • The default power configuration is typically 12V DC with a 5.5 × 2.1 mm tip, so confirm adapter compatibility before replacement testing.

  • Test shutdown or reboot behavior from the FDOS GUI interface.

  • Also verify manual shutdown behavior by pressing and holding the power button for 5 seconds.

If the unit does not power on, isolate the issue by checking the outlet, DC adapter output, connector fit, and any upstream power strip or cabinet power distribution.

2. Display output

Once power is confirmed, verify that the device provides stable video output on the intended interface.

  • Connect an external monitor or touch display to the rear HDMI 1, HDMI 2, or DisplayPort (DP).

  • Confirm that the initial FDOS setup wizard, including the Welcome screen, renders correctly.

  • Verify that the connected display operates correctly at supported resolutions up to 3840 × 2160 @ 30 Hz.

If the screen remains blank, verify cable seating, display input selection, monitor power state, and whether another known-good display cable or port produces output.

3. Network and gateway connectivity

Network validation is critical because the FactoryClient depends on reliable communication with the target FactoryBrain server.

  • Connect an RJ45 network cable to one of the two rear-panel Realtek Gigabit Ethernet ports.

  • Open Step 3 of the FDOS setup wizard.

  • Run the automatic connection tests to the target FactoryBrain Server IP.

  • Confirm that all required protocol checks return a status of OK.

Protocol check

Expected result

Purpose

ICMP 0/8

OK

Verifies basic IP reachability to the target server.

TCP/443

OK

Confirms secure application or service communication path.

TCP/452

OK

Confirms required application-specific connectivity.

If any flow check fails, such as TCP/452 status - NOT OK, verify local IP settings, subnet mask, default gateway, VLAN assignment, routing path, and firewall rules with local IT before continuing.

4. Wi-Fi and Bluetooth beacon signal range

If the unit relies on wireless features or beacon-based detection, confirm antenna installation and signal quality.

  • Ensure that both RP-SMA antennas are securely attached to the rear antenna connectors.

  • If signal reception is weak, confirm that the issue is not caused by enclosure placement, machine shielding, or cabinet mounting location.

  • Where needed, connect extended antennas with RP-SMA male connectors and re-test signal strength.

Weak beacon or wireless reception is often environmental rather than device-related. Metal cabinets, dense machinery, and recessed mounting locations can reduce effective range.

5. Input peripherals and on-screen keyboard

Operator usability depends on both hardware input devices and software keyboard behavior.

  • Connect a USB keyboard and mouse to the front or rear USB 3.0 ports.

  • Verify that pointer movement, clicking, and keyboard input respond normally.

  • In FDOS Step 4, test localization settings by selecting the correct keyboard layout such as QWERTY or AZERTY.

  • Click the OS top-bar keyboard icon and verify that the system On-Screen Keyboard (OSK) opens and enters text correctly.

  • If the unit is running Vision Client Launcher, select an input field and confirm that the application-level Ignition OSK opens as expected.

6. Application deployment

After core hardware and connectivity checks are complete, validate runtime installation and auto-launch behavior.

  • In Step 5 of the setup wizard, select and install the target runtime application.

  • Supported target applications include Vision Client Launcher and Perspective Workstation.

  • Verify that installation completes successfully and that an on-screen confirmation appears before finalizing setup.

  • Reboot the system.

  • After reboot, confirm that the selected application launches automatically into the industrial interface.

Successful deployment means the operator does not need to manually start the runtime after reboot. Auto-launch should take the user directly into the intended operational environment.

7. Network reconfiguration shortcut

The reconfiguration shortcut is useful when a deployed unit must be redirected to a different network or when setup needs to be reopened without a full rebuild.

  1. Power cycle the FactoryClient.

  2. Wait for the boot message Loading modules up... to appear.

  3. Using an external USB keyboard, press [CTRL] + [ALT] + [SHIFT] + [P] simultaneously.

  4. Verify that the reconfiguration GUI opens successfully.

If the shortcut does not trigger, confirm that the keyboard is recognized during boot, that the key sequence is pressed at the correct timing, and that the unit has progressed to the displayed boot message before input is attempted.

Troubleshooting by Symptom

Symptom

Likely causes

Recommended checks

Escalation path

Unit does not power on

Failed adapter, no upstream power, loose DC connector, hardware fault

Check outlet power, verify adapter rating, test compatible 9V–24V DC adapter, inspect connector fit, observe Power LED

Escalate to hardware support if known-good power input fails

No display output

Wrong input selected, bad cable, unsupported display path, monitor issue

Test HDMI 1, HDMI 2, and DP, confirm monitor input source, use a known-good cable and display

Escalate if no video appears on any tested output

ICMP or TCP checks fail

Incorrect IP settings, gateway issue, DNS or routing problem, firewall restrictions, wrong server IP

Review Step 3 results, verify addressing, subnet, gateway, cable link lights, firewall policy, and target server IP

Coordinate with local IT or network team

Weak wireless or beacon reception

Antennas missing, poor antenna placement, RF shielding, long distance to source

Confirm both RP-SMA antennas are attached, test extended antennas, relocate if possible, compare signal strength after changes

Escalate to site engineering if installation environment limits signal quality

Keyboard or OSK does not respond

USB peripheral issue, incorrect layout, software input issue

Try another USB port, validate layout in Step 4, test top-bar OSK, test Ignition OSK in Vision Client Launcher

Escalate to application support if hardware input works but software keyboard fails

Application does not auto-launch after reboot

Deployment incomplete, wrong runtime selected, startup configuration issue

Repeat Step 5, confirm install success message, reboot again, verify target application selection

Escalate to software deployment support

Quick Validation Checklist

Use this checklist for a final pass before handing the system over to operations.

  • Power button lights up green and power LED behavior is normal
  • Display output renders correctly on the connected HDMI or DP monitor
  • Network link lights are active on the connected RJ45 port
  • FactoryBrain server connection checks for ICMP, TCP/443, and TCP/452 are confirmed OK
  • Wi-Fi and Bluetooth antennas are attached and signal reception is verified
  • USB keyboard, mouse, and system On-Screen Keyboard respond as expected
  • Target application launches properly after reboot
  • [CTRL] + [ALT] + [SHIFT] + [P] opens the reconfiguration wizard
Field notes and practical tips
  • Use known-good cables, displays, keyboards, and power adapters when isolating faults.

  • When troubleshooting network failures, confirm physical link first before reviewing software settings.

  • For wireless issues, installation environment can matter as much as device configuration.

  • Document which port, adapter, and display were used during testing so repeated failures can be compared consistently.

Last updated: