Firmware Upgrade Files

Filenaming for firmware upgrade files will follow the format "<prod>_<typ>.<ext>.<cmp>", where;

• <prod> = product name, some examples are;
  • m202plus.
  • m205.
  • m270.
  • m270clr.
• <typ> = file type.
  • <blank> = firmware (default, the "_" delimeter is not used).
  • dl = downloader.
  • fs = collection of support files (e.g. html, gif, java applets, scripts, utility programs).
• <ext> = file extension.
  • bin = binary format file.
  • hex = binary (hexidecimal) format file.
• <cmp> = compression format used.
  • zip = WinZip format.

Some example filenames according to the given format;

• m202plus.hex.zip = firmware binary file for m202plus product.
• m205.hex.zip = firmware binary file for m205 product.
• m205_dl.hex.zip = downloader binary file for m205 product.
• m270clr_fs.zip = support files for m270clr product.

Software Upgrade Files

Filenaming for software upgrade files will follow the format "<soft>.<ext>", where;

• <soft> = software program name, some examples are;
  • ipassign.
  • mps.
  • waldo.
• <ext> = file extension
  • exe = Windows executable.
  • tar.Z = Unix tar (tape archive) in compress format.
  • zip = WinZip format.

Some example filenames according to the given format;

• waldo.exe = executable file for waldo program.
• mps.zip = zip file containing mps program files.
• npdist.tar.Z = compressed tar file for npdist program.

There are several ways to get the necessary upgrade files:

• Microplex FTP Site
• Microplex WEB Site
• Microplex Customer Service or Technical Support

Microplex FTP Site (ftp.microplex.com)

The FTP site is an "anonymous" site which is provided to support distributors and users of Microplex products.

Once you've entered the ftp root directory you'll need to change to the "support" directory.

• cd support

The "support" directory is broken down into product sub-directories, so you'll want to change to the one which matches the product type you're wanting to upgrade, ex;

• m204
• m202plus
• m270

These product sub-directories are further broken down into sub-directories, as follows;

• docs
  • contains all documents related to product (e.g. "user manuals", "release notes", "additional information").
  • the documents found here are available in PDF format, for viewing with Adobe Acrobat Reader v3.0 or later.
• firmware
  • contains all Firmware files for upgrading products firmware.
  • contains all Downloader files for upgrading products firmware.
  • contains all Support files for upgrading products firmware.
• software
  • contains links to all host software applicable for that product.
  • see readme.txt file in this directory for descriptions of software types.

In the products firmware/software directories (for software this will be once you've changed to the software type and then software program name directories), you will find the following;

• beta
  • version directory containing ALL files required for upgrading that products firmware to the latest beta release version.
• current
  • version directory containing ALL files required for upgrading that products firmware to the current production release version.
• previous
  • version directory containing ALL files required for downgrading that products firmware to the last production level release version prior to the current production release version.
• readme.txt
  • text file containing the version number information (e.g. v1.0.1) for each of the files found in the above version directories.

Firmware upgrade files vary according to product, for example not all products require Downloader files or Support files. Therefore if they are not found in a products firmware versions directory (as above), then they are not required.

Each of the firmware/software versions directories will contain a changes.txt file, which will provide a brief synopsis of the changes which took place since the last version release.

To "get" the required firmware upgrade files you simply change to the products firmware directory and then to the desired versions directory. For example, starting from the "/ftp/support" directory;

• cd m202plus
• cd firmware
• cd current
• bin (make sure to set to "binary" mode before downloading)
• get m202plus.hex.zip (upgrade file following file format defined above)

To "get" software upgrade files you simply change to the products software directory, then to the software type directory, then to the software program directory, and finally to the desired versions directory. For example, starting from the "/ftp/support" directory;

• cd m202plus
• cd software
• cd windows_sw
• cd mps
• cd current
• bin (make sure to set to "binary" mode before downloading)
• get mps.zip

Microplex WEB Site (http://www.microplex.com/)

Once you get to Microplex's home page, simply click on Technical Support to bring up the "Support Shack".

Click on Download Distribution Files to bring up links for all of the Microplex products. Here you will find links for each Microplex product model (e.g. M202Plus, M205, M270Clr etc.). Select the link of the product you wish to upgrade to access it's distribution files.

Once at the products distribution file page, you can download the necessary files by simply selecting the links which are available.

Microplex Customer Service or Technical Support

If you do not have access to the Internet, you can call or write to Microplex to order a diskette containing these upgrade files. Be sure to ask for Customer Service or Technical Support and have your product's serial number and current firmware version on hand along with your full shipping address.

1. product model
   • suitable for that particular file (e.g. "C205..." means this file can be used with M205 and M206 models only).
2. type
   • the type of file (e.g. "...DLTFTP..." says this is a download file rather than a firmware binary file).
3. version
   • the version of that file (e.g. "C205-DLTFTP 5.6 1643" is version 5.6).
4. checksum
   • the checksum for that file (e.g. "C205-ROM 5.6 14699" has a checksum of 14699).

These lines were incorporated into the upgrade files as a security measure to prevent users from mixing up files with product models and using incorrect versions with each other. They do nothing more than protect the unit from upgrade mishaps.