Progress Reports‎ > ‎

Anthony Tse

Progress Report for Week 10 (03/07/2011 to 03/11/2011)

posted Mar 19, 2011, 12:14 AM by Anthony Tse

Project title: RFID

 

Summary

 

Technical Tasks and Time spent (Examples shown)

•Reading technical documentations: _3_ hours

•Meeting with teammates to work on project: _30_ hours

•Looking up info on evaluation boards:  __ hours

•Working on development tool tutorial:  __ hours
•Independent work: _2_ hours
Non-technical Tasks and Time spent

•Looking for a teammate:  ___ hour

•Looking for parts:  __ minutes

•Ordering parts:  ___ minutes

•Writing project report:  __0_ hours

Total time spent:_35_ hours

 

Highlights

·         Gateway Emulation
·         RFID and Keypad Integrated with Wireless
·         Logging
 
Details
(fill in as much as you can, by including screen shots, photos, schematics, and links)

 

·         I worked on Gateway Emulation, which was basically our receive program with autoack with payload and logging received data.
·         Integrated RFID and Keypad with wireless so whenever a student submits his/her information, a payload is generated and sent to Gateway. Also added code for our RTC and tested its functionality.
·         Kevin worked on coding up the Backend process we designed. We tested the Backend program individually and it seemed to work, but once we integrated it with the rest of the program that separate thread caused our board to run out of memory. We tried reviewing our entire program and optimizing where we could, but eventually decided to drop it since we were running short on time.
·        Kevin finished the enclosure.
·        Seng finished all his tasks, added a boot up screen to ask users to verify date and time, and worked on Power Saver modes.
 
Plans
(snapshot of your calendar schedule)

·         Look for business opportunities.

Progress Report for Week 9 (02/28/2011 to 03/06/2011)

posted Mar 18, 2011, 11:25 PM by Anthony Tse   [ updated Mar 19, 2011, 12:13 AM ]

Project title: RFID

 

Summary

 

Technical Tasks and Time spent (Examples shown)

•Reading technical documentations: _2_ hours

•Meeting with teammates to work on project: _9_ hours

•Looking up info on evaluation boards:  __ hours

•Working on development tool tutorial:  __ hours
•Independent work: _2_ hours
Non-technical Tasks and Time spent

•Looking for a teammate:  ___ hour

•Looking for parts:  __ minutes

•Ordering parts:  ___ minutes

•Writing project report:  __0_ hours

Total time spent:_13_ hours

 

Highlights

·         Met with Gateway Team
·         Payload Manager
·         Receive Multibyte
·         RFID Integration with main program
 
Details
(fill in as much as you can, by including screen shots, photos, schematics, and links)

 

·         Met with Gateway Team. Found out they were having troubles with the Nordic so I tried to help them for a bit. We got the payload specification from Gateway. We suggested that gateway team use XTEA encryption as well, and Kevin helped them get setup with sample code and explaining how XTEA works. Realizing how much trouble Gateway was having with the Nordic, our team decided to add Gateway Emulation to our lists of tasks before demo day.
·         I did not feel the payload structure Gateway outlined for us was the optimal for our purposes because it used 30 of the 32 bytes available in the payload, everything was expressed in ASCII, and it had no way of handling synchronization issues. So the next day I defined a new payload structure (outlined on our team page) that was only 21 bytes long but had additional fields for system date and time for synchronization purposes, and had enough bytes remaining for us to create some type of identification for assembling multiple packets in the future. I then wrote a PayloadManager class, that would assemble and disassemble a payload into the right format given the correct parameters. When initializing PayloadManager, one could specify an encryption type so during assembly it would encrypt student's sensitive data automatically, and decrypted it during disassembly on the receiver side.
·         I wrote code to handle receiving payloads with multiple bytes, and verified the functionality of our TX and RX programs for the Nordic. Afterwards I started working on autoack with payload to send our "Gateway's" system time back to our Scanner, as another way to handle time synchronization issues.
·        Added events and event handlers for RFID Reader, so when a card is scanned the main program will be notifed. 
·        Purchased an enclosure online
 
Plans
(snapshot of your calendar schedule)

·         Finish enclosure, work on logging, integrate rfid and keypad with wireless.

Progress Report for Week 8 (02/21/2011 to 02/27/2011)

posted Mar 18, 2011, 11:14 PM by Anthony Tse

Project title: RFID

 

Summary

 

Technical Tasks and Time spent (Examples shown)

•Reading technical documentations: _4_ hours

•Meeting with teammates to work on project: _9_ hours

•Looking up info on evaluation boards:  __ hours

•Working on development tool tutorial:  __ hours
Non-technical Tasks and Time spent

•Looking for a teammate:  ___ hour

•Looking for parts:  __ minutes

•Ordering parts:  ___ minutes

•Writing project report:  __0_ hours

Total time spent:_13_ hours

 

Highlights

·         Wireless can now send multiple bytes and do dynamic payload length reliably
·         Poster for EWeek BBQ

Details

(fill in as much as you can, by including screen shots, photos, schematics, and links)

 

·         Spent majority of our meet up time working on the poster (design, content, bill of materials, etc). Seng took care of the Bill of Materials, I wrote most of the content, and Kevin put everything together on Photoshop.
·         Kevin and I got most of the features and configurations set the way we wanted for the Nordic devices. We tested his send multibyte code, which seemed to work, however our receive program could only receive one byte at a time...so that's something we have to do the following week. 
·         We spent some time with Google Sketchup, but eventually decided it was too time consuming and difficult to use. So we decided to order a premade enclosure instead 
 
Plans
(snapshot of your calendar schedule)

·         Buy enclosure

·         Finish integration and wireless

Progress Report for Week 7 (02/14/2011 to 02/20/2011)

posted Mar 18, 2011, 10:46 PM by Anthony Tse

Project title: RFID

 

Summary

 

Technical Tasks and Time spent (Examples shown)

•Reading technical documentations: _4_ hours

•Meeting with teammates to work on project: _9_ hours

•Looking up info on evaluation boards:  __ hours

•Working on development tool tutorial:  __ hours
Non-technical Tasks and Time spent

•Looking for a teammate:  ___ hour

•Looking for parts:  __ minutes

•Ordering parts:  ___ minutes

•Writing project report:  __0_ hours

Total time spent:_13_ hours

 

Highlights

·         Integration with keypad, lcd and main program
·         Contacted Gateway Team
·         Encryption
·         Progress with wireless

Details

(fill in as much as you can, by including screen shots, photos, schematics, and links)

 

·         I wrote events and event handlers for Keypad class so whenever a key is pressed the interrupt also triggers an event to notify the main program which key was pressed. The main program then takes the character associatied with the key and displays it on the LCD. Once this was ready, Seng took over and started working on menus, messages for LCD, and configuration settings.
·         I sent an email to Gateway to update them on our progress with the Nordic and ask about their progress with the Nordic and what they had decided for encryption, payload structure, payload length, CRC, handling time synchronization, any additional data to send besides IDs, if they would send us any data back.
·         Kevin implemented and tested encryption and decryption for XTEA and RSA. We think RSA might be overkill for this application, but included it into our program just in case. Most likely we'll be using XTEA since the max size for a Nordic payload is 32 bytes and XTEA doesn't add any additional bytes. 
·         Helped Kevin research, implement and test Shockburst mode for Nordic
 
Plans
(snapshot of your calendar schedule)

·         Make enclosure

Progress Report for Week 6 (2/7/2011 to 2/13/2011)

posted Mar 18, 2011, 10:19 PM by Anthony Tse

Project title: RFID

 

Summary

 

Technical Tasks and Time spent (Examples shown)

•Reading technical documentations: _1_ hours

•Meeting with teammates to work on project: _9_ hours

•Looking up info on evaluation boards:  __ hours

•Working on development tool tutorial:  __ hours

Non-technical Tasks and Time spent

•Looking for a teammate:  ___ hour

•Looking for parts:  __ minutes

•Ordering parts:  ___ minutes

•Writing project report:  ___ hours

Total time spent:_10_ hours

 

Highlights

·         LCD functional
·         New Keypads
·         Noticed factory defect on LiPoly Charger we purchased from Sparkfun

Details

(fill in as much as you can, by including screen shots, photos, schematics, and links)

 

·         Seng finished off the LCD, but it was randomly crashing and not working. We eventually found out that it was caused by the "Change Brightness" command. Kevin had problems with Wireless but eventually got it to work 
·         We noticed a factory defect on the LiPoly Charger we purchased from Sparkfun, there was a capacitor that was not properly soldered on to the board. I contacted Sparkfun, however at the time they had already discontinued selling that particular charger. So instead of replacing the board we had, they gave us the newer version of that charger. 
·         We replaced the old keypad we had with the new ones we ordered. The new ones were a lot smaller and had better buttons, however the layout was different from our old one. Once we figured out the button matrix we were good to go. Kevin noticed that the response of the keypads were very good and had much less bounce, so he turned down the timer from 200ms to 8ms. When testing, I noticed sometimes keys were getting duplicated and showed up twice when it should have only shown up once. After debugging, we determined it was because of the change to the timer, so we increased to 150ms.
Plans
(snapshot of your calendar schedule)
·         Wireless and poster!
·         Start working on enclosure design

Progress Report for Week 5 (01/31/2011 to 02/6/2011)

posted Mar 18, 2011, 9:48 PM by Anthony Tse

Project title: RFID

 

Summary

 

Technical Tasks and Time spent (Examples shown)

•Reading technical documentations: _2_ hours

•Meeting with teammates to work on project: _7_ hours

•Looking up info on evaluation boards:  __ hours

•Working on development tool tutorial:  __ hours

Non-technical Tasks and Time spent

•Looking for a teammate:  ___ hour

•Looking for parts:  __ minutes

•Ordering parts:  ___ minutes

•Writing project report:  ___ hours

Total time spent:__9_ hours

 

Highlights

·             Parts arrived

·             Power subsystem working
·             Restructuring of main program
·             Progress on LCD
 
Details
(fill in as much as you can, by including screen shots, photos, schematics, and links)

 

·         I gave Kevin all the parts and he soldered and assembled the power subsystem.

·         I noticed we were having a lot of conflict issues because each of us kept rewriting main program for our own testing. So redesigned the main program to introduce case statements for each subsystem, and made sure both Kevin and Seng used the respective case for their testing to prevent unnecessary conflicts and code rewrites.

·         Seng is making progress with the LCD, and creating some api functions we defined. Our team had a slight disagreement on how to handle printing to the LCD when a user types on the keypad. The two options were to display a character at a time as the user types or to re-write the whole line (16 characters each time). Personally I would have wanted one character at a time, because the other method seems unnecessarily wasteful..but we went with the other option because of ease of implementation..

·         While trying to enable additional features on the Nordic, Kevin noticed that some of the register mappings that came with the Nordic wireless sample code was wrong. Their mapping was for the NRF24L01, which didn't have some registers and commands that the NRF24L01+ had. So Kevin started to revise some of the Nordic constants in our program and make them match the ones specified in the NRF24L01+ data sheet.

Plans

(snapshot of your calendar schedule)

·         Enable more features on Wireless
·         Start on enclosure design

Progress Report for Week 4 (01/24/2011 to 01/30/2011)

posted Mar 18, 2011, 9:15 PM by Anthony Tse

Project title: RFID

 

Summary

 

Technical Tasks and Time spent (Examples shown)

•Reading technical documentations: _2_ hours

•Meeting with teammates to work on project: _7_ hours

•Looking up info on evaluation boards:  __ hours

•Working on development tool tutorial:  __ hours

Non-technical Tasks and Time spent

•Looking for a teammate:  ___ hour

•Looking for parts:  _60_ minutes

•Ordering parts:  ___ minutes

•Writing project report:  __0_ hours

Total time spent:_10_ hours

 

Highlights

·             Basic functionality working for Nordic

·             Problems testing Nordic

Details

(fill in as much as you can, by including screen shots, photos, schematics, and links)

 

·         Was not able to use USB Serial Interface we purchased for Nordic. After programming one of the devices for transmit, we placed the other Nordic into the USB Serial Interface board and connected it to our laptops but was not able to configure or read anything. We eventually decided to give up on the USB Serial Interface board, brought out our second FEZ Domino board and I wrote a small receive program for testing. With one board running the transmit program and the other running the receive program, we were able to send one byte continuously between the devices. However, we noticed packet loss most likely due to the noise within Kevin's complex.

Plans

(snapshot of your calendar schedule)

·         Enable more features on Nordic 
·         Start on enclosure design

Progress Report for Week 3 (01/17/2011 to 01/23/2011)

posted Mar 18, 2011, 8:43 PM by Anthony Tse   [ updated Mar 18, 2011, 9:09 PM ]

Project title: RFID

 

Summary

 

Technical Tasks and Time spent (Examples shown)

•Reading technical documentations: _2_ hours

•Meeting with teammates to work on project: _7_ hours

•Looking up info on evaluation boards:  _0.5_ hours

•Working on development tool tutorial:  __ hours

Non-technical Tasks and Time spent

•Looking for a teammate:  ___ hour

•Looking for parts:  _60_ minutes

•Ordering parts:  _30_ minutes

•Writing project report:  __0_ hours

Total time spent:_11_ hours

 

Highlights

·             Continued testing of RFID Reader and Keypad
·             On schedule for project progress

·             Ordered remaining parts

Details

(fill in as much as you can, by including screen shots, photos, schematics, and links)

 

·         After Kevin finished his USB Mass Storage and microSD program, we realized that running short on COM ports. Originally we were using COM1 for the RFID Reader, but for the USB Mass Storage to work we had to give COM1. We looked into the FEZ documentation and found out we could remap a few analog pins into a COM port, which we did to solve our problem.
·         Retested RFID Reader and Keypad to ensure functionality
·         After finding a suitable step-up and serial LCD, I ordered the remaining parts from Sparkfun which included:
o    2 Keypad - 12 Button (http://www.sparkfun.com/products/8653)
o    1 5V DC to DC Step Up - VPack PCB  (http://www.sparkfun.com/products/8290)
o    2 Serial Enabled 16x2 LCD - White on Black 3.3V (http://www.sparkfun.com/products/9067)
Power Buttons:
o    1 Pushbutton Power Switch LV  (http://www.sparkfun.com/products/8903)
o    1 Surface Mount Right Angle Switch (http://www.sparkfun.com/products/8769)
 
·         Starting to help Seng with Nordic, and reading documentation for the device.
 
Plans

(snapshot of your calendar schedule)

·         Find the time to convert our source and upload to doxygen.

·         Wire up battery stuff once the step up regulator comes

·         Start on enclosure design once we finalize our parts layout relative to each other

Progress Report for Week 2 (01/10/2011 to 01/16/2011)

posted Mar 18, 2011, 8:10 PM by Anthony Tse   [ updated Mar 18, 2011, 8:31 PM ]


Project title: RFID

 

Summary

 

Technical Tasks and Time spent (Examples shown)

•Reading technical documentations: _1_ hours

•Meeting with teammates to work on project: _8_ hours

•Looking up info on evaluation boards:  __ hours

•Working on development tool tutorial:  __ hours
•Independent Work:  _4.5_ hours

Non-technical Tasks and Time spent

•Looking for a teammate:  ___ hour

•Looking for parts:  _60_ minutes

•Ordering parts:  ___ minutes

•Writing project report:  __0_ hours

Total time spent:_14.5_ hours

 

Highlights

·         Finished code for RFID reader, keypad
·         microSD is functional, Seng is working on Wireless

·         Power subsystem parts arrived.

Details

(fill in as much as you can, by including screen shots, photos, schematics, and links)

 

·         Helped Kevin debug his microSD/USB Mass Storage program. Sometimes Fez Domino board crashes when plugging and unplugging Fez from our computers.
·         Finished writing code for interrupt-driven RFID Reader. Whenever a RFID tag is scanned, an interrupt will parse the data received, calculate and compare checksum for data to make sure there were no errors, and finally print either an error message or the scanned RFID tag to the Debug Console
·         Since I finished the RFID Reader earlier than expected, I worked on integrating the keypad. There was sample code in the Fez documentation for handling keypads with polling. I copied and pasted the code into our program and it seemed to work fine, however I decided to take rewrite the whole Keypad class to give it a more flexible design and make it interrupt-driven. After the code was written, I had an array for specifying the pin layouts, an array for specifying the characters on the keypad, and a interrupt to determine what key was pressed only if it was held down long enough. The program seemed to work fine, but I noticed occasional errors due to button bouncing/debouncing, so I implemented a timer to handle the problem and everything turned out nicely after that. Each team member tried to type as fast as possible on the keypad (with two fingers even), and the Keypad program was able to keep up.
 
Plans
(snapshot of your calendar schedule)

·         Purchase remaining parts

·         Start working on enclosure design
 

Progress Report for Week 1 (01/03/2011 to 01/09/2011)

posted Mar 18, 2011, 7:39 PM by Anthony Tse

Project title: RFID

 

Summary

 

Technical Tasks and Time spent (Examples shown)

•Reading technical documentations: _1_ hours

•Meeting with teammates to work on project: _8_ hours

•Looking up info on evaluation boards:  _1_ hours

•Working on development tool tutorial:  _2_ hours

Non-technical Tasks and Time spent

•Looking for a teammate:  ___ hour

•Looking for parts:  _60_ minutes

•Ordering parts:  _30_ minutes

•Writing project report:  __0_ hours

Total time spent:_13.5_ hours

 

Highlights

·         Ordered parts for power subsystem
·         Wired up RFID Reader
·         Team meeting was very productive.

Details

(fill in as much as you can, by including screen shots, photos, schematics, and links)

 

·         Kevin worked on getting the USB Mass Storage to work on the FEZ. With this subcomponent set up, we would be to read and write to our microSD card and allow users to access content on the microSD by connecting their computer with our system via a usb cable.

·        I wired up the RFID reader as specified in Fall quarter's report. Since we did not have a buzzer available, I attached a LED to the ID-12's buzzer pin for visual confirmation that a card was scanned. When swiping the 125kHz RFID tag over the ID-12, the LED lit up and seemed to verify our wiring was correct. We took a video of the RFID reader in action to demo our progress. Although we have not written any code yet, know that the wiring is correct will allow us to focus on the software aspect next week.
·        We decided it would be best for us to purchase parts from Sparkfun for our power subsystem, rather than building them ourselves mainly to save time from troubleshooting circuit on questionable breadboards. After confirming the parts for the power subsystem with the team, I purchased the following items from Sparkfun:
For Power Subsystem:
      · 1 Polymer Lithium Ion Battery - 2000mAh (http://www.sparkfun.com/products/8483)
      · 1 LiPoly Charger - Single Cell 3.7-7V Input (http://www.sparkfun.com/products/726)
      · 1 Wall Adapter Power Supply - 5VDC 1A (http://www.sparkfun.com/products/8269)
For RTC Clock
      · 2 Coin Cell Holder - Sewable SMD (http://www.sparkfun.com/products/8822)
      · 2 Coin Cell Battery - 20mm (http://www.sparkfun.com/products/338)
 
Plans
(snapshot of your calendar schedule)
·         Work on RFID reader, making it interrupt-driven and reliable
·         Purchase remaining parts, including LCD and step-up regulator
 

1-10 of 15