[Tinyos-help] tinyos.jar to .NET?

[Javier Barbarán]

Thank you very much Greg! It is working...!! and it would be enough for 
the first prototype that we need to use.

I didn't used it before because I thought I just could launch 
SerialForwarder from cygwin, but actually I can launch it just having 
the tinyos.jar and in addition I remember that somehow I can launch the 
SerialForwarder without GUI, so I think it is very very nice indeed. And 
on the other hand I have available all the interfaces, like MoteIF, 
Packet, and so on, that simplifies the task of reading messages from the 
sensor network. The last thing I have to face of is I have to create an 
IKVM of the classes generated by mig, cause I don't think that there is 
a mig available for C#.

So, Thanks again Greg.

Regards, and I hope this post helps to other people that are thinking on 
developing a C# .NET application using sensors.



Greg Hackmann escribió:
> On 3/5/09 9:41 AM, Javier Barbarán wrote:
>> Hi Urs and all,
>>
>> And thank you very much for your help. I've never used this kind of
>> application, but I searched on the Internet and I found straceNT for
>> windows, and I have used it in order to check where could be the
>> problem, but without help cause the information that provides is not 
>> useful.
>>
>> I have no other ideas for the momment, but I just think that it could be
>> really nice to open the possibility on developing easily applications
>> for sensor networks using .NET, but just using a .NET version of the
>> tinyos.jar.
>>
>> If anyone of you knows anything related to, or could give any clue..
>> please tell me, Thank you very much again, and thanks Urs, Ill continue
>> searching other debug application as you suggested me.
>>
>> Regards.
>
> One thing you may want to try is starting the TinyOS SerialForwarder 
> application in a regular Java VM before running your .NET application 
> (see 
> http://docs.tinyos.net/index.php/Mote-PC_serial_communication_and_SerialForwarder). 
>  Then, from your .NET application, use the source "sf at localhost:9002" 
> instead of "serial at com4:micaz".
>
> If this works, then it's pretty likely that the native C code is 
> causing the crash.
>
> Greg Hackmann
>
> __________ NOD32 3906 (20090303) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
>
>
>