I don't think you need the SF on PC1. Clients should be able to connect
directly to SF on PC2 using the MOTECOM or command line "[EMAIL PROTECTED]:7000"
setting.
Have you tried running Deluge on PC2 directly to the USB port and then
connecting to the PC2 SF? That would eliminate at least one hop to get
started...
MS
Emiliano wrote:
Hi all,
I'm posting this message because I couldn't run sf properly in my scenario.
The set up is as follows: PC1 <-> (ethernet) <-> PC2. I have a Sky Mote
connected vis USB to PC2. I want to run the Deluge java toolchain on PC1 (which hosts the
Deluge java package) and send the streams to PC2 which, by using sf, forwards them to the
Sky Mote to operate the reprogramming.
Below there is what I've done:
- I make sf running on PC2 ($ ./sf 7000 /dev/usb/tts/1 57600 telosb)
- I run sf on PC1 as follows: $ java net/tinyos/sf/SerialForwarder -comm [EMAIL
PROTECTED]:7000
- before running Deluge on PC1 I export the MOTECOM var as follows: $ export
[EMAIL PROTECTED]:7000
- on PC1 I run Deluge ping: $java net/tinyos/tools/Deluge --ping
What I get is:
- on the PC1's sf GUI:
Listening to [EMAIL PROTECTED]:7000
Platform telos
Listening for client connections on port 7000
- Deluge hangs:
[EMAIL PROTECTED] java]$ java net/tinyos/tools/Deluge --ping
Pinging node ...
Deluge doesn't go through.
Do you please have any suggestions? What am I missing?
Thank you very much,
Emiliano
_______________________________________________
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
_______________________________________________
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
