Omega Owners Forum
Omega Help Area => Omega Electrical and Audio Help => Topic started by: zYx on 05 January 2020, 12:15:12
-
Hi all,
In the past I have had issues changing time manully as if you left it for a period of time, time was off by a few minutes. The only way for me to change time manually was to disconnect the battery for 20 minutes or so. I had to do this a couple of weeks ago and I was able to update time, but for some reason the date stays at 21/05/2000 and can't change it. When I try to adjust it, as soon as I press OK, I can see the date resets itself to 5/2000...
The date does change itself, i.e., it will change to 22/05/2000 tomorrow etc.
What else can I do? Is there any way to reset it? i.e., the radio stations always stay on the list. Maybe there's a "factory reset" option somewhere?
Any suggestions would be greatly appreciated.
-
Is the RDS working? That may be overriding it.
-
Is the RDS working? That may be overriding it.
Yes RDS is working and I tried enabling/disabling the auto time adjustment and still nothing :(
I’ve disconnected the battery again but this time entirely whilst it’s charging.
-
Unfortunately, you need to listen to Radio 2 for a while. Should sort itself out ;)
-
Unfortunately, you need to listen to Radio 2 for a while. Should sort itself out ;)
I’ve just been playing with it in the last hour or so. When I ‘unplug’ the battery, I can set time and date from the clock buttons (when the radio is of, ) and it says there until I turn the radio on. It then resets itself back to 21/05/2000. I don’t know how to reset all radio stations so I manually tuned into a non existent frequency and programmed 10 items on the list to that frequency ensuring the RDS was off on each station, on both U bands.
I even changed the band (disconnecting the battery each retry) and no matter what I do, the radio starts scanning all available FM stations, no matter what band I’m on, and sets itself to Radio 4. I think this is when the date changes back to 2000.
I’ll tune in to Radio 2 and let’s see what happens.
At least time is correct. <facepam>
-
The NCDC's occasionally corrupt their eeprom.
If yours has done this - though normally is loses its pairing as well - it needs depairing, reprogramming, re-pairing, then retesting.
-
The NCDC's occasionally corrupt their eeprom.
If yours has done this - though normally is loses its pairing as well - it needs depairing, reprogramming, re-pairing, then retesting.
I have a second colour display that works for up to 1 minute and the displays “display safe”, but when it works I can see the same date issue.
Are there any tools available to play with EEPROM other than tech2?
-
The NCDC's occasionally corrupt their eeprom.
If yours has done this - though normally is loses its pairing as well - it needs depairing, reprogramming, re-pairing, then retesting.
I have a second colour display that works for up to 1 minute and the displays “display safe”, but when it works I can see the same date issue.
Are there any tools available to play with EEPROM other than tech2?
The issue is with the NCDC, not the CID/GID.
Getting a dump from the NCDC eeproms might be possible in circuit, though my attempts have been unsuccessful - probably due to an awful lot of pins for the clip. Unsoldering them is probably the best way, but a one way street if you damage it.
I doubt you'd be able to interpret the contents to something meaningful, usually the code section on that type of device is encrypted. Its likely that the low byte is stored on one eeprom chip, high byte on the other.