Re: [AIRcable] AirCable and Serial Device

[Juergen Kienhoefer]

sure I help you

but I need more information.
Host down from the BlueZ stack means that the device you are trying to connect
is already connected or it is not available on the air.

Using Bluetooth over the graphical interface is VERY different. It uses
dbus interface to send commands to BlueZ in the Android OS.

While you are connected with Android phone to a PC and using adb shell
to issue commands, you say, it works?

Maybe host down was not a message from the BlueZ stack for a
Bluetooth device, but more a message from the Linux kernel trying to
communicate with the PC over a network connection that is used for
debugging.

Host would be your PC then. Host down means, you disconnected the PC.

OK back to AIRcable.

The switches just mean that you are running at 9600 baud 8N1 no hardware
handshake, when connected.

Look at the blue LED. If blinking, you have no connection. If on steady
you are connected.

Green means that all has been loaded and working.

Make sure you run in "cable slave" mode. So you still can find it
when not connected.

Hope that helps
Juergen
Wireless Cables Inc.

On Thu, Sep 13, 2012 at 6:46 AM, crusso <cru...@clarke.com> wrote:
> I am currently working on trying to setup the Aircable as a bluetooth
> connection to a serial device.
>
> If I have the AirCable setup as a Cable - Slave with 9600 bps and connected
> to the serial device and I have the below bluetooth android program running
> on an HTC EVO LTE in Debug mode with the HTC EVO LTE hooked up to my
> computer when the sendR is run the phone talks to the aircable send the Q to
> the serial device and the serial device sends back the information
> "DL300,399"(Which is what I am expecting).
>
>
>
> Once I disconnect the phone from the computer and I still have the aircable
> connected to the serial device when I run the program again I get the error
> message that the host is down.
>
> I currently have the switches on the AirCable set to 1 - on, 2 - on, 3 -
> off, 4 - off. What am I doing wrong? I have tried the other modes as well
> with no success.
>
> Any help is greatly appreciated
>
> --
> You received this message because you are subscribed to the Google Groups
> "AIRcable(tm)" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/aircable/-/HDDK-rqngxQJ.
> To post to this group, send email to airc...@googlegroups.com.
> To unsubscribe from this group, send email to
> aircable+u...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/aircable?hl=en.

[crusso]

Juergen,

 

I want to thank you for your help on this.  The aircable was actually working beautifully.  It was the code that I inherited that was causing the issue.  It was not connecting and disconnecting from the bluetooth correctly.  Therefore, since it kept the communication between the devices open and didn't close it when it went to connect again to send the next message it was giving the busy reply.

 

Thanks you again for your help on this.  I do really appreciate it.

 

Thanks,

crusso

[Juergen Kienhoefer]

no problem, anytime.

do you want to share your code with the community?
it's always good to see how others do BT software....

Thanks
Juergen

> https://groups.google.com/d/msg/aircable/-/lAb-HsDn4LEJ.

[crusso]

Sure.  I will post it as soon as I have it written and tested fully.

 

Thanks again.

On Thursday, September 13, 2012 12:47:37 PM UTC-5, Juergen Kienhoefer wrote: