Oh! Now i realize that you want to connect from the NXT to the pc and not the other way round...
That is quite exactly the problem i am trying to deal with. I already put a similar question into this post
where i ask how i could connect from the NXT to a droid phone.
As the NXTs dont even succeed in pairing a phone or a pc, but are able to pair each other, this seems to be a problem on the pc/phone side...
So my problem is that we would like to distribute the bluetooth
traffic evenly on two sockets. The one thing is that i cannot establish a second
socket from the phone to the NXT. The other thing is that a connection from the NXT to the phone (or the pc) is not possible.
gloomyandy wrote:The problem is that on many systems especially windows PCs this'll first end point is already in use, typically as Bluetooth serial port...
So what exactly is this that is blocking the connection? An SPP daemon running in the background?
Do you have a hint on this, Andy?
This would be the easier way than to construct an implementation which manages a package identification model like in TCP for example (to avoid messages being mixed up).
As for now, i wanted to check out where the open port is assigned for the incoming bluetooth
connection on the NXT side.
The idea was that the problem might be that the NXT is restricted to only one incoming port. Is this true and is there a hint where to get control of that?
I did not find the handling of "cmdInit(MSG_OPEN_PORT..." in the lejos.nxt.comm.Bluetooth
Is this the wrong way to think of getting control of the port assignment? Or might this lead to a solution?