Changed all document images from tiff format to png, as tiff not compatable...

Changed all document images from tiff format to png, as tiff not compatable with newer web browsers.


git-svn-id: https://redoubt.ligo-wa.caltech.edu/svn/advLigoRTS/trunk@3275 6dcd42c9-f523-4c6d-aada-af552506706e

doc/AdcUse.dox

@@ -18,7 +18,7 @@ There are 10 ADC parts located in the RCG I/O parts section of CDS_PARTS.mdl, AD
 The output of this block must be tied to one or more ADC Selector blocks to pick out and further connect individual ADC signal channels. As shown in the example, each ADC part actually contains a bus creator, with channels 0 thru 31 predefined. Individual channels are then selected via bus selector for further connection to user code components.
 
 \endverbatim
-///	\image html AdcPart.tiff "ADC example" width=50cm
+///	\image html AdcPart.png "ADC example" width=50cm
 ///	\verbatim
 4. EPICS Channels
 For each ADC, 32 EPICS channels will be auto-generated, of the form IFO:SYS-MADC#_EPICS_CH#
@@ -28,5 +28,5 @@ NOTE: All 32 for an IOP, but only those channels actually used (connected) in a
 5. Auto Generated MEDM Screens
 For each ADC, an MEDM screen is generated which contains the EPICS channels generated above.  The screen name is of the form MODELNAME_MONITOR_ADC#.adl. This screen is automatically linked to the higher level GDS_TP screen generated for this model.
 \endverbatim
-///	\image html AdcMedm.tiff "ADC AutoGen MEDM Screen" width=50cm
+///	\image html AdcMedm.png "ADC AutoGen MEDM Screen" width=50cm
 

doc/Contec6464DioUse.dox

@@ -21,7 +21,7 @@ Up to 4 Contec6464 modules per I/O chassis are supported by the RCG. As shown in
 
 
 \endverbatim
-///	\image html Contec6464DioPart.tiff "Contec 6464 Part Library" width=50cm
+///	\image html Contec6464DioPart.png "Contec 6464 Part Library" width=50cm
 ///	\verbatim
 4. EPICS Channels - None.
 \endverbatim

doc/DacUse.dox

@@ -19,8 +19,8 @@ There are 12 DAC parts located in the RCG I/O parts section of CDS_PARTS.mdl in
 	USER_MODEL: The standard user application model need only contain those DAC parts from which signals will be used eg if only signals from DAC2 are needed, then only DAC2 need be placed in the user model.
 
 \endverbatim
-///	\image html DacPart1.tiff "DAC Subsystems" width=50cm
-///	\image html DacPart2.tiff "DAC Parts" width=50cm
+///	\image html DacPart1.png "DAC Subsystems" width=50cm
+///	\image html DacPart2.png "DAC Parts" width=50cm
 ///	\verbatim
 4. EPICS Channels
 For each DAC, EPICS channels will be auto-generated, of the form IFO:FEC-DCUID_DAC_OUTPUT_CARDNUM_CHANNUM
@@ -29,5 +29,5 @@ For each DAC, EPICS channels will be auto-generated, of the form IFO:FEC-DCUID_D
 5. Auto Generated MEDM Screens
 For each DAC, an MEDM screen is generated which contains the EPICS channels generated above.  The screen name is of the form MODELNAME_DAC_MONITOR_CARD#.adl. This screen is automatically linked to the higher level GDS_TP screen generated for this model.
 \endverbatim
-///	\image html DacMedm.tiff "DAC AutoGen MEDM Screen" width=50cm
+///	\image html DacMedm.png "DAC AutoGen MEDM Screen" width=50cm
 

doc/GotoFrom.dox

@@ -13,4 +13,4 @@ These modules must be used in pairs, a single named GOTO with a matching FROM.
 These modules must appear on the same level of a model ie a GOTO from one subsystem level may not be connected to a matching FROM at a higher or lower level.
 
 \endverbatim
-/// 	\image html GotoFrom.tiff "GOTO FROM Example"
+/// 	\image html GotoFrom.png "GOTO FROM Example"