Ethical Guidelines

University of Illinois trained engineers are the best and most highly sought in the world. Our graduates are superbly trained, highly competent, and creative. This, however, is not enough. Our engineers must also be trusted to conduct themselves according to the highest ethical standards. All teams must address ethical considerations in their projects. This requirement has two parts.

First, there is a stringent Code of Ethics published by professional societies, such as IEEE and ACM. The power of these Codes of Ethics is to provide guidance to engineers in decision making and to lend the weight of the collective community of engineers to individuals taking a stand on ethical issues. Thus the Code of Ethics both limits the professional engineer and empowers the professional engineer to stand firm on fundamental ethical bedrock. All teams must read the IEEE code and ACM code and comment on any sections of the code that bear directly on the project.

Second, we expect our students to have personal standards of conduct consistent with the IEEE and ACM Codes of Ethics, but also beyond it. That is, there are areas of ethics not addressed by these Codes that the engineer may consider in taking on projects or jobs or making other professional decisions. These are personal standards and choices. In the context of the class, there are no right or wrong answers here. Our students simply need to demonstrate that they are thinking deeply about their own decisions and the consequences of those decisions. We encourage our students to consider the wider impact of their projects and address any concerns raised by potential uses of the project. Students should ask themselves, "Would I be comfortable having my name widely attached to this project? Do I want to live in a society where this product is available or widely used? Would I be proud of a career dominated by the decision making demonstrated here?" Remember that UIUC engineers have a long history of inventions that really has changed the world.

If the students feel that these Codes of Ethics does not directly bear on their project and that there are no other reasonable concerns, they should not invent issues where there are none. Students will still be expected to be familiar with the IEEE Code of Ethics and ACM Code of Ethics.

Prosthetic Control Board

Caleb Albers, Daniel Lee

Prosthetic Control Board

Featured Project

Psyonic is a local start-up that has been working on a prosthetic arm with an impressive set of features as well as being affordable. The current iteration of the main hand board is functional, but has limitations in computational power as well as scalability. In lieu of this, Psyonic wishes to switch to a production-ready chip that is an improvement on the current micro controller by utilizing a more modern architecture. During this change a few new features would be added that would improve safety, allow for easier debugging, and fix some issues present in the current implementation. The board is also slated to communicate with several other boards found in the hand. Additionally we are looking at the possibility of improving the longevity of the product with methods such as conformal coating and potting.

Core Functionality:

Replace microcontroller, change connectors, and code software to send control signals to the motor drivers

Tier 1 functions:

Add additional communication interfaces (I2C), and add temperature sensor.

Tier 2 functions:

Setup framework for communication between other boards, and improve board longevity.

Overview of proposed changes by affected area:

Microcontroller/Architecture Change:

Teensy -> Production-ready chip (most likely ARM based, i.e. STM32 family of processors)

Board:

support new microcontroller, adding additional communication interfaces (I2C), change to more robust connector. (will need to design pcb for both main control as well as finger sensors)

Sensor:

Addition of a temperature sensor to provide temperature feedback to the microcontroller.

Software:

change from Arduino IDE to new toolchain. (ARM has various base libraries such as mbed and can be configured for use with eclipse to act as IDE) Lay out framework to allow communication from other boards found in other parts of the arm.