1 / 15

Bowling Alley Communications

Bowling Alley Communications. Mark Patterson EKU Dept. of Technology, CEN. MOTIVATION. Cut down on time to fix lanes Eliminate unneeded communications Wanted project that was low budget. INTRODUCTION. Blackout communication has always been done the same way.

hao
Download Presentation

Bowling Alley Communications

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Bowling Alley Communications Mark Patterson EKU Dept. of Technology, CEN

  2. MOTIVATION • Cut down on time to fix lanes • Eliminate unneeded communications • Wanted project that was low budget.

  3. INTRODUCTION • Blackout communication has always been done the same way. • Never had any attempt at improvement. • No existing improvement found online. • Lot’s of wasted time as is.

  4. PROBLEM STATEMENT • Too much down time between when a lane messes up and when the mechanic is made aware of the problem. • Wasting time finding error code for each lane.

  5. PROPOSED SOLUTION • List steps taken to solve the problem such as: • Brainstorming (gist of ideas tried) • Proposed solution with justification • Arranging for software/hardware • Assembly • Testing & troubleshooting • Verifying results • This might continue on multiple slides

  6. Ideas • Interface the front display on machines for error codes. • Run signal from blackout lights to shop. • Hook buzzer up to alert mechanics. • Use encoder/decoder to cut down on wire.

  7. Hardware • Lots of wire • Breadboards • Logic Gates and Chips • LEDs or Lamps • 24VAC Relays • Power Supply

  8. Assembly • Created the circuit in MultiSim. • Tested in MultiSim and it worked. • Created the Encoder with Logic Gates. • Used a different Board for Decoder Chip • Tested in the Lab and they were working properly.

  9. Assembly (Cont)

  10. Implementation • Hooked relays up to 24VAC bulbs on the lanes. • Used relays as a switch to close inputs for the encoder.

  11. Implementation (Cont) • Ran communication line from lanes into mechanics area. • Hooked communication line to input for decoder.

  12. Troubleshooting • Had to get 6V batteries from the lab. • Had to use a wire to connect grounds on both boards. • Put a switchboard in to troubleshoot. Causing lanes to mess up just to troubleshoot took too long.

  13. Results • Got the encoder/ decoder to work. • Lot of troubleshooting.

  14. CONCLUSIONS • This will be very expensive to implement on all 32 lanes because of Relays. • A larger encoder/decoder, such as a 16:4 would work much better as it would save lot of money on wire. • Finding the right encoder would be far less troublesome.

  15. FUTURE WORK • I plan on extending this in some way to all 32 lanes in the future. • Questions, or Suggestions? • mark.patterson18@gmail.com

More Related