Dear Trnsys-aficionados
When I include my self written little type 192 in the trnsys input file,
it won't run and the message:
***** ERROR ***** TRNSYS ERROR # 105
TYPE 192 WAS CALLED IN THE TRNSYS INPUT FILE BUT NOT LINKED.
LINK TYPE 192 BEFORE RUNNING THIS SIMULATION.
Strange is, that the subroutine is linked which can positively be
verified by switching from Y to N (no) the respective statement in the
file cnfgtr.trn.
Also, other self-written subroutines are used and work normally. I
cannot find any difference in the code of these other subroutines and
type 192, which could explain why type 192 is treated differently in the
checking-of-unlinked-subroutines scheme. File Type192.for is included as
attachment, if anybody is willing to have a look.
I can of course work without checking for the "unlinked" subroutines,
but would prefer to leave the respective statement on Y.
Has anyone come accross this problem? Any ideas are appreciated. Thanks
and the my best wishes for X'mas and Co.
Peter
--------------------------------------------------------------------------------------------------------------------------