JPH0787507B2 - Image transmitter - Google Patents

Description

Description: TECHNICAL FIELD The present invention relates to an image transmitting apparatus for transmitting an image signal, and more particularly to an image transmitting apparatus including a storage unit for storing an image signal.

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

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, when the recording scan line densities of a plurality of communication destinations are different, the recorded image may be elongated or contracted in spite of sending the same image data.

<Objective> In view of the above problems, the present invention transmits the scanning line densities of the image signals for a plurality of pages stored in the storage unit even if the scanning line densities of the respective pages are different. It is an object of the present invention to provide an image transmitting device that can perform high-speed conversion according to the above.

In order to achieve this object, the present invention provides a reading unit that can read line by line at a plurality of scanning line densities, an encoding unit that encodes an image signal read by the reading unit for each line, and First storage means for storing a plurality of pages of image signals encoded line by line by the encoding means together with delimiter data indicating delimiters between lines, and images for a plurality of pages stored in the first storage means The second storage means for storing the data indicating the scanning line density of each page of the signal, the receiving means for receiving the signal designating the scanning line density from the destination of the image signal, by the pre-procedure prior to the image transmission When it is determined that the scanning line density indicated by the data stored in the second storage means is higher than the scanning line density designated by the signal received by the receiving means, the scanning line density designated by the destination is specified. Image signal transmission means for thinning and transmitting the image signal stored in the first storage means according to the delimiter data so as to match the scanning line density, and the image signal for one page by the image signal transmission means. After the transmission is completed, it is determined whether the scanning line density of the next page is the same as the scanning line density of the transmitted page. The scanning line density of the transmitted page and the scanning line of the next page stored in the second storage means. When the discriminating means for discriminating on the basis of the data indicating the density and the scanning line density of the next page are discriminated to be the same as the scanning line density of the transmitted page by the discriminating means, the next page is scanned with the same scanning line density. A procedure signal transmitting means for transmitting a procedure signal indicating that the procedure is to be transmitted and transmitting a procedure signal indicating that the pre-procedure is performed again when it is determined that they are not the same.

<Embodiment> An embodiment of a 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 image forming lens, 43 is a mirror, 44 is an original illumination lamp, 45 is an original feeding roller, 46 is an original discharging roller, 47 is an original 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 discharge roller, 39 is a roll paper conveying roller, 40 is a recording head, and 33 is a recording head. A roll paper cover sensor that detects 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. The original is illuminated by the lamp 44 at the reading position P, and the reflected light is reflected by the mirror 43 and the lens 42.
An image is formed on the image sensor 41 via the, and the image sensor 41 converts the image into an electric signal.

On the other hand, at the time of recording, the roll paper 35 is nipped by the roller 39 and the head 40 and conveyed, and at the same time, the head 40 is put on the heat-sensitive roll paper 35.
An image is formed by. 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 Fast-in-fast-out RAM (hereinafter FIFORAM) that functions as an image memory that stores image signals for several pages, 11 MP
Read-only memory (hereinafter ROM) that stores the operation program of U23, 13 is a RAM that stores the flags and data necessary for MPU operation, 15 is an operation unit that has input keys and a display, 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 network control unit (NCU), 25 is a character generator that stores character fonts for transmitting the transmission time, the name of the transmission source as image data, and recording communication management data in addition to the original image. Container (hereinafter CG), 23 is an MPU that controls the entire system
Is. In this embodiment, as the MPU 23, a 16-bit data bus 24
And, Intel 8086 that can directly access the memory space of up to 4 megabytes is used.

Since the Merit using this MPU has a 16-bit data bus, it is easy to handle encoded image data. For example, run length code 2048
12bit data is required to handle bit data, 8b
If you use it's MPU, you have to access it twice, but if it is 16 bits, you only need to access it once.

Also, since a large capacity memory space can be directly accessed, it has become possible to use the system memory as an image memory to provide a broadcasting function. In the conventional device, an external memory unit was used, or a memory that could not be accessed directly by the MPU via the bus was used even within the device, but the broadcast function was provided as an image memory. There was a problem such as an increase in size.

(Function of MPU) There are six 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 length code and writes the run length code into the RAM3, and the MPU23 reads the run length code from the RAM3 and uses it to read the code conversion table in the ROM11. To convert to MH code. Conversion table is ROM1
MH code data corresponding to the run indicated by the address is written with the run length 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 lower 4b
The code length information of the MH code is put in it to recognize the code length. Although the MH code is assigned to the upper 12 bits, there is a maximum 13-bit code in the MH code table. 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 16
Since it fits in a bit, processing with a 16-bit MPU (micro processing unit) becomes easy, and high-speed MH
You can find the 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. “Pixel white /
There is "black inversion detection." Therefore, the reading unit writes run-length data to RAM3 so that the detection can be performed easily.
It is coded.

The program flow for converting to the MR code by the run length code is shown in Fig. 3 (B), and the parameter b1
FIG. 3 (C) shows the decision subroutine of.

In FIG. 3 (B), parameters a0 and b1 are first initialized to 0, and the run length code next to the target line is read to determine a1, and b1 is determined by the routine in FIG. 3 (C). After that, b2 is determined by calling the RL code next to the reference line. Then, the MR encoding routine recommended by T4
At the same time that the sign is decided, the next value of the parameter a0 is decided.

In FIG. 3 (c), the parameter b1 is determined according to the definition of the recommendation that a0 is the change point of the first color different from a0 in the target line on the right side of a0.

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 charactor 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. Run conversion table output
The run data is not the length code but the raw data.
If you create a table with a length, the number of codes will increase, and a large CG table will be required. This is to reduce the capacity of the CG25 by making it raw data. Also, by using raw data, G2 mode etc. There is also a merit that decoding is not required in the case of transmission in the non-compressed mode.

d) Handling of EOL In G3 mode transmission / reception, image data uses a line synchronization form, and as a line synchronization signal therefor, EOL (EOL (E
nd 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 99, 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
U23 is performed when reading the code from RAM9 and transmitting 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 out data from RAM9, 0 of 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, the storage form of the data and EOL in the RAM 9 when there is no "1" in the last data of the line in the last byte is
Shown in the figure. Data contained in the last byte A as shown in the figure
When DT is all 0s, all 0s are inserted in the rest of byte A, and 0s are 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 0s are 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 FIFORAM9 and perform 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, the MH code is searched bit by bit and 0
If so, the data at the address indicated by the current address pointer is checked, and if "1", the data at the next address is checked. If the MBS is "1", the data is run length, and if the MBS is "0", the data is written to the address pointer and used for the next search. That is, 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. And at the destination,
The processing corresponding to the MR code is performed and the run length code is generated.

Since MR encoding is a two-dimensional compression encoding method, 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. Fill if it is less than the minimum transmission time
Bit (data 0) is inserted and EOL is added after the minimum transmission time or more.

This device judges whether the transmitted data is more than the minimum transmission time, by converting it from the minimum transmission time and the transmission rate to the number of bytes of the transmission data, and it is judged whether the number of transmission bytes is more than 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. RA
If the M9 stores the Fill bit, which is an unnecessary signal as image data, the RAM 9 is wasted.

Also, since the number of Fill bits changes depending on the capacity of the other device when transmitting to the memory, the maximum number of Fis calculated from the maximum and minimum transmission time and data speed that can be considered during memory storage.
You'll have to insert ll bits.

Therefore, in this embodiment, at the time of G3 mode transmission and memory accumulation, the Fill bit is not inserted into the FIFORAM9 at all, and at the time of transmission.
After reading from the FIFORAM9, the Fill bit is inserted and transmitted.

In addition, at the time of reception, when 3 or more bytes of 0s continue, the method of not writing the 0th byte after the 3rd byte to the RAM 9 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 stored in FIFORAM9 is E
Lines can be easily judged because one line is separated by OL. 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. If the data is not EOL, the data is output to the modem, the pointer is set to +1 and the data transfer is repeated. When the EOL is detected, the EOL in RAM9 is sent to the EOL for transmission as described above.
(CCITT recommendation), then add a bit bit, add a file if necessary, and output EOL and file to the modem. Then, it is determined whether fine-to-standard conversion is necessary, and if not, the pointer is incremented by 1 and the data reading for 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 → Raw data conversion) When transmitting memory in G2 mode, the data stored in FI code in FIFORAM9 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, by using the decoding function described above, the MH code is once converted into a run length code,
Furthermore, the program is simplified by the method of converting it into raw data.

For example, the conversion from run length code to raw data is No. 8
It is performed as shown in FIG.

That is, the RLC code is read, and if RLC is black data, "1" is output to the line memory and the process is repeated until RLC becomes 0. R
If LC is white data, output “0” to line memory and
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. But (the other machine is A4
B4 data (2048bi if only recording width is available)
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.

The conversion from B4 to A4 in the run length code and the conversion of numbers 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 1728
That's right. Factoring this, 32 × 2 ⁶ : 27 × 2 ⁶ 3
The ratio is 2:27. Therefore, the data of 2048 dots of B4 is 32
Divide each into 64 blocks. And 1 block
For 32 dots, 5 dots will be thinned out to 27 dots. FIG. 8 (D) shows 32 dots per block. 6,13,19,26,3 hatched in this figure
By thinning out the second 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. To facilitate the explanation of the flow chart, for example,
Data as shown in Fig. (F), that is, run length code: white 8, black
An example of converting 32 dot codes of 5, white 15 and black 4 into 27 dots will be described.

First, in SP1, set the 1-line total RL counter TCNT, the 32-dot counter TRL, and the converted run-length code SRL to 0, set the decimation number counter MC in 5 to 32, and the MA indicating the decimation address to 6. Set.

And call the first RL code white 8 from RAM9 in SP2,
Then, in SP3, both TCNT and TRL are set to 8. TRL = 8
Is larger than MA = 6, the data RLC of white 8 is converted to the data RLC of white 7 (SP5).

Since RLC = White 7 and SRL is 0, MA becomes 13 at SP10, MC becomes 4 at SP10, and returns to SP4 again. This time TRL = 8 is smaller than MA = 13, so proceed to SP16, SPL is set to white 7, TCNT
Is smaller than 2048, the process returns to SP2, the next RLC = black 5 is called, 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
Since the color of RLC = black 4 is different, the data of white 7 is output to the line memory at SP9 and SRL is reset to 0.
Furthermore, MA is set to 19 and MC is set to 3. Then, it returns to SP4 and SP1.
Go to 6. 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 larger than MA = 19, so RLC = white 15 is white 14
Is converted to SRL = black 4 and RLC = white 14 is compared in SP8, the data of black 4 is output to the line memory, and SRL is 0.
To be reset.

And MA is set to 26 and MC is set to 2. Step SP4
Since TRL = 28 is still larger than MA = 26, 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 RLC
= After calling black 4, white 13 is output at SP9, and then black 3 is output in the same manner.

As described above, the data of white 8, black 5, white 15, and black 4 in the upper part of FIG. 8 (F) is converted into the run length codes of white 7, black 4, white 13, and black 3 in the lower part almost evenly. Is done.

Note that steps SP13, SP14, and SP15 indicate the initialization of MC, MA, and TRL when the processing of one block and 32 dots is completed.
The 15 also has an adjustment function when the run length code spans between blocks. SP18 shows the output of the last run length code of one line to the line memory.

In this way, main scan 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 key 51, the one touch dial key 54, and the speed dial key 5 on the operation panel 50 shown in FIG. 10 are used.
3. Start up with the memory key 52.

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 communication of the pre-procedure signal prior to the message (image data) communication of the fax communication allows the other device's mode to be G3.
You can know if the mode is 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, as shown in FIG. 9 (a), the receiver checks whether it is off-hook or on-hook. If it is on-hook, the original copy mode M14 is entered if the original is at the transmission position. If there is no original and the roll paper cover is closed, the roll paper cutter operates, and if 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 M1, M
Move to 2, 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 allocation routine when the memory key 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.

If 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) is displayed.
Displays the amount of image data stored in RAM9 and 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 transfers the data in the RAM 3 to the two line buffers RAM 5 and RAM 7 as they are, alternately by one line, and encodes the run length code RL read from the two line buffers into the MH code and writes it into the FIFORAM 9. 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 transmission rate. Since data transfer is done in byte units, 8/9600 = 9600bps
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. While the MPU 23 is performing 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 ENC23
The code after -1 is 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.

Figure 12 (B) shows CG data in MH and image data in MR in RAM9.
Show the program to store in. 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.

When 24 lines are completed, the image data of the RL code is read from RAM 5 or 7 this time, and shown in FIGS. 3 (B) and (C).
According to the MR encoding routine of, each line is converted into an MR code and stored in RAM9.

(Mode M3) G3 original transmission, MH, RAM9 unusable Figure 13 shows the flow of image data. Unlike the case where RAM9 in Fig. 11 can be used, it was used as a line buffer.
It is used as a buffer memory for RAM7 and MH code. Therefore, the line buffer is only one RAM5, and the encoder ENC23-1 can handle only one line of data.
If 9 is unavailable, MR transmission cannot be performed.

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 ... (A), (B), (C) of FIG. 14 The flow of image data in the case of mode M4 is shown in FIG. 14 (A). Image data read in the fine mode or the standard mode is stored in the FIFORAM 9 in the form of MH code. Further, various information of the image data is stored as a label at the head of the page as shown in FIG. As information, the read size of the image data (the number of main scanning dots) SZ,
Fine or standard (scan line density) F / S, number of EOLs on that page
There are 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. When only the mode is provided, it is necessary to perform the above-mentioned scanning line density conversion.

FIG. 14 (B) shows the distribution letin. 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.

When the partner machine does not have the fine recording mode and the fine recording mode is stored in the RAM 9, further conversion of the sub-scanning line density is 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-3
In EOL counter EOC + 1, M4-2, 4-4 EOC +
I will do 2. And EOC is PLN which shows the number of EOL of the page in RAM9.
To the page end subroutine which coincides with.

The page end sub-routine is shown in FIG. 14 (C), and the label GE shown in the last page of the group stored in RAM 9 together with the series of pages is checked. The EOP indicating the end of the transmission is output and the transmission ends. On the other hand, if it is not the last page of the group, the next page 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 also sent in the same mode is output. If there is a difference, the EOM signal indicating that the previous procedure is to be started again is sent to the other device.

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

(M4-1) Main scanning dots, sub-scanning line density conversion-free image data in RAM9 is added with fill bits by Fill23-3 and sent from NCU21 via model 19. Also, CG2
5 output raw data is MH coded by ENC23-1, and direct fill
Not transferred to.

(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 RAM
It is output to Fill23-3 via 3,5,7.

(M4-3) With main scanning dot number conversion MPU23 extracts MH image data from RAM9, and DEC23-2
Convert to run length code RL with and convert B4 to A4 in the state of RL. Then at ENC23-1, return to MH code again and FiF
o Output to RAM3,5,7 used as memory. Then F
A file bit is added in ill23-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.
After converting to DEC23-2 run length code RL, B4 / A4
Convert and convert the converted run length code RL to ENC23-1
Return to MH code with and transfer to RAM3,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 into the run length code RL, converts it to raw data RAW, and transfers it to the RAM5, 7 alternately line by line. And sequentially RAM
The raw data is extracted from 5, 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 CG25 is transferred to the modem 19 via RAW5,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 skipping 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 is transferred 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. Then, the MPU23 uses the data of RAM3 as it is for two line buffer RAM5, RAM7-1.
Transfer lines line by line. Then, in response to the data request interrupt from the model, the raw data is transferred byte by byte from the RAM 5 or RAM 7 to the model 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 the MPU23 receives the MR code from the line via NCU21 and modem 19, first the file bit is deleted and the data is stored in RAM9. If there is no, go to RAM9, if there is data in RAM9, go to RAM3 MR
Transfer the code as it is. Then, the MR code is sequentially extracted from the RAM 9 or 3 and decoded to the run length code RL, and then transferred line by line to the RAM 5 and the RAM 7 alternately. At the same time, the run length code RL is transferred to the recording unit 17 and recorded. RA of decoded run length code RL
The reason why the data is transferred to M5 and RAM7 and stored is that it is used as previous line information when MR coding is performed.

(Modes M9, M10) G3 reception MH mode RAM can be used (impossible) ... Fig. 18 When the MPU23 receives the MH code from the line via the NCU21 and model 19, first the file bit is deleted and RAM9 can be used. If so, transfer to RAM9, if not possible, transfer to MH3,5,7 as MH code. Then, the MH code is sequentially removed from the RAM 9 or 3, 5, and 7, converted into a run length code RL, transferred to the recording unit 17, and recorded.

(Mode M11) G2 reception ... Fig. 19 Since uncompressed raw data is sent in G2 mode, MPU2
When the raw data 3 receives the raw data from the line through the NCU 21 and the modem 19, the raw data is transferred to the line buffer RAMs 5 and 7 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 the MPU23
When transmitting to the recording unit 17, the image signal corresponding to the sync signal is excluded.

(Mode M12) Memory storage ・ ・ ・ Fig. 20 FIFORAM9 is almost the same as mode M1 until it is stored in MH code, except that there is no data from CG25, and RAM9
This is to add the label LB for fine management to the beginning 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. 21. 1
At the 3rd byte, 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 data from the standard (3.85 lines / mm) or fine (7.7 lines / mm) scanning line density is stored in the F / S.

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

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 contain the total line number PLN of the page, the 10th to 14th bytes contain the time when the memory was stored, and the 10th byte contains "minutes".
The 11th byte stores "hour", the 12th byte stores "day", the 13th byte stores "month", and the 14th byte stores "year". Further 15th
At the 24th byte, the file name PFN of the page is entered as a code.

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 to 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 stored 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 (Fig. 1)
The date and time data of is output to CG25, and the transmission time is transmitted together with the image. At the same time, the T
Memorize the time with ELNO. 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 above clock is stored in RAM9 as data TD
Output as. 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 MPU23
Sequentially extracts the raw data from the RAM 3, transfers it to the recording unit 17, and records it. The CG25 output data is recorded in the form of raw data in the recording unit 17
Will be transferred to and recorded.

In this way, the RAM 9 stores the compression-encoded image signal, and the MPU 23 converts the scanning line density with the encoded image signal as it is. Therefore, the processing associated with the density conversion and the transmission processing can be speeded up. Therefore, the time required for transmission can be shortened, and the time required for transmission can be shortened.

<Effect> As described above, according to the present invention, the operation for transmission is simplified by storing the image signals for a plurality of pages in the storage means, and even if the scanning line densities are different from each other. However, the scanning line densities of the image signals for a plurality of pages stored in the storage unit can be converted at high speed according to the destination.

[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 in the case of converting a code into a run length code, FIG. 8 (B) is a diagram showing a processing flow chart of the MPU 23 when receiving a data request interrupt from the modem 19, and FIG. 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 for storing in RAM9 by MR code, FIG. 13 shows a flow of image data in mode M3, FIG. 14 (A) shows a flow of image data in mode M4, FIG. 14 (B) Is a flow chart for mode M4 and further distributes modes M4-1 to M4-4 according to the partner's machine. FIG. 14 (C) shows a page end subroutine. FIG. 15 shows the flow of image data in mode M5. 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, and FIG. 18 is a diagram showing the flow of image data in modes M9 and M10. FIG. 19 is a diagram showing the flow of image data in mode M11, FIG. 20 is a diagram showing 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.
Fig. 23 is a flow chart for automatically clearing the image data in RAM9. Fig. 23 (A) is a diagram showing the flow of image data in mode M13. Fig. 23 (B) is a diagram showing a time management subroutine. Fig. 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, 7 are RAMs, 9 is a FIFORAM used as an image memory, 23 is an MPU, and 25 is a CG.

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Masakyo Takahashi 3-30-2 Shimomaruko, Ota-ku, Tokyo Canon Inc. (72) Inventor Motoaki Yoshino 3-30-2 Shimomaruko, Ota-ku, Tokyo Canon Inc. (72) Inventor Yasuhide Ueno 3-30-2 Shimomaruko, Ota-ku, Tokyo Canon Inc. (72) Inventor Nobuhiro Watanabe 3-30-2 Shimomaruko, Ota-ku, Tokyo Canon Inc. Company (72) Inventor Yosei Oto 3-30-2 Shimomaruko, Ota-ku, Tokyo Canon Inc. (72) Inventor Ken 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) Reference JP-A-58-138162 (JP, A) JP-A-59-223057 (JP, A) JP 59-188272 (JP, A) JP 57-97271 (JP, A)

Claims (1)

[Claims] 1. A reading unit capable of reading each line with a plurality of scanning line densities, an encoding unit for encoding the image signal read by the reading unit for each line, and each line for the encoding unit. A first storage unit for storing a plurality of pages of the image signal encoded together with the delimiter re-data indicating the delimiters between the lines, and the respective pages of the image signals for the plurality of pages stored in the first storage unit. Second storage means for storing data indicating a scanning line density, receiving means for receiving a signal designating a scanning line density from a destination of the image signal, and the second storage by a pre-procedure prior to image transmission. When it is determined that the scanning line density indicated by the data stored in the means is higher than the scanning line density specified by the signal received by the receiving means, the scanning line density specified by the destination is met. An image signal transmitting unit that thins out and transmits the image signal stored in the first storage unit according to the delimiter data, and the next page after the image signal transmitting unit finishes transmitting one page of the image signal. Whether the scanning line density of the same is the same as the scanning line density of the transmitted page based on the data indicating the scanning line density of the transmitted page and the scanning line density of the next page stored in the second storage means. And a procedure for transmitting the next page at the same scanning line density when the scanning line density of the next page is determined to be the same as the scanning line density of the transmitted page by the determining means. An image transmitting apparatus comprising: a procedure signal transmitting means for transmitting a signal and, if it is determined that they are not the same, transmitting a procedure signal indicating that the pre-procedure is performed again.