Hello,
on a MDA III the synchronisation over a serial RS232 cable works fine
(although T-Mobile doesn't sell such a cable). Some software which I
develop for PDAs which uses the RS232 port there for communication
with external electronic hardware works fine on PDas but not on the MDA
III. It always crashes when I try to open the port (COM1).
Some installed device manager tool (a view only tool) seems to confiorm
that COM1 is the right one. It is named like this: "Serial cable on COM1".
What's wrong here? Active Sync has been closed before starting my
application. SOmebody somewhere mentioned that the keyboard could
block the com-port. Is this true? And if yes, how can ActiveSync then use
it?
Greetings
Markus
Re: seriel RS232 port on MDA III -sync works but own app. no
mh2005 said:
SOmebody somewhere mentioned that the keyboard could
block the com-port. Is this true?
Click to expand...
Click to collapse
No, it's not true. The port is open by an
IR daemon listening for the connection,
and serial and IR share the same UART.
Uncheck the button in the settings, and
everything will work.
Everybody who has a RS232 GPS receiver
had the same problem.
Hello!
want to use a IR Remote programs on my BlueAngel but i don't succed till now to make it work on any com ports i've tryed.
Does anyone use Infrared Remote programs on BA?
THX
Hi all,
This forum being the greatest about HTC, I think you guys will have the answer :
I would like to use my TyTN to connect to the console of a router (using serial connection) :
1. Does anyone know where I could find a miniUSB-DB9 adapter ?
2. Will there be a driver for serial port, or is it natively managed with COM ?
Such cables exist but for PC, but not miniUSB and with a Windows driver, no info about the same thing for PocketPC.
Anyone knows ?
Thanks
zEar - HTC TyTN
Re
----
DELETED Message where I thought I found it..
Understood the problem..
Hi all,
AFAI understood I cannot find a solution due to the lack of USB Host support in the TyTN. I still wonder if the port can be used in direct low level serial mode as you see in bootloader. Could WinMobile use it ?
Another way would be to have a device that would be usb host, putting the phone into slave mode, but maybe I dream...
Thanks for any reply..
there is a bluetooth to serial adaptor which has been reported to work with the tytn.
COM1
Hi,
After much googleing there's still hope. Windows Mobile presents a COM port : 'COM1 via cable' and in the specs of the TyTN there is RS232 communication.
I still cannot figure out if the miniUSB connector pins could be simply mapped to the corresponding RS232 signals. Probably not
Anyway I flashed the XDA-Live wm6 ROM and it's great ! the battery seem to last longer (still 70% after 2 days!)
Thanks to the xda-dev community
First let me apologize for spamming the forums with some similar threads... each time I overcame a hurdle and a new one presented itself, I just began a new thread to discuss that. From now on I will append the initial thread... thanks for your patience.
1. WM6.1 and WMDC 6.1 (vista x64) are not too friendly... as the interface, though designed to be intuitive.... is anything but. I am sure it will get worked out in the future... but now it is one tough SOB to conquer
2. From doing enough reading on the web, though recently updated (12-17-07)... the Toshiba BT stack also does not play nicely with WM6.1 ... as numerous smartphone and PPC users are experiencing issues across multiple mobile platforms.
3. In Vista x64 (this is my personal experience) the only way for me to sync via bluetooth is to drop the Toshiba BT stack and use the generic M$ drivers. However... doing so I lose the stereo and serial port services
4. For whatever reason, it seems that activesync locks up STK (R08). When I disable STK, I can establish a connection infintely quicker. Alternatively... when I have activesync disabled, STK is much snappier and its failure/crash rate drops substantially
If anyone has had similar and/or different/"better" experiences with similar hardware... I'd love to hear about it
OS: Vista ultimate x64
ROM: Kavana/Rickwyatt .18
BT adapter: Kensington Micro USB (toshiba rebadge)
HTC: s620
Poser said:
First let me apologize for spamming the forums with some similar threads... each time I overcame a hurdle and a new one presented itself, I just began a new thread to discuss that. From now on I will append the initial thread... thanks for your patience.
1. WM6.1 and WMDC 6.1 (vista x64) are not too friendly... as the interface, though designed to be intuitive.... is anything but. I am sure it will get worked out in the future... but now it is one tough SOB to conquer
2. From doing enough reading on the web, though recently updated (12-17-07)... the Toshiba BT stack also does not play nicely with WM6.1 ... as numerous smartphone and PPC users are experiencing issues across multiple mobile platforms.
3. In Vista x64 (this is my personal experience) the only way for me to sync via bluetooth is to drop the Toshiba BT stack and use the generic M$ drivers. However... doing so I lose the stereo and serial port services
4. For whatever reason, it seems that activesync locks up STK (R08). When I disable STK, I can establish a connection infintely quicker. Alternatively... when I have activesync disabled, STK is much snappier and its failure/crash rate drops substantially
If anyone has had similar and/or different/"better" experiences with similar hardware... I'd love to hear about it
OS: Vista ultimate x64
ROM: Kavana/Rickwyatt .18
BT adapter: Kensington Micro USB (toshiba rebadge)
HTC: s620
Click to expand...
Click to collapse
Never thought of STK being the culprit of activesync issues. Since i didnt have these issues with WM 6.0 . Now i also use the toshiba bluetooth stack but i use winXP and there was a way that i could get activesync to work. (not sure how this would translate to WMDC) here it goes. Basically i created another bluetooth COM port with the toshiba BT configurator. then made sure that COM port # was selected in connection settings under activesync then i opened activesnc on my phone searched for new bluetooth devices and when it found my PC and connected, activesync was one of the options. Trying to go the other way around by pairing the phone starting with toshibas program did not yield the same results, in fact i could never get it to paired the other way around.
very interesting...
I will try the technique with today... usually my issue comes about when the devices cant exchange passkeys... although they are identical.
pudge.... should I set the com port as server or client?
Poser said:
pudge.... should I set the com port as server or client?
Click to expand...
Click to collapse
Do what? the com port needs to be a serial COM port. not a bluetooth DUN or PAN com port
pudgedaddy said:
Do what? the com port needs to be a serial COM port. not a bluetooth DUN or PAN com port
Click to expand...
Click to collapse
I gotcha... when I use the BT com port utility it asks whether I want to create a client-side or server-side port
since its serial it needs to be "server" side...
I tried, but still no luck, it pairs.... lists stereo and activesync in the services, but then refuses to sync
I think this is a flaw in WMDC 6.1
Poser said:
I gotcha... when I use the BT com port utility it asks whether I want to create a client-side or server-side port
since its serial it needs to be "server" side...
I tried, but still no luck, it pairs.... lists stereo and activesync in the services, but then refuses to sync
I think this is a flaw in WMDC 6.1
Click to expand...
Click to collapse
the only other thing you might try is in bluetooth settings -->security on your device. disable (temporarily) the OBEX security option and try again.
You can also try and create a COM port on your device. When you're on the screen where you add a new bluetooth device. press right soft key and select COM ports. right soft key again and then select new outgoing port. then select your PC (or laptop) on the list of devices that shows up. then add a com port . and it will let you pick com 6 or com 7. Then try again
pudgedaddy said:
the only other thing you might try is in bluetooth settings -->security on your device. disable (temporarily) the OBEX security option and try again.
You can also try and create a COM port on your device. When you're on the screen where you add a new bluetooth device. press right soft key and select COM ports. right soft key again and then select new outgoing port. then select your PC (or laptop) on the list of devices that shows up. then add a com port . and it will let you pick com 6 or com 7. Then try again
Click to expand...
Click to collapse
already been down that road, trying to set up a new outgoing com port (6,7) no dice.
I think the deal is WMDC6.1 ... it makes me sad
Poser said:
already been down that road, trying to set up a new outgoing com port (6,7) no dice.
I think the deal is WMDC6.1 ... it makes me sad
Click to expand...
Click to collapse
sorry to hear that. Well since i have the same drivers, i will not be using vista anytime soon (not that i needed this as an excuse to begin with)
I was thinking of perhaps looking for some compatable drivers to replace the Toshiba stack. The generic MS drivers allow me to connect via activesync... but thats all, I lose all serial services (including object push, file transfer, stereo etc....)
I'll be honest though, I have been an XP guy for a long time... but after learning how to tweak, hack and optimize my vista install, I love it.
Hello everybody
I would like to connect my HTC TyTn II to a device which is using a RS232 for a serial connection. The software I need is running under Windows Mobile 6.1. So what I need is a device to "convert" the USB into a RS232. For PC such things are can be easily bought but I have not yet found something similar for Windows Mobile 6.1 and MiniUSB.
Have I overlooked something (maybe it was to obvious) or do those device really not exist ?
Can you guys help ?
Thanks
Michael
Hm, I believe you can do COM connections over bluetooth (I believe the phone simulates a COM port over bluetooth). You might want to look for a Bluetooth to COM adaptor (don't know whether this exists, though).
even if you found a converter and one could just use one of the many rs232 to normal usb dongles and then a usb to miniusb converter
but it would never work
because to use those conveters the device is required to support usbHost which HTC TyTn II don't