Data Flow¶
How Information Moves Through REVA v4.0
Overview¶
REVA transforms operator actions into physical output waveforms through a sequence of processing layers.
Understanding this flow makes it possible to understand how a parameter change eventually affects D9 and D10.
Complete Data Flow¶
Operator Input
↓
Parameter Update
↓
Packet Selection
↓
Packet Executor
↓
Timer2 Scheduler
↓
Timer1 Carrier Engine
↓
D9 / D10 Outputs
Operator Input¶
The process begins with operator interaction.
Examples include:
- family selection
- pulse scaling
- gap scaling
- configuration changes
At this stage only control information exists.
No waveform changes have yet occurred.
Parameter Update¶
The Parameter Manager validates and stores updated values.
This layer maintains the current operating configuration.
Packet Selection¶
The selected packet family is retrieved from the active packet category.
Examples:
- Harmonic Family
- Fibonacci Family
- Golden Ratio Family
The result is a packet definition containing segment information.
Packet Executor¶
The Packet Executor converts packet definitions into timing instructions.
Responsibilities include:
- segment interpretation
- pulse scaling
- gap scaling
- execution sequencing
The output of this stage is executable timing data.
Timer2 Scheduler¶
Timer2 receives timing instructions from the Packet Executor.
Responsibilities include:
- segment timing
- gap timing
- packet repetition
- transition management
Timer2 creates the packet envelope.
Timer1 Carrier Engine¶
Timer1 continuously generates the carrier waveform.
Timer2 determines when that carrier is allowed to appear.
The result is a packetized carrier stream.
Output Generation¶
Timer1 drives:
- D9 (OC1A)
- D10 (OC1B)
These outputs are connected to the IR2304 half-bridge driver.
Engineering Perspective¶
The complete process can be summarized as:
Operator Intent
↓
Configuration Data
↓
Packet Geometry
↓
Timing Instructions
↓
Carrier Modulation
↓
Output Waveform