Thanks Larry! I'll await others, and Scott's responses too. Regards,
-Frank C. On Sep 1, 2010, at 4:07 PM, k7ybz wrote: > If the memory has gone bad, and it appears it has, I would contact Scott > Miller at Argent Data. He has been very good about such things and would > either repair or replace the unit. He normally monitors the group and will > chime in unless he is playing with ballons somewhere. > > Larry > K7YBZ > > --- In [email protected], "Frank C." <fchri...@...> wrote: > > > > Larry, > > > > The unit is barely a year old with plenty of power to it. I've tried the > > option you said along with disabling turbo and no results. > > > > What would I do if the flash memory has gone bad? > > > > Regards, > > > > -Frank C. > > > > On Sep 1, 2010, at 15:06, "k7ybz" <k7...@...> wrote: > > > > Frank, > > > > How old is the unit and are you trying to program while the OT2 is on a > > good 12V power supply capable of supplying at least 1 amp? > > > > One way to reprogram is via the opening window of the otwincfg that selects > > the comm port. Check the box in the lower left corner to "Erase device and > > load new firmware". This should get you back to the starting configuration. > > Once that completes and the config program actually opens, go ahead and put > > in your specific configurations settings. If that doesn't work then the > > flash memory has gone bad. > > > > Larry > > K7YBZ > > > > --- In [email protected], "Frank C." <fchrist2@> wrote: > > > > > > Sorry for the two bad emails, my phone glitched. > > > > > > As for the update the address is now staying at 0x0880 and 0x0ec0 > > > > > > Regards, > > > > > > -Frank C. > > > > > > On Sep 1, 2010, at 14:36, "Frank C." <fchrist2@> wrote: > > > > > > Now it > > > Sp > > > Regards, > > > > > > -Frank C. > > > > > > On Sep 1, 2010, at 14:32, "Frank C." <fchrist2@> wrote: > > > > > > > > > I tried updating my settings via OTWINCFG and it failed 2 times. Well I > > > ran into a stumbling block. Got the "unable to verify block at 0x?????" > > > message after going to re-run the firmware. > > > > > > Any help or ideas? > > > > > > Regards, > > > > > > -Frank C. > > > > > > >
