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

Troubleshoot initial controller connection

Troubleshoot a Controller 6000 that cannot establish its first Command Centre connection.

General controller points

When bringing a controller online to Command Centre:

⚠️ If the Server has more than one network interface, ensure that the Use different IP for Server field has the IP address for the network interface that is connecting to the controllers.


6000 Linux-specific points

If you are having trouble bringing on a new (to the site) Controller 6000, or upgrading an older 8.10 and earlier 6000 to Linux (firmware 8.20 and above) on a site, note the following:

  1. When the controller first comes online, ensure the software selected is left as None Selected until the controller has connected.

  2. The controller will restart a number of times. Don't change the software settings while it's upgrading.

  3. The upgrade process involves Command Centre upgrading the controller to v8.10 WinCE first, then upgrading to the Linux version.

⚠️ DIP Switch 2: During the upgrade process, DIP Switch 2 should remain ON if using the BootP addressing option.

  1. If the site has to assign IP addresses using the DIP Switch 1, 2, 3 procedure, once the controller has its IP address set, turn OFF all DIP Switches.

  2. Upgrading via USB is an alternative upgrade option. See the release notes for your version of Command Centre for the correct procedure.

For the full WinCE-to-Linux upgrade procedure (DHCP, Default IP, and BootP variants), see Upgrading WinCE to Linux.


🔗 Related

Last updated

Was this helpful?