MINDSTORM, NXT-G & ISADORA
-
thanks Gavspav, I'm still in Snow Leopard because with Lion there where problems with other software... I will try to find out...
-
I've lent my laptop with 10.6 on to someone so looks like I can't try and get it working without a load of grief.
What you need to do is first connect to the mindstorms. Then follow the legosc instructions - click on legosc.jar/enter the correct com port.Get the connection set up - I'm guessing the log tab will tell you when you are successfully connected.For the purposes of this test connect a motor to port 1 of the nxt brick.Then set the ports up - for the Legosc port choose anything - say 8001.In the Your Application section enter Isadora and for port enter 1234.Then open Isadora. Open a new file. Go to Isadora>Preferences>Midi/Net and check the OSC Port no. is 1234 - if it isn't change it to 1234.Close the preferences.You should see an Isadora window labeled untitled. In the search box in the top left type osc.Near the bottom there should be some text labeled OSC transmit. Click and drag it to the big window on the right.You then should have an OSC transmit actor.Click on the 1234 in the port section of that actor - it should turn yellow. Then change it to 8001.Click on isadora in the address section. Change this to one of the addresses that legosc provides eg /motorForward 1 (or if this doesn't work try /motorForward1 - not sure which it is)Then in the search window in top left, type mouse.Drag the Mouse Watcher (near the bottom) into the right hand window.Connect the 'horizontal postion' of the mouse watcher actor to the 'value' of the OSC Transmit actor.You should now be controlling the speed of the lego motor with the horizontal position of the mouse.I've tried to attach an Isadora patch to save you doing that bit but not sure its working. In any case its only 2 actors.Let us know how it goes. -
thanks Gavspav, I'm trying.... lets see if I can manage, hopefully, have to investigate as something I'm not familiar with :)
but I'm thankful -
Am I being daft but the lego website is awful; been looking for the mac NXT software for nearly half an hour.... any help?
-
Start here with some good information about installing it
https://discussions.apple.com/thread/4158314?start=0&tstart=0Download with Firefox[MINDSTORMS NXT 2.0](http://en-us.kb.lego.com/ics/support/DLRedirect.asp?fileNum=84974&deptID=5622) -
I downloaded that .iso from your link vanakaru and it appears to install ok!
I still haven't got isadora>nxt communication to work - but quite close.A few additions to my earlier post. I didn't connect to the nxt brick using the nxt software but just paired via bluetooth. I used ls /dev/tty.* via terminal to find out which com port i was using. /dev/tty.NXT-DevB for me.I put this into the diablu settings and in the log window it opens the port and starts running the server.It tells you the address legosc is listening too. You use the ip address in the udp adress section of the osc transmit actor in the isadora window. And the last 4 digit number is the port number.Not sure why I am giving this advice as as I said I haven't actually got it to work!I've connected legosc to the nxt brick and am receiving osc data from Isadora but haven't managed to get the motor to move! -
exciting news gavspav you're getting closer!
-
Even closer now - got it working with the Pure Data sample patch and Isadora looked like it should work but then the batteries dies in the Nxt brick.
Loads of batteries in them things. Send me some more! -
are you in London? I can take you some this w/e from Portugal :)
-
Ok finally I have some batteries and can now confirm that Isadora and LegoOsc DON'T work together!
For some reason either LegoOsc or the NXT brick don't understand the OSC messages that Isadora is spitting out.The workaround would be to write some little bridging app in Max or PD that converts say midi to OSC that works.A simple if clumsy solution. -
Dear Gavin,
I can assure you that the OSC messages Isadora sends follow the standard. Have you tried turning off type tags? What kind of messages does the NXT brick expect? Is there any documentation on that?Best Wishes,Mark -
Hmm well it could be human error but it really didn't seem like it. Maybe I'll have another look on Monday.
If I turn off type tags then legoOsc doesn't receive/understand the incoming messages.I had the Pure Data example working and the legoosc java code reports the incoming OSC messages in its log window.I tried it with Isadora and had identical messages in the legoosc log window but the lego brick didn't respond. I assumed it was something to do with OSC message format as I have had problems with this before (not just with Isadora).One thing which could potentially be causing problems is that the message is in the format /motorForward 0 iCould the spaces be causing an issue? Or the fact that I am sending integers?I'm straw clutching rather than employing logic. -
well what exactly comes after the /motorForward part?
/motorForward is a valid OSC address.But is the rest text? is the actual message "0 i" (less the quotes) ? Or???Best Wishes,Mark -
may I send you some good vibes of encouragement not to give up??!! thank you
-
It's /motorForward i n
where i is the number of the motor and n is the speed of the motor.So, "/motorForward 1 4" would tell motor 1 to turn quite slowly and"/motorForward 1 127" would tell it to turn alot quicker.There are no quotes in the message - I just put those in. I've never seen an OSC message like that before normally its /address/ value but this is the way it seems to be with LegoOSC.The pure data patch sends /MotorForward 1 $1 (where $1 is the value) and it works.Isadora - I set the transmit address to /MotorForward 1 with the value determined by the value input of course.Like I said the values received by LegoOsc look identical in the log window, except it don't work. -
Is it possible to send the Pure Data patch that outputs the working values. I could analyze them to see how they are different than what Isadora sends.
Best Wishes,Mark -
Here we are. 2e4051-nxt.pd.zip
