Although very uncommon, it is possible for the controller to become unresponsive. One possible cause could be an infinite reset-cycle caused by a bug in the VCL program.  In such cases, it may not be possible to flash the controller using the regular process in CIT. 

For such cases, there is a mechanism that can block the OS for starting. When following the procedure below, the controller will stop it's boot process in the start manager. In the start manager it will report a solid yellow LED, and flashing using the standard steps in CIT is possible.

The following workflow was introduced in CIT 1.5.8. Earlier versions of CIT do not support inhibit recovery of FOS devices.

1. Remove all devices from the bus except for the unresponsive target device. Ensure the bus is still properly terminated before continuing.

2. In Launchpad, open or create a project containing a device with the target node ID. Do note that if the VCL bug responsible for the reset cycle has not been fixed, and the unresponsive device is updated with the same VCL, the controller may remain unresponsive after flashing.

3. Specify the correct target baud rate for the unresponsive device. AUTO will not work as there is nothing on the bus sending messages.

4. Connect launchpad to the bus.

5. Select the unresponsive node in Launchpad. It should indicate that the device is not connected by showing an open connector with a red dot.

6. From the Tools menu, select "Perform Inhibit Recovery on Selected Node".

    - Note that it may be necessary to cycle KSI at around the same time as the menu item is clicked to recover the device. The goal should be for the device to reach the start manager within 1 second of clicking the menu item.

    - Launchpad will present a message if the device is not detected after attempting to keep the device in the start manager.

    - It is not harmful to retry this process.

    - If the procedure fails consistently, verify the bus is properly terminated and well connected. Verify that you are connecting at the correct baud rate for the target controller.

    - It may be helpful to add a second device to the bus if the CAN dongle is entering an error state that prevents it from sending messages. If you suspect this is happening, a CAN monitor tool (such as PCAN-View) may be available for the CAN dongle and may show these error states in a status view.

7. In a moment, the connection state of the node should show a closed connector with a yellow dot, indicating that CIT has detected heartbeats from the target device. The LED indicator on the target device should also be displaying a solid yellow, indicating the device is in the start manager.

8. Open Pack & Flash. The affected node should indicate that its bus status is "Stopped" state. Click on the text in the "Bus Status" column and select "Preoperational".

9. Flash the device using the appropriate button in the "Flash" column.