1 / 32

SD May06-18

IOWA STATE UNIVERSITY Department of Electrical and Computer Engineering Computer Control of Theater Performance Electronics. SD May06-18. May06-18 Team. Tarun Bhatia Amanda Farniok Sheng Ly Alex Sills. Project Client . Iowa State Dance Janice Baker Co-Motion Dance Company

camdyn
Download Presentation

SD May06-18

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. IOWA STATE UNIVERSITYDepartment of Electrical and Computer EngineeringComputer Control of Theater Performance Electronics SD May06-18

  2. May06-18 Team • Tarun Bhatia • Amanda Farniok • Sheng Ly • Alex Sills

  3. Project Client • Iowa State Dance • Janice Baker • Co-Motion Dance Company • Valerie Williams

  4. Project Advisory Board • Faculty Advisors • Dr. Julie Dickerson • Dr. Gerald Sheble • Emeritus Faculty • Dr. David Stephenson

  5. Purpose • Provide clients with better control of their performance environment

  6. Reason • The environment can be manipulated as an interpretive, active portion of the artistic dance performance. With this design, up to four dancers can be identified on the stage by their transmitter and their input will manipulate the environment settings.

  7. Method • Using Isadora • It takes input from “sensors” to “Actors”

  8. Method Contd • Use electronic sensors on dancer’s body to transmit information to a computer • The computer will take the data and use the information to control settings of video, sound, and lighting predetermined by the performers

  9. Previous Research Project • VrJuggler was previously used on a research project to manipulate input from sensors and display 3D video on projectors. • Certain aspects of previous research was taken into consideration. • The old hardware was reviewed to be used for the initial development of our hardware solution • Software setup to read sensors was managed through past documentation and research papers

  10. Hardware Layout

  11. Hardware Design - Research • Analog audio wireless transmission method • Problems: Modulation/compression issues, capacity/channel issues, possible interference problems

  12. Hardware Design - Research • Industrial SCADA-type wireless transmission method • Problems: Bulky packaging, insufficient channels/capacity, possible software (Isadora) compatibility issues

  13. Hardware Design - XBow • Crossbow “Mote” Transmission Method • Reasons for choice: Compact sizing, 2.4GHz band avoids interference and allows for multiple transmitters, TinyOS accompanying software suited for project goals • Possible problems: TinyOS/Isadora communication, line of sight issues

  14. Hardware Design - XBow

  15. Analog Output Circuit • Crossbow motes accept analog inputs • Flex sensor variable resistors used in a simple analog circuit to give 1.0-2.5 Volt output to mote board

  16. Circuit Diagram - Four Sensor Output

  17. MDA300 Sensor Board • Accepts analog inputs via screw terminals • Provides excitation voltages, power supplies for analog circuit • Converts analog to digital signal for wireless transmission

  18. MICAz Transceivers • Connects to sensor board and serial interface with 51-pin connector • Transmits on 2.4 GHz Zigbee compliant band (good range, multiple channels, minimal interference problems) • Powers sensor board, simple AA battery power supply

  19. MIB510 Serial Interface • Receives signal from transceiver and transmits to computer through TinyOS software • Powered by external AC adapter • Through TinyOS, programs/configures transceivers and sensor board

  20. Hardware Software Integration • TinyOS is a platform bridges the hardware serial input and xmidi. • Xmidi - XML Musical Instrument Digital Interface • XML Representation of MIDI data • Isadora recognizes MIDI as an input.

  21. Isadora SDK • Provides overall design needed for working Isadora Plugin/Actor. • Provides data structures and functions that are needed to implement.

  22. Isadora Data Structure Implementation How Do We Do It? • Important Data Structures PluginInfo { // Struct that contains variables unique to this plugin ActorInfo* mActorInforRef. //ptr to our ActorInfor MessageReceiveRef mMessageReceiver //ptr to our msg reciever int sensorInput //input sensor to read from int lowerThreshold //input min limit int maxTheshold //input max limit float triggerThreshold //input threshold for on/off float scaledOutput //output scaled for flex float trigger //output for on/off }

  23. Isadora SDK Function • Unique Function Logic static void ReceiveMessage( IsadoraParameters* ip, //ptr to MessageMask // Message to listen to PortIndex // applicable to midi const MsgData* // data to read UInt32 // length of data for the message long inRefCon //ptr to our Actor info )

  24. Other Data Structures Isadora Actor Group Identification - static const OSType kActorClass Unique 4 letter id for Isadora actor - static const OSType kActorID Name for the actor used in Isadora - static const char* kActorName Defines the input and output for the actor in Isadora static const char* - static const char* sPropertyDefinitionString Contains information regarding the input and output and Actor info - const char* sHelpStrings[]

  25. Isadora Functions - Minor • Isadora Standard functions with minor data Called when an input parameter value is changed, just reload with new data - static void HandledPropertyChangeValue() Function that gets the area needed to draw the actor in Isadora, bases on # of input and outputs - static Boolean GetActorDefinedArea()

  26. Isadora Functions Standard Function called when actor is required to be drawn in Isadora - static void DrawActorDefinedArea() Gets Actors class and id and also all the ptrs to all the plugins functions - EXPORT_ void GetActorInfo() Getter function for the Parameter Sting - static const char* GetParameterString() Getter function the Help Strings - static void GetHelpString() Function that instantiates the actor - static void CreateActor() Function that destroys the actor when deleted, scene is closed, or actor is cut - static void DisposeActor() Sets the activate flag true or false depending if the actors scene is activated - static void ActivateActor()

  27. General Flow of the Functions

  28. Isadora Actor Mockup Our Actor Mockup Actor Link Connection

  29. Putting the Pieces Together • Integration between hardware and software will be completed using the research and documentation available. • Testing will be done with trial components on lend from the Department of Electrical Engineering to assure products to be purchased will function correctly under all requirements.

  30. Expected Product Deliverables • An alpha version delivered February for use in March. • Consist of a transmitter/receiver set for one dancer • By the first week of May, a finalized version of software and hardware will be released

  31. Coming Up Next • Writing SDK for actors specified by our client • Find testing software for borrowed hardware • Implementing hardware design for final product demonstration • Evaluate using test cases

  32. Any Questions?

More Related