The Micro1401-3 has five clocks, used for timing external signals (clocks 0 and 1), generating general purpose timing pulses (clock 2), controlling waveform output (clocks 3 and 4) and controlling the waveform input sampling rate (clock 4).
These clocks are managed automatically by the application software. The user may often need to drive a clock from an experiment, for example to trigger the start of sweeps of waveform sampling. The BNC Trigger input on the front panel will be connected to the correct clock by software, to act upon your signal.
Sometimes, you need pulses generated by the application software to drive your experiment. The BNC Clocks connector brings the output of clock 2 to the front panel. Your application manual will describe this, if it is relevant.
You may need to take your timing source from outside the Micro1401, instead of the internal crystal clock. All the clocks can be programmed to use an external frequency source on pin 7 on the back panel Cannon 15 pole socket marked Events, in place of the internal sources.
Where signals are to be timed or counted, the application program may use the front panel Event 0 and 1 inputs. For more than two signals, the rear panel Digital inputs, or special purpose top boxes, may be used.
The inputs respond to TTL or switch closure signals, and are held internally to +5 Volts by 10 kOhm resistors. Input pulses should not be less than 100 ns wide and must fall below 0.8 Volts to guarantee recognition. To pull the inputs low, the driving device must be able to sink at least 0.5 mA. The safe working range of the BNC inputs is up to ±10 Volts.
More clock-related inputs, the Clock E series, are provided on the rear panel Events connector. These inputs provide close control of the clocks for people writing their own software. Full details are given in the 1401 family programming manual, and the Micro1401 technical manual. The front panel Event inputs 0 and 1 are often assigned by software to the Clock E0 and E1 inputs.
The F input, pin 7 on the rear Events connector, responds to TTL or switch closure signals, and is held internally to +3 Volts. The input clock rate should not be greater than 10 MHz; no pulse should be narrower than 50 nanoseconds.
The Clock E inputs respond to TTL or switch closure signals, and are held internally to +5 Volts by 10 kOhm resistors. Input pulses should not be less than 100 ns wide and must fall below 0.8 Volts to guarantee recognition. To pull the inputs low, the driving device must be able to sink at least 0.5 mA.
The safe working range of these inputs is 0 to +5 Volts.
The sense of the Clock E and ADC external convert inputs may be inverted by a switch option, but the inputs would all then be held active high if no input is connected.
Registered in England: 972132
VAT: GB 214 2617 96
Producer Registration number: WEE/BD0050TZ
For our US customers, we can provide tax form W-8BEN, that identifies us as a UK company.
(Int.+44) (0)1223 420186
1 800 345 7794
CED, through this site, does two things that relate to privacy. We would like to explain them.
We offer free down-loads of many files on our site, from test programs to complete install files for updated versions of major packages like Spike2 and Signal.
When customers wish to take a down-load of a major package, we ask a few questions, including their name, email address, the serial number of the software for which they seek an upgrade and whether they would like an automatic email whenever we update the product. This information is emailed back to CED when they access the final down-load screen. Within this email, your browser transmits the type and version of browser you are using, and the screen resolution you are running.
The reasons why we take and keep this information are that it is useful for our software development team to know who has taken the latest versions, and it is useful for our web site development team to know which browsers people are using to view our site, and what resolution they have their screens set to.
When people down-load a major package, we try to write a cookie, a small file in your computer, that records your name, serial number of the software package, and the version you are down-loading. These files have a lifetime of one year.
The reasons for storing this information are firstly that if you ask for another down-load some other time, your details are read from the cookie and are pre-written into the form, to save you looking them up again. The other reason is that next time you access our site, your browser looks through your CED cookies and compares the versions down-loaded with the latest version numbers read from our site. If there is a later version of a product you have already down-loaded, we tell you on the home page screen, so you know that it is worth going to the down-load page again.
None of this information is ever given to anyone outside CED. ×