Kineme 2D Serial???

cwilms's picture

Does anyone know how Kinema sends their serial number when you buy from them? I have the purchase confirmation invoice email for Kineme 2D from Kosada (May 18th, 2012) but can't find the serial number anywhere to reinstall it.

Serial IO basic documentation?

vjsuperlight's picture

I am just starting with using Arduino connected to proximity sensors for controlling my quartz av performance. Is there some basic information about the settings for correct data input from arduino to quartz? ie. the data bits, stop bits, break string etc. I have the sensor data coming into quartz, but the data values skip/jitter around a bit dropping to 0 randomly. In the Arduino serial monitor, the data is consistently good.. but in quartz the same data jumps around a bit.. anyone have any hints on this behaviour? thank you

HRM data to QC

ginsu777's picture

hi. i am new here and I am obsessed with turning my HRM data into real-time graphics. I have the sparkfun polar board and it is all working quite well in processing over the serial/usb port (FTDI drivers)

i am trying to use the serial IO plugin to get the heartrate and graph to display in QC. any help would be appreciated, and I look forward to sharing what I have learned.

SerialIO problem with Arduino

tivonrice's picture


I've been playing around with Kineme's Serial Output, and I've had a very strange problem. My patch will only talk to the Arduino if I first open the Arduino software's serial monitor.

After doing this, I can close the Arduino app and communication is fine.

But, If I just run my patch without first running the Arduino app... nothing.

Any thoughts?


Serial IO patch flow control

ahoeben's picture

Thanks for the Serial IO patch. I am trying to use it to control (turn on/off) a projector. The protocol for the projector is pretty straightforward, but I am running into an issue.

I am using a Prolific PL2303-based USB-to-RS232 bridge. Most - if not all - USB-to-DB9 RS232 converters seem to be based on that chipset. Prolific has OS X drivers, but they seem to be unstable; they work fine using 'screen >/dev/tty.usbserial', but they lock up when piping output from the terminal to the port more than once, and when using them with the Serial IO patch.

I have found an open sourced alternative for the drivers that works lots better:

However I am still having a somewhat strange issue. If I use a terminal app ('screen', like above), I can control the projector just fine. When I use Quartz Composer and connect the serial port to another serial port using a null-modem cable, I can see that Quartz Composer outputs the correct characters over the serial port. But when I connect the serial cable to the projector, I can't get it to work; commands don't seem to get through. When I connect the serial port back to the null-modemed connection to the other computer, the serial connection is no longer working, even using screen instead of QC.

So somehow, even though QC is outputting the correct characters, and uses the correct timing, etc, it seems to lock up the serial port once connected to the projector. As a last straw, I am thinking that my 'screen-over-null-modem' has support for RTS/CTS hardware handshaking, whereas the projector does not implement flow control (I am not sure about that; grasping straws...). Could that be an issue? Is the Serial IO patch enforcing strict handshaking? Can I somehow configure the port not to use handshaking?