[Tinyos-help] please help me (command for running tossim program)
Can anyone please let me know how to run the tossim program? The tossim I am using is of version 1.0. Please let me know the command for the same. Thanks & Regards Ms. Amrita Ghosal Assistant Professor Department of Computer Science and Engineering Dr. B C Roy Engineering College Jemua Road, Fuljhore Durgapur-713206 West Bengal, India___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] TinyOS on Atmega128RFA1 : Problem
Hi, I am using TinyOS on Atmel Atmega128RFA1 , I am using Phillipp Sommer port of TinyOS for Atmega128rfa1. I have been trying to synchronize number of Atmega128RFA1 modules to accuracy of < 25 microsecond using FTSP. I have been able to run FTSP on these nodes and subsequently synchronize number of nodes in range of millisecond. Now, `I am having a strange problem, I have written my version of TimeSyncC.nc for microsecond, I found the LocalTimeMicroC gives incorrect time in Microseconds. I further debugged and found that, whenever a Timer event is called, the delay between starting of timer and subsequently calling of fired() is not reflected in Time maintained by system in microseconds, while time in milliseconds is updated, it is not the case with microsecond. I used LocalTime and LocalTime and printed time value, while TMilli was updated, TMicro wasnt. For instance: If I start Timer at 1202658 seconds and have a delay of 1 seconds, when I read time again in fired, I find time still is 1202658, when it should be 2202658, this is giving inaccurate results with FTSP. Can anyone suggest me why this is happening ? On Zigbit modules and port of TinyOS for meshbean developed at ETH, Zurich, It was working fine. Thanks, Ambuj Varshney Research Engineer Embedded systems and Wireless sensor network Group DA-IICT, India ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Telosb light sensor specification
Good afternoon everyone, I use a telosb node equipped with a light sensor, I have succeeded in receiving data from the node on my laptop, but for me the data are talking non sense because I always get a value next to 4000 (when I convert the readings to a decimal value) even if it is dark in my place. Is there a way to treat those data, I know that for example for temperature data we have to apply a formula to get the real temperature value. Does anyone know how to interpret the light data ? Have a good day, regards, -- Arthur Baudry ESEO ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Home automation system
Hello everyone, I am trying to design an home automation system with telosb nodes, right now I have only two nodes, one node is plugged into my laptop as a sink for data reception using BaseStation and the other is equipped with a light sensor and use Oscilloscope to transfer data to the BaseStation node, where the data are forwarded to my laptop thanks to the serial forwarder. Therefore I am receiving my light sensor data on the laptop and I can treat it. But I need to send command like turn on/off the light to an RF to X10 converter (X10 being a type of communication used in home automation system) then this command is send to an X10 switch. The RF signal needs to come from the nodes, this means that I need that sometimes the BaseStation nodes to receive and sometimes to transmit, is there an application ready for this ? Another problem is that the RF to X10 converter is not a node I assume that he will detect when a RF signal is within range and convert it automatically but I am not sure about that so if anyone has some more information or has ever built a system like this, some help would be great :) Have a very good day. Regards, -- Arthur Baudry ESEO ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Problems with Atmel128 I2C-Components (iris) with slow I2C sensors
Yes, TOS 1.x, which underlies Moteworks. Although I just noticed that the last release of T1 has a hardware impl for I2C in mica128. Here is what I used, including my small patch to I2CM.nc: http://www.etantdonnes.com/Motes/T1_I2C.zip But I imagine that it will be fairly pointless to try to use it as all the bit access methodology was changed in T2, so there'd be a bunch of porting to do. I also put the spec that I used to debug my problem here, where the section of interest is "3.7 Clock synchronization": http://www.etantdonnes.com/Motes/NXPI2Cspec_UM10204_3.pdf My symptom was that I missed the first bit of the second byte of data from the slow device and thus lost bit sync and failed to complete that byte (if memory serves correctly...). I found this by looking at the data line with a scope and counting the bits... If you really think your problem is the clock stretching issue then it might be better to see how the ATmega hardware thinks it should be dealing with it. MS Sebastian Dölker wrote: > Unfortunately I have never worked with moteworks > and T1 (T1 = tinyos 1.X ?) > > I work with tinyos-2.1.1 and the standard i2c component of atmle128L (iris) > which uses the under laying twi (two wire interface) > of the atmel128L chip but it seems that with this > special co2-sensor (with long reaction times and the “clock > synchronization mechanism”) this doesn’t work well. > > I guess I have to do bitbanging.. > > Is it possible to use the sources that you mentioned as a starting point? > > Where can I find them? > > > ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Problems with Atmel128 I2C-Components (iris) with slow I2C sensors
Hi, Can you find out what's in the state variable when the i2c stops working? By the way: when we had problems with the i2c drivers, I modified the hpls to print every low level communication: http://dl.dropbox.com/u/363226/munka/I2CDriver.zip Don't forget to change the Clk/Data pins in the HplAtm128I2CBusC (there might be other things to change back), we used it with atm128rfa1 (ucmini platform). If you don't familiar with DiagMsg, check its readme in $TOSDIR/lib/DiagMsg Andris On Thu, Nov 24, 2011 at 4:16 PM, "Sebastian Dölker" wrote: > Sorry I was imprecise.. I started with tinyos 2.1.1 > but work with a check out from the googlecode repository. > (Downloaded in august 11) > > Anyway i downloaded the newest source today.. > but the problem seems to continue! > > Because the I2C-Funktions returned EBUSY I thought, > that there was a problem with the arbiter so I tried it > without arbiter an wired experimentally direct to the Atm128I2CMasterPacketP > (via I2CPacket-interface), > but the Problem continued… > > I discovered that while the I2C-components returned EBUSY the > software runs through the else-block at the beginning of the > read-function in Atm128I2CMasterPacketP, because of that I tried > to „reset“ the i2c component with the i2c_abort() function.. > but as you mentioned this isn’t a good idea.. > > Have you an idea what can cause such a bad state > in Atm128I2CMasterPacketP and how it can be corrected? > > Thanks in advance, > Sebastian > > -- > > > > > > > > > > > > NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie! > Jetzt informieren: http://www.gmx.net/de/go/freephone > ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Problems with Atmel128 I2C-Components (iris) with slow I2C sensors
Sorry I was imprecise.. I started with tinyos 2.1.1 but work with a check out from the googlecode repository. (Downloaded in august 11) Anyway i downloaded the newest source today.. but the problem seems to continue! Because the I2C-Funktions returned EBUSY I thought, that there was a problem with the arbiter so I tried it without arbiter an wired experimentally direct to the Atm128I2CMasterPacketP (via I2CPacket-interface), but the Problem continued… I discovered that while the I2C-components returned EBUSY the software runs through the else-block at the beginning of the read-function in Atm128I2CMasterPacketP, because of that I tried to „reset“ the i2c component with the i2c_abort() function.. but as you mentioned this isn’t a good idea.. Have you an idea what can cause such a bad state in Atm128I2CMasterPacketP and how it can be corrected? Thanks in advance, Sebastian -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] built-in routing protocol in tinyos 2.1.1
pls , could any one tell me which routing protocol is built-in for tinyos 2.1.1 and where the source .nc file is located???___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] simulation of routing protocol in tinyos 2.1.1
which simulator can be used for simulating routing protocol in tinyos 2.1.1 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Blink Compile problem on iris motes
I have recently installed Tinyos-2.0.2 with the support for IRIS motes, I can compile the blink application on mica2 but when I try to compile on iris ( make iris) I have got the following problem: mkdir -p build/iris compiling BlinkAppC to a iris binary ncc -o build/iris/main.exe -Os -Wall -Wshadow -Wnesc-all -target=iris -fnesc-cfi le=build/iris/app.c -board=micasb -DIDENT_PROGRAM_NAME=\"BlinkAppC\" -DIDENT_USE R_ID=\"hafid_amazigh\" -DIDENT_HOSTNAME=\"hafidamazigh\" -DIDENT_USER_HASH=0xe48 85304L -DIDENT_UNIX_TIME=0x4e919289L -DIDENT_UID_HASH=0xd7f0e437L -fnesc-dump=wi ring -fnesc-dump='interfaces(!abstract())' -fnesc-dump='referenced(interfacedefs , components)' -fnesc-dumpfile=build/iris/wiring-check.xml BlinkAppC.nc -lm In file included from /opt/tinyos-2.x/tos/platforms/micaz/hardware.h:50, from /opt/tinyos-2.x/tos/system/SchedulerBasicP.nc:41, from /opt/tinyos-2.x/tos/system/TinySchedulerC.nc:40: /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:90: unknown attribute `safe' /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:90: empty scalar initializer /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:90: (near initialization for `@safe') /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:94: unknown attribute `safe' /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:94: empty scalar initializer /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:94: (near initialization for `@safe') /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:111: unknown attribute `safe' /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:111: empty scalar initializer /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:111: (near initialization for `@safe') /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:121: unknown attribute `safe' /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:121: empty scalar initializer /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:121: (near initialization for `@safe') /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:142: unknown attribute `safe' /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:142: empty scalar initializer /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:142: (near initialization for `@safe') /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:184: syntax error before `siz eof' /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:184: conflicting types for `_ _nesc_ntoh_afloat' /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:182: previous declaration of `__nesc_ntoh_afloat' /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h: In function `__nesc_ntoh_afl oat': /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:186: `source' undeclared (fir st use in this function) /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:186: (Each undeclared identif ier is reported only once /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:186: for each function it app ears in.) /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h: At top level: /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:190: syntax error before `siz eof' /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:190: conflicting types for `_ _nesc_hton_afloat' /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:182: previous declaration of `__nesc_hton_afloat' /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h: In function `__nesc_hton_afl oat': /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:191: `target' undeclared (fir st use in this function) /opt/tinyos-2.x/tos/chips/atm1281/atm128hardware.h:191: `value' undeclared (firs t use in this function) In file included from /opt/tinyos-2.x/tos/system/TinySchedulerC.nc:41: In component `McuSleepC': /opt/tinyos-2.x/tos/chips/atm1281/McuSleepC.nc: At top level: /opt/tinyos-2.x/tos/chips/atm1281/McuSleepC.nc:82: unknown attribute `safe' /opt/tinyos-2.x/tos/chips/atm1281/McuSleepC.nc:82: empty scalar initializer /opt/tinyos-2.x/tos/chips/atm1281/McuSleepC.nc:82: (near initialization for `@sa fe') In file included from /opt/tinyos-2.x/tos/chips/atm1281/timer/Atm128AlarmAsyncC. nc:67, from /opt/tinyos-2.x/tos/platforms/mica/AlarmCounterMilliP.nc:3 3, from /opt/tinyos-2.x/tos/platforms/mica/HilTimerMilliC.nc:44, from /opt/tinyos-2.x/tos/system/TimerMilliP.nc:41, from /opt/tinyos-2.x/tos/system/TimerMilliC.nc:40, from BlinkAppC.nc:46: In component `Atm1281AlarmAsyncP': /opt/tinyos-2.x/tos/chips/atm1281/timer/Atm1281AlarmAsyncP.nc:58: unknown attrib ute `safe' /opt/tinyos-2.x/tos/chips/atm1281/timer/Atm1281AlarmAsyncP.nc:58: empty scalar i nitializer /opt/tinyos-2.x/tos/chips/atm1281/timer/Atm1281AlarmAsyncP.nc:58: (near initiali zation for `@safe') In file included from /opt/tinyos-2.x/tos/chips/atm1281/timer/HplAtm1281Timer2As yncC.nc:89, from /opt/tinyos-2.x/tos/chips/atm1281/timer/Atm128AlarmAsyncC. nc:68, from /opt/tinyos-2.x/tos/platforms/mica/AlarmCounterMilliP.nc:3 3, from /opt/tinyos-2.x/tos/platfo
Re: [Tinyos-help] Problems with Atmel128 I2C-Components (iris) with slow I2C sensors
Hi Sebastian, The I2CMasterPacketC in tinyos 2.1.1 had a bunch of bugs, try the SVN version from here: http://code.google.com/p/tinyos-main/ It should be enough to replace the i2c folder. Andris On Thu, Nov 24, 2011 at 11:57 AM, "Sebastian Dölker" wrote: > Unfortunately I have never worked with moteworks > and T1 (T1 = tinyos 1.X ?) > > I work with tinyos-2.1.1 and the standard i2c component of atmle128L (iris) > which uses the under laying twi (two wire interface) > of the atmel128L chip but it seems that with this > special co2-sensor (with long reaction times and the “clock > synchronization mechanism”) this doesn’t work well. > > I guess I have to do bitbanging.. > > Is it possible to use the sources that you mentioned as a starting point? > > Where can I find them? > > > > -- > > > > > > > > > > > > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > ___ > Tinyos-help mailing list > Tinyos-help@millennium.berkeley.edu > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Problems with Atmel128 I2C-Components (iris) with slow I2C sensors
Unfortunately I have never worked with moteworks and T1 (T1 = tinyos 1.X ?) I work with tinyos-2.1.1 and the standard i2c component of atmle128L (iris) which uses the under laying twi (two wire interface) of the atmel128L chip but it seems that with this special co2-sensor (with long reaction times and the “clock synchronization mechanism”) this doesn’t work well. I guess I have to do bitbanging.. Is it possible to use the sources that you mentioned as a starting point? Where can I find them? -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
