JPH088630B2 - Image transmitter - Google Patents

Description

Description: TECHNICAL FIELD The present invention relates to an image transmitting apparatus that transmits an image signal, and more particularly to an image transmitting apparatus that includes a storage unit that stores the image signal.

<Prior Art> Conventionally, as such an image transmitting device, a facsimile machine having an image memory is known.

The image memory is extremely useful when the same image data is transmitted to various destinations, or the original image can be stored in the apparatus when it is not connected to the destination at the time of transmission.

However, since only the image signal of the document is stored in the image memory, the user cannot determine whether or not the data in the image memory can be erased.

<Purpose> In view of the above problems, an object of the present invention is to provide an image transmitting apparatus capable of identifying the date and time when the image in the storage means is stored.

<Embodiment> An embodiment of the facsimile apparatus for realizing the present invention will be described in detail below.

(Mechanical System) FIG. 1 shows a sectional view of the facsimile machine. In the figure, 41 is a CCD solid line image sensor, 42 is an imaging lens, 43 is a mirror, 4 is a document illumination lamp, 45 is a document feeding roller, 46 is a document discharging roller, 47 is a document feeding tray, 31
Is a document detection sensor that detects the presence or absence of a document on the paper feed tray.

Further, 34 is a roll paper storage cover, 35 is roll paper, 36 is an original and recording paper discharge tray, 37 is a cutter, 38 is a roll paper discharging roller, 39 is a roll paper conveying roller, 40 is a recording head, and 33 is a recording head. A roller paper cover sensor for detecting opening / closing of the cover 34.

In the figure, at the time of reading the original, the original on the original feeding tray 47 is conveyed by rollers 45 and 46. Lamp 44 at reading position P
The original is illuminated by the mirror and the reflected light is reflected by the mirror 43 and the lens.
An image is formed on the image sensor 41 via 42, and the image sensor 41 converts the development into an electric signal.

On the other hand, at the time of recording, the roll paper 35 is nipped and conveyed by the roller 39 and the head 40, and at the same time, the head is placed on the heat-sensitive roll paper 35.
An image is formed by 40. When the recording for one page is completed, the roll paper 35 is cut by the cutter 37 and discharged onto the paper discharge tray 36 by the roller 38.

(Basic Block) FIG. 2 (A) is a basic control block diagram of the facsimile machine of this embodiment. In the figure, reference numeral 1 is a reading unit for reading an original image and converting it into an electric image signal, and 3, 5, 7, as one mode thereof, a random access memory (hereinafter referred to as RAM) functioning as a buffer for temporarily storing the image signal, 9 is A first-in first-out RAM (hereinafter FIFORAM) that functions as an image memory that stores image signals for several pages.
A read-only memory (hereinafter ROM) that stores the operation program of the MPU23, 13 is a RAM that stores the flags and data that are necessary for the operation of the MPU, 15 is an operation unit that has an input key, a display, etc., and 17 is a thermal paper. A recording unit for recording copy images, received images and management data, 19 a modem for modulating transmission data and demodulating the received data, 20 a telephone, 21 a communication line 22 for controlling connection of the modem 19 or the telephone 20. A rope control unit (hereinafter NCU), 25 is a character generator that stores character fonts for transmitting the transmission time and the name of the transmission source as image data in addition to the original image and recording communication management data. The container (hereinafter CG), 23 controls the entire system
It is an MPU. In this embodiment, as the MPU 23, a 16-bit data bus 24 and an Intel 8086 capable of directly accessing a memory space of up to 4 megabytes are used.

Since the Merit using this MPU has a 16-bit data bus, it is easy to handle encoded image data. 20 for run length code
12-bit data is required to handle 48-bit data,
If you use an 8-bit MPU, you have to access it twice, but if it is 16-bit, you only need to access it once.

Moreover, since a large capacity memory space can be directly accessed,
Using the system memory as an image memory, it became possible to have the function of broadcasting. In the conventional device, an external memory unit or a memory that the MPU cannot access directly via the bus even within the device was used to have a broadcast function as an image memory, but the circuit became complicated, There was a problem such as enlargement of the device.

(Function of MPU) There are six types of basic functions of the MPU 23 as shown in Fig. 2 (B). Each function will be described below.

Encoding function (Run length → MH, MR code conversion, etc.) a) Run length → MH code conversion When performing encoding, first issue a 1-line read command to the reading unit 1. Then, the reading unit 1 converts the read image data of one line into a run-ings code and writes it in the RAM3, and the MPU23 reads out the run-ings code from the RAM3 and uses it to read the code conversion table in the ROM11. To convert to MH code. Conversion table is RO
MH code data, which is expanded on M11 and corresponds to the run indicated by the address, is written with the run / ings code as the address. The structure of the MH code data is shown in FIG.

In FIG. 3 (A), the MH code is entered in the upper 12 bits on the left. Since the MH code is a variable length code,
The code length information of the MH code is put in 4 bits to recognize the code length. Although the MH code is assigned to the upper 12 bits, the MH code table has a maximum length of 13 bits. In order to deal with this, focusing on codes with a code length of 13 bits, it can be seen that the beginning (MSB) of all codes starts with "0". Therefore, in the data in the conversion table, 12 bits excluding the leading "0" are used as the MH code, and information of the data length "13" is added. Then, when the data tone is "13" by drawing the conversion table, the MPU adds "0" to the beginning of the code.

Thus all MH codes and their code lengths are all
Since it fits in 16bit, processing by 16bit MPU (micro processing unit) is easy and fast.
You can look up the MH code.

b) Run length → MR code conversion The conversion to MR code is performed by MPU23 with reference to the basic flow shown in CCITT's T4 recommendation. The most frequent and important items in the basic flow are as follows. There is "white / black inversion detection of pixel". Therefore, the data written by the reading unit to RAM3 is run-length coded so that the detection can be performed easily.

The program flow for converting to MR code by the run length code is shown in Fig. 3 (B), and the parameters are shown.
The subroutine for determining b1 is shown in FIG.

In FIG. 3 (B), first, parameters a ₀ and b ₁ are initialized to 0, and the run length code next to the target line is read to determine a ₁ , and b ₁ is set in FIG. 3 (C). after determining in the routine, it is determined by calling the following RL code reference line b _2. And in the MR encoding routine of T4 recommendation
At the same time that the MR code is decided, the next value of the parameter a ₀ is decided.

In FIG. 3 (C) the parameter b ₁ is the right side of the target line from a _0, as defined by the recommendation that the a ₀ is the first color changing points of different colors (white, black), are determined.

Since the conversion to the MR code is performed from the run length code in this way, it is extremely fast and easy compared to the conversion from the raw image data.

C) CG code → MH code conversion This device has a function of converting information such as characters into MH code and transmitting it as image data in addition to the image data read by the reading unit. , First, with CG code, the raw data corresponding to the CG code is fetched from CG25, converted to run length code, and further converted to MH code for transmission. The conversion table output is not the run length code, but the raw data. The reason is that if you create a table with the run length, the number of codes will increase and a large CG table will be required. There is also a merit that by using raw data, decoding becomes unnecessary in the case of transmission in non-compressed mode such as G2 mode.

d) Handling of EOL In G3 mode transmission / reception, image data uses a line synchronization form, and EOL is used as a line synchronization signal for that purpose.
(End OF Line) is set. EOL consists of 11 consecutive "0" s plus 1 (1 or 0 is added in case of MR).

The MPU23 adds this E to the image data for each line end detection.
The OL is added and sent, but when adding this EOL,
The transmission time of the transmission line is calculated, and if it is less than the minimum transmission time, a fill bit is inserted to make it the minimum transmission time and then EOL is added. In the actual transmission, the MH code is temporarily stored in the FIFORAM 9, and the MPU reads the code from the RAM 9 and transmits it. Then, the calculation of the minimum transmission time and the insertion of the file bit are performed by MP
This is done when U23 reads the code from RAM9 and sends it. Therefore, the detection of the line end signal EOL when reading from the RAM 9 becomes an important problem. Therefore, this device uses the following methods to simplify EOL detection and EOL transmission when reading from RAM9.

 First, as a basic idea of handling EOL (1) EOL is added when writing to RAM9.

(2) EOL detection when reading from RAM9 is 0 for 2 consecutive bytes
Done in.

(3) When sending data from RAM9, 0 for 2 consecutive bytes
Of these, 0 of the 2nd byte is not transmitted.

There are three points. The two cases will be described below, depending on the case.

FIG. 4 shows the storage form of the data and EOL in the RAM 9 when "1" in the final data of the line exists in the final byte. In the figure, DT of the last byte A is image data. Byte A is padded with 0 after data DT, bytes B, C
Is set to 0, and 1X is inserted at the D byte. However,
Depending on the number of 0s inserted in byte A, the number of 0s before 1X of the Dth byte is changed as shown in the table below.

In this way, 11 0s can be secured even if EOL 0s in the memory are sent after removing 1 byte.

Next, FIG. 5 shows a storage form of data and EOL in the RAM 9 when "1" in the last data of the line does not exist in the last byte. As shown in the figure, when the data DT contained in the last byte A is all 0s, all 0s are inserted in the rest of byte A,
0 is also inserted in the next byte B. Then, in the byte C, the number n of 0s inserted in the byte A is subtracted from 11, and 0 is inserted, and then 1 × is inserted.

Since there is no last consecutive 0 or more 4 in the MH code, the number of 0s inserted in the A byte is not considered to be 4 or less.

Further, considering white line skip transmission, as a judgment criterion for all white, when 1 line is all white data, 0 of the second byte is distinguished as "01" (hexadecimal display).

By writing to FIFORAM9 with the above format, EOL detection at the time of reading from RAM9 is 0 for 2 consecutive bytes.
Or it can be easily done with 1 byte 0 and "01" (hex).
Further, when the read data is transmitted, the EOL can be easily transmitted by deleting the 0 (or "01") of the second byte. EOL can be sent without deleting the second byte 0, but by deleting it, unnecessary data can be prevented from being sent and the transmission time can be shortened.

Decoding function (MH, MR code → run length code) a) MH code → run length code conversion The encoding method is to fetch the MH code from the FIFORAM9 and perform the decoding using the MH → run length conversion table. , The way of drawing the table is slightly different from the run length → MH code conversion method described above.

FIG. 6 shows a conversion flow from MH code to run length code, and FIG. 7 shows a table. As is clear from the flow of FIG. 6, search the MH code bit by bit,
If it is 0, the data at the address indicated by the current address pointer is checked, and if it is "1", the data at the next address is checked. If the MSB is "1", the data is run length, and if the MSB is "0", the data is written to the address pointer and used for the next search. The MH code is searched bit by bit until the MSB finds "1" data (data starting with 8). MH code black "0000111" in Fig. 7.
The search example of From the figure, it can be seen that the above code is a run length code of "black 12".

And the conversion table is made different by the code of black and white. The reason is that the same MH code exists in different run lengths of black and white.

b) MR code → run length conversion A table search method similar to MH → run length conversion is performed using a conversion table, but the MSB = 1 data is not the run length code, but the jump destination address of the program is written. ing. Then, at the jump destination, processing corresponding to the MR code is performed to generate a run length code.

Since MR encoding is a two-dimensional compression encoding method, 1
There is no run length code corresponding to one MR code. Since the run length code must be created using the MR code based on the data of the previous line, the jump destination address of the program is written in the table. FIG. 8 (A) shows an example of a table search for MR code "000011".

(Calculation of minimum transmission time and insertion / deletion of Fill) When G3 is sent, EOL is added after 1 line of data, and the transmission time of 1 line of data sent at this time is calculated. Fi if it is less than the minimum transmission time
ll bit (data 0) is inserted and EOL is added after the time other than the minimum transmission time.

In this device, whether the transmitted data is longer than the minimum transmission time or not is determined by converting the minimum transmission time from the transmission rate into the number of bytes of the transmission data, and whether or not the number of transmission bytes is greater than or equal to this converted number of bytes. There is.

If the minimum transmission time is 10ms and the transmission rate is 9600Bps, the number of transmission bytes within the minimum transmission time is Becomes

And the Fill bit is inserted byte by byte.

In this device, transmission / reception data in G3 mode and data stored in the memory are always transferred via the FIFORAM 9.
If the Fill bit, which is an unnecessary signal, is recorded in the RAM 9 as image data, the RAM 9 is wasted.

Also, since the number of Fill bits changes depending on the capability of the other device when performing memory transmission, the maximum number of Fill bits calculated from the maximum possible minimum transmission time and data speed during memory storage
You will have to insert a Fill bit.

Therefore, in the present embodiment, the Fill bit is not inserted into the FIFORAM 9 at the time of G3 mode transmission and memory storage, but the Fill bit is inserted and transmitted after reading from the FIFORAM 9 at the time of transmission.

In addition, if 0 of 3 bytes or more continues when receiving, 3
The method of not writing the bytes of 0 after the byte to RAM9 is used.

(Fine to standard conversion) In this embodiment, there is a function to perform fine to standard conversion when transmitting the image data accumulated in the MH code to the FIFORAM 9. When comparing the fine and standard, the line density in the main scanning direction is equal to 8 pel / mm, the line density in the sub scanning direction is 7.7 line / mm, and the standard is 3.85 line / mm, which is 1/2 the standard for fine. It has become. The data accumulated in the FIFORAM9 is delimited by one line by EOL, so the line can be easily determined. Therefore, in this apparatus, when the data in the FIFORAM 9 is transmitted, every other line is transmitted to perform fine-to-standard (scan line density) conversion.

FIG. 8 (B) shows a processing flow chart when a data request interrupt is received from the modem 19 when the scanning line density conversion is performed and when it is not performed.

First, when an interrupt occurs, the data of the current read address pointer is called from the FIFORAM9. Data is EOL
If not, after outputting the data to the modem, the pointer is incremented by 1 and the data transfer is repeated. When the EOL is detected, the EOL in the RAM9 is sent to the E for sending as described above.
Convert to OL (CCITT recommendation), then add file bit if necessary, and output EOL and file to modem. Then, it is judged whether the fine-to-standard conversion is necessary or not, and if not, the pointer is incremented by 1 and the data reading of one line is completed. On the other hand, if the scanning line density conversion is required, the address pointer is stepped to the next EOL to delete one line of data, and then the process returns to the main routine.

(Run length to raw data conversion) When transmitting to memory in G2 mode, the data stored in FIFORAM9 with MH code must be transmitted as raw data. This device performs the data conversion by software, but it is quite difficult to directly convert MH code to raw data. Therefore, the decoding function described above is used to convert the MH code into a line length code once, and then the MH code is converted into raw data to simplify the program.

The conversion from the run length code to the raw data is performed, for example, as shown in FIG.

That is, read the RLC code, and if the RLC is black data, set it to "1".
To the line memory and repeat until RLC becomes 0. If RLC is white data, "0" is output to the line memory, and similarly RL → RAW conversion is performed by repeating until RLC becomes 0.

(B4 → A4 reduction by software) In this embodiment, reading is performed using the reading unit 1 having a 2048-bit light receiving element. Therefore, it is possible to send B4 width originals at 8 pel / mm. However (the other machine
If you have only A4 width recording capacity) B4 data (2048bi
It is necessary to convert t) to A4 data (1728bit) before sending. In the case of normal document transmission, the processing is performed by the reading unit 1.
However, if the memory transmission is considered, it is impossible to use the reduction function of the reading unit 1 from the viewpoint of the data flow. Therefore, in this embodiment, reduction is performed by software. First, the data stored in MH code in RAM9 is converted to run length code by using the decoding function, then reduced in the main scanning direction of one line, and converted to MH code (raw data in the case of G2) again. Convert and transfer to modem.

The reduction in the sub-scanning direction is performed by thinning out the data in units of one line, as described above.

A dot-to-A4 dot and number conversion with a Lang code will be described with reference to FIGS. 8 (D), (E), and (F).

The number of dots in one main scanning line of B4 is 2048 dots and that of A4 is 17 dots.
28 dots. This is factored into 32 × 2 ⁶ : 27 × 2 ⁶
The ratio is 32:27. Therefore, the data of 2048 dots of B4 is divided into 64 blocks of 32 dots each. And about 32 dots per block, 5 dots are thinned from this point to 27 dots.
All you have to do is convert it to dots. FIG. 8 (D) shows 32 dots per block. The shaded lines in this figure are 6, 13, 19,
By thinning out the 26th and 32nd dots, it is possible to thin out the dots in the main scanning direction at a substantially uniform density.

FIG. 8 (E) shows a flow chart for performing this conversion. In order to facilitate the explanation of the flow chart, for example, the data as shown in FIG.
An example of converting 32 dot codes of black 5, white 15, and black 4 into 27 dots will be described.

First, at SP1, the 1-line total RL counter TCNT, the 32-dot counter TRL, and the converted run length code SRL are set to 0.
, The thinning-out counter MC in 32 dots is set to 5, and the MA indicating the thinning-out address is set to 6.

Then at SP2, the first RL code white 8 is called from RAM9, and at TTCNT and TRL are both set to 8. TRL
= 8 is larger than MA = 6, the white 8 data RLC is converted to white 7 data RLC (SP5).

Since RLC = White 7 and SRL is 0, SP10 returns MA to 13 and MC to 4, returning to SP4 again. This time TRL = 8 is smaller than MA = 13, so proceed to SP16, SRL is set to white 7, TCNT is 204
Since it is less than 8, the next RLC = black 5 is called back to SP2, and both TCNT and TRL become 13. Since TRL is equal to MA = 13, RLC is black 4 at SP6. And at SP8 SRL = White 7 and RLC
= Since the color of black 4 is different, the data of white 7 is output to the line memory at SP9 and SRL is reset to 0. In addition, MA is set to 19 and MC is set to 3, then SP4 is returned to SP16.
Proceed to. This time, RLC = Black 4 is set in SRL. Then the next RLC = white 15 is called and TCNT and TRL are set to 28. 28 is greater than MA = 19, so RLC = white 15 is converted to white 14, and SP8 compares SRL = black 4 and white of RLC = white 14 and outputs the data of black 4 to the line memory. 0
Is reset to

And MA is set to 26 and MC is set to 2. Step SP
At 4, TRL = 28 is still larger than MA = 26, so the data of white 14 is further converted to white 13, and SRL is 0 at this time, so SP8, SP9
Set MA to 32 and MC to 1 in SP10 and 11 without judging and outputting.

Returning to SP4 again, this time MA = 32 is greater than TRL = 28, so SP13 sets white 13 to SRL. And the next R
After calling LC = black 4, white 13 is output at SP9, and similarly black 3 is output thereafter.

As described above, white 8, black 5, white 15, in the upper part of FIG.
The data of black 4 is converted into the run length codes of white 7, black 4, white 13, black 3 in the lower row almost evenly.

Note that steps S13, S14, and Sp15 indicate the initialization of MC, MA, and TRL when the processing of one block and 32 dots is completed.
15 has an adjusting function when the run length code extends over the blocks. SP18 shows the output of the last run length code of one line to the line memory.

In this way, the number of main scanning dots can be converted with the run length code as it is.

(Operation Mode) As shown in the table below, there are a great number of operation modes relating to transmission / reception and transfer of image data in this embodiment. The data flow and code form in each mode will be described below with reference to the drawings.

First, FIGS. 9 (a) to 9 (c) show flow charts of the judgment algorithm of the MPU 23 used when the present apparatus determines the above-mentioned 14 operation modes M1 to M14.

In this embodiment, the start / stop on the operation panel 50 shown in FIG.
Key 51, One Touch Dial Key 54, Speed Dial Key
53, the memory key 52 is used for activation.

Further, judgment / branching is performed based on the outputs of the sensor 31 for detecting the presence / absence of the document in FIG. 2, the sensor 32 for detecting the ON / OFF state of the hook of the telephone, and the roll paper cover sensor 33.

In addition, the message (image data) of Huaximir communication
Pre-procedure prior to communication
You can know whether it is G3 mode or G2 mode. At the same time, it is possible to know whether the partner machine has the MR coding function or only the MH coding function.

Further, it is possible to determine whether or not the FIFORAM 9 can be used at the time of message communication based on the usage state of the image memory of the own device. If the memory is stored in the RAM 9, the RAM 9 cannot be used, and if the memory is not stored, the RAM 9 can be used.

The 14 operation modes determined by this flow are added with item numbers M1 to M14.

First, when the start key is pressed, FIG. 9 (a)
As shown in, if the receiver is off-hook or on-hook, and if it is on-hook and the original is in the transmission position, the original copy mode M14 is entered, and if there is no original and the roll paper cover is closed, roll When the paper cutter operates and the cover is open, the roll paper is fed by a predetermined amount.

On the other hand, in the case of off-hook, if there is a document, the transmission mode is set, and M
Move to 1, M2, M3, M6. If the document is off-hook and there is no document, the process proceeds to the receiving mode sorting routine of FIG. 9 (b). In FIG. 9B, M7 to M11 are selected according to the partner machine mode and the availability of RAM9.

FIG. 9C shows a mode distribution routine when the memory 52 is pressed.

When the memory key 52 is pressed, a software timer is activated, and when a document is placed on the reading section 1 during this timer, the memory storage mode M12 is entered and the image data of the document is stored in the RAM 9.

If the start key 51 is pressed when the document is not placed on the reading unit 1, if the document is on-hook at this time, the image data in the RAM 9 is transferred to the memory copy mode M13 in which the recording unit 17 records the image data.

If it is off-hook at this time, the memory transmission mode is entered. When the one-touch key 54 or the speed dial key 53 is pressed, the memory transmission mode is entered regardless of the hook state. The memory transmission mode is classified into a G3 memory transmission mode M4 or a G2 memory transmission mode M5 depending on whether the partner machine is a G2 or G3 machine.

When the memory key is pressed and the document is not placed on the reading section and there is no other key operation, the display 55 (Fig. 10)
The accumulated amount of image data in RAM19 is displayed on, and it returns to the standby mode when the software timer times out.

The flow of image data according to each mode M1 to M14 will be described below.

(Mode M1) G3 Original Transmission, MH, RAM9 Available The flow of image data in mode M1 will be described with reference to FIG.

The reading unit 1 converts the image data for one line into a run length code RL and writes the run length code RL in the RAM 3 in response to a read command from the MPU 23. Then, the MPU 23 alternately transfers the data of the RAM 3 to the two line buffers RAM5 and RAM7 to 1 line alternately, encodes the run length code RL read from the two line buffers into the MH code and writes the MH code into the FIFORAM9. Then, in response to the data request interrupt from the modem 19, the MPU 23 transfers the MH code from the FIFORAM 9 byte by byte to the modem. At this time, the minimum transfer time is calculated for each line and the file bit is inserted.

Character information such as the originator and origination time added to the beginning of the image is transferred to the FIFORAM 9 using the conversion function of the raw image data 25 output from the CG 25 to the raw data → MH code.

Except for the case of the reading unit 1 → RAM 3 and the modem 19 → NCU 21 in the figure, all other data transfers are performed via the bus 24 of the MPU 23.

The interrupt interval of the data request interrupt from the modem 19 changes depending on the transfer rate. Data transfer is done in bytes, so 8/9600 at 9600 bps
= An interrupt occurs every 0.83 × 10 ^-3 sec.

Further, when the data transfer from RAM3 to RAM5, RAM7 is completed, the MPU 23 outputs a read command to the reading unit. MPU23
During the encoding process ENC and the interrupt process, the reading unit 1 reads the document and converts the raw data to the run length data.

(Mode M2) G3 original transmission, MR, RAM9 available Figure 12 (A) shows the flow of image data. The data flow is almost the same as in mode M1. The difference is ENC2
The code after 3-1 is to become the MR code. However, the data from CG25 is output from ENC23-1 in MH code. For example, if a 24 × 16 dot character is added to the beginning, 24 lines of data will be sent in MH code.

In Fig. 12 (B), CG data is MH and image data is MR and RA.
Show the program to store in M9. First, the line number L of CG data is initialized, the data of each line is called from the beginning, and from raw data to run length RL code From RL code
Convert to MH code and store in RAM9 for each line.

And when it finishes about 24 lines, this time RAM5 or 7
Read the image data of RL code from Fig. 3 (B),
According to the MR encoding routine of (C), each line is converted into an MR code and stored in the RAM 9.

(Mode M3) G3 original transmission, MH, RAM9 unusable Figure 13 shows the flow of image data. Unlike the case where the RAM 9 in FIG. 11 can be used, the RAM 7 used as the line buffer is used as the MH code buffer memory.
Therefore, the line buffer is only one RAM5, and the encoder ENC23-1 can handle only one line of data.
MR transmission cannot be performed when AM9 is not available.

The reason for this is that in order to carry out MR coding, a line buffer for two lines of the current coded line and the reference line is required.

(Mode M4) G3 memory transmission MH ... Fig. 14 (A), (B), (C) The flow of image data in the case of mode M4 is Fig. 14 (A).
Shown in Image data read in the fine mode or the standard mode is stored in the FIFORAM 9 in the form of MH code.
Also, as shown in FIG. 21, various information of the image data is
It is stored as a label at the top of the page. As information, the read size of the image data (number of main scanning dots) S
Z, fine or standard (scan line density) F / S, EOL of the page
There are several PLN etc.

Therefore, if the size of the recording paper of the partner machine is smaller than the reading size SZ, it is necessary to perform the main scanning dot number conversion described above.Although it is stored in RAM9 in the fine mode, the partner machine is the standard. In the case of having only a board, it is necessary to perform the above-mentioned scanning line density conversion.

FIG. 14 (B) shows the distribution routine. In FIG. 14B, first, the EOL counter EOC is set to 0, and the recording sheet size ASZ of the partner machine is sensed in the previous procedure. Then, as compared with the label SZ, if ASZ is greater than or equal to SZ, the mode M4-1 or M4-2 is selected. In this case, conversion of the number of main scanning dots is not required.

If ASZ is smaller than SZ, mode M4-3, M4−
4 is selected. In this case, it is necessary to convert the number of main scanning dots.

And the other machine does not have a fine recording mode, RAM9
When the fine mode is used for recording, the sub-scanning line density conversion is further required, and the mode M4-2 or M4-4 is selected.

That is, M4-1 does not require both main scanning dot number conversion and sub-scanning density conversion. M4-2 requires only sub-scan density conversion and M4-3 requires only main-scan dot number conversion. Also, M4-4 requires both conversions.

A detailed description of the data flow in each mode will be given later, but when the transmission of one line is completed, the mode M4-1,4-
In 3, the EOL counter EOC is incremented by 1, and in M4-2 and 4-4, EOC is incremented by +2. And EOC is the PE showing the EOL number of the page in RAM9.
Move to the page end subroutine that matches N.

The page end subroutine is shown in FIG.
The label GE indicating the last page of the group stored together with the series of pages is looked at, and if the page is the last page of the group, EOP indicating the end of the transmission is output to the partner device and the transmission ends.
On the other hand, if it is not the last page of the group, the next pages SZ and F / S are read out, and if F / S and SZ are the same as the previous page, the MPS signal indicating that the next page is sent in the same mode is output. If they are different, the EOM signal indicating that the pre-procedure is repeated from the beginning is sent to the other device.

The flow of image data in each of the modes 4-1 to M4-4 will be described below.

(M4-1) Main scanning dot, sub-scanning line density conversion-free image data in RAM9 is added with a fill bit by Fill23-3 and sent from NCU21 via modem 19. Also, C
Output raw data of G25 is MH coded by ENC23-1, and is directly Fi
not be forwarded to ll.

(M4-2) With sub-scanning line density conversion MPU23 converts the fine MH output of RAM9 to standard with F / S23-4, that is, deletes data every other line, RAM3, 5, Output to 7. The MH data in the RAMs 3, 5, and 7 is added with a fill bit by the Fill 23-3 and transferred to the modem 19. Also, output raw data of CG25 is ENC23-1 and R
It is output to Fill23-3 via AM3, 5, and 7.

(M4-3) With main scanning dot number conversion MPU23 extracts MH image data from RAM9, and DEC23-
Convert to run length code RL in 2 and B4 → A4 in RL state
Conversion of. Then, in ENC23-1, return to MH code again F
Output to RAM3,5,7 used as iFo memory. After that, a fill bit is added by Fill 23-3 and transferred to the modem 19. Output raw data of CG25 is also converted to MH code by ENC23-1, and then transferred to Fill23-3 via RAM3, 5, and 7.

(M4-4) With both conversions MPU23 performs F / S conversion of MH data in FIFORAM9 as MH, and after converting to DEC23-2 run length code RL, B
4 / A4 converted, converted run length code RL ENC23
The value is returned to MH code by -1 and transferred to RAM 3,5,7. Similarly, the output of CG25 is transferred to Fill via ENC23-1, RAM3, 5, and 7.

(Mode M5) G2 memory transmission --- Fig. 15 The MPU23 extracts the MH code from the FIFORAM9, decodes it to the run length code RL, converts it to raw data RAW and transfers it to the RAM5 and 7 alternately line by line. . And then RA
Raw data is extracted from M5, 7 and transferred to the modem 19. Also, when performing mode conversion from fine to standard, RA
F / S23-4 is applied between M9 and DEC23-2, and B4 / A423-5 conversion is applied between two DEC23-2 when reduction is performed.

The output data of the CG 25 is transferred to the modem 19 via the RAMs 5 and 7 in the form of raw data RAW. However, at that time, the data of CG25 is sent out at 7.7 line / mm in the sub-scanning direction without thinning out the scanning lines, thereby doubling the character size vertically as compared with the G3 mode. This is done to ensure that the source information can be read even in the G2 mode because the image quality of the G2 is greatly deteriorated due to the analog transmission of the G2.

(Mode M6) G2 original transmission --- Fig. 16 All data transfer is done in the form of raw data. The reading unit 1 writes the image data for one line as raw data into the RAM 3 in response to a read command from the MPU 23. And MPU23 is RAM3
Data is alternately transferred to the two line buffers RAM5 and RAM7 as they are, one line at a time. Then, in response to the data request interrupt from the modem, the raw data is RA byte by byte
Transfer from M5 or RAM7 to modem 19.

Character information such as a sender record added to the beginning of the image is transferred from the CG 25 to the RAMs 5 and 7 as raw data.

In the G2 mode, 1728-bit image data including a synchronization signal is written in RAM5 and RAM7. The image signal corresponding to this synchronizing signal is created by the MPU 23.

(Mode M7, M8) G3 reception MR mode, RAM9 can be used (impossible) --- Fig. 17 When MPU23 receives MR code from the line via NCU21 and modem 19, it deletes the file bit first. If there is no data in RAM9, go to RAM9. If there is data in RAM9, go to RAM3.
Transfer the MR code as it is. And MR sequentially from RAM9 or 3
The code is extracted and decoded into the line length code RL and then transferred line by line alternately to RAM5 and RAM7. At the same time, the run length code RL is transferred to the recording unit 17 and recorded. Decoded run length code
The reason why the RL is transferred to and stored in the RAM5 and RAM7 is to use it as the previous line information for MR coding.

(Mode M9, M10) G3 reception MR mode RAM9 can be used (impossible) --- Fig. 18 When the MPU23 receives the M code from the line via the NCU21 and the modem 19, the file bit is deleted first and the RAM9 If is available, it is transferred to RAM9. If it is not available, it is transferred to RAM3, 5, 7 as MH code. Then, the MH code is sequentially removed from the RAM 9 or 3, 5, 7 and converted into the line length code RL, and the recording unit 17
Transfer to and record.

(Mode M11) G2 reception --- Fig. 19 In G2 mode, uncompressed raw data is sent, so MP
When the U23 receives the raw data from the line via the NCU 21 and the modem 19, it transfers the raw data to the line buffer RAM5 and RAM7 alternately line by line. Then, the raw data is sequentially removed from the RAM5 and RAM7, transferred to the recording unit 17, and recorded.

The image signal 1728 bits for one line demodulated by the modem 19 is written in the RAM5 and RAM7. This includes the image signal obtained by demodulating the synchronization signal, so MPU2
When the data 3 is transferred to the recording unit 17, the image signal corresponding to the sync signal is excluded.

(Mode M12) Memory storage --- Fig. 20 It is almost the same as mode M1 until it is stored in FIFORAM9 with MH code, except that there is no data from CG25 and RAM9.
This is to add a label LB for file management to the top of the page from the RAM 13 when transferring to.

 Here, the label will be described.

The label consists of 24 bytes as shown in FIG.
At the 1st to 3rd bytes, there is an LPM indicating that the labeled data is the last page and an NPA indicating where the start address of the next page is. Information for each page is entered in the 4th byte. In the 4th byte MSB, when the data is divided into not only page units but also group units, information GE indicating whether or not it is the last page of the group is entered. The F / S contains data on whether the scanning line density is standard (3.85 lines / mm) or fine (7.7 lines / mm).

The MD stores information as to which form of the data in the RAM 9 is recorded in MH, MR, RL, RAW or ASCII code. Information on whether the data in the RAM 9 is read width A4, B4 or A3 is stored in SZ.

The fifth byte is the GPC, which indicates the page number within the group when the data is divided into groups. The 6th to 9th bytes are the total line number PLN of the page, the 10th to 14th bytes are the time when the memory was stored, the 10th byte is "minute", the 11th byte is "hour", 12th byte is "day", 13
The month is stored in the bait, and the year is stored in the 14th byte.
Furthermore, in the 15th to 24th bytes, the file name PE of the page
N is a code and enters each.

Then, at the time of memory transmission and memory copy, the mode is determined and the information is added based on the information in this label. Is printed, the information in the label LB is ignored during memory transmission and the transmission time is sent. When time specified transmission is performed, the time printed on the received image is not the time stored in RAM9,
This is taken into consideration so that the actual time of transmission is reached.

In addition, the image data and label LB once stored in RAM9
Is cleared by the manual operation of the operator and automatically. The flow of automatic clearing is shown in Fig. 22.

 Note that memory clear is not performed after memory copy.

(Mode M13) Memory copy --- FIG. 23 (A) The MPU 23 sequentially removes the MH code from the DRAM 9, converts it into a run length code, and transfers it to the recording unit 17 for recording. In addition, the header information is converted from a character code into raw data via the MPU, transferred to the recording unit 17, and recorded. As the time during the header, the time at which the memory storage in the file management label LB recorded in the RAM 9 is performed is converted into an image by the CG 25 and recorded in the recording unit 17.

FIG. 23 (B) shows a time management subroutine. First, in the transmission mode, the clock 27 managed by the MPU 23 (first
Output the date and time data shown in the figure) to the CG25 and send the sending time together with the image. At the same time, the time is recorded in the communication management RAM 13 together with the destination TELNO. Also, the date and time data TD in the label is output to the CG25 when copying the memory.
When the memory is stored, the date and time data of the clock is output to the RAM 9 as data TD. Also, at the time of reception, the data of the clock 27 is stored in the RAM 13 together with the other party's TELNO.
In the case of the manuscript copy mode, the time data has no influence.

(Mode M14) Original copy --- Fig. 24 The reading unit 1 writes the data for one line which receives the read command from the MPU 23 to the RAM 3 in the form of raw data RAW. And MPU
The RAM 23 sequentially extracts the raw data from the RAM 3 and transfers the raw data to the recording unit 17 for recording. The output data of CG25 is recorded in the form of raw data.
Transferred to 17 and recorded.

<Effect> As described above, according to the present invention, when the stored image signal is transmitted, the data of the transmission time is transmitted to the destination, so that the destination knows when the image was transmitted. be able to. Further, according to the present invention, the stored image signal is visibly reproduced, and the data of the storage time is visibly reproduced. Therefore, what kind of image is stored and when it is stored The user can easily recognize and manage the stored image signal.

[Brief description of drawings]

FIG. 1 is a sectional view of the facsimile machine of this embodiment, FIG. 2 (A) is a basic control block diagram of the facsimile machine of this embodiment, and FIG. 2 (B) is the basic of the MPU 23 of FIG. 2 (A). Figure showing function, Figure 3 (A) is MH in ROM 11 of Figure 2 (A)
FIG. 3 is a diagram showing the structure of code data, FIG. 3 (B) and (C) are flow charts for converting run length code to MR code, and FIGS. 4 and 5 are diagrams showing the structure of EOL in RAM9.
Fig. 6 is a flow chart for converting MH code to run length code. Fig. 7 is a diagram showing a search example when converting MH code to run length code. Fig. 8 (A) is MR
FIG. 8 (B) is a diagram showing a search example when a code is converted into a run length code, FIG. 8 (B) is a diagram showing a processing flow chart of the MPU 23 when a data request interrupt is received from the modem 19, and FIG. 8 (C) is Conversion chart from run-length code to raw data, Fig. 8 (D), (E),
(F) is an explanatory diagram of the conversion of the dot number from B4 to A4, and FIGS. 9 (a), (b), and (c) are flow charts for determining the 14 operation modes of the MPU 23, and FIG. FIG. 11 is a plan view of the operation unit 50, FIG. 11 is a diagram showing a flow of image data in the mode M1, FIG. 12 (A) is a diagram showing a flow of image data in the mode M2, and FIG. 12 (B) is a CG. Data is MH code, image data is
Flow chart diagram for storing in RAM9 with MR code, Fig. 13 is a diagram showing the flow of image data in mode M3, Fig. 14 (A)
Shows the flow of image data in mode M4, Fig. 14 (B)
Mode M4 to M4-4 to M4-4
FIG. 14 (C) is a diagram showing a page end subroutine, FIG. 15 is a diagram showing the flow of image data in mode M5, and FIG. 16 is a diagram showing the flow of image data in mode M6. FIG. 17 is a diagram showing the flow of image data in modes M7 and M8, FIG. 18 is a diagram showing the flow of image data in modes M9 and M10, and FIG. 19 is a diagram showing the flow of image data in mode M11. Figure 20 shows the flow of image data in mode M12,
FIG. 21 is a diagram showing the structure of a file management label attached to the top of a page when image data is stored in the RAM 9, FIG.
The figure shows a flow chart for automatically clearing the image data in RAM9. Figure 23 (A) shows the flow of image data in mode M13. Figure 23 (B) shows the time management subroutine. Figure 24. FIG. 13 is a diagram showing a flow of image data in mode M14. In the figure, 1 is a reading unit, 3, 5 and 7 are RAMs, 9 is a FIFORAM used as an image memory, 23 is an MPU, and 25 is a CG.

 ─────────────────────────────────────────────────── ─── Continued front page (72) Inventor Motoaki Yoshino 3-30-2 Shimomaruko, Ota-ku, Tokyo Canon Inc. (72) Inventor Yasuhide Ueno 3-30-2 Shimomaruko, Ota-ku, Tokyo Kya Non-Incorporated (72) Inventor Nobuhiro Watanabe 3-30-2 Shimomaruko, Ota-ku, Tokyo Canon Inc. (72) Inventor Yosei Oto 3-30-2 Shimomaruko, Ota-ku, Tokyo Canon Inc. (72) Inventor Ken Ono 3-30-2 Shimomaruko, Ota-ku, Tokyo Canon Inc. (72) Inventor Shigeo Miura 3-30-2 Shimomaruko, Ota-ku, Tokyo Canon Inc. (56) References JP-A-57-192167 (JP, A) JP-A-59-40757 (JP, A)

Claims (1)

[Claims] 1. A reading unit for reading an image, a first storage unit for storing the image signal read by the reading unit, and a storage time data for storing the image signal in the first storage unit. 2 storage means, a transmission means for transmitting the image signal stored in the first storage means, a reproduction means for visually reproducing the image signal or time data, and the storage means stored in the first storage means. When transmitting the image signal, the data of the transmission time is transmitted to the destination, and the first
The image transmitting device, wherein the reproducing means reproduces the image signal stored in the storing means, and the reproducing means reproduces the storage time data of the second storing means.