Welcome to Adams/Solver Subroutines - Kxcad.net

More documents

Recommendations

Info

126 Adams/Solver Prerequisite None Calling Sequence CALL USRMES (msgflg, mesage, id, msgtyp) Input Arguments id An integer variable that specifies the ID of the statement that is currently invoking the user-written subroutine. mesage A character string or variable of as many as eighty characters that you want USRMES to document. This character string should be a descriptive message and should include the name of the subroutine issuing the message. msgflg A logical (true or false) variable. When msgflg is true, USRMES documents a message. msgtyp A character variable that indicates what type of message is given. msgtyp can have one of four values: Extended Definition INFO - For information messages WARN - For warnings ERROR - For error messages FAULT - For fatal error messages INFO_NOPAD - Prints out the information message but without the USRMES:USER1 tag before the message LOGINF - Writes out the message in the message file but doesn’t print it out on the screen If msgtyp has any other value, Adams/Solver issues an information message. USRMES allows you to output messages from user-written subroutines. The messages always go to the Message File, and during interactive execution, Adams/Solver displays them on the screen.
User-Written Subroutines Welcome to Adams/Solver Subroutines User-written subroutines, while a little more difficult to use, provide a degree of generality, efficiency and flexibility that function expressions do not. Subroutines allow you to use FORTRAN-77 features to define functions not otherwise available with Adams/Solver, and to tailor Adams/Solver to your needs. By linking in user-written subroutines, you don't lose any efficiency or decrease the simulation speed. Subroutines and function expressions serve essentially the same purpose: they both allow you to define non-standard input to Adams. Function expressions are easier to work with, because you don't have to compile or link programs. Also, they work on every machine on which Adams/Solver is available. User-written subroutines, however, are much more general. The power of the programming language is available to define modeling elements or special output. On the other hand, function expressions support a limited set of programming constructs. Therefore, complicated phenomena, especially those involving a lot of logic, cannot be easily described using function expressions. You use user-written subroutines when: • Dataset functions become awkward. • You need to define functions used by a group of users. • Statements, such as GSE and UCON, require them. • You want to control the running of complex simulations that require decision-making logic. Write user-written subroutines with care because incorrectly coded subroutines are very difficult to debug. Follow a crawl-walk-run approach for developing user subroutines. Start with simple versions of a user-written subroutine, make sure it works as desired, then gradually increase the complexity of the subroutine. Make sure that there are no compiler or linker warnings when your subroutine is linked into Adams. The "C" style interface to user subroutines has been enhanced to replace some of the arguments with a pointer to a structure. This will require changes to your user subroutine source code. If you are using the fortran style interface to user subroutines you will not be effected and no changes will be required. The new argument list to the "C" style interface replaces some of the arguments with a pointer to a structure. This structure contains the replaced arguments plus additional information. Old arguments such as ID, PAR, and NPAR have been incorperated into the structure. New arguments such as marker id's have been added to the structure. CFFSUB The CFFSUB evaluation subroutine computes a set of friction force values for a CONTACT statement (C++ or FORTRAN). You can use a CFFSUB when the default friction force routine is not applicable to your model. 127
Page 1 and 2:
Welcome to Adams/Solver Subroutines
Page 3 and 4:
Compilers and Linkers Welcome to Ad
Page 5 and 6:
Utility Subroutines About Utility S
Page 7 and 8:
Subroutine: Does the following: Uns
Page 9 and 10:
Page 11 and 12:
Input Arguments Welcome to Adams/So
Page 13 and 14:
RETURN END AKISPL Welcome to Adams/
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Use Called By Any user-written subr
Page 23 and 24:
T1( x - x0) = x - x0 CUBSPL , Welco
Page 25 and 26:
Output Arguments Extended Definitio
Page 27 and 28:
Extended Definition Welcome to Adam
Page 29 and 30:
Input Arguments Output Arguments We
Page 31 and 32:
Input Arguments Output Arguments Ex
Page 33 and 34:
Page 35 and 36:
Use Welcome to Adams/Solver Subrout
Page 37 and 38:
GETCPU retrieves CPU time used so f
Page 39 and 40:
GETMOD returns the current analysis
Page 41 and 42:
Use Called by Any user-written subr
Page 43 and 44:
Prerequisite Welcome to Adams/Solve
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
C C Inputs: C INTEGER ID C C Output
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Output Arguments Welcome to Adams/S
Page 57 and 58:
C = [-A-1B] Welcome to Adams/Solver
Page 59 and 60:
Output Arguments Welcome to Adams/S
Page 61 and 62:
Prerequisite STRING statement in da
Page 63 and 64:
Prerequisites None Calling Sequence
Page 65 and 66:
function. Welcome to Adams/Solver S
Page 67 and 68:
Calling Sequence CALL IMPACT (x, x'
Page 69 and 70:
Output Arguments Extended Definitio
Page 71 and 72:
Input Argument Welcome to Adams/Sol
Page 73 and 74:
Input Argument Welcome to Adams/Sol
Page 75 and 76: Use Called By Any user-written subr
Page 77 and 78: Use Called By SPLINE_READ Calling S
Page 79 and 80: Input Arguments Welcome to Adams/So
Page 81 and 82: `S232' Space-two: 2-3-2 `S313' Spac
Page 83 and 84: Welcome to Adams/Solver Subroutines
Page 85 and 86: Callng Sequence CALL SHF (x, x0, a,
Page 89 and 90: Calling Sequence CALL STEP5 (x, x0,
Page 103 and 104: C INTEGER IPAR(2), N_UVX, N_UVY, N_
Page 105 and 106: CALL NMODES(FBDYID,NQ,ERRFLG) STRIN
Page 111 and 112: F(M 1 (q), M 2 (q), ..., M N (q)) W
Page 113 and 114: Examples Welcome to Adams/Solver Su
Page 115 and 116: SUBROUTINE SFOSUB (ID, TIME, PAR, N
Page 117 and 118: DO 100 J = 1 , 6 DFDDIS(I,J)=0.D0 D
Page 121 and 122: Use Called By Any user-written subr
Page 125: Welcome to Adams/Solver Subroutines
Page 139 and 140: C - Evaluate Normal Force component
Page 153 and 154: Output Arguments Welcome to Adams/S
Page 167 and 168: C X rotational field torque C ... F
Page 169 and 170: }; int NPAR; const double* PAR; int
Page 171 and 172: Using the DFLAG Variable Welcome to
Page 173 and 174: C RESULT(2) = ... RESULT(3) = ... R
Page 175 and 176: GSE_UPDATE Calling Sequence Welcome
Page 177 and 178:
Page 179 and 180:
Use Corresponding Statement Welcome
Page 181 and 182:
Output Arguments scale A double-pre
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Use Corresponding Command Calling S
Page 191 and 192:
Page 193 and 194:
C ENDIF C C - Create request inform
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
* * SENSOR struct sAdamsSensorEval
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
FORTRAN - Prototype Welcome to Adam
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
C C C C C C C C C C C C C C VALUES(
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
C - Derivatives of prior first deri
Page 227 and 228:
Page 229 and 230:
C C - Subroutine initialization ---
Page 231 and 232:
Page 233 and 234:
*/ struct sAdamsVforce { int ID; in
Page 235 and 236:
FORTRAN - Prototype Welcome to Adam
Page 237 and 238:
Examples For an example of this sub
show all

Welcome to Adams/Solver Subroutines - Kxcad.net

Create successful ePaper yourself

Delete template?

Save as template?