add more detail

This commit is contained in:
2026-04-01 09:06:54 -07:00
parent c0dc376d79
commit 36cdf24e93

View File

@@ -23,7 +23,10 @@ for the methods of that class should be put into a header file in the
headers directory.
Another class would be used to communicate with the raspberry pies that
will obtain data from the ais and ads-b software defined radios.
will obtain data from the ais and ads-b software defined radios. This
is for purposes of adding targets. Marine radar can pick up low flying
targets plus I may (in the future) add an option for a vintage air traffic
control radar with precision approach radar, but not now.
Another class would be used for simulating targets, like for example
a sailboat regatta race.
@@ -38,16 +41,41 @@ The platform is a Geekom GEEKOM A8 Max, AMD Ryzen 9 8945HS 5.2GHz 32GB RAM
Now here is the overall project and proposed architecture
This project is to simulate a period 1950 to 1960 marine radar with a crt p7
phosphor for the ppi scope and a p4 phosphor for the a scope. The ppi scope
phosphor for the ppi scope and a p1 phosphor (this is oscilloscope phosphor)
for the a scope. The ppi scope
will be on the right side of the screen and the a scope will be on the left
hand side of the screen. The user will use a knob to set the bearing for the
a scope as that only shows range.
hand side of the screen.
For now, the a scope will not be made full because I have not figured out
how to implement the bearing control. Just put the display up on the screen.
Notes for controls the user can play with
The main ppi scope will take up the right hand side of the screen. You need to leave about
a 1/2 inch margin around the sides of the circular scope.
Here are the controls that I am proposing
1. Intensity
2. Focus
3. Astignatism
4. Range selection (for both a scope and ppi scope)
5. Sensitivity
6. Clutter elimination (I believe only ppi scope; please research)
7. There is some sort of control having to do with the mangatron
but I don't know what its called and what it does.
8. Bearing (only for a scope) which in the old days uses a servo motor to
rotate the antenna. I don't know what form of feedback (text on the
screen or mechanical numbers on a dial)
(Please suggest other controls I may have missed.)
Now, for controls, the tentative approach is to use encoders (that do not
have end stops so they cannot be broken by visitors at the museum) I will
need help on how to impliment them. I am guessing a few raspberry pies to
handle the encoders. I am thinking of encoders have one common terminal and
a clockwise pulse terminal and a counter clockwise pulse terminal.
Let do this like this. The control handling will be a different class and run
as a separate thread from the display. Each control function will have a parameter
for how many pulses received and in what direction. That would be permanent.
Temporary code necessary for changing control selection and value via the
keyboard until I get the necessary hardware for the controls.
Details for A scope (predecessor to the PPI scope)