Digitax F3 Plus Technical Manual page 33

Nr. Functions
99 Increase unit-cost in Prog-Date 6 - Should the unit-cost (Q.8 to Q.10) in Prog-Date 6 be increased based on the percentage (Q.98)?
100 Increase initial-cost in Prog-Date 6 - Should the initial-cost (Q.11) in Prog-Date 6 be increased based on the percentage (Q.98)?
101 Decrease unit-distance in Prog-Date 6 - Should the unit-distance (Q.2 to Q.4) in Prog-Date 6 be decreased based on the percentage (Q.98)?
102 Decrease unit-waiting-time in Prog-Date 6 - Should the unit-waiting-time (Q.5 to Q.7) in Prog-Date 6 be decreased based on the percentage (Q.98)?
103 Insert as fixed cost in Prog-Date 6 - When passing from HIRED to STOPPED in Prog-Date 6 should the parameter of Q.98 be inserted as a fixed cost?
104 Insert as percentage in Prog-Date 6 - When passing from HIRED to STOPPED in Prog-Date 6 should the parameter of Q.98 be inserted as a percentage?
105 Insert as fixed cost in Prog-Date 6 with K1 - Passing from HIRED to STOPPED in Prog-Date 6 should the parameter of Q.98 be inserted as a fixed cost pressing K1?
106 Insert as percentage in Prog-Date 6 with K1 - Passing from HIRED to STOPPED in Prog-Date 6 should the parameter of Q.98 be inserted as a percentage pressing K1?
107 Block-number in Prog-Date 7 - The block number (absolute) to be used during the date and hour programmed in Prog-Date 7. The value goes from 0 (min) to 62 (max).
108 Block-offset in Prog-Date 7 - The block offset (relative) to be used during the date and hour programmed in Prog-Date 7. 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).
109 Percentage or cost in Prog-Date 7: this is the percentage or the cost that will be applied during the date and time as programmed in Prog-Date 7. The interpretation as a
percentage or as a cost depends on questions Q.110 to Q.117. In case of percentage consider Q.110 to Q.113, Q.115 and Q.117. Questions Q.114 and Q.116 should be
answered with: NO. In case of cost consider Q.114 and Q.116. Questions Q.110 to Q.113, Q.115 and Q.117 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).
110 Increase unit-cost in Prog-Date 7 - Should the unit-cost (Q.8 to Q.10) in Prog-Date 7 be increased based on the percentage (Q.109)?
111 Increase initial-cost in Prog-Date 7 - Should the initial-cost (Q.11) in Prog-Date 7 be increased based on the percentage (Q.109)?
112 Decrease unit-distance in Prog-Date 7 - Should the unit-distance (Q.2 to Q.4) in Prog-Date 7 be decreased based on the percentage (Q.109)?
113 Decrease unit-waiting-time in Prog-Date 7 - Should the unit-waiting-time (Q.5 to Q.7) in Prog-Date 7 be decreased based on the percentage (Q.109)?
114 Insert as fixed cost in Prog-Date 7 - When passing from HIRED to STOPPED in Prog-Date 7 should the parameter of Q.109 be inserted as a fixed cost ?
115 Insert as percentage in Prog-Date 7 - When passing from Hired to Stopped in Prog-Date 7 should the parameter of Q.109 be inserted as a percentage?
116 Insert as fixed cost in Prog-Date 7 with K1 - Passing from Hired to Stopped in Prog-Date 7 should the parameter of Q.109 be inserted as a fixed cost pressing key K1?
117 Insert as percentage in Prog-Date 7 with K1 - Passing from Hired to Stopped in Prog-Date 7 should the parameter of Q.109 be inserted as a percentage pressing K1?
118 Block-number in Prog-Date 8 -The block number (absolute) to be used during the date and hour programmed in Prog-Date 8. The allowed value goes from 0 (min) to 62
(max).
119 Block-offset in Prog-Date 8: the block offset (relative) to be used during the date and hour programmed in Prog-Date 8. 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).
120 Percentage or cost in Prog-Date 8. this is the percentage or the cost that will be applied during the date and time as programmed in Prog-Date 8. The interpretation as a
percentage or as a cost depends on questions Q.121 to Q.128. In case of percentage consider Q.121 to Q.124, Q.126 and Q.128. Questions Q.125 and Q.127 should be
answered with: NO. In case of cost consider Q.125 and Q.127. Questions Q.121 to Q.124, Q.126 and Q.128 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).
121 Increase unit-cost in Prog-Date 8 - Should the unit-cost (Q.8 to Q.10) in Prog-Date 8 be increased based on the percentage (Q.120)?
122 Increase initial-cost in Prog-Date 8 - Should the initial-cost (Q.11) in Prog-Date 8 be increased based on the percentage (Q.120)?
123 Decrease unit-distance in Prog-Date 8 - Should the unit-distance (Q.2 to Q.4) in Prog-Date 8 be decreased based on the percentage (Q.120)?
124 Decrease unit-waiting-time in Prog-Date 8 - Should the unit-waiting-time (Q.5 to Q.7) in Prog-Date 8 be decreased based on the percentage (Q.120)?
125 Insert as fixed cost in Prog-Date 8 - When passing from HIRED to STOPPED in Prog-Date 8 should the parameter of Q.120 be inserted as a fixed cost?
126 Insert as percentage in Prog-Date 8 - When passing from HIRED to STOPPED in Prog-Date 8 should the parameter of Q.120 be inserted as a percentage?
127 Insert as fixed cost in Prog-Date 8 with K1 - Passing from HIRED to STOPPED in Prog-Date 8 should the parameter of Q.120 be inserted as a fixed cost pressing K1?
128 Insert as percentage in Prog-Date 8 with K1 - Passing from HIRED to STOPPED in Prog-Date 8 should the parameter of Q.120 be inserted as a percentage pressing K1?
129 Priority of Prog-Date 1 (night-time) - This is the number that corresponds with the priority that Prog-Date n. 1 has with respect to the other Prog-Dates. The allowed
number goes from: 8 (min. priority) to: 1 (max. priority). If two or more Prog-Dates have the same number then those Prog-Dates have the same priority.
130 Priority of Prog-Date 2 (holiday-time) - This is the number that corresponds with the priority that Prog-Date n. 2 has with respect to the other Prog-Dates. The allowed
number goes from: 8 (min. priority) to: 1 (max. priority). If two or more Prog-Dates have the same number then those Prog-Dates have the same priority.
131 Priority of Prog-Date 3 -This is the number that corresponds with the priority that Prog-Date n. 3 has with respect to the other Prog-Dates. The allowed number goes from:
8 (min. priority) to: 1 (max. priority). If two or more Prog-Dates have the same number then those Prog-Dates have the same priority.
132 Priority of Prog-Date 4 -This is the number that corresponds with the priority that Prog-Date n. 4 has with respect to the other Prog-Dates. The allowed number goes from:
8 (min. priority) to: 1 (max. priority). If two or more Prog-Dates have the same number then those Prog-Dates have the same priority.
The information contained here are property of DIGITAX Automotive Electronics Italy, and extremely confidential. Any disclosure, copying, distribution to third
party is strictly prohibited.
PROG-DATE N. 7
PROG-DATE N. 8
Prog-Date priority ManagemeNt
Value
No / Yes
No / Yes
No / Yes
No / Yes
No / Yes
No / Yes
No / Yes
No / Yes
0 - 62
0 - 62
0 - 65535
percentage/c
ost
No / Yes
No / Yes
No / Yes
No / Yes
No / Yes
No / Yes
No / Yes
No / Yes
0 - 62
0 - 62
0 - 65535
percentage/c
ost
No / Yes
No / Yes
No / Yes
No / Yes
No / Yes
No / Yes
No / Yes
No / Yes
No / Yes
No / Yes
No / Yes
No / Yes
33