![Nautilus Be Strong Commercial R916 Assembly Manual Download Page 34](http://html2.mh-extra.com/html/nautilus/be-strong-commercial-r916/be-strong-commercial-r916_assembly-manual_3519601034.webp)
Console Firmware Upgrade to V21 Using FISP
Setting up the FISP for One or Two Device Programming
There are various versions of the FISP windows application in use, the earliest versions do not have as
many features as the later and the first step toward successful programming the FISPs will be to
access the vendor’s web site and download the most current version:
http://www.4d-electronics.co.nz/Business/productsbusiness/productdownloadbusiness.htm
The vendor has upgraded the FISP loading application to include a web based programming
application, this has required the use of new extensions to the program setup files currently known as
*.fsp. The new program will accept the former extension setup files but will save to a new *.4dx format.
The person programming the FISPs may need to change the program’s file locations if so, upon saving
this changed program, an extension change will be realized. This impacts application versions of
2.X.X.X that are pre 3.x.x.x.
The FISP may be setup to contain multiple programs, the limitation is that only programs of different
processor types should be loaded into one FISP. Such as the VSD and Console, not C51 and C52
console programs! Upon being connected to the Target system, the FISP queries the processor and
selects the first program in it’s list that matches the processor type to download.
The newest *fsp setup files will have the files needed called from the same directory as the *.fsp setup
file, if a directory is created for each version, all the files should be self-contained within it.
25
Appendix