EN polling process limits and mileage input

Preamble

When working with card limits (exception "limit per fill") and/or input of mileage values at the card reader/s, then the polling process has to be adapted respectively organised in a specific way.

Explanations

• When working with more than one card reader, these card readers are not connected between each other. So a card reader does not know who and when a filling has being done at one of the other card readers.

• When working with a periode limit, which is being managed via Autopoll, the filling limit will be calculated everytime anew. So all fillings of all card readers have to be transmitted to Autopoll before the new limit calculation.

• When working with mileage input at the card reader, all fillings of all card readers have to be transmitted to Autopoll before the highest mileage value can be saved in the corresponding vehicle and the actual mileage value can be transmitted to all card readers.

Polling process when working with limits and/or mileage input at the card reader

Polling 1

• only polling of all fillings from all card readers

• NO polling of cards

• When all fillings are being polled from all the card readers, the card limits will be calculated anew and/or the mileage values (only higher values) are being saved in the corresponding vehicles.

Polling 2

• transmitting of the changed cards only to all card readers

Periode start when working with card limits

• At the start of a new periode (e.x. on the first day of a month when dealing with a monthly limit), the card limits change just because a new month starts. The card limits will be set to the starting value. So at the start of a periode it is absolutely necessary to execute "Polling 1" first and afterwards "Polling 2" as explained above. But when executing "Polling 2" at this moment, ALL cards have to be transmitted to ALL card readers.