pjpalmer
Newbie
Posts: 8
|
 |
« on: June 18, 2006, 11:07:57 AM » |
|
Trying out the Beta 2.0 - Using an IPAQ 5555 and the Navman 3450 gps sleeve (fixed last issue with 1.1.5). The auto detection process does not find the GPS sleeve. should be on COM4 @ 57600. The detection process scans the com ports but is done in less than a moment.
|
|
|
|
|
Logged
|
|
|
|
|
Nathan
|
|
« Reply #1 on: June 19, 2006, 08:17:18 AM » |
|
I'm not sure why this is failing. Previous problem was fixed when you could manually specify 57600 baud. Device Detection checks at 57600,38400, and 4800 baud.
Make sure that the GPS is nto tied up in anything else, including BackCountry Navigator 1. To do this, soft reset the pocket pc and then run BackCountry Navigator first thing. I'll see if there are other parameters to tweak here.
|
|
|
|
|
Logged
|
|
|
|
berion
Newbie
Posts: 1
|
|
« Reply #2 on: June 24, 2006, 08:23:55 PM » |
|
Hello, using Ipaq 3835 with bluetooth, but Beta goes into detect mode for GPS and takes forever to find GPS. Is there a manual way to configure the GPS settings?
Thanks
|
|
|
|
|
Logged
|
|
|
|
|
Nathan
|
|
« Reply #3 on: June 29, 2006, 11:35:47 AM » |
|
I'll look more into what is tweakable here. There are some options that go with device detection; we just need to put together a form to control some settings.
It is worth noting that if bluetooth is on when starting the program, it can get an early start on device detection and can often find the GPS by the time you need it.
|
|
|
|
|
Logged
|
|
|
|
|
Nathan
|
|
« Reply #4 on: July 11, 2006, 02:49:36 PM » |
|
I thought baud 57600 was being checked by default, but I found this was not the case.
I've added 57600 baud rate to device detection in version 2.0.6, available now.
|
|
|
|
|
Logged
|
|
|
|
johros
Newbie
Posts: 7
|
|
« Reply #5 on: July 23, 2006, 04:42:49 PM » |
|
???I have a MIO 550 with build in GPS using COM4 and it is failing to detect it and yet Microsoft Streets can. Any solution?
|
|
|
|
|
Logged
|
|
|
|
|
Nathan
|
|
« Reply #6 on: July 24, 2006, 07:05:21 AM » |
|
Do you know what baud rate it connects at? ie 38400. Be sure the COM Port is not busy with another GPS program.
There was a fix related to MIO 550 in 2.0.6 and later. This is the text from our logs:
FIXED: On Windows Mobile 5.0 devices, GPS devices which connect at 38400 baud would not connect after the first connection due to a bug in the GPS Intermediate Driver. A stable workaround has been implemented, resolving this issue. Devices such as the ETEN G500 and related integrated-GPS hand-held devices should have better performance with this build.
If you are experiencing this with the latest build, then I will look more into it when I get a chance.
|
|
|
|
|
Logged
|
|
|
|
johros
Newbie
Posts: 7
|
|
« Reply #7 on: July 24, 2006, 07:55:49 AM » |
|
I am using the Beta version 2.0.7 and it says it detects the com20 at 57600 baud but it is on com4. Would 2.0.6 be different? If so, I would be glad to purchase it if you would refund if it did not work. thanks!!  |
|
|
|
|
Logged
|
|
|
|
|
Nathan
|
|
« Reply #8 on: July 24, 2006, 10:13:40 AM » |
|
No, 2.0.6 wouldn't be different from 2.0.7 in this regard. I'll have to check with some people to see why that fix didn't work for you.
Com20 and 57600 baud are just the last port it tried. Automatic detection tries all ports at a few different baud rates.
When it has completed detection, is there anything in the select box just below the satellite image? If there is, you can push connect.
If you still have time on your trial period, I would wait to buy until you are sure we have a fix for this.
|
|
|
|
|
Logged
|
|
|
|
johros
Newbie
Posts: 7
|
|
« Reply #9 on: July 25, 2006, 06:41:25 AM » |
|
Still no luck with Mio 550. Does not detected com4. I downloaded oziexplorerce since, like your program, I like to download good topo maps and it recognizes com port. Your program is easier to use. Let me know if you come up with a solution. john |
|
|
|
|
Logged
|
|
|
|
|
Nathan
|
|
« Reply #10 on: July 25, 2006, 09:32:04 PM » |
|
The forum topic "Window Mobile 5 Device Settings" just might help you.
If it does not, I'll be able to do more investigation later this week. I'm still waiting to hear back from someone.
|
|
|
|
|
Logged
|
|
|
|
johros
Newbie
Posts: 7
|
|
« Reply #11 on: July 26, 2006, 04:12:56 PM » |
|
I already had access box checked and I tried unchecking it. I have a build in GPS (no bluetooth) and hardware is defaulted to com2 and data to com4. Tried other com ports without success. I get "device detection completed" but no device listed and connect does not connect. It does work with Microsoft Streets (poor topo maps) and Oziexplorer (expensive and hard to use) Thank you so much for working on the problem. john |
|
|
|
|
Logged
|
|
|
|
johros
Newbie
Posts: 7
|
|
« Reply #12 on: July 28, 2006, 02:41:47 PM » |
|
:)Good news and bad news. I downloaded 1.2.1 and it worked if I used Com2 which is the "hardware" port but not on the data port com2 which is fine by me. However, I really want to use version 2.. Does this help you figure out what is wrong with the automatic configuration?
|
|
|
|
|
Logged
|
|
|
|
|
Nathan
|
|
« Reply #13 on: August 01, 2006, 07:22:56 AM » |
|
Yes, this should help.
I'm hoping this will be resolved either with some minor fixes we're doing for devices that return nulls, or by allowing one to specify exact port and baud rate. We are working on something for later this week.
|
|
|
|
|
Logged
|
|
|
|
|
Nathan
|
|
« Reply #14 on: August 09, 2006, 09:55:11 PM » |
|
2.0.8 has a fix for detection when devices return nulls.
If this fails to help, we can do something to explicitly set the baud rate and port.
|
|
|
|
|
Logged
|
|
|
|
|
OtterBox Cases
Author
