certi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [certi-dev] Unable to create RTI ambassador


From: Eric Noulard
Subject: Re: [certi-dev] Unable to create RTI ambassador
Date: Wed, 31 Aug 2011 14:59:42 +0200

2011/8/31 Jan-Patrick Osterloh <address@hidden>:
>> Ok, I would be interested in knowing more about that, would you be able
>> to publish some code (and may be some doc :-] ) concerning this work?
>
> Yes, this should be possible. In short:
> We are currently using two different HLA implementations. We started
> with Pitch RTI, and are now going to use CERTI, because we can't force
> our research partners to use a commercial RTI.

This is a common issue we are well aware of...

> We will use CERTI in the
> D3CoS Project (www.d3cos.eu) for implementing a multi-agent simulation
> platform. Therefore we will connect the cognitive architecture CASCaS
> (as human agents) to different simulations (xplane, matlab). My main
> work will be on simulation control, i.e. I will develop a framework to
> define and run the simulation. We already connected successfully CASCaS
> to CERTI (I have two instances of CASCaS exchanging information): As
> CASCaS is implemented in C we needed a wrapper, which allows connection
> to the C++ Part via a simple interface. This wrapper currently works for
> PITCH and CERTI, so that we can share as much code as possible.
> Especially the internal data management (we did not hard-code the SOM in
> the Federate) is shared.

Interesting, may be we could define some unofficial C API binding for
an HLA subset.
With CERTI we already have Python, Matlab and Fortan90, adding C may be nice.

>>> In the process explorer I can see, that the RTIA is started up, but then
>>> it is exits very quickly again. But I think too, that it could be
>>> something in the path. I tested to put rtia and associated libs to
>>> different paths, but without success.
>> If RTIA is starting and dying rapidely may be there could be a DLL issue?
>> RTIA depends on severals DLL.
>>
>> If you installed several version of CERTI (or other RTI) be sure that you 
>> don't
>> have DLL version mismatch.
>
> I have only one RTIA and version of CERTI installed. I used the
> Dependency Walker to check which DLLs are loaded by our wrapper, and
> they are the same for CASCaS as well as for xplane. The Paths are also
> the same.

Is the XPlane/HLA plugin multithreaded ?

Currently libRTI is not thread-safe so that you should serialize the
call to libRTI
from a possible multithreaded app.

Could you try to setup

RTI_EXCEPTION=X
and
CERTI_EXCEPTION=X in order to see if any exceptoin is raised before RTIA dies?

You may try to monitor message exchange using:
RTIA_MSG=D
and
RTIG_MSG=D

that way CERTI will trace the message (sent or received) between
Federate and RTIA (RTIA_MSG)
and RTIG and RTIA (RTIG_MSG).

Did you verify that all the federate which are trying to join the
federation have unique name?

>>
>> We lack systematic Windows tester, would you be willing to help
>> us to maintain a clean Windows build?
>
> I will ask Christoph which patches are in the version he send me. He
> send me a version that is able to be compiled on Windows/MinGW, so I
> guess. I'm not so familiar with Cmake, but I can try.
> As stated above, I will be using CERTI with Windows in our project, so
> I've interested in having a usable windows version. I will have to
> figure out how I could manage testing while maintaining a working
> version that I can use in the project.

Our problem here is that we do not use the windows version so much,
even if we try
hard to maintain a working Windows version each time we release CERTI.

Nevertheless we usually do many changes between versions so that current
CVS verison may not work on Windows unless someone compiles it and
run basic tests (may be our HLA TestsSuite) regularly.

Fixing one regression at a time during development is usually easier
than waiting
to fix every breaking change at release time.


> I will checkout the latest CSV version and try to compile it, later. I
> will let you know.

OK.

>> Check DLLs too.
>>
> I checked the DLLs, but everything seems OK so far. I can only imagine
> that xplane is loading some DLLs that interfere with CERTI, but I have
> no idea how to check this... the dependency walker just shows that
> xplane.exe uses a subset of the DLLs that the wrapper uses, and these
> are the same. I tried to copy the CERTI dll's also to different
> locations (next to xplane.exe, as well as in the plugin directory next
> to my plugin, but it makes no difference. I'm running out of ideas. If I
> would know, which DLLs are missing/wrong etc, it would be helpful.

When you test your XPlane HLA connection are there any other federate
in the federation?

-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org



reply via email to

[Prev in Thread] Current Thread [Next in Thread]