Ugur Buyukdurak

01/31/2016 Weekly activities including accomplishments, problems changes to plan, meeting minutes, etc...

I will start working with Quansor team ITC. Followings are from John's letter to me about what is expected of me.

(a) Develop a structure for a control and reporting module for a new water sensor product;

(b) Provide code for the module both locally and on a web-based reporting site, including a streaming graph of customer contaminant concentration data;

(c) Provide control interfaces for sensor peripherals, including metering pumps, calibration tables, water parameter measurements such as pH, pH adjustment and temperature and activation of sensor regeneration modules.

(d) Provide the architecture to accumulate and share sensor chemical receptor protocols;

(e) Provide the architecture for a customer service website.

Most important of all is to make communication between Teensy3.2 and an operating system running a database for data to be stored in a proper way. Once data is stored in a proper way in a computer, other goals can be succeeded.

02/07/2016 Weekly activities including accomplishments, problems changes to plan, meeting minutes, etc...

Still waiting a response from ISSS as to status of approval of CPT.

---UPDATE 2/8/2016---

From 2/8/2016 3 p.m onwards I have my CPT.

02/14/2016 Weekly activities including accomplishments, problems changes to plan, meeting minutes, etc...

---UPDATE 2/15/2016---

I will meet with one of the team members today to discuss details further.

Visited Ganesh from the team and obtained further information about how the circuit works, what pins are used, what is expected and so on. Tomorrow we will be soldering Teensy Duo 3.2 I bought not to alter other Teensy 3.2 they use. It is already come with a pre-loaded software which they don't have access to its source code. Therefore for not altering its original program, we will use another Teensy Duo. We will also try to disassembbly the object code from first Teensy duo. For doing that, we need to figure out how to transfer back program from Teensy Duo back to a computer. It may be possible it may not be. I will give a try.

---UPDATE 2/16/2016---

I asked in the forum of the company that produces TeensyDuo whether it is possible to fetch object code out of Teensy. Admin of the forum simply said no.

02/21/2016 Weekly activities including accomplishments, problems changes to plan, meeting minutes, etc...

We replaced other John's Teensy Duo with mine not to lose original program in John's Teensy. As we tried we are able to transfer programs between my computer and Teensy. New goal is to interpret incoming data in a meaningful way from specific pins. Actual component which makes the sensing is out of its place as of now. It needs to be readjusted again to obtain most reliable data.

As of now I made my first attempt to read data from the circuit. Results I am getting are inconsistent and doesn't make any sense. These results can be product of many possibilities. I need to consult Ganesh. It can be a problem with physical connection, sensor's unexpected physical shift from its place, or wrong approach to reading data. I am not sure in what way pins should be read. Circuits description Ganesh told me has some missing parts as to how to read data in a proper way. Before everything we need to make sure there is nothing wrong in physical state of the circuit.

02/28/2016 Weekly activities including accomplishments, problems changes to plan, meeting minutes, etc...

03/06/2016 Weekly activities including accomplishments, problems changes to plan, meeting minutes, etc...

03/13/2016 Weekly activities including accomplishments, problems changes to plan, meeting minutes, etc...

03/20/2016 Weekly activities including accomplishments, problems changes to plan, meeting minutes, etc...

03/27/2016 Weekly activities including accomplishments, problems changes to plan, meeting minutes, etc...

04/03/2016 Weekly activities including accomplishments, problems changes to plan, meeting minutes, etc...

04/10/2016 Weekly activities including accomplishments, problems changes to plan, meeting minutes, etc...

04/17/2016 Weekly activities including accomplishments, problems changes to plan, meeting minutes, etc...

04/24/2016 Weekly activities including accomplishments, problems changes to plan, meeting minutes, etc...

05/01/2016 Weekly activities including accomplishments, problems changes to plan, meeting minutes, etc...

05/08/2016 Weekly activities including accomplishments, problems changes to plan, meeting minutes, etc...