--- In b..., "femme_pacita" wrote:
> Maria

Well, he's a she! There was a hint, I guess, but no matter. Maria, I
still somehow have little idea of what you did, but I'm glad to hear
that it sufficed.
Tom

I guess it must be Thursday. I suspect, unless he has, indeed, built
the time machine and we'll hear from him again last week, he's on his
way home for the holidays, I'll bet.

Who would like a no-reward job teaching strangers who take, take some
more, and some more, then vaporize, leaving not a hint if you were
helpful or foolishly wasteful of your time? You'll need to provide
your own tools, supplies and workspace, but the perks are, uh, uh,
well, there are no perks.
Tom

This code worked perfect with S2Midi program. I sent data with a eb500
connected to the BX and was read by the Hyper Terminal. I don't have
the MIDI code in here, but here it is for connecng eb500 and Hyper
Terminal in a pc.
Public Sub Main()
dim ibuffer as byte
dim obuffer as byte
dim q1 (1 to 160) as byte
dim q2 (1 to 160) as byte

Call DefineCom3(16, 17, bx0000_1000)
Call OpenQueue (q1, 160)
Call OpenQueue (q2, 160)
Call OpenCom (3, 9600, q1, q2)

Do
Call PutQueueStr (q2, "funcion whatever")
call delay (0.2)
Loop
End Sub

Sorry for that- As you must suspect, I have slept 8 hours in the last
4 days, and now we finally succeded. And really, I couldn't have done
it without your help and advise.

We used a code called s2midi that detects midi input from the serial,
so we could send data via bluetooth. The rest is history.

Thanks a lot

Maria

--- In b..., "Tom Becker" wrote:
>
> I guess it must be Thursday. I suspect, unless he has, indeed, built
> the time machine and we'll hear from him again last week, he's on his
> way home for the holidays, I'll bet.
>
> Who would like a no-reward job teaching strangers who take, take some
> more, and some more, then vaporize, leaving not a hint if you were
> helpful or foolishly wasteful of your time? You'll need to provide
> your own tools, supplies and workspace, but the perks are, uh, uh,
> well, there are no perks.
> Tom
>

> Ups, sorry, somehow I thought both bluetooth had to be COM3.
> Now my problem is that I don't know how to recieve the MIDI that my bx
> is sending out. Should I connect another BX to the PC? How can I do
> that so incoming data can be trasfered to the MIDI box? Or is there
> some program that can read the data that I'm sending in the pc itself,
> so I can trasfer it to some audio program?
>
> By the way, thanks SO MUCH for your help. I'm hanging on a cliff here.
>
> --- In b..., Tom Becker wrote:
> >
> > > ... when I tell the bluetooth in the pc to detect the other
one, it
> > only finds a COM5...
> >
> > That's probably correct. COM5 is the _PC_ COM5, a logical port
> assigned
> > to _its_ Bluetooth device. COM5, on the PC, is the port you must
> use to
> > talk to the remote radio. Try running a terminal program on the
PC and
> > look at COM5.
>

You're right about that. So I'm thinking about buying another eb500
and connect it to another bx. That way I can split my sensors-midi
code, so one bx captures data and trasnform it into midi, while the
other one recieves the midi through the bluetooth and sends the audio
out to a midi board.

My main problem here is that I don't know how to connect the two
bluetooth without the "friendly" pc interface.
I know that I should find out the eb500 adress, but I really have no
idea how to do that. Can you help me with it please?? Deadline
Thursday. Thanks a lot!!

> ...COM1ToADC...

No.
Tom

> ... My question is: do I send the sensors data by bluetooth or do I
send the MIDI by it?

I suspect you can do either, that's a design decision that you need to
make. I would send the raw data wirelessly and convert to MIDI at the
other end. Like you suggest next:

> You told me that COM3 doesn't send midi, so should I
> change the com or it would be easier to send the sensors data out so
> that the second bx is the one that transform it to midi?

BX-24 COM3 can't send MIDI because it can't make the MIDI rate, only
BX-24 COM1 can get close.

What MIDI board? I think that's the first mention of it. Let's see a
link.

Could the Com1ToAdc and DACtoCom1 functions be usefull in this case?

Ok. The thing is I have 2 bx, 2 eb500 and midi boards. The proyect is
to capture certain sensors, so when one of them is activated, we send
a midi note out. Diferent sensors activated means different notes. And
this must be wireless.
So, I have the first bx connected to the sensors and the eb500; then I
have the second bx connected to the second eb500 and to the MIDI out.

My question is: do I send the sensors data by bluetooth or do I send
the MIDI by it? You told me that COM3 doesn't send midi, so should I
change the com or it would be easier to send the sensors data out so
that the second bx is the one that transform it to midi?