I have an older software application (around Windows CE timeframe) running on the Wizard. It runs fine. The program is designed to take RS232 serial data from a comport and plot it on a map screen. Here's the issue: Older devices had cables that connected to serial (db9) connectors on one end and plugged into the phone on the other end. Any ideas on how to work this on a Wizard?
Related
Hi there
Part of my job envolves monitoring data from various sensors, this involves booting my laptop, pluging it in, cause the battery fecked, hookin to the sensor, 3 seconds to check the data then pack it all away again.
I think I`ve found a Hyperterminal for ppc called vxhpc, looks like it has the right functions.
I have opened a plug that I have that connects to the bottom plug, and I can see 22 pins, but I dont know which one does what.
I`m after com1 wiring I think, it will mostly be RS232 signals that I`m monitoring.
The options in the software are:
Serial cable on com1
CAM1
IR Port
Com2 Serial on usb
there are a few more.
I assume serial on com1 is the obvious choice, but you guys and gals will know better than me.
So the pin outs of the bottom connector, and if anyone knows of a better software, that would be fanastic.
The telnet part, I also have some telnet software called Mini Telnet, Many of the systems I work on control ship engines and thruster, If i could connect to the engine managment system network via the XDA2S, I could, In theory, control the ships movement, and monitor the system aswell.
Unfortunatly, due to saftey reasons, all networks on ships are hardwired.
Is it possible to connect from the bottom plug to a network hub ?????
If so, do you know how ?
Thanks for all your help
All the best
Nikki
just noticed, the Wallaby and Himalaya have the same wiring, does this mean, chances are the blue angel is the same again ? maybe ??
okay, i have been investigating a wee bit, my findings so far, this is about the telnet side of things, if I`mwrong anywhere, please correct me.
Taken from the wiki site
5 ANALOG GND
6 RS232_DCD
7 RS232_CTS
8 RS232_TXD
9 RS232_RTS
10 RS232_RXD
11 RS232_DTR
So, RJ-45 to DB9 pc comport
rj 45 side -------------------XDA2s Side
1 DCD------------------------6 DCD
2 DSR------------------------?? DSR, i dont see this one on the list, is it important ?
3 DTR-------------------------11 DTR
4 SigGnd----------------------5 SigGnd, Plenty of these
5 TXD-------------------------10 RXD ???
6 RXD-------------------------8 TXD???do i have these the right way around ?
7 CTS-------------------------7 CTS
8 RTS-------------------------9 RTS
So, does this look about right ? and how important is the DSR signal, I`m unsure of it puropse.
Like I said, if you see anything wrong, at all, please post
cheers
nikki
If using com 1 make sure you have beams switched off in settings/connections, also disable any external keyboard driver if present as this too will take com 1.
I cant find a pinout for the 16pin plug and was wondering where I can find it, but I dont think that would help me anyway.
I have a requirement for a Standard Serial port (RS232 type not USB).
Does anyone have any experience/advice on how to do this?
Do USB to serial adapters work?
Is there a mini SD to Serial port that anyone makes?
Any other ideas?
Thanks in advance
Jon
Have a look at something like this http://www.roalan.com/Bluetooth Wireless Serial RS232 Converter.htm you will have to code your own application for the phone to make use of it, I have used a similar device with my Athena - Mike
Thanks,
I am trying to avoid a wireless conection. What I am trying to do is use the Athena as a moving map for a glider. To do this I need to make use of an external GPS NMEA source. The software I am using works fine on a pda that has a std com port, I am hoping for a 'quick fix' to try it on the athena.
will this work, I havent looked for drivers yet tho!
http://www.roalan.com/USB to Serial RS232 RS422 RS485 Converter.htm
Cheers
Jon
I have to ask the obvious question though, why not use the internal GPS receiver in the phone? - if the application software you have isn't capable of switching the internal GPS on (some struggle with this) use Fransons GPS Gate to activate the inbuilt receiver and configure the ports, I would expect the inbuilt GPS to work quite well in a glider to be honest, and it does output NMEA data - what mapping application are you trying to use?
USB / RS232 converters are not the way forwards though, the mini USB port on the device is not a true USB port, it will not work with this sort of hardware, even if it did the converters generally don't work well as they don't use standard RS232 voltage levels - Mike
A good question. The external NMEA source contains additional sentances for things like accurate air speed and vertical speed that comes from a flight computer making measurements of the air. This is used for some of the calculations on the PDA. The software I will probably use is called SeeYou http://www.naviter.si/products/seeyou-mobile.php. There are several others, but this seems to work best in Landscape which is how I want it.
The internal GPS works fine with the software just to give map position.
I have managed to get it working by emulating a NMEA output over Bluetooth from a PC. I will try something like the Bluetooth to serial adapter and see what happens!
Cheers
Jon
Hi
I am having a problem with my Wizard. This weekend i was taken by surprise by a downpour and my phone somehow got wet. At first it didn't seem like a big deal, everything seemed to work just fine but on monday when i got back to the office and tryied to sync my phone i've noticed the problem.
The thing is that it can't get an ip, the connection (usb) reports limited or no connectivity and can't get an IP thus, can't sync. The phone runs ok, i can get it charged;
Can anyone help?
I dont think so that its because of it getting wet, it might be a problem with your ROM or PC but still wait for advice by someother Senior member too.
There are two main possibilities:
1) If your computer can't seem to connect to the device via USB (it won't show up in the Device Manager, and may trigger an malfunctioning device error), it's possible the water short-circuited your onboard USB controller. This might render a data connection via USB to the host computer impossible while still allowing the device to charge off the Slave voltage pins.
2) If you can connect to your wizard and the device (if, for example, it shows up in the Device Manager), that means that serial communications are working just fine, as, if your computer was able to interpret the USB Device ID, your onboard USB controller is most likely not damaged. In this case, I'd probably try screwing with your ActiveSync settings, and focus on undoing anything you've changed recently, like USB drivers on the host computer or ROM on the device.
I'm having a hard time getting my Titan to be able to activesync over wireless with bluetooth. I've read every "how to" and everything is pretty straight forward, I just run into a few problems when things don't happen the way they should be according to the walk throughs.
Problem number 1: When pairing for the first time, Either from the Titan or from the PC. THe list of services on the Titan are, Wireless Stereo, Serial Port, and Headset. I've never seen an activesync service pop up when pairing, tried refreshing the services a few times and still no luck. On the PC end, I can select it as a service and it will create a bluetooth com port. Great. But still no activesync profiles =\.
Problemy number 2: So I tick the Serial Port option on the titan and try to add a new port that matches the one created by my bluetooth stack. Most of the time it is com4. I try making a new com 4 port on the PPC, and it says it cannot be created.... ugh... The only ports that it looks like I can make are 8 and 9. So after playing around with a few settings I manage to a bluetooth serial port on com 8. So everything *should* be in order. Activesync settings of allow connections... on com8, Windows Mobile shows I have an outgoing com8 and my BT stack shows my port is on com8. still, no luck.
I read somewhere that a certain build had issues with Activesync over bluetooth. Not sure when build I have. I'm using No2Chems 5069k build. Not a single problem until I couldn't get this working and noticed a few things weren't happening the way they should. Any ideas? Does that build just have bluetooth issues? cause I know a few of the 5069 series had bluetooth problems.
THanks!
Have you had the devices syncing before (with the USB cable)?
Try this: http://wiki.xda-developers.com/index.php?pagename=AS_BT
You need to create a COM Port on the PC first, and then initiate the connection between the two devices.
Hi,
I am attempting to connect a bespoke USB device to the athena.
The bespoke device is recognised as both a mass storage device and keyboard in windows XP.
But when plugged into the Athena, the red charging light turns on. But it doesn't appear in file explorer.
One time (though I havn't been able to reproduce it), a dialog box poped up asking me if I wished to format a device. The bespoke device uses FAT12, does anyone know if Windows mobile even supports FAT12?
Also, is there "add-remove hardware" type funtionality in windows mobile? Should I have to reboot each time or should new hardware be picked up straight away?
Any help would be greatly appreciated.
How is it connected - through the built-in usb port or through the 4-in-1 cable?
I'm using the 4-in-1 cable.
One interesting thing, if I reboot it with it plugged in. It hangs for a little while on the windows mobile splash screen. Then if I press the power button once and then again to turn the screen back on. For a few seconds a "Hard drive" is in explorer.
The bespoke device also is detected as HID device and a number of other USB devices (but using only built in Microsoft drivers) when plugged into a PC (i'm in contact with the hardware vendor to geta concise list). So my other theory is that it hangs trying to find the other drivers (if FAT 12 is supported at all).
Ok, I started wondering when you said the red charge light came on. I was wondering if you were plugging it into the sync/charge port and somehow the device was backfeeding some energy, tricking the device to go into charge mode.
I think you are on the right track. Windows Mobile has few built-in drivers, so the delay probably is due to a search for non-existent drivers. If the manufacturer doesn't have WM drivers, you might try looking at other manufactuers with similar devices that do have WM drivers and try them. Others here have gotten peripherals to work that way.
I just found this page which discusses the file system used by WM. I haven't read the links on that page yet.
http://blogs.msdn.com/jasonlan/archive/2007/03/13/what-file-system-does-windows-mobile-use.aspx