Post by thread:[EE:] Terminal program accessing > com4? BT <=> RS

'[EE:] Terminal program accessing > com4? BT <=> RS'

I am trying to debug a bluetooth serial link, which

appears as com 8 or com 11 or com 40 (depending on the host

hardware).

Anyone have any leads on terminal programs that can

access serial ports higher than Com 4?

Ones that allows access to all ports the OS reports?

Ones that allow non-standard baud rates?

So far everything I've found on the web at the various

shareware/trialware sites seem to be limited to com 4 max.

I know there was an old MSDOS program that went to com 8

and another supported any baud rate the dividers could make,

but I can't remember their names and I doubt that they would

work under XP. (Even trusty old Procom 4.5 won't work

under XP {not that it can go beyond com4)).

Anyone have experience forcing Linksys devices to sit at

com4 (not 8) or D-link (com11) or Toshiba tablet internal

(Com40!! beyond even XP's API ability to access).

XP device manager just doesn't seem to let one set the

port to where you want (unlike drive letters).

I'm willing to buy something that WORKS on ALL available

comm ports.

I Can't figure out how these bluetooth host device manufactures

can create drivers that appear at ports that most

programs can't access.

And as long as I'm talking bluetooth, anyone have leads on

an inexpensive Class ONE! RS232<=>bluetooth device/module?

http://www.wirelessrs232.com/ has some nice modules but

I'd like to see if there is anything else out there (don't

like sole sources when 2k+ units/year at stake).

I'd also like on board batteries like 3ETI had, before they

ditched the product.

Thanks in advance for any leads.

Robert

_______________________________________________

http://www.piclist.com

View/change your membership options at

http://mailman.mit.edu/mailman/listinfo/piclist

At 12:38 AM 10/11/2004, Robert Rolf wrote:

>I am trying to debug a bluetooth serial link, which

>appears as com 8 or com 11 or com 40 (depending on the host

>hardware).

>Anyone have any leads on terminal programs that can

>access serial ports higher than Com 4?

>Ones that allows access to all ports the OS reports?

>Ones that allow non-standard baud rates?

Oddly enough, hypterterminal

Don't know about nonstandard bauds.

I use it with my Edgeports up through COM40-ish depending on how I have them set up.

_______________________________________________

http://www.piclist.com

View/change your membership options at

http://mailman.mit.edu/mailman/listinfo/piclist

Dave VanHorn wrote:

> At 12:38 AM 10/11/2004, Robert Rolf wrote:

>>I am trying to debug a bluetooth serial link, which

>>appears as com 8 or com 11 or com 40 (depending on the host

>>hardware).

>>Anyone have any leads on terminal programs that can

>>access serial ports higher than Com 4?

>>Ones that allows access to all ports the OS reports?

>>Ones that allow non-standard baud rates?

> 

> 

> Oddly enough, hypterterminal

No joy.

Can't even open Com3 (Microsoft USB GPS) that Teraterm can.

I was surprised that it correctly lists the available

serial ports (including TCP/IP [telnet]}. Previous versions

(not XP) were so brain dead I didn't even waste my

time checking. It can't seem to open anything that isn't

a 'real' UART.

> Don't know about nonstandard bauds.

Not supported.

> I use it with my Edgeports up through COM40-ish depending on how I have them set up.

Interesting. I'll give it a try on the Tablet (Com40).

I'll have to check the Microsloth Knowledge base to

see what the issue with USB might be. My guess is that

it wants to change baud rate, which is irrelevant to

USB Bluetooth since the driver setup panel has to do that.

Thanks for making me look at hyperterm again.

Robert

_______________________________________________

http://www.piclist.com

View/change your membership options at

http://mailman.mit.edu/mailman/listinfo/piclist

>

>No joy.

>Can't even open Com3 (Microsoft USB GPS) that Teraterm can.

Danger will robinson!

Do you by chance have a microsoft ballpoint mouse driver loaded?

When MS detects a new serial port, and sees GPS data on PNP discovery, it thinks this is a ballpoint mouse. Causes all sorts of grief like this.

My edgeports have a setting to kill PNP discovery through the serial port, works great.

_______________________________________________

http://www.piclist.com

View/change your membership options at

http://mailman.mit.edu/mailman/listinfo/piclist

> And as long as I'm talking bluetooth, anyone have leads on

> an inexpensive Class ONE! RS232<=>bluetooth device/module?

> http://www.wirelessrs232.com/ has some nice modules ...

That's a ferocious price!

About $79US in approaching 100 volume.

Given that you can buy standard PC end USB device retail in NZ for the 

equivalent of about $UZ50, the module is overpriced. Scarcity and limited 

demand is all that saves it. I have a potential semi volume application 

which would benefit from Bluetooth capability but unfortunately that price 

is completely outside the acceptable price range.

        RM 

_______________________________________________

http://www.piclist.com

View/change your membership options at

http://mailman.mit.edu/mailman/listinfo/piclist

>When MS detects a new serial port, and sees GPS data

>on PNP discovery, it thinks this is a ballpoint mouse.

>Causes all sorts of grief like this.

Is that what happens. Had this happen when trying to connect a GPS receiver

through a USB converter when powering up the machine. The resulting mess of

cursor moving, menus popping up and down, and miscellaneous strange things

happening was most disconcerting.

_______________________________________________

http://www.piclist.com

View/change your membership options at

http://mailman.mit.edu/mailman/listinfo/piclist

On 11 Oct 2004 at 20:40, Russell McMahon wrote:

> > And as long as I'm talking bluetooth, anyone have leads on

> > an inexpensive Class ONE! RS232<=>bluetooth device/module?

> > http://www.wirelessrs232.com/ has some nice modules ...

The Class 1 requirement narrows the field quite a bit. 

We went for BlueRadios modules. They don't do point-to-multipoint 

though, if that's a requirement.

> Given that you can buy standard PC end USB device retail in NZ for the

> equivalent of about $UZ50, the module is overpriced.

That's sort of like comparing an ethernet card to a webserver.

The USB device only has the rf section and the lower levels of the 

protocol stack, leaving the PC to provide multiple profiles. The serial 

modules have a complete implementation of single profile.

Steve.

==========================================

Steve Baldwin                          Electronic Product Design

TLA Microsystems Ltd             Microcontroller Specialists

PO Box 15-680, New Lynn                http://www.tla.co.nz

Auckland, New Zealand                     ph  +64 9 820-2221

email: spam_OUTsteveTakeThisOuTtla.co.nz                      fax +64 9 820-1929

=========================================

_______________________________________________

http://www.piclist.com

View/change your membership options at

http://mailman.mit.edu/mailman/listinfo/piclist

At 04:53 AM 10/11/2004, Alan B. Pearce wrote:

>>When MS detects a new serial port, and sees GPS data

>>on PNP discovery, it thinks this is a ballpoint mouse.

>>Causes all sorts of grief like this.

>

>Is that what happens. Had this happen when trying to connect a GPS receiver

>through a USB converter when powering up the machine. The resulting mess of

>cursor moving, menus popping up and down, and miscellaneous strange things

>happening was most disconcerting.

We call that "psychomouse"!.

I've also had it happen with the data stream from an EMWIN receiver.

_______________________________________________

http://www.piclist.com

View/change your membership options at

http://mailman.mit.edu/mailman/listinfo/piclist

>We call that "psychomouse"!.

>

>I've also had it happen with the data stream from an EMWIN receiver.

I would leave off the "mouse" part :))))

I did not think these ports were supposed to enumerate as a mouse. Guess it

means you could use an ordinary serial mouse on a USB converter.

_______________________________________________

http://www.piclist.com

View/change your membership options at

http://mailman.mit.edu/mailman/listinfo/piclist

At 10:53 AM 10/11/2004, Alan B. Pearce wrote:

>>We call that "psychomouse"!.

>>

>>I've also had it happen with the data stream from an EMWIN receiver.

>

>I would leave off the "mouse" part :))))

>

>I did not think these ports were supposed to enumerate as a mouse. Guess it

>means you could use an ordinary serial mouse on a USB converter.

certainly.

In fact, I use them on a USB converter that's hooked in through my LAN.

Spooky!

_______________________________________________

http://www.piclist.com

View/change your membership options at

http://mailman.mit.edu/mailman/listinfo/piclist

> I did not think these ports were supposed to enumerate as a mouse.

They don't. They enumerate as a serial port. However, when Windows 

detects a serial port, it looks for the first character to be "M". If it gets 

one, it decides that it is a serial mouse and pipes all the data in that 

direction.

Obviously, there's a catch if the device continually sends data containing 

an "M", or something that appears as one if it's out of sync or the wrong 

baud rate, character size, etc.

To the OP - Did you know that you can set the COM port number in 

WinXP through the Device Manager / USB Serial Port / Port Settings / 

Advanced / ComPort number ?

You can also disable other non-hardware ports to make room.

I use the free "Terminal v1.9b by Bray" for general serial stuff. It only 

goes to COM6 though.

Steve

_______________________________________________

http://www.piclist.com

View/change your membership options at

http://mailman.mit.edu/mailman/listinfo/piclist

At 02:02 PM 10/11/2004, .....steveKILLspam@spam@tla.co.nz wrote:

>> I did not think these ports were supposed to enumerate as a mouse.

>

>They don't. They enumerate as a serial port. However, when Windows 

>detects a serial port, it looks for the first character to be "M". If it gets 

>one, it decides that it is a serial mouse and pipes all the data in that 

>direction.

>Obviously, there's a catch if the device continually sends data containing 

>an "M", or something that appears as one if it's out of sync or the wrong 

>baud rate, character size, etc.

GPRMC?

Boy, I'm glad they do such an exhaustive test to see what they are connected to! 

:-P

_______________________________________________

http://www.piclist.com

View/change your membership options at

http://mailman.mit.edu/mailman/listinfo/piclist

TeraTerm can use COM ports up to 16 but, you have to edit the ini file to

allow it.

In TeraTerm.ini change this setting

"MaxComPort=4"

to the highest number you need.

Paul

> {Original Message removed}