Changes for page SCChart Controller

Last modified by Richard Kreissig on 2025/01/30 12:18

From version 11.1
edited by stu122612
on 2020/03/14 09:58
Change comment: There is no comment for this version
To version 8.1
edited by stu122612
on 2020/03/14 09:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -11,10 +11,6 @@
11 11  
12 12  [[image:attach:Overview.png]]
13 13  
14 -{{expand title="Full Overview (all regions expanded)"}}
15 -[[image:attach:Screen Shot 2020-03-14 at 10.38.05.png]]
16 -{{/expand}}
17 -
18 18  The behaviour and information processing is distributed across multiple regions in the controller.
19 19  
20 20  (% style="list-style-type: square;" %)
... ... @@ -24,22 +24,16 @@
24 24  * Red: These two regions control launching. {{code language="none"}}manual launching{{/code}} just holds both flippers up for a long enough period for the machine to launch the ball into the game. The other region is in charge of detecting when the launch lamp is blinking and then waiting the appropriate amount of time to acquire the 20 million launch bonus.
25 25  * Blue: These are the main brain of the controller. These regions retrieve ball positions, ask for predictions on future ball positions, process a little game information to determine possible targets and decide when and how to actuate the flippers.
26 26  
27 -= Actuating =
23 +{{expand title="Full Overview (all regions expanded)"}}
24 +[[image:attach:Screen Shot 2020-03-14 at 10.38.05.png]]
25 +{{/expand}}
28 28  
29 -[[image:attach:Screen Shot 2020-03-14 at 10.46.45.png]]
27 += Trigger Delayed =
30 30  
31 -The actuation of flippers is implemented via a common automaton to which the appropriate signals are connected. The connected output signals are what is used to set the values of the GPIO pins by the outside system. With the {{code language="none"}}trigger{{/code}} signal a standard actuation of the flipper can be initiated. The automaton waits after enabling and disabling for the real world to catch up, as the flipper arms take some time to move from their resting position and back. Additionally there is a hold signal which can be used from the outside to basically override the behaviour regarding the cooldown.
29 += Actuating =
32 32  
33 -(% style="font-size: 24.0px;letter-spacing: -0.01em;" %)TriggerDelayed
34 -
35 -[[image:attach:Screen Shot 2020-03-14 at 10.47.09.png]]
36 -
37 -As previously mentioned these regions are simply an extension on top of the {{code language="none"}}Actuating{{/code}} regions. They receive a trigger signal and then wait for a certain amount of time until passing that information onwards (ie. setting the trigger signal connected to one of the {{code language="none"}}Actuating{{/code}} regions seen above.
38 -
39 39  = Prediction =
40 40  
41 -TODO
42 -
43 43  = Launching =
44 44  
45 45  [[image:attach:Screen Shot 2020-03-14 at 10.25.04.png]]
... ... @@ -61,7 +61,3 @@
61 61  \\
62 62  
63 63  \\
64 -
65 -\\
66 -
67 -\\
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -73072643
1 +72450084
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/PP18/pages/73072643/SCChart Controller
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/PP18/pages/72450084/SCChart Controller