Elements of Robotics

Course Description

Elements of Robotics is an introductory course in the multidisciplinary field of robotics with analysis and design of robots and robotic tasks. It includes class projects in robot programming and design. UWF notes that a material and supply fee will be assessed and that a grade of C-minus or better is required in the prerequisites.

Within the SCNS taxonomy, EEL is the Electrical Engineering prefix. The University of West Florida publishes this at 3 semester hours through the Department of Electrical and Computer Engineering, College of Science and Engineering. It is offered at approximately 2 Florida institutions.

⚠ The SCNS title for this number is "Applied Robotics"; UWF publishes it as "Elements of Robotics." The local title suggests fundamentals over application, and the catalog's emphasis on analysis and design alongside class projects points to a course that teaches the mathematics and then builds — rather than a build-first course. Carry a syllabus when transferring.

Robotics is where a student discovers that the hard problem is rarely the robot. Making an arm move is straightforward; making it arrive where it was told, repeatably, in the presence of sensor noise, model error, and a world that does not match the map, is not. The mathematics that makes this tractable is coordinate transformation — homogeneous transforms, forward and inverse kinematics — and it is the part students underestimate because it looks like bookkeeping. It is not; it is the language in which every other robotics problem is stated.

⚠ Note the prerequisite structure: differential equations and a programming course, with no controls requirement. That places this course earlier in a plan than students expect, and it means the control content is introduced rather than assumed. Pairing it with EEL4657 and EEL4657L gives a much stronger foundation.

⚠ The contact-hour figure is derived — the University of West Florida publishes none

UWF's catalog publishes a credit value in semester hours, the college and department, prerequisites, and a description. It does not publish contact hours, a lecture and laboratory split, or terms of offering for any course. It does publish a material and supply fee notice on the minority of courses that carry one — and maintains a separate Material & Supply and Equipment Fees section of the catalog — so the absence of a fee notice on this entry is meaningful, while the fee amount is not published here. Every contact-hour value in a UWF guide in this repository is therefore derived. The figure here applies the standard lecture convention of 15 contact hours per credit, giving 45 hours for a 3-semester-hour course. Confirm the meeting schedule with the department.

Learning Outcomes

Required Outcomes

• Describe robot classifications, configurations, and workspace types.
• Describe robot components: links, joints, actuators, sensors, end effectors.
• Apply coordinate frames and homogeneous transformations.
• Compose and invert transformations between frames.
• Apply the Denavit-Hartenberg convention to assign frames.
• Solve the forward kinematics of a serial manipulator.
• Solve the inverse kinematics of a simple manipulator and identify multiple solutions.
• Compute the Jacobian and relate joint rates to end-effector velocity.
• Identify singularities and explain their practical consequences.
• Describe manipulator dynamics at an introductory level.
• Plan trajectories in joint space and in Cartesian space.
• Describe actuator types and select appropriately for a task.
• Describe robot sensors and their characteristics and limitations.
• Apply basic feedback control to a robot joint.
• Describe mobile robot kinematics and differential drive.
• Describe localisation and mapping concepts at an introductory level.
• Describe path planning and obstacle avoidance methods.
• Program a robot to perform a specified task.
• Apply robot safety practice.
• Design and document a robotic solution to a stated problem.

Optional Outcomes

• Apply computer vision to a robotic task.
• Use a robotics middleware framework such as ROS.
• Describe force control and compliant manipulation.
• Describe machine learning applications in robotics.
• Describe multi-robot coordination.
• Simulate a robot in a physics-based environment.

Major Topics

Required Topics

• Robot classification and configurations
• Robot components and end effectors
• Coordinate frames and homogeneous transformations
• Denavit-Hartenberg parameters
• Forward kinematics
• Inverse kinematics and multiple solutions
• The Jacobian and velocity kinematics
• Singularities
• Introductory manipulator dynamics
• Trajectory planning
• Actuators: motors, servos, and drives
• Sensors: encoders, IMUs, range sensors, vision
• Joint-level feedback control
• Mobile robot kinematics
• Localisation and mapping concepts
• Path planning and obstacle avoidance
• Robot programming
• Robot safety
• Design projects

Optional Topics

• Computer vision for robotics
• ROS and robotics middleware
• Force control and compliance
• Machine learning in robotics
• Multi-robot systems
• Physics-based simulation

Resources & Tools

• Craig, Introduction to Robotics: Mechanics and Control — the most widely adopted text, and the standard treatment of DH parameters and kinematics.
• Spong, Hutchinson and Vidyasagar, Robot Modeling and Control — the common alternative, stronger on control.
• Corke, Robotics, Vision and Control — comes with an excellent free MATLAB and Python toolbox, and is unusually good at building intuition.
• ROS 2 (ros.org) — free and open source; the de facto standard robotics framework in both research and industry, and genuinely worth learning.
• Gazebo and Webots — free physics-based robot simulators; simulate before you damage hardware.
• Python Robotics (github, atsushisakai) — free; readable implementations of path planning and localisation algorithms, and excellent for learning.
• MATLAB Robotics System Toolbox — check UWF's campus licence.
• An inexpensive robot platform — Arduino or Raspberry Pi based kits are cheap, and a small differential-drive robot teaches more about odometry drift in an afternoon than a chapter does.
• ANSI/RIA R15.06 and ISO 10218 — the industrial robot safety standards; ISO/TS 15066 covers collaborative robots. Check UWF Libraries for standards access.
• IEEE Robotics and Automation Society — inexpensive student membership.

Career Pathways

• Electrical engineers — SOC 17-2071; mechanical engineers — SOC 17-2141; robotics genuinely sits between them.
• Robotics engineering — growing, and the field rewards people who can span mechanical, electrical, and software.
• Industrial automation — Florida's manufacturing base, including aerospace and medical device manufacturing, integrates robotic cells.
• Autonomous systems and unmanned vehicles — a significant Northwest Florida sector tied to the naval and Air Force presence: Eglin Air Force Base, NSA Panama City and their contractors work on autonomous air, ground, and undersea systems.
• Defence robotics — Lockheed Martin in Orlando and L3Harris in Melbourne.
• Space robotics — the Space Coast sector.
• Warehouse and logistics automation — a large and rapidly growing employer category, and Florida's distribution sector is substantial.
• Medical and surgical robotics.
• Agricultural robotics — Florida agriculture, particularly citrus and speciality crops, faces persistent labour shortage and is an active application area.
• ⚠ A practical note: robotics roles frequently ask for a portfolio. The class projects in this course are the start of one, so document them properly — video, code, and a written description.

Special Information

⚠⚠ The asterisk in a UWF prerequisite means the course may be taken at the same time

• UWF's catalog marks a concurrent course with an asterisk, defined on the catalog's Course Information page as: "This course may be taken prior to or during the same term."
• ⚠ This is the single most useful piece of notation in the UWF engineering catalog, and it is easy to miss. A prerequisite written without an asterisk must be completed first; one written with an asterisk may be taken in the same term.
• The practical effect is on time to degree. Reading an asterisked prerequisite as a hard prerequisite adds a term to the sequence for no reason, and in a tightly chained major like electrical engineering that error compounds down the whole plan.
• Confirm with an advisor before relying on it, and note that the registration system, not the catalog text, is what actually enforces the rule.

⚠⚠ The prerequisite is mathematics and programming — and the grade condition is C-minus

• UWF publishes: (MAP2302) AND (EEL4834 OR COP3014 OR COP2253 OR COP2334), with a grade of C-minus or better required in the prerequisites.
• ⚠ The C-minus threshold is lower than the C required by several other EEL courses, including EEL3112 and EEL4213. UWF's grade conditions are not uniform across the prefix, and assuming one standard is a mistake worth avoiding.
• Neither branch is asterisked, so both must be complete before enrolling.
• ⚠⚠ No controls course is required, and none is assumed. That makes this course available earlier than students expect — but the control content is necessarily introductory, and students who have taken EEL4657 will get considerably more from the feedback material.
• Linear algebra is used heavily and is not a listed prerequisite. Matrix multiplication, inversion, and rotation matrices are the working tools; refresh them before the term if they are rusty.

⚠ A material and supply fee is assessed for this course

• UWF publishes a fee notice on this entry but not the amount. The amount is in the catalog's separate Material & Supply and Equipment Fees section, and it is charged in addition to tuition.
• ⚠ Budget for it. Laboratory fees are billed with tuition and are not always visible when a student estimates the cost of a term from credit hours alone.
• Check whether the fee covers consumables you would otherwise buy — components, boards, and kits are frequently included, which changes the real cost comparison.

⚠⚠ Where robotics students actually struggle

• Frame assignment, not the algebra. Once frames are assigned correctly the kinematics is mechanical; assigning them wrongly produces an answer that is confidently and completely incorrect, and the error is hard to see.
• ⚠ Draw the frames. Every time. Students who try to do DH parameters in their heads produce sign errors that take hours to find.
• ⚠⚠ Inverse kinematics has multiple solutions, or none. A manipulator can reach the same point in several configurations, and choosing among them — elbow up or down — is a real decision with real consequences for collision and joint limits. Points outside the workspace have no solution at all, and code that assumes one will fail.
• Singularities are not edge cases. At a singularity the Jacobian loses rank and required joint velocities go to infinity — a robot commanded through one moves violently or faults. This is a practical safety matter, not a mathematical curiosity.
• Odometry drifts, without exception. Wheel encoders accumulate error from slip and from imperfect radius estimates, and dead reckoning alone diverges without bound. This is why external references and sensor fusion exist.
• ⚠ Simulation is not reality. Simulators omit friction, backlash, compliance, and latency, and code that works perfectly in Gazebo routinely fails on hardware. Budget time for that gap rather than being surprised by it.

⚠⚠ Robot safety: the machine does not know you are there

• Industrial robots are strong, fast, and have no awareness of people unless explicitly equipped for it. Robot-related injuries and fatalities are documented and occur overwhelmingly during maintenance, teaching, and setup — not during normal automatic operation.
• ⚠⚠ Never enter a robot's workspace while it is energised in automatic mode. Use lockout-tagout, guarding, and light curtains as the laboratory provides them.
• ⚠ The most dangerous moment is running new code for the first time. A sign error in a trajectory sends an arm somewhere unintended at full speed. Test in simulation, then at reduced speed, then at rate.
• Know where the emergency stop is before energising, and keep the teach pendant's enabling device understood rather than merely held.
• Collaborative robots are designed to work near people under ISO/TS 15066, and that is a specific engineered capability — not a property any robot has by default.

Course format and position in the curriculum

• Lecture with problem sets and class projects in robot programming and design, as the catalog specifies.
• Typically taken in the fourth year, although the prerequisites permit it earlier.
• A material and supply fee is assessed, with the amount published separately — consistent with a project-based course using hardware.
• ⚠ Project work takes longer than estimated. Hardware integration is where schedules fail; start early and get something moving badly before trying to make it move well.
• Pairs strongly with EEL4657 and EEL4657L, and with EEL4744C-equivalent microprocessor work.
• UWF publishes no contact hours, lecture and laboratory split, or terms of offering for any course. Confirm the offering pattern with the department.

FE exam relevance

The Fundamentals of Engineering (FE) exam is the first step toward Professional Engineer licensure, and in Florida it is administered under the Florida Board of Professional Engineers. Most students take the FE Electrical and Computer exam in their final year. Licensure matters less in electrical engineering than in civil — the industrial exemption means most electrical engineers in manufacturing and product work never need a PE — but it is required for consulting practice, for sealing designs, and for power and building-systems work, which is exactly where Florida's utility and infrastructure employment sits.

How Florida course levels affect transfer

The first digit of an SCNS number denotes the year of offering, not transferability. Courses at the 1000 and 2000 levels transfer transparently between Florida public institutions, and 3000 to 4000 is unproblematic since both are upper division. The boundary that actually matters is 2000 to 3000, where lower-division credit generally cannot satisfy an upper-division requirement. ⚠ For engineering specifically, ABET-accredited programmes commonly require that upper-division engineering coursework be taken in residence, so transferability of the credit and applicability to the degree are separate questions.

EEL4663 is 3 semester hours at the University of West Florida. Because the SCNS title ("Applied Robotics") and the local title differ, students transferring credit should carry a syllabus.