UPdate based on feedback

This commit is contained in:
2026-04-01 23:56:49 -07:00
parent 2e72f5e590
commit e88a95e7f9

View File

@@ -23,7 +23,7 @@ Location is 48.72° N Latitude and -122.51° W Longitude
The proposed maximum range is 15 miles.
Selectable ranges sould be 2, 5, 10, and 15 miles
The project will be implimented on on a Geekom A8 Max
The project will be implemented on on a Geekom A8 Max
with AMD AI chip R9-8945HS with 32 GB ram
The operating system is Linux (Ubuntu)
@@ -91,6 +91,12 @@ running linux.
I plan to have a variety of phony targets simulated in addition to
those received on uat, ads-b, and ais.
Note that directions shall be true, not magnetic
Note that shoreline data is from noaa maps
(NOAA provides free ENC (Electronic Nautical Chart) data in S-57 format covering
Bellingham Bay and surrounding waters.)
I prefer to have separate shader sets for each major function to facilitate
troubleshootng
Major functions:
@@ -109,7 +115,7 @@ Display colors:
2. A Scope graticule is incandescent color
3. PPI scope active targets including scatters, graticule range rings, shoreline,
all p7 phosphor (active white blue)
4. All persistance for PPI scope active targets including
4. All persistance (also p7 greenish yellow persistance) for PPI scope active targets including
scatters, graticule range rings, shoreline
5. PPI scope bearing ring and ticks is incandescent color.
@@ -129,6 +135,8 @@ Need to have following fixed singnal strength:
2. yachts would be bright but not blooming
3. sailboats would be medium bright and not blooming
4. kayaks and roaboats would be small and dim
5. May consider fading small boats like kayaks
and sail bots above 3 miles
Details of each feature:
@@ -144,6 +152,10 @@ A scope:
scope and inserts the replacement through the same slot. All these graticules
are lighted with incandescent colors.
Note on screen update vs pulse repition frequency. We need to be careful
since we have no control of the display update frequency and need
to do whatever is needed to reduce aliasing or flickering
PPI Scope active targets
1. Active boats/planes; brightness determined by size as noted above
2. Blue white color
@@ -171,17 +183,17 @@ Here are the controls that I am proposing
1. Intensity
2. Focus
3. Astignatism
3. astigmatism
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
6. Sensitivity time control STC / sea clutter
7. There is some sort of control having to do with the magnetron
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)
9. Magnetron tune
10. Anti clutter rain (ftc)
10. FTC / Rain Clutter
11. Will not need heading (this will be a fixed radar location for
the harbor master or lifeguard
12. Off-centering
@@ -189,6 +201,7 @@ Here are the controls that I am proposing
14. Reset (in case kids really mess things up)
15. Pulse length selection (short pulse for better range resolution,
long pulse for better sensitivity at distance; operator selectable)
16. Pulse repition frequency
(Please suggest other controls I may have missed.)
@@ -249,6 +262,7 @@ Those classes will use a common target data structure:
The RPi communication thread blocks on a socket read until data arrives, then
writes to a shared target queue protected by a mutex and signals a condition
variable. The main application consumes from that queue.
Prefer TCP.
The Raspberry Pi code will live in a separate git repository with its own CLAUDE.md
and its own CMakeLists.txt, since it targets a different architecture (ARM) and has
@@ -275,5 +289,5 @@ Order of testing features.
========================================================
Now, just comment on this, noting any errors or anything you think is smissing.
Now, just comment on this, noting any errors or anything you think is missing.
DO NOT GENERATE CODE