Plus FireFinder Software Programming Guide FireFinder Plus Software Programming guide TABLE OF CONTENTS Page No. 1. Introduction ............................................................................................................................... 1 2. Configmanager Plus Programming Tool ............................................................................... 1 3. Recommended Software Updating Steps .............................................................................. 2 4. Programming Application Software ....................................................................................... 3 5. 6. 7. 8. 9. 4.1 Transfer Wizard.............................................................................................................. 3 4.2 Terminal Window ........................................................................................................... 7 4.2.1 [In Boot mode] .................................................................................................... 7 4.2.2 [In Diagnostic mode – Standalone system] ....................................................... 7 4.2.3 [In Diagnostic mode – Network system] ............................................................ 7 Programming Boot-code Software ......................................................................................... 8 5.1 Transfer Wizard:............................................................................................................. 8 5.2 Terminal Window: .......................................................................................................... 9 5.2.1 [In Boot mode] .................................................................................................... 9 5.2.2 [In Diagnostic mode – Standalone system] ....................................................... 9 5.2.3 [In Diagnostic mode – Network system] ............................................................ 9 Programming NIC Software ................................................................................................... 10 6.1 Transfer Wizard:........................................................................................................... 10 6.2 Terminal Window: ........................................................................................................ 11 6.2.1 [In Boot mode] .................................................................................................. 11 6.2.2 [In Diagnostic mode – Standalone system] ..................................................... 11 6.2.3 [In Diagnostic mode – Network system] .......................................................... 11 Programming Slave CPU Software ....................................................................................... 12 7.1 Transfer Wizard:........................................................................................................... 12 7.2 Terminal Window: ........................................................................................................ 14 7.2.1 [In Diagnostic mode – Standalone system] ..................................................... 14 7.2.2 [In Diagnostic mode – Network system] .......................................................... 14 Programming Configuration.................................................................................................. 17 8.1 Transfer Wizard:........................................................................................................... 17 8.2 Terminal Window: ........................................................................................................ 21 8.2.1 [In Boot mode] .................................................................................................. 21 8.2.2 [In Diagnostic mode – Standalone system] ..................................................... 21 8.2.3 [In Diagnostic mode – Network system] .......................................................... 21 Programming EEPROM Setting ............................................................................................ 22 9.1 EEPROM Setting Window: .......................................................................................... 22 9.2 Terminal Window: ........................................................................................................ 23 9.2.1 [In Boot mode] .................................................................................................. 23 9.2.2 [In Diagnostic mode – Standalone system] ..................................................... 23 10. Event Logs (GUI)..................................................................................................................... 24 11. Revision History ..................................................................................................................... 25 FireFinder Plus Software Programming guide 1. Introduction This document provides the instructions to program the following: • FireFinder Plus Application Software • FireFinder Plus Boot Software • FireFinder Plus NIC Software • FireFinder Plus Slave Software • FireFinder Plus Configuration • FireFinder Plus EEPROM Configuration Setting 2. Configmanager Plus Programming Tool ConfigManagerPlus (CM+) should be used as the programming tool. To set up the commination port in CM+, select Options->Environment Settings->Communications”. A valid serial port to the FF+ FACP will be automatically established if it exists. Note: the baud rate (default communications speed) should be 115200. CM+ provides 2 tools that can be used for programming: a. The “Transfer Wizard” is a convenient tool accessed by selecting “Transfer->Send” b. The “Terminal Window” is an advanced programming option. Note: This option is not available by default. To enable access to the “Terminal Window” and “EEPROM Setting Window” Customer technical support should be consulted. 1 FireFinder Plus Software Programming guide 3. Recommended Software Updating Steps It is recommended that customers are advised to update software by using the “Transfer Wizard” as access to the terminal window is no longer provided in the Config tool by default. The Transfer Wizard will automatically take into account whether the connected panel is a standalone panel or part of a network system. Where applicable the following steps should be followed in the order shown: 1. Connect your Laptop to the FireFinder Plus CIE and establish communications using your current version of CM+. 2. Receive the existing panel configuration file and save it. This is done by selecting Transfer > Receive > Configuration and Save. A XXXX.dat file will be stored in your chosen directory (replace XXXX with relevant and meaningful name). 3. Install the latest version of CM+. 4. Using the Transfer Wizard send the latest Application software to the CIE (Refer to section 4 for details). Note: sending application around a 28 node network takes about 13 minutes. 5. Using the Transfer Wizard send the latest Bootcode to the CIE (Refer to section 5 for details). Note: sending bootcode around a 28 node network takes about 4 minutes 6. Using the Transfer Wizard send the latest NIC software to the CIE (Refer to section 6 for details). Note: sending NIC software around a 28 node network takes about 4 minutes 7. Using the Transfer Wizard send the latest Slave software to the CIE (Refer to section 7 for details). Note: Transfer wizard is only applicable with CM+ versions greater than V2.4.0.15. Earlier versions must use the terminal window option. Sending slave software around a 28 node network with 60 Slaves takes about 15 minutes 8. Using the latest CM+ convert the XXXX.dat file that was saved in step 2 above. Select Tools > Convert file from FireFinder Plus system 9. Verify the converted project and check/fix warnings and any errors. Select Tools > Verify Project Note: New versions of CM+ may indicate Warnings or Errors that were not present in earlier versions. These are outcomes of ongoing improvements to the product. 10. Compile and Save the project using the latest CM+. It is recommended that you save the project files using a different name than the one you used in step 2. 11. Send the new compiled config to the CIE using the transfer wizard 2 FireFinder Plus Software Programming guide 4. Programming Application Software 4.1 Transfer Wizard From the main menu, select TransferSendApplication Software. Once the option is selected, the Transfer Wizard will commence the automatic update of the application software - see the following screen captures (note that these captures are based on a 5 panel configuration). It will first determine the status of the system ie is it a single panel or network. A prompt will then be displayed for the user to select the application software file. 3 FireFinder Plus Software Programming guide The application software is first downloaded to the panel in question. When the local download is completed, the application software is then stored into the FLASH of the panel in question. 4 FireFinder Plus Software Programming guide Once the application is successfully stored locally, the network file transfer will start. Each panel will program the application software into its FLASH once the network file transfer is completed successfully. 5 FireFinder Plus Software Programming guide Once the network programming is successfully completed, all the panels will reboot. A check is performed to confirm the version of the application software. The “Status/Version#” indicates the application software version at each panel. The user shall check and verify all running application version numbers are as expected. If there are missing panels from the list, the user shall use <Retrieve Version#> button to refresh the version numbers list. Click the “Close” button to exit the Transfer Wizard. 6 FireFinder Plus Software Programming guide Terminal Window 4.2 The programming can be done either Boot or Diagnostic mode. 4.2.1 - [In Boot mode] Put the panel in Boot mode (Type BT) - Send the Application file App_Vx.x.x.BIN to the panel. - When the download and programming is completed, set the panel to Application Mode (Type GA) - The LCD on the panel should show the new Application Code (version number) when starting. 4.2.2 - [In Diagnostic mode – Standalone system] Put the panel in Diagnostic mode (Type GD) - Send the Application file App_Vx.x.x.BIN to the panel. - When the download and programming is completed, perform a warm boot (Type WB) - The LCD on the panel should show the new Application Code (version number) when starting. - Alternatively, type QV to interrogate the application version of the panel or use the menu system on the front panel (select “MENU->SYSTEM”) 4.2.3 - [In Diagnostic mode – Network system] Put the system in Diagnostic mode (Type NGD) Use the QP command to confirm the status of all the panels – ensure that all panels are in Diagnostic mode. Note that the prerequisite for the network commands to work correctly is that the system must be already networked. - Send the Application file _App_Vx.x.x.BIN to the panel. - When the download and programming is completed, perform a “network send application” (Type NSA). - When the “network send application” operation is completed, each of the receiving panels will transmit its status to the panel that initiates this command. Observe the messages at the terminal window. It should indicate that all the CPUs have successfully received the application software. - To program the application (into flash) around the network, type NPA. - When the “network program application” operation is completed, each of the receiving panels will transmit its status to the panel that initiates this command. Observe the messages at the terminal window. It should indicate that all the CPUs have successfully programmed the application software. - Now, type NWB to warm boot the network. - The LCD of all the panels should show the new Application Code (version number) when starting. - Alternatively, use the NIP command to confirm the application version of the system, use the menu system on front panel (select “MENU->SYSTEM”), or use the QV command to interrogate the application version of the panel in question. 7 FireFinder Plus Software Programming guide 5. Programming Boot-code Software 5.1 Transfer Wizard: The Boot-Code could be updated by Transfer Wizard tools. Select Transfer Send Boot Code File option and follow the instructions to update the code. At the end of the programming sequence, the user will be provided with the list of running boot code version numbers. The user shall check and verify all running Boot-Code version numbers are as expected. If there are missing panels from the list, the user shall use <Retrieve Version#> button to refresh the version numbers list. At the end <Close> the window and check the system is in normal state. 8 FireFinder Plus Software Programming guide 5.2 Terminal Window: The programming can be done either Boot or Diagnostic mode. 5.2.1 [In Boot mode] - Put the panel in Boot mode (Type BT) - Send the Boot file Boot_Vx.x.x.BIN to the panel. - When the download and programming is completed, the panel will reboot automatically. - The LCD on the panel should show the new Boot Code (version number) when starting. ▪ 5.2.2 [In Diagnostic mode – Standalone system] - Put the panel in Diagnostic mode (Type GD) - Send the Boot file Boot_Vx.x.x.BIN to the panel. - When the download and programming is completed, do a warm boot (Type WB) - The LCD on the panel should show the new Boot Code (version number) when starting. 5.2.3 [In Diagnostic mode – Network system] - Put the system in Diagnostic mode (Type NGD) - Use the QP command to confirm the status of all the panels – ensure that all panels are in Diagnostic mode. Note that the prerequisite for the network commands to work correctly is that the system must be already networked. - Send the Boot file Boot_Vx.x.x.BIN to the panel. - When the download and programming is completed, perform a “network send boot” (Type NSB). - When the “network send boot” operation is completed, each of the receiving panels will transmit its status to the panel that initiates this command. Observe the messages at the terminal window. It should indicate that all the CPUs have successfully received the boot software. - To program the boot software (into flash) around the network, type NPB. - When the “network program boot” operation is completed, each of the receiving panels will transmit its status to the panel that initiates this command. Observe the messages at the terminal window. It should indicate that all the CPUs have successfully programmed the boot software. - When the “network program boot” operation is completed, perform a network warm boot (Type NWB) - The LCD on the panels should show the new Boot Code (version number) when starting. - When System is in application mode, investigate the Boot Code software version numbers by typing NIB on the terminal 9 FireFinder Plus Software Programming guide 6. Programming NIC Software 6.1 Transfer Wizard: Select Transfer Send ‘Network Card File’ option and follow the instructions to update the code. After selecting the right binary (NIC_Vx.x.x.BIN ) file, the wizard sends it to the connected panel and then it gets sent around the network. At the end of the programming sequence, the user will be provided with the list of running version numbers. The user shall check and verify all running Network card (NIC) version numbers are as expected. If there are missing panels from the list, the user shall use <Retrieve Version#> button to refresh the version numbers list. At the end <Close> the window and check the system is in normal state. 10 FireFinder Plus Software Programming guide Terminal Window: 6.2 The programming of the NIC can only be done Diagnostic mode. 6.2.1 - [In Boot mode] Put the panel in Boot mode (Type BT) - Send the NIC Software file NIC_Vx.x.x.BIN to the panel. - When the download and programming is completed, set the panel to Diagnostic Mode (Type GD) so that the NIC can be programmed. - Refer to the programming section in the following. See “[In Diagnostic mode – Network system]”. 6.2.2 - [In Diagnostic mode – Standalone system] Put the panel in Diagnostic mode (Type GD) - Send the NIC Software file NIC_Vx.x.x.BIN to the panel. - Refer to the programming section in the following. See “[In Diagnostic mode – Network system]”. 6.2.3 - [In Diagnostic mode – Network system] Put the system in Diagnostic mode (Type NGD) Use the QP command to confirm the status of all the panels – ensure that all panels are in Diagnostic mode. Note that the prerequisite for the network commands to work correctly is that the system must be already networked. - Send the NIC Software file NIC_Vx.x.x.BIN to the panel. - When the download is completed, perform a ‘network send nic’ (Type NSN). - When the “network send nic” operation is completed, each of the receiving panels will transmit its status to the panel that initiates this command. Observe the messages at the terminal window. It should indicate that all the CPUs have successfully received the NIC software. - To program the NIC software (into flash) around the network, type NPN. - When the “network program nic” operation is completed, each of the receiving panels will transmit its status to the panel that initiates this command. Observe the messages at the terminal window. It should indicate that all the CPUs have successfully programmed the NIC software. - Note that all the NICs will reboot automatically after the programming operation. - Use the QP command to confirm the status of all the panels and NICs. This is to ensure that the NICs have successfully restarted after the reprogramming. - When the network is back to normal, type NGA to enter Application mode. - Once the system is normal, use the menu system (MENU-STATUS-NETWORK) to verify that the NIC software version numbers are correct. 11 FireFinder Plus Software Programming guide 7. Programming Slave CPU Software 7.1 Transfer Wizard: This is only applicable when using CM+ version V2.4.0.15 or newer. Any version older than this the slave programming will need to be done by using the Terminal Window method. Select Transfer Send “Slave Module File” option and follow the instructions to update the code. Select and load the Slave CPU file 86SCB_APP_Vx.x.x.BIN Select <Program All> to update all existing Slave Modules in the system. 12 FireFinder Plus Software Programming guide The wizard tool will attempt to program the local panel’s Slave Modules first. (This will take about 3 Minutes) Then the wizard tool will attempt to program the remote panels’ Slave Modules. (This will take about 4 Minutes) The user will be informed to check the programmed Slave Modules’ version numbers. If there was any module whose version number did not match, then the user can individually select and program that module by using using the <Program Selected> button. Additionally the user could select and program all modules on any specific node, by selecting the respective node number, if needed. By closing the programming window the system will switch to application mode. 13 FireFinder Plus Software Programming guide Terminal Window: 7.2 7.2.1 - [In Diagnostic mode – Standalone system] Put the system in Diagnostic mode (Type GD) - Send the Slave CPU file SCB_APP_Vx.x.x.BIN to the panel (if it has not been done). - Type ‘ps 8’ to program all slaves and it will take about 3 minutes. When the slaves are programmed, the panel will state the following messages on the Terminal Window: FINISHED *** SLAVE REPROG: Completed *** - Alternatively, each slave can be individually programmed and each programming will take about 2 minutes. • Type ‘ps 0’ to program the first slave CPU. It will take about 3 minutes. When the slave CPU is programmed, the panel will indicate the following messages on the Terminal Window: “FINISHED” “*** SLAVE REPROG: Completed ***” • If fitted, repeat for slave 2 by typing ‘ps 1’ • If fitted, repeat for slave 3 by typing ‘ps 2’ • If fitted, repeat for slave 4 by typing ‘ps 3’ • If fitted, repeat for slave 5 by typing ‘ps 4’ • If fitted, repeat for slave 6 by typing ‘ps 5’ • If fitted, repeat for slave 7 by typing ‘ps 6’ • If fitted, repeat for slave 8 by typing ‘ps 7’ - Type GA to enter Application mode. - Once the panel is normal, use the menu system (MENU-STATUS-MODULE-SLAVE-MODULE) to verify that all of the slave CPU version numbers are correct. - Alternatively, use the NIM command to display the slave CPU software version information on the Terminal Window. 7.2.2 - [In Diagnostic mode – Network system] Put the system in Diagnostic mode (Type NGD) Use the QP command to confirm the status of all the panels – ensure that all panels are in Diagnostic mode. Note that the prerequisite for the network commands to work correctly is that the system must be already networked. - Send the Slave CPU file SCB_APP_Vx.x.x.BIN to the panel (if it has not been done). - When the download and programming is completed, the terminal should indicate “slave software saved”. - Perform “network send slave software” (Type NSS) to send the file around the network. - When the “network send slave software” operation is completed, each of the receiving panels will transmit its status to the panel that initiates this command. Observe the messages at the Terminal Window. It should indicate that all the CPUs have successfully received the file. 14 FireFinder Plus Software Programming guide - Type ‘ps8’ to program local panel slaves and it will take about 3 minutes. When the slaves are programmed, the panel will state the following messages on the Terminal Window: FINISHED *** SLAVE REPROG: Completed *** - Alternatively, each slave can be individually programmed and each programming will take about 3 minutes. • Type ‘ps 0’ to program the first slave CPU. It will take about 3 minutes. When the slave CPU is programmed, the panel will indicate the following messages on the Terminal Window: “FINISHED” “*** SLAVE REPROG: Completed ***” • If fitted, repeat for slave 2 by typing ‘ps 1’ • If fitted, repeat for slave 3 by typing ‘ps 2’ • If fitted, repeat for slave 4 by typing ‘ps 3’ • If fitted, repeat for slave 5 by typing ‘ps 4’ • If fitted, repeat for slave 6 by typing ‘ps 5’ • If fitted, repeat for slave 7 by typing ‘ps 6’ • If fitted, repeat for slave 8 by typing ‘ps 7’ - To program the remote slave CPUs (into slave’s flash), type ‘npsa’. - Each remote panel will take about 3 minutes and each remote panel will transmit its status to the panel (sender) when the programming process is started. The following message should be displayed on the Terminal Window (note that “X, Y, Z” refer to the node addresses): node X slaves programming started node Y slaves programming started node Z slaves programming started - When the remote slaves CPUs have completed the programming, the remote panels will transmit its status around the network and the following messages should be displayed on the Terminal Window (note that “X, Y, Z” refer to the node addresses): node X slaves programming completed node Y slaves programming completed node Z slaves programming completed - Once all remote slave CPUs are programmed, perform a local slave CPU program. Please refer to the previous “[In Diagnostic mode – Standalone system]” for the instructions. - Type NGA to enter Application mode for the network system. - Once the panel is normal, type NIM (network inspect module) command to display all the slave CPU software version information on the Terminal Window. - Alternatively, ▪ Each remote panel’s slave modules can be programmed all at once and each programming will take about 3 minutes. Type ‘nps Node# 8’. (e.g. ‘nps 10 8’ to program all slave modules on node 10) 15 FireFinder Plus Software Programming guide ▪ Each remote panel’s slave module can be programmed individually and each programming will take about 3 minutes. Type ‘nps Node# Module#’. (e.g. ‘nps 10 0’ to program module 1 on node 10, ‘nps 10 1’ to program module 2 on node 10 and so on.) 16 FireFinder Plus Software Programming guide 8. Programming Configuration 8.1 Transfer Wizard: From the main menu, select TransferSendCurrent Project or select TransferSendSaved Project. Note that the “Saved Project” option allows the user to select from an existing DAT configuration. Once the option is selected, the Transfer Wizard will commence the automatic update of the configuration see the following screen captures (note that these captures are based on a 5 panel configuration). It will first determine the status of the system. If “Saved Project” is selected previously, a prompt will then be displayed for the user to select the configuration file. 17 FireFinder Plus Software Programming guide When the local download is completed, the configuration is then stored into the FLASH of the panel in question. Once the configuration is successfully stored locally, the network file transfer will start. 18 FireFinder Plus Software Programming guide Each panel will program the configuration into its FLASH once the network file transfer is completed successfully. A check is performed to confirm the version of the Configuration file. The “Status/Version#” indicates the configuration version (major version / minor version) at each panel. Once the network programming is successfully completed, all the panels will reboot. 19 FireFinder Plus Software Programming guide Click the “Close” button to exit the Transfer Wizard. 20 FireFinder Plus Software Programming guide Terminal Window: 8.2 The programming can be done either in Boot mode or Diagnostic mode. 8.2.1 - [In Boot mode] Put the panel in Boot mode (Type BT) - Send the Configuration file XXX.DAT to the panel. - When the download and programming is completed, set the panel to Application Mode (Type GA) - To confirm the configuration, use the menu system on the front panel (select “MENU->SYSTEM”) and check that the configuration details (date time, major and minor number) matches the record in the DAT file – refer to the first record on the DAT file and the line (on the LCD) that starts with “CONFIG: …”. 8.2.2 - [In Diagnostic mode – Standalone system] Put the panel in Diagnostic mode (Type GD) - Send the Configuration file XXX.DAT to the panel. - When the download and programming is completed, set the panel to Application Mode (Type GA) - To confirm the configuration, use the menu system on the front panel (select “MENU->SYSTEM”) and check that the configuration details (date time, major and minor number) matches the record in the DAT file – refer to the first record on the DAT file and the line (on the LCD) that starts with “CONFIG: …”. 8.2.3 - [In Diagnostic mode – Network system] Put the system in Diagnostic mode (Type NGD) Use the QP command to confirm the status of all the panels – ensure that all panels are in Diagnostic mode. Note that the prerequisite for the network commands to work correctly is that the system must be already networked. - Send the Configuration file XXX.DAT to the panel. - When the download and programming is completed, perform a “network send configuration” (Type NSC). - When the “network send configuration” operation is completed, each of the receiving panels will transmit its status to the panel that initiates this command. Observe the messages at the terminal window. It should indicate that all the CPUs have successfully received the configuration. - To program the configuration (into flash) around the network, type NPC. - When the “network program configuration” operation is completed, each of the receiving panels will transmit its status to the panel that initiates this command. Observe the messages at the terminal window. It should indicate that all the CPUs have successfully programmed the configuration. - To confirm the configuration, use the NIC command. Each panel will transmit its configuration details (checksum and date time information) to the panel initiating this command. - Alternatively, set the system into Application mode by typing the NGA command and then use the menu system confirm the configuration at each panel (on the front panel, select “MENU->SYSTEM”) 21 FireFinder Plus Software Programming guide 9. Programming EEPROM Setting EEprom settings can not be programmed over a network. If applicable each panel will individually need to be connected to directly to change any EEprom settings. 9.1 EEPROM Setting Window: From the main menu, select Transfer->EEPROM Setting Window. Once the option is selected, the EEPROM setting Window will be displayed. It will attempt to retrieve the existing EEPROM settings from the FACP. Note that this Window does not include all the EEPROM settings – it only provides the settings for the important/mandatory fields. Select “Open File” to read from an existing EEPROM file that is saved on the PC. Select “Load” to retrieve the EEPROM settings from the FACP. Select “Save File” to download the current EEPROM settings to the FACP. A “Save File As …” Window will be displayed: - If the new settings are required to be saved on the PC as a file (e.g. backup), provide a valid filename and then select the “save” button. - If the new settings are not required to be saved on the PC, click the “cancel” button. - Once the “save” or “cancel” button is clicked, the FACP will automatically be set to “boot mode” and the new EEPROM setting will be saved and applied at the FACP. 22 FireFinder Plus Software Programming guide Select “Reboot Panel & Exit” to reboot the FACP and exit the wizard. Terminal Window: 9.2 9.2.1 - - 9.2.2 - - [In Boot mode] Put the panel in Boot mode (Type BT) Send the EEPROM configuration file EEPROM_FFPLUS_xxx.BIN to the panel: ▪ EN54 = EEPROM_FFPLUS_EN54 ▪ AS7240 = EEPROM_FFPLUS_AS7240 ▪ CP10 = EEPROM_FFPLUS_CP10 The download process is quick and should take < 3 seconds When the download and programming is completed, restart the panel (Type WB) to apply the new setting [In Diagnostic mode – Standalone system] Put the panel in Diagnostic mode (Type GD) Send the EEPROM configuration file EEPROM_FFPLUS_xxx.BIN to the panel: ▪ EN54 = EEPROM_FFPLUS_EN54 ▪ AS7240 = EEPROM_FFPLUS_AS7240 ▪ CP10 = EEPROM_FFPLUS_CP10 The download process is quick and should take < 3 seconds When the download and programming is completed, restart the panel (Type WB) to apply the new setting 23 FireFinder Plus Software Programming guide 10. Event Logs (GUI) Event logs can be retrieved and presented graphically via CM+ >= V2.0.0.0. From the main menu, select Transfer->Event Logs. Note that the retrieval of the log data may take a while as it depends on the number of records stored at the FACP. Select “Refresh” to retrieve all the logs again. Select “Cancel” to an existing “Refresh” request. Select “Save” to save the log data to a file. Select “Print” to print the log data. Select “X” icon to exit this Window. 24 11. Revision History Date Author Revision Description 25-06-2013 Lex Tan 1.0 Created 02-10-2013 Lex Tan 2.0 Updated to include the programming of the EEPROM configuration setting. 11-11-2014 Lex Tan 3.0 Updated to include the programming of configuration file, application software via the Transfer Wizard, the EEPROM Programming Window and the Event Log Window 09-02-2015 Lex Tan 4.0 Updated to include the programming of slave cpu software around the network, and Updated the EEPROM Setting section to include the new option (“Periodic Fault Buzzer Sound”) 26-02-2015 Lex Tan 5.0 Updated the EEPROM Setting section to include the updated button labels 08-02-2016 Lex Tan 6.0 Update the Slave CPU software section to indicate that the programming should be done in diagnostic mode 18-07-2017 Khalil Tawosli 7.0 1- Added new transfer wizard instructions for Slave CPU, NIC, and Boot-Code tools 2- updated Slave CPU programming procedures for terminal window tool 25/10/2017 A. Skellham 8.0 Reformatted and added programming steps UNCONTROLLED DOCUMENT NOTE: Due to AMPAC’s commitment to continuous improvement specifications may change without notice.