Project

# Title Team Members TA Documents Sponsor
10 Camera Inventory System for ECE 445 Components
Krish Naik Aparaj
Rohan Harpalani
Rushil Duggal
Sanjana Pingali design_document3.pdf
final_paper1.pdf
photo1.jpg
photo2.heic
presentation1.pdf
proposal2.pdf
video
# Camera Inventory System for ECE 445 Components

Team Members:
- Krish Naik Aparaj (krishn2)
- Rohan Harpalani (rohanhh2)
- Rushil Duggal (rduggal2)

# Problem

The current inventory system for students to borrow parts for the ECE 445 Senior Design project is very manual and tedious for the TA's. It requires the student providing their NetID and physically showing the TA's which components they are taking and having the TA's manually record who took what part. This same process has to be repeated at the end of the semester when students have to return their parts and when certain parts aren't returned, it becomes the TA's responsibility to try to track the student down to get the parts back. There are also security concerns in terms of taking parts and not returning them at the semester, ending up in a loss for the ECE department.

# Solution


Our solution plans to eliminate the need for TA’s to be present during the part retrieval and return process. We plan on having the components in a locked box and the components are all tagged with a QR code. For the component retrieval process, the student would have to scan their iCard and then the box would unlock. Once they pick out the components they need, they would scan the QR code to the camera attached to our microcontroller on the box and in the backend, we would store a record of which student took what component. To account for students potentially not scanning components, we would have another camera in the upper corner of the room for security purposes to monitor if the student took any unscanned components. For the returning process, the student would scan their iCard to unlock the box and then scan the components once more to indicate that they are returning the components. In the backend, we would be able to keep track of which student is returning what component. At the end of this, the TA’s can have a report of which students still have components to return, thus automating the process in a secure way.

# Solution Components

## Locked Box
A container to hold the components within and uses a strike lock to securely lock and unlock the box.

## RFID Identifier System

A system where the iCard is read by the RFID system and then stores the student information and also unlocks the box with the components in it.

## PCB + Report Generation

The PCB will incorporate an ESP32 Micrcontroller along with two camera peripherals (one for scanning the components and one for security purposes). The microcontroller will also take information on the student and store that with the component information to create a report for the TA’s to track the components.

## QR Codes and QR Code Scanner

Need to assign each component a unique QR code to scan each item and need to implement code to enable the camera to scan the QR code and identify the item.


# Criterion For Success

A successful inventory system should be able to correctly generate a report every time a student scans their iCard to open the box and correctly identify either a return or borrow when the student holds the component to the camera. Along with the report, a video recording of the student when either returning or borrowing the component should be stored in the backend for security purposes.

ATTITUDE DETERMINATION AND CONTROL MODULE FOR UIUC NANOSATELLITES

Shamith Achanta, Rick Eason, Srikar Nalamalapu

Featured Project

Team Members:

- Rick Eason (reason2)

- Srikar Nalamalapu (svn3)

- Shamith Achanta (shamith2)

# Problem

The Aerospace Engineering department's Laboratory for Advanced Space Systems at Illinois (LASSI) develops nanosatellites for the University of Illinois. Their next-generation satellite architecture is currently in development, however the core bus does not contain an Attitude Determination and Control (ADCS) system.

In order for an ADCS system to be useful to LASSI, the system must be compliant with their modular spacecraft bus architecture.

# Solution

Design, build, and test an IlliniSat-0 spec compliant ADCS module. This requires being able to:

- Sense and process the Earth's weak magnetic field as it passes through the module.

- Sense and process the spacecraft body's <30 dps rotation rate.

- Execute control algorithms to command magnetorquer coil current drivers.

- Drive current through magnetorquer coils.

As well as being compliant to LASSI specification for:

- Mechanical design.

- Electrical power interfaces.

- Serial data interfaces.

- Material properties.

- Serial communications protocol.

# Solution Components

## Sensing

Using the Rohm BM1422AGMV 3-axis magnetometer we can accurately sense 0.042 microTesla per LSB, which gives very good overhead for sensing Earth's field. Furthermore, this sensor is designed for use in wearable electronics as a compass, so it also contains programable low-pass filters. This will reduce MCU processing load.

Using the Bosch BMI270 3-axis gyroscope we can accurately sense rotation rate at between ~16 and ~260 LSB per dps, which gives very good overhead to sense low-rate rotation of the spacecraft body. This sensor also contains a programable low-pass filter, which will help reduce MCU processing load.

Both sensors will communicate over I2C to the MCU.

## Serial Communications

The LASSI spec for this module requires the inclusion of the following serial communications processes:

- CAN-FD

- RS422

- Differential I2C

The CAN-FD interface is provided from the STM-32 MCU through a SN65HVD234-Q1 transceiver. It supports all CAN speeds and is used on all other devices on the CAN bus, providing increased reliability.

The RS422 interface is provided through GPIO from the STM-32 MCU and uses the TI THVD1451 transceiver. RS422 is a twisted-pair differential serial interface that provides high noise rejection and high data rates.

The Differential I2C is provided by a specialized transceiver from NXP, which allows I2C to be used reliably in high-noise and board-to-board situations. The device is the PCA9615.

I2C between the sensors and the MCU is provided by the GPIO on the MCU and does not require a transceiver.

## MCU

The MCU will be an STM32L552, exact variant and package is TBD due to parts availability. This MCU provides significant processing power, good GPIO, and excellent build and development tools. Firmware will be written in either C or Rust, depending on some initial testing.

We have access to debugging and flashing tools that are compatible with this MCU.

## Magnetics Coils and Constant Current Drivers

We are going to wind our own copper wire around coil mandrels to produce magnetorquers that are useful geometries for the device. A 3d printed mandrel will be designed and produced for each of the three coils. We do not believe this to be a significant risk of project failure because the geometries involved are extremely simple and the coil does not need to be extremely precise. Mounting of the coils to the board will be handled by 3d printed clips that we will design. The coils will be soldered into the board through plated through-holes.

Driving the inductors will be the MAX8560 500mA buck converter. This converter allows the MCU to toggle the activity of the individual coils separately through GPIO pins, as well as good soft-start characteristics for the large current draw of the coils.

## Board Design

This project requires significant work in the board layout phase. A 4-layer PCB is anticipated and due to LASSI compliance requirements the board outline, mounting hole placement, part keep-out zones, and a large stack-through connector (Samtec ERM/F-8) are already defined.

Unless constrained by part availability or required for other reasons, all parts will be SMD and will be selected for minimum footprint area.

# Criterion For Success

Success for our project will be broken into several parts:

- Electronics

- Firmware

- Compatibility

Compatibility success is the easiest to test. The device must be compatible with LASSI specifications for IlliniSat-0 modules. This is verifiable through mechanical measurement, board design review, and integration with other test articles.

Firmware success will be determined by meeting the following criteria:

- The capability to initialize, configure, and read accurate data from the IMU sensors. This is a test of I2C interfacing and will be tested using external test equipment in the LASSI lab. (We have approval to use and access to this equipment)

- The capability to control the output states of the magnetorquer coils. This is a test of GPIO interfacing in firmware.

- The capability to move through different control modes, including: IDLE, FAULT, DETUMBLE, SLEW, and TEST. This will be validated through debugger interfacing, as there is no visual indication system on this device to reduce power waste.

- The capability to self-test and to identify faults. This will be validated through debugger interfacing, as there is no visual indication system on this device to reduce power waste.

- The capability to communicate to other modules on the bus over CAN or RS422 using LASSI-compatible serial protocols. This will be validated through the use of external test equipment designed for IlliniSat-0 module testing.

**Note:** the development of the actual detumble and pointing algorithms that will be used in orbital flight fall outside the reasonable scope of electrical engineering as a field. We are explicitly designing this system such that an aerospace engineering team can develop control algorithms and drop them into our firmware stack for use.

Electronics success will be determined through the successful operation of the other criteria, if the board layout is faulty or a part was poorly selected, the system will not work as intended and will fail other tests. Electronics success will also be validated by measuring the current consumption of the device when operating. The device is required not to exceed 2 amps of total current draw from its dedicated power rail at 3.3 volts. This can be verified by observing the benchtop power supply used to run the device in the lab.