
Originally Posted by
kamold
Ok, just went through the adaptation channels, coding and all setup/test mode options, there doesn't appear to be anything that would control this.
Anyone want to be a guinea pig and try an upgrade to 5238 to see if it corrects it? I am on 5238 now but I have not ever seen these reported symptoms on any level of firmware from 26xx to 5238, with everything in between on my unit....
Bookmarks