Now there you go! What we need here is a little rationality! Jim----- Original Message ----- From: "Chris Grabowski" <chris@xxxxxxxxxxxxxxxx>
To: <gps-talkusers@xxxxxxxxxxxxx> Sent: Thursday, December 13, 2007 7:15 PM Subject: [gps-talkusers] Re: BrailleNote GPS vs Voice Sense GPS
Hi all, I'll do the side by side tomorrow. Chris On Thu, 13 Dec 2007 19:06:44 -0800, "Kevin Chao" <g.unit89@xxxxxxxxxxxxx> wrote:Jim and Charles, very good points regarding the timing of the route creation. We don't need precision of a millionth of billionth of a second here. I created the route on the PK and it came out at 1 minute and 18 seconds. I hit the stop watch created the route thenhit the stop watch off on the PK. We will see what the VoiceSense gets. Kevin -----Original Message-----From: gps-talkusers-bounce@xxxxxxxxxxxxx [mailto:gps-talkusers-bounce@xxxxxxxxxxxxx] On Behalf Of Charles LaPierreSent: Thursday, December 13, 2007 6:53 PM To: gps-talkusers@xxxxxxxxxxxxx Subject: [gps-talkusers] Re: BrailleNote GPS vs Voice Sense GPSn>For this even if the difference is a second it won't matter that muchits not like we are clocking FLOPS or something. A 60+ mile route will have enough of a difference that a stopwatch will be more that enough to determine how fast both calculate the same route. I would imagine that the Voice Sense having 100 MHz faster processor will hands down beat the BrailleNote in route creation, my guess is there will be probably a 5 to 10 second speed difference on the Voice Sense. Charles. At 06:41 PM 12/13/2007, you wrote:Actually, neither are a good solution. Depending on the OS's (Did someone say Windows CE?) you should run a benchmarking tool. Or, maybe that's to complex, maybe if again it's a windows derivitive, you could employ a port of the unix time command which literally times the exact start and stop of a given process. I'm not sure how open these devices are though, my gut tells me not very but I've been pleasantly surprised lately. I'm rather thinking that the results may be similar enough that human measurement might not provide enough resolution. At a minimum, precision is always a good thing. (tm) :) ----- Original Message ----- From: "Jim Gammon" <jgammon1@xxxxxxxxxxxxx> To: <gps-talkusers@xxxxxxxxxxxxx> Sent: Thursday, December 13, 2007 6:16 PM Subject: [gps-talkusers] Re: BrailleNote GPS vs Voice Sense GPSSounds great, but to be fair, you should use a stopwatch to time the route creation in both cases and see how long each unit takes. Counting beeps is probably not accurate as they may go faster on the Voice Sense due to the faster processor. Jim ----- Original Message ----- From: "Raul A. Gallegos" <raul@xxxxxxxxxxx> To: <gps-talkusers@xxxxxxxxxxxxx> Sent: Thursday, December 13, 2007 12:40 PM Subject: [gps-talkusers] Re: BrailleNote GPS vs Voice Sense GPSHi. On the Voice Sense I put in Sendero as the virtual position and the Lighthouse as the destination. It showed that the destination was 64.37 miles southwest from Sendero. The Voice Sense plays progress tones, but I don't think they are three seconds apart. I created the route using two slightly methods. The first was using the micro hard drive CF card with the whole West of the US loaded. The second test was with only the California maps loaded in the flashdisk of the Voice Sense. In both cases the result was the same. Creating a vehicle route took 57 beeps. The route had 364 waypoints. To be honest, this is longer than what I would have thought. At least when I've created many routes in Denver, Chicago, and Fort Wayne, 60 or so mile routes do not seem to take as long, but I don't know if POIs or map areas have something to do with this. So, there is the Voice Sense side of things. Kevin Chao said the following on 12/13/2007 1:14 PM:If we wwant to figure this out we can run a test. Let's say we just have the maps for California loaded and create a route from Sendero Group to the LightHouse and see what the difference in speed is. Raul, I am not sure if there is some progress tone on the Sense Nav. On the Sendero GPS, there is a swoosh that occurs every 3 seconds to indicate some progress. Starting: Sendero Group 11188 Maple Lane Davis, CA Ending: LightHouse 214 Van ness Ave San Francisco, CA Could someone perform the route calculation on the BrailleNote and someone on the VoiceSense? We then can compare notes. It might be faster on the VoiceSense as Alex suggested as there is more processing power and RAM on the VoiceSense. There are many variables that aren't accounted for, but this is just a general comparison. Kevin -----Original Message----- From: gps-talkusers-bounce@xxxxxxxxxxxxx [mailto:gps-talkusers-bounce@xxxxxxxxxxxxx] On Behalf Of Judy W Sent: Thursday, December 13, 2007 8:58 AM To: gps-talkusers@xxxxxxxxxxxxx Subject: [gps-talkusers] Re: BrailleNote GPS vs Voice Sense GPS Isn't the chip in the Braille Sense faster? Maybe someone from sendero could tell us if route calculation is noticeably faster. Judy -----Original Message----- From: gps-talkusers-bounce@xxxxxxxxxxxxx[mailto:gps-talkusers-bounce@xxxxxxxxxxxxx]On Behalf Of Raul A. GallegosSent: Thursday, December 13, 2007 10:47 AM To: gps-talkusers@xxxxxxxxxxxxx Subject: [gps-talkusers] Re: BrailleNote GPS vs Voice Sense GPS Hello Eric. I'd be happy to comment on the Voice Sense side of things although I'm not sure how much my comments will mean since I've onlyused the Voice Sense and not the Braille note. The things i can commenton are mainly things which I've seen from reading other user experiences, but none from me personally. Eric Brinkman said the following on 12/13/2007 11:26 AM:Hi, I am curious whether anyone who has used both the BrailleNote GPS and the Voice Sense GPS can comment on any differences between the two. Thanks in advance. Eric-- Raul A. Gallegos .. GW Micro Technical Support Voice: 260-489-3671 .. Fax: 260-489-2608 WEB: http://www.gwmicro.com FTP: ftp.gwmicro.com-- Raul A. Gallegos .. GW Micro Technical Support Voice: 260-489-3671 .. Fax: 260-489-2608 WEB: http://www.gwmicro.com FTP: ftp.gwmicro.comCharles M. La Pierre CTO Sendero Group, LLC Lat. 37 15' 25" N Lon: 121 53' 04" W __________ NOD32 2722 (20071214) Information __________ This message was checked by NOD32 antivirus system. http://www.eset.com