When a PC data acquisition board or card is installed in a personal computer, a wide variety of test automation, measurement, and control applications can be accomplished.

A PC data acquisition system can convert analog signals into a digital output form, which can be manipulated with software. Using software in conjunction with a personal computer, analog data can be displayed, logged, charted, graphed, or stored in memory as needed.

Stored data can later be used and compared with a set of established limits. Control decisions are made if the stored data is at the limit, above or below the limit. With repetitive measurement made by a PC data acquisition system, continuous monitoring and control can be performed.

Based on matching, meeting or exceeding the set limits, a digital control signal (in the form of a single-bit output signal) can be used to turn on or turn off a relay. This in turn can be used to turn on various control elements like fans, pumps, motors, etc.

Alternatively, based on the difference between an input and an established set point, a precise analog output signal can be generated. This signal can be used to provide a complete closed loop control patch, providing continuous control of a process.

All input/output devices provide fully conditioned direct sensor interfaces for temperature, pressure, strain, distance as well as 4-20ma sensors

The company provides comprehensive pre-sales and post -sales support from the sale of individual products to complete data acquisition systems.

What is data acquisition?

Data acquisition is the collection of data in real time from either analog or digital sensors so that it can be processed or stored by a computer. Data Acquisition Systems normally comprise an input scanner or switch, an analog to digital converter and signal conditioning, to either energise sensors or process them so they can be measured directly in engineering units and a computer to process, log and display the information.

Data Acquisition systems can also form part of a process control system which through the use of appropriate software provides direct digital control of various industrial processes. Similarly they can be used for data logging and process or alarm monitoring.

Data Acquisition Systems are used pervasively in a wide range of industries including electricity generation and transmission, Chemical and Petrochemical, Highways and Transport, Oil and Gas and Steel production, as well as research and development.

Measurement Systems has been in the data acquisition industry since 1981 and has supplied several million data acquisition channels on an international basis. Visit page

License: Demo
Cost: $150.00
Size: 4.12 MB
Download OPCNetListener Free Trial

Transistor T1 can also be a TUP. Check out the TUP/TUN document for a large selection of European transistors and what this system is all about. Diodes D2 and D3 are both small signal diodes (1N4148). Diode D1 (1N4001) eliminates transients and possible sparking over the relay coil. Do not use a signal diode for this but a rectifier diode like the 1N4001 or other types of the 1N400x series. Resistor R2 controls the sensitivity. Also your choice. Select one between 10 and 22 Mega-ohm, or use a trim-pot.

The MC14093B is a CMOS quad 2-input NAND Schmitt trigger. The supply voltage can be between 3.0 and 18Vdc. It is pin-for-pin compatible with the CD4093. The capacitors are standard ceramic types but try others if you have them available. (download schematic)

Parts List:

   R1 = 470K                N1,N2 = MC14093B
R2 = 15M*                   T1 = 2N3906 (these will work also: PN200, 2N4413)
C1-C4 = 2N2 (2.2nF)                        (NTE159, ECG159, BC557, BC157, TUP)
D1 = 1N4001                 Ry = Relay (12V or matching supply voltage)
D2,3 = 1N4148             Sensor = Stainless Steel probes, brass, chrome, etc.

Please note:
Unused inputs MUST be tied to an appropriate voltage level, either ground or +12V. In this case, tie input pins 8, 9, 12, and 13 to either ground or +12v. Unused outputs (10 & 11) MUST be left open. You can use them as spares when needed.
In regards to the sensor, use your imagination. Stainless steel would be preferred but try other materials too. Depending on what type of fluid you use it for you naturally would choose your type of sensor which would resist corrosion for that particular fluid. I often use chrome bicycle spokes with very good success. The 'Sensor' works via the capacitive method.

The "RESET" switch in the circuit is optional. The relay can be replaced with anything you like; buzzer, lamps, other relays, etc.

Below are a couple valuable comments from Dave Burton of Burton Systems Software:

Thanks, Tony, for publishing your Fluid-Level Sensor design. I'm using it to detect sewer line plugs (water backing up toward the access port), and hot water heater / clothes washer / AC condensate pump overflows/leaks (water on the basement floor). It works very well.

Also, it says "the 'Sensor' works via the capacitive method." But I don't think that is correct. It would be more accurate to say that, for detecting fluids that are perfect insulators, the circuit CAN be made to work by detecting an increase in capacitance when the fluid replaces air in an air gap in the sensor.

But for the more common case of fluids that are not perfect insulators (like water on my basement floor), the circuit works by detecting resistive conduction through the fluid. It is lowered resistance that is detected, not increased capacitance.

To detect insulating fluids via the capacitive method would require good sized plates separated by an air gap, and careful adjustment of the sensitivity via R2 to distinguish between the possibly small change in capacitance due to the presence of the fluid. The difference might be small because there is only a fairly small differences between the dielectric constants of air and some common fluids. E.g., air has a dielectric constant of 1, and typical oils have dielectric constants of 2 to 5. Note, too, that desire to get a measurably large amount of capacitance leads us to desire that the gap between the plates be small (because the capacitance is inversely proportional to the distance between the plates), but the gap cannot be too small, lest capillary action hold fluid between the plates even after the fluid level has dropped below our sensor.

But to detect dirty water or tap water you can use almost anything: even a pair of bare wire ends several am apart works just fine.

Also, one handy feature not mentioned in the article is that several resistive "sensors" can be hooked up together (in parallel) to detect fluid at any of several different locations. visit page

Notable Parts:

* K1 is the return fuel line relay
* K2 is the send fuel line relay
* S1 is the primary switch
* S2 is the bypass switch
* S3 is the purge button
* S4 is the On/Off switch
* LED1 is the return line indicator
* LED2 is the send line indicator (download schematic)


Usage
When the vehicle is warm enough so that it can run on vegetable oil turn on S1. The send line will immediately switch to VO and the return line will stay on diesel for a user specified amount of time. To determine correct timing switch your engine to VO and time how long it takes for the diesel to be purge from the system. Now you set the time in the circuit by changing R1 to the correct value based on 1.1 * R1 * C2. To make it easier, I set C2 at 1000µF, so if you want about 45 seconds use the closest value below 45Kohms (45,000 ohms). In the circuit as set up above R1 is 39K ohms giving a timing of just under 45 seconds (1.1 * 39 = 42.9).

When you are a few minutes from home turn off S1 and press S3. By turning off S1 you will switch the send line back to diesel and by pressing S3 you will keep the return line on VO for a user specified amount of time. To set timing use the same value resistor for R4 as you did for R1.

If you stop for a short period of time and the engine is still warm enough to run on VO when you restart it then either switch on S2 for a minute or so or press the purge button. In either case you will bypass the on-delay timer and keep the VO going to the VO tank.
Caveats
Do not expect exact timing from this circuit because capacitors are not perfect and voltage leakage will increase the time to some extent. When I timed the above circuit I found that it varied approximately 2 - 5 seconds (though I used a stopwatch and might have hit the start early or late, so YMMV). The timing can also be affected by length of time of discharge of the capacitors. If you turn off the circuit and turn it on again pretty quickly the timing can be much shorter than expected. I do not consider this an issue because the time it takes for the vehicle to cool down should be well longer than the time it takes for the capacitors to discharge. If this does become a problem use a lower value capacitor and a higher value resistor, for instance you can use a 220uF capacitor and a 180K ohm resistor to get approximately the same amount of time but the timing errors I initially stated may become more noticeable.

Modifications
If you want the circuit to be more automated so you can just switch it on when you turn on the vehicle and it will wait until temperatures are high enough before switching from diesel to VO, just add a thermostat into the circuit directly before S1. Use a NO (normally open) thermostat set to close it's contacts when the desired temperature is reached.
Parts List

* (1) 7805 voltage regulator
* (2) 1N4148 diodes
* (2) SPST switch
* (1) DPST switch
* (1) N/O momentary push button switch
* (2) LM555 timer
* (2) 1000uF polarized capacitors
* (1) 0.01uF non-polarized capacitor
* (3) 0.1uF non-polarized capacitors
* (2) LEDs
* (2) 500 ohm resistors
* (2) 100K ohm resistors
* (2) resistors chosen for timing value (R1 and R4)
* (2) solid state relays capable of handling the current your solenoid valves draw

All capacitors should be rated at least 25 volts, anything higher is fine.
Resistors should be rated for 1/4 watt.
7805 is a generic voltage regulator, if it says 78L05AZ or something it's still fine. visit page

Disclaimer & Terms Of Use:
This circuit is presented as is with no warranty of any kind, I can not be held responsible for any damages you incur either financial or otherwise. This design was created by Seth Koster and may not be used for profit. I hereby grant permission to use this circuit for personal use. Be sure to keep a careful eye on the circuit for a while after you install it to ensure that it is working properly and you installed it correctly. Please use safety equipment when working on electronics!

To assemble and test the circuit, you will need the following tools

* Soldering iron, solder and a small wet sponge to clean the iron
* A small pliers and a snips
* Multimeter for measuring voltages and testing connections

Electrical schematic is here

Bill of materials is here

PCB silkscreen is here

PCB layout is here View and order PCBs using the free software at www.expresspcb.com Three mini-boards cost $51 + shipping.

Assembly drawing of the layout

Sensor
Start with the pressure sensor end. Its the section in the dashed box on the first page of the schematic. Pictures of the construction are shown here. You will need a soldering iron, fine solder, a piece of vero board, a snips and a volt meter. Order the pressure sensor (26PCBFA6D), the INA122, and a small aluminium box from farnell. You will also need a 4m length of 1/4" plastic tubing and a long length of 3 core cable. The length of cable depends on the distance from the sensor to the solar panel at the river bank. Measure the distance with a throw-bag rope and add a few metres. I used shielded cable but ordanary house wiring cable should do fine. Solder the circuit together, power it with a 9V or 12V battery and measure the output using a volt meter. It should read about 0.1V normally and increase when you suck on the tube. If all is ok, put it in the box. You will have to drill holes in the box for the tube and cable. Use a separator to create a cavity for the open end of the sensor as shown in the pictures. Test the circuit again and then fill it with epoxy. Make sure nothing is shorted to the side and that epoxy doesn't get into the open end of the sensor. Test it again while the epoxy is wet by connecting a battery to the far end of the cable. If something has shorted, you will still have a chance to move things around. If all is ok, stick on the lid and let it dry. After it has cured, drop it in a barrel of water and power up the far side of the cable with your battery. If the signal voltage reads somewhere around 1.5V per metre of water, pat yourself on the back.

Before I potted the sensor with epoxy, I screwed the box to one end of a 0.5m length of stainless steel. At the other end of the steel, I drilled some 10m holes to allow me to bolt the sensor to the side of an existing stick gauge at the river bank. The distance between the sensor and 10mm holes allowed the sensor to be mounted under the water without having to drill any holes under water. The system should be installed while the river is at a very low level to ensure the sensor always stays under water.

Pictures of sensor construction
Datasheets for the components can be found at Honeywell , Texas Instruments and Farnell

Controller
Order the controller components and solder them in. The PIC, PT6102 and the INA122 can be obtained as free samples. Look at the Bill of Materials to get order numbers for the rest of the components. Use an ic socket to mount the PIC. The Batt and Phone connectors have extra holes to either use terminal blocks or "Molex" connectors. I find Molex very convenient but if you don't have a crimping tool, go for the terminal blocks. Once assembled you will need access to a PIC programmer such as the ICD2. If you have no way of prorgamming it, send me a PIC and I'll program it for you. Program the PIC using the hex file below and the MPLAB softwar e that you can download from Microchip. During programming, the ICD2 needs to be connected to, and configured to use, an external 9V supply. If you're stuck, send me a PIC and I'll program it for you. Next power up the system using a 12V supply or a battery. The LED should toggle on and off every second.

Hex file for programming PIC is here

Phone

So far, I have built systems using the Siemens M35 and the C45. Any old Siemens phone should do but the connectors on the later ones have gotten smaller so it won't be as easy to solder on the wires. The battery is removed from the phone and it is powered directly by the controller. The AT language used to talk to the internal modem is much the same for all Siemens phones. I have put some pictures of wiring an M35 here . The wire needs to be very fine. I used "wire-wrap" wire. It helps to put some solder on the wire before soldering to the phone. In the pictures shown, the red and black wires are soldered directly to the phone pcb. It is also possible (and easier) to solder them to the contacts that would normally press against the battery. Siemens also make a range of GSM modems such as the TC35. These are made for telemetry applications and would be easy to wire up but would cost you a lot more that an old phone.

Phone connector pin-out here

Pictures of phone wiring here

Installation
A picture of an early RiverSpy rev 2.0 controller is shown below. The latest version is a bit larger and uses through hold components instead of surface mount to make it easier for an inexperienced person to assemble. I'll put up some pictures of the latest rev later.

1. Terminal block for solar panel or external 12V supply
2. Molex connector for battery (paralleled with connector 1)
3. Debugging interface can be used to monitor phone communications using a pc serial port
4. ICD2 interface for programming the PIC
5. Molex connector to mobile phone
6. Molex connector to underwater sensor

The controller, battery and phone should be mounted in a waterproof box. A plastic box allows optimum phone coverage but if vandalism concerns require the use of a metal box, then an external antenna for the phone may be required. A frame should be contructed to mount the solar panel and the box. To optimise solar energy in winter, the solar panel must face south, have a clear view of the sky and be inclined at 70 degrees to the horizontal. Once all of the components have been connected together, configure it as per the installation manual given below.
Send me an email if you need some help.

Installation manual is here

Debugging

I have also put up a schematic of a small circuit that I use for debugging here. All it does is convert a 5V-0V signal to a +12V-12V signal suitable for connecting to the serial port of a pc or laptop. It listens in on the communications between the control board and the phone. I normally connect it to the RX (receive) line of the PIC. RX and GND are at pins 5 and 6 of the connector J4. RX carries the data going from the phone to the PIC. The phone should echo the characters sent from the PIC to the phone so you should see both sides of the conversation. If this is not working, it can also be connected to the TX (transmit) line but this only shows the characters sent by the PIC. The characters can be displayed on the pc using hyperterminal set at COM1, 9600,N,8,1, no flow control. A similar circuit is included in a siemens pc data cable so if you have one of those, just disassemble the connector at the phone end and use that instead. The pinout of the phone connector is given here. Do not connect the TX of the data cable (pin6, RX of the phone) to the phone at the same time as connecting the TX from the PIC. (its like two people trying to talk using walkie talkies at the same time) Also note that pin 3 (Power) and pin 4 (Fbatt+) shown in the phone connector pinout are not the same as the positive terminal of the phone battery (BATT+).

Contacts
If you have questions, contact Daithí Power, visit page

The sensor board is connected to the controller board via a 3-core cable. One wire carries a 10V supply to the sensor board. Another wire carries the analog pressure signal back to the controller. The third wire is a ground. The controller board is mounted somewhere on the river bank, in a weather-proof box along with a 12V battery and an old mobile phone. A solar panel is mounted above the box so the location should have an unobstructed view of the southern sky. If vandalism is a concern, the system should perhaps be mounted on top of a tree or a high pole.

Every 15 minutes, the controller board powers up the sensor board and reads the signal once per second for thirty seconds. The measurements are averaged so that the reading is not affected by surges in the water level. Once the reading has been taken, it is stored in memory and the system goes into a low power mode until it is time to take the next reading. Once a day at 09:00, the 96 measurements taken the previous day are collated into a single sms message and sent to an email gateway. The email generated is read by a server which updates the wap and web sites.

The phone that I used is an old Siemens M35, but I think that the command set is the same for all of the M,C and S 25 and 35 phones. The phone does not contain its own battery. (The batteries in those phones were fairly bad anyway) Instead it runs from a supply taken from the 12V battery via a dc-dc converter.

When the system receives a phone call, it examines the caller id to see if an administrator is calling. If it is an admin, the system allows the remote phone to ring once and then hangs up. An sms is sent to the administrator containing the most recent level, the level from 30min previous, the level from 60 min previous and the current state of the 12V battery. If the caller id is not that of an admin, the system will answer the call and give a series of beeps to indicate the most recent level.


Controller board, phone, battery and solar panel mount
The photo below shows the original RiverSpy system with a controller prototyped on veroboard. RiverSpy 2 is laid out on a printed circuited board. The layout file is at the bottom of this page.


When admins ring the phone, the system declines the call and sends back a text of the level now, 30 mins ago and 1 hour ago. When others ring the phone, the system answers the call and gives a series of beeps to indicate the current level.

Next Page

• thermometer with 1°F (0.5C) resolution
• four switch inputs, four relay outputs
• only an handful of cheap parts
• graphic LCD display
• script interpreter built-in, can run ASCII programs (basic-like)
• 6KB non volatile script memory
• full screen editor built-in
• modular C source code (need a graphic LCD driver?)
• Two applications provided:

CHARTING THERMOMETER
Load this script to make Scriptherm draw temperature graphs





SMS PHONE-MAIL ENPOWERED VENDING MACHINE
Load this script to control a refrigerated vending machine that sends you a SMS phone mail message when empty




Downloads: the contest entry with project all circuit details and source code from the National Semiconductor's web site, or the PDF schematic only. Visit Page

A circuit board was designed using ExpressPCB software. The image of the board is below. The design file requires a free download from ExpressPCB (for windows only). Traces on the top of the board are red, and on the bottom are green. Component values are given on yellow, but are not printed on the board, if you use the cheapest board production service. There are actually two copies of the circuit on one production board (see design file), so you need to cut them apart with a band saw.

Parts list:

• LED is a one watt Cree XLamp™ 7090WBL ordered from All Electronics, part number LED-112 (blue light) or LED-110 (white).
• BUZ71A is an N-channel power MOSFET ordered from All Electronics, part number BUZ71A
• The IC is a NE556 dual timer, digikey part number 296-6504-5-ND, or digikey part number LM556CN-ND
• All surface mount parts are 1206 sized parts from digikey. Capacitors are type X7R from kit part number PCC6-KIT-ND. Resistors are 5% tolerance, thick film, from kit part number CR1A-KIT-ND .
• Variable resistors are Audio Taper Potentiometers jameco part number 255441; manufacturer's part number RV24A-10-15R1-A100K
• Push button and switches can be any small, low power switches. The push button (Trigger) should be normally-open.
• Battery pack consisted of 4 AA cells (6 volts nominal). The battery holder was similar to digikey part number BH24AAW-ND.
• Box is a 5"x2.5"x2" ABS Speedy box, jameco part number 18913

Construction

Solder the surface mount components first, then a socket for the 556 ic. Put the 4.7 microfarad through-hole capacitor and MOSFET on the board last. Controls were mounted on the front panel, then wired to the board. A small plastic insert held the battery pack at one end of the box. The box is small enough that the printed circuit board was simply pushed against the bottom of the box by the connecting wires. To fit the small box I used, the MOSFET had to be bent flat toward the right side of the board, as you can see in the photo below.


Wires going to the controls were twisted to minimize noise. HOWEVER, it may be necessary to fiddle with the placement of the wires in the bos in order to keep the LED from latching on. When you first turn on the circuit be ready to immediately. visit page

The circuit shown above has two standard CMOS multivibrators. The second is gated by the first. The duty cycle of the first oscillator is about 1%, or 10 mSec every second. A logic-high at the telemetry transmitter control turns it on.


The circuit board was layed out using ExpressPCB software. You will need to download a copy to view the design file. The components are all surface mount. The dots shown below are on a 0.1 inch grid.


Note the antenna lead at the lower left. At 433 MHz (70 cm wavelength) a quaterwave antenna should be 17 cm long. The battery is partly shown at the right. It is a CR1620 lithium cell, but any 3 volt source may be used. The transmitter module sticks out to the left. Visit page

IMPLEMENTATION
The PIC16C5X based controller receives movement commands from a host, compares them to the actual position, calculates the desired motor drive level and then pulses a full H-bridge (Figure 2). In this way it serves as a remote intelligent positioner, driving the load until it has reached the commanded position. It can be used to control any proportional D.C. actuator (i.e., D.C. motor or proportional valve).

This system is ideally suited for remotely positioned valves and machinery. It can be used with D.C. motors to easily automate manual equipment. Because of the 5-wire serial interface, the positioner can be installed near its power supply and load. The remote intelligent positioner can then be linked to the central control processor by a small diameter easily routed cable. Since the positioner is running its own closed-loop PID algorithm (Figure 3), the host central processor needs only to send position commands and is therefore free to
service the user interface, main application software and command multiple remote positioners.

The limit switch inputs provide a safety net which keeps the system from destroying itself in the event that the feedback device is damaged. The optional current sense input can be used to determine if the load has jammed and prevent overheating of the actuator and drive electronics.

The commanded positions are presented to the PIC16C5X via a microwire type protocol at bit-rates of up to 50 Kbs for a 4 MHz part. As currently implemented in this application note, the position request is the only communication. There are several
variable locations available which could be used to down-load the loop gain parameters, read positioner information, or set a current limit. The host that is sending the position request must set the chip select low, and wait for the PIC16C5X to raise the "busy" (DO) line high. At this point, eight data bits can be clocked into the PIC16C5X. The requested position is sent most significant bit first and can be any 8-bit value. Values 1 through 255 represent valid positions with 0 being
reserved for drive disable. The PIC16C5X acquires its data by way of a
Microwire(R)

A/D converter. This part was chosen for low cost while providing adequate performance. In Figure 1 the second channel of the A/D converter is shown connected to a peak current detector. If the user desires, the PIC16C5X could monitor and protect the motor from overcurrent conditions by monitoring the second channel.

Download: Documentation Source Code Visit Page

Once it was determined that 400 MHz radiation is capable of forest penetration to the range specified, the telemetry transmitter design was optimized for greater battery life. After exploring several potential oscillator designs for transmitter input, an op-amp circuit was designed with appropriate PCB layout. A 433 MHz transmitter/receiver pair was constructed and tested to show signal range at the same level as earlier measurements at significantly lower power consumption rate. The final transmitter has a total current draw of 70 uA. This translates to roughly one and a half months of continuous operation using freely available 70 mAh lithium-ion coin batteries. Components for the transmitter receiver pair are available at considerably less cost than commercial devices, with component cost for each transmitter at roughly ten dollars and for the receiver at less than twenty dollars.



Original document Wireless Telemetry: Christopher Yeou - Hwa Chau

Here is a screen shot of the Visual Basic 5 Program. The program still has some bugs, but its just error trapping things, like clicking the connect button with no com port selected will give you a error. I will fix that later, or you can do it your self. The software is available to anyone who wants it, feel free to modify it and way you wish. This program is made in Visual Basic 5, but will work fine in Visual Basic 6.


The program will update the current temperature every one second on the PC screen and will save it to a txt file on the Hard Drive every five minutes, along with the time and date. It will also display max and min temperature and max and min pressure for a 24 hour period, and plots pressure and temperature for a 24 hour period.

Weather Monitor logger Schematic
The LM335 is a presision temperature sensor, its output is a linear relationship (10mV/Kelvin). The LM335 is a zener diode that its voltage drop across increase as temperature increases. Note that there is a 2.2 Kohm current limiting resistor. Without the limiting resistor the LM335 will have to dissipate too much heat and increase the temperature reading. The formula for calculating the output of the LM335 is

Temp(in C) = (Vout*100)-273.15

To convert that to F it would be

Temp(in F) = (temp*1.8)+32

From a range of -20C(68F) to 45C(113F) the output range is about 1.3V's. However the ADC has a range of 4.096V, which is fine but if you would like to get a better resolution(more accurate temp reading) you could use a op amp circuit to make the output votlage be 0 V at -20C and 4V at 45C. Connecting it directly will, however, give you 0.1 C/1mV or .05F/1mV which is very good, but the opamp circuit would be more work, but would give you close to .01F/1mV. I dont think it really worth it , but i just thought i might mention it. I also just added a MPX4115 pressure sensor to monitor pressure as well, but i havnt updated the schematic with yet.


Note that i didnt show the connection to the PC, this is showen on the intro page.

Downloads
1 Kb BASIC Stamp II Code
3 Kb Visual Basic 5 Code
0 Kb Templogger Setup program Coming soon.
100 Kb Datasheet for the LM335

Note: The Visual Basic code is the code you can edit in Visual Basic 5, the Templogger program is a setup file to install vbtemplog.exe. If you dont have Visual Basic 5 you can install this and use the Temp Logger program. You cant modifiy it though.

Conclusion
With a little more work you could use this to read up to 8 different temperatures in different areas. This would require a lot more code on the Visual Basic side of it because the string of data coming in would be 32 bits long, however not impossible. In the future i plan on adding a MPX4115 pressure sensor to this and log the pressure as well.

This circuit overcomes this weakness. The switch is activated by voice level above the noise and not activated by background noise. This is done by utilizing the differences in voice and noise waveforms. Voice waveforms generally have a wide range of variation in amplitude, whereas noise waveforms are more stable. The sensitivity of the voice activation depends on the value of R6. The voice activation sensitivity is reduced from 3.0dB to 8.0dB above the noise if R6 changes from 14k to 7.0k.

The potentiometer VR1 varies the voltage to the A/D U1 pin6, since only the lower 6 bits are used; the trim pot VR2 has to adjust so that the maximum input to the U1 will not exceed 1.25V. The S2 (D6) and S3 (D7) are used for controlling the rotation direction of the motors. S1 set the transmitter address; this address has to match with the address of the decoder circuit.


The receiver module WZ-R01 receives the data from the transmitter and feeds that data to the decoder U1 (HT-648L); the 8bit data will then be decoded. The first two significant bits D7 and D6 control the motor rotation direction. The lower 6 bits vary the duty cycle of the output pulse. U2 is a 12bit counter; it is configured so that it will reset itself every 64 counts. The oscillation circuit forms by U4c, U4d and U4e providing approximately 1MHz clock to the counter U2.

The 8-bit magnitude comparator U3 (74HCT688) compares the data from the counter U2 with the data of the decoder U1; when data from both are match, it will output a pulse to cause the D-flip flop U5 changing it's state.

By varying the data output of the decoder from 0-64; the duty cycle of the output pulse at U5 pin5 can also change from 0-100%. This output pulse will then be used to control the speed of the motor.

With 1MHz clock input the PWM frequency output is about 15.6KHz. The motor has less audible noise when run at a frequency higher than 10KHz.You may need to change the frequency depending on the motor you're going to use.


The motor driver section is very straightforward; the LMD18200 can handle 3A continuous motor current and 6A peak. In this circuit the sign/magnitude mode of operation is implemented. The current sensing circuit provides protection to both the driver and the motor; it set at 2A max. You can change the current limit by using a different current sensing resistor value (see LMD18200 data sheet for details) or the voltage reference at pin6 of the U7Op-Amp

All of the components use in this project can be purchased from us. Email us at wzmicro@worldnet.att.net, if you have any questions or comments. Your feedback is mostly appreciated.

What Can T/Mon NOC Do for You?

• T/Mon NOC provides a single, one-screen view of all your monitored equipment. T/Mon NOC will tell you 100% for certain whether anything has gone wrong with any of your monitored equipment, so you can be absolutely sure there are no secret problems anywhere in your system.
• T/Mon NOC can monitor up to 1 million alarmpoints, giving you ample capacity to monitor everything in your facilities.
• T/Mon NOC presents information in simple, plain English, including detailed text messages telling system operators exactly what to do in case of an emergency.
• T/Mon NOC’s Derived Alarms and Derived Controls let you automate every aspect of your systems using simple Boolean logic.
• You can filter alarms for the needs of different users. You can select which alarms are immediately forwarded to technicians via pager and email, which alarms can be viewed locally on the T/Mon NOC console, and which alarms are just logged to a history file for recording and later analysis.
• At every level of your organization, people can see the information they want without being bombarded with nuisance alarms. Actually, this list just scratches the surface of T/Mon NOC’s capabilities. For more information about what T/Mon NOC can do for you, see the T/Mon NOC Product Data Sheet on page 16.
  

How Can You Know That T/Mon NOC Will Work for You?
T/Mon NOC is not a new or untested product. T/Mon units have been in the field for years, successfully performing for clients who need stable, bulletproof monitoring and control to support their mission-critical operations.

What Do Real People Who Use T/Mon NOC Say?
“DPS Telecom gave us a reliable way of accessing a variety of equipment, regardless of the brand or provider. We now have a common interface for our existing system.” Harold Moses, KMC

Telecom “DPS told us we didn’t have to pay if it didn’t work. It works and it’s sweet.” Glenn Lippincott, Southern Company

“It’s hard to find companies with the intelligence and aptitude to meet the customer’s exact needs, and I believe that is what DPS is all about.” Lee Wells, Pathnet

Why You Need Help With Your SCADA Implementation
Implementing an SCADA system can seem deceptively easy — you just look on the Web, find a few vendors, compare a few features, add some configuration and you’re done, right?

The truth is, developing a SCADA system on your own is one of the riskiest things you can do. Here are some of the typical problems you might face if you don’t get expert advice when you’re designing your system:

1. Implementation time is drawn out: It’s going to take longer than you think. Network monitoring is a highly technical subject, and you have a lot to learn if you want a successful implementation. And anytime you are trying to do something you’ve never done before, you are bound to make mistakes — mistakes that extend your time and your budget beyond their limits.
2. Resources are misused: If you’re not fully informed about your options for systems integration, you may replace equipment that could have been integrated into your new system. Rushing into a systemwide replacement when you could have integrated can cost you hundreds of thousands of dollars.
   
3. Opportunities are missed: If you install a new SCADA system today, you’re committing your company to that system for as long as 10 to 15 years. Many companies design what they think is a state-of-the-art SCADA system — and then find that their technology is actually a generation behind.

But you’ve got to be able to make an informed decision, because the stakes are incredibly high. ASCADAsystem is a major, business-to-business purchase that your company will live with for maybe as long as 10 to 15 years. When you make a recommendation about a permanent system like that, you’re laying your reputation on the line and making a major commitment for your company.

And as much as SCADA can help you improve your operations, there are also some pitfalls to a hasty, unconsidered SCADA implementation:

• You can spend a fortune on unnecessary cost overruns
• Even after going way over budget, you can STILL end up with a system that doesn’t really meet all your needs
• Or just as bad, you can end up with an inflexible system that just meets your needs today, but can’t easily expand as your needs grow
  

So let’s go over some guidelines for what you should look for in a SCADA system.

What to Look for in a SCADA RTU
Your SCADA RTUs need to communicate with all your on-site equipment and survive under the harsh conditions of an industrial environment. Here’s a checklist of things you should expect from a quality RTU:

• Sufficient capacity to support the equipment at your site … but not more capacity than you actually willuse. At every site, you want an RTU that can support your expected growth over a reasonable period of time,but it’s simply wasteful to spend your budget on excess capacity that you won’t use.
• Rugged construction and ability to with standextremes of temperature and humidity. You knowhow punishing on equipment your sites can be. Keep in mind that your SCADA system needs to be the mostreliable element in your facility.
• Secure, redundant power supply. You need your SCADA system up and working 24/7, no excuses. Your RTU should support battery power and, ideally, two power inputs.
• Redundant communication ports. Network connectivityis as important to SCADA operations as a power supply. A secondary serial port or internal modem will keep your RTU online even if the LAN fails. Plus, RTUs with multiple communication ports easily support LAN migration strategy.
• Nonvolatile memory (NVRAM) for storing software and/or firmware. NVRAM retains data even whenpower is lost. New firmware can be easily downloaded to NVRAM storage, often over LAN — so you can keep your RTUs’ capabilities up to date without excessive site visits.
• Intelligent control. As I noted above, sophisticated SCADA remotes can control local systems by themselves according to programmed responses to sensor inputs. This isn’t necessary for every application, but it does come in handy for some users.
• Real-time clock for accurate date/time stamping of reports.
• Watchdog timer to ensure that the RTU restarts after a power failure.
  

What to Look for in a SCADA Master
Your SCADA master should display information in the most useful ways to human operators and intelligently regulated your managed systems. Here’s a checklist of SCADA master must-haves:

• Flexible, programmable response to sensor inputs. Look for a system that provides easy tools for programmingsoft alarms (reports of complex events that track combinations of sensor inputs and date/time statements) and soft controls (programmed control responses to sensor inputs).
• 24/7, automatic pager and email notification. There’s no need to pay personnel to watch a board 24 hours a day. If equipment needs human attention, the SCADA master can automatically page or email directly to repair technicians.
• Detailed information display. You want a system that displays reports in plain English, with a complete description of what activity is happening and how youcan manage it.
• Nuisance alarm filtering. Nuisance alarms desensitize your staff to alarm reports, and they start to believe that all alarms are nonessential alarms. Eventually they stop responding even to critical alarms. Look for a SCADA master that includes tools to filter out nuisance alarms.
• Expansion capability. A SCADA system is a longterm investment that will last for as long as 10 to 15 years. So you need to make sure it will support your future growth for up to 15 years.
• Redundant, geodiverse backup. The best SCADA systems support multiple backup masters, in separate locations.. If the primary SCADA master fails, a second master on the network automatically takes over, with no interruption of monitoring and control functions.
• Support for multiple protocols and equipment types. Early SCADA systems were built on closed, proprietary protocols. Single-vendor solutions aren’t a great idea — vendors sometimes drop support for their products or even just go out of business. Support for multiple open protocols safeguards your SCADA system against unplanned obsolescence

These functions are performed by four kinds of SCADA components:

1. Sensors (either digital or analog) and control relays that directly interface with the managed system.
2. Remote telemetry units (RTUs). These are small computerized units deployed in the field at specific sites and locations. RTUs serve as local collection points for gathering reports from sensors and delivering commands to control relays.
3. SCADA master units. These are larger computer consoles that serve as the central processor for the SCADA system. Master units provide a human interface to the system and automatically regulate the managed system in response to sensor inputs.
4. The communications network that connects the SCADA master unit to the RTUs in the field.
   

The World’s Simplest SCADA System
The simplest possible SCADA system would be a single circuit that notifies you of one event. Imagine a fabrication machine that produces widgets. Every time the machine finishes a widget, it activates a switch. The switch turns on a light on a panel, which tells a human operator that a widget has been completed.

Obviously, a real SCADA system does more than this simple model. But the principle is the same. A full-scale SCADA system just monitors more stuff over greater distances.

Let’s look at what is added to our simple model to create a fullscale SCADA system:

Data Acquisition
First, the systems you need to monitor are much more complex than just one machine with one output. So a real-life SCADA system needs to monitor hundreds or thousands of sensors.
Some sensors measure inputs into the system (for example, water flowing into a reservoir), and some sensors measure outputs (like valve pressure as water is released from the reservoir). Some of those sensors measure simple events that can be detected by a straightforward on/off switch, called a discrete input (or digital input). For example, in our simple model of the widget fabricator, the switch that turns on the light would be a discrete input. In real life, discrete inputs are used to measure simple states, like whether equipment is on or off, or tripwire alarms, like a power failure at a critical facility.

Some sensors measure more complex situations where exact measurement is important. These are analog sensors, which can detect continuous changes in a voltage or current input. Analog sensors are used to track fluid levels in tanks, voltage levels in batteries, temperature and other factors that can be measured in a continuous range of input. For most analog factors, there is a normal range defined by a bottom and top level. For example, you may want the temperature
in a server room to stay between 60 and 85 degrees Fahrenheit. If the temperature goes above or below this range, it will trigger a threshold alarm. In more advanced systems, there are four threshold alarms for analog sensors, defining Major Under, Minor Under, Minor Over and Major Over alarms.

Data Communication
In our simple model of the widget fabricator, the “network” is just the wire leading from the switch to the panel light. In real life, you want to be able to monitor multiple systems from a
central location, so you need a communications network to transport all the data collected from your sensors.

Early SCADA networks communicated over radio, modem or dedicated serial lines. Today the trend is to put SCADAdata on Ethernet and IP over SONET. For security reasons, SCADA data should be kept on closed LAN/WANs without exposing
sensitive data to the open Internet.

Real SCADA systems don’t communicate with just simple electrical signals, either. SCADA data is encoded in protocol format. Older SCADA systems depended on closed proprietary protocols, but today the trend is to open, standard protocols and protocol mediation.

Sensors and control relays are very simple electric devices that can’t generate or interpret protocol communication on their own. Therefore the remote telemetry unit (RTU) is needed to
provide an interface between the sensors and the SCADA network. The RTU encodes sensor inputs into protocol format and forwards them to the SCADA master; in turn, the RTU receives control commands in protocol format from the master and transmits electrical signals to the appropriate control relays.

Data Presentation
The only display element in our model SCADA system is the light that comes on when the switch is activated. This obviously won’t do on a large scale — you can’t track a lightboard of a thousand separate lights, and you don’t want to pay someone simply to watch a lightboard, either.

A real SCADA system reports to human operators over a specialized computer that is variously called a master station, an HMI (Human-Machine Interface) or an HCI (Human- Computer Interface).

The SCADA master station has several different functions. The master continuously monitors all sensors and alerts the operator when there is an “alarm” — that is, when a control factor is operating outside what is defined as its normal operation. The master presents a comprehensive view of the entire managed system, and presents more detail in response to user requests. The master also performs data processing on information gathered from sensors — it maintains report logs and summarizes historical trends.

An advanced SCADA master can add a great deal of intelligence and automation to your systems management, making your job much easier.

Control
Unfortunately, our miniature SCADA system monitoring the widget fabricator doesn’t include any control elements. So let’s add one. Let’s say the human operator also has a button on his control panel. When he presses the button, it activates a switch on the widget fabricator that brings more widget parts into the fabricator.

Now let’s add the full computerized control of a SCADA master unit that controls the entire factory. You now have a control system that responds to inputs elsewhere in the system. If the machines that make widget parts break down, you can slow down or stop the widget fabricator. If the part fabricators are running efficiently, you can speed up the widget fabricator.

If you have a sufficiently sophisticated master unit, these controls can run completely automatically, without the need for human intervention. Of course, you can still manually override the automatic controls from the master station.

In real life, SCADA systems automatically regulate all kinds of industrial processes. For example, if too much pressure is building up in a gas pipeline, the SCADAsystem can automatically open a release valve. Electricity production can be adjusted to meet demands on the power grid. Even these real-world examples are simplified; a full-scale SCADA system can adjust the managed system in response to multiple inputs.

1. The process/system/machinery you want to monitor a control — this can be a power plant, a water system, a network, a system of traffic lights, or anything else.
2. A network of intelligent devices that interfaces with the first system through sensors and control outputs. This network, which is the SCADA system, gives you the ability to measure and control specific elements of the first system.
   

You can build a SCADA system using several different kinds of technologies and protocols. This white paper will help you evaluate your options and decide what kind of SCADA system is best for your needs.

Where is SCADA Used?
You can use SCADA to manage any kind of equipment. Typically, SCADA systems are used to automate complex industrial processes where human control is impractical — systems where there are more control factors, and more fast-moving control factors, than human beings can comfortably manage.

Around the world, SCADA systems control:

• Electric power generation, transmission and distribution: Electric utilities use SCADA systems to detect current flow and line voltage, to monitor the operation of circuit breakers, and totake sections of the power grid online or offline.
• Water and sewage: State and municipal water utilities use SCADA to monitor and regulate water flow, reservoir levels, pipe pressure and other factors.
• Buildings, facilities and environments: Facility managers use SCADA to control HVAC, refrigeration units, lighting and entry systems.
• Manufacturing: SCADA systems manage parts inventories for just-in-time manufacturing, regulate industrial automation and robots, and monitor process and quality control.
• Mass transit: Transit authorities use SCADA to regulate electricity to subways, trams and trolley buses; to automate traffic signals for rail systems; to track and locate trains and buses; and to control railroad crossing gates.
• Traffic signals: SCADA regulates traffic lights, controls traffic flow and detects out-of-order signals.
  

As I’m sure you can imagine, this very short list barely hints at all the potential applications for SCADA systems. SCADA is used in nearly every industry and public infrastructure project — anywhere where automation increases efficiency. What’s more, these examples don’t show how deep and complex SCADA data can be. In every industry, managers need to control multiple factors and the interactions between those factors. SCADA systems provide the sensing capabilities and the computational power to track everything that’s relevant to your operations.

What’s the Value of SCADA to You?
Maybe you work in one of the fields I listed; maybe you don’t. But think about your operations and all the parameters that affect your bottom-line results:
• Does your equipment need an uninterrupted power supply and/or a controlled temperature and humidity environment?
• Do you need to know — in real time — the status of many different components and devices in a large complex system?
• Do you need to measure how changing inputs affect the output of your operations?
• What equipment do you need to control, in real time, from a distance?
• Where are you lacking accurate, real-time data about key processes that affect your operations?

Real-Time Monitoring and Control Increases Efficiency and Maximizes Profitability
Ask yourself enough questions like that, and I’m sure you can see where you can apply a SCADA system in your operations. But I’m equally sure you’re asking “So what?” What you really want to know is what kind of real-world results can you expect from using SCADA.

Here are few of the things you can do with the information and control capabilities you get from a SCADA system:
• Access quantitative measurements of important processes, both immediately and over time
• Detect and correct problems as soon as they begin
• Measure trends over time
• Discover and eliminate bottlenecks and inefficiencies
• Control larger and more complex processes with a smaller, less specialized staff.

A SCADA system gives you the power to fine-tune your knowledge of your systems. You can place sensors and controls at every critical point in your managed process (and as SCADA technology improves, you can put sensors in more and more places). As you monitor more things, you have a more detailed view of your operations — and most important, it’s all in real time.

So even for very complex manufacturing processes, large electrical plants, etc., you can have an eagle-eye view of every event while it’s happening — and that means you have a knowledge base
from which to correct errors and improve efficiency. With SCADA, you can do more, at less cost, providing a direct increase in profitability.

The whole box is acoustically and electromagnetically screened. A 3 core shielded cable brings the signal to the rest of the circuit and to the power supply (+/- 15V). The SB140 diodes are Schottky type and pin 8 (substrate) of the IC should be connected to ground.

Since then, we have many observations of our Solar System neighbors, first with telescopes and, after the opening of the Space Age, with orbiting spacecraft, flyby, probe, and lander missions. Nowhere else in the diversified and imaginative programs of NASA and other space agencies from different nations has there been such a plethora of observational and scientific triumphs as the exploration of the planets and the Cosmos beyond.

Most of the same instruments that survey the electromagnetic spectrum (EM) around Earth have been the principal tools for exploring our planetary associates and beyond; searching well into outer space at stars and other members of the Universe. Here is a list of remote sensing methods using EM spectral measurements that have provided exceptional information about planetary surfaces, atmospheres, and, indirectly, interiors:

METHOD	EM SPECTRUM	INFORMATION	INTERPRETATION	MISSION
Gamma-Ray Spectroscopy	Gamma rays	Gamma spectrum	K, U, Th Abundances	Apollo 15, 16: Venera
X-ray Fluorescence spectrometry	X-rays	Characteristic Wavelengths	Surface mineral/ chemical comp.	Apollo; Viking Landers
Ultraviolet Spectrometry	UV	Spectrum of Reflected sunlight	Atmospheric Composition: H,He,CO2	Mariner; Pioneer; voyager
Photometry	UV, Visible	Albedo	Nature of Surface; Composition	Earth Telescopes; Pioneer
Multispectral Imagers	UV, Visible, IR	Spectral and Spatial	Surface Features; Composition	On most missions
Reflectance Spectrometers	Visible, IR	Spectral intensities of reflected solar radiation	Surface Chemistry; mineralogy; processes	Telescopes; Apollo
Laser Altimeter	Visible	Time delay between emitted and reflected pulses	Surface Relief	Apollo 15,16,17
Polarimeter	Visible	Surface Polarization	Surface Texture; Composition	Pioneer; Voyager
Infrared Radiometer (includes scanners)	Infrared	Thermal radiant intensities	Surface and atmospheric temperatures; compos.	Apollo; Mariner; Viking; Voyager
Microwave Radiometer	Microwave	Passive microwave emission	Atmosphere/Surface temperatures; structure	Mariner; Pioneer Venus
Bistatic Radar	Microwave	Surface reflection profiles	Surface Heights; roughness	Apollo 14,15,16; Viking
Imaging Radar	Microwave	Reflections from swath	Topography and roughness	Magellan; Earth systems
Lunar Sounder	Radar	Multifrequency Doppler Shifts	Surface Profiling and imaging; conductivity	Apollo 17
S-Band Transponder	Radio	Doppler shift single frequency	Gravity data	Apollo
Radio Occultation	Radio	Frequency and intensity change	Atmospheric density and pressure	Flybys and Orbiters

* Adapted from Billy P. Glass, Introduction to Planetary Geology, 1982, Cambridge University, Press

This list is incomplete but is still highly representative. The exploration of the planets, while dominated by remote sensing devices, is also supported by some non-remote sensing methods. Chief among these is landing astronauts on the Moon to observe first hand, deploy instruments, and collect samples. Landers have set down on other planetary bodies as well. So far in the study of stars and galaxies, the methods used have been entirely remote sensing, as will be evident in the Section 20 review of Cosmology.

The Command and Service Module on the Apollo lunar missions carried a complement of remote sensors and other instruments including alpha-particle spectrometers, mass spectrometers, magnetometers, far UV spectrometers, scintillometers, and others designed to measure geochemical and geophysical properties. The astronauts also deployed, on the surface, instruments for specific studies. Among these were seismometers, magnetometers, gravimeters, solar wind gauges, cosmic-ray detectors, heat flow probes, and laser ranging retroreflectors. However, in retrospect, sensors that produce images, especially photographs and similar items, have provided the most direct and readily interpretible sets of data, and will continue to be a mainstay of future missions.

While remote sensing, especially in the optical or visible segment of the EM spectrum, is a mainstay in planetary studies, the resulting data still need to be interpreted. The new observations of a planet's or moon's surface tend to reveal exotic features which at first seem alien to those who live on Earth. Yet the very familiarity of the Earth to these observers is often the key element in explaining extra-terrestrial features, since Earth's surface has been well explored and documented visually. The Earth then is the "frame of reference" that commonly provides features resembling those on other planetary bodies; and, much is normally known about the mode of origin and development of these features. This approach has been termed "Comparative Planetology". As an example of how one proceeds in identifying and describing a geological feature on another planet in terms of a terrestrial counterpart, consider these two views of channels on Mars and then a similar set of channels on the Earth (in Africa):

The Chad volcano has been studied in the field, so that the role of running water in carving out the channels shown (they tend to follow fractures) is well documented. Note the similarity in morphology to the two martian sets of channels. This close resemblance illustrates the type of argument planetologists use to explain martian channels: those channels look like terrestrial channels - they probably have similar origins (this still is inference rather than firm proof).

Before proceeding, it may be helpful to you to visit and browse a website that deals with (mostly NASA's) Solar System programs - past, present, and future. Check, too, the Nine Planets and Solar View websites that list most of the spacecraft sent to other planets and solar system objects. To see a large collection of images of the nine planets, go to JPL's Photojournal website, and click on the planet of interest. Then check out one of JPL's movies. Access through the JPL Video Site, then follow the pathway Format-->Video -->Search to bring up the list that includes "Interplanetary Superhighway", July 17, 2002. To start it, once found, click on the blue RealVideo link.

If the two stations have turned on their transmitters but are at a pause when no program material is being transmitted, then the spectrum would show just two "lines", like the two gray vertical lines on the graph below. The spectrum shows the relative power at different frequencies. If a station transmits music, then power is tansmitted at other frequencies besides the central line. This is true whenever we transmit any kind of useful information; the spectrum looks something like the black lines. Notice that the two stations are spaced in frequency to avoid interfering with each other.


A radar is like a radio station, but it has a receiver that picks up radio waves reflected from objects (targets). Just as the music changes the spectrum of the radio station, the traget can change the spectrum of the radar signal.When a simple target reflects the transmitted signal, one additional frequency is introduced into the spectrum by the target, depending upon its motion. If the target is moving away from the radar, then the wave front that has just reflected from the target has done so farther away from the radar than the previous one, and so it takes longer to get to the receiver than the previous one. Thus the receiver gets fewer wave fronts in a given time than the tranmitter makes, and so the change downward in frequency as shown on the spectrum.


Although a radio station transmits continously, a radar can transmit short bursts of waves. It can then receive waves when it is not transmitting. Since waves take longer to return from targets that are farther away, the radar can measure the distances to various targets. In the diagram below, one sees that as time increases, the waves get further from the transmitter. They take longer to get to target 2 than 1, and also longer to return.

Since the INS8048 series microprocessors are single-chip, multiple I/O line, high speed devices designed as efficient controllers, the capacity to interface with analog peripherals is obvious. That the conversion be fast, inexpensive and easily expanded to accommodate a number of I/O devices is desirable.


The INS8048 is a self-contained, 8-bit processor in a 40-pin dual-in-line package. It contains its own system timing, control logic and memory. All parts contain RAM (64, 128, 256 bytes) and offer the option of on-board ROM (1k, 2k, 4k depending on part). It provides extensive bit-handling capabilities, 97 instructions, and offers easy expansion for I/O and memory. The ADC0833 A/D converter is an 8-bit successive-approximation device with serial I/O and conversion time of 25 ms.

This family of converters offers various configurations of multiplexed analog inputs which can be software programmed as single-ended, or as differential inputs, or both. Single-ended inputs are referenced to a common pin which is either referred to analog ground or to a fixed reference voltage. Like the INS8048 family, a single 5V power supply is all that is needed. The inputs will accept a 0V-5V range. No zero adjust is necessary. It is compatible with TTL and MOS at both input and output. The output can be selected as either MSB or LSB first. Visit Page