Manufacturer of the i-STAT System, a handheld blood analyzer for point-of-care testing, and the US distributor for Piccolo Xpress. At Abbott, we help people live fully with our life-changing technology. We keep your heart healthy, nourish your body at every stage of life, help you feel and move better, and bring you information, medicines and breakthroughs to manage your health. Dear Twitpic Community - thank you for all the wonderful photos you have taken over the years. We have now placed Twitpic in an archived state.

The EV3 has four input ports for connecting sensors and other devices (likesensor multiplexers or motor controllers). If you are trying to use somethingthat plugs into one of those ports, you are in the right place.

1. Abbott USB Data Cable Installation is a Shareware software in the category Miscellaneous developed by Abbott Labs. It was checked for updates 63 times by the users of our client application UpdateStar during the last month. The latest version of Abbott USB Data Cable Installation is currently unknown.
2. Links which take you out of Abbott worldwide websites are not under the control of Abbott, and Abbott is not responsible for the contents of any such site or any further links from such site. Abbott is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement of the linked site by Abbott.

Supported Sensors¶

This is a list of sensors that currently have drivers available in the ev3devkernel. The Part Number column links to the vendor website. The Namecolumn links to the sensor’s entry in Appendix A.

Unsupported Sensors¶

One of the goals of ev3dev is to support as many sensors as possible. In fact,even if a manufacturer’s documentation says that a device does not work withthe EV3, chances are it will work with ev3dev.

If you have a sensor that is not supported yet, let us know about it byopening an issue on GitHub. For many sensors adding a driver is trivial -even if you are not a “kernel hacker” or a “c programmer”. For the non-trivialsensors, see the contributing page for information on how to write a driveror how to donate hardware to someone who will.

Using Sensors¶

Automatic Detection¶

The EV3 has “smart” sensor ports that can identify most sensors. Beware!Full automatic detection works on EV3 only. And even on EV3, some sensors cannotbe automatically detected. See notes below in the table of supported sensors.

For sensors that cannot be automatically detected, you can manually controlthe input port mode. Read more about it on Input / Output Ports page.

On FatcatLab’s EVB, EV3/Analog and EV3/UART sensors can be automatically detected.For NXT/Analog sensors, you must manually set the mode. Most NXT/I2C sensors shouldbe automatically detected.

On BrickPi, BrickPi+ and BrickPi3, sensors cannot be automatically detected atall. You must manually configure the input ports for all sensors.

On PiStorms, detection of EV3/UART, EV3/Analog and NXT/I2C sensors issemi-automatic. If you put the input port into ev3-uart, ev3-analog,or i2c-thru mode, the specific type of sensor will be automatically detected(assuming it is a LEGO compatible sensor). So you usually don’t have to write tothe set_device attribute of the port for these sensors.

MINDSTORMS Compatible Sensors¶

Most of the supported sensors are designed to work with LEGO MINDSTORMS. Thesesensors use the LEGO sensor class. You can find thesein sysfs at /sys/class/lego-sensor/. The sensors have modes that selectwhat type of data is read from the sensor. Generally, you will select a modeand then read the data value from the sensor. Follow the link above for moredetails.

Other Sensors and Advanced Usage¶

Many sensors that were not specifically designed for LEGO MINDSTORMS can be usedwith ev3dev too. You can read more about the “Other” sensor types below. Also,some MINDSTORMS compatible sensor may have advanced features that are notaccessible using the lego-sensor class.

When using sensors this way, often automatic detection will not work correctly,therefore it is usually best to manually select the mode of input port (e.g.other-i2c or other-uart).

For more information on using I2C sensors, check out Appendix C: I2C Devices.

Types of Sensors¶

When dealing with sensors in ev3dev, it is useful to know how it communicateswith the EV3 brick. There are three basic kinds of communication that the inputports can use to get information from the sensor, Analog Sensors, I2C Sensorsand UART Sensors, plus one special type for LEGO NXT Color Sensors.

Analog Sensors¶

These are the simplest type of sensor. The measured value is converted to avoltage (0-5VDC) that is read by the EV3.

EV3/Analog Sensors¶

These are sensors that were designed specifically for the EV3 and will not workon the NXT because the pinout is different. They contain an ID resistor so thatthe EV3 can tell different types of sensors apart. The actual analog value ismeasured on pin6.

NXT/Analog Sensors¶

These sensors are designed for the NXT, but also work on the EV3. The EV3 cannotdifferentiate between most of these sensors though, so you have to tell itwhich one your have or just use the generic driver.

RCX/Analog Sensors¶

RCX sensors also fall into this category, but do not work with the EV3 - atleast not with the converter cable described in the NXT Hardware Developerskit. This is due to a difference in the input port pins between the EV3 andthe NXT. If someone wants design a new converter cable, we could make them work.

WeDo/Analog Sensors¶

WeDo sensors are also analog sensors. They are actually electrically similar toEV3/Analog sensors (require 5V power and have ID resistor). Currently, we onlysupport WeDo sensors attached to a WeDo hub, but if someone would like to designa cable and modify the wedo-sensor and lego-ports drivers, we couldeasily make them work with the input ports on the EV3.

Drivers Abbott Labs (adc) Port Devices Gigabit

LEGO NXT Color Sensors¶

The LEGO NXT Color Sensor is in a class of its own. It uses a hybrid of analogand (non-standard) digital communications. The NXT Color Sensor is not usableat this point in time. We can detect it with the auto-detect, but we don’thave a driver for it yet.

I2C Sensors¶

I2C sensors are sensors that communicate with the intelligent brick via theI2C protocol. In the NXT documentation, they are referred to a “digital”sensors. These sensors can be sorted into two categories.

NXT/I2C Sensors¶

These are sensors designed using LEGO’s guidelines for NXT digital sensors.NXT/I2C sensors can be automatically detected because they contain vendor andproduct IDs at specific I2C registers.

Other/I2C Sensors¶

These can be any off-the-shelf I2C device or 3rd party sensors that are designedfor LEGO MINDSTORMS, but do not follow the guidelines of NXT/I2C sensors.

UART Sensors¶

The EV3 has a UART transceiver connected to each input port that canbe used to communicate with many devices using this widely used standard.

EV3/UART Sensors¶

These is a new type of sensor that is designed specifically for the EV3 (theydon’t work with the NXT). These sensors are a bit “smarter” in that in additionto sending the data of what they measure, they also send information about theircapabilities. This means that any new EV3/UART sensors should “just work” withoutus having to write new drivers.

Other/UART Sensors¶

In addition to sensors designed to work with EV3, any UART device can be connected.But, be careful of voltage levels. The EV3 uses 3.3V I/O. It is safe to connectother devices that use 3.3V or 5V I/O. But, don’t connect anything with highervoltage!

The lego-sensor Subsytem¶

The lego-sensor class provides a uniform interface for using most of thesensors available for the EV3. The various underlying device drivers willcreate a lego-sensor device for interacting with the sensors.

Sensors are primarily controlled by setting the mode and monitored byreading the value<N> attributes. Values can be converted to floatingpoint if needed by value<N> / 10.0 ^ decimals.

Identifying sensors¶

Since the name of the sensor<N> device node does not correspond to theport that a sensor is plugged in to, you must look at the addressattribute if you need to know which port a sensor is plugged in to. However,if you don’t have more than one sensor of each type, you can just look for amatching driver_name. Then it will not matter which port a sensor isplugged in to - your program will still work.

Sysfs¶

Sensors can be found at /sys/class/lego-sensor/sensor<N>, where <N>is incremented each time a sensor is loaded.

Note

The number <N> is not related to the port address.

Events¶

In addition to the usual add and remove events, the kernel changeevent is emitted when mode or poll_ms is changed. The value<N>attributes change too rapidly to be handled this way and therefore do nottrigger any uevents.

Sensor Modules¶

The sensor drivers are implemented in the following modules:

EV3/Analog¶

The ev3-analog-sensor module provides all of the drivers for EV3/Analogsensors.

You can a list of the the devices implemented by this module by reading thedriver_names attribute in the /sys/bus/lego/drivers/ev3-analog-sensor/.

EV3/UART¶

The ev3-uart-sensor-ld module is a tty line discipline that runs ontop of a tty. It listens for the information data that is sent from EV3/UARTsensors. When it receives valid data, it negotiates with the sensor, tellingthe sensor to enter data sending mode.

This line discipline has been assigned the number 29. To attach this linediscipline to a tty, run ldattach29/dev/tty<N> where <N> is the nameof the tty you want to connect to.

Note

This driver works with any tty, which means the sensor does notnecessarily have to be plugged into one of the input ports on the EV3.

EV3/UART sensors do not require individual driver implementations like othertypes of sensors. Instead, all of the needed info to sent from the sensor ina common format. As a result, the name returned by the driver_nameattribute may not be a real driver name. For well-known sensors (the LEGOEV3 sensors and FatcatLab sensors) it will return a name like lego-ev3-color.For unknown sensors it returns ev3-uart-<N>, where <N> is the type idof the sensor.

The ev3-uart-sensor module provides all of the drivers for EV3/UARTsensors. This module is only used on devices that can’t use the linediscipline.

You can a list of the the devices implemented by this module by reading thedriver_names attribute in the /sys/bus/lego/drivers/ev3-uart-sensor/.

NXT/Analog¶

The nxt-analog-sensor module provides all of the drivers for NXT/Analogsensors. These drivers scale the analog voltage read from the sensor to auseful value.

You can a list of the the devices implemented by this module by reading thedriver_names attribute in the /sys/bus/lego/drivers/nxt-analog-sensor/.

NXT/I2C¶

The nxt-i2c-sensor module provides all of the drivers for NXT/I2C sensors.

Note

These parameters can be changed at runtime by writing to/sys/module/nxt_i2c_sensor/parameters/<parameter>.

Drivers Abbott Labs (adc) Port Devices List

You can a list of the the devices implemented by this module by reading thedriver_names attribute in the /sys/bus/lego/drivers/nxt-i2c-sensor/.

Drivers Abbott Labs (adc) Port Devices Inc

Drivers Abbott Labs (adc) Port Devices For Sale

Drivers Abbott Labs (adc) Port Devices Inc

Drivers Abbott Labs (adc) Port Devices Phone Number

Drivers Abbott Labs (adc) Port Devices St Lucie