The following outlines each step data must take from the initial triggering to the actuation. Different groups are focusing on different portions of this process, and some in-between portions are being dealt with as they emerge.

1. Conductor creates/maps vibrobyte OSC data for display (GUI and input mapping in Max/MSP, PD, etc.)
2. Data is sent to remote spaces
   1. OSC Data is transmitted (ports must be open, remote space must have necessary hardware & software)
   2. (...continues as with local space)
3. Data is distributed at local space
   1. Data is packaged (from OSC into a form suitable for local transmission: serial packets, using Max/MSP, PD, etc.)
   2. Data is sent via serial to an Arduino
   3. Arduino echoes data to RF transmitter
   4. Each vibrobyte RF receiver sends packets to the microcontroller
   5. Each vibrobyte microcontroller interprets the packets and executes the command
      1. Outputs (vibrator motors) may be actuated (need to be attached to performers)
      2. LEDs may be triggered

• LEDs driven directly from the 168, no transistor, and one quad resistor
• DC/DC step up converter allows for multiple battery sources (2v->5v input)
• Correctly wired RF receiver
• Correctly wired LEDs
• Proper 3x2 ICSP header
• 2-position DIP switch with permanently "on" DC-DC converter
• Smaller SOIC output amplifiers instead of through-hole (1 amp / pwm output)
• Evenly bright LEDs
• Breakout into through-hole contacts for unused ADC and other IO (side of pcb)
• Freepcb bac files: LINK
• Freepcb schema files: LINK

1. Solder the 16 MHz crystal
2. Solder the diode, C1 (1uF) capacitors, 100 uF capacitor and MAX756
3. Solder the RJ-11 jack
4. Solder the 22 uH inductor
5. Test that the MAX756 is outputing 5V and using about 20-30 mA (pin 1 or 5)
6. C2 (22pF) capacitors, R1 (10.5 kOhm) resistor, ATmega 168 and DIP switch
7. Test that Pauline is using 30-40 mA
8. Add the ICSP header and try connecting with the AVRISPMKII
9. Add components for driving LEDs (quad resistor R2 and LEDs)
10. Upload PaulineBlink from the Arduino environment, the LEDs should flash (RGB, off, IR, off); if not:
    1. Check the resistance between the 168 side of the resistor and the positive terminal
    2. Check the resistance between the LED positive terminal and the 168
    3. Make sure the solder is clean around the quad resistor, and there is no cross-solder
11. Add components for driving output
12. Upload PaulineBuzz from the Arduino environment, the motors should buzz (output1, pause, output2, pause, output3, pause); if not:
    1. Check for cross-solder on the driver chips
    2. Make sure your motors are wired correctly
13. Add RX module

1. Connect the AVR ISP MKII to Pauline and open AVR Studio.
2. Go to Tools > Program AVR > Connect
3. Under "Main", select ATmega 168
4. Under "Program", select the "..." next to "Input Hex File" and select Pauline.hex
5. Hit the "Program" button
6. Under "Fuses", next to "EXTENDED", "HIGH" and "LOW" enter 0xF8, 0xDF and 0xFF (same as Arduino fuse bits)
7. Hit the "Program" button
8. Under "Lock Bits", next to "LOCKBIT" enter 0xCF (same as Arduino lock bits)
9. Hit the "Program" button

1. Change the above settings in AVR studio
2. Open C:\Documents and Settings\username\Application Data\Arduino\preferences.txt
3. Change "upload.using=bootloader" to "upload.using=avrispmkii"

If this doesn't work, you may need to disable the AVR Studio drivers and use the libusb drivers instead. There are some notes here on doing that.

1. When reprogramming or updating firmware, via the ICSP header, output 2 will oscillate.
2. When not in use, remove batteries from pauline to prevent parasitic draw (70ma). Pauline pcb's can stay in standby for well over 20 hours from 2 standard NiMH / NICD 2000mah rechargeable AA cells.
3. When choosing rechargeable batteries for performances, be sure to look for data regarding output current, and charging current, most unmarked AA / AAA style cells require overnight charging, whereas certain cells accept larger current charge rates.

• Addressing
• Mode recognition
• Multiple outputs
• Amplitude, Sustain and Frequency (with smooth switching)
• Reprogramming
• LED display
• Grouping
• Ask modes: blinkinput, blinkoutput, batterylife

Revision 3 breaks the basic 3-byte packet pattern of revisions 1 and 2. Packets are composed of anywhere from 3 to 8 bytes and are specialized for a continuous transmission system.

Every packet begins with a header byte followed by an address byte. Remaining bytes are optional and specified by the header.

The header byte takes the form 011a bcde

• a address type: 0 is single, 1 is group
• b-e packet includes output state, led state, modes, and group state, respectively

Notice that the header byte is the only byte to begin with a 0, distinguishing it from all other bytes.
The address byte takes the form 1aaa aaaa, with all bits a used for an address 0-127.

[Output State]

The output state is encoded in two bytes 1wwa aass 1fff fooo

• w wave shape
• a amplitude
• s sustain
• f frequency
• o outputs this applies to

[LED State]

The LED state is encoded in two bytes 11ir rrrg 1ggg bbbb

• i ir
• r red
• g green
• b blue

[Modes]

Output mode and LED mode is encoded in one byte 1111 ooll

• o output mode
• l led mode

[OSC Communications]

All OSC control packets begin with /vibrobyte.

Every float should be in the range [0, 1].

As per OSC-1.0, i is int32, f is float32, and s is string.

/vibrobyte/output ,sisfffiii dest-type dest wave amp sus freq out1 out2 out3
/vibrobyte/output/mode ,sis dest-type dest output-mode
/vibrobyte/led ,siffff dest-type dest ir red green blue
/vibrobyte/led/mode ,sis dest-type dest led-mode
/vibrobyte/group/add ,sii dest-type dest group
/vibrobyte/group/remove ,sii dest-type dest group
/vibrobyte/group/reset ,si dest-type dest

• dest-type destination type for this message, takes the values {single, group}
• dest
  • when dest-type is single, a vibrobyte address
  • when dest-type is group, a group number
• wave is the wave shape, takes the value {square, saw-ascending, saw-descending, absolute-sine}
• amp is the amplitude of the wave
• sus is the sustain of the wave
• freq is the frequency of the wave
• out1, out2 and out3 are boolean values describing which outputs this message applies to
• output-mode takes the value {repeat, impulse, off}
• led-mode takes the value {battery, quality, blinkinput, blinkoutput}
• group is a group number, (starting with group 1, group 0 is reserved for referring to all vibrobytes)

Place in jsui-library folder.

Accepts:

• floats: changes the intensity (0 is off, 1 is on)
• setcolor: changes LED color
• setbgcolor: changes background color
• setdiameter: changes the LED diameter

Outputs:

• float: the intensity of the led, can be toggled between 0 and 1 by clicking

Color and size can be specified via the jsui Inspector window arguments field. Right-click and drag to change intensity. Hold shift for fine adjustment.

Tele-Morphosis (excerpt) from Kyle McDonald on Vimeo.

Vibrobyte Transmitter Demo from Kyle McDonald on Vimeo.