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.

Electrical components: Meeting with Joe Hathaway / dmsp-perception24 by is licensed under a