Programming a Color Display and Recovering a Bricked Display

Option 1 - Program Display from USB Flash Drive

• Use a USB Flash drive formatted with FAT32 file system
• Plug USB Flash drive with the file on it into displays USB Port
• Displays with Buttons - Press and hold button down then apply power (do not use lower left button)
• Glass Displays with only Touch Screen- Apply magnet to back of display as shown in displays installation instructions then apply power.
• If the USB Flash drive is not recognized see complete instructions linked below.
• Follow on-screen prompts to select and load the file.
• See Complete Instructions.

Option 2 - Program Display Directly from PowerVision over LAN (For developers Only)

• Hardware Needed
  • Plugable brand USB/Ethernet Adapters 10/100Mbps over USB 2.0 (Qty 2)
  • Ethernet Crossover Cable           

• • Complete kits are available with all USB/Ethernet adapters, Pwr/USB harnesses, and power supply. Go to  display page then model, on main website for kit part numbers.
  • Detailed LAN Information is available for troubleshooting purposes.
• Connect one USB/Ethernet adapter into the computer and the second one into the displays USB port with the Ethernet crossover cable in between the adapters. It must be a crossover cable.
• Powervision versions 2.9 and newer should auto connect.
• Verify display is connected in the PowerVision Configuration Tab, the display hardware type and IP address will be shown next to the "Communicate Over" selection when connected. 

• Select the Firmware Tool Button, Create the  Application or Configuration Installation file then  select "Load All', the file will then be transferred to the display. 

Option 3 - Powervision Toolkit

Complete instructions on using the Toolkit

Option 4 - Autoload - Programming Glass Displays with No Touch

• If the display has no Touch Screen and no buttons or the wrong touch tune the display can be automatically reprogrammed over USB with no user intervention.
• Rename the configuration file to display part number-autoload.pv1 with no spaces in between. Example: 78700622-autoload.pv1.
• Follow the standard procedure for programming a display from a USB Flash drive.
• As soon as display boots up and sees the autoload file it will install it with no further user input. 
• These displays can also be programmed directly from Powervision using the LAN connection.

Recovering a Bricked Display/Black Screen

These instructions only apply to displays that become inoperative after attempting to install new software. Displays that have become bricked to to a hardware issue cannot be recovered.

PV500, PV700, PV780B, PV1100, and PV1200 displays - Boot load from USB Method.

If the programming operation fails for whatever reason on a M2/G1e display as listed above, corrupting the bootloader, the screen will remain blank when attempting to access the bootloader. To recover the display follow these steps.

• Copy one of the bootloader files included below onto a USB Flash drive along with your configuration file
• Follow the standard process of programming a display from USB by using a magnet to boot to the loader on power up.
• The screen will remain blank  while the bootloader file will be read off of USB and transferred to the displays RAM memory after which the bootloader screen will appear.
• This process may take a few minutes due to the size of the file.
• Once the bootloader screen appears you can select your configuration file and install it as normal.
• If the first bootloader file selected does not work repeat the process with the other bootloader file.
• Note- do not rename these bootloader files and verify Windows did not append a (1) to the file name.

Bootloader 4.748     

Bootloader

Bootloader for PV500 & P70

Note: If the wrong file has been installed on a display corrupting the touch screen see Autoload.

PV450, PV485, and PV780 Displays

For this family of display if the bootloader does no appear when you press and hold a button down while applying power then the display must be returned to Enovation Controls to be recovered.

Error Codes

If there is an issue during the download process one of the following error codes will be generated.

• Unit gets stuck indefinitely loading the file – possibly illegal characters in the file name () or spaces or file is corrupted. See ! – 0 error code which are similar.
• ! - 0 - cannot recognize the file, may have (x) added to the extension; .tar(1).gz instead of .tar.gz , (1).gcibin, or file is corrupted. Check for illegal characters in file name – spaces or ().
• 300 – Password flag read error
• 301 – Invalid file: password flag, wrong file type for display, PV780-.gcibin vs PV780B-.pv1), possibly out of memory from large data log files. On M2 Platforms before loading a .pv2 file install the PV2 Support Upgrade.pv1 file.
• 302 – Security error: Unsecured file on a secured unit
• 303 – Part Number Match failed
• 304 – Corrupted tar file
• 305 – Load for different display type (.tar)
• 306 – Load for different display type (.gciBin)
• 307 – Unknown file extension (check for spaces in file name or illegal characters)
• 308 – Not a post ECC corrected load
• 309 – Password incorrect
• 401 – Corrupted tar file
• 402 – Unknown hardware family
• 403 – Corrupted load file or Missing Part Number
• 404 – Not a post ECC corrected load or Missing Serial Number
• 405 – Attempt to Downgrade the BootLoader, Attempt Rejected
• 406 – eMMC Downgrade Error – Config needs to be built in newer version of PowerVision
• 501 – Factory Reset Error