Digitax F2 PLUS - Page 33

The information contained here are property of DIGITAX Automotive Electronics Italy, and extremely confidential. Any disclosure, copying, distribution to third party
is strictly prohibited.
33
65
Percentage or cost in Prog-Date 3 - This is the percentage or the cost that will be applied during the date and time as programmed in Prog-Date 3. The interpretation
as a percentage or as a cost depends on questions Q.66 to Q.73. In case of percentage consider Q.66 to Q.69, Q.71 and Q.73. Questions Q.70 and Q.72 should be
answered with: NO. In case of cost consider Q.70 and Q.72. Questions Q.66 to Q.69, Q.71 and Q.73 should be answered with: NO. The cost is given in the local currency
with an accuracy of 1. The allowed value goes from 0 (min) to 65535 (max). See Q.273 and Q.274 for adding a fixed decimal point. The percentage is given with an
accuracy of 0.1. The allowed value goes from 0 (min) to 6553.5 (max).
0 - 65535
percentage/
cost
66
Increase unit-cost in Prog-Date 3 - Should the unit-cost (Q.8 to Q.10) in Prog-Date 3 be increased based on the percentage (Q.65) ?
No / Yes
67
Increase initial-cost in Prog-Date 3 - Should the initial-cost (Q.11) in Prog-Date 3 be increased based on the percentage (Q.65)?
No / Yes
68
Decrease unit-distance in Prog-Date 3 - Should the unit-distance (Q.2 to Q.4) in Prog-Date 3 be decreased based on the percentage (Q.65)?
No / Yes
69
Decrease unit-waiting-time in Prog-Date 3 - Should the unit-waiting-time (Q.5 to Q.7) in Prog-Date 3 be decreased based on the percentage (Q.65)?
No / Yes
70
Insert as fixed cost in Prog-Date 3 - When passing from HIRED to STOPPED in Prog-Date 3 should the parameter of Q.65 be inserted as a fixed cost?
No / Yes
71
Insert as percentage in Prog-Date 3 - When passing from HIRED to STOPPED in Prog-Date 3 should the parameter of Q.65 be inserted as a percentage?
No / Yes
72
Insert as fixed cost in Prog-Date 3 with K1 - Passing from HIRED to STOPPED in Prog-Date 3 should the parameter of Q.65 be inserted as a fixed cost pressing K1?
No / Yes
73
Insert as percentage in Prog-Date 3 with K1 - Passing from HIRED to STOPPED in Prog-Date 3 should the parameter of Q.65 be inserted as a percentage pressing
K1?
No / Yes
PROG-DATE N. 4
74
Block-number in Prog-Date 4 - The block number (absolute) to be used during the date and hour programmed in Prog-Date 4.
The allowed value goes from 0 (min) to 62 (max).
0 - 62
75
Block-offset in Prog-Date 4 - The block offset (relative) to be used during the date and hour programmed in Prog-Date 4. The relative block offset is the number of
blocks to add to the current block number in order to obtain the new block number. The allowed value goes from 0 (min) to 62 (max).
0 - 62
76
Percentage or cost in Prog-Date 4 - This is the percentage or the cost that will be applied during the date and time as programmed in Prog-Date 4. The interpretation
as a percentage or as a cost depends on questions Q.77 to Q.84. In case of percentage consider Q.77 to Q.80, Q.82 and Q.84. Questions Q.81 and Q.83 should be
answered with: NO. In case of cost consider Q.81 and Q.83. Questions Q.77 to Q.80, Q.82 and Q.84 should be answered with: NO.
The cost is given in the local currency with an accuracy of 1. The allowed value goes from 0 (min) to 65535 (max). See Q.273 and Q.274 for adding a fixed decimal point.
The percentage is given with an accuracy of 0.1. The allowed value goes from 0 (min) to 6553.5 (max).
0 – 65535
percentage/
cost
77
Increase unit-cost in Prog-Date 4 - Should the unit-cost (Q.8 to Q.10) in Prog-Date 4 be increased based on the percentage (Q.76)?
No / Yes
78
Increase initial-cost in Prog-Date 4 - Should the initial-cost (Q.11) in Prog-Date 4 be increased based on the percentage (Q.76)?
No / Yes
79
Decrease unit-distance in Prog-Date 4 - Should the unit-distance (Q.2 to Q.4) in Prog-Date 4 be decreased based on the percentage (Q.76)?
No / Yes
80
Decrease unit-waiting-time in Prog-Date 4 - Should the unit-waiting-time (Q.5 to Q.7) in Prog-Date 4 be decreased based on the percentage (Q.76)?
No / Yes
81
Insert as fixed cost in Prog-Date 4 - When passing from HIRED to STOPPED in Prog-Date 4 should the parameter of Q.76 be inserted as a fixed cost?
No / Yes
82
Insert as percentage in Prog-Date 4 - When passing from HIRED to STOPPED in Prog-Date 4 should the parameter of Q.76 be inserted as a percentage?
No / Yes
83
Insert as fixed cost in Prog-Date 4 with K1 - Passing from HIRED to STOPPED in Prog-Date 4 should the parameter of Q.76 be inserted as a fixed cost pressing K1?
No / Yes
84
Insert as percentage in Prog-Date 4 with K1 - Passing from HIRED to STOPPED in Prog-Date 4 should the parameter of Q.76 be inserted as a percentage pressing
K1?
No / Yes
PROG-DATE N. 5
85
Block-number in Prog-Date 5 : NOT USED for F2 Plus
0 - 62
86
Block-offset in Prog-Date 5 : NOT USED for F2 Plus
0 - 62
87
Percentage or cost in Prog-Date 5 : NOT USED for F2 Plus
0 - 65535
percentage/
cost
88
Increase unit-cost in Prog-Date 5 : NOT USED for F2 Plus
No / Yes
89
Increase initial-cost in Prog-Date 5 : NOT USED for F2 Plus
No / Yes
90
Decrease unit-distance in Prog-Date 5 : NOT USED for F2 Plus
No / Yes
91
Decrease unit-waiting-time in Prog-Date 5 : NOT USED for F2 Plus
No / Yes
92
Insert as fixed cost in Prog-Date 5 : NOT USED for F2 Plus
No / Yes
93
Insert as percentage in Prog-Date 5 : NOT USED for F2 Plus
No / Yes
94
Insert as fixed cost in Prog-Date 5 with K1 : NOT USED for F2 Plus
No / Yes
95
Insert as percentage in Prog-Date 5 with K1 : NOT USED for F2 Plus
No / Yes
PROG-DATE N. 6
96
Block-number in Prog-Date 6 : NOT USED for F2 Plus
0 - 62