-
Notifications
You must be signed in to change notification settings - Fork 0
/
Scrapbook
46 lines (31 loc) · 1.23 KB
/
Scrapbook
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
----------------------
DEPRICATED
----------------------
More on the beacon's behaviors.
The beacons work in a hybrid ring/mesh topology with 4 nodes.
Mostly the Ring topology.
How a transmission occurs:
A wire radio's 4 outputs on each beacon will give the following:
Channel (identifies which beacon it is)
X pos
Y pos
Z pos
The radios will be used to tell mechs where the beacons were put down at.
Once a Mech gets the information listed above, it will assess which beacon is closest,
and then point its mounted transferrer to the satelite dish on that beacon.
PRetty basic for now, soon the beacons will use relaying to bounce info between eachother using line
of sight communication. Save that for when we establish a communication protocol for the mechs
----------------------
Mech behaviour
----------------------
Currently navi is raw navigation and only walks to target and throws triggers at difinable ranges and conditions such as when facing, and when at X distance away
----------------------
Mech roles
----------------------
----------------------
NAVI commanding functions
----------------------
----------------------
NAVI comms protocol
----------------------
Navi will use datasignals, more on this when it becomes prevalent