Lab

Recommended Tools

In addition to the resources that the course provides, students may find it useful to obtain the tools below:

  • wire cutter
  • wire stripper
  • needle nose pliers
  • screwdrivers
  • hex set (ball ends)
  • electrical tape
  • small scissors
  • a small file

Lab Resources

The Srivastava Senior Design Lab (2070 ECEB) is dedicated to ECE 445 usage. This lab provides you access to a vast array of lab equipment, hardware, and software for your use in developing and implementing your senior design project. In addition, course staff will make themselves available in this lab during their office hours to provide guidance on your project throughout the semester. It is our intention that this laboratory space provides you and your team with all the tools you would need to develop and test your project (within reason!). If there is something that you require in the lab to complete your project that does not exist in the lab, talk to your TA and we will see if we can remedy the situation.

Lab Bench Reservations

If and when the semester gets so busy that finding a lab bench to work at becomes difficult, please make use of the Lab Bench Reservation System in PACE. Reserving a lab bench will guarantee priority access to that bench, even when the lab is busy. To use the tool, after authenticating in PACE, you will see a page with a title "Signup for lab bench" with some text and a large table below that. The table shows the schedule for each bench on a given day (use the orange arrows or "Go To Date" text box to see a different day).  You make your reservation by simply clicking in a grid cell in the table, which will turn the box green. Click on it again to un-reserve the bench (and the box will turn white again).  Benches that are already reserved by another group will be denoted with a yellow box (you can hover your mouse over a yellow box to find out what group has reserved the bench).

A few ground rules:

  1. You may use a lab bench (a) during a time for which you have it reserved or (b) any time during which it is not reserved in the system (on a first-come-first-served basis). However, if you are working at a bench that is unreserved and somebody reserves it using the online system, the group with the reservation gets the lab bench.
  2. There is a limit on the amount of time for which you can reserve benches in 2070 ECEB.  The limit is currently a total of 4 hours of total bench time in the lab per group per day (e.g., 2 hours at Bench A and 2 hours at Bench B would max out your team's reservations for the day).  While this may seem restrictive, keep in mind that the course serves more than 60 groups in a typical semester and the lab has only 16 benches.  Also keep in mind that you can work at a bench if it is unreserved.
  3. Some lab benches have specialized equipment at them, such as digital logic analyzers.  Try to reserve the lab bench that has the equipment that you need.
  4. Cancel reservations that you will not need as soon as possible to give other groups a chance to reserve the lab bench.  You can cancel a reservation up to 1 hour before time and not have it count against your daily allotment.
  5. Conflicts and/or reports of people not following these rules should be sent to your TA with the course faculty in copy.
  6. Above all, be courteous.  Especially near the end of the semester, the lab will be full most of the time and stress will abound.  Clean up the lab bench when you are done with it.  Start and end your sessions on time.  Be patient and friendly to your peers and try to resolve conflicts professionally.  If we notice empty lab benches that have been reserved, we will cancel your reservations and limit your ability to reserve lab benches in the future. Similarly, do not reserve more time than you will need.  If we notice that you are frequently canceling reservations, we will limit your ability to reserve lab benches in the future. Finally, do not try to “game” the system and reserve a bench for 30 minutes every hour for eight hours. We will notice this and revoke your ability to reserve a bench.

Lab Rules

There are two overriding rules of working in the Srivastava Senior Design Lab. First, be safe. Second, be courteous. Lab access will be revoked if you fail to complete the required laboratory safety training by the deadline or if you break any of the lab rules. Specific points and examples of what we expect:

Breaking the rules or exhibiting bad laboratory etiquette will lead to a loss of points and/or revocation of laboratory access.

Lab Equipment Rules

Do not remove any equipment from the lab. Students may not change the connections on equipment without TA approval. Any approved changes that are made should be undone before leaving the lab. If a bench instrument is malfunctioning, a red repair tag should be placed on it and you should notify your TA. This alerts the staff to the problem, and allows the Electronics Services Shop to fix the problem.

When using a piece of laboratory equipment for the first time, please ask a TA for help. If you are inexperienced with a piece of hardware, do not assume that it is broken just because you cannot figure out how to use it. Similarly, if you use a piece of equipment to test your project and the equipment does not perform the way you think it should, do not assume the fault is with the equipment, and do not try again with equipment on another bench. Rather, stop and make absolutely sure the problem is not with your connections or project.

If you break any laboratory equipment, you must tell your TA within 1 business day. Any attempts to conceal breakage will result in an F in the course.

Room Access

The lab room (2070 ECEB) is on the electronic key-card system. The Department automatically adds room access to the building and the lab for all students on the roster. You will need a “prox enanabled” I-Card to swipe into the room. If the door does not open after several attempts, you may need to get a replacement card. Room access is automatically restricted to faculty and TAs during official breaks (i.e., Thanksgiving, Christmas, and Spring Break).

Computer Access

The lab computers are EWS computers and are setup like other Windows-based EWS systems you are familiar with. Standard EWS rules apply to these machines. In particular, please store any/all files you generate on a network drive or in the cloud. The C: drive should not be used for any personal material, since it is unprotected and is available only on the particular machine where it was originally stored. A particular computer may be cleared and reconfigured at any time for maintenance reasons.

In addition to the desktop computers, EWS maintains the printer in the lab. You are free to use it to print documents related to your project, but be aware that this printing counts against your standard print quota.

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.