Control Module is installed in a place, convenient for the driver. To it are connected the speakers of alerting in the cabin, up to 4 exterior Information Display modules, up to 4 Cashless Payment Terminals, and also an optional internal "scrolling line" LED-panel for displaying the name of the next stop. Looks sufficient 2 external Information Display modules on the vehicle (at front and right-side). In this case, they reflect only information about the route number, for example, 162k. Installation of the "scrolling line" inside the cabin can be reasonable, for example, by the need to service passengers with hearing loss or on routes, where a large number of tourists are expected.

Given the possibility of missing reliable data from the GPS-receiver, additional methods of the vehicle coordinates determining should be provided by other standard means of implementing the MESH-network of the selected type. Throughout the route, the driver presses the Next Stop and Route Start/End buttons (see below). The response of the controller to the absence of an event of the driver pressing the corresponding button should be provided when the vehicle reaches the next scheduled stop (see below).

Design of the Control Module

ktc

 

 

Controls and displays should not contain unnecessary elements, distracting the driver from the main job, and at the same time, be sufficiently informative and intuitive. The main function of the controller is the timely automatic provision of the Information Board at the stop with information about the time of arrival of this vehicle, as well as informing the Transport Company of its whereabouts and status, if remotely requested by Dispatcher PC software. Additional functions are the automatic issuance of voice messages to the passengers of the vehicle about the name of the current and the next stops, as well as indication of the recommended speed to the driver to be in schedule.

In addition to the elements shown in the figure, the Control Module contains a built-in GSM-modem (or MESH-network support module of the selected type), a GPS-receiver and a rewritable non-volatile memory for storing the route descriptor and voice messages of the current shift.

 

 

 

Control Module Elements

Driver's Personal Card

It is the main element of activation of the Vehicle Controller. If it is not inserted into the corresponding slot of the Control Module, then all elements of the display are extinguished, pressing the buttons does not cause a reaction and, if Dispatcher of Transport Company remotely requests vehicle current status, the controller returns "No Driver's Personal Card".

On the front of the Driver's Personal Card, must be printed a photograph of the driver and information about the number of the Transport Company, the telephone of the dispatcher, and also the name of the driver and his blood group. The photo should also contain information about the date when it is done.

The Driver's Personal Card is a standard size and has 256 byte memory chip, for example, SLE4432/PCF2032, SLE4442/PCF2042, PCF8582E, or MCM2814ATR series. It is desirable to use chips series SLE4432/PCF2032, SLE4442/PCF2042, because its first 32 bytes can be independently protected from change.

Thus, in the first 32 bytes, the following information can be stored:

  • Unique Transport Company Identifier (2 bytes)
  • Unique Driver Identifier in the Transport Company (or State Identification Code) (up to 20 bytes)
  • Control information (2 bytes)

Starting from the 33-rd byte, information can be recorded regarding the current working shift of the driver. Some of the data stored in the personal card driver, also appear to be useful for statistical calculations of the vehicle load, the actual conditions of the drivers employment contract and other, desirable, for example, to implement of electronic payment cards:

  • Type of vehicle (1 byte, where 1 is a bus, 2 is a trolley, 3 is a tram, 4 is a fixed-route taxi). This information is required by the Information Board to determine which module to send information about this vehicle arrival.
  • Index (pointer) of Starting Route Number and Route's Change Mask (1 byte, where the lower 5 bits contain the mask of routes, serviced by the driver on this shift. For example, the hexadecimal number "D" (01101), which means that the driver works today on the routes 169d, 998 and 31 (see below). Most significant 3-bits contains the rout number from which today's shift starts (numbering begins with 0) For example, the number 2, will mean an initial route 998).
  • A descriptor of the today's shift route's change order (2 bytes - each byte is divided into information tetrads. The tetrad contains the index for the next route number. The least significant tetrad of the first byte contains an index to the second route in the order. The most significant tetrad of the second byte contains an index on the 5-th route.

    In the above example, driver operates on 3 routes during the shift. The first byte can be, for example, written as the hexadecimal number "30". Here, the least significant tetrad has index 0 on the route 169d (2-nd in today's shift order), while the most significant tetrad stores index 3, for route 31 (3-rd by order). The content of the 2-nd (high) byte in this case is indifferent, since the mask of routes change (see above) contains information only about 3 routes).
  • The scheduled time of the routes change (8 bytes. 4 pairs of bytes containing the transition to the next route in the order. 1-st pair contains the transition to the 2-nd, ... 4-th - to the 5-th route  in the order. Most significant byte of each pair comprises a clock, least significant - minutes. Thus, for the above example, when the driver should be serviced 3 route during the shift, in the 1-st pair of bytes can be written, for example, the value 1200, and the second - 1700. The vehicle controller periodically reads the mask route change, and if there is evidence that the driver today operates on more than one route, compares the current time with stored in this table. If it is a time to change the route, the controller periodically plays a voice message, up to the the moment of confirmation by driver).
  • Route number (for example, 169d) (4 bytes)
  • Start time on the route (2 bytes)
  • End time on the route (2 bytes)
  • Total route mileage (km) (2 bytes)
  • The total number of runs from "start to finish" (1 byte)
  • The total number of runs from the "end to the beginning" (1 byte)
  • Total downtime (minutes) (2 bytes)
  • Total time in the state "No Personal Driver's Card" (minutes) (2 bytes)
  • The traffic interval between 6:00 - 8:00 (minutes) (1 byte. The traffic interval in this case means a planned time for moving the vehicle between the final stops on the route. The controller continuously processes the vehicle's current position and displays a speed value, necessary to comply with the schedule, prescribed at the current time of day).
  • The traffic interval between 8:00 - 10:00 (minutes) (1 byte)
  • The traffic interval between 10:00 - 12:00 (minutes) (1 byte)
  • The traffic interval between 12:00 - 14:00 (minutes) (1 byte)
  • The traffic interval between 14:00 - 16:00 (minutes) (1 byte)
  • The traffic interval between 16:00 - 18:00 (minutes) (1 byte)
  • The traffic interval between 18:00 - 20:00 (minutes) (1 byte)
  • The traffic interval between 20:00 - 22:00 (minutes) (1 byte)
  • The traffic interval between 22:00 - 0:00 (minutes) (1 byte)
  • Route No. (for example, 70) (4 bytes)
  • Start time on the route (2 bytes)
  • End time on the route (2 bytes)
  • Total route mileage (km) (2 bytes)
  • The total number of runs from "start to finish" (1 byte)
  • The total number of runs from the "end to the beginning" (1 byte)
  • Total downtime (minutes) (2 bytes)
  • Total time in the state "No Personal Driver's Card" (minutes) (2 bytes)
  • The traffic interval between 6:00 - 8:00 (minutes) (1 byte)
  • The traffic interval between 8:00 - 10:00 (minutes) (1 byte)
  • The traffic interval between 10:00 - 12:00 (minutes) (1 byte)
  • The traffic interval between 12:00 - 14:00 (minutes) (1 byte)
  • The traffic interval between 14:00 - 16:00 (minutes) (1 byte)
  • The traffic interval between 16:00 - 18:00 (minutes) (1 byte)
  • The traffic interval between 18:00 - 20:00 (minutes) (1 byte)
  • The traffic interval between 20:00 - 22:00 (minutes) (1 byte)
  • The traffic interval between 22:00 - 0:00 (minutes) (1 byte)
  • Route No. (for example, 998) (4 bytes)
  • Start time on the route (2 bytes)
  • End time on the route (2 bytes)
  • Total route mileage (km) (2 bytes)
  • The total number of runs from "start to finish" (1 byte)
  • The total number of runs from the "end to the beginning" (1 byte)
  • Total downtime (minutes) (2 bytes)
  • Total time in the state "No Personal Driver's Card" (minutes) (2 bytes)
  • The traffic interval between 6:00 - 8:00 (minutes) (1 byte)
  • The traffic interval between 8:00 - 10:00 (minutes) (1 byte)
  • The traffic interval between 10:00 - 12:00 (minutes) (1 byte)
  • The traffic interval between 12:00 - 14:00 (minutes) (1 byte)
  • The traffic interval between 14:00 - 16:00 (minutes) (1 byte)
  • The traffic interval between 16:00 - 18:00 (minutes) (1 byte)
  • The traffic interval between 18:00 - 20:00 (minutes) (1 byte)
  • The traffic interval between 20:00 - 22:00 (minutes) (1 byte)
  • The traffic interval between 22:00 - 0:00 (minutes) (1 byte)
  • Route No. (for example, 31) (4 bytes)
  • Start time on the route (2 bytes)
  • End time on the route (2 bytes)
  • Total route mileage (km) (2 bytes)
  • The total number of runs from "start to finish" (1 byte)
  • The total number of runs from the "end to the beginning" (1 byte)
  • Total downtime (minutes) (2 bytes)
  • Total time in the state "No Personal Driver's Card" (minutes) (2 bytes)
  • The traffic interval between 6:00 - 8:00 (minutes) (1 byte)
  • The traffic interval between 8:00 - 10:00 (minutes) (1 byte)
  • The traffic interval between 10:00 - 12:00 (minutes) (1 byte)
  • The traffic interval between 12:00 - 14:00 (minutes) (1 byte)
  • The traffic interval between 14:00 - 16:00 (minutes) (1 byte)
  • The traffic interval between 16:00 - 18:00 (minutes) (1 byte)
  • The traffic interval between 18:00 - 20:00 (minutes) (1 byte)
  • The traffic interval between 20:00 - 22:00 (minutes) (1 byte)
  • The traffic interval between 22:00 - 0:00 (minutes) (1 byte)
  • Route number (for example, 169d) (4 bytes)
  • Start time on the route (2 bytes)
  • End time on the route (2 bytes)
  • Total route mileage (km) (2 bytes)
  • The total number of runs from "start to finish" (1 byte)
  • The total number of runs from the "end to the beginning" (1 byte)
  • Total downtime (minutes) (2 bytes)
  • Total time in the state "No Personal Driver's Card" (minutes) (2 bytes)
  • The traffic interval between 6:00 - 8:00 (minutes) (1 byte)
  • The traffic interval between 8:00 - 10:00 (minutes) (1 byte)
  • The traffic interval between 10:00 - 12:00 (minutes) (1 byte)
  • The traffic interval between 12:00 - 14:00 (minutes) (1 byte)
  • The traffic interval between 14:00 - 16:00 (minutes) (1 byte)
  • The traffic interval between 16:00 - 18:00 (minutes) (1 byte)
  • The traffic interval between 18:00 - 20:00 (minutes) (1 byte)
  • The traffic interval between 20:00 - 22:00 (minutes) (1 byte)
  • The traffic interval between 22:00 - 0:00 (minutes) (1 byte)
  • Total mileage per shift (km) (2 bytes)
  • Total revenue per shift (4 bytes)
  • Total number of ordinary passengers (2 bytes)
  • Total number of privileged passengers (2 bytes)
  • Prefix to the phone numbers when initiating a communication session with the dispatcher of the Transport Company (GSM service provider identifier). For example, "8050". (4 bytes)
  • Dispatcher's phone number 1 (7 bytes)
  • Dispatcher's phone number 2 (7 bytes)
  • Dispatcher's phone number 3 (7 bytes)
  • The number of registered passengers in the interval 6:00 - 8:00 (2 bytes)
  • The number of registered passengers in the interval 8:00 - 10:00 (2 bytes)
  • The number of registered passengers in the interval 10:00 - 12:00 (2 bytes)
  • The number of registered passengers in the interval 12:00 - 14:00 (2 bytes)
  • The number of registered passengers in the interval 14:00 - 16:00 (2 bytes)
  • The number of registered passengers in the interval 16:00 - 18:00 (2 bytes)
  • The number of registered passengers in the interval 18:00 - 20:00 (2 bytes)
  • The number of registered passengers in the interval 20:00 - 22:00 (2 bytes)
  • The number of registered passengers in the interval 22:00 - 0:00 (2 bytes)
  • The key to validating information (protection against forgery) (2 bytes)
  • Control information (2 bytes)

There are situations when the driver must change the route during the shift. As you see above, to preserve the informativeness of the Driver's Personal Card in such cases, 5 identical groups of fields are entered:

  • Route number
  • Time to start work on the route
  • End time on the route
  • Total route mileage (km)
  • Total number of runs from "start to finish"
  • Total number of runs from "end to start"
  • Total downtime (minutes)
  • Total time in the state "No Personal Driver Card" (minutes)
  • The traffic interval between 6:00 - 8:00 (minutes)
  • The traffic interval between 8:00 - 10:00 (minutes)
  • The traffic interval between 10:00 - 12:00 (minutes)
  • The traffic interval between 12:00 - 14:00 (minutes)
  • The traffic interval between 14:00 - 16:00 (minutes)
  • The traffic interval between 16:00 - 18:00 (minutes)
  • The traffic interval between 18:00 - 20:00 (minutes)
  • The traffic interval between 20:00 - 22:00 (minutes)
  • The traffic interval between 22:00 - 0:00 (minutes)

Those, during the shift, the driver can change route up to 5 times. The route numbers, specified in the explained above field of Route's Change Mask should be present in the route descriptor, supported by this vehicle (recorded in the controller's non-volatile memory). Otherwise, the controller must extinguish all indicators and issue a voice message "Mismatch of route maps" until the Driver's Personal Card removed.

At the very beginning of the shift, the driver receives his Personal Card with the route(s), automatically assigned by Transport Company software. If necessary, during the shift, further changes to the route are made by the driver manually. When he confirms the selection of the next route ("Confirm" button), the corresponding message is automatically sent to the Dispatch Center. The vehicle's controller automatically modifies and stores the relevant information in the memory of the Driver's Personal Card for the entire shift. At the end of the shift, the driver returns his Personal Card to the Transport Company, and its software automatically download information to the database.

Controller's Buttons

Control button

is located on the left side of the Control Module housing. It is desirable to perform it in the form of a spring-loaded slider with one fixed position. This button intended to prevent automatic activating of remote communication session with Transport Company software, if driver accidentally pressed one of the buttons in the group of Session Type Select. When the Control Button is pressed, the green LED of Control Button Confirmation lights up.

Buttons of Session Type Select

automatically initiate communication session with the dispatcher (with the Control Button pressed):

  • "First Aid", "Fire", "Police". When one of these buttons is pressed, an appropriate message is sent to the Dispatch Center, which is automatically recorded in the Transport Company database. At the same time, the Transport Company software provides voice and light signals to attract the attention of the dispatcher.
  • "Vehicle failure". Pressed in case the vehicle needs technical support of the Transport Company. At the same time, an appropriate message is sent to the Dispatch Center, which is automatically recorded in the Transport Company database. The Transport Company software provides voice and light signals to attract the attention of the dispatcher.
  • "Route". Intended for manual change of the Route Number by the driver. The Driver's Personal Card contains short descriptors of up to 5 routes (see above). Pressing this button scrolls through these routes until the desired number appears on the display. To lock the selection, the driver presses button "Confirm". In this case, a message about changing the route of this vehicle will be automatically sent to the Dispatch Center.
  • "Confirm". Intended to confirm certain actions of the driver. For example, if the Driver's Personal Card is withdrawn, the controller issues a voice message "Confirm the removal of the Driver's Control Card" at a rate of 1 every 5 seconds for 30 seconds. In this case, if the withdrawal is made by the driver (authorized), then he must click the "Confirm" button. Otherwise, the message "Unauthorized removal of the Driver's Personal Card", will be sent automatically to the Dispatch Center and recorded in the Transport Company database. The Transport Company software provides voice and light signals to attract the attention of the dispatcher.
  • "Request a connection". To be pressed if driver need to establish a voice connection with the Dispatch Center.
    NOTE: at the moment it seems to be an unnecessary function.

The buttons for Informing Passengers and the Dispatch Center

  • "Route Start/End". The driver presses this button when vehicle arriving to the end points of the route. An appropriate message is automatically sent to the Dispatch Center to be stored in the Transport Company database.
  • "Next Stop". When driver press this button, the controller issues a voice message to the passengers about the name of the current and next stops. If the 'scrolling line' installed in the cabin, then the corresponding information is displayed on them.

Display Elements

  • "Current Time". Indicates the real local time. The data source is the internal clock of MCU, synchronized by the GPS-receiver.
  • "Route No.". Shows the number of the current route. Data source - Driver's Personal Card.
  • "Communication Request LED". Flashing in addition to the audio signal when Dispatch Center establishes a voice communication with driver.
    NOTE: at the moment it seems to be an unnecessary function.
  • "Control Button Pressed Confirmation LED". Lights when the Control Button is pressed.
  • "Vehicle's Recommended Speed". Linear LED-indicator. Together with a special sound signal, provides the driver with information about vehicle's speed, required to reach the nearest stop at the scheduled time. The data source is a GPS-receiver (and optionally other standard methods of chosen MESH-network means).

Card of Cashless Payment of Travel

When using the cashless payment system, conflicts may occur if passenger tries to prove that he paid the fare in this vehicle, but the driver or conductor claims the opposite. To resolve the conflict, the Control Module provides a slot for the Cashless Card. The controller reads the card's data and if the last payment was not done in this vehicle, a voice message "The travel is not paid" appears. If the format of the card data does not correspond to the established standard (possibly a fake card), then a voice message "Non-standard card" is issued. If the last payment is made in this vehicle, the time and date of payment of the fare shall be reported by voice. For example, "The travel was paid on the tenth of May at zero fifteen." The year is not specified.

Vehicle's Controller Electronics

ktc schComposition:

  • MCU
  • Means of GSM communication support (intercity routes) or other MESH-network (city routes)
  • GPS-receiver
  • Control buttons and display elements for the driver
  • Sensor of Illumination for automatic adjustment of external Information Display modules brightness
  • Terminals for the Driver's Personal Card and Cashless Payment Card (for the settlement of disputable issues with the passenger)
  • The power supply unit, considering the needs of up to 4 external Information Display Units, the "scrolling line" panel and 3 Cashless Payment Terminals

Additional elements:

  • Interior Information Display modules
  • Outdoor elements to display the Route Number. It seems sufficient 2 (front and right), but can be up to 4.
  • "Scrolling line" panel inside the cabin (optional)
  • The terminal of Cashless Payment Card (optional). It seems sufficient to install up to 3 terminals in one vehicle.

NOTE: in the picture, the optional elements are highlighted in yellow