reala10001986 / time-circuits-display Goto Github PK

Apologies if I am being completely thick - but recently when trying to unzip the downloaded sound pack it, it is only produces a 'TCDA.bin' file, rather than the audio files for the SD card. What am I doing wrong?

Cheers!

Hello,

As seen in part III (in the train scene when Marty enters OCT 27 1985) after entering the date on the keypad, every single digits are displayed one after another from left to right as opposed to part I [DAY YEAR HOUR MIN] (altogether) then [MONTH].
And the AM/PM indicators are reversed (PM on the top).
Also, the keypad sounds are slightly different, I don't know if they are available anywhere ?

It would be very cool to have this option ! :)

Thank you for the great work

Hi

I would ask if it possible to do some change in firmware;

How you know in my old previous mail, I have installed sensor light and temperature sensor in the TCD and they works good;

When the TCD is in night mode (low light), only the present time is ON, but I'd like to see in the night mode also a temperature in speedometer (with different brightness)

Ii'd like to change brightness of speedometer in 3 cases:

• speedometer in time sequence (as now)
• temperature on speedometer (as now)
• night mode - temperature/speedometer (new function. now speedometer is off in night mode )

Thanks if you want to implement this function, otherwise your work is fantastic just now;

bye

Fabio

is it possible to have a schematic, how to connect light and temperature sensor ?
e.g. for TSL2561:
scl to i2c scl ?
sda to i2c sda ?
int not connected ?
no resistor or capacitor?

in the code where I can change the address for various type of compatible sensor ?
can i use sht41 instead of sht41, it have yhe same address ?

can i connect 2 sensor in the same I2c connector ?

thanks

At some point recently AUTO beep mode stopped working after time travel.

If beep auto beep mode 2 or 3 is active, the beeps are muted after time travel - the 30 or 60 second mute delay is not honored. If a return from time travel (push and hold 9) is activated the beeps and time delay mute do work as expected.

The beeps appear to work as expected in all other unmuting situations (fake power, reboot, enter of new date, etc).

Good evening,
the goal is just to have a time counter over a year, to count down the time until a date entered via the keyboard.
For the alarm the goal is to tint the bells of the clock instead of the sound of the alarm.
THANKS.

Hi,
always me :)

I made a home made flux capacitor and I connected it with IO14;
I have some problem to synchronized the TCD with my flux capacitor effect, is it possible to have the time(duration in seconds) from start (IO14 High)?:

• first time departure time / present time/destination time blinking
• all display off first time
• display disruption
• all display off second time
• display ON

thanks if it possible

bye
Fabio

Hi there

Running version A10001986 (JAN062024) with the most recent sound pack installed. the beep sounds on startup are not running consistently. When set to 30 secs, 60 secs or On, the TCD will beep a few times, skip a beep, continue beeping a few more times, skip again, etc. I've tried refreshing the firmware, reinstalling the sound pack and a different SD card.

Other sounds are working, and music can be played, however I have just noticed that every once in a while, hitting the enter button will cause the white light to flash, but no there is no sound - it is intermittent. It is the same with the keypad presses - sometimes there is no sound. I've not noticed this previously and the only changes I have made recently is the firmware, and changing the speedo display type.

Cheers!

On the TCD:
As long as I can remember, this has been the case in Night Mode. The ” : “between the hour and min display is “OFF” when in Night Mode. During normal operation these flash once per second. I can understand not having the flashing during Night Mode, but would it be possible to have the lights remain ON without blink during Night Mode? This would make it easier to at a glance identify the hour and min digits when it is dark (and you are half awake if using this as a clock).

On the TCD and Flux Capacitor:
Press and hold #9 is back to “real time”. Not sure if the intent of this was to “time travel” back like a standard travel event, or to just bring the TCD back to “default”. Currently it runs a shorter time travel sequence compared to when you press and hold 0 for a traditional time travel sequence. Additionally it DOES reset the beep timer for the 30/60 second duration upon finishing the cycle. However it DOES NOT trigger activation of the Flux Capacitor (over BTTFN). So with the shortened sequence and now lack of Flux interaction - to me if this is more of a “soft reset” back to “real time”. I would suggest it be made to either (fixed or optionally) respond like a “normal” time travel OR with similar visuals and sound that occur when hitting enter after entering a new destination date (no actual travel sequence, just display reset - with or without Auto Beep reset?!). Bottom line it just seems like press and hold 9 is and has been operating in strange way (somewhere between a full time travel and soft reset of the current time), which is even more unusual now with the addition of the Flux Capacitor and lack of interaction with the Flux Capacitor. For me no travel event, and no Flux interaction is fine - soft reset get me back "home", but that is just me. Right now it is in a strange form somewhere in the middle and I think it should be solidified as a full travel, or just a display reset.

On the TCD and Flux Capacitor:
I like the way that the Beep Auto mode works. I also like the Wakeup/Sleep mode interaction between the TCD and the Flux (Night Mode, push and hold 4 for wake and sleep), etc. However I think that the TCD should also “wake up” the display and/or sounds on the Flux Capacitor when a new date is entered on the TCD keypad (which currently restarts the BEEP when in Auto mode). When Auto Beep is idle, the TCD beeps are silent, and the Flux Sounds and/or Display are likely idle/off as well. Currently when you enter a new destination date on the TCD and hit enter, the beeps start on the TCD, but the Flux sits domant (until time travel starts). I think it would be nice to see the visual and audio of the Flux follow the TCD beep behaviors - and wake up the sounds and display functions of the Flux Capacitor. The Flux has Screen Saver and Sound Mode, maybe sound mode settings can supersede Screen Saver when tied to a TCD? Not sure, but it would be nice to keep the option of having visuals stay active with or without sound and have influence from the TCD that matches Beep Mode of the TCD. Bottom line it would be nice to have the Flux wake up prior to the start of the time travel sequence. Maybe an option to tie or separate display and sound timers on the Flux, and then a simple "wake-up/sleep" signal when beeps @ 30/60 are engaged and disengaged - keeps the stand alone flexibility and enables sound and/or visual when the TCD beeps are activated.

Good evening,
here is a small list of request for evolutions:

• have the possibility of programming a countdown but with a programmed day-Month-year and hour-minutes.
• Is it possible to have an output for the programmed alarm and have the choice between the sound or the active output.
  Thank you for your work.

Would it be possible to have an "on/off/auto" setting for the beeps? On and off would be as they are today, Auto would turn the beep on for a selectable amount of time - after an "event" - travel, after power on, after touching the keypad.

So let's say "auto" is selected, and an idle timer of 60 seconds is set. The beeps will occur/start when the TCD is powered up, keypad entry occurs, a time travel occurs, etc. Beeping would continue until 60 seconds after the device is "idle", and then stops. Basically an idle timer/timeout for the beeping sound. Idle timer could be a selection of hard coded options like the time rotation setting (15/30/60 seconds), or a user defined time.

This might create a bunch of work because of the idle timer concept - like needing to track/reset the idle timer when keys are pressed. Maybe limiting it to start for the pre-set amount of time only after a time travel and "power up" from Fake off and actual off.