Help me solve the rfcomm programming.
Hi,
I am writing a programm using serial profile. But it makes me crzay.
When I am using serial port program (client and server) after I am setting
using "rfcomm command" ,i.e, listen and connect, it is ok.
But, When I try to merge with my program The Peer doesnot gets Data even though the connection is opened successfully and client sent data successfully.
My program is like this.
open("/dev/rfcomm0")
test "config1" -----fork--------------------------^----*----- read( nothing or less than sent!!!)
| | signal (to let parent know I can reciev
+---- exec ( rfcomm listen) ....
|
+------- exec (rfcomm connect)
| | signal (to let parent know it can send something)
test "config2" -----fork ---- v ----*------* write( 100 bytes)
open("/dev/rfcomm4") IS THIS Because I am using two USB dongle in the same Desktop linux???? I think it is not, becuase I tested one dongle with one pc also, and same result. Is it bug or something new thing I don't understand??????
Please check the attachment file for me
The reason I do this, we want relaying data (application level scatter net service!!!) It is reuired for us but scatter net doesnot supported in my dongle and even bluez!!
thanks!!!!!
----------------
Ahn, Heejune, Assistant Professor, PhD
Dept. CIE of Seoul National University of Technology
mobile: +82-1-3065-5418
office : +82-2-970-6543
www : cie.snut.ac.kr/ahn
----------------------------------------------
Marcel Holtmann
maintainerHi,
Quoted 6 lines
I am writing a programm using serial profile. But it makes me crzay.
When I am using serial port program (client and server) after I am setting
using "rfcomm command" ,i.e, listen and connect, it is ok.
But, When I try to merge with my program The Peer doesnot gets Data even though the connection is opened successfully and client sent data successfully.
My program is like this.
Quoted 9 lines
open("/dev/rfcomm0")
test "config1" -----fork--------------------------^----*----- read( nothing or less than sent!!!)
| | signal (to let parent know I can reciev
+---- exec ( rfcomm listen) ....
|
+------- exec (rfcomm connect)
| | signal (to let parent know it can send something)
test "config2" -----fork ---- v ----*------* write( 100 bytes)
open("/dev/rfcomm4")if you don't use a legacy application that needs an TTY then you also don't need to use the TTY feature of RFCOMM. Use the RFCOMM sockets directly and your life will be a lot more easier.
Quoted 1 line
IS THIS Because I am using two USB dongle in the same Desktop linux????
No. This works perfect. They only situation where this is problematic is PAN/BNEP, because the Linux TCP/IP then routes all data of the loopback interface.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users