WiTilt


    Aug 21 2006 | 8:08 pm
    I was talking to Stefan Prosky at SIGGRAPH and he turned me on to the WiTilt from Spark Fun, which I've been playing with a little bit over the last few days. Stefan mentioned that he was having trouble parsing the data, and Tom Igoe's article at ITP mentioned something similar. So, here's a little patch that does simple parsing of the raw data coming out of the thing. Might be useful to someone out there.
    jb

    • Aug 22 2006 | 1:54 pm
      this is a thread i opend on using max and witilt. http://www.sparkfun.com/cgi-bin/phpbb/viewtopic.php?t=2727
      a third solution to the problem, regexp... nice!
      2006/8/21, Jeremy Bernstein :
      > I was talking to Stefan Prosky at SIGGRAPH and he turned me on to the > WiTilt from Spark Fun, which I've been playing with a little bit over > the last few days. Stefan mentioned that he was having trouble > parsing the data, and Tom Igoe's article at ITP mentioned something > similar. So, here's a little patch that does simple parsing of the > raw data coming out of the thing. Might be useful to someone out there. > > jb > > #P window setfont "Sans Serif" 9.; > #P window linecount 1; > #P comment 154 387 100 196617 Z; > #P comment 117 387 100 196617 Y; > #P toggle 82 185 15 0; > #P newex 82 203 29 196617 gate; > #P toggle 184 185 15 0; > #P newex 184 203 29 196617 gate; > #P comment 287 78 100 196617 > #P number 152 367 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0; > #P number 116 367 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0; > #P number 80 367 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0; > #P newex 80 342 67 196617 unpack 0 0 0; > #P newex 337 268 20 196617 t b; > #P newex 296 211 40 196617 t clear; > #P newex 337 242 67 196617 match 10 13; > #P newex 337 179 48 196617 bucket 2; > #P message 265 77 20 196617 32; > #P newex 32 315 202 196617 regexp .*X=(\\d+).*Y=(\\d+).*Z=(\\d+); > #P newex 142 279 40 196617 itoa; > #P newex 142 250 67 196617 zl group 240; > #P message 265 51 20 196617 49; > #P toggle 77 48 15 0; > #P newex 77 71 57 196617 qmetro 20; > #P newex 82 226 54 196617 print data; > #P newex 184 226 63 196617 print status; > #P newex 142 116 71 196617 serial e 9600; > #P comment 288 51 100 196617 > #P comment 78 387 100 196617 X; > #P window linecount 4; > #P comment 269 363 169 196617 This patch simply reads the default > data out of the WiTilt. In the other modes of the device , it could > serve as a resonable model for extension.; > #P connect 10 0 11 0; > #P connect 7 0 6 0; > #P connect 11 1 17 0; > #P connect 17 0 18 0; > #P connect 25 0 24 0; > #P connect 24 0 5 0; > #P fasten 3 0 24 1 147 192 106 192; > #P connect 17 1 19 0; > #P connect 6 0 3 0; > #P fasten 12 0 3 0 270 98 147 98; > #P fasten 8 0 3 0 270 71 147 71; > #P connect 3 0 9 0; > #P fasten 16 0 9 0 342 294 281 294 281 173 147 173; > #P connect 9 0 10 0; > #P connect 17 2 20 0; > #P connect 23 0 22 0; > #P connect 22 0 4 0; > #P connect 3 1 22 1; > #P connect 13 0 15 0; > #P fasten 3 0 13 0 147 137 342 137; > #P connect 13 0 14 0; > #P connect 13 1 14 0; > #P connect 15 0 14 0; > #P connect 14 0 16 0; > #P window clipboard copycount 28; > >
    • Aug 22 2006 | 3:20 pm
      the WiTilt looks really interesting - can you give us a little run- down on your experiences with it, when you've had a good chance to play with it?
      thanks, evan
      On Aug 21, 2006, at 9:08 PM, Jeremy Bernstein wrote:
      > I was talking to Stefan Prosky at SIGGRAPH and he turned me on to > the WiTilt from Spark Fun, which I've been playing with a little > bit over the last few days. Stefan mentioned that he was having > trouble parsing the data, and Tom Igoe's article at ITP mentioned > something similar. So, here's a little patch that does simple > parsing of the raw data coming out of the thing. Might be useful to > someone out there. > > jb > > #P window setfont "Sans Serif" 9.; > #P window linecount 1; > #P comment 154 387 100 196617 Z; > #P comment 117 387 100 196617 Y; > #P toggle 82 185 15 0; > #P newex 82 203 29 196617 gate; > #P toggle 184 185 15 0; > #P newex 184 203 29 196617 gate; > #P comment 287 78 100 196617 > #P number 152 367 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0; > #P number 116 367 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0; > #P number 80 367 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0; > #P newex 80 342 67 196617 unpack 0 0 0; > #P newex 337 268 20 196617 t b; > #P newex 296 211 40 196617 t clear; > #P newex 337 242 67 196617 match 10 13; > #P newex 337 179 48 196617 bucket 2; > #P message 265 77 20 196617 32; > #P newex 32 315 202 196617 regexp .*X=(\\d+).*Y=(\\d+).*Z=(\\d > +); > #P newex 142 279 40 196617 itoa; > #P newex 142 250 67 196617 zl group 240; > #P message 265 51 20 196617 49; > #P toggle 77 48 15 0; > #P newex 77 71 57 196617 qmetro 20; > #P newex 82 226 54 196617 print data; > #P newex 184 226 63 196617 print status; > #P newex 142 116 71 196617 serial e 9600; > #P comment 288 51 100 196617 > #P comment 78 387 100 196617 X; > #P window linecount 4; > #P comment 269 363 169 196617 This patch simply reads the default > data out of the WiTilt. In the other modes of the device , it > could serve as a resonable model for extension.; > #P connect 10 0 11 0; > #P connect 7 0 6 0; > #P connect 11 1 17 0; > #P connect 17 0 18 0; > #P connect 25 0 24 0; > #P connect 24 0 5 0; > #P fasten 3 0 24 1 147 192 106 192; > #P connect 17 1 19 0; > #P connect 6 0 3 0; > #P fasten 12 0 3 0 270 98 147 98; > #P fasten 8 0 3 0 270 71 147 71; > #P connect 3 0 9 0; > #P fasten 16 0 9 0 342 294 281 294 281 173 147 173; > #P connect 9 0 10 0; > #P connect 17 2 20 0; > #P connect 23 0 22 0; > #P connect 22 0 4 0; > #P connect 3 1 22 1; > #P connect 13 0 15 0; > #P fasten 3 0 13 0 147 137 342 137; > #P connect 13 0 14 0; > #P connect 13 1 14 0; > #P connect 15 0 14 0; > #P connect 14 0 16 0; > #P window clipboard copycount 28; >
    • Aug 22 2006 | 6:57 pm
      we use the witilt for tracking a conductors hand inertia. for a good read on the subject of motion capture i recommend Motion Tracking: No Silver Bullet, but a Respectable Arsenal>>
      2006/8/22, evan.raskob [lists] : > > the WiTilt looks really interesting - can you give us a little run- > down on your experiences with it, when you've had a good chance to > play with it? > > thanks, > evan > > > > On Aug 21, 2006, at 9:08 PM, Jeremy Bernstein wrote: > > > I was talking to Stefan Prosky at SIGGRAPH and he turned me on to > > the WiTilt from Spark Fun, which I've been playing with a little > > bit over the last few days. Stefan mentioned that he was having > > trouble parsing the data, and Tom Igoe's article at ITP mentioned > > something similar. So, here's a little patch that does simple > > parsing of the raw data coming out of the thing. Might be useful to > > someone out there. > > > > jb > > > > #P window setfont "Sans Serif" 9.; > > #P window linecount 1; > > #P comment 154 387 100 196617 Z; > > #P comment 117 387 100 196617 Y; > > #P toggle 82 185 15 0; > > #P newex 82 203 29 196617 gate; > > #P toggle 184 185 15 0; > > #P newex 184 203 29 196617 gate; > > #P comment 287 78 100 196617 > > #P number 152 367 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0; > > #P number 116 367 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0; > > #P number 80 367 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0; > > #P newex 80 342 67 196617 unpack 0 0 0; > > #P newex 337 268 20 196617 t b; > > #P newex 296 211 40 196617 t clear; > > #P newex 337 242 67 196617 match 10 13; > > #P newex 337 179 48 196617 bucket 2; > > #P message 265 77 20 196617 32; > > #P newex 32 315 202 196617 regexp .*X=(\\d+).*Y=(\\d+).*Z=(\\d > > +); > > #P newex 142 279 40 196617 itoa; > > #P newex 142 250 67 196617 zl group 240; > > #P message 265 51 20 196617 49; > > #P toggle 77 48 15 0; > > #P newex 77 71 57 196617 qmetro 20; > > #P newex 82 226 54 196617 print data; > > #P newex 184 226 63 196617 print status; > > #P newex 142 116 71 196617 serial e 9600; > > #P comment 288 51 100 196617 > > #P comment 78 387 100 196617 X; > > #P window linecount 4; > > #P comment 269 363 169 196617 This patch simply reads the default > > data out of the WiTilt. In the other modes of the device , it > > could serve as a resonable model for extension.; > > #P connect 10 0 11 0; > > #P connect 7 0 6 0; > > #P connect 11 1 17 0; > > #P connect 17 0 18 0; > > #P connect 25 0 24 0; > > #P connect 24 0 5 0; > > #P fasten 3 0 24 1 147 192 106 192; > > #P connect 17 1 19 0; > > #P connect 6 0 3 0; > > #P fasten 12 0 3 0 270 98 147 98; > > #P fasten 8 0 3 0 270 71 147 71; > > #P connect 3 0 9 0; > > #P fasten 16 0 9 0 342 294 281 294 281 173 147 173; > > #P connect 9 0 10 0; > > #P connect 17 2 20 0; > > #P connect 23 0 22 0; > > #P connect 22 0 4 0; > > #P connect 3 1 22 1; > > #P connect 13 0 15 0; > > #P fasten 3 0 13 0 147 137 342 137; > > #P connect 13 0 14 0; > > #P connect 13 1 14 0; > > #P connect 15 0 14 0; > > #P connect 14 0 16 0; > > #P window clipboard copycount 28; > > > >
    • Aug 22 2006 | 9:04 pm
      I tried to use font aerial (ttfont)and as it's written max window active changes in aerial but my patcher still reloads geneva instead . I tried to change that by moving the font in different folder from the font book and correct all my double problems but blabla. Any idea could be nice? Try to change to other fonts and didn't get the problem so why did i choose the one who loads weirdly. If ever someone has an idea Well i could change the font i would like to use... OSX.4.7 17" PPC MM 4.5.7 J1.5.2 Thanks Hubert
    • Aug 22 2006 | 10:20 pm
      Take a look at init/max-fontmappings.txt.
      You'll have to edit that file if you want to see Arial on Mac OS.
      On 22-Aug-2006, at 23:04, Hubert PICHOT wrote:
      > I tried to use font aerial (ttfont)and as it's written max window > active changes in aerial but my patcher still reloads geneva instead . > I tried to change that by moving the font in different folder from > the font book and correct all my double problems but blabla. > Any idea could be nice? > Try to change to other fonts and didn't get the problem so why did > i choose the one who loads weirdly. > If ever someone has an idea > Well i could change the font i would like to use... > OSX.4.7 17" PPC MM 4.5.7 J1.5.2 > Thanks > Hubert >
      -------------- http://www.bek.no/~pcastine/Litter/ ------------- Peter Castine +--> Litter Power & Litter Bundle for Jitter Universal Binaries on the way iCE: Sequencing, Recording & Interface Building for |home | chez nous| Max/MSP Extremely cool |bei uns | i nostri| http://www.dspaudio.com/ http://www.castine.de
    • Aug 22 2006 | 11:00 pm
      Thanks Pete but.....
      It is Font AERIAL with an e. AERIAL
      Well open Max4preferences folder file maxoptions
      max setoption deffont 4242 12 "Gill Sans"; + blabla everything works fine each time i make a new object it's in gill sans
      When i change it in AERIAL max setoption deffont -16452 9 Aerial; + blabla
      ..put some quotes on it or delete the minus sign but hell of that font it loads in aerial on max window
      but my new object is still in geneva.
      So i write my object and then select aerial everything is fine
      The odd of the thing is that even my FTM image on loading is using aerial font but not my new objects
      Tried in the init file and changed every fonts in init file looks like this now
      max system windows genericfontmap "Sans Serif" Arial; max system windows genericsavefontmap Arial "Sans Serif"; max system macintosh genericfontmap "Sans Serif" Aerial; max system macintosh genericsavefontmap Aerial "Sans Serif"; max system windows genericfontmap "Fixedwidth Serif" "Courier New"; max system windows genericsavefontmap "Courier New" "Fixedwidth Serif"; max system macintosh genericfontmap "Fixedwidth Serif" Aerial; max system macintosh genericsavefontmap Aerial "Fixedwidth Serif"; max system windows genericfontmap "Proportional Serif" "Times New Roman"; max system windows genericsavefontmap "Times New Roman" "Proportional Serif"; max system macintosh genericfontmap "Proportional Serif" "Aerial"; max system macintosh genericsavefontmap "Aerial" "Proportional Serif";
      do i have to take sans serif words out and what about the quotes???
      No way So is there anywhere in the lines a specific order for new created object to use the font geneva by default when there is a problem?? Does anyone know what's going on???
      Well seems boring but my webdesigner wants to build using this font may be it's going to be easier to change his mind afterall
      Cheers`
      Hubert
    • Aug 23 2006 | 9:39 am
      On 23-Aug-2006, at 1:00, Hubert PICHOT wrote: > Thanks Pete but.....
      Je m'appelle Peter.
      > It is Font AERIAL with an e. AERIAL
      Sorry, in your message yesterday I assumed that was just a typo since Arial is such a common font *and* use of Arial would match the symptoms you reported exactly.
      In this case I would leave the max-fontmappings.txt file alone. However, It would be worth saving a patch with your font problems in text format to see how the font is being saved. You'll see lines like
      scattered through the file, with FFFF replaced by the font name and SSSS by the font size. Are you seeing Aerial or "Sans Serif"?
      I am wondering if, somehow, your Aerial font (with Ae) is managing to convince the OS and/or Max that it is really a synonym for the more common Arial (no e). I seem to recall that there are mechanisms for font aliases & substitution, although it has been ages since I've looked at this stuff.
      > what about the quotes???
      These are messages to Max. The font name is being represented as a Max symbol. Use quotes if there is a space embedded in the font name, no quotes if there are no embedded spaces.
      > Well seems boring but my webdesigner wants to build using this font > may be it's going to be easier to change his mind afterall
      It might be easier--and, indeed, better--to shoot your web designer.
      -- Peter
      -------------- http://www.bek.no/~pcastine/Litter/ ------------- Peter Castine +--> Litter Power & Litter Bundle for Jitter Universal Binaries on the way iCE: Sequencing, Recording & Interface Building for |home | chez nous| Max/MSP Extremely cool |bei uns | i nostri| http://www.dspaudio.com/ http://www.castine.de
    • Aug 24 2006 | 12:08 am
    • Aug 26 2006 | 2:19 pm
      Hi Jeremy,
      Like your patch - thanks.
      I have been trying to get the WiTilt to work with a dual AMD XP machine running a Blue Soleil BlueTooth dongle.
      The system sees the device and I can query and read date from hyperterminal, but when I bang the serial object in the max patch, Max freezes and I have to reboot.
      WiTilt is showing up on Comm 5 but the serial object, when asked to report, says it only sees Comm 4. Of course any attempts to move the Blue Tooth device to Comm 4 have failed.
      Any ideas - did you have similar problems and/or are you using different hardware for the Platform and Bluetooth receiver?
      Thanks,
      Keith
      Jeremy Bernstein wrote: I was talking to Stefan Prosky at SIGGRAPH and he turned me on to the WiTilt from Spark Fun, which I've been playing with a little bit over the last few days. Stefan mentioned that he was having trouble parsing the data, and Tom Igoe's article at ITP mentioned something similar. So, here's a little patch that does simple parsing of the raw data coming out of the thing. Might be useful to someone out there.
      jb
      Keith McMillen BEAM Foundation http://www.beamfoundation.org/ 510.502.5310
    • Aug 27 2006 | 7:10 am
      keith, read my report on the sparkfun forum for (possible) solution for your com problem. in short, if witilt is recognized as com5 then follow the English lettering to find the corresponding letter. [serial e 9600] should then work
      2006/8/26, Keith McMillen : > > Hi Jeremy, > > Like your patch - thanks. > > I have been trying to get the WiTilt to work with a dual AMD XP machine > running a Blue Soleil BlueTooth dongle. > > The system sees the device and I can query and read date from > hyperterminal, but when I bang the serial object in the max patch, Max > freezes and I have to reboot. > > WiTilt is showing up on Comm 5 but the serial object, when asked to > report, says it only sees Comm 4. Of course any attempts to move the Blue > Tooth device to Comm 4 have failed. > > Any ideas - did you have similar problems and/or are you using different > hardware for the Platform and Bluetooth receiver? > > Thanks, > > Keith > > > *Jeremy Bernstein * wrote: > > I was talking to Stefan Prosky at SIGGRAPH and he turned me on to the > WiTilt from Spark Fun, which I've been playing with a little bit over > the last few days. Stefan mentioned that he was having trouble > parsing the data, and Tom Igoe's article at ITP mentioned something > similar. So, here's a little patch that does simple parsing of the > raw data coming out of the thing. Might be useful to someone out there. > > jb > > #P window setfont "Sans Serif" 9.; > #P window linecount 1; > #P comment 154 387 100 196617 Z; > #P comment 117 387 100 196617 Y; > #P toggle 82 185 15 0; > #P newex 82 203 29 196617 gate; > #P toggle 184 185 15 0; > #P newex 184 203 29 196617 gate; > #P comment 287 78 100 196617 > #P number 152 367 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0; > #P number 116 367 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0; > #P number 80 367 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0; > #P newex 80 342 67 196617 unpack 0 0 0; > #P newex 337 268 20 196617 t b; > #P newex 296 211 40 196617 t clear; > #P newex 337 242 67 196617 match 10 13; > #P newex 337 179 48 196617 bucket 2; > #P message 265 77 20 196617 32; > #P newex 32 315 202 196617 regexp .*X=(\\d+).*Y=(\\d+).*Z=(\\d+); > #P newex 142 279 40 196617 itoa; > #P newex 142 250 67 196617 zl group 240; > #P message 265 51 20 196617 49; > #P toggle 77 48 15 0; > #P newex 77 71 57 196617 qmetro 20; > #P newex 82 226 54 196617 print data; > #P newex 184 226 63 196617 print status; > #P newex 142 116 71 196617 serial e 9600; > #P comment 288 51 100 196617 > #P comment 78 387 100 196617 X; > #P window linecount 4; > #P comment 269 363 169 196617 This patch simply reads the default > data out of the WiTilt. In the other modes of the device , it could > serve as a resonable model for extension.; > #P connect 10 0 11 0; > #P connect 7 0 6 0; > #P connect 11 1 17 0; > #P connect 17 0 18 0; > #P connect 25 0 24 0; > #P connect 24 0 5 0; > #P fasten 3 0 24 1 147 192 106 192; > #P connect 17 1 19 0; > #P connect 6 0 3 0; > #P fasten 12 0 3 0 270 98 147 98; > #P fasten 8 0 3 0 270 71 147 71; > #P connect 3 0 9 0; > #P fasten 16 0 9 0 342 294 281 294 281 173 147 173; > #P connect 9 0 10 0; > #P connect 17 2 20 0; > #P connect 23 0 22 0; > #P connect 22 0 4 0; > #P connect 3 1 22 1; > #P connect 13 0 15 0; > #P fasten 3 0 13 0 147 137 342 137; > #P connect 13 0 14 0; > #P connect 13 1 14 0; > #P connect 15 0 14 0; > #P connect 14 0 16 0; > #P window clipboard copycount 28; > > > > > > Keith McMillen > BEAM Foundation > http://www.beamfoundation.org/ > 510.502.5310 > > > >
    • Aug 27 2006 | 7:13 am
      it is also possible to change the com port manualy. i hope my posts get to the list. please someone ping me ;)
      2006/8/27, yair reshef : > > keith, read my report on the sparkfun forum for (possible) solution for > your com problem. > in short, if witilt is recognized as com5 then follow the English > lettering to find the corresponding letter. > [serial e 9600] should then work > > 2006/8/26, Keith McMillen : > > > Hi Jeremy, > > > > Like your patch - thanks. > > > > I have been trying to get the WiTilt to work with a dual AMD XP machine > > running a Blue Soleil BlueTooth dongle. > > > > The system sees the device and I can query and read date from > > hyperterminal, but when I bang the serial object in the max patch, Max > > freezes and I have to reboot. > > > > WiTilt is showing up on Comm 5 but the serial object, when asked to > > report, says it only sees Comm 4. Of course any attempts to move the Blue > > Tooth device to Comm 4 have failed. > > > > Any ideas - did you have similar problems and/or are you using different > > hardware for the Platform and Bluetooth receiver? > > > > Thanks, > > > > Keith > > > > > > *Jeremy Bernstein * wrote: > > > > I was talking to Stefan Prosky at SIGGRAPH and he turned me on to the > > WiTilt from Spark Fun, which I've been playing with a little bit over > > the last few days. Stefan mentioned that he was having trouble > > parsing the data, and Tom Igoe's article at ITP mentioned something > > similar. So, here's a little patch that does simple parsing of the > > raw data coming out of the thing. Might be useful to someone out there. > > > > jb > > > > #P window setfont "Sans Serif" 9.; > > #P window linecount 1; > > #P comment 154 387 100 196617 Z; > > #P comment 117 387 100 196617 Y; > > #P toggle 82 185 15 0; > > #P newex 82 203 29 196617 gate; > > #P toggle 184 185 15 0; > > #P newex 184 203 29 196617 gate; > > #P comment 287 78 100 196617 > > #P number 152 367 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0; > > #P number 116 367 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0; > > #P number 80 367 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0; > > #P newex 80 342 67 196617 unpack 0 0 0; > > #P newex 337 268 20 196617 t b; > > #P newex 296 211 40 196617 t clear; > > #P newex 337 242 67 196617 match 10 13; > > #P newex 337 179 48 196617 bucket 2; > > #P message 265 77 20 196617 32; > > #P newex 32 315 202 196617 regexp .*X=(\\d+).*Y=(\\d+).*Z=(\\d+); > > #P newex 142 279 40 196617 itoa; > > #P newex 142 250 67 196617 zl group 240; > > #P message 265 51 20 196617 49; > > #P toggle 77 48 15 0; > > #P newex 77 71 57 196617 qmetro 20; > > #P newex 82 226 54 196617 print data; > > #P newex 184 226 63 196617 print status; > > #P newex 142 116 71 196617 serial e 9600; > > #P comment 288 51 100 196617 > > #P comment 78 387 100 196617 X; > > #P window linecount 4; > > #P comment 269 363 169 196617 This patch simply reads the default > > data out of the WiTilt. In the other modes of the device , it could > > serve as a resonable model for extension.; > > #P connect 10 0 11 0; > > #P connect 7 0 6 0; > > #P connect 11 1 17 0; > > #P connect 17 0 18 0; > > #P connect 25 0 24 0; > > #P connect 24 0 5 0; > > #P fasten 3 0 24 1 147 192 106 192; > > #P connect 17 1 19 0; > > #P connect 6 0 3 0; > > #P fasten 12 0 3 0 270 98 147 98; > > #P fasten 8 0 3 0 270 71 147 71; > > #P connect 3 0 9 0; > > #P fasten 16 0 9 0 342 294 281 294 281 173 147 173; > > #P connect 9 0 10 0; > > #P connect 17 2 20 0; > > #P connect 23 0 22 0; > > #P connect 22 0 4 0; > > #P connect 3 1 22 1; > > #P connect 13 0 15 0; > > #P fasten 3 0 13 0 147 137 342 137; > > #P connect 13 0 14 0; > > #P connect 13 1 14 0; > > #P connect 15 0 14 0; > > #P connect 14 0 16 0; > > #P window clipboard copycount 28; > > > > > > > > > > > > Keith McMillen > > BEAM Foundation > > http://www.beamfoundation.org/ > > 510.502.5310 > > > > > > > > >
    • Aug 27 2006 | 2:02 pm
      Hi,
      Yes I did try both of your suggestions multiple times. Read the post and seems very similar to everything I tried, but when changing the serial letter select in Max it would freeze Max to the point of needing a new reboot. Again this a AMD XP sustem I am working on. What hardware are you using ie Platform and Bluetooth receiver chipset?
      Thanks,
      KMc
      yair reshef wrote: it is also possible to change the com port manualy. i hope my posts get to the list. please someone ping me ;)
      2006/8/27, yair reshef < yair99@gmail.com>: keith, read my report on the sparkfun forum for (possible) solution for your com problem. in short, if witilt is recognized as com5 then follow the English lettering to find the corresponding letter. [serial e 9600] should then work
      2006/8/26, Keith McMillen < keith@beamfoundation.org>: Hi Jeremy,
      Like your patch - thanks.
      I have been trying to get the WiTilt to work with a dual AMD XP machine running a Blue Soleil BlueTooth dongle.
      The system sees the device and I can query and read date from hyperterminal, but when I bang the serial object in the max patch, Max freezes and I have to reboot.
      WiTilt is showing up on Comm 5 but the serial object, when asked to report, says it only sees Comm 4. Of course any attempts to move the Blue Tooth device to Comm 4 have failed.
      Any ideas - did you have similar problems and/or are you using different hardware for the Platform and Bluetooth receiver?
      Thanks,
      Keith
      Jeremy Bernstein wrote:
      I was talking to Stefan Prosky at SIGGRAPH and he turned me on to the WiTilt from Spark Fun, which I've been playing with a little bit over the last few days. Stefan mentioned that he was having trouble parsing the data, and Tom Igoe's article at ITP mentioned something similar. So, here's a little patch that does simple parsing of the raw data coming out of the thing. Might be useful to someone out there.
      jb
      Keith McMillen BEAM Foundation http://www.beamfoundation.org/ 510.502.5310
      Keith McMillen BEAM Foundation http://www.beamfoundation.org/ 510.502.5310