Support Files Upgrade using FTP

Procedures

This document covers the procedures required for upgrading of support files (when required) for new firmware version upgrades of all Microplex products (with flash PROMs), using the FTP protocol.

Not all Microplex products require Support Files, in addition for products that do, not all firmware version upgrades necessarily require an upgrade of the Support Files as well. To determine this you need to analyze the firmware versions directory (e.g. "beta", "current") for the product you are upgrading.

  • if there is no Support Files zip file found then they are not required at all.
  • if there is a Support Files zip file, but it's version has not changed from what it was for the previous firmware version then they do not need to be upgraded.
  • if there is a Support Files zip file, with a new version number from what it was for the previous firmware version then they need to be upgraded.

How to determine the Support Files zip file version number.

  • from the FTP site, see the "readme.txt" file located in each products firmware directory (e.g. "/ftp/support/m270clr/firmware/readme.txt").
  • from the Web site, the version number link is provided within each products distribution page in the Firmware Files table.

 

Upgrade Steps

Note;

For demonstration purposes only, the following assumptions and values will be used for the upgrade steps given below;

  • Throughout this document the Microplex product being upgraded is represented by <prod>, some examples are;
    • m270
    • m270clr
  • The new firmware version upgrade for <prod> which these support files are intended, has already been completed.
  • This <prod> uses the IP address "192.75.11.87".

Steps for upgrading of additional support files:

  1. Once the firmware portion of the upgrade is complete, if the <prod> you are upgrading requires additional support files, you will also need to get them from Microplex (see "Getting Upgrade Files" section), and place them on to a host server you can FTP to the <prod> from.
    • Support files are available as a single zip file (e.g. <prod>_fs.zip)
  2. Extract the contents of the support files zip file into a new (empty) directory on your host server.
    • support files may consist of any collection of the following;
      • html files
      • text files
      • image files (e.g. gif, jpeg)
      • utility programs
      • java applets
      • scripts
      • batch files
    • the structure of the support files zip file is as follows;
      • top level files.
        • these are the files which must be copied onto the <prod> via FTP.
        • usually just html, and gif files.
      • recursive directory files.
        • these files remain on the host.
        • they are organized into sub-directories which are created when extracting the zip file.
        • usually utility programs, java applets, and scripts provided for the benefit of the user.
  3. Open an FTP session with the <prod> from within the temporary host directory containing all the files you just extracted from the zip file.
    • ftp 192.75.11.87
  4. Log in as "root" and at the password prompt, just hit <enter> (or <return>) since there's no password by default.
  5. Change to the "http" directory in the <prod> once logged in.
    • cd http
  6. Change to binary mode by typing in "binary" at the FTP prompt.
  7. Do a directory listing to look for any proprietary files of yours stored within this "http" directory, for example;
    • You may have your own HTML file for displaying the captured images or maybe some GIF files for this HTML file.
    • If found, copy each file to the host directory where you began this FTP session from (this should be to the top level of the directory, not into one of the sub-directories created when extracting the zip file).
      • get filename
      • mget filenames
  8. Once you are sure there are no other proprietary files of yours that you want to keep, located within this "http" directory on the <prod>, then delete all of the remaining files.
    • mdel *.*
  9. Do a directory listing on "http" to ensure this directory is now empty.
  10. Now copy all of the files stored within the top level only of the host directory where you began this FTP session from to this "http" directory on the <prod>.
    • mput *.*
    • This is were those proprietary files of yours which you wanted to keep, get restored to the <prod> (see step 7).
  11. When complete, do another directory listing on "http" to ensure all files have been placed onto the <prod>.
  12. Close the FTP session when done.
  13. End of procedure.

 


Microplex Home Product Info Technical Support Contact Us