JP2589311B2 - Taxi operation status management device - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION [Industrial Application Field] The present invention receives operation information of a taxi vehicle transmitted from a taxi vehicle to a base station by radio waves, and operates the taxi vehicle based on the received operation information. The present invention relates to a taxi operation status management device for managing status.

[Problems to be solved by conventional technology and invention]

Conventionally, as a device of this type, a taxi vehicle transmits to a base station, in conjunction with a toll meter mounted on the taxi vehicle, empty information of the taxi vehicle, dynamic information indicating the actual vehicle state together with information indicating a vehicle number, and Based on the information, the base station displays the dynamics of all vehicles on a cathode ray tube so that the dynamic state of all vehicles can be grasped instantaneously and comprehensively so that an efficient dispatch command can be issued. Have been.

In the above-described conventional system, it is impossible to know the business situation of the taxi vehicle on the day, in particular, the actual number of vehicles, so that it is impossible to allocate vehicles from the viewpoint of averaging the sales of the taxi vehicle. Of course, the dynamic information from each taxi vehicle is counted on the base station side,
It is also possible to know the actual number of vehicles, but if you do this, the taxi vehicle will be out of business or the actual number of vehicles when operating outside the radio wave reach range, and after grasping the exact operation situation There is a drawback that it is not possible to dispatch vehicles by train.

The present invention has been made in view of the above points, and an object of the present invention is to provide a taxi operation status management device capable of accurately grasping a more detailed operation status of a taxi vehicle.

[Means for solving the problem]

In order to solve the above problems, a taxi operation status management device according to the present invention performs a radio call with a radio 22 mounted on a taxi vehicle 2 as shown in the basic configuration diagram of FIG. A wireless device 12 for receiving data including information such as a vehicle number, a tariff state, and the number of actual vehicles detected from the wireless device 22 for each tariff change of the toll meter, and a wireless device 12 provided in advance corresponding to each taxi vehicle, A vehicle data storage unit 141c having a storage area for storing information such as a tariff state and the number of actual vehicles, and a vehicle data storage unit 141c based on data received from the taxi vehicle 2 through the wireless device 12, such as a tariff state and the number of actual vehicles. Writing means 141a for writing information and the vehicle data storage means 141c
Display means 141e for displaying the tariff state of each taxi vehicle together with information such as the number of actual vehicles based on the stored contents of the taxi vehicles.

[Action]

According to the above configuration, the operator who manages the operation of the Tashi vehicle 2 can know the current tariff state of the taxi vehicle 2 and the actual number of vehicles by looking at the display means 141e. It is possible to allocate an appropriate one of the taxi vehicles 2 that are in an empty state in a direction to make the sales uniform.

〔Example〕

Hereinafter, an embodiment of a taxi vehicle operation status management device according to the present invention will be described with reference to the drawings.

FIG. 2 is a block diagram showing a vehicle monitoring system to which a taxi vehicle operation status management device according to the present invention is applied;
In the figure, reference numeral 1 denotes a base station which performs transmission and reception with a taxi vehicle 2 as a mobile station. The base station 1 has an antenna 11 and a radio device for transmitting and receiving signals through the antenna 11.
The system includes a modem 12, a modem 13 for modulating and demodulating signals transmitted and received by the wireless device 12, and a taxi vehicle operation status management device 14 configured using a personal computer. On the other hand, the taxi vehicle 2 includes an antenna 21, a radio 22 for transmitting and receiving signals through the antenna 21, a modem (MODEM) 23 for modulating and demodulating signals transmitted and received by the radio 22, and an electronic toll meter 2.
And 4.

The electronic toll meter 24 includes a travel sensor that generates one distance pulse every time the taxi vehicle travels a certain distance, and a plurality of tariff switches that switch the tariff to a state such as pick-up, surcharge, rental, empty, and payment. A tariff switching unit, a charge indicator, a memory for storing meter index data, an index indicator for displaying a meter index, and the like are provided.A distance pulse from the travel sensor, a tariff status signal from the tariff switching unit, a fare system, etc. A charge for each business is calculated, the charge is displayed on the charge display, and a wind sign signal for displaying the tariff state on the wind sign is output. The meter index data stored in the memory of the electronic toll meter 24 includes the sum of the fees for each business, the total of business hours, the total of business hours, the total of running hours,
There are the total of the idling distance, the total of the mileage, the total of the business mileage, the total number of times immediately after (the frequency exceeding the basic charge), the total number of business times, etc., and these meter index data are the empty car tariff of the tariff switching section. It is serially output in a predetermined format according to the switching to the state.

The MODEM 23 has a buffer memory for holding meter index data serially transmitted from the toll meter 24 in response to an empty vehicle tariff until the next empty vehicle tariff. Part or all of the meter index data stored in the buffer memory is read out when the wind sign information changes from the charge meter 24, when polling from the base station 1, when the microphone is pressed by the wireless device 22, or the like. The signal is transmitted to the base station 1 via the radio 22 and the antenna 21.

The wireless device 12 of the base station 1 performs transmission and reception with the wireless device 22 of the mobile station 2. MODEM13 is based on command information on polling sent together with the vehicle code from the taxi vehicle operation status management device 14 by the operation of the operator,
The polling signal is transmitted to the mobile station 2 through the radio 12 and the antenna 11
In addition, the meter index data transmitted from the mobile station 2 is stored in a predetermined area of the temporary buffer memory, and is used for the taxi vehicle operation status management by the taxi vehicle operation status management device 14.

FIG. 3 shows a specific example of the configuration of the taxi vehicle operation status management device 14, which comprises a personal computer (personal computer) 141 and a code selector 142 having a number of keys. The personal computer 141 stores a central processing unit (CPU) 141a that operates according to a predetermined control program, a read-only memory 141b storing a control program of the CPU 141a, and the like, and stores data processed by the CPU 141a and a work area of the CPU 141a. It has a random access memory (RAM) 141c used as vehicle data storage means to be used, and the CPU 141a has a CRTI
CRT 141e, LPTI / 0 as display means via circuit 141d
Line printer (LPT) 141g, FDDI / 0 via circuit 141f
Floppy disk driver (FDD) 141 via circuit 141h
i, keyboard (KB) 141k via KBI / 0 circuit 141j, first
And the second RS-232C circuits 141l and 141m are connected respectively. The first RS-232C circuit 141l includes the MODEM 13 and the personal computer 141, and the second RS-232C circuit 141m includes the code selector 142.
And the personal computer 141 are interconnected.

There are various tasks performed by the CPU 141a in accordance with the control program stored in the ROM 141b.

The first is the menu function, which is a CRT1
Perform the tasks of displaying the menu screen on 41e, selecting a job, and shutting down the system. The menu screen is displayed as shown in FIG. 4, and the menu is selected by selecting a job number by operating the key of the code selector 142.

The first wireless dispatching program will be described later.
First, the menus 2 to 5 will be outlined.

In the basic vehicle registration 2, a vehicle registration screen as shown in FIG. 5 is displayed on the CRT 141e, and a code selector driver management file as shown in FIG. 6 is mainly polled in a predetermined area of the RAM 141c for each vehicle. To create and collect data. For example, the total revenue is polling 1 and polling AL
At L (to be described later), the number of times of operation × basic fee + number of times of pick-up ×
It is obtained by calculating the pick-up car charge + the number of times after the event x the fee after the event, and this value is the next polling 1 and polling AL
It is held until L time. The number of business hours, the number of business hours, and the number of pick-ups are registered with specific digits of the meter index at the time of departure on the day, and these are used for calculating total revenue at polling 1 and ALL. The operating mileage and the total mileage are registered with a specific digit of the final index at the time of departure on the day, and are used to calculate the actual mileage. The running time is used to calculate the steering time,
Registered at a specific digit of the exponent. The business travel km and business hours are registered with specific digits of the final index at the time of delivery on the day. The steering wheel time is obtained by calculating traveling time (minute) −business traveling time (minute) + business time (minute).

In the code selector management of 3, the registration of the district name and the employee name to the code selector 142, registration change, and cancellation are performed.
Launch registered contents with LPT141g.

In the basic company registration of 5, registration of company name, company code,
Register vehicle basic charges and targets (sales, number of operations).

In the above-mentioned radio dispatching program, first, initialization is performed. In this initialization, tasks such as initialization of the RS-232C circuits 141l and 141m, reading of the code selector file (FIG. 7) from the code selector 142, and determination of interruption or not are performed. The job branches depending on the presence or absence of the interruption, and if there is no interruption, the job of registering the crew attached to the dispatched vehicle is performed. If there is an interruption, the job of registering the crew is skipped and the interruption file (work file (FIG. 8) Read from the floppy disk with the same contents as in)).

After the completion of the above-mentioned crew registration or reading of the interruption file, a search of the buffer memory of the MODEM 13 and the code selector 142 is performed in this order, and if there is a reception of the MODEM 13 by this search, a MODEM reception process is performed, and the code selector 1 is executed.
If there are 42 inputs, a code selector input process is performed. If both are not present, the system clock is counted up and the above search is repeated.

In the MODEM receiving process, the type of the received data is determined based on the information of the first byte of the actual empty vehicle data (FIG. 9) and the polling data (FIGS. 10 to 12) stored in the buffer memory of the MODEM 13. , Branching the work ahead. In the code selector input process, the code selector 142
The primary selection of the submenu is performed by the input from. The primary selection of this submenu is to issue daily and monthly reports, re-register crewmembers, suspend and stop dispatching operations, enter actual / vacant areas, assign vehicles, enter movement information, switch screens, and perform tasks such as polling. Branch to

The work performed by the CPU 141a mainly on the above-described vehicle allocation management program will be described in detail below.

The CPU 141a executes a task based on the control program shown in the flowcharts of FIGS. 13 to 26 in response to the power-on of the personal computer 14, and the code selector 142 is connected in the first step S1 of the flowchart (menu) of FIG. Open the SR-232C circuit 141m, and wait for an operation of any key of the court selector 142 in step S2. If there is a key input from the code selector 142 in step S2, the process proceeds to step S3, where it is determined whether the key input is normal. If the determination in step S3 is NO, the process returns to step S1, and if the determination is YES, the process proceeds to step S4, where a menu is displayed on the screen of the CRT 141e as shown in FIG. Then, in the subsequent step S5, the input of the “0” to “5” keys of the code selector 142 is waited.

When there is a key input, it is determined in step S6 whether the key input is "0" or "1". If the determination is "0", the flow advances to step S7 to close the RS-232C circuit 141m. In the next step S8, the end display is displayed on the CRT 141e, and then the execution of the flowchart ends.

When the determination in step S6 is "1", it is determined that the wireless dispatching program has been selected, the process proceeds to <A> in FIG. 14, and the determination is NO.
In step S10, the process proceeds to step S10. In step S10, it is determined whether or not the key input is "2". If the determination is YES, a program (not shown) for performing vehicle basic registration is executed, and if the determination is NO, the process proceeds to step S11.

In step S11, it is determined whether or not the key input is "3". If the determination is YES, the code selector management program is executed to register, change, and cancel the district name and the crew name in the code selector 142. At the same time, the registered data is launched by the LPT 141g.

If the determination in step S11 is NO, the process proceeds to step S12, where it is determined whether or not the key input is "5". If the determination is YES, a program for performing company basic registration is executed. In this basic company registration program, a company name, a wireless code, basic and other charges for each vehicle type, and the like are registered. If the determination in step S12 is NO, step S4
And the steps described above are executed again.

The above-described radio dispatching program starts from step S20 in the flowchart (initialization) in FIG. In step S20, the RS-232C circuits 141l and 141m are opened, and in subsequent step S21, one bit is stored in the buffer memory of the MODEM 13.
After reading the bytes of data, it is determined in step S22 whether or not there is data. Thereafter, initialization is performed by repeatedly executing steps S21 and S22 until there is no more data in the buffer memory, and proceeds to step S23 when the determination in step S22 is NO.

In step S23, a code selector file is read from code selector 142 and stored in a predetermined area in RAM 141C. The code selector file is a dictionary indicating the correspondence between key codes and district names or crew names, and can be created for 800 district names and crew names. Each file has a structure as shown in FIG. 7, where the 10-byte "FILLER" contains the kanji data of the district name or crew name, and each 1-byte "shift-in"
And "shift out" to start and end kanji data,
A waiting code is stored in a 4-byte “standby place”, and a key input code is stored in a 4-byte “code”.

After reading the code selector file in step S23, the process proceeds to step S24, where the interrupted file is opened, and it is determined in the following step S25 whether or not there is an interrupted file. In the case of interruption on the day, there is an interruption file, otherwise, there is no interruption file. Steps
When the determination in S25 is NO, the process proceeds to <C> in FIG. 15, and when the determination is YES, the process proceeds to <D> in FIG.

The interruption file is data temporarily saved on a propi disk so that the data stored in the RAM 141c is not lost when the operation of the personal computer 141 has to be stopped for some reason, as shown in FIG. It has the same configuration as the work file. In FIG. 8, each item consists of 4 bytes, and YEAR, MONTH, H0, M0, S0 contain year, month, day, hour, minute, second data, H0 based on the system clock.
(I), M0 (I) and S0 (I) indicate the elapsed time of the empty vehicle, H1
(I), M1 (I), S1 (I) show actual vehicle elapsed time, H2
(I), M2 (I), S2 (I), dispatch elapsed time, KURUMA
(I) vehicle number, CHIKU0 (I) departure, CHIKU1 (I)
Stopover at CHIKU2 (I), round trip at OHFUKU (I), tariff status at STAT (I), empty position at KUUSHA (I, 0), KUUSHA (I, 0) at JUN (I) Same empty ranking, KAIS
U (I) is the actual number of vehicles, JRC (I), JRD (I) and JRF (I)
The display color and the like of a specific portion on the CRT 141e are respectively stored, and Nos. 23, 24, 27 and 30 are unused.

The flowchart (crew member registration) in FIG. 15 is a case where there is no interruption file, and performs a job for registering the dispatched vehicle and the crew. First, in the first step S30, a message to the effect that the date should be input is displayed on the CRT 141e, and in the subsequent step S31, the input of the date from the code selector 142 is waited. If there is an input from the code selector 142, it is displayed on the CRT 141e in the next step S32, and in a succeeding step S33, an input for confirming whether or not the input displayed on the CRT 141e is correct is waited. Thereafter, in step S34, it is determined whether or not the confirmation input in step S33 was "correct". When the determination is NO, the process returns to step S30, and when the determination is YES, the process proceeds to step S35. Step S3
In step 5, after performing the process for the hour and minute input in the same procedure as in steps S30 to S33 described above, the process proceeds to the next step S36.

In step S36, a message indicating that crewmember registration is to be performed is displayed on CRT 141e, and in step S37, input of a vehicle number by code selector 142 is awaited. Step S37
When the vehicle number is input in step S38, the registered vehicle is searched for in the next step S38, and it is determined whether the input is OK or not in the next step S3.
Judge at 9. When the determination in step S39 is NO, the process returns to step S37, and when the determination is YES, the process proceeds to step S40.

In step S40, input of the crew name by the code selector 142 is awaited.
Search for crew names. The result of the search is determined in the following step S42, and when the crew name is duplicated, the fact is displayed on the CRT 141e in step S42 'and the process returns to step S40, and when the input is OK, the process proceeds to step S43.
When the input is NG, the process returns to step S40. In step S43, a message indicating that the entered crew name should be confirmed is displayed on CRT1.
The process goes to 41e, and in the subsequent step S44, the end of the crew registration or the continuation input is waited. The input in step S44 is determined in step S45. If the determination is continued, the process returns to step S37, waits for the input of the next vehicle number, and if the determination is completed, proceeds to <E> in FIG. .

The determination in step S25 described above with reference to FIG. 14 is YES,
If there is an interrupted file, the process proceeds to <D> in the flowchart (search) in FIG. <D> in FIG. 16 corresponds to step S5
Starting from 0, in this step S50, the FDD 141i is operated to read the interrupt file from the floppy disk. This reading is performed for each predetermined unit, and it is determined in the next step S51 whether or not there is data in the read.
If the determination in step S51 is YES, the process returns to step S50,
When the determination is NO, the process proceeds to step S52 assuming that all the interruption files have been read.

In step S52, a comprehensive screen as shown in FIG. 27 is displayed on the CRT 141e, and in the next step S53, the MODEM1
Search one byte of the buffer memory of 3. Thereafter, the process proceeds to step S54, where it is determined based on the search in step S53 whether or not there is a reception. If the determination in step S54 is YES, the flow chart of FIG.
F>, and when the determination is NO, the process proceeds to the next step S55. In step S55, a search of the buffer memory of the code selector 142 is performed.
In S56, it is determined whether or not there is a reception. Step S56
If the determination is YES, the process proceeds to <G> in the flowchart of FIG. 18 (code selector input process), and if the determination is NO, the process proceeds to step S57, where the time index of the work file of each vehicle is incremented by +1. It returns to step S52.

When the determination in step S54 is YES, <F in FIG.
Then, in the first step S60, it is determined whether or not the command (No. 1) of the actual empty vehicle data in FIG. 9 is "F0". If the determination is YES, the process proceeds to <H> in the flowchart of FIG. 19 (distribution of received data) when the radio of the taxi vehicle is the microphone press, and to NO, the process proceeds to step S61. In step S61, it is determined whether or not the command is "F1". If the determination is YES, the flow proceeds to <H> in FIG. 19 when the tariff of the charge meter is changed or the position switch is on,
When the determination is NO, the process proceeds to step S62.

In step S62, it is determined whether or not the command is "F2". When the determination is YES, the flow advances to step S63 in the case of a call request, and here, the work file No. 21STAT of the vehicle is read.
After (I) is set to "2", the process proceeds to <H> in FIG. Steps
If the determination in S62 is NO, the process proceeds to step S64, in which it is determined whether the command is "F3". If the determination is YES, the emergency switch is determined to be on, and in step S65 the work file of the vehicle is After setting No. 21 STAT (I) to "9", the process proceeds to <H> in FIG. If the determination in step S64 is NO, the process proceeds to step S66, where it is determined whether the command is "F4". If the determination in step S66 is YES, it is determined that continuous pressing is performed, and STAT (I) is set to "7" in step S67.
After that, the process proceeds to <H> in FIG. 19, and if the determination is NO, the process proceeds to step S68. In step S68, the command is "F
It is determined whether it is 5 "or not. If the determination is YES, the polling answer is determined, and the process proceeds to <I> in the flowchart (reception of polling data) in FIG. 20. If the determination in step S68 is NO, the process proceeds to step S69. After performing the error processing, an error is displayed in step S70, and the process returns to step S55 of <J> in FIG.

<In the flowchart of FIG. 19 (distribution of received data)
H>, in the first step S80, the remaining data is read from the buffer memory of the MODEM13.
Proceed to S81. In step S81, it is determined whether or not the command (No. 1) of the actual empty vehicle data in FIG. 9 is "F3".
In the case of ES, the process proceeds to step S82, where emergency processing is performed. If the determination in step S81 is NO, the process proceeds to step S83, where it is determined whether the meter (No. 5) of the actual empty vehicle data in FIG. 9 is "E2". The determination in step S83 is YE
If S, proceed to step S84, where the work file
Set STAT (I) to Ride status “5” and color code,
Other processing is performed, and when the determination is NO, step S85
Proceed to.

In step S85, it is determined whether or not the meter (No. 5) is "E3". When the determination is YES, the process proceeds to step S86, where the STAT (I) of the work file is set to the empty vehicle status "1" and Color classification and other processes are performed, and when the determination is NO, the process proceeds to step S87. In step S87, it is determined whether or not the meter is "E4". When the determination is YES, the process proceeds to step S88, where the STAT (I) of the work file is determined.
Is set to the pick-up status “11”, color-coded, and other processes are performed. When the determination is NO, the process proceeds to step S89.
In step S89, it is determined whether or not the meter (No. 5) is "E5". When the determination is YES, the process proceeds to step S90, where the STAT (I) of the work file is set to the additional status "13". And perform other processing such as color coding,
When the answer is O, the process proceeds to step S91.

After performing error processing in step S91, the CRT 141e displays an error in step S92.
J> Return to step S55. On the other hand, steps S82 and S8
After execution of 4, S86, S88 and S90, the process proceeds to step S93, where it is determined whether or not the tariff has changed from an actual vehicle to an empty vehicle.If the determination is YES, the process proceeds to step S94, where the actual After adding the empty vehicle data as a daily report file having the form shown in FIG. 28, if the determination is NO, the process skips step S94 and proceeds to step S95. In step S95, page data is created based on the vehicle code.
After switching the page screen of the CRT141e in S96, <J> in Fig. 16
Return to step S55.

As is clear from the description of the flowchart in FIG. 19 described above, the CPU 141a of the personal computer 141 executes the steps S80 to S95 to store the paging data by the vehicle code in the RAM 141c based on the data received from the taxi vehicle 2 through the wireless device 22. As a means for writing information such as the tariff state and the number of actual vehicles.

Flowchart of Fig. 20 (Reception of polling data)
<I> in the first step S101, MODEM1
The remaining data is read from the buffer memory of No. 3, and in the next step S102, No. 3 of the polling reception data is read.
I see. Subsequently, the process proceeds to step S103, where the above No. 3
Is “F1”, and if the determination is YES, the process proceeds to step S104. In step S104, the current time data is fetched, and thereafter, the process proceeds to step S105 to calculate (1)
I do. In calculation (1), an index calculation (current index−attendance (previous) index) and a revenue calculation (number of business operations × basic charge + number of times after service × number of times after service + number of times of picking up × service charge) are performed on the received data. After the calculation is completed, the process proceeds to step S106, where a predetermined area of the file in FIG. 6 is updated, and then the process returns to step S55 of <J> in FIG.

If the determination in step S103 is NO, step S108
Then, it is determined whether or not the above No. 3 is “F2”. If the determination is YES, the process proceeds to step S109. In step S109, the index is calculated by calculation (2), and then the process proceeds to step S106. When the determination in step S108 is NO, the process proceeds to step S110, where it is determined whether or not the above No. 3 is "F3". If the determination in step S110 is YES, the process proceeds to step S110, where the calculation time (3) is used to calculate the handle time (running time (minute) -business running time (minute) + business time (minute)) in addition to the index calculation. And then step S106
Proceed to. If the determination in step S110 is NO, step S112
After displaying an error on the CRT141e at <
J> Return to step S55.

If the determination in step S56 described above with reference to FIG.
<In the flowchart of FIG. 18 (code selector input processing)
G>, in the first step S120, it is determined whether or not the input from the code selector 142 is a vehicle code. If the determination in step S120 is YES, the process proceeds to <K> in the flowchart (vehicle code input) in FIG.
If NO, the process proceeds to step S121. In step S121, it is determined whether or not the input from the code selector 142 is "0". When the determination is YES, the process proceeds to <L> in the flowchart (submenu) of FIG. 22, and when the determination is NO, <M in the flowchart of FIG. 23 (polling selection)
Go to>.

When the determinations in steps S120 to S122 are NO, the process proceeds to step S123, where the waiting order is arranged. Thereafter, the process proceeds to step S124, where a map screen as shown in FIG. 29 is displayed on the CRT 141e, and then, to step S125, where the time index of the work file of each vehicle is incremented by 1, and then < Return to E>.

In the first step S130 of <K> in FIG. 21, it is determined whether or not the input vehicle code is a registered one. If the determination is NO, the process proceeds to step S131, and the unregistered display is displayed as a CR.
After T141e, the process returns to step S52 of <E> in FIG. If the determination in step S130 is YES, step S13
The process proceeds to step 2, where the page is switched to the screen of the input vehicle code, and then the process proceeds to step S133. In step S133, STAT (I) is searched from the file of the vehicle, and
Proceeding to S134, a page switched page is displayed on the CRT 141e here.

Thereafter, the process proceeds to step S135, where the above-described step S133 is performed.
It is determined whether or not the vehicle is a real vehicle based on the STAT (I) searched in the above. If the determination in step S135 is YES, the display of the vehicle on the CRT 141e is performed in a predetermined color in step S136, and then the process proceeds to step S137, where the code selector 142 waits for the input of the actual vehicle area and the input of the destination area. If the determination in step S135 is NO, the process proceeds to step S138, where it is determined whether or not the vehicle is empty, and the determination is YES.
If so, the process proceeds to step S139. In step S139, the display of the vehicle on the CRT 141e is performed in a predetermined color, and then the process proceeds to step S140, where the vehicle has a dispatch area input and a destination area input. If the determination in step S138 is NO, the process proceeds to step S141. Here, it is determined whether the vehicle is a moving vehicle. If the determination is YES, the process proceeds to step S142. In step S142, the display of the vehicle on the CRT 141e is performed in a predetermined color, and then the process proceeds to step S143, where the code selector
Wait for the destination district input by 142. If the determination in step S141 is NO, the process proceeds to step S144, in which it is determined whether or not the vehicle is a dispatched vehicle.If the determination is YES, a display indicating that fact is displayed on the CRT 141e, and then in the next step S146 Wait for a cancel input by the code selector 142.

When the determination in step S144 is NO, or in step S1
After execution of steps S140, S143, and S146, the process proceeds to step S147, where it is determined whether or not there is an input from the code selector 142. If the determination in step S147 is YES, step S13
Returning to step 4, when the determination is NO, the process proceeds to step S148, where the work file is changed based on the input by the code selector 142, and displayed on the CRT 141e with the changed work file data in the next step S149. After that, the process returns to step S52 of <E> in FIG.

In the first step S150 of <L> in FIG.
After closing the RS-231C circuit 141l for the DEM 13 to disable reception, the process proceeds to the next step S151, where the 27th
Tasks as indicated by the dotted lines are displayed on the command line of the display screen shown in the figure. After that, the process waits for an input of any of the business numbers 1 to 4 by the code selector 142, and when there is an input, the process proceeds to step S153, and it is determined whether or not the input number is "1".

If the determination in step S153 is YES, the process proceeds to <C> in FIG. 15, and re-registration is performed. If the determination in step S153 is NO, the process proceeds to step S154, where the input number is "2". Determine whether or not. When the determination in step S154 is YES, the process proceeds to <N> of the flowchart (daily and monthly report output) in FIG. 24A, and the book table output operation is performed. When the determination in step S154 is NO, the process proceeds to step S155. In step S155, it is determined whether or not the input number is "3". If the determination is YES, the process returns to step S4 of <B> in FIG. 13 to display the menu. If the determination in step S155 is NO, the process proceeds to step S155.
Proceed to S156. In step S156, it is determined whether or not the input number is "4". If the determination is YES, it is determined that the job is interrupted, and the process proceeds to step S157, where a work file or the like is written in the interrupt file of the floppy disk. Returning to step S4 of <B> in FIG. 13, the menu screen is displayed.
If the determination in step S156 is NO, the process proceeds to step S158, where the RS-232C circuit 141l for the MODEM 13 is opened, and then returns to step S52 of <E> in FIG.

In the first step S160 of <M> in FIG. 23, the code selector for the screen display instruction at the time of polling
The input of “EXIT”, “existence”, and “absence” by 142 is awaited, and the input is determined in the following step S161. Step S161
If the input is "EXIT" as a result of the determination, the process returns to step S52 of <E> in FIG. 16, and if the input is "YES" in the determination, the process proceeds to step S162, where the CRT 141e screen is displayed as a polling screen, If the input is "none", step S1
Go to 63.

In step S163, “EXIT” by the code selector 142 regarding the selection of the previous polling data,
It waits for an input of “presence” or “absence”, and determines the input in the following step S164. If the input is “EXIT” as determined in step S164, the process returns to step S52 of <E> in FIG.
If the input is “yes” as a result of the determination, <O in the flowchart (previous polling data display or printing) in FIG.
>, If the input is “absent” by the determination, step S1
Proceed to 65.

In step S165, input of “EXIT”, “existence”, and “absence” by the code selector 142 for the selection of the designated vehicle is waited, and in step S166, the input is determined. If the input is “EXIT” as determined in step S166, the process proceeds to step S52 of <E> in FIG. 16, and if the input is “present” as determined, the process proceeds to step S167. If the input is “absent” as determined. Goes to step S168. In step S167, the control waits for the input of the vehicle number from the code selector 142, and if there is an input, it is determined whether or not the vehicle number input in the next step S169 is unregistered. Steps
If the determination in S169 is YES, the process returns to step S165, and the determination is N
In the case of O, the process proceeds to step S170, where the vehicle code corresponding to the vehicle number is inserted into the transmission data for polling, and then the process proceeds to step S168.

In step S168, the input of the polling type is selected by the code selector 142, and the input is determined in the following step S171. If the input is “EXIT” as determined in step S171, the process returns to step S52 of <E> in FIG. 16, and if the input is “present”, the process proceeds to step S172, and if the input is “absent” as determined. Returns to step S168. In step S172, a polling condition is generated by inputting the presence or absence of the designated vehicle in step S165, and instructing the polling type in step S168, and then the process proceeds to <P> in the flowchart of FIG. 26 (polling transmission and reception).

In the first step S180 of <N> in FIG. 24 (a), a screen for selecting which of a daily report and a monthly report is to be output is displayed on the CRT 141e, and the selection by the code selector 142 is performed in the subsequent step S181. Waiting for an input, the input is determined in the following step S182. Step S182
If the input is "EXIT" according to the determination in step S52, the process proceeds to step S52 of <E> in FIG. 16, if the input is "daily report" according to the determination, the process proceeds to step S183. Proceed to S184. In step S183, the process waits for an input to select whether the daily report to be output is that of the current day or the past, and then determines the input in step S185.

If the input is “EXIT” as determined in step S185, the first
The process proceeds to step S52 of <E> in FIG. 6, and if it is determined that the input is “the current day”, the process proceeds to step S186, where date data of the current day is inserted. Thereafter, the process proceeds to step S187, where a screen for selecting whether the data to be output is that of the designated vehicle or that of all vehicles is displayed on the CRT 141e. Then, in the next step S188, the code selector 14
Wait for a selection input by 2 and then determine input in step S189.

If the input is “EXIT” as determined in step S189, the first
The process proceeds to step S52 of <E> in FIG. 6, and if a designated vehicle is selected by inputting "designation", the process proceeds to step S190.
If “all” is input and all vehicles are selected, the process proceeds to <N−1> in FIG. 24 (b). In step S190, 1 is inserted into MAX, and the process proceeds to <N-2> in FIG. 24 (b).

If the input is “past” and the output of the past daily report file is selected by the determination in step S185, the process proceeds to step S191, where it is determined that date data should be input.
Display on CRT141e. After that, in the next step S191, the input of the date data by the code selector 142 is waited, and when there is the input, the CRT 141e displays that the input date should be confirmed in the following step S192. And the next step S19
In 3, wait for confirmation input by the code selector 142,
At the subsequent step S194, a confirmation input is determined. Confirmation input
In the case of YES, the process proceeds to step 195, where the input date data is inserted on the search date, and then the process proceeds to step S187. If the confirmation input is NO, the process returns to step S190.

In step S184, after inserting the maximum value of the daily report file into the loop variable, the process proceeds to step S187.

<N-1> in FIG. 24 (b) starts in step S196,
Here, after inserting the maximum value of the vehicle registration into MAX, step S19
Go to 7. <N-2> in FIG. 24 (b) starts in step S197, where the daily report file is opened.
Proceed to S198. In step S198, it is determined whether to output a daily report or a monthly report.If the determination is a daily report output, the process proceeds to step S199,
If the determination is a monthly report output, the process proceeds to <N-3> in FIG. 24 (c).

In step S199, the title of the daily report is printed on the LPT 141g, and thereafter, the process proceeds to step S200, where data is extracted from the daily report file. Thereafter, the process proceeds to step S201, where a daily report as shown in FIG. 30 is printed on the LPT 141g based on the data extracted here. Subsequently, the process proceeds to step S202, where it is determined whether or not MAX = 1. If the determination is YES, the process returns to step S52 of <E> in FIG. 16, and if the determination is NO, the process proceeds to step S203. . In step S203, MAX-1 is calculated, and in subsequent step S204, it is determined whether MAX = 1. When the determination in step S204 is YES, <in FIG.
E> Return to step S52, and if the determination is NO, step S52
Return to 199.

<N-3> in FIG. 24 (c) starts at step S205,
Step S after printing the monthly report title LPT141g
Proceed to 206, where data is extracted from the daily report file. Then, in step S207, the value is added to MAX and Loop = L
Then, the process proceeds to step S208, where it is determined whether or not the data reading has been completed based on whether or not Loop = 0. When the determination in step S208 is YES, the process proceeds to step S209, and when the determination is NO, the process returns to step S206.

In step S209, a monthly report is printed on the LPT 141g, and in the next step S210, MAX = MAX-1 is calculated. Based on the calculation result, it is determined in the next step S211 whether MAX = 0 or not. If the determination is YES, the step S <E> in FIG.
Returning to 52, if the determination is NO, the total memory is cleared in step S212, and then the process returns to step S205.

<O> in FIG. 25 (a) starts in step S220, where the retrieval data is read from the vehicle data. Then step
Proceeding to S221, a message to the effect that the vehicle number should be entered is displayed on the screen of the CRT 141e, and in the subsequent step S222, the input by the code selector 142 is held.
At 233, the input is determined. If the input is "EXIT" as determined in step S223, the process proceeds to step S52 of <E> in FIG. 16, and if the input is "vehicle number", the process proceeds to step S224. When output is instructed, the process proceeds to step S225.

In step S224, uncollected data is checked, and the result is determined in the next step S226. In step S226, it is determined whether or not data is present in the memory.If the determination is YES, the process proceeds to step S277.If the determination is NO, the process proceeds to step S228, where it is displayed that there is no data on the CRT 141e. Return to S221. In step S227, a message indicating that screen output and printer output should be selected is displayed on CRT1.
41e, and in the next step S229, the code selector 1
Waiting for the selection input by 42, the input is determined in the following step S230.

If the input is “EXIT” as determined in step S230, the 16th
The process proceeds to step S52 of <E> in the figure. If it is "screen", the process proceeds to step S231.
The process proceeds to <O-1> in FIG. In step S231, the data of the designated vehicle is displayed on the screen of the CRT 141e in the form shown in FIG. 31, and in the next step S232, it is determined whether MAX is 0>, 0, or 0 <. When the determination in step S232 is 0>, the process returns to step S52 of <E> in FIG. 16, when it is 0, the process proceeds to step S233, and when it is 0 <, the process proceeds to step S2.
Return to 31. In step S233, after calculating MAX = MAX-1, the process returns to step S52 of <E> in FIG.

In step S225, after all the vehicle data are sorted, the process proceeds to step S234, where the data is expanded on the memory and MAX is inserted into the loop variable, and then the process proceeds to step S227.

In the first step S235 of <0-1> in FIG. 2B, the buffer of the LPT 141g is opened, and the next step S23
In step 6, it is determined whether or not the power of the LPT141g is turned on.
If the determination in step S236 is YES, the process proceeds to step S237. If the determination is NO, an error display of LPT141g is performed in step S238, and the process returns to step S235. In step S237, it is determined whether the LTP141g paper is OK. If the determination is YES, the process proceeds to step S239, and if the determination is NO, the process returns to step S235 via step S238.

In step S239, the title is printed by the LPT 141g, and in the following step S240, the data is printed in the form shown in FIG. Then proceed to step S241, where MAX
Is 0 or 0 <, and if the determination is 0, the process returns to step S52 of <E> in FIG. 16, and if 0 <, the process proceeds to step S242. In step S242, the row count is
It is determined whether 50> or 50 <. If the determination is 50>, the process returns to step S239. If the determination is 50 <, the process proceeds to step S243, where 1 is added to the row count and After calculating MAX = MAX-1, the process returns to step S240.

<P> in FIG. 26 starts in step S250, where it is determined whether or not there is a designated vehicle. If the determination is YES, the process proceeds to step S251, where 1 is inserted into the search MAX, and then the process proceeds to step S252. move on. When the determination in step S250 is NO, the process proceeds to step S253, where the maximum value is inserted into the search MAX, and then the process proceeds to step S252.

In step S252, it is determined whether polling is 1 or not. If the determination is YES, the process proceeds to step S254, and if the determination is NO
In the case of, the process proceeds to step S255. In step S255, it is determined whether polling is 2 or not. If the determination is NO, the process proceeds to step S257. If YES, the process proceeds to step S256. In step S257, it is determined whether polling is 3 or not. When the determination is YES, the process proceeds to step S258, and when the determination is NO, the process proceeds to step S259. In step S259, polling
It is determined whether it is ALL or not. If the determination is YES, the process proceeds to step S260. If the determination is NO, the process returns to step S52 of <E> in FIG.

In steps S254, S256, and S258, "F1", "F2", and "F3" are inserted into the transmission data, respectively.
Proceed to S261, where 1 is inserted into the loop variable. Next, the process proceeds to step S262, in which data is transmitted to the MODEM 13, and then the process proceeds to step S263, where data is received from the MODEM 13. Thereafter, it is determined whether or not there is a change in the received data by the switch S264.
At 265, the change data is inserted into the reception buffer memory, and the process proceeds to step S266. If the determination in step S264 is NO, skip step S265 and proceed to step S266.
Here, after calculating AX = MAX-1, the process returns to step S101 of <I> in FIG.

In step S260, 3 is inserted into the loop variable, and then the process proceeds to step S267, where it is determined whether MAX is 0 or 0 <. If the determination in step S267 is 0, the process proceeds to step S268. Here, Loop = Loop-1 is calculated, and then the process proceeds to step S269. If the determination is 0 <, the process immediately proceeds to step S269. In step S269, it is determined whether Loop is 0, 0 <, and when the determination is 0, <0 in FIG.
Returning to step S52 of E>, when the determination is 0 <, the process proceeds to step S270. In step S270, after inserting the next loop variable into the transmission data, step S101 of <I> in FIG.
Return to

Although omitted in the illustrated flowchart, CRT1
Display of 41e, waiting for input of code selector 142, and LPT 141
Obviously, in the printing step of g, the work for incrementing the data regarding the time in the work file is also performed in a timely manner.

(Effect)

As described above, according to the present invention, since the operator of the base station can know the tariff state of each taxi vehicle and the actual number of vehicles on the day, it is appropriate that the sales of all vehicles owned by the taxi company be averaged. You can dispatch vehicles.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a basic configuration of a taxi operation status management device according to the present invention, FIG. 2 is a block diagram showing a vehicle monitoring system to which the device of the present invention is applied, and FIG. 3 is an embodiment of the device of the present invention. 4 and 5 are diagrams showing examples of screens displayed on the CRT in FIG. 3, and FIGS. 6 to 12 are stored in a RAM or the like in FIG. 13 to 26 are flowcharts showing the work performed by the CPU in FIG. 3, and FIG. 27 is a diagram showing another example of the screen displayed on the CRT in FIG. FIG. 28 is a view showing a data file stored in the RAM in FIG. 3, FIG. 29 is a view showing an example of a screen displayed on the CRT in FIG. 3, and FIG. Fig. 31 shows an example of print output by PLT. Fig. 31 shows an example of the screen displayed on the CRT in Fig. 3. Fig. 32 shows printing by LPT in Fig. 3. Is a diagram illustrating an example of a force. 2. Taxi vehicle, 12, 22, wireless device, 141c vehicle data storage device, 141a writing device, 141e display device.

 ──────────────────────────────────────────────────続 き Continuation of the front page (72) Inventor Masayuki Seki 2771 Ooka, Numazu City (56) References JP-A-55-116198 (JP, A)

Claims (1)

(57) [Claims] 1. A data communication system for making a radio call with a radio device mounted on a taxi vehicle and including information such as a vehicle number, a tariff state, and the number of actual vehicles transmitted from the radio device every time the tariff of the toll meter changes. Wireless data receiving means, vehicle data storage means provided in advance corresponding to each taxi vehicle, and having a storage area for storing information such as the tariff state of the taxi vehicle, the number of actual vehicles, etc., received from the taxi vehicle through the wireless device Writing means for writing information such as a tariff state and the number of actual vehicles to the vehicle data storage means based on the obtained data; and a tariff state for each taxi vehicle based on the storage contents of the vehicle data storage means together with information such as the number of actual vehicles. A taxi operation status management device, comprising: display means for displaying.