Assistance with identification,

[Tucnak]

Assistance with identification, this is in a two AA battery pack powering a string of led's. There is a switch that is an on/off only. When on the led's are on for 3 hrs and off for 9 hours. I would like it to be on for 6hrs and off for 18hrs.
Is this possible ?
What would I need to add/change
Datasheet if possible.

 

[Ivan Bliminse]

First off.... What's it attached to, i mean there isn't a lot to go on with this pic. Maybe expand your picture and supply more details..?

 

[TheLostSwede]

I think you might have better luck at some kind of electronics forum.
Also, that's most likely some xinese chip that you'll never find out what it is, less so any specs of it.

 

[ShrimpBrime]

I think you might have better luck at some kind of electronics forum.
Also, that's most likely some xinese chip that you'll never find out what it is, less so any specs of it.

It's an RTC chip. (Bios chip).

Possibly a firmware update, but who's to know. Make and model of the card would be most helpful.

Would have to edit the bios if there isn't a firmware update to accomplish what OP is asking. Of course simply an assumption. The timer is set in stone otherwise.

 

[Bill_Bright]

Pretty sure that is a PROM (programmable ROM) - meaning write once, read many. This means the code is permanent, cannot be erased and cannot be changed. The only way to change the timing of the string of LEDs is to replace the PROM with a different one.

So, as ShrimpBrime noted, the time is set in stone.

Or get this.

 

[ty_ger]

It's gotta be a microcontroller of some sort. It could be reprogrammable, or maybe not, to save costs.
It would be a good project to learn to program an ATtiny85 to replace it.
One problem you are going to see is that the internal clock will drift over time, so you will keep needing to reset it to a certain start time over the period of weeks or months.

 

[Bill_Bright]

These are not really clocks. That is, they don't know or tell the time of day. They are just counters. They start counting when you turn them on (or insert the batteries - depending on type). And they are actually pretty accurate - as long as the batteries are good and they are not subject to temperature extremes.

I have a battery operated, lighted Christmas wreath that is 6 hours on, 18 off. It goes up 1 December and comes down 1 Jan. I "set" it to go on at 5PM. I have to say, this last season, I didn't notice any drift at all after 1 months of use. But let me quickly add, however, that this wreath hangs indoors where the ambient temperature remains consistently at normal room temperatures. If hung outdoors here in Nebraska, with the potential for subzero temps, I suspect it surely would drift.

 

[ty_ger]

In computer terms, the 'clock' is a timer which the core uses to regulate its frequency. It's common to hear someone say that a computer is 'clocked' to 4ghz or is 'overclocked'. These cheap chips can be bought for less than a dollar, and their timer oscillator is usually just a cheap RC circuit of some sort and loosely works as expected. To make them more accurate, you need to incorporate an external crystal or realtime clock, which is just big and overkill for this application. I was just making the user aware.
If the clock is 32khz, and drifts by 100hz, it may be off by a few seconds per month. Maybe better, maybe worse. I have seen them drift by a minute in a month or two.
You also need to be aware of overflows if counting a timer for a long time, and handle it as needed. That too is a lot easier to deal with when using a realtime clock to handle your events.
I made a timer, waterer, and air monitor device, connected to wifi, for a greenhouse and needed to incorporate an external realtime clock to make it perform to my expectations longterm. It's really a matter of how picky you are.
I don't know the user's application, but I imagine they might be annoyed if their lights are off by half an hour a year or two later, or 'randomly' stops working predictably every X number of days when their mishandled timer variable overflows.