1 / 16

System for Engine Location Of a Web Train

System for Engine Location Of a Web Train. Paul Wimmer and Adam Weintrop Dr. Irwin and Dr. Schertz 2/20/06. Outline. Current position on time line Accomplishments of last week Goals for next week. Time Line. Outline. Current position on time line Accomplishments of last week

derora
Download Presentation

System for Engine Location Of a Web Train

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. System for Engine Location Of a Web Train Paul Wimmer and Adam Weintrop Dr. Irwin and Dr. Schertz 2/20/06

  2. Outline • Current position on time line • Accomplishments of last week • Goals for next week

  3. Time Line

  4. Outline • Current position on time line • Accomplishments of last week • Goals for next week

  5. Last Week • Recoded all DCC generation software • Much more efficient and useful • 3 Tier Menu: • Select Train (Blue/White) • Select Direction (Foreword/Backward) • Select Speed (0-9) • Problems with White Train • Tested the new transformers • Organized software program flow

  6. Results The results of the transformer circuit (200 turn sensor and 1 MOhm terminating resistor) -With Train off track ~30 mV -With Train idle on track ~130 mV -With Train running ~upwards of 1 V Could use resistor in engine to increase off / idle voltage range -May not be necessary with 100mV difference

  7. Program Flow • 7 Primary modules/functions • Main • Compare positions • Dx • Dt • Velocity • Basic Collision Avoidance? • Relay to PC?

  8. Main • Change MUX inputs • Test each MUX ouptut • Determine if the train is on a given section of track • Code is written, not done troubleshooting

  9. Compare • Compares the new position to the previous position • Further action is only taken if the position has changed • No relevant info if position is the same

  10. Dx • Distance traveled by the train • Based on: • New track section • Old track section • Direction (when necessary) • Table? Set of loops and if statements?

  11. Dt • Determine the time that the train took to cross the last track section • Stop a timer upon entrance of a section • Extract the values • Start up the next timer • A certain amount of overflow = idle train

  12. Speed • Dx/Dt determined in C in floating point • Conversion to an 8 bit integer (char) • An averaging algorithm may be implemented (time permitting)

  13. Collision Avoidance • If a train is approaching another: • Send out an e-stop (if on same processor as the DCC signal) • Warn user (if a GUI is setup in Java) • Kill the power --> the most practical method

  14. Back to PC • Time permitting: • Transfer values from EMAC to PC • Create a GUI in JAVA

  15. Outline • Current position on time line • Accomplishments of last week • Goals for next week

  16. Problems to Address for Next Week • Finish hardware (comparators, multiplexers) • Interface with software • Test hardware and software I/O • Write more independent software functions • Divide them up between us • Latch or Sample and Hold hardware?

More Related