JPS61176249A - Picture transmitter - Google Patents

Abstract

PURPOSE:To enable a user to decide the erasion of the data stored in a picture CONSTITUTION:In a transmission mode the date/time data on a timepiece 27 controlled by an MPU.

Description

DETAILED DESCRIPTION OF THE INVENTION Technical Field The present invention relates to an image transmitting device that transmits image signals, and more particularly to an image transmitting device equipped with a storage means for storing image signals.

<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 transmitting the same image data to various recipients, or when the recipient cannot be connected during transmission, because it allows the document image to be stored in the device.

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

<Objective> In view of the above-mentioned problems, the present invention aims to provide an image transmitting device capable of identifying the date and time when an image in a storage means is stored.

<Embodiment> Hereinafter, an embodiment of a facsimile apparatus that implements the present invention will be described in detail. □ (Mechanism) Figure 1 shows a cross-sectional view of the facsimile machine.

In the figure, 41 is a COD solid-state line image sensor;
2 is an imaging lens, 43 is a mirror, 44 is a document illumination lamp, 45 is a document feed roller, 46 is a document discharge roller, 4
7 is a document feed tray, and 31 is a document detection sensor for detecting the presence or absence of a document on the document feed tray.

Further, 34 is a roll paper storage cover, 35 is a roll paper, and 36 is a roll paper storage cover.
37 is a paper output tray for originals and recording paper, 38 is a cutter, and 38 is a paper output tray for originals and recording paper.
39 is a roll paper discharge roller, 39 is a roll paper transport roller,
40 is a recording head, and 33 is a roll paper cover sensor that detects the opening and closing of the cover 34 once.

In the figure, when reading a document, the document on the document feed tray 47-t is conveyed by rollers 45 and 46.

The document is illuminated by a lamp 44 at the reading position P, and the reflected light is imaged on the image sensor 41 via the mirror 43 and lens 42, and the image sensor 41 converts the image into an electrical signal.

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

(Basic Block) FIG. 2A is a basic control block diagram of the facsimile apparatus of this embodiment. In the figure, 1 is a reading unit that reads an original image and converts it into an electrical image signal; 3, 5.7. One aspect of this is a random access memory (hereinafter referred to as RAM) that functions as a buffer for temporarily storing the image signal;
9 is a first-in-first 7'RAM' (hereinafter referred to as FIFORAM) which functions as an image memory for storing several pages of image signals; 11 is a read-only memory (hereinafter referred to as ROM) that stores the operation program of the MPU 23; 13
is R that stores flags, data, etc. necessary for MPU operation.
AM, 15 is an operation unit having an input key 1 display, etc., 17
19 is a modem that modulates the transmitted data and demodulates the received data; 20 is a telephone; 21 is a communication line 22;
A network control unit (hereinafter referred to as NCU) 25 connects to the modem 19 or telephone 20 and controls the transmission time,
A character generator (hereinafter referred to as CG) 23 which stores character fonts for transmitting the name of the sender as image data and for recording communication management data is an MPU that controls the entire system. In this embodiment, the MPU 23 uses an Intel 8086 that can directly access a 16-bit data bus 24 and a memory space of up to 4 megabytes.

The advantage of using this MPU is that the 16-bit
data bus, it became easy to handle encoded image data. For example, to handle 2048 bits of data with a run length code, 12 bits are required.
data is required, and if an 8-bit MPU is used, access must be performed twice, but 16' bit data is required.
If it is t, one access is sufficient.

Furthermore, since a large capacity memory space can be directly accessed, it has become possible to use the system memory as an image memory and provide a reporting function. Conventional devices use an external memory unit or a memory that cannot be directly accessed by the MPU via the bus even if it is inside the device to provide a relay function as image memory, but this increases the complexity of the circuit and the device. There were problems such as increasing the size.

” (Function of MPU) The basic functions of MPU 23 include 6 as shown in Figure 2 (B).
There are seeds. Each function will be explained below.

Encoding function (run length → MH, MR code conversion, etc.)a
) When performing run length → MH coat conversion encoding, first, a one line read command is issued to the reading unit 1. Then, the reading unit 1 converts the read one line of image data into a run length code and writes it into the RAM 3, and the MPU 23 reads the run length code from the RAM 3 and uses it to convert the code in the ROMI l. Look up the table and convert it to MH code. The conversion table is developed on ROMI1, and MH code data corresponding to the run indicated by the address is written using the run φ length code as an address. The structure of the MH code data is shown in FIG.

In Figure 3 (A), MH is placed left-justified in the upper 12 bits.
Enter the code. Furthermore, since the MH code is a variable length code, the code length information of the MH code is entered in the lower 4 bits 4 to recognize the code length. Top 12biti
Although this MH code is assigned, the MH code table contains codes of up to 13 bits. To deal with this, if we focus on codes with a code length of 13 bits, we can see that the beginning (MSB) of all codes starts at 0°. Therefore, the data in the conversion table has 12 bits excluding the leading ``0'' as the MH code, and information of the data length "13" is added. Then, when the conversion table is checked and the data tone is '13', the MPU adds 0° to the beginning of the code.

In this way, all MH codes and their code lengths fit within 16 bits, so 16bit (7)
Processing by the MPU (micro processing unit) becomes easier, and MH codes can be searched at high speed.

b) Run length → MR code conversion Conversion to MR code is performed by the MPU 23 with reference to the basic flow shown in CCITT's T4 recommendation, but the basic flow also has a high frequency and is an important item. One example is "detection of white/black inversion of a pixel." Therefore, in order to easily detect this, the data written into the RAM 3 by the reading section is converted into a run-length code.

A program flow for converting a run-length code into an MR code is shown in FIG. 3(B), and a subroutine for determining the parameter b1 is shown in FIG. 3(C).

In Fig. 3 (B), first set the parameter a O + b1 to 0.
By reading the code during the next run length of the target line, al is determined, and bl is determined as shown in Fig. 3 (C).
After determining b2 in the routine of
The decision is made by calling the code. MR of T4 recommendation
At the same time as the MR code is determined in the encoding routine, the next value of the parameter aO is determined.

In FIG. 3(C), in the target line where parameter b1 is on the right side of aO, aO is the color (white).

It is determined according to the definition of the Recommendation that the first color change point is different (black).

Since the conversion to the MR code is performed from the run-length code in this way, it is extremely faster and easier to perform than conversion from raw image data.

C) CG code → MH code conversion This device has the function of converting information such as characters in addition to the image data read by the reading unit into MH code and transmitting it as image data. , first CG
With the code, extract the raw data corresponding to the CG code from CG25, convert it to a run length code,
Furthermore, it is converted into an MH code and transmitted. The reason why the conversion table output is raw data instead of run length code is because if you create a table using run length, the number of codes will increase and a large CG table will be required. The purpose of this is to reduce the amount of decoding, and by using raw data, there is also the advantage that decoding is not required when transmitting in uncompressed mode such as G2 mode.

d) Handling of EOL When transmitting and receiving image data in G3 mode, line synchronization is used for image data, and EOL is used as a line synchronization signal for this purpose.
OL (End OF Line) is set. The EOL consists of 11 consecutive "0" plus l (in the case of MR, an additional 1 or 0 is added).

Each time the MPU 23 detects the end of a line, it adds this EOL to the image data and sends it out. When adding this EOL, it calculates the transmission time of the transmission line and determines if it is less than the minimum transmission time. In such cases, EOL is added after inserting fill pits to achieve the minimum transmission time. In actual transmission, the MH code is temporarily FIFORA
The code is stored in M9, and the MPU reads the code from RAM9 and transmits it. The calculation of the minimum transmission time and the insertion of fill bits are performed when the MPU 23 reads the code from the RAM 9 and transmits it. Therefore, detection of the line end signal EOL when reading from the RAM 9 becomes an important issue. Therefore, in this device, the EOL when reading from RAM9 is
The following method is used to simplify detection and EOL transmission.

First, the basic philosophy of handling EOL is (1) E OL is added when writing to RAM9.

(2) EOL detection when reading from RAM 9 is 2
Perform bytes continuously.

(3) When sending data from RAM 9, the second byte of 0 out of 2 consecutive 0 bytes is not sent.

There are three points. I will explain the following two cases separately.

FIG. 4 shows the storage format of data and EOL in RAMQ when "°1" in the final data of a line exists in the final byte. In the figure, the final byte A's DT is image data. Fill byte A with 0 after data DT,
(Pi) B and C are all 0, and LX is inserted at the D-th byte. However, depending on the number of 0's inserted into byte A, the number of 0's before IX of the D-th byte is changed as shown in the table below.

In this way, 11 O's can be secured even if 1 byte of 0's at EOL in the memory is removed and extracted.

Next, FIG. 5 shows the storage format of data and EOL in RAMQ when "1" at the end of the line does not exist in the final byte. As shown in the figure, when the data DT included in the final byte A is all 0, all 0s are inserted into the remainder of byte A, and 0 is also inserted into the next byte B. Then, in byte C, after inserting 0's equal to 1 minus the number n of 0's inserted into the byte, lx is inserted.

does not exist, so the number of 0s inserted in the A-th byte does not take into account 4 or less.

Furthermore, in consideration of white line skip transmission, as a margin judgment criterion, if one line is all white data, O in the second byte is distinguished as O1' (hex display).

By writing to PI FORRAM9 in the above format, EOL detection when reading from RAMQ is 2
This can be easily done with a continuous byte of O or one byte of O and 01" (hex). Furthermore, when sending the read data, it can be easily done by deleting the second byte of 0 (or 01"). It is also possible to send and send EOL.

Although it is possible to send EOL without deleting O in the second byte, 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
The code → run length code conversion encoding method is F
I took out the MH code from FORRAM9,
The decoder is performed using an MH to run length conversion table, but the method of drawing the table is somewhat different from the run length to MH code conversion method described above.

FIG. 6 shows a conversion flow from an MH code to a run-length code, and FIG. 7 shows a table. As is clear from the flowchart in FIG. 6, search the MH code 1 bft at a time (1), and if it is 0, look at the data at the address indicated by the current address pointer; if it is "1", look at the data at the next address. If the MSB is 1'', the data is the run length, and if it is 0, the data is written to the address revo pointer and used for the next search. In other words, the MSB is l
1 until finding the data ``'' (data starting with 8)
The MH code is searched bft by bft. 7th
Figure 2 shows an example of the code ``HD-do black''0000111°'. From the figure, it can be seen that the above-mentioned code is a ten-length code of ``black 12''.

And the conversion table is made up of different black and white codes. The reason for this is that the same MH code exists with different run lengths for 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 data with MSB = 1 is written not as a run length code but as the program jump address. ing. And on that flight,
Processing corresponding to the MR code is performed to generate a run length code.

MR encoding is an encoding method using two-dimensional compression, so 1
There is no run length code corresponding to one MR code. Since we have to create a run-length code using the data from the previous line using the Motoni MR code, there is a small amount in the table. Figure 8 shows the MR code “OOOO
11” table search example is shown.

(Calculating the minimum transmission time and inserting and deleting iF animals) When transmitting G3, an EOL is added after one line of data and sent. , if it is less than the minimum transmission time, then FiJ
A 1u bit (data O) is inserted, and EOL is added after the minimum transmission time has elapsed.

This device determines whether the transmitted data exceeds the minimum transmission time by converting the transmitted data into the number of bytes based on the minimum transmission time and transmission rate, and then determines whether the number of transmitted bytes is equal to or greater than this converted number of bytes. There is.

The number of bytes transmitted within the minimum transmission time is 9600x10, assuming the minimum transmission time is 10m5 and the transmission rate is 9600Bps.
X10-3 = 12 (bytes).

Fill bits are inserted in byte units.

In this device, the transmission reception data in the G3 mode and the data stored in the memory are always transferred via the FIFORAM 9. If the fill bit, which is an idle signal, is stored in the RAM 9 as image data, the RAM 9 will be wasted.

Also, since the number of FiJIJj bits changes depending on the capabilities of the other device when performing memory transmission, when storing memory, it is necessary to insert the maximum number of Fill bits calculated from the maximum possible minimum transmission time and data speed. .

Therefore, in this embodiment, during G3 mode transmission and memory storage, no Fill bit is inserted into the PIFORAM 9, and after reading from the PIFORAM 9 during transmission, the Fill bit is inserted into the PIFORAM 9.
The KLJl bit is inserted and sent.

Also, during reception, if there are 3 or more consecutive 0 bytes, a method is used in which the 3rd byte and subsequent 0 bytes are not written to RAM9. It has a function to convert from fine to standard when transmitting image data accumulated in . Comparing fine and standard, the line density in the main scanning direction is equal to 8 peu/mm, the line density in the sub-scanning direction is 7.7 ine/mm for fine, and 3.8541 ine/mm for standard. Standard is 1/2 of fine. Since the data stored in the PI FORRAM 9 is separated by one line at EOL, the line can be easily determined. Therefore, in this device, when transmitting data from PI FORRAM 9, 1
Fine → standard (scanning line density) conversion is performed by transmitting every other line.

FIG. 8(B) shows a processing flowchart when a data request interrupt is received from the modem 19 with and without scanning line density conversion.

First, when an interrupt is entered, the data of the current read address pointer is called from the PIFORAM 9. If the data is not EOL, after outputting the data to the modem, the pointer is incremented by 1 and data transfer is repeated. E
When OL is detected, as mentioned earlier, E in RAMQ is
The OL is converted into a (7) EOI for transmission (CCITT recommendation), then a fill pit is added, and a fill is added if necessary, and the EOL and fill are output to the modem. Then, it is determined whether fine→standard conversion is necessary or not. If not, the pointer is incremented by 1 and reading of one line of data is completed. - If it is necessary to convert the force scanning line density, step the address pointer to the next EOL, delete the data for the - line, and then return to the main routine.

(Ranken Shiningu → Raw data conversion) When sending memory in G2 mode, FIFORAM 9
The data stored in the MH code must be transmitted as raw data. In this device, the data conversion is performed by software, but it is quite difficult to convert directly from MH code to raw data. Therefore, the program is simplified by using the decoding function described above to convert the MH code into a line-length code and then converting it into raw data. □ Conversion from run length code to raw data is
This is done as shown in Figure (C).

That is, the Rf and C codes are read, and if RLC is black data, "1" is output to the line memory.

□Repeat until RLC becomes O. If RLC is white data, 0'' is output to the line memory, and RL-RAW conversion is performed by repeating the same process until RLC becomes O.' (B4 → A4M small by software) In this example, 2'048 bits Reading is performed using a reading section l having a light-receiving element. □ Therefore, 8 p e
It is possible to send a B4-width original with Q/mr. However, if the recipient's machine only has the ability to record A4 width), it is necessary to convert B4 data (2048 bits) to A4 data (1-728 bits) before sending. In some cases, the processing is carried out in the reading section 1 using optical or electrical means, but when considering memory transmission, it is not possible to use the reduction function of the reading section 1 considering the data flow. It is impossible.□
Therefore, in this embodiment, reduction is performed using software.

First, the data stored in the RAM 9 as MH code is converted into a run-length code using the decoding function □, and then the data is reduced in the main scanning direction of the line, and then the MH code is
Convert it to a code (or raw data in the case of G2) and transfer it to the modem.

Note that the reduction in the sub-scanning direction is performed by thinning out data line by line, as described above.

do.

The number of dots in the lifetime scanning line of B4 is 2048 dots, A
4 is 1728 dots. If you factor this out, it becomes 32
X26:27X26 gives a ratio of 32:27. So, the data of 2048 dots of B4 is 6 by 32 dots.
Divide into 4 blocks. Then, for one block of 32 dots, it is sufficient to thin out 5 dots and convert it to 27 dots. $8 1 block 3 in figure (D)
2 dots are shown. 6, 13, 1 with diagonal lines in this diagram
By thinning out the 9th, 26th, and 32nd dots, it is possible to thin out the dots at approximately uniform density in the main scanning direction.

FIG. 8(E) shows a flowchart 1 for performing this conversion. In order to facilitate the explanation of the flowchart, for example, data such as the one shown in FIG.
．． Black 5. An example of converting a 32-dot code of white 15 degrees and black 4 to 27 dots will be explained.

First, the total RL counter for one line is TCNT in SPI.
, a 32-dot counter TRL, and a converted run length code SRL are set to 0, a decimation number counter MC among 32 dots is set to 5, and MA indicating an address to be decimated is set to 6.

Then, in SF3, the first RL code white 8 is called from RAM9, and both TCNT and TRL are set to 8 in SF3. Since TRL=8 is larger than MA=6, White 8's data RLC is converted to White 7's data RLC (SF
3).

RLC=white 7-rSRL is o, so MA is 1 with 5P1o
3, the MC becomes 4 and returns to S P 4 again. This time, TRL=8 is /l\larger than MA=13, so 5P16
, SRL is set to White 7, and TCNT is 2o4.
Since it is smaller than 8, the process returns to SF3 and the next RLC=black 5 is called, and both TCNT and TRL become 13. T.R.
I, is equal to MA=13 Ll, N(7)teS P 6teR
LC becomes Black 4. And in SF8 5RL-white 7 and R
Since the color of LC=black 4 is different, the data of white 7 is output to the line memory in SF3, and SRL is reset to 0. Furthermore, MA is set to 19, MC is set to 3, and S is set again.
Return to F3 and proceed to SPI 6. This time RLC to SRL
- Black 4 is set. Then, the next RLC=white 15 is called, and TCNT and TRL are set to 28.

28 is MA=19J: large innote, RLC=white 15 is converted to white 14, 5RL=black 4 and white of RLC=white 14 are compared in SF3, data of black 4 is output to line memory, and SRL is reset to 0.

Then, MA is set to 26 and MC is set to 2. At step SP4, since TRL=28 is still larger than MA=26, the data of White 14 is further converted to White 13, and at this time, S
Since RL is 0, MA is set to 32 and MC is set to 1 at SPI 0.11 without determining and outputting SF3 and SF3.

Return to SF3 again, this time MA=32 has TRL=2
Innote is greater than 8, and White 13 is set on SRL at 5P16. Then, after calling the next RLC = black 4, SF3
Then, White 13 is output, and then Black 3 is output in the same way.

As mentioned above, in the upper row of FIG. 8(F), white 8° and black 5. white 1
5. Black 4's data is the bottom 7° Black 4. White 13. It is almost evenly converted to the black 3 run length code.

Note that step S13. S14, 5p15 is 1 block 3
This shows the initialization of MC, MA, and TRL when 2-dot processing is completed. In particular, 5P15 also has an adjustment function when the run length code spans between blocks. or,
5P18 indicates the output of the last run length code of the l line to the line memory.

In this way, it is possible to convert the number of main scanning dots while using the run length code.

(Operating Modes) As shown in the table below, there are a large number of operating modes regarding the transmission, reception, and transfer of image data in this embodiment. The data flow and code format numbers in each mode will be explained below using diagrams.

First, this device operates in the 14 operation modes M1 to M14 described above.
9(a) to 9(c) are flowcharts of the determination algorithm of the MPU 23 used in determining.

In this embodiment, activation is performed using the start key 51, one-touch dial key 54, speed dial key 53, and memory key 52 on the operation panel 50 shown in FIG.

Furthermore, the judgment is made based on the outputs of the sensor 31 that detects the presence or absence of a document in FIG. 1, the sensor 32 that detects the ON10FF state of the telephone hook, and the roll paper cover sensor 33.
A branch is made.

Furthermore, the mode of the other party is set to G due to the communication of pre-procedure signals prior to facsimile message (image data) communication.
You can know whether it is 3 mode or G2 mode. At the same time, it is also possible to know whether the other party's device has an MR encoding function or only an MH encoding function.

Furthermore, it can be determined whether the FIFORAM 9 can be used during message communication based on the usage status of the image memory of the own device. If memory is stored in RAM9, RAM
9 cannot be used, and if memory is not stored,
RAM9 can be used.

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

First, when the start key is pressed, it is checked whether the earpiece is off-hook or on-hook, as shown in FIG. If there is no document and the roll paper cover is closed, the roll paper cutter operates, and if the cover is open, the paper is fed by a predetermined amount.

-, in the case of off-hook, if there is a document, it enters the transmission mode, and depending on the mode of the other party and the availability of RAM 9, Ml, N2. N3. Move to N6. If there is no document due to off-hook, the reception mode assignment shown in FIG. 9(b) shifts to the routine. In Figure 9(b), the partner machine mode,
M7 to Mll are selected depending on the availability of RAM9.

FIG. 9(C) shows a routine for mode distribution when the memory key 52 is pressed.

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

If the original is not placed on the reading section L, press the start key 51.
When is pressed, if it is on-hook at this time, the mode shifts to memory copy mode M13 in which the image data in RAMQ is recorded in the recording section 17.

Also, if it is off-hook at this time, it shifts to memory transmission mode. When the one-touch key 54 or speed dial key 53 is pressed, the mode shifts to memory transmission mode regardless of the hook state. Memory transmission mode is 02 or 0 when the other machine is
03 memory transmission mode M4. Or it is assigned to G2 memory transmission mode 1M5.

Also, when the memory key is pressed and no original is placed in the reading section and no other key operations are performed, the amount of image data stored in RAMQ is displayed on the display 55 (Fig. 10), and the software timer is activated. waits for the timeout and returns to standby mode.

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

(Mode M1) G3 original transmission, MH, RAM 9 usable The flow of image data in mode M1 will be explained with reference to FIG.

In response to a reading command from the MPU 23, the reading unit 1 converts one line of image data into a run length code RL.
Write to AM3. Then, the MPU 23 transfers the data in RAM 3 to two tree line buffers RAM 5 and RAM 7.
The run length code RL read from the two line buffers is encoded into an MH code and written into the PIFORAM 9. And M
In response to the data request included from the modem 19, the PU 23 transfers the MH code from the FIFORAM 9 to the modem one byte at a time. At this time, the minimum transfer ratio is calculated for each line and fill pits are inserted.

In addition, character information such as the source and time of transmission to be added to the beginning of the image is converted to PI FO using the raw image data 25 output from the CG 25 using the raw data → MH code conversion function.
Transferring to RAM9.

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

The interlinked data request interval from the modem 19 changes depending on the transmission rate.

Data transfer is done in bytes, so 9600
For bps(7), 8/9600=0.83XIO-3
An interwoven occurs every sec.

Furthermore, when the data transfer from RAM3 to RAM5 and RAM7 is completed, the MPU 23 outputs a reading command to the reading section. While the MPU 23 is performing encoding processing (ENC) and interwoven processing, the reading unit 1 performs reading of the original and converting raw data to run length data.

(Mode M2) G3 original transmission, MR, RAM9 available FIG. 12(A) shows the flow of image data.

The data flow is almost the same as in mode M1. The difference is that the code after ENC23-1 is an MR code. However, the data from CG25 is output from ENC23-1 in MH code. For example 24X
When adding a 16-dot character to the beginning, 24 lines of data are transmitted using the MH code.

In Figure 12 (B), CG data is MH, image data is M
A program for storing data in RAM 9 in R is shown below. First, CG
Initialize the number of lines of data, call the data of each line from the beginning, convert the raw data to run length code, RL code to MH code, and R for each line.
Save to AM9.

When the 24th line is completed, the image data of the RL code is read from RAM 5 or 7, as shown in FIG. 3(B).
, (C), each line is MR encoded according to the MR encoding routine of (C).
It is converted into a code and stored in the RAM 9. , (Mode M3) G3 original transmission, MH, RAM 9 usable image data flow is shown in FIG. RAM in Figure 11
Unlike the case where RAM 9 can be used, RAM 7, which was used as a line buffer, is used as a buffer memory for the Ml code.

Therefore, the line buffer is limited to the RAM 5.1 tree, and the encoder ENC 23-1 can only handle data for -lines, so MR transmission cannot be performed if the RAM 9 is unavailable.

The reason for this is that MR encoding requires line buffers for two lines: the current encoded line and the reference line.

(Mode M4) G3 Memory Transmission M H --- Figure 14 (A), (b), (C) The flow of image data in mode M4 is shown in Figure 14 (A). Image data read in fine mode or standard mode is stored in the PI FORRAM 9 in the form of MH code. Further, various information of the image data is stored as a label at the top of the page, as shown in FIG. The information includes the reading size of the image data (number of main scanning dots) SZ, fine or standard (scanning line density) F/S
, the EOL number PFN of that page, etc.

Therefore, if the size of the recording paper of the other machine is smaller than the reading size SZ, it is necessary to perform the main scanning dot number conversion described above, and even if the recording paper size of the other machine is stored in RAM 9 in fine mode, If only the standard mode is available, it is necessary to perform the scanning line density conversion described above.

FIG. 14(B) shows the distribution routine. In FIG. 14(B), first the EOL counter EO
Set C to 0 and set the recording paper size A of the other machine in the previous step.
Sense SZ. And compared with label SZ, ASZ
is greater than or equal to SZ, select mode M4-1 or M4-2. In this case, there is no need to convert the number of main scanning dots.

Also, if ASZ is smaller than SZ, mode M4-3
, M4-4 are 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, and the RAM
If the fine mode is stored in the mode M4-2) or M4-4, it is necessary to further convert the sub-scanning line density.
is selected.

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

A detailed explanation of the data flow in each mode will be given later, but when the transmission of one line is completed, mode M4-1.4
-3, the EOL counter EOC is +1, and M4-2.4
-4 increases EOC by +2. Then, the process moves to a page end subroutine in which the EOC matches the PFN indicating the EOL number of that page in the RAM 9.

The page end subroutine is shown in FIG.
The label GE indicating the final page of the group stored together with a series of pages in M9 is checked, and if the page is the final page of the group, an EOP indicating the end of transmission is output to the other party's machine, and the transmission ends.

On the other hand, if it is not the last page of the group, the next page SZ, F/
S is read out, and if F/S and SZ are the same as the previous page, an MPS signal indicating that the next page will also be sent in the same mode is output.

If not, it sends an EOM signal to the other device indicating that the previous procedure should be repeated from the beginning.

The flow of image data in each mode of M4-1 to M4-4 will be explained below. (M4-1) Main scanning dot, no sub-scanning line density conversion The image data in the RAM 9 is added with a fill bit in the FI document 23-3, and sent from the NCU 21 via the modem 19. Also, the output raw data of CG25 is ENC23-
1 and is MH encoded and not directly transferred to FiJljl.

(M4-2) MPU 23 with sub-scanning density conversion converts from fine to standard using F/523-4 while keeping the MH small output MH code in RAM 9, that is, deletes every other line of data, and writes RAM 3.5.7 Output to. RAM3.5.

The MH data in MH 7 is added with a fill bit by Fil 123-3 and is transferred to modem 19.

Also, the output raw data of CG25 is also ENC23-1 and RA.
Output to Fi Ribun 23-3 via M3.5.7.・(M4-3) MPU23 with main scanning dot number conversion is R
Extract the image data of MH from AM9 and transfer it to DEC23-
2 to convert to run length code RL, and in RL state B
Perform the conversion from 4 to A4. Then M again with ENC23-1
RAM returned to H code and used as FiFo memory
Output to 3.5.7. Thereafter, fill pits are added to the signal by FiuJlj 23-3, and the signal is transferred to modem 19. C
The output raw data of G25 is also converted to MH code by ENC23-1 and then sent to Fi statement 23-3 via RAM3.5.7.
will be forwarded to.

(M4-4) The MPU 23 with both conversion converts the MH data in the FIFORAM 9 into M
After F/S conversion with H as it is, converting it to DEC23-2 run length code RL, converting it to B4/A4, converting the converted run length code RL back to MH code with E, NC23-1, and RAM3.5 Transfer to .7. The output of CG25 is similarly transferred to Fill via ENC23-1, RAt3, and 5°7.

Mode M5) G2 memory transmission --- Figure 15 MP
The U23 extracts the MH code from the FIFORAM 9, decodes it into a run length code RL, and further converts it to raw data RAW, which is alternately transferred line by line to the RAM 5.7. Then, raw data is sequentially extracted from the RAM 5.7 and transferred to the modem 19. In addition, when performing mode conversion from fine to standard, RAM9 and DEC23-
When performing reduction, B4/A423-5 conversion is performed between two DEC23-2s.

The output data of CG25 is stored in RAM5 in the form of raw data RAW.
．． 7 to the modem 19. However, in this case, the CG25 data is transmitted at 7.7 KLine/mm in the sub-scanning direction without thinning out the scanning lines, so that the character size is doubled vertically compared to the 63 mode. This is done to ensure that the sender information can be read even in G2 mode, since G2 is an analog transmission and the image quality deteriorates significantly due to transmission.

(Mode M6) G2 original transmission - 111 Figure 16 All data transfer is performed in the form of raw data. The reading unit 1 writes 1547 minutes of image data as raw data to the RAM 3 in response to a reading command from the MPU 23. And MPU23
transfers the data in RAM3 directly to the two-tree line buffer R
One line at a time is alternately transferred to AM5 and RAM7. Then, in response to data requests from the modem, the raw data is transferred one byte at a time from RAM5 or RAM7 to the modem 19.
Transfer to.

Further, character information such as a source record added to the beginning of an image is transferred from the CG 25 to the RAM 5.7 as raw data.

Furthermore, in the case of G2 mode, 1728-bit image data including a synchronization signal is written into RAM5 and RAM7. The MPU 23 creates an image signal corresponding to this synchronization signal.

(Modes M7, M8) G3 reception MR mode, RAM9 usable (unavailable) - 111 Figure 17 When the MPU 23 receives the MRm+- code from the line via the NCU 21 and modem 19, it first deletes the fill pit. Do, RA
If there is no data in M9, the MR code is transferred to RAM9, and if there is data in RAM9, it is transferred to RAM3 as is. Then, the MR code is sequentially extracted from the RAM 9 or 3, decoded into a line length code RL, and then transferred line by line to the RAM 5 or RAM 7 alternately. At the same time, the run length code RL is transferred to the recording section 17 and recorded.

The decoded run length code RL is stored in RAM5, R
The reason why it is transferred to AM7 and stored is to use it as front line information when converting into MR code.

(Mode M9, MI 0) G3 reception MH code RAM 9 usable (unavailable) - 111 Figure 18 When the MPU 23 receives the MH code from the line via the NCU 21 and modem 19, it first deletes the fill pit. , RAM
If 9 is usable, go to RAM9, otherwise go to RAM3.5
．． Transfer to 7 as MH code. Then, the MH code is sequentially extracted from the RAM 9 or 3, 5.7, converted into a line length code RL, and transferred to the recording section 17 to be recorded.

(Modem Mll) G2 reception --- Figure 19 In G2 mode, uncompressed raw data is sent, so MPU2
3 receives raw data from the line via the NCU 21 and the modem 19, and then alternately stores the raw data one line at a time in the line buffer RAM.
5.

Transfer to RAM7. Then, raw data is sequentially extracted from the RAM 5 and RAM 7, transferred to the recording section 17, and recorded.

Further, 1728 bits of image signals for 1 life demodulated by the modem 19 are written into the RAM 5 and RAM 7.

Since this includes the image signal obtained by demodulating the synchronization signal, the MPU 23 removes the image signal corresponding to the synchronization signal when transferring it to the recording section 17.

(Mode M12) Memory storage-111 Figure 20 F I
M to FORRAM9) (It is almost the same as mode M1 until it is stored by code, the difference is that there is no data from CG25, and when transferring to RAM9, a label LB for file management is added from RAM13 to the beginning of the page. It is to be.

Let me explain about labels here.

The label consists of 24 bytes as shown in FIG. The 1st to 3rd bytes contain an LPM indicating that the data with that label is the final page, and an NPA indicating where the start address of the next page is. The fourth byte contains information for each page. The MSB of the fourth byte contains information GE indicating whether or not this is the last page of the group when data is divided not only in pages but also in groups. F
/S has a standard scanning line density (0.85 lines/mm
) or fine (7 wood/mm).

The data in RAMQ is MH and MR in MD.

Information on whether the data is stored in RL, RAW, or ASCII code is entered. SZ contains information as to whether the data in RAMQ has a reading width of A4, B4, or A3.

The fifth byte is 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 memory storage was performed, the 10th byte contains "minutes", the 11th byte contains "hours", 12th byte is 1
The 13th byte stores the month, and the 14th byte stores the year. Furthermore, the file name PFN of the page is entered as a code in the 15th to 24th bytes.

Then, during memory transmission and memory copying, the mode is determined and information is added based on the information in this label, but regarding time data, memory copying uses the information in the label to set the time of the poem stored in memory as a header. The information in the label LB is ignored and the transmission time is sent when the label is printed and sent to the memory. When time-specified transmission is performed, consideration is given so that the time printed on the received image is not the time stored in the RAM 9, but the time at which the transmission was actually performed.

Furthermore, the image data and label LB once stored in the RAM 9 are cleared manually or automatically by the operator. The automatic clearing flow is shown in FIG. 22.

Note that memory clearing is not performed after memory copying.

(Mode M13) Memory copy --- Figure 23 (A)
The MPU 23 sequentially extracts the MH code from the DRAM 9, converts it into a length code, transfers it to the recording section 17, and records it. Further, the header information is converted from character code to raw data via the MPU, transferred to the recording unit 17, and recorded.

The time in the header is the time when memory storage was performed in the file management label LB stored in RAM9.
25 into an image and recorded in the recording section 17.

FIG. 23(B) shows the time management subroutine. First, in the case of transmission mode, the clock 27 (
The date and time data shown in FIG. 1) are output to the CG 25, and the transmission time is transmitted together with the image. At the same time, RA for communication management
The time and the destination number are stored in M13.

Also, during memory copying, the date and time data TD in the label
is output to CG25. At the time of memory storage, the date and time data of the clock is output to the RAM 9 as data TD.

In addition, data from the clock 27 is stored in the RAM 13 in the receiving eye.
to be stored together with the destination number. Note that in the case of original copy mode, time data is not involved at all.

(Mode M14) Original copy --- FIG. 24 Reading section 1 receives a reading command from MPU 23 and writes 1242 minutes of data into RAM 3 in the form of raw data RAW. Then, the MPU 23 sequentially extracts raw data from the RAM 3, transfers it to the recording section 17, and records it. The output data of the CG 25 is transferred to the recording section 17 in the form of raw data and is recorded.

<Effects> As described above, the image transmitting device of the present invention includes a reading means for reading an image and converting it into an image signal, a storage means for storing the image signal, and a transmission means for transmitting the image signal, Since the date and time at which the image signal was stored is stored together with the image signal, it is possible to later read out when the image in the storage means was read and stored, and it is possible to erase the data. Appropriate information can be given to the operator when deciding whether or not to do so.

Furthermore, when transmitting an image stored in the storage means, data on the transmission time is sent together with the image, and when copying, the memorized date and time is recorded and output, which is convenient for both the receiving and transmitting sides.

[Brief explanation of drawings]

FIG. 1 is a sectional view of the facsimile device of this embodiment, FIG. 2(A) is a basic control block diagram of the facsimile device of this embodiment, and FIG. 2(B) is the basics of the MPU 23 of FIG. 2(A). A diagram showing the functions, Figure 3 (A) is the ROMI of Figure 2 (A)
A diagram showing the structure of MH code data in I, Figure 3 (B)
, (C) is a flowchart of conversion from run-length code to MR code, and Figures 4 and 5 are EO in RAM9.
FIG. 6 is a flowchart of conversion from MH code to run-length code, FIG. 7 is a diagram showing a search example when converting MH code to run-length code, and FIG. 8 (A) 8(B) is a diagram showing a search example when converting an MR code to a ten-length code, and FIG.
A diagram showing the processing flowchart 1 of the PU23, FIG.
) are flowcharts of conversion from run-length code to raw data, FIGS. 8(D) and (E). CF) is an explanatory diagram of the conversion of the number of dots from B4 to A4, Figures 9 (a), (b), and (c) are flowcharts for determining the 14 operation modes of the MPU 23, and the $lO diagram is 11 is a diagram showing the flow of image data in mode M1, FIG. 12(A) is a diagram showing the flow of image data in mode M2, and FIG. The code and image data are MR codes and are a flowchart for storing them in the RAM 9. Figure 13 is a diagram showing the flow of image data in mode M3, and Figure 14 (A) is in mode M4.
Figure 14 (B) is a flowchart diagram that further distributes mode M4 into modes M4-1 to M4-4 according to the partner machine, and Figure 14 (C) shows the page end subroutine. 15 shows the flow of image data in mode M5, FIG. 16 shows the flow of image data in mode M6, and FIG. 17 shows the flow of image data in mode M7. FIG. 18 is a diagram showing the flow of image data in M8 mode. M.I.
A diagram showing the flow of image data in O, FIG. 19 is a diagram showing the flow of image data in mode Ml
Figure 20 shows the flow of image data in mode M1.
Figure 21 is a diagram showing the flow of image data stored in RAM9. Figure 21 is a diagram showing the configuration of a file management label attached to the top of the page for a poem stored in image data in RAM9. Figure 22 is a diagram showing the flow of image data stored in RAM9.
Flowchart diagram for automatically clearing image data in □,
23(A) is a diagram showing the flow of image data in mode M13, FIG. 23(B) is a diagram showing the time management subroutine, and FIG. 24 is a diagram showing the flow of image data in mode M14. In the figure, 1 is a reading unit, 3, 5.7 are RAMs, 9 is FIFORAM used as an image memory, 23 is an MPU, and 25 is a CG. ku■09 kuωQ 悉qFigure (b) m+ nb

Claims (2)

[Claims] (1) It has a reading means for reading an image and converting it into an image signal, a storage means for storing the image signal, and a transmission means for transmitting the image signal, and the storage means records the date and time when the image signal was stored together with the image signal. An image transmitting device characterized by storing information. (2) In claim 1, the transmission time data is sent together with the image data when the transmission means transmits the data, and when the image in the storage means is played back, the stored date and time is output. image transmitting device.