= HF8V = / = SP8WJT = / = SP0106RZ =

HF-6030

PROJECT: HF-6030
DESCRIPTION: Digital System on ATMEGA8
STATUS: operational
PROJECT START DATE: 2001
DOCUMENTATION: paper
UC-###: UC-256
uC FAMILY: AVR
THN ADDRESS: 0x9C
TYPE: 0x14

Modules:

PROJECT	DESCRIPTION	PCB	STATUS	REMARKS
HF-6030	Digital System on AT90S2313 (version 1)	TPD55000	u	UC-002
HF-6030	Digital System on ATTINY2313 (version 2)	TPD55000	u	UC-???
HF-6030	Digital System on ATMEGA8 (version 3)	TPD55000	u	UC-256

Hardware:
Current hardware version: 3.3

HF-6030 main board is 1980's keyboard from terminal MERA 7935(?). It was used with main frame computers like MERA-400 etc.. I cutted original PCB with 102 keys and left only 40 most important (A-Z, 0-9, ESC, SEND, SPC, RST). In hardware version 3, original demultiplexer 74154 and counter 7493 uses only 5 ports of ATMEGA8 to scan 3x16 matrix.

User ports: PORTB, PORTC (PC0-PC5)
System ports: PORTD

Software:
Current software version: 3.39
Menu functions: 37
Vector functions: 180
UART functions: 0 (planned)

HF-6030 is my first digital system I ever constructed. From beginning main idea behind it was CW output device as main output channel and this works perfectly till today, althought many versions and uCs changed throught the years... In practise I very rarely use other output channels than CW.

CW plus vector functions are so economic way for input and output that it is almost magical how many functions can be packed in 4096 instructions...

Project HF-6030 has a long history:
Version 1: AT90S2313 (demux 74154, generator 7400)
Version 2: ATTINY2313 (added EEPROMS: EEP1 and EEP2)
Version 3: ATMEGA8 (added counter 7493)

Important feature of HF-6030 is very effective HAVR compiler and interpreter. This allows me writing very quickly almost infinite amount of HAVR programs (25CSM04 can store 2040 files).
HAVR is also very economic language, 66% of its 73 instructions are 1 byte instructions. Typical quick program is 16-20 bytes long, while shortest program I ever wrote is 8 (10 with START and END instructions) bytes long.
At first I had been writing all straight in machine code, what was very simple because easy to remember 73 instructions and there is only one addressing mode: absolute, one-byte.
HAVR interpreter loop takes some 1.3us per HAVR instruction, this is only one disadvantage of HAVR.

STATUS CODES

f	failed
p	planned
q	not accomplished
r	resigned
u	fully operational
w	assembled but not tested
x	not avalaible (returned, sold, lost or no data)
z	decomissioned (disassembled)

HF Register

Microcontrollers in my contructions

Apache/2.4.38 (Debian) Server at Port 80