Problem with establishing interface between TRNSYS and BCVTB

[Adam Rysanek]

Dear all,

We have been trying for a month to establish a working setup with TRNSYS and BCVTB. We are encountering the same error no matter what type of configuration we are trying. Regarding our attempts:

- We have been using only the latest version of BCVTB (Release 1.5.0)

- We have tried to get TRNSYS<->BCVTB working on both a Windows 32-bit and 64-bit machines

- We have tried TRNSYS versions 17.0 and 17.2

- We have ensured, to the best of our knowledge, that full user permissions are provided on the Windows machines

We've tried all types of configurations you can create from the above list, and each time we have received the same error generated by TRNSYS when attempting to run the BCVTB TRNSYS example "TRNSYS17-room".

From the LST file, we receive:

----------------

 *** Fatal Error at time   :         0.000000

    Generated by Unit     : Not applicable or not available

    Generated by Type     :  6666

    TRNSYS Message    105 : A TYPE was called in the TRNSYS input file but was either not linked into trndll.dll or was not found in an external dll. A dummy subroutine was called in its place. Please link the TYPE or remove it from the input file

    Reported information  :  Type6666 could not be located in either the trndll.dll or in an external dll. Please relink theTRNDll.dll including this Type or make sure that an external DLL in the \UserLib\DebugDLLs and \UserLib\ReleaseDLLs folders contain the Type.

 

 

*** Fatal Error at time   :         0.000000

    Generated by Unit     : Not applicable or not available

    Generated by Type     :  6667

    TRNSYS Message    105 : A TYPE was called in the TRNSYS input file but was either not linked into trndll.dll or was not found in an external dll. A dummy subroutine was called in its place. Please link the TYPE or remove it from the input file

    Reported information  :  Type6667 could not be located in either the trndll.dll or in an external dll. Please relink theT

-------------------

I've e-mailed TESS about this, and they're unsure of the solution but stated that most errors between TRNSYS and BCVTB are related to permission issues. However, I can't tell where I would need to increase permissions more than I have done so.

Has anyone encountered the above errors?

If not, and you have been able to get TRNSYS-BCVTB working, would be able to share what softare versions / hardware configuration worked for you?

Would be very grateful for your help,

Adam

[Manuel Ostheimer]

Hi Adam,
have you already solved the Problem? I've the same and would be very grateful for some inputs.
Best regards
Manuel

[Jaimie Swartz]

Hi Adam,

I am getting the exact same issue, and this thread has the same case:

http://energy-models.com/forum/building-controls-virtual-test-bed-13-has-been-released

One user says "The DLL with Type 6666 and 6667 has not been added to the
standard TRNSYS package yet. Please contact your TRNSYS distributor to
receive the files."

Guess we need to contact TRNSYS,
Jaimie

[Jaimie Swartz]

Hi Adam,

My previous post was before I had the full version of Trnsys 17. Now that I do have the full version, I am still getting the same errors as you even after I received the files from trnsys and used the following steps given by Trnsys to configure the blocks:

1) TRNSYS-BCVTB.zip - this contains the BCVTB type (Type6666) and a type for the example project (Type6667) - uncompress and place this in the Trnsys17\UserLib\ReleaseDLLs directory.

2) BCVTB-Proforma.zip - this contains the proformas for the Types so you can use them in Studio - uncompress this folder somewhere in the \Trnsys17\Studio\Proformas directory (I put it under Utility\Calling External Programs).

3) BCVTB-Project.zip - this contains an example project using the BCVTBtype - uncompress this folder in the Trnsys17\MyProjects directory.

I put this in the Trnsys17\Examples\BCVTB directory instead

4) TRNSYS-Room.zip - this contains an example BCVTB project that calls TRNSYS with controls in BCVTB (the same example that is used for all the other programs) - uncompress this folder in the bcvtb\examples directory.

Using c-room example instead of room example since the setup is exactly the same, only difference is the path to the simulator, which points to BCVTB_Example.dck

You should be able to start up BCVTB and open the system.xml file in the examples\TRNSYS-room folder and run the example project.

--------------------------------------------------------------------------------------------------------------------------------------

Like you, I am getting 2 errors in the lst file (both when running the example project in Trnsys studio and when running the c-room example in BCVTB) :

*** Fatal Error at time   :         0.000000

    Generated by Unit     : Not applicable or not available

    Generated by Type     :  6666 and 6667

    TRNSYS Message    105 : A TYPE was called in the TRNSYS input file but was either not linked into trndll.dll or was not found in an external dll. A dummy subroutine was called in its place. Please link the TYPE or remove it from the input file

    Reported information  :  Type6666 and Type 6667 could not be located in either the trndll.dll or in an external dll. Please relink theTRNDll.dll including this Type or make sure that an external DLL in the \UserLib\DebugDLLs and \UserLib\ReleaseDLLs folders contain the Type.

--------------------------------------------------------------------------------------------------------------------------------------------------

Has anyone been able to solve this? It seems that the system can't detect TRNSYS-BCVTB.dll.

I don't know what permissions I should check but all of this is installed on the C drive and I have administrative access so idk what more I can do there.

Thank you,
Jaimie

[Nauman Azam]

Hi Jaimi,

You are getting the same error even after getting the files from your TRNSYS provider because there is one step missing in what you did with the files after receiving them from your TRNSYS provider. This step is as follows:

TRNSYS_add_dlls.zip - this contains additional needed dlls - uncompress and place this in the Trnsys17\exe directory.

You should/must have received TRNSYS_add_dlls.zip file which you should unzip in TRNSYS17/Exe directory.
Make sure to put the two unzipped files (bcvtb.dll & libexpat.dll) directly in TRNSYS17/Exe directry. One problem that people, normally do is that  while unzipping the file, they put it in TRNSYS17/Exe/TRNSYS_add_dlls.

I know it is late for the reply of this thread. But, it might be helpful for the people googling the same problem and landing at the same thread.

Bests,
Nauman

[Λάμπρος Λαμπρόπουλος]

Dear Nauman,

I am facing the same problem with communication between TRNSYS18 demo (64 bit) and BCVTB.

I dit what you wrote but the message still persists.

Is there any clue of what can I do?

kind regards

[Zhou Young]

Hi Jaimie,

I also encountered the same problem that there are no type6666.dll and type6667.dll. I have the license for trnsys 18 and emailed the TESS team. However, they haven't replied so far. So, could you provide these two types for me? my email is  zhouyo...@gmail.com. Thank you very much.