Thank you so much for your quick reply. > Have you checked that:
> - every epuck has a different id What exactly do you mean by id? > - asebaswitch tells you that the connections went fine Yes. > - the bluetooth LED on the e-puck indicates that the link is working? Yes. We are not sure if we need to set a specific option in Aseba Studio to load /dev/rfcommX. We tried to set ser:device=/dev/rfcommX in "Custom" (when loading Aseba Studio), but this doesn't seem to work either. Muriel 2010/9/24 Stéphane Magnenat <[email protected]>: > Hello, > >> We are having a problem connecting Aseba Studio to our e-pucks. For >> the connection of the e-pucks we are using the following commands: >> >> sudo rfcomm bind 0 "XX:XX:XX:XX:XX:XX" sudo rfcomm bind 1 >> "XX:XX:XX:XX:XX:XX" sudo rfcomm bind 2 "XX:XX:XX:XX:XX:XX" sudo >> rfcomm bind 3 "XX:XX:XX:XX:XX:XX" >> >> asebaswitch -v "ser:device=/dev/rfcomm0" "ser:device=/dev/rfcomm1" >> "ser:device=/dev/rfcomm2" "ser:device=/dev/rfcomm3" >> >> However, when we launch Aseba Studio, the e-pucks don't show up in >> the "Serial" section. >> >> How can we connect the e-pucks to Aseba Studio? > > Have you checked that: > - every epuck has a different id > - asebaswitch tells you that the connections went fine > - the bluetooth LED on the e-puck indicates that the link is working? > > Good luck, > > Stéphane > > -- > Dr Stéphane Magnenat > http://stephane.magnenat.net > -- key :: 0x6070C31A _______________________________________________ Aseba-user mailing list [email protected] https://mail.gna.org/listinfo/aseba-user
