Saturday, February 6, 2016

This week in EVT EE

(note: this post was written by a new member without a sense of humor)

Preparations to command someone else's magical metal box to use electrons from large energy boxes to spin something.

IMG_20160130_151240.jpg
caption: magical metal box; alt-text: Sevcon motor coftroller
IMG_20160130_151952.jpg
{caption: Magical metal box's life support system; alt-text: 12-volt power supply}
IMG_20160130_151728.jpg
{caption: a smaller version of our large energy boxes; alt-text: The real ones are much nicer, I'm told}
IMG_20160203_203524.jpg
{caption: DC and smaller than what we are using, but it still spins right?; alt-text: The real motor is AC and much larger}
Some little metal strings go between our squirrel containment facilities and the giant metal box to allow the magical squirrel inhabitants to talk to each other.
IMG_20160130_151445.jpg
{caption: metal strings; alt-text: wires}
IMG_20160130_151537.jpg
{caption: squirrel containment facility; alt-text: our devboards at work}
The metal box really wants to talk to someone, but our squirrels were deemed too unimportant because they don't know the secret password.

To learn about the metal box, we needed to stare at lines formed by small squares on a glowing rectangle.
Once we decided that the lines failed to contain the information we needed, we pressed large buttons repeatable to create our own lines for another human to interpret.
That human, a person that works with the creators of the magical metal box, will give us the secret password that their squirrels require.


More clear explanation:
This week, we worked with the Sevcon Gen4Size10 motor controller.
It sits on a table with power supplies rather than the actual batteries for testing.
After working for a while to learn how to use CANopen, and reading through the documentation for the motor controller, we began trying to talk to it using our devboards.
We found that the motor controller is in master mode, and tries to send out a SYNC message to tell the other CANopen nodes to talk to it.
After trying to write values to the motor controller to change it's ID, disable the SYNC message, and switch it to slave mode, we found that it was always broadcasting an error message with each attempt.
The error message pointed us to another CANopen index to read, which informed us that we do not have a high enough access level.
In order to change the access level, a password must be provided to the Sevcon.
We have sent an email to a representative at Sevcon asking about the password.

MechE Battery Party!

MechE Updates

Our primary concern today was designing structures to hold and support our battery packs in the back of the Opel. By the afternoon, literally everyone on the MechE team was engrossed in this task. We were even honored to have Sir Nicholas Arango from the EE team come and help us generate ideas.
Being a team with a small car and big ambitions, one of our biggest design constraints in our Opel project is that we have 464 individual battery packs to distribute between what used to be the engine compartment and the space which used to house the back subframe and gas tank. Each group of cells has to be housed such that none of the cells are at risk of being ruptured in the case of a collision. At the same time, the front and back compartments each require a cooling system for these cells, and in addition to our subframe, motor, and transmission in the rear compartment, each compartment will eventually house one or more modules such as our motor controller or our battery controller. Our design constraints, therefore, are difficult to work with, and it took hours narrowing down what path we should take.

Alex helping lead discussion. Alex and Joey, who had done a great deal of work designing our battery supports in weeks past, proved invaluable.

Leave it to Rango to bring out the best in people.

After hours of work, first in small subteams and then as a whole, we were able to come up with a modular design for our supports which could be implemented universally across virtually any permutation of battery placement. We designated two teams—one to generate plausible battery placements with batteries oriented towards the back of the vehicle, another with cells toward the passenger side—to create a library of battery placements to choose from. This coming week, we will select the design that seems most feasible, stable, and space-conscious so we can start building the support frame itself.


A set of one of many sizes of battery module CADded by Joey
In addition to this, Jacob, Ryan, and Olivia worked with Jimmy from the EE team to decide how and where to mount potentiometers to the accelerator and brake pedals in the Opel, and Joey created comprehensive CAD of the structural members of the Opel frame.


Joey’s CAD of the structural components of the Opel frame





Thursday, January 28, 2016

EE Team Updates


Today the EE team converged once again to check in regarding what each of us were working on, if we were stuck on issues, and finally, discuss the very important (and safety critical) shutdown sequence of the car.

First, Rango discussed a sizing issue that was realized after our newly printed PCB was put into our lovely-looking, insulated PCB enclosure:

IMG_20160126_202156.jpg
The EE team apprised of a redesign: our first printed PCBs had not accounted for the size of the lips/flange of the adaptor connecting the PCB to peripherals, CAN bus, and power lines. As such, the cover to the insulating box surrounding the PCB does not lie flush to the PCB. Unhappiness.

We then went through in detail exactly what sequence of events needs to happen the moment the driver turns the key to “off” (assuming no critical errors initiating or during the shutdown sequence - we’ll handle that next Tuesday). In our discussion, we took into account safety checks, possible design improvements to our sequence, and the conditions necessary to safely turn off the vehicle.   The following is the Opel’s democratically-decided shutdown protocol:

shutdown-sequence_1.jpg
The team’s white board design of the checks and action sequence that the car’s driving state machine ought to undergo in order for the car to safely shutdown.

Our team checked in at the beginning of the meeting to discuss their current projects, their short-term goals, and the obstacles that they need to overcome.

Rebecca continued her work on the User Interface Module. Specifically, she is working on getting test examples on the SPI protocol up and running, and beginning to write the code for the User Interface.

Toby is continuing his work on the Power Distribution Module. He is going to add connectors to his computer and experiment with the gauges so that he knows he is able to communicate with them using I2C.

Jonathan located a handful of 2-twisted-wires that we will use to wire the CAN bus. He also started working on matching up pins in each module’s external peripheral/CAN bus connector.

Skanda/Bryson

The Skanda and Bryson duo are writing unit tests for the Driver Interface. Certain functions in their driver utility code currently do not have tests written for them, so they will continue to work on that in the near future and work on implementing the car initialization sequence.

Hugo - electric vacuum pump to buy; pricey, but had all the comments

Hugo was looking for more improved parts to use in our braking system. He found an electric vacuum pump that satisfies all of our requirements and that was more efficient than our previous pump. Even though the part is pricey, he felt that its functionality was worth the cost.

Jordan continued working on designing the circuits used to control the driver interface relays.

Helmuth managed to talk to the motor controller (!), getting a motor interface communication example using CANOpen up and running!

The team is busily working on finishing the OpelGT system modules!

Electrical Architecture Finalized


After a few months of design, we finalized the electrical system architecture of the electric Opel GT. Our design philosophy was to create small, simple modules that all interface over a shared CAN bus and tie the Motor Controller, BMS, and charger together. The diagram shows the architecture including the power sources for the modules. Signals are shown with thin lines and power connections are shown in bold. This diagram is abbreviated, but shows the significant details for the turn-on and turn-off of the vehicle. Six of the modules in the car are being designed in house, while three others are commercial products.


evt arch.png


In-House Modules:

  • Driver Interface: Acts as interface between user controls and their associated peripherals (ignition, lights, drive mode, etc). Controls the state of the vehicle.
  • Throttle Interface: Reports throttle and brake pedal positions and ensures accurate readings with redundant measurements.
  • User Interface: Responsible for reporting status of the vehicle to the user through gauges, indicator lights, and displays. Also responsible for logging vehicle state.
  • Wheel Velocity Sensor: Reads vehicle velocity from hub sensors and broadcasts to the vehicle.
  • Motor Interfaces: Acts as the interface between our modules’ CAN bus and the sevcon CANOpen bus. Also generates control signals for motor controller.
  • Low Voltage Detection System: Monitors low voltage power buses and backup power sources
Off the Shelf Modules:
  • Tritium IQ Battery Management System
  • Sevcon Gen4 Size 10 Motor Controller
  • Brusa NLG513 Charger


All of the modules will reside in small aluminum extruded enclosures. All the PCB’s are designed from a common template to keep input/output connectors the same, allowing us to design only one faceplate. Each module will have one 8-pin CAN/Power connecter, one 23-pin auxiliary connector, one 6-pin programming header, and breakout for up to 8 status LEDs. An NXP LPC11C14 microcontroller is the heart of each module, powered off a shared 12V power bus.


A prototype of the Wheel Velocity Sensor module was completed today. While the 9 pin can connector was not available from digikey, all other components have been assembled and tested.

We are excited to have our first module complete and to see through the completion of several more over the next few weeks. We hope to have our custom designed hardware for all of the modules in hand within the next two months, working in a prototype state on our testbench shortly after.

Wednesday, January 20, 2016

EE Meeting: Car Startup Sequence

On Tuesday, the EE subteam gathered to discuss the Opel’s startup sequence. We hammered out a specification detailing all the steps between initial turn of the key to Motor Controller enable. The discussion revolved around several themes:
  • In what ways should the Opel’s startup sequence be similar to the startup sequence of a conventional gas-powered car?
  • How robust should each electrical module be to failures in the other modules?
  • In the case of a failure, how much decision-making responsibility should the driver be given? Should the driver be warned with an indicator on the UI? Should the car be allowed to start up if the failure occurs in a nonessential module?
  • Which systems should turn on which other systems? In what order? How do we check that the required systems are functioning correctly?
  • Since the DI’s codebase is already very large, the team expects an increasing probability of bugs as the new startup sequence is coded into the DI state machine. What steps should be taken to combat this?
Startup sequence

Clutch and turnkey
Old DI state transition diagram (to be updated with changes to startup sequence)


Monday, January 18, 2016

MechE: Playoff Saturday!

A quick turnaround from the all-nighter on Thursday, and the gang was back where we left off!  We needed to take some ride height and suspension measurements on faculty advisor, Professor Dan Frey's original Opel, so he invited us over to his house to inspect the Opel as well as watch the Pat's Playoff game against the chiefs.  

The squad made it in early to make up for the time, with Ryan getting right to CAD practice on the 2D transmission mounting parts.

 

Alex and Alberto continued cutting the necessary support members for the rear suspension structure, according to the CAD that we began to finalize on Thursday night.


 Crazy Jake continued cranking away as the team librarian, reading up on some serious suspension research in order to make sure that we would take the correct measurements at Dan's house.


The frame is slowly beginning to take shape, and we're hoping to install the motor/transmission assembly soon.  EVT legend John Kongoletos was back to offer some mentoring to the young welders!


Jarrod continued working through the CAD and relaying the measurements to the weld team...in addition to getting everyone setup and organized with Solidworks EPDM on their personal laptops.  


After lunch, the MechE subteams met with their EE team counterparts to discuss the integrated tasks such as enclosures and throttle setup.  Then we were done for the day, packing it up and heading to Dan's house.


The trip is never complete without checking out Dan's chicken coop and holding the hens!



The young members got a chance to meet Dan and we had a good time taking a break from welding to watch the game.  At least most of us were happy that the Pats won!


 At halftime we made it out to Dan's garage, where he gave us the rundown on all of his vehicles and current car projects....


And Crazy Jake got down to take all of the necessary Opel measurements to take back to the shop.  Overall it was a successful & productive day, and a fun time hanging out with Dan.  Now we just have to finish up the electric Opel for him!  Two more weeks of IAP, let's go!


Friday, January 15, 2016

MechE Marathon Thursday is back!

The MechE Team tradition of staying up late on Thursday nights was reinstated yesterday!  With much work to be done, nearly the entire team made it out for the "other 9 to 5" Marathon Thursday work party!


After the weekly team organizational meeting, it was all hands on deck for the MechE crew.  The remaining Miata control arm mounting components of the original subframe were ground down and sanded, with the necessary jigs and fixtures put in place to prepare for welding. 


A combined effort of welding and CAD-ing at the same time brought everything together, and it's looking like the new subframe geometry will fit nicely in the rear of the car! 


Alex and Z were able to design the lower deck for supporting the batteries, and AA was able to weld it all together.


The frame still needs further development and construction, but the dimensions have now been confirmed and everything appears to be aligned correctly.


Saturday's meeting will focus on incorporating and mounting the drivetrain components, and proceeding to attach the entire assembly to the scrap Opel frame.  Still much work to be done, but we're hoping to be starting the installation process on the black Opel next week!


After a long work night, there's nothing better than the routine trip to Beantown right before it closes at 4AM!