UDP, the "User Datagram Protocol," is the Internet Protocol for sending packets (a.k.a. "datagrams") between machines without establishing a connection between the machines and without any expensive mechanism for detecting lost packets and retrying them. UDP is used for streaming video and audio and many other applications on the Internet.OpenSound Control is an application-level protocol. OSC defines only the bit format and interpretation of those bits; you could transmit OpenSound Control messages via UDP, TCP, shared memory, compact disc, or any other digital protocol.Because UDP can be used to transmit many kinds of data besides OSC, and because OSC can be transmitted by many kinds of networking technology besides UDP, our implementation puts the UDP part and the OSC part in separate objects. People have used the OTUDP object without the OpenSoundControl object to send and receive data in formats other than OSC. (This requires writing a max external to translate between Max data and binary data in the non-OSC format.) People have used OpenSoundControl without UDP as a sort of super pack/unpack, to be able to pass entire OSC bundles as single Max messages.Nevertheless, the main use of both the OTUDP and OpenSoundControl Max objects is to use them together, as shown by the help patches

Assuming that you configured your IpSonCompact to send the OSC strings to port 8000, you start your patch with reading port 8000. In the example on the right, I used the otudp read object. There are more udp objects around, depending on which Max/Msp version you work with and what kind of computer you have (Intel / PowerPC). I still work with Max/Msp version 4.5.4. on a powermac G4. You can download all the objects from the Berkely website. Check it out. For checking the communication, you can connect a print object to the output of the udp read object and see wether data is flowing in.

The output of the otudpread object is connected to the opensoundcontrol object. The osc-route object is used to filter the data. On the left outlet all data with /ic in the header will be put out. The middle output for /cr. The right outlet is not used for the IpSonCompact.

This is the IpSonCompact testpatch.
With this patch you can fully control the IpSonCompact interface.

OSC communication
In the left upper corner, you can see the [otudp-read 8000] object. This max-object (part of max 4.5.x] reads the incoming data on local port 8000 (the port where the IpSonCompact is streaming it's data to.

In the corner left down, the [otudp-write 10.1.60.37 10001] max-object is placed. This object sends all streaming data coming from the patch to ip address 10.1.60.37, port 10001. This is ofcourse the port of the IpSonCompact.

Analog sensor input
The darkgrey block in the middle represents the microcontroller (pic18f4420) chip on the printed circuit board; it actualy has the same pinout. The yellow numberboxes represent the incoming sensor data (0-1024). The 'gray boxes above can be changed; it represents the threshold of that input. When this values is changed, it should be 'SET' by pressing (clicking) the SET button on the left.

Distance measurement
The green number boxes represent the distance measurement values (only in0, in1 and in2) and the digital input (4 switch values of 0/1). In case of switch in/out, the little yellow led indicators, will light up when a switch is pushed. When the configuration is made active for using three distance sensors, the green number boxes will show the 8 bit value.

IpSonCompact configuration
In the little gray block in the left corner, adjustments can be made for the timing of the sample rate and switching on/off the distance measurment on in0, in1 and in2. For the values, check the tables on this page. Every change made, should be followed by a click on the SET button. This sends the /cf string to the IpSonCompact. By sending the /cf string, the IpsonCompact always responds with the values set within the eeprom. The values are displayed within the 'pink' number boxes. In this way you can always verify whether the processor does have the right values set.

Driving Ouputs On/Off or Pulse Width Miodulation
With the 14 faders, 8bit values can be send to the IpSonCompact which will be converted into pulse width modulation signals. Now, the outputs can drive all kind of processes (like light, dc engines and lots more). Whether the output is on/off or pwm, is determined by the settings of the button right underneath the faders. By clicking on the red 'switches' the outputs can be set 'high (=5V) or 'low' (=0V).

The little gray block in the middle does have 3 buttons. With status, the acual status can be 'requested' of the IpSonCompact. The mute all button, does 'mute' all the outputs to zero. With the recall button, the status of the IpSonCompact can be requested; you can use this feature right after you switch on the IpSonCompact and you do want to restore the latest values used.

Connecting Inputs and Outputs
We are working on a version where the inputs can be connected to the outputs within a matrix. In this way you can easily drive processes and make nice feedback.

Assuming that you configured your IpSonCompact (xport) to send the OSC strings to port 8000, you start your patch with reading port 8000. On the right a example of how to read port 8000 with PD. The output of the dumpOSC object is filtered with OSCroute /ic and OSCroute/cr. The ouputs of the route objects are sent to the right location within the patch, to extract all data.

For the first initial read, the connection has to be made with the IpSonCompact. When the object 'connect' is pushed, the connection will be made. The IP-address within the object is the address of the IpSonCompact.