DE3429719C1 - Electronic timed detonator programming system - Google Patents

Abstract

The programming system uses a programming device for entering a binary word representing the required delay time in a memory, for subsequent read-out by a clock generator. A real time is also entered in the memory by the programming device, for providing a comparison standard for the clock frequency of the oscillator, with the binary word read rom the memory corrected in dependence on the quotient of the actual clock pulse count and the required clock pulse count.

Description

The present invention relates to methods for Programming of electronic short time transmitters according to the Generic terms of claims 1 and 4. This Ver driving are particularly used in programming of runtime detonators in storeys.

A basic distinction is made when programming the like short-term timer between a so-called fixed value programming and a so-called floating-point programming. In fixed value programming, for example, a Series of pulses a counter in the detonator on one of the set the desired runtime binary value and then with the clock frequency of an oscillator in the detonator counted down. The clock frequency of the oscillator in the detonator is primarily given as constant and specified provided. Because of the high accelerations that the ignition system is exposed, but can not high-precision crystal-controlled oscillators can be used. Because other oscillators are one of the environmental conditions have dependent clock frequency, it is fixed at this value programming very uncertain whether the set run time is actually achieved.

From DE-PS 33 01 251 it is for programming a electronic timer and in particular an elec tronic runtime igniter known, a programming device  to be equipped with a highly stable quartz clock generator and the timer with a clock generator unknown Frequency. For programming one in the Programming device set runtime on the one hand with the stable frequency and on the other hand in the short-term timer counted the unknown frequency. When reaching the barrel time in the programming device becomes the counter operation in the short time encoder stopped and the run determined in this way stored in a changeable read-only memory. Then there is a test run in which the ver changeable read-only memory stored runtime in a Auxiliary memory is transferred and then the in the Auxiliary memory stored time as well as that in the Programming device preset time can be counted down. When the auxiliary memory in the timer has been counted down, this stops the counting process in the programming device. If the deviation of both counts is within one given tolerance, the programming is considered a success richly displayed.

Based on this state of the art, it is the task the present invention to provide a method that also without feedback when programming fixed values or sliding value programming, in in any case ensures that the set runtime is aimed. This task is solved according to the characterizing features of claims 1 and 4. Further advantageous embodiments of the invention  The dependent subclaims.

When programming the floating-point value, the runtime is the time interval between two entered in the detonator Impulses given. In the detonator from the first to the second pulse a counter with the clock pulses of the detonator oscillator counted up, its clock frequency not be is known. In the flight phase of the projectile, the Counter in the detonator with corresponding in frequency divided pulses from the same detonator oscillator down counted so that it is essentially ensured that the set duration is also achieved. With the one However, one always assumes a set term special initial velocity of the projectile. If this initial speed varies, so does the Flight distance vary, after which the projectile explodes. For this reason, the An to measure the initial speed at the exit of the projectile and the set running time if the ge measured initial speed from that at the Program based on the initial speed correcting speaking.

As stated above, it is another object of the present Er finding to provide a method by which the term of an igniter corrected when programming sliding values can be. This task is solved according to the characteristic features of the further independent Claim, as already stated above.

Advantageously, this is speed-dependent Correction also for fixed value programming Made use of. Both solutions have in common that a calibration time from the programming device into the igniter will give, which then serve as a standard of comparison is pulled to the in a fixed value programming Flight time memory stored value once or at a measurement of the initial speed twice  correct or with a floating value programming and a measurement of the initial speed in flight time correct the stored value once.

Based on the figures in the accompanying drawing The exemplary embodiments presented below are The method according to the invention explained in more detail. Show it:

Fig. 1, the invention Tempiersequenz at a fixed value programming;

Fig. 2 Tempiersequenz the invention at a Gleitwertprogrammierung;

Fig. 3 is a block diagram for explaining the inventive method in a fixed value programming; and

Fig. 4 is a block diagram for explaining the inventive method in a sliding value programming.

According to Fig. 1 of the projectile after loading the system is activated at any one time in a first phase by actuation of the firing button, that is, the igniter battery is switched on and initialised in the system. The duration of this process is approx. 2 ms.

The time is then entered in a second phase by means of the programming device, being in a count memory in the detonator a series of 17 pulses entered and every impulse due to its impulse / pauses represents a binary value of "1" or "0". The binary value is preferably “0” due to a pause time of 25% and a pulse time of 75%. The binary value "1" is preferably given by a pause time of 50% and a pulse time of 50% is shown. The first impulse determines the mode of operation of the detonator. With a binary value of "1", the detonator works as a delay detonator and with a binary value of "0" as an impact detonator without delay, which should not be explained in more detail here.  

The duration of the igniter is binary coded with pulses 2 to 17 . Each pulse entered corresponds to a duration of the igniter of 250 µs or 0.25 ms. After the detonator has been programmed, the detonator is calibrated in a third phase by entering 2 calibration pulses with a time interval of 250 μs in a manner to be described in more detail. The duration of the calibration is measured in the detonator with a resolution of 3.125 x 10 ^-8 seconds, which corresponds to a clock frequency of the detonator oscillator of 32 MHz.

The result is:
Calibration time: 250 10 ^-6 seconds
Duration of the sampling pulses: 3.125 x 10 ^-8 seconds.

It can thus be seen that the calibration time is 8000 Impulse is sampled when the detonator oscillator with its nominal frequency of 32 MHz works. At a Synchronous error of, for example, 2 scanning pulses there is thus a maximum scanning error of:

d. H. a sampling error of 0.25 per thousand.

With a maximum runtime of 4 seconds and one average flight speed of 1000 m per second there is a spread of 1 ms or approx. 1 m.

The method according to the invention in the case of fixed value programming is explained in more detail below with reference to FIG. 3 and a few calculation examples. Assume a maximum flight time (FLZ) of 4 seconds, which is a
mean flight speed of 1000 m per second corresponds to a flight distance of 4 km. The nominal frequency of the internal oscillator f _OSZ is 32 MHz. The flight time is 0.25 ms per bit stored in the flight time memory (FSP). This means that a flight distance (FSTR) of 4 km must be encoded by 16,000 bits. With these parameters, an initial speed of 1000 m per second also corresponds to the number of oscillator pulses counted during 0.25 ms.

The flight time per bit is therefore pre-determined by the calibration time give and is at the nominal frequency of the oscillator from 32 MHz:

Y = 0.25 ms.

If the frequency of the The following flight time results for each oscillator:

The content of the fixed value in the flight time memory FSP is the to correct as follows:

The following relationship applies to the corrected flight time FLZ:

FLZ _corr = FSP _corr · X

Finally, taking into account the actual initial speed v₀ for the flight route FSTR the following correction:

The necessary corrections are based on the following of four examples, the first example assume that the oscillator frequency is nominal frequency corresponds and the initial speed of the Projectile corresponds to the target speed in the second  Example of a deviation in the oscillator frequency is taken, in the third example, a deviation of the An speed is assumed and in the fourth Example of both a deviation in the oscillator frequency as well as the initial speed is assumed.

example 1

f _OSZ = 32 MHz
Target v₀ = 1000 m / s
Actual v₀ = 1000 m / s
FSTR = 4000 m
FSP = 16,000 bits

Example 2

f _OSZ = 24 MHz
Target v₀ = 1000 m / s
Actual v₀ = 1000 m / s
FSTR = 4000 m
FSP = 16,000 bits

Example 3

f _OSZ = 32 MHz
Target v₀ = 1000 m / s
Is-v₀ = 900 m / s
FSTR = 4000 m
FSP = 16,000 bits

Example 4

f _OSZ = 24 MHz
Target v₀ = 1000 m / s
Is-v₀ = 900 m / s
FSTR = 4000 m
FSP = 16,000 bits

FIG. 3 shows a block diagram, on the basis of which the fourth example mentioned above is to be explained. As already mentioned, deviate from the nominal frequency of the oscillator, the actual frequency 24 MHz and deviate from the assumed initial speed corresponding to 1000 m / s, the initial speed is 900 m / s.

From an unillustrated programmer memory 12 is written 'within a count memory 12 is a binary word in a time of flight which is read out at a time of flight per bit of 0.25 ms and a flight distance of 4000 m by 16,000 pulses having a frequency of 32 MHz . On the other hand, 8000 pulses are counted per 0.25 ms at a clock frequency of 32 MHz. These 8000 pulses are stored in a constant memory 14 as a setpoint. During the calibration time of 0.25 ms, an actual pulse memory 16 is opened by the programming device, which accumulates the pulses of an ignition oscillator 10 during this time.

The pulses of the oscillator 10 , which only oscillates at 24 MHz in the present case, are input into the actual pulse memory 16 , with only 6000 pulses arriving in this pulse memory 16 due to the lower frequency in the calibration time of 0.25 ms. After the calibration time, these 6000 pulses are compared with the nominal value of 8000 pulses in a comparison element 18 , ie the quotient of the two pulse numbers is formed, and the number of bits stored in the time-of-flight memory 12 'is corrected in a first correction. This correction is made in a correction element 12 '', so that in the present example the binary word is corrected according to a count of 16,000 bits to 12,000 bits.

If the initial velocity v₀ of the projectile is measured and this deviates from the assumption (1000 m / s) only 900 m / s, then 6666 pulses run into a v₀ measurement counter 22 with a corresponding choice of the measurement section (0.25 m) while the 6000 pulses in the pulse memory 16 , which have run in for 0.25 ms, now specify a setpoint. These 6000 pulses correspond to an initial speed of 1000 m / s, since by definition the calibration time of 0.25 ms is also assigned to the target initial speed of 1000 m / s. In a second comparator 20 , the quotient of the two pulse counts of the counters 16 and '22 is now compared and this quotient is used for a second correction in a correction element 12 ''', the value initially corrected to 12,000 bits now being increased again to 13,332 bits is increased.

As can be seen from the above-mentioned example 4, which is based on the block diagram according to FIG. 3, despite the deviating oscillator frequency and the deviating initial velocity of the projectile, there is an exact adherence to the flight distance, after which the detonator ignites.

Referring to Figs. 2 and 4, he process according to the invention will be explained optimization at a Gleitwertprogram below. According to Fig. 2 of the projectile is activated at any one time in a first phase of the system by actuation of the firing button after loading. This phase in turn takes about 2 ms.

The programming then takes place in a second phase of the detonator by entering two pulses, the time of which distance proportional to the desired duration of the Zunders is. In the igniter, this is from the first to the second pulse a counter with the clock pulses of the Ignition oscillator counted up. This clock frequency is not known. During the flight phase, this becomes corresponding set counter with divided pulses of the same Oscillators counted down. This is the case, for example Counting the pulses with a frequency of 32 MHz and counting down the pulses with a frequency of 8 KHz. This results in a ratio of temp time to Flight time from 1 to 8000, d. H. for a flight time of 4 s the temp time is 1.0 ms.

The method in the programming of the floating point value is explained in more detail below with reference to FIG. 4 and some calculation examples. Again, a maximum flight time (FLZ) of 4 seconds is assumed, which corresponds to a flight distance of 4 km at an average flight speed of 1000 m / s. The nominal frequency of the internal oscillator is 32 MHz. Deviating from the example in the fixed value programming, it should now be assumed that the flight time per bit stored in the flight time memory (FSP) is 0.125 ms. This means that a flight distance (FSTR) of 4 km must be encoded by 32,000 bits. Again with these parameters an initial speed v₀ of 1000 m / s corresponds to the oscillator pulses counted during 0.25 ms.

The flight time per bit is again due to the calibration time given and is at the nominal frequency of the oscillator  from 32 MHz:

Y = 0.125 ms.

If the frequency of the The following flight time results for each oscillator:

Thus, taking into account the actual Projectile initial velocity for flight stretch FSTR the following value:

The necessary corrections are based on the following of four examples again explained, the same Numbers as used for fixed value programming will. Only the content of the flight time memory (FSP) is replaced by the programming time, which is uniform should be 1 ms in all examples.

example 1

f _OSZ = 32 MHz
Target v₀ = 1000 m / s
Actual v₀ = 1000 m / s
FSTR = 4000 m
PROGZ = 1 ms

Example 2

f _OSZ = 24 MHz
Target v₀ = 1000 m / s
Actual v₀ = 1000 m / s
FSTR = 4000 m
PROGZ = 1 ms

Example 3

f _OSZ = 32 MHz
Target v₀ = 1000 m / s
Is-v₀ = 900 m / s
FSTR = 4000 m
PROGZ = 1 ms

Example 4

f _OSZ = 24 MHz
Target v₀ = 1000 m / s
Is-v₀ = 900 m / s
FSTR = 4000 m
PROGZ = 1 ms

FIG. 4 shows a block diagram, on the basis of which the fourth example will be explained. As already mentioned, deviate from the nominal frequency of the oscillator (32 MHz), its clock frequency is 24 MHz and deviate from the assumed initial speed of the projectile (1000 m / s), the initial speed of the projectile is 900 m / s.

As can also be seen from the preceding examples, the frequency of the internal oscillator 100 is irrelevant and does not in itself require correction of the flight time memory 120 ′ contained in the counting memory 120 ′. This frequency is irrelevant because it is used once to count pulses in the flight time memory 120 'during the time window specified by the programming device and then after subdivision in a frequency divider 240 is also used to count down the stored pulses.

On the other hand, there would be a difference in the distance traveled Flight distance if the specified in the programming assumed initial speed v₀ from the actual Initial speed differs.

To take this into account, the programming device specifies a target calibration time of 0.5 ms, and the pulses arriving from the oscillator 100 during this time are counted in a block 140 . The initial velocity of the projectile is then measured by counting the pulses arriving at a measuring point as the projectile flies by. Since, by definition, an initial speed of 1000 m / s should correspond to a target value of 0.25 ms, the number of pulses corresponding to the initial speed must be multiplied by a factor of 2 before comparing in a comparator 200 , since the calibration time is 0, 5 ms is specified.

Claims (4)

1. Method for programming an electronic timer, in particular an electronic runtime igniter, in which a binary word corresponding to the desired time is entered into a time memory by a programming device and is then read out by a clock generator (fixed value programming), characterized by the additional input a calibration time corresponding to a target clock pulse number of the clock generator, a comparison of the target clock pulse number with an actual clock pulse number detected during the calibration time and a correction of the set binary time word in the time memory with the quotient of the actual and target clock pulse number. 2. The method according to claim 1, characterized by comparing the actual number of clock pulses per Calibration time as a proportional target speed value with a measured actual speed value and a Correction of the binary word in the time memory with the Quotient of actual and target speed value. 3. The method according to claim 2, characterized records that the actual speed value with the Pulses of the clock generator in the short-term timer determined becomes. 4. Procedure for programming an electronic short timer, especially an electronic runtime zünders, in which two pulses from a programming device are output, the time interval between which the time and during that time a clock generator in the short timer clock pulses into one Counts in counters, which are then replaced with a reduced Clock of the same clock generator can be counted down (Sliding value programming) by specifying a calibration time corresponding to a desired target speed value, a comparison  this target speed value with a measured Actual speed value and a correction of the on put time with the quotient of target and actual Speed value.