Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Upgrading WinCE Controllers using Default IP

Upgrade a Windows CE Controller 6000 using its default IP address.

This is the common way to address the Controller 6000 where BootP is disabled or does not work (for example, where controller and server are on different subnets).

What gets cached

When configuring a Controller 6000 using initial default IP web config, basic information is cached, including:

  • Controller IP

  • Server IP

  • Subnet mask

  • Gateway

When DIP Switch 2 and 3 are turned OFF, this information is retained, which helps the Controller communicate with the server when connected to the server network.

⚠️ If DIP Switch 2 and 3 are NOT turned OFF, the controller address will need to be configured multiple times during the upgrade, as it drops its IP configuration on restart.


Process

The general process is:

Default IP upgrade process flow diagram
  1. Configure the controller using the default IP web config (192.168.1.199/config.). See Method 2 in Assigning a Controller an IP address.

  2. Set Controller IP, Server IP, Subnet, Gateway.

  3. Turn DIP Switch 2 and 3 OFF.

  4. Connect to the site network.

  5. The controller comes online to the server.

  6. The controller is upgraded to the correct firmware version for the site.


Retry note

⚠️ If the controller has failed its upgrade and you are repeating the process: ensure the controller's software version is selected to 'None Selected' before connecting the controller to the network again after addressing.

After selecting 'None Selected':

  • Either restart the FT Controller Service, or

  • Perform the overrides Disable Communication then Enable Communication.


🔗 Related

Last updated

Was this helpful?