Hi Chico,
I think that Viptos, the Ptolemy/TinyOS interface created by Elaine
Cheong, uses sockets to communicate with the TinyOS TOSSIM simulator.

This code was rather difficult to create, in part because I 
think it uses JNI.  

The code can be found in $PTII/ptolemy/domains/ptinyos/, try
searching for Socket.  See especially kernel/PtinyOSDirector.java.

I'm not that familiar with the details of the Viptos code, but
that is one place to start.

There are also Datagram actors in actor/lib/net, but these actors
are currently failing the tests.  

If I remember correctly, Ptolemy Classic used a RPC based interface to
communicate between the gui (called pigi) and the backend (called
pigiRpc).  There were also different efforts to communicate between
non-graphical Ptolemy Classic engines uses sockets.  One downside with
splitting simulator and communicating via sockets is that it is
difficult to get really tight interaction.  One upside is that the UI
and the engine are two processes, so in principle if your UI exits, it
might be possible to reconnect to the engine.

Instead of sockets, you might want to consider using JNI instead, even
though JNI is a real bear to get right.

_Christopher
 

--------

    Hello everyone,
    
    i am currently developing a framework in C#.NET and i would like to submit 
   test
    it by applying simulation techniques. I would like to know if it is possibl
   e to
    establish communication between Ptolemy and the framework using sockets. Do
   es
    anyone have some experience in this and if so could you share some insight 
   on
    the problems that will probably come along.
    
    Thank you in advance
    
    Francisco 
    
    
    ---------------------------------------------------------------------------
   -
    Posted to the ptolemy-hackers mailing list.  Please send administrative
    mail for this list to: [EMAIL PROTECTED]
--------

----------------------------------------------------------------------------
Posted to the ptolemy-hackers mailing list.  Please send administrative
mail for this list to: [EMAIL PROTECTED]
  • [no subject] Francisco Bernardo
    • [no subject] Christopher Brooks

Reply via email to