I've just completed a 2,000+ mile trip from Rockport, TX, to Cedar Rapids, IA. Yes, I know it is not 2,000 miles between those two points, but we took the scenic route!The highlight: a visit to Big Bend National Park! The peaks called "Mule Ears" is pictured here.
I became a bit more proficient at operating the device. I also discovered that some "features" were a bit cumbersome ---so cumbersome that I didn't/couldn't use them. And some functions just didn't seem to work correctly.
Some details:
* Cumbersome: Routes
I just couldn't seem to get a decent route put together at the beginning. Sort of like squeezing a balloon: squeeze it in here, and it bulges out there. Later, I did get an 800 mile route to work, with only a few problems and surprises.
I'll post some comments on route building which may help you. But not now.
* Faulty(?): Computations
When going to a destination or waypoint (Lowrance calls them "vias") 300 miles away and travelling at a constant speed of 60 mph, it seems almost obvious that it would take 5 hours, if you maintained the speed, etc., etc. Chances are that it will take longer than 5 hours in the real world. And there is almost zero chance that you'll do it in less than 5 hours, such as 4+20 or even 4+40!
Yet my iWay500c consitently reported the required time enroute as less than the distance divided by the rate!!!
Certainly yours must do this, too. Can you offer any explanation?
* Usefulness: Great
In spite of these things requiring explanation, I really do like the machine! Even though we were not in any really tricky situations, the iWay500c is without question a great helper to have along!
If I were a trucker, I would have one without fail.

No comments:
Post a Comment