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...

This week Ganesh and I were able to read temperature with Teensy. To do that we had to modify hardware circuit path that connected temperature sensor to Teensy. What I learned from Ganesh is it is wrong the raw data coming from the sensor directly. There is a program needed to convert raw data coming from the sensor and such program's specifications is stated within data sheet of the sensor which can be found online. What we did is we didn't write necessary program to interpret incoming values from the sensor. Rather, we found a library that does the job for us.

We also came across a problem with Teensy compiler. Teensy doesn't do what it is supposed to. We need to do some prototyping.

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

I emailed pjrc forum to have some help to the problem we had last week. Forum admin made his tests and told me there is nothing wrong with Teensy and its development environment. At this point I can't say anything before doing some more prototyping.

I also asked John for providing me some tools. He asked me to ask Ganesh if he has those or he suggested me to buy those and said he'll pay later. I already bought another Teensy for the project with my own budget. It is sometimes hard to communicate with team members due to time constraints. I may have to buy a breadboard, couple cables and LEDs by myself at this point. It is much easier that way.

My prototype will test input and output pins and their correctness. Last time we didn't get what we expected out of Teensy.

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

I visited Ganesh and took some necessary stuff to do prototyping including a breadboard, couple cables, the board itself. My primary job is to check whether the toggle pin works correctly or not. It was the pin I and Ganesh obtained conflicting results in terms of voltage. I will try the pin once again with a LED to see what's wrong with it. I thought the problem was a compiler issue but manufacturer is pretty determined that it is not.

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

I checked the problem once again and I am facing the same issue. The code doesn't result with the intended output from the pin. I might have to tell Ganesh to take Teensy out of its place and I will have to try it again without it being soldered to other board that Ganesh had already soldered.

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

Problem with Toggle pin, necessary examination should be made.

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

Problem with Toggle pin, necessary examination should be made.

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

We are able to read both temperature and frequency at the same time. We found that unstable values was due to physical state of the chip. We took it from its place on the board and placed it into a breadboard. After that we started to obtain reasonable results. There is couple changes made to the initial circuit design so initial design for the board will have to be changed sooner or later. Then there was a little problem about the software. The reason is we are using some libraries and libraries sometimes block output screen and intended code doesn't work as expected all the time.

This Thursday and Friday I will be setting up necessary system for another computer that will be on for couple of days to see how stable the numbers are from the system. Next step is to be able to store the numbers from the chip to a database.

Database will provide necessary foundation for distributing information and will allow one to operate on the data. From the point on more complex structures can be worked on.

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...