On Tue, 12 Oct 2004, Ryan Supak wrote:

Hi, I'm messing with the [comport] object right now, trying to sketch out a subpatch to interpret raw MS serial mouse data since I can't get [serialmouse] to do anything. I'm using this link as my guideline: http://astronomy.swin.edu.au/~pbourke/dataformats/serialmouse/

The serialmouse abstraction uses serialctl to get the data from the serial port, translates them into float numbers and then the serial_ms external parses this stream of floats into mouse events.

serialctl is basically the same as comport, but it is older and linux only, therefore I advice not to use it.

The problem with serial mice is that you have to send them an initialisation message, otherwise they won't work. That might be the problem that you encounter.

Guenter

First, I used serial port monitoring software to ensure that the antique serial mouse I found is working -- it is.

Then, I create [comport], assign port 0 (COM1), 1200 baud, 7 bits, with no problem. When I try to assign 1 stop bit, it tells me that it could not assign it. However, that's not the real source of my confusion.

The real thing that's confusing me is that I guess I was imagining [comport] to have 9 outlets (one for each pin) or something. It appears to have only one outlet, and I can't get that outlet to do anything, no matter how much I wiggle the mouse.

Thanks for any suggestions! rs