Electronic Fight Judge ECE 345 Project

1
Electronic Fight JudgeECE 345 Project 29

• Yingkai John Liaw
• Wojciech Magda

2
Project Concept

• Integration of martial arts into a fun and
  practical engineering project
• In martial arts sparring competitions, points
  are awarded for punches or kicks delivered
  successfully to specific target areas of the
  opponents body. Due to the speed of
  contestants, it is often difficult to correctly
  award points for contact.
• We propose an electronic judging system that
  will automatically detect and interpret contact
  between contestants.
• The information will be relayed to computer that
  will create a visual real-time representation of
  the fight.
• This system will aid judges in awarding points
  for successful hits and in determining the
  winner.

3
Objectives

• To design a practical and useful system for
  judging sparring competitions.
• To make the system easy to use for the
  competitors and judges.
• Intended Functions
• Sensors embedded in sparring gear that detect
  certain thresholds of activity or pressure
  symbolic of direct contact between competitors.
• Valid wireless transmission of data from sensors
  to computer.
• Software to interpret data from the sensors.
• User interface and visual representation of
  sparring session in the software to allow judges
  to gauge time and points scored.

4
Hardware Design

• Two sets of sparring gear, embedded within each
  set of sparring gear are
• 13 contact Sensors
• Accelerometer with A/D converter
• 16 to 4 priority encoder
• Glolab GL-104 encoder
• Linx Transmitter
• Two receiver units containing
• Linx Receiver
• Glolab GL-104 Decoder
• Links to parallel port of PC

5
Hardware DesignSensors

• Accelerometer circuit embedded in full sparring
  helmet is used to detect G-force from contact
  with the head.
• Contact sensors (embedded in chest guard,
  sparring gloves, feet guard, and shin guard)
  detect pressure representative of a punch or
  kick.

6
Original Design Hardware Flow Chart
7
Original DesignSoftware Flow Chart
8
Hardware ImplementationTransmitting Unit

• Each wireless transmitting unit has
• Sensors
• Accelerometer ADXL05 (Analog Devices)
• Detects G-force along one axis, scalable output
• Contact sensors copper alloy momentary tap
  switches
• 9-4 Priority Encoder SN74LS147
• Converted 9-bit sensor data into 4-bit data
• Glolab GL-104 Encoder
• Converted the 4-bit data into serial stream for
  transmission
• Linx transmitter (2 different frequencies)
• 9 Volt battery and DC-DC converter

9
Hardware ImplementationReceiving Unit

• Two LINX receivers
• Two Glolab GL-104 decoders
• 4 MHz Resonator
• Voltage Detector Reset (VDR)
• Eight NPN transistors
• Parallel-Port cable

10
Hardware ImplementationFlow Diagram
Contact Sensors Accelerometer circuit
9-4 Encoder
Glolab GL-104 Encoder
Transmitter
9
4
1
Transmitting unit on one set of sparring
gear Powered by 9V battery
Receiver
Glolab GL-104 Decoder
Computer (PC) Software and interface
1
4
One Receiving Unit
11
Software Implementation

• Visual C with MFC
• User Interface

12
Changes From Original Design

• Exit condition for Threads
• Parallel-Port decoding done by Parallel-Port
  Thread
• Main loop used only for user interface
• Addition of Score updating and end of game
  condition check

13
New Program Flow Chart
Initialize
Initialize
Create Timer and Parallel-Port Threads
Initialize
Stop
Stop
Read Parallel Port
Handle User Interface
Change of State?
Yes
Display Timer
Update Screen
Exit?
Exit?
No
Yes
Exit?
Yes
Exit
No
Yes
End Time?
No
Exit Clean Up
Stop Reading Port?
No
Yes
Exit
Yes
14
Graphics

• Software used
• Poser 4.0
• 3D modeling
• Adobe PhotoShop 5.0
• Image touch-up

15
Testing Hardware

• Hardware
• Transmitter and receiver pairs
• GL-104 with T/R pair
• Accelerometer circuit
• Different gain values
• Parallel-port
• Using test program
• Software
• Manually
• Using test program

16
Problems and Challenges

• Insufficient Current for Parallel-Port
• Output from GL-104 Encoders 25mA
• Needed 30 to 40 mA
• Solution NPN transistors
• Inflexible Cables
• Shipping Delays
• Small Transmitting Unit hard to solder

17
What Went Right

• Good understanding of design and functionality of
  parts used
• Sensors properly embedded in sparring gear
• Transmission of correct data
• Correct digital data from sensors was transmitted
  and received
• Priority of data from sensors were correct
• Properly working software
• User-friendly interface
• Real-time graphics display of fight

18
What Went Wrong

• Didnt reach ultimate project goal to put on
  units and test in actual sparring situation
• Fragile transmitting unit and soldering
• Cumbersome sparring gear with long, inflexible
  wires

19
Lessons Learned

• Always have backup parts
• Importance of good organization and distribution
  of workload
• Mastery of soldering

20
Recommendations for Future Projects

• Make all sensors wireless
• More data from sensors
• No cumbersome wiring
• Streamlined and more user-friendly sparring unit
• Improve software
• 3D animation
• Include more fighting combinations

21
Questions Comments