Any views expressed within media held on this service are those of the contributors, should not be taken as approved or endorsed by the University, and do not necessarily reflect the views of the University in respect of any particular issue.

Category: Meeting notes

2nd Meeting with Joe Hathway

27/05 Meeting Notes:

1. OSC Broadcast Implementation:
– Utilize OSC (Open Sound Control) broadcasting to transmit signals from the main node to all connected nodes simultaneously, eliminating the need for individual transmissions.

– Add “255” to the end of the IP address to enable broadcasting across the entire network, serving as the broadcast frequency.

2. NEED: USB-C Cable Requirement:
– Ensure each M5 device is equipped with a USB-C connection; therefore, we need to get 7 USB-C cables to facilitate connectivity.

3. Communication Testing with M5 Sticks:
– Conducted coding exercises to ascertain the capability of M5 sticks connected to the same network to exchange messages. Demonstrated successful data transmission between M5 sticks, validating the feasibility of custom code deployment for activating sounds or LEDs.

4. Light Testing Phase:
– Plan to conduct isolated testing of LED neopixels on M5 sticks.
– Incorporate the ‘adafruit.neopixel’ library into the codebase to enable control functions for the LEDs.
– For the code: Specify the ring’s LED count (12 LEDs) and develop an object to manage LED activation with customizable colours.
– Emphasize adjusting brightness levels (0 to 255) instead of simple on/off toggling to accommodate potential signal delays.

5. Integration of Additional Sensor:
– Investigate compatibility of an additional sensor with the M5 devices and network infrastructure, including potential connectivity to laptops.

6. Network Setup:
– Establish a designated M5 stick network named “m5node” with password “12345678” to facilitate seamless communication.
– Confirm successful message transmission and reception among M5 sticks.
– Observe functionality of light pulsing and color-changing sequences.

Next Steps to have before next meeting:
– Proceed with soldering the neopixels.
– Fine-tune data of M5 sticks on Max patch, then add that data to the code.

Meeting with David House

20/05/24

At this meeting, the following was discussed:

    • The location where the exhibit would take place.
    • The equipment needed.
    • The possible interactions with the main mushroom.
    • The UX for the audience.
    • Possible ways to better the Max files.

This diagram illustrates the main mushroom on the left connected to a laptop, which in turn is linked to an audio interface. Instead of relying solely on a single speaker or utilizing speakers provided by the location, the decision was made to enhance the immersive experience of the installation by employing smaller speakers, one for each node. Ideally, these speakers will be connected to the user interface using green XLR cables. This approach aims to improve users’ understanding of the correlation between light flickers and sound, as both will emanate from the same direction.

Showing 4 different poles of interaction.
Creating a diagram in which the node can be moved to.

 

 

 

 

 

 

 

In these diagrams, the concept of establishing four distinct “extremes of interaction” was investigated. The proposal suggests that along the North to South axis (up and down), the mushroom would maintain a balanced state of interaction, whereas along the West to East axis (left to right), it would exhibit a disrupted state. This disruption could be manifested through an increase in tempo in the corresponding sound. To facilitate user comprehension of this interaction and to deepen their understanding of the installation’s themes, the idea of creating a diagram depicting four factors that fungi favour or disfavour is explored, as depicted in the right image. For instance, if a node were oriented towards the west, resembling a sunny arid landscape, it would trigger the disrupted state, while orienting it towards water would induce the opposite effect.

During our exploration of potential locations, we visited rooms B14 and E15A. Following the tour, we concluded that B14 appealed to us more due to its aesthetic, characterized by broken walls and paint that align with our desired aesthetic. However, we had reservations about the space’s isolation in the ECA building and its popularity for other student projects. Conversely, this meeting took place in the Design and Digital Media room Q25, which features a storage area at the back, making it the most suitable option for our project for several reasons. Firstly, its accessibility facilitates regular work sessions leading up to the exhibit. Consequently, we settled on Q25.A as our chosen location.

Considering the compact size of Q25.A, we deliberated on the user experience of entering the space and conceived the idea of a U-shaped installation. This layout would allow users to enter the space without needing to navigate around it, enhancing accessibility and engagement.

Furthermore, we discussed the possibility of creating mushroom clusters instead of individual nodes. However, this decision remains unresolved, as the number of nodes will depend on the quantity of M5 sticks provided by Joe Hathaway.

Electrical components: Meeting with Joe Hathaway

  1. Node Components and Communication:
    • Each node requires a receiver component.
    • Using M5 Stick might be preferable due to code duplication ease.
    • Consider duplicating working code if one node setup proves successful.
    • Utilize OSC messages for sending signals over WiFi.
  2. WiFi Setup and Configuration:
    • Investigate UoE device network for WiFi connectivity.
    • Explore options for a portable WiFi writer to connect laptops and M5 Sticks.
    • If connecting the M5 Sticks to the university network proves challenging, an alternative solution would be to utilize the M5 Stick itself as a router.
    • In the M5 stick code configure network settings, passwords, and IP addresses for the laptop.
    • Ensure consistent port settings on Max for communication (if it says 8000 on the code it should be the same on Max).
  3. Communication Protocols:
    • Explore ESP Now for short-distance communication between M5 Sticks.
      • If not: Utilize OSC for communication over the same WiFi network.
  4. Hardware Considerations:
    • Code LED behavior, considering the required color and intensity and how it would look on the prototype.
    • Neopixel LED plates offer easier programming with only three pins.
    • Consider the limitations of Uno R3 boards, which require wired connections and may need extensive wiring if spaced out.
  5. Collaboration:
    • Collaborate with Joe Hathaway, who will script the setup based on LED plate specifications.
    • Investigate soldering requirements for LED plates, considering options like doing it at UCreate.
    • Provide detailed information to Joe, including expected reactions, working Max patch file, and inquiries about hardware availability.
  6. BONUS: Functionality and Customization:
    • Implement custom delays for delayed reactions, with a base of 1000 ms delay after having MVP ready.
    • Experiment with pulsing LED behavior, potentially adjusting pulse speeds for variation.
    • Consider individualized delays for each node after basic functionality is achieved.
  7. Additional Resources:
    • Access shared GitHub repository for references on ESP and OSC signaliging:  GitHub Repository

In summary:

We will be changing from Arduino to M5 sticks nodes because:

  • There is no need to have wires around the installation,
  • We can duplicate the code from the node.
  • It is easier to program with what we have.

Prototyping and the testing circuit

The purpose of this meeting was twofold: Firstly, to explore the feasibility of 3D printing the mushroom nodes. Agnes created a 3D file for this purpose, which was subsequently uploaded to the uCreate space machines.  Secondly, the meeting aimed to initiate hands-on work with the electrical components.

For this purpose, Agnes set up a circuit, while I reached out to John Hathaway to schedule a meeting for next week to seek further assistance. We anticipate needing help with soldering as well. Additionally, we expect all the LEDs to arrive next week, so by around Wednesday, we could commence assembling everything.

Summary of past 2 meetings

Meeting Notes:

Dates: 28th and 29th of February

1. Venue Selection:
– Consensus reached on utilizing the atrium at Alison House for the Mycelium Network experience.

2. Lighting Selection:
– Deliberation on using diode lights for the immersive experience.

3. Mother Mushroom Sensor and Node Aesthetics:
– The decision to retain the mother mushroom concept due to its efficiency with only one sensor.
– Exploring materials suitable for the stem’s flexibility and stability.

4. Node Aesthetics:
– Agreement on adopting a less realistic aesthetic, favouring an artistic approach such as paper lanterns for the nodes.

5. Visualization of Signaling Complexity:
– Brainstorming methods to represent various signalling types:
1. Stress signals
2. Food signals
3. Symbiotic relationships with other plants

6. Project Timeline:
– Acknowledgment of the five-week timeframe and the necessity for a detailed plan to ensure project completion. Therefore, we assigned roles:

  • Joe: produce sound examples for next week.
  • Agnes: design UX and visual of the exhibit after what was discussed.
  • Shirin: experiment with materials to bring to life the M5 stick mushroom.

Next Meeting: Wednesday 6th of March

Plan:

  • Choose exhibition hours and book it.
  • Get LEDs and try them out.
  • Look into booking a soldering workshop.

 

Prototyping – M5 stick and Max workshop with prof. Jules Rawlinson

Workshop on M5 and Max Usage: Mon Feb 12

During the workshop, it was discussed that the Arduino sketch retrieves various data bits from the device and transmits a message with an address, enabling the M5 stick to receive these values. The patch for submission 1 (due tomorrow) is nearly complete, requiring some adjustments and debugging.

Professor Jules outlined the following tasks:

    1. Address the high activity level of the M5 stick by implementing data smoothing.
    2. Develop a calibration routine to instruct Max on the usable range of the stick.

Fixes and Notes:

  • The gyro and accelerometer data are grouped, resulting in reduced activity.
  • The M5 stick oscillates between 0 and 90 and back to 0 degrees instead of 180.
  • To smooth the data, utilize sliding parameters (e.g., “slide 10 10”). However, for improved effectiveness, adjust to “slide 50 50” to obtain an average and stabilize the readings. Despite expectations, using smaller sliding numbers twice provides better filtering.
      • Ensure that the data types are specified as floats.
  • For scaling, designate numbers within the range of -90 to +90 degrees (e.g., “scale -90.90.0.1”). This instruction prompts the program to obtain values between 0 and 1, simplifying the scaling process.

    Patching the ‘data filtering’.
  • Given the intention to apply double sliding and scaling to other project components, this procedure will be patched. So if there needs to be a change it will update in all the places.
  • Developed a basic soundwave oscillator to input pitch data into the program.
      • When working with pitch, add 440 to achieve a final value of 220 at 440 if it’s halved.
  • After the initial motion-sound testing: The outcome indicates a lack of smoothness in the generated sound; the pitch fluctuates abruptly, stepping up and down.
  • For light, on Max, we would set which numbers equal ‘neutral’ blue or ‘disturbed’ red.
css.php

Report this page

To report inappropriate content on this page, please use the form below. Upon receiving your report, we will be in touch as per the Take Down Policy of the service.

Please note that personal data collected through this form is used and stored for the purposes of processing this report and communication with you.

If you are unable to report a concern about content via this form please contact the Service Owner.

Please enter an email address you wish to be contacted on. Please describe the unacceptable content in sufficient detail to allow us to locate it, and why you consider it to be unacceptable.
By submitting this report, you accept that it is accurate and that fraudulent or nuisance complaints may result in action by the University.

  Cancel