can someone give something for totally green?
Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tam
. Now I am struggling to put the character generator in the eprom, and I will not fit in any way - and the program memory is not enough (bascom limit to 4kB). Certainly it will end up with switching to C or rewriting in assembly language - great material for learning about the construction and handling of a slingshot.witm1212 wrote:Oh, a question for the author: why didn't he use hardware TWI to power the drivers ??
. The control of the 33 LEDs with this pin was not dictated by any serious reasons. Just like that, the question of freedom, I had to hook up somewhere. If someone uses my schematics, please check if the board has a 10k resistor pulling the SQW line of the RTC under the VCC, because I'm not sure if I updated the board. And if someone has already made a PCB, there is no tragedy because, fortunately, the path system allows you to solder this resistor without dedicated pads (I did it).
#include
#define F_CPU 10000000
#define __OPTIMIZE__ s
#include
#define set_clk PORTB |= 0b00000001
#define clr_clk PORTB &= ~0b00000001
#define set_data PORTB |= 0b00000010
#define clr_data PORTB &= ~0b00000010
#define set_le PORTB |= 0b00000100
#define clr_le PORTB &= ~0b00000100
#define set_oe PORTB |= 0b00001000
#define clr_oe PORTB &= ~0b00001000
unsigned char linia [48]={0,1,0,1,1,0,1,1,1,0,1,1,1,1,0,0,0,0,1,1,1,1,1,1,1,1,1,0,0,0,0,0,0,0,0,0,1,1,1,1,1,1,1,1,1,0,0,1,};
int main()
{
DDRB = 0xff;
PORTB = 0;
signed char x=0;
clr_le;
set_oe; // wyłączamy prąd diod - można, ale nie trzeba
clr_clk;
for(x=48;x>=0;--x)
{
clr_clk;
if(linia[x] == 1)
{
set_data;
}
else
{
clr_data;
}
set_clk; // i tutaj zatrzaskujemy dane w rejestrze
// zboczem narastającym
}
set_le; // zatrzaskujemy
clr_le; // dane w latchu
clr_oe; // włączamy prąd diod
while(1);
} Quote:... I connected everything as it should be ...
unsigned char linia [8][10]={
{0,0,1,1,1,1,0,0,0,0},
{0,1,0,0,0,0,1,0,0,0},
{1,0,1,0,0,1,0,1,0,0},
{1,0,0,0,0,0,0,1,0,0},
{1,0,1,0,0,1,0,1,0,0},
{1,0,0,1,1,0,0,1,0,0},
{0,1,0,0,0,0,1,0,0,0},
{0,0,1,1,1,1,0,0,0,0}
};
int main()
{
DDRB = 0xff;
PORTB = 0;
signed char x=0;
signed char y=0;
while(1)
{
for(y=0;y=0;--x)
{
clr_clk;
if(linia[y][x]==1)
{
set_data;
}
if(linia[y][x]==0)
{
clr_data;
}
set_clk;
}
set_le;
clr_le;
_delay_loop_2(300);
}
}
}
. As for the watch, no new version was created, although I had a lot of thoughts, mainly about the power supply (coreless transformer) and data transmission to the device (IrDA, Bluetooth, or FM modulation of the power waveform). The minus mentioned by you, in my opinion, is not a minus of the device itself. I could just as well write that the downside of the device is that it will not be made by a person who has never had a soldering iron in his hand 
.
mb1988 wrote:As for the watch, no new version was created, although I had a lot of thoughts, mainly about the power supply (coreless transformer) and data transmission to the device (IrDA, Bluetooth, or FM modulation of the power waveform).
mot wrote:Sure. I don't really know what role.Is it possible to use the 555 timer for this project?
mlassota wrote:Just my main concern was the efficiency of the transformer, while inside the coils there would be an aluminum rotor of the motor. There were concerns that the device would be more suitable for an induction heater. The only solution would be to move the coils away from the body itself to minimize eddy current losses. As for your mysterious "00:00:80", I remember that it also showed up to me sometimes. The answer why this is happening can be found directly in the documentation:the aluminum block from which the rotor overlay is made, which enables the mounting of the plate, heats up quite strongly, while the power transferred to the secondary winding was small.
Quote:The 00h register is used to store seconds. Like most values in this clock, the seconds are also stored in BCD format. Bits [3: 0] are units of seconds, while bits [6: 4] are tens of seconds. As we read in the quoted fragment, bit 7 is a control bit that activates the operation of the oscillator. A simple software BCD decoder does not take into account that the older half of the seconds register is not entirely dedicated to storing the tens digit value. And that when the clock is on, we have set to bit 7 and the reading of the seconds always ends with a surprising value of 80Bit 7 of Register 0 is the clock halt
(CH) bit. When this bit is set to 1, the oscillator is disabled. When cleared to 0, the oscillator is enabled. He first
application of power to the device the time and date registers are typically reset to 01/01/00 01 00:00:00
(MM / DD / YY DOW HH: MM: SS). The CH bit in the seconds register will be set to a 1.
.
ISR(TIMER1_CAPT_vect)
{
TIMER1_OFF;
TCNT1 = 0;
g_tick = ICR1 / RESOLUTION;
g_pos = 0;
OCR1A = g_tick;
TIMER1_ON;
}
ISR(TIMER1_COMPA_vect)
{
if(g_pos < RESOLUTION) OCR1A = OCR1A + g_tick;
// tutaj wyswietlanie
// ....
Send4BytesT(buff);
_delay_us(20);
RED_OFF;
SET_OE;
g_pos++;
}
TL;DR: One Propeller-Clock rotor spins 50 rps (≈3 000 rpm) while an ATmega32 drives 32 LEDs; “in spectral clocks the issue of software … can make a difference” [Elektroda, Twizzter, post #4815839] Size, speed and code tweaks decide image quality. Why it matters: these tips prevent the common “00:00:80” bug and burnt HDD motors.
• Rotor speed: 45-55 rps recommended to avoid flicker [Elektroda, mb1988, post #4814890] • Power draw: 5 V / 250 mA (motor), 12 V / 80 mA (LEDs) [Elektroda, mb1988, post #4816959] • LED count: 32 SMD on radius = 63 pixels diameter [Elektroda, mb1988, post #4815891] • Motor driver: Philips TDA5140A; drop-in LB1688 works with minor tuning [Elektroda, mb1988, post #4815034] • Typical build cost: PLN 50–60 for electronics; case from scrap plexi [Elektroda, mb1988, post #4816863]
