Thread: iPAQ 310 serial
View Single Post
  #15  
Old August 5th 09, 09:30 AM posted to rec.aviation.soaring
Jim White[_3_]
external usenet poster
 
Posts: 286
Default iPAQ 310 serial

At 01:22 05 August 2009, QT wrote:
On Aug 4, 1:36=A0pm, Nick Hill wrote:
Jim White wrote:
Looking at the fora it looks as though the problem is that the

aircable
mini uses the same baud rate for serial and bluetooth ports.

Therefore
=
as
the LX transmits at 4800 baud the bluetooth goes at 4800 baud which

the
HP3xx interprets as gobbledegook.


SNAFU!


Still looking for a cable solution? or a Baud rate converter?
Jim


The following would solve the problem:

http://serialgadget.com/index.php

You can use it to take the 4800 baud signal from the slow devices and
feed it out at 9600 or 19200 etc. =A0Not the cheapest little gadget

but
does the job.

The spec on the web says it requires 5V but a friend of mine has one
which they made up for him which takes 8-16V as input. He uses it in

his
glider to upscale a Colibri output from 4800 to 19200 to feed to his
Ipaq so he can switch between the Colibri and Flarm NMEA streams as

the
Flarm only outputs the extra flarm data at 19200 or higher.

Nick Hill


On the HP31x, it turns out that the usb cable is a 5 (not 4) wire
cable. If you ground the 5th wire, it turns the usb port into a TTL
level serial port. Combining this with a level converter and a baud
rate converter should let the 31x talk to 4800 baud devices (assuming
you don't overrun the buffer in the baud rate converter). And then
there is the issue of the software on the 31x making assumptions about
what baud rates various devices (SN10, CAI 10/20/25 etc) can
communicate at.

Working on the problem with all the necessary parts. Standby.


Good work Nick. I await with bated breath! Can you magic up some charge
current at the same time??

JIm