patelamarh's profile - activity

Hi Per-Olof, yes, I plan to address some of the comments I can here.

Storing them is a design choice, suggested it just to avoid repeated calculations. Users can use for example INTICN(M) through INTICN(M+3) to store the values of J0, K0, L0 and M0 and use the associated get/set APIs. INTICNs are indexed the same as ICON and can be used as integer scratch locations.

THE ADINTN must be changed to the MODE 5 and MODE 7 logic example as shown in uexs_VINDP.for (also the same in uexs_obsolete.for) in the example files, i.e., using Docuheading and SHOW_MODEL_INDICIES. You don't have to write the bus name (the model details of where it is connected will now be written out by call to docuheading as shown in uexs_VINDP.for)

You can't write any longer to IPRT directly. You will have to write to DBUF01 (as shown in usexs_VINDP.for) and flush out contents of DBUF01 to the report windw using the call to REPORTS as shown in uexs_VINDP.for.

Regarding using MODCNX and NUMCNX:

You can use the API MDLIND to get the values of J0, K0, L0, M0 (4 calls to MDLIND) and then you can remove the use of MODCNX and NUMCNX. Note that it is adequate to compute the values of J0 etc in MODE 4 or MODE 1 (at initialization), store these values and use it repeatedly during simulation (in MODE 2). By doing this you would have avoided repeated calls to MDLIND.

To use UEL2 as a macro call, please change that to UEL2CDUM which can be found in the latest version (36.3.1 as of this comment).