The text is terminated by a newline character (10) or a return (13). Remember that what is happening is that individual bytes are arriving, one at a time, and need to be assembled into a line of text.
It uses a Pure Data loop to assemble the message (which is a line of text) and then uses FUDI (Fast Universal Digital Interface) to parse the text and extract a message which is then routed to the appropriate destination. The patch decodes the input message and routes it to the required destination. At the bottom of the patch you can see a data flow coming out of the comport object and ending in a rather enigmatic way. My blog post here shows how to get a Pure Data patch to receive data from a com port. The Python code that sends these messages is: The encoder message is generated by Circuit Python running inside a PICO which is connected to the encoders and sends messages out over the serial port. The second number (5) is the number of the encoder. The word encoder tells the receiver that a new encoder value is coming The first number (97) is the new encoder value. The controller generates messages like this when an encoder is turned. Lets take a look at the kind of message that I might want to send from the controller to a Pure Data patch: It’s a very simple text based protocol which means that it will be very easy to make the PICO assemble FUDI messages for the Pure Data patch to read. He’s invented the FUDI protocol for sending messages. The man behind Pure Data (Miller Puckette) has thought of this. Now I want to see about sending packets of useful data. Last time I got the comport working now that I can send raw data bytes between the devices. Isn’t this exciting? I’m just on the brink of sending useful messages between my PICO powered controller (which has buttons and a display) and a Pure Data patch running on a Raspberry Pi.
0 kommentar(er)
