Re: [Tinyos-help] hardware platform choice

2011-06-03 Thread CJ Davies
Incidentally I would ideally want to be able to buy/build single devices 
that can provide both input (sensing) & output (actuation) rather than 
the situation I had in my dissertation of the Tmote Invents providing 
input & completely separately from them the Phidget relays providing output.

On 06/03/2011 02:15 PM, CJ Davies wrote:
> I have recently completed an undergraduate dissertation that used 
> Tmote Invent nodes & a Phidget controller with relay boards to create 
> a cross-reality system using a real world location & a simulation of 
> that location in OpenSim (Second Life). I am continuing the research 
> as a postgraduate & have the opportunity to buy some new equipment. I 
> still have access to the Tmote Invent nodes but I found them difficult 
> to work with because of the lack of official 2.1 support.
>
> If I were to buy new nodes, what would this mailing list's 
> recommendation be? I will probably want to buy ~5 nodes to begin with 
> & could probably spend £300-£500 on them. Later I will probably want 
> to expand the experiment by buying more nodes.
>
> I don't really know where to start looking for information about the 
> available platforms, as the wiki doesn't really have a comparison of 
> the available platforms (that I could find anyway).
>
> Regards,
> CJ Davies
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


[Tinyos-help] hardware platform choice

2011-06-03 Thread CJ Davies
I have recently completed an undergraduate dissertation that used Tmote 
Invent nodes & a Phidget controller with relay boards to create a 
cross-reality system using a real world location & a simulation of that 
location in OpenSim (Second Life). I am continuing the research as a 
postgraduate & have the opportunity to buy some new equipment. I still 
have access to the Tmote Invent nodes but I found them difficult to work 
with because of the lack of official 2.1 support.

If I were to buy new nodes, what would this mailing list's 
recommendation be? I will probably want to buy ~5 nodes to begin with & 
could probably spend £300-£500 on them. Later I will probably want to 
expand the experiment by buying more nodes.

I don't really know where to start looking for information about the 
available platforms, as the wiki doesn't really have a comparison of the 
available platforms (that I could find anyway).

Regards,
CJ Davies
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


Re: [Tinyos-help] tmote sky reference sheet?

2010-11-18 Thread CJ Davies
My bad - just discovered they are actually tmote invent, despite the 
only branding anywhere outside or inside the device saying tmote sky!

Regards,
CJ Davies

On 11/18/2010 05:21 PM, CJ Davies wrote:
> Is there any reference documentation for the tmote sky from moteiv, in 
> particular which actually lists how each sensor/LED is accessed? The 
> models I have here have a daughter board that sits on top of the main 
> board & has 3 LEDs on it which line up with 3 holes in the plastic 
> casing - however if I use LedsC & Leds.led{0-2}toggle() this activates 
> the LEDs on the main board, not the daughter board - this is a bit 
> annoying because the LEDs on the main board are obscured by the casing 
> so can only be seen when it is dismantled!
>
> Regards,
> CJ Davies

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


[Tinyos-help] tmote sky reference sheet?

2010-11-18 Thread CJ Davies
Is there any reference documentation for the tmote sky from moteiv, in 
particular which actually lists how each sensor/LED is accessed? The 
models I have here have a daughter board that sits on top of the main 
board & has 3 LEDs on it which line up with 3 holes in the plastic 
casing - however if I use LedsC & Leds.led{0-2}toggle() this activates 
the LEDs on the main board, not the daughter board - this is a bit 
annoying because the LEDs on the main board are obscured by the casing 
so can only be seen when it is dismantled!

Regards,
CJ Davies
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


[Tinyos-help] xubuntos + boomerang

2010-11-17 Thread CJ Davies
Does anybody have any advice on how to use Xubuntos with Moteiv's 
(Sentilla's) Boomerang distribution? I've downloaded Boomerang from here;

http://tinyos.cvs.sourceforge.net/tinyos/tinyos-1.x/contrib/boomerang/

and I've put it at

/opt/tinyos-1.x/contrib/boomerang

however when I try to run "make tmote" on the Boomerang version of 
Oscilloscope at;

/opt/tinyos-1.x/contrib/boomerang/apps/Oscilloscope

I get;

ERROR, "tmote ident_flags tos_image bnp" does not specify a valid 
target. Stop.

This is after I've run "tos1" to set up for TinyOS 1.x

Can anybody shed some light on this matter?

Regards,
CJ Davies
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


[Tinyos-help] tmote sky hamamatsuC missing?

2010-11-16 Thread CJ Davies
I am trying to change the SenseC application to access the temperature 
sensor on a Tmote Sky node, which I think should be as simple as 
starting by changing

new DemoSensorC() as Sensor

to

new HamamatsuC() as Sensor

in SenseAppC.nc however I can't find HamamatsuC anywhere in my tinyos 
source tree. I'm using the VMWare image from the TinyOS website so I 
presumed everything would already be there, but it doesn't seem to have 
the neccessary stuff from moteiv.

Can anybody shed some light on this, it's driving me crazy blundering 
through the directories hoping to come across what I need!

Regards,
CJ Davies
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


[Tinyos-help] Blink app, main.ihex No such file

2010-11-09 Thread CJ Davies
I'm using the Xubuntos VMWare image with a telosb mote attached via USB 
& connected through into the VM, with the correct 
ownership/permissions/etc. yet when I try to compile even the simplest 
program I get the following error;

xubun...@xubuntos-tinyos:~/Blink$ make telosb reinstall bsl,/dev/ttyUSB0
cp build/telosb/main.ihex build/telosb/main.ihex.out
cp: cannot stat `build/telosb/main.ihex': No such file or directory
make: *** [setid] Error 1

Can anybody shed any light on this? Google gives me nothing except that 
it might be a Cygwin problem, but my setup has nothing to do with Cygwin!

Regards,
CJ Davies
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


[Tinyos-help] Installation problems

2010-10-01 Thread CJ Davies
Msp430GeneralIOC.nc:340: 
cannot find `P63'
/opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:341: 
cannot find `P64'
/opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:342: 
cannot find `P65'
/opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:343: 
cannot find `P66'
/opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:344: 
cannot find `P67'
/opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:346: 
cannot find `P66'
/opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:347: 
cannot find `P67'
/opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:349: 
cannot find `P67'
/opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:350: 
cannot find `P57'
In component `PlatformLedsC':
/opt/tinyos-2.1.1/tos/platforms/telosb/PlatformLedsC.nc:22: cannot find 
`Port54'
/opt/tinyos-2.1.1/tos/platforms/telosb/PlatformLedsC.nc:25: cannot find 
`Port55'
/opt/tinyos-2.1.1/tos/platforms/telosb/PlatformLedsC.nc:28: cannot find 
`Port56'
make: *** [exe0] Error 1


=

PlatformLedsC.nc as taken from one of the tutorials;

[...@reddawn Blink]$ cat 
/opt/tinyos-2.1.1/tos/platforms/telosb/PlatformLedsC.nc
#include "hardware.h"

  configuration PlatformLedsC {
provides interface GeneralIO as Led0;
provides interface GeneralIO as Led1;
provides interface GeneralIO as Led2;
uses interface Init;
  }

  implementation {
components
HplMsp430GeneralIOC as GeneralIOC
  , new Msp430GpioC() as Led0Impl
  , new Msp430GpioC() as Led1Impl
  , new Msp430GpioC() as Led2Impl
  ;
    components PlatformP;

Init = PlatformP.LedsInit;

Led0 = Led0Impl;
Led0Impl -> GeneralIOC.Port54;

Led1 = Led1Impl;
Led1Impl -> GeneralIOC.Port55;

Led2 = Led2Impl;
Led2Impl -> GeneralIOC.Port56;

}


=

Regards,
CJ Davies
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help