Hi Mike, I'm using Ubuntu natively. Got the system working, i has able to connect the two shimmers, slave and master, after a refresh install of tinyOS from the googlecode SVN. I know i followed all the steps of the tutorial to install from the GIT repository, did it two times, and when i installed from the SVN it compiled for shimmer2r with no problems and the two shimmers interacted as intended. Maybe GIT is outdated or has some faulty files.
Regarding the python script, still can't use it and maybe that's because the embedded Bluetooth requires always to be the Master in all connections or there is a bug in Bluez. When the shimmer connects to the PC's Bluetooth it always show a popup window telling that the shimmer wants to connect to a service that has a uuid different from the one in the python script. Also tried to auto-bind the shimmer to no success. When i grant the access to the node, the green led blinks and there is no more reactions from either side. Thanks for the Help! João Mesquita 2013/2/7 mike healy <[email protected]> > Hi João, > > If you have a shimmer2r then you should be using "make shimmer2r", or > results will be unpredictable. See here to confirm which you have: > http://www.shimmer-research.com/products-2/shimmer-revisions > > But in any case the shimmer2 and the shimmer2r use the exact same > bluetooth driver. > > The fact that the PC is requesting to pair with the shimmer is odd. This > should not be required. > > Yesterday I tested using Ubuntu 10.04 (installed natively on the PC), > using the BlueZ BT stack, and with a Belkin BT dongle, and I got no such > pairing request (when the python ran as expected for me). > > Are you running Linux natively or within VMware? In the past I had no > problem running the python scripts within Linux running in a VMware image > on top of Windows. However, when I just tested this again today I am > running into the same issue you are (i.e. VMware asks for a pairing code > with the shimmer and then doesn't seem to go any further). I presume this > is due to the change in how BT is handled in recent versions of VMware > Player (it tries to share the BT radio between the host and client OS, > rather than giving either full control). My initial thinking is that this > is not designed to work when the PC is a BT slave (which would be a > relatively unusual situation) and the cause of my issue. > > As long as you are able to compile the application I doubt the problem is > with your TinyOS install, and it is much more likely that the issue is at > the PC side of the link. > > Mike > > > > On Wed, Feb 6, 2013 at 10:35 PM, João Mesquita <[email protected]> wrote: > >> Hi Mike, thanks for the reply, >> >> Just to be sure, i re-downloaded the bluetoothMasterTest apps , and >> tested and still can't get any output in the python script. >> Another problem is that only with "make shimmer2" i get the request to >> pair the node with the PC (the label on the back of the shimmer clearly >> says shimmer2r). Using shimmer or shimmer2r builds the shimmer can't be >> found by Bluetooth detection. >> >> I used this guide to install TinyOS: >> http://docs.tinyos.net/tinywiki/index.php/Installing_from_SVN/GIT >> >> Could be due to faulty Bluetooth on my PC or problems on the SVN/GIT >> repository? >> >> Thanks >> >> >> 2013/2/6 mike healy <[email protected]> >> >>> Hi João, >>> >>> I've just retested it, but that application works fine for me building >>> it with the following command: >>> >>>> make BT_SLAVE="000A3A872892" shimmer2r install bsl,/dev/ttyUSB0 >>>> >>> >>> When I run the bluetoothMasterTest.py script ( >>> http://tinyos.cvs.sourceforge.net/viewvc/tinyos/tinyos-2.x-contrib/shimmer/scripts/bluetoothMasterTest.py?content-type=text%2Fplain) >>> I see: >>> >>> Waiting for connection on RFCOMM channel 1 (Ctrl-C to quit) >>>> Seq No || accelX | accelY | accelZ | gyroX | gyroY | gyroZ >>>> 203 || 2017 | 1866 | 1979 | 1834 | 1678 | 1847 >>>> 204 || 2028 | 1862 | 1978 | 1835 | 1677 | 1847 >>>> 205 || 2022 | 1865 | 1986 | 1835 | 1678 | 1847 >>>> <<<<<lots more values here>>>>> >>>> 008 || 2029 | 1865 | 1981 | 1835 | 1677 | 1847 >>>> 009 || 2028 | 1871 | 1981 | 1836 | 1678 | 1848 >>>> 010 || 2028 | 1865 | 1979 | 1833 | 1677 | 1847 >>>> disconnected >>>> Waiting for connection on RFCOMM channel 1 (Ctrl-C to quit) >>>> >>> etc. >>> >>> You should however note that the script should be running before the >>> shimmer is powered on/rebooted, as this app only tries to connect to the >>> Slave device (the PC) once, and if it fails it goes to sleep and doesn't >>> try again. >>> >>> Mike >>> >>> >>> >>> On Tue, Feb 5, 2013 at 7:28 PM, João Mesquita <[email protected]>wrote: >>> >>>> Hi, >>>> >>>> I'm trying to use Bluetooth to send some data, Slave sends data to >>>> Master, and i have problems pairing both shimmers. >>>> I followed the example from: >>>> >>>> http://tinyos.cvs.sourceforge.net/viewvc/tinyos/tinyos-2.x-contrib/shimmer/swtest/BluetoothMaster/ >>>> >>>> >>>> Connecting the PC with both nodes, using rfcomm and minicom, everything >>>> works (data is sent, connection to master is successful). >>>> Using the python scripts to test the Master connecting, the script gets >>>> stuck on connecting to RFCOMM channel 1 while the rfcomm says >>>> the connection to the master is up. >>>> >>>> I've tried multiple formats of BT_SLAVE_ADDRESS, >>>> "00:06:....", "0x00066..." , "00066..." >>>> none of them worked. >>>> >>>> What could be the problem? >>>> >>>> Thanks. >>>> >>>> João Mesquita >>>> >>>> >>>> _______________________________________________ >>>> Shimmer-users mailing list >>>> [email protected] >>>> https://lists.eecs.harvard.edu/mailman/listinfo/shimmer-users >>>> >>>> >>> >> >
_______________________________________________ Shimmer-users mailing list [email protected] https://lists.eecs.harvard.edu/mailman/listinfo/shimmer-users
