I think I might have tracked the problem down, just need to re-install the
T2-301 in the truck to test it this weekend.
Found a cracked solder joint on the radio's DE9 connector, once I resoldered
the points it took a download and responded in seconds to ot2wincfg connecting.
Since I loaded new firmware, I had to recreate my switching script and also had
a couple of questions...
With the GPS position set to GPS and "Save" it writes the position to memory
every 30 seconds... Is this written to flash so subject to possibly wearing out
the memory?
ALso which would be more proper or does it really matter?
If Profile 2
Do Once
Exec "POWER OFF"
End Block
Else
Do Once
Exec "POWER ON"
End Block
End Block
or
If Profile 1
Do Once
Exec "POWER ON"
End Block
End Block
If Profile 2
Do Once
Exec "POWER OFF"
End Block
End Block
Thinking about the flash wearing out, I think I'll have to play with the power
control settings in each profile to see if I can do it there instead, I think I
saw a post about setting a -1 enable time to alwas enable it, time to start
playing.
Garrett
VE6RKY
--- In [email protected], "gsdatplace" <sp...@...> wrote:
>
> Running into a little problem here...
>
> I have a T2-301 connected to a Nuvi 350 in the truck, with a minor mod to
> enable external power switching on it.
> Its been working great for around a month, but since this last weekend its
> started acting strange...
> Its still following its script, when the trucks running and the voltage comes
> up it switches to profile 1 and powers up the nuvi, but it usually shows a
> communications error and it won't beacon or respond to any commands, so I
> fire up OT2WinCfg, and after around 30-40 seconds it will finally connect.
> Looking at the settings at this time, its usually switched to fixed position
> vs GPS, and Port A switches to KISS vs what it was set at AUTO, Port B is
> still set to Garmin. I load the proper config or make the changes, write to
> the unit and it will go back to normal for a few hours, then lock up again.
> Sometimes on connecting ot2wincfg it won't connect, or it will come up with a
> "invalid config or firmware" error and download and flash the unit, sometimes
> on a write of the config it comes up with a "writing block ?x???" error, but
> after a power cycle or two it'll connect again and come up with the invalid
> firmware message.
> I'm running the latest dev build, but have been with no problems so far and
> as far as I can see all the connections and solder work on the board look
> good.
>
> Any idea on where to start looking for problems?
>
> Garrett
> VE6RKY
>
> Hate to say it: "You were right James". I should have sold it to them as a
> backup cutdown device... Then I could have had a few new ones!
>
