文件列表:

VISSIM\ACMOTOR.VSM (14850, 1993-05-26)
VISSIM\ANALYZE.DLL (53216, 1993-05-26)
VISSIM\ANL_PLL.VSM (8800, 1993-05-26)
VISSIM\AXEL.VSM (504, 1996-05-02)
VISSIM\AXEL1.VSM (616, 1996-05-02)
VISSIM\BIOREACT.VSM (2927, 1993-02-19)
VISSIM\BOUNCE.VSM (2254, 1993-05-26)
VISSIM\BWORTH.VSM (2190, 1993-05-26)
VISSIM\CHKLIST.MS (108, 1996-09-06)
VISSIM\CONTROL.VSM (5685, 1993-05-26)
VISSIM\CORNU.VSM (744, 1993-02-19)
VISSIM\DCMOTOR.DAT (3808, 1990-04-23)
VISSIM\DCMOTOR.VSM (1400, 1993-02-19)
VISSIM\DIAGRAM1.VSM (3480, 1998-05-15)
VISSIM\DIG_PLL.VSM (11691, 1993-02-19)
VISSIM\DIGCTRL.BMP (5302, 1993-04-19)
VISSIM\DOOR12.BMP (17702, 1993-04-19)
VISSIM\DOORSYS.VSM (13120, 1993-05-26)
VISSIM\ENCODR12.BMP (3198, 1993-04-19)
VISSIM\F_SERIES.VSM (35166, 1993-05-26)
VISSIM\FIL_RESP.VSM (2675, 1993-02-22)
VISSIM\FLEXLOAD.VSM (10246, 1993-02-22)
VISSIM\FW_RECT.VSM (5271, 1993-05-10)
VISSIM\GASMIX.VSM (7012, 1993-05-26)
VISSIM\GEARING.BMP (5558, 1993-04-19)
VISSIM\I2T.MAP (169, 1990-05-09)
VISSIM\IC_FIND.VSM (3328, 1993-02-22)
VISSIM\IMP_RESP.VSM (8561, 1993-02-22)
VISSIM\KUGLER.VSM (1681, 1993-02-22)
VISSIM\LAGCMP.VSM (2171, 1993-02-22)
VISSIM\LEIA.ME (64, 1996-04-08)
VISSIM\LIMCYCLE.VSM (1697, 1993-02-22)
VISSIM\LIMITINT.VSM (1106, 1993-02-22)
VISSIM\LORENZ.VSM (3188, 1993-02-22)
VISSIM\MANUFACT.VSM (7241, 1993-02-22)
VISSIM\METER.VSM (819, 1993-02-22)
VISSIM\MOTOR.BMP (4990, 1993-04-19)
VISSIM\NEUROWIN.DLL (5920, 1993-01-22)
VISSIM\PHYSBE.VSM (30398, 1992-09-24)
VISSIM\PLL_CTRL.VSM (10839, 1993-02-22)
... ...

VisSim Readme File Thank you for purchasing VisSim. We have done our best to ensure that VisSim runs quickly and reliably. If you run across problems or have suggestions about how we might improve VisSim, please fill out the Bug report form at the end of this document. If you encounter problems during installation, please call our tech support line at 508-392-0100, or FAX us at 508-692- 3102, or send us email via internet at "tech@vissol.com". If you want to upgrade VisSim, or want to know about the latest products from Visual Solutions, call our direct sales line at 508-392-0100. This document is formatted as an ASCII text file. It can be opened using many word processors and reformatted, if desired. If you have purchased a VisSim add-on, for example, VisSim/Analyze or VisSim/RT, an additional README__.TXT file exists containing information specific to that product. See For information ----- -------------------- READMEAZ.TXT About VisSim/Analyze READMENN.TXT About VisSim/Neural-Net READMERT.TXT About VisSim/RT This README.TXT file is organized in the following way: 1.0 IMPORTANT INSTALLATION INFORMATION 2.0 DOCUMENTATION UPDATES 3.0 TROUBLESHOOTING 4.0 CREATING DLL FUNCTIONS 5.0 BUG AND SUGGESTION REPORT ***************************************************** 1. IMPORTANT INSTALLATION INFORMATION ***************************************************** The following is the most up-to-date list of files currently shipping with VisSim. This list of files supersedes the files listed in Appendixes E and F of the VisSim User's Guide. Note that many of the block diagram files listed below were shipped with previous versions of VisSim. If you do not want Install to overwrite the block diagram files, activate "WARN ME BEFORE OVERWRITING" in the Install dialog box. \VISSIM Directory ACMOTOR.VSM ANL_PLL.VSM BIOREACT.VSM BOUNCE.VSM BWORTH.VSM CONTROL.VSM CORNU.VSM DCMOTOR.DAT DCMOTOR.VSM DIG_PLL.VSM DIGCTRL.BMP DOOR12.BMP DOORSYS.VSM ENCODR12.BMP F_SERIES.VSM FIL_RESP.VSM FLEXLOAD.VSM FW_RECT.VSM GASMIX.VSM GEARING.BMP I2T.MAP IC_FIND.VSM IMP_RESP.VSM KUGLER.VSM LAGCMP.VSM LIMCYCLE.VSM LIMITINT.VSM LORENZ.VSM MANUFACT.VSM METER.VSM MOTOR.BMP PHYSBE.VSM PLL_CTRL.VSM PP.MAP PSWEEP.VSM PWM_EX.VSM RAYLEIGH.VSM RL_DES.VSM RMS_EX.VSM ROCKET.VSM ROOMCTRL.VSM ROOTS.VSM ROWER.VSM SM_1PH.VSM SOMBRERO.VSM SPRING.VSM STUKBLOK.VSM THE2GAIN.MAP THETA2X.MAP VALVE.VSM VTCDELAY.VSM XCL.DAT \VISSIM\CONTROLS Subdirectory DERIV_A.BMP DERIV_A.VSM DERIV_D.BMP DERIV_D.VSM DIFFR.BMP DIFFR.VSM HYST_CTL.BMP HYST_CTL.VSM HYSTER.BMP HYSTER.VSM LAG.BMP LAG.VSM LEAD.BMP LEAD.VSM P_CTL.BMP P_CTL.VSM PI_CTL.BMP PI_CTL.VSM PID_CTL.BMP PID_CTL.VSM RATE_LIM.BMP RATE_LIM.VSM RFB_CTL.BMP RFB_CTL.VSM TF1_CONT.BMP TF1_CONT.VSM TF1_DISC.BMP TF1_DISC.VSM TF2_CONT.BMP TF2_CONT.VSM TF2_DISC.BMP TF2_DISC.VSM TRIM_INT.BMP TRIM_INT.VSM ZINTBR.BMP ZINTBR.VSM ZINTFR.BMP ZINTFR.VSM ZINTTR.BMP ZINTTR.VSM \VISSIM\ELECMECH Subdirectory A2D.BMP A2D.VSM ACDQ_MOT.BMP ACDQ_MOT.VSM D2A.BMP D2A.VSM DC_MOT.BMP DC_MOT.VSM ENCODER.BMP ENCODER.VSM MUX4.BMP MUX4.VSM PWM.BMP PWM.VSM \VISSIM\FILTERS Subdirectory BANDPASS.VSM BWRTH_1.VSM BWRTH_2.VSM BWRTH_3.VSM BWRTH_4.VSM BWRTH_5.VSM BWRTH_6.VSM CHEB2_3.VSM CHEB2_3A.VSM CHEB2_5.VSM \VISSIM\SIGGEN Subdirectory 3_PHASE.BMP 3_PHASE.VSM CAL_TIME.BMP CAL_TIME.VSM DT.BMP DT.VSM SAWTOOTH.BMP SAWTOOTH.VSM SQR_WAVE.BMP SQR_WAVE.VSM TRIANGLE.BMP TRIANGLE.VSM \VISSIM\TOOLS Subdirectory AVG_VAL.BMP AVG_VAL.VSM COUNTER.BMP COUNTER.VSM MAG_PHAS.BMP MAG_PHAS.VSM MAX_VAL.BMP MAX_VAL.VSM MIN_VAL.BMP MIN_VAL.VSM PERIOD.BMP PERIOD.VSM PH_DIFF.BMP PH_DIFF.VSM RMS.BMP RMS.VSM SWEEP.VSM VEC_ANLY.BMP VEC_ANLY.VSM \VISSIM\TUTLIB Subdirectory IWZ.VSM LME.VSM LMI.VSM ZAC.VSM ZCC.VSM ZDF.VSM ZDL.VSM ZDT.VSM ZGC.VSM ZGN.VSM ZIR.VSM ZSE.VSM ZSP.VSM ZUD.VSM \VISSIM\VSDK Subdirectory COMBO.DEF COMBO.DLL COMBO.MAK COMBODLL.VSM EX1.FOR EX1.VSM FUSER.DEF FUSER.DLL FUSER.FOR FUSER.MAK FUSER.VSM HELLO.C HELLO.DEF HELLO.DLL HELLO.MAK HELLO.RSP HELLO.VSM IMPSIM.LIB LIBENTRY.OBJ NNET.C NNET.DEF NNET.DLL NNET.MAK NNET.VSM TESTPDLL.PAS TESTPDLL.VSM VSUSER.H VTOOLS.DEF VTOOLS.DLL VTOOLS.MAK WINMEM.C WINMEM.H WPRINTF.C WPRINTF.H ***************************************************** 2. DOCUMENTATION UPDATES ***************************************************** PRINT COMMAND/PRINT TO FILE PARAMETER (p.80) Use the MS/DOS Copy command to print a file created with the Print to File parameter in the dialog box for the File menu's Print command. For example, suppose you activated the Print to File parameter and printed your block diagram to the file named OUTPUT in C:\VISSIM. To print OUTPUT on the printer connected to LPT1, type the following command at the MS/DOS prompt: COPY C:\VISSIM\OUTPUT LPT1 LIMIT BLOCK (p. 140, and Block Reference Table). The first line in the symbolic equation for the limit block is backwards. It should read: x(1) if lb <= x(1) <= ub PARABOLA BLOCK/TIME DELAY PARAMETER (p.152) The Time Delay parameter is an offset that is used in the calculation of a signal. For a constant-valued delay, wire the block into a unitDelay or timeDelay with an initial condition of the desired constant value. PLOT BLOCK/LABELING X AXIS ON XY PLOT (p.160) To label the x axis on an XY plot, call up the plot block dialog box and click on the Label Signals... button. Enter a label for each input signal and click on the OK button. Activate the XY Plot parameter and select the signal (1, 2, 3, or 4) for the x axis. PULSETRAIN BLOCK (p.163) In the paragraph that begins "You can add two input connector tabs..." replace the words "pulse width" with "time between pulses." The pulseTrain block generates unit pulses of one time step, separated by zeroes. You cannot control the duration of the pulse itself, you can only control the time between pulses. RAMP BLOCK/TIME DELAY PARAMETER (p.165) The Time Delay parameter is an offset that is used in the calculation of a signal. For a constant-valued delay, wire the block into a unitDelay or timeDelay with an initial condition of the desired constant value. SINUSOID BLOCK/TIME DELAY PARAMETER (p.172) The Time Delay parameter is an offset that is used in the calculation of a signal. For a constant-valued delay, wire the block into a unitDelay or timeDelay with an initial condition of the desired constant value. TRANSFERFUNCTION BLOCK (p.179) VisSim determines the order of the transfer function by the number of denominator coefficients entered. (An nth order transfer function will have n+1 coefficients.) VisSim supports transfer functions up to the 45th order; Personal VisSim supports transfer functions up to the 15th order. VISSIM-SUPPLIED FILES FOR CREATING DLL FUNCTIONS (p.196-197) The following files have been added to the VSDK subdirectory. A description of how to use these files to create DLL functions is contained in the section titled "CREATING DLL FUNCTIONS" later on in this file. COMBO.DEF COMBO.DLL COMBO. MAK COMBODLL.VSM EX1.FOR EX1.VSM FUSER.DLL FUSER.MAK HELLO.C HELLO.DEF HELLO.MAK HELLO.RSP HELLO.VSM NNET.DLL VTOOLS.DEF VTOOLS.DLL VTOOLS.MAK WINMEM.C WINMEM.H WPRINTF.C WPRINTF.H VISSIM DLL CALLING CONVENTIONS (p. 200-201) For each of the following functions, the arguments have been given as arrays of pointers. They should be changed to arrays of doubles, as shown below: Function Correct Format Parameter Init. voidDLLfunPI( double FAR param[]) Parameter Change char FAR * DLLfunPC( double FAR param[]) Simulation Start void DLLfunSS( double FAR param [], long FAR * runCount) Simulation End void DLLfunSE( double FAR param []) Time Step void DLLfun( double FAR param[], double FAR inSig[], double FAR outSig[]) ***************************************************** 3.0 TROUBLESHOOTING ***************************************************** YOU'RE SOLVING AN IMPLICIT SYSTEM AND YOUR EQUATIONS DIVERGE WHEN THEY SHOULD CONVERGE (p. 101, 232-234) 1) If you are solving for a set of roots that are equidistant from zero, such as the square root of 2, you must initialize the unknown to a value other than zero to force the equations to converge. 2) The Relaxation parameter for FP iteration also applies for Newton-Raphson iteration. To set the Relaxation parameter for Newton-Raphson iteration, activate FP and enter a positive number for the Relaxation; then click on the OK button to put the settings into effect. Re-invoke the dialog box for the Simulate menu's Change Parameters... command and activate Newton- Raphson. If your equations continue to diverge and you believe they shouldn't, choose a Relaxation value closer to 1, or increase the Max Iteration Count. YOUR FREQUENCY DOMAIN PLOT PRODUCES UNEXPECTED PEAKS (p. 155) Check the simulation step size in the dialog box for the Simulate menu's Change Parameters... command to verify that your sampling rate is adequate for obtaining accurate results. Then, based on the simulation step size and range, check the Max Plotted Points parameter in the dialog box for the plot block to verify that you are indeed plotting each time step. SOME OF THE DLLS I USED SUCCESSFULLY WITH VISSIM 1.1 GIVE ME AN APPLICATION ERROR WHEN I CALL THEM FROM VISSIM 1.2 (P. 20). The order of the arguments for the Time Step function has been changed. In VisSim 1.1, the order was: void DLLfun(double FAR inSig[], double FAR outSig[], double FAR param[]) In VisSim 1.2, the order is: void DLLfun(double FAR param[], double FAR inSig[], double FAR outSig[]) Also note that in the 1.2 version of the manual, the arguments for the Time Step function are given as arrays of pointers. They should be changed to arrays of doubles, as shown above. ***************************************************** 4.0 CREATING DLL FUNCTIONS ***************************************************** TABLE OF CONTENTS 1. Makefile Tutorial 2. Microsoft Fortran DLLs (fuser and vtools) 3. Microsoft C DLLs (nnet) 4. Combined DLLs (combo and nnet) 5. Borland C++ DLLs (hello) The VSDK development subdirectory includes sample C (nnet), Borland C++ (hello), FORTRAN (fuser,vtools) and Pascal (testpdll) userFunction blocks. Use the .def and .mak files as templates for your DLLs and edit them accordingly. The DLLs were compiled at Visual Solutions using these compilers: Microsoft C version 6.0 Microsoft Fortran version 5.1 Borland C++ version 2.0 You may generate a DLL with any compiler capable of creating a Windows DLL. Please note that this limitation is compiler- dependent, not VisSim-dependent. If you want to build custom dialog boxes, and your compiler does not ship with the Windows Resource Compiler rc.exe, then you'll also need to purchase the Windows SDK, available from Microsoft. To compile and link your demo DLL files, type "nmake" plus the filename or "nmk" plus the makefile name if you use Microsoft compilers. If you are unfamiliar with the make utility, read the makefile tutorial that follows. ***************************************************** 1. MAKEFILE TUTORIAL ------------------------------------ For those unfamiliar with "make", a brief tutorial... Make is a program build utility first developed at Bell Labs to run on the Unix system. It takes a program description file ("makefile" by default) and determines the least amount of work to do in order to build an up-to-date version of your program. It does this by comparing file dates of source files to object files and compiling any source files that are newer than their corresponding objects. It then compares the file dates of your programs with the dates of its constituent object files and will re- link your program if any objects are newer than your program. In this way, all rules for program build can be embodied in one file, and only the minimal actions necessary to build your program are done. Though "make" utilities available under the MS/DOS operating system are relatively faithful reproductions of their Unix ancestors, there is one maddening limitation of the DOS variety: DOS only allows 127 characters on a command line. You typically run into this limitation when you have long link commands with many object files. You will not run into this unless you add more file names for your user blocks. If you do, the first line of defense is to use short file names to try and squeeze the line in. Another approach is to use "lib" to create a small library of your additional objects and put the library in the object position on the link command line. The last resort is to use a "response" file which is documented in your compiler utilities programming guide. ***************************************************** 2. Microsoft Fortran DLLs ------------------------------------ The VISSIM\VSDK subdirectory contains files for building two Fortran DLLs: ========== VTOOLS.DLL ========== The vtools application uses these files: IMPSIM.LIB, LIBENTRY.OBJ, and VSUSER.H are VisSim- supplied files. EX1.FOR is a Fortran function. VTOOLS.DEF is the definition file for creating VTOOLS.DLL. VTOOLS.MAK is the makefile for creating VTOOLS.DLL. VTOOLS.DLL is the DLL file for EX1.FOR created by command-line compiling and linking: nmake vtools.mak EX1.VSM is the sample VisSim file for EX1.FOR ========= FUSER.DLL ========= The fuser application uses these files: IMPSIM.LIB, LIBENTRY.OBJ, and VSUSER.H are VisSim- supplied files. FUSER.FOR is a Fortran function. FUSER.DEF is the definition file for creating FUSER.DLL. FUSER.MAK is the makefile for creating FUSER.DLL. FUSER.DLL is the DLL file for FUSER.FOR created by command-line compiling and linking: nmake fuser.mak FUSER.VSM is the sample VisSim file for FUSER.FOR ***************************************************** 3. Microsoft C DLLs ------------------------------------ ======== NNET.DLL ======== The nnet application uses these files from the VISSIM\VSDK directory: IMPSIM.LIB, LIBENTRY.OBJ, and VSUSER.H are VisSim- supplied files. NNET.C is a C neural net function. NNET.DEF is the definition file for creating NNET.DLL. NNET.MAK is the makefile for creating NNET.DLL. NNET.DLL is the DLL file for NNET.C created by command- line compiling and linking: nmk nnet.mak NNET.VSM is the sample VisSim file for NNET.C ***************************************************** 4. Combined C and Fortran DLLs ------------------------------------ ====================== COMBO.DLL AND NNET.DLL ====================== The combo application uses these files from the VISSIM\VSDK directory: IMPSIM.LIB, LIBENTRY.OBJ, and VSUSER.H are VisSim- supplied files. EX1.FOR and FUSER.FOR are Fortran functions for COMBO.DLL. COMBO.DEF is the definition file for COMBO.DLL. NNET.C is a C neural net function. NNET.DEF is the definition file for creating NNET.DLL. COMBO.MAK is the makefile for creating COMBO.DLL and NNET.DLL. COMBO.DLL is the DLL file for EX1.FOR and FUSER.FOR. NNET.DLL is the DLL file for NNET.C. Both of these DLLs are created by command-line compiling and linking: nmk combo.mak COMBO.VSM is the sample VisSim file for EX1.FOR, FUSER.FOR, and NNET.VSM ***************************************************** 5. Borland C++ DLLs ------------------------------------ ========= HELLO.DLL ========= We would like to thank Orbital Research, Inc. for this application, developed for use with the Borland C++ 3.0 compiler. For users of Borland C++ 2.0, be sure to read the end of this section. The hello application uses these files from the VISSIM\VSDK subdirectory: IMPSIM.LIB and VSUSER.H are VisSim-supplied files. HELLO.C is a demonstration routine. WINMEM.H and WPRINTF.H are header files. WINMEM.C is a routine to dynamically allocate memory for Windows. WPRINTF.C is a debug message routine to create a dialog or message box. HELLO.RSP contains a list of all C source files. HELLO.DEF contains the definitions file for creating HELLO.DLL. HELLO.MAK contains the rule for creating DLL files and a procedure for automated generation of DLL files from a single source file or from multiple source files. HELLO.DLL is the DLL file for HELLO.C created by command- line compiling and linking: make -f hello.mak HELLO.VSM is the sample VisSim file for HELLO.C. --------For users of Borland C++ version 2.0------- Make the following changes: 1. Comment out line 63 of the HELLO.MAK file: LIBS=impsim import cw$(MODEL) mathw(MODEL) 2. Uncomment line *** of the HELLO.MAK file: LIBS=impsim import cwin$(MODEL) math$(MODEL) c$(MODEL) 3. To link, type: make -fhello.mak ***************************************************** 5.0 BUG AND SUGGESTION REPORT ***************************************************** VisSim Bug and Suggestion Form ------------------------------ How can we reach you? Name: _________________________________________________ Company: _________________________________________________ Address: _________________________________________________ _________________________________________________ _________________________________________________ Phone: ________________________ Fax: ________________________ E-mail: ________________________ What Visual Solutions products are you using? Product Version Serial number ________________________ _____________ ___________________ ________________________ _____________ ___________________ ________________________ _____________ ___________________ ________________________ _____________ ___________________ Tell us about your system: Meg RAM: ___________________ Processor: ___________________ Operating System: ___________________ Version: _________________ GUI: ___________________ Version: _________________ Co-processor: ___________________ Printer: ___________________ Printer Driver: ___________________ Version: _________________ Please describe your bug or suggestion: Severity(Circle one): Showstopper Problem Nuisance Suggestion Synopsis:________________________________________________________ Details: ________________________________________________________ ________________________________________________________ ________________________________________________________ ________________________________________________________ ... ...

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：