18649 - Network Schedule
18649 Spring 2010
Group 7 - Justin Ray/justinr2
CAN Message Dictionary
Add a summary here
Sender Node Name |
Message Name |
Deadline (ms) |
Message ID |
Source Node Type |
Replication Type |
Base CAN ID |
VendPosition Sensor |
mVendPosition |
50 |
100 |
10 |
s |
0x08640A00 |
VendControl |
mVend |
50 |
200 |
20 |
none |
0x08C81400 |
VendPositionControl |
mVendMotor |
50 |
300 |
30 |
none |
0x092C1E00 |
ButtonControl |
mButton |
100 |
400 |
40 |
s |
0x09902800 |
CoinReturn Sensor |
mCoinReturn |
100 |
500 |
50 |
none |
0x09F43200 |
CoinControl |
mCoinCount |
100 |
600 |
60 |
none |
0x0A583C00 |
Empty Sensor |
mEmpty |
500 |
700 |
70 |
none |
0x0ABC4600 |
Network Schedule Analaysis
Add a summary here
|
Field 1 |
Total Bit Len |
Total Byte Len |
Best Case Msg Len |
Worst Case Msg Len |
Best Case BW
(bits/sec) |
Worst Case BW
(bits/sec) |
Sender Node Name |
Message Name |
Base CAN ID |
Replication Count |
Deadline (ms) |
Desc |
Type |
Bit
Len |
VendPosition Sensor |
mVendPosition |
0x08640A00 |
1 |
50 |
position
sensor |
boolean |
1 |
1 |
1 |
75 |
90 |
1500 |
1800 |
VendControl |
mVend |
0x08C81400 |
1 |
50 |
vend
actuator |
boolean |
1 |
1 |
1 |
75 |
90 |
1500 |
1800 |
VendPositionControl |
mVendMotor |
0x092C1E00 |
8 |
50 |
vend
motor |
d |
2 |
2 |
1 |
75 |
90 |
12000 |
14400 |
ButtonControl |
mButton |
0x09902800 |
8 |
100 |
button
pressed |
boolean |
1 |
1 |
1 |
75 |
90 |
6000 |
7200 |
CoinReturn Sensor |
mCoinReturn |
0x09F43200 |
1 |
100 |
coin
return
pressed |
boolean |
1 |
1 |
1 |
75 |
90 |
750 |
900 |
CoinControl |
mCoinCount |
0x0A583C00 |
1 |
100 |
coin
count |
int |
8 |
8 |
1 |
75 |
90 |
750 |
900 |
Empty Sensor |
mEmpty |
0x0ABC4600 |
1 |
500 |
chute
state |
boolean |
1 |
1 |
1 |
75 |
90 |
150 |
180 |
|
Total
bw |
22650 |
27180 |
<Excel sheet intentionally omitted from the example>
Simulation Analysis
Running the simulation with bandwidth of 60kbps, we obtain the results
listed below. Multiplying the network bandwidth by the
utilization gives us the actual bandwidth used:
60000 * 0.4161 = 24966 bps
This is between the best- and worst-case values predicted by our
analysis.
In addition the above results, this test revealed issue #17 from the
issue log.
Simulator Parameters:
Command line = -cc 15 -rt 6000s -b 60
RandomSeed = 1265845088385
CanNetworkBitTime = 16667 ns
Effective Can Bitrate = 59998.800023999516
Run Time = 6000.0s
Real time rate = null
Running Acceptance Test for 15 customers
[Elevator] @0.000000000: Starting Simulation
[Elevator] @60.000000000: Progress indicator
[Elevator] @120.000000000: Progress indicator
[Elevator] @180.000000000: Progress indicator
[Elevator] @240.000000000: Progress indicator
[Elevator] @300.000000000: Progress indicator
[Elevator] @336.794000000: Simulation Finished
Network Utilization Summary:
Recent: 41.61 % Max: 41.61 % Overall: 41.61 %
STATISTICS FOR CUSTOMERS
------------------------
Customer Summary
Satisfied: 15
Unsatisfied: 0
Total: 15