Team 6 - Safety and Access Control System Meeting Minutes

Wednesday, 11/30 - Google Hangouts

• Discussed and organized the outline of our presentation
• Created a list to reorganize our GitHub files into folder structures

RPM to MPH for Accelorometer

 #Accelrometer RPM to MPH
 #Rahul Manoharan
 #11/17/2016

import smbus
import time


bus = smbus.SMBus(1)


 # This is the address we setup in the Arduino Program
address = 0x08


def writeNumber(value):
     bus.write_byte(address, value)
     return -1


def redNumber():
     number = bus.read_byte(address)
     return number


while True:
     var = input("enter a number:")
     writeNumber(var)
     print ("RPI: Hi Arduino, I sent you "), var
     time.sleep(1)

     #number is rpm number
     number = readNumber()
     print ("Arduino: Here's the current RPM: "), number
     
    #conversion equation
     MPH = ( (4.5 * number) * 60) / 63360
     print ("Here's the current MPH: "), MPH

Team 3 Meeting Minutes 11/17/16

We discussed

• Connectivity class redesign
• CNS class with methods like CNSTransfer which takes the data and transfer it(implemented by monitoring and logging. Calls cns transfer method and put in the data we need. (Define the needs Define transfer protocol. Checksum needed: HCI))
• Take that data for Notification Class. Checks for checksum, Call CNS transfer

ALAN/ KEVAL/ SYDNEED- DEFINE CNS CLASS and CNS Transfer methods

ABU - Notification Bluetooth

Team 1 Command and control Meeting minutes

Meeting minutes 11/17
- Created an interface for 440
- Discussed communication issues in our team
- Discussed with other teams to communicate with us

IST411 Team 2 Monitoring and Logging Meeting Minutes

What we discussed:

• Important aspects of the code
• Requirements for CNS integration
• Requirements from CCS communication system
• Issues left going forward
• System Complexity

What we accomplished:

• Refactored monitoring class to adjust threading mechanism to accept communication code from CCS
• Blueprinted additional methods to allow Monitoring class to be invoked by outside systems
• Diagrammed overall system integration flow with other groups in 411

What needs to be done:

• Write watchdogs and threading methods in Monitoring class
• Write logic for payload recognition
• Discuss messaging protocol complexity with CCS

IST440 Messages to send and recieve

Team 1 Braking System Meeting Minutes

Tuesday 11/8, Thursday 11/10 and Friday 11/11

Our team met up and talked about the work for the rest of the projects. Tuesday and Thursday both are in class, Friday late afternoon our team met for an hour. We focused on brake On and Off .py program.

Progress:

• Python Code for E-Brake (Parking Brake), Sensor Brake, Normal Brake, and ABS Brake are all finished for Turning them ON.  

• Creating Python Code for OFF in all these Brake Type. 

• We redesigned the Android UI for with horizontal view and buttons on the one side of screen.

• Created a user in Android application, Only the driver will be able to login the apps and apply the brakes.

Work for next stage:

• Create more secure way to connect Android to Pi. (External file to read the host name and password for RPi. 

• Create two way communication between Pi and Android ( Apache2, PHP, MySQL and PHPMyadmin in thoughts), Create a socket between two devices, will test out.

• Finish the background code for when android buttons were clicked.

Team 3 Climate Control Meeting Minutes

Our team met and talked together in a Google hangouts call and discussed about the objectives we are trying to  complete. This meeting took about 1 hour and 30 minutes. We also meet in the classroom on 11/9 and 11/11 for about 4 hours total.

Worked on:

- Python code for outside temperature, outside humidity, inside temperature, both fans on and off, cooling on and off , and heating pad on and off.

- Updated the User Interface by adding manual increase and decrease of temperature through buttons.

- Manual toggle of Fan 1 and Fan 2 (ON and OFF function, ex: color change of toggle buttons)

- Bluetooth Connectivity


Working towards:

- JSON script to send over Bluetooth for outside temperature, outside humidity, inside temperature, both fans on and off, cooling on and off , and heating pad on and off.

- Read JSON and place the values into the text view.

- Read JSON from Android to Raspberry Pi through Bluetooth.

-  Perform a test where you must FIRST be able to have the server connected to Bluetooth and have it LISTEN for feedback, server socket. 

- Perform a test where you can send data to the server from a different script which is the client socket

Team 1 Command and Control meeting minutes

11/10/16 7:30 - 9:30

Update as of 11/10/16:
1. xBee communication through
   Serialization done.
2. Message queue done.
3. Command & Control System local communication between our
   system and Monitoring & Logging has begun. We are using a
   localhost pika connection to communicate incoming messages
   from the xBee to the Monitoring & Logging System.
4. Created dummy Monitoring and Logging client code to wait for
   messages for the sake of testing using pika.
5. Cleaned up folder system.

Plan as of 11/10/16:
-----------------------
1. Finish up local pika communication between Command and
   Control and Monitoring and Logging.
2. Get "serial" package installed for Python, removing this
   error:

3. Write Unit Tests for testing.
4. Provide finalized pika communication interface to Monitoring
   & Logging.
5. Provide finalized xBee communication interface (A few lines
   of code in a function) to all 440 Teams.

IST 411 Team 3 Connectivity and Notification Team Meeting Minutes

Meeting 11/8/16
During this meeting:

• Use bash script to check for external device.
• Send the Json dump file using SFTP. The Json dump from the logging system is sent as a text file. 
• Will have to figure out if we want to use bluetooth, wifi, or USB connection to send files.
• (Updated) Uses WIFI.
• Added left and right turn signal lights "out" unit testing for both front and rear lights.
• Will have to get more specific names from the lighting team.

IST 411 Team 2 Monitoring and Logging System 11/10/2016 Meeting Minutes

In development for next week:

• Finishing Unit Tests for logging.py
• Look at how we will interface with Command and Control
• Remove threading from Monitoring
• Instantiate a Monitoring object, one object will handle all of the incoming messages globally
• Transferring messages that contain sub-optimal health codes to Connectivity and Notifications

Finished this week:

• Started on Unit Tests for logging.py
• Started on clearing messages from the Mongo Database
• Finished dumping a text file containing the messages in the database
• Can dump by:
• Subsystem
• Errors
• All collections

Example of an All Collection data text file 

Thursday 11/10 - In class 

Tasks:

• Upgraded OS to Rasbperry Pi Pixel
• Configured ad hoc network
• Currently working on connecting via Bluetooth
• updated Jira server tasks

Team 6 - Safety and Access Control System Meeting Minutes

Wednesday, 11/9 - Google Hangouts

Tasks:

• Got nfc.py to run on RPi 2, however bluetooth isn't supported unless we use a bluetooth dongle. Will need further research and discussion.
• Research about ad hoc wifi network
• Updated tasks in Jira: 
• Write and test code for triggering car alarm using the gyroscope, accelerometer, & magnetometer sensors on the Sense HAT 

IST 411 Team 1 Command & Control - Progress Update

We met with the other 411 groups after our 412 class on Wednesday, 11/2/2016. There, we came up with a unified cohesive view of what the project would be. The Command and Control team now has a crystal clear picture of what is expected of our system and can move forward with the process of writing code.

----------------------------------------------------------------

Team Plan as of 11/3/2016:

1. Update Jira with tasks for code stubbing and method writing
2. Begin code stubbing process.
3. Meet with IST 440 during their class time to create messaging
   standard.
4. Write interface code for message sending and receiving for a
   client xBee.(Breaking System, Lighting System, etc.)
5. Write interface code for message blast-out from Command &
   Control xBee.

----------------------------------------------------------------

Team Goal: By next Thursday 11/10/2016:

1. Have functioning code for sending and receiving messages
   that we can provide to the 440 Teams.
2. Have functioning code for receiving and blasting out
   messages from the Command & Control xBee.
3. Provide interface for Monitoring & Logging to store messages
   that Command & Control receives.

IST 411 Team 3 Connectivity and Notification Team Meeting Minutes

Meeting date 11/2/2016

• Added more unit testing to github in the  notification_unitTest.py file.
• Updated working code for connecting to the internet via blue tooth.
• Discussed with group leaders of how and when we will send messages to each other.
• Provided examples of what we need in another post.

IST 411 Team 3 Connectivity and Notification information Req from Monitoring and Logging

The extreme health codes from each system eg : {'OID' : 'MLS', 'DID' : 'CNS', 'PLD' : ' HC# Brakes have failed'}, {'OID' : 'MLS', 'DID' : 'CNS', 'PLD' : 'HC# left turn signal non functional'}

We will also need the information that are maintenance related like :
{'OID' : 'MLS', 'DID' : 'CNS', 'PLD' : ' Batteries need to be changed'}
{'OID' : 'MLS', 'DID' : 'CNS', 'PLD' : ' Brake calipers need to be changed'}
{'OID' : 'MLS', 'DID' : 'CNS', 'PLD' : ' Fans for the climate control system needs to be changed'}
{'OID' : 'MLS', 'DID' : 'CNS', 'PLD' : ' Lights are near the end of their life cycle'}

We could set up the alert to be sent once the light have been turned on and off for a certain number of times or when the brakes have been used a certain number of times (setting up a life cycle for the wear and tear parts of the vehicle). An entry of a counter variable into the collection would work.

IST 411 Team 2 Monitoring and Logging meeting minutes

Group meeting with entire class discussed requirements for communication and interfacing with the XBees. Continued discussing messaging standards and the need for groups to define their payloads.

Group Progress:

• Fixed logging class to provide all basic mongo functionality
• Created methods needed for handling parsing of messages in to various collections
• Refactored code to allow for code reuse and remove duplicate code
• Added comments to new and updated methods
• Created a testing program for the logging class
• Discussed the need for a full class meeting with 440 to determine message payload requirements

Tasks under development:

• Create logging file output in easy to read format
• Determine how to get the logging file from Pi to whatever device requested it
• Create db message retrieve and clear methods
• Design, implement, and test interface between monitoring class and communication class

Team 3 Climate Control Meeting Minutes

Our team met up together in a Google hangouts call and discussed about the objectives we are trying to  complete. This meeting took about 1 hour and 30 minutes.

11/02/2016

• Created Python code for:
• Fan ON/OFF
• Cooling Fan ON/OFF
• Heating Pad ON/OFF
• We are going to send files via Bluetooth to the pi and have it communicate with android devices
• Updated Jira server tasks for each member
• Temperature sensor is working with the pi

Update 11/04/2016

Spent five hours working on Android UI and Bluetooth Connect:

• Configured all python files with correct GPIO Pin and made On/Off files for
• Fan One
• Fan Two
• Heating Pad
• AC Cooling 
• Connect Breadboard to the Raspberry Pi
• Power on Fans, AC Cooling, and Heating pad
• Connect Pi to Android tablet and use tablet to turn fan ON and OFF with buttons 

IST 440 Lighting Team Meeting Minuets

The weeks of October 24th and October 31st:

• Got the new lights for the car. Consisting of two light matrices and two LED progress bars. 
• The two light matrices will work as the front lights on a car, whereas the progress bar will be the two back lights.
• Worked with both the lighting matrix and the progress bar to create the lights we need.
• Got all the necessary lights needed laid out on the light matrix.
• Added new toggles to the Android app.
• Tested the new toggles. 
• Ran into an issue where we had an issue when running two lights at once.
• Added logic to the Android app to turn off the previous toggle. 
•  Ran into an issue with the Progress bar. 
• When we run the same code we get different outcome even though there is no instance of randomness.
• Currently working to debug the Progress bars to get a constant outcome on what is needed. 
• Once all lights are laid out, we will communicate with other teams to have the lights go off when certain criteria is meet.