|
The Samraksh Company |
.png){kind=spacer} |
Could not compile stylesheet for timeless. Using last compiled stylesheet.
By:
Bahri cagliyan
Hello we are a research group at Tobb University of Economics and Technology on Turkey.
We just bought the BumbleBee radar set and we are trying to launch them.
We installed the TinyOs succesfully.After set up the enviroment for tinyOs we plugged the Telosb to the Pc.
But when we type "motelist" in Cygwin,it says "No device found".
What should we do in that problem?
We installed all rpm files we need.
We just bought the BumbleBee radar set and we are trying to launch them.
We installed the TinyOs succesfully.After set up the enviroment for tinyOs we plugged the Telosb to the Pc.
But when we type "motelist" in Cygwin,it says "No device found".
What should we do in that problem?
We installed all rpm files we need.
Accepted Answer
By:
Michael
Hello Bahri,
Is the TelosB visible in Windows Device Manager? The TelosB may show up as an FTDI serial device. If not, please ensure that you have installed FTDI drivers.
Does the TelosB/FTDI device have a COM port number assigned to it in Windows Device Manager? If not, check all of Device Manager's Port entries for an entry that looks like TelosB or FTDI.
If you can find the TelosB/FTDI device in Windows Device Manager, then everything should be okay even though motelist does not work. Explicitly pass the COM# port when issuing TinyOS command line programs like "make telosb install.0 bsl,#" where # is replaced by the COM# you found for the TelosB/FTDI device in Windows Device Manager.
When a TelosB is plugged into a computer, Windows assigns the TelosB a device ID and new COM port number. In newer versions of Windows, the device ID is assigned by Windows instead of the FTDI serial port driver that communicates with the TelosB. Therefore, MoteList may be looking in the old FTDI location for the device ID. Explicitly listing the serial port COM number will tell the TelosB boot-strap loader script which serial port COM number to use even though motelist can't automatically find your TelosB in the Windows registry.
So, in summary, check for the TelosB's assigned serial port number in Windows Device Manager.
Thank you for purchasing the BumbleBee radar set. Please let us know how your problem is resolved to better aid other community members. What version of Windows are you using? What FTDI driver version is installed? What TinyOS version are you using? Did you obtain TinyOS from RPM or build it from SVN or the latest GIT development branch? This motelist issue may have already been resolved in the latest TinyOS version, but you should still be able to install without motelist if everything else is set up correctly.
In addition to the TelosB mote running TinyOS, the BumbleBee radar also works with Samraksh's more powerful eMote .NOW line of motes based on the .NET Micro Framework, which is designed to be simpler to use and more intuitive than TinyOS
.
Please let us know if you have additional questions. I've subscribed to this and all forum posts to help me catch and provide faster answers next time.
Sincerely,
Michael McGrath
Samraksh intern and student at Ohio State University
Is the TelosB visible in Windows Device Manager? The TelosB may show up as an FTDI serial device. If not, please ensure that you have installed FTDI drivers.
Does the TelosB/FTDI device have a COM port number assigned to it in Windows Device Manager? If not, check all of Device Manager's Port entries for an entry that looks like TelosB or FTDI.
If you can find the TelosB/FTDI device in Windows Device Manager, then everything should be okay even though motelist does not work. Explicitly pass the COM# port when issuing TinyOS command line programs like "make telosb install.0 bsl,#" where # is replaced by the COM# you found for the TelosB/FTDI device in Windows Device Manager.
When a TelosB is plugged into a computer, Windows assigns the TelosB a device ID and new COM port number. In newer versions of Windows, the device ID is assigned by Windows instead of the FTDI serial port driver that communicates with the TelosB. Therefore, MoteList may be looking in the old FTDI location for the device ID. Explicitly listing the serial port COM number will tell the TelosB boot-strap loader script which serial port COM number to use even though motelist can't automatically find your TelosB in the Windows registry.
So, in summary, check for the TelosB's assigned serial port number in Windows Device Manager.
Thank you for purchasing the BumbleBee radar set. Please let us know how your problem is resolved to better aid other community members. What version of Windows are you using? What FTDI driver version is installed? What TinyOS version are you using? Did you obtain TinyOS from RPM or build it from SVN or the latest GIT development branch? This motelist issue may have already been resolved in the latest TinyOS version, but you should still be able to install without motelist if everything else is set up correctly.
In addition to the TelosB mote running TinyOS, the BumbleBee radar also works with Samraksh's more powerful eMote .NOW line of motes based on the .NET Micro Framework, which is designed to be simpler to use and more intuitive than TinyOS
.Please let us know if you have additional questions. I've subscribed to this and all forum posts to help me catch and provide faster answers next time.
Sincerely,
Michael McGrath
Samraksh intern and student at Ohio State University
Responses (3)
-
Accepted Answer
By: Bahri cagliyanWe are using TinyOs-2.x in 32 bit windows 7 operating system.Here are the outputs of the Blink and RadarDataCollect program captures.
Bahri Çağlıyan
TOBB ETU RADAR SYSTEMS LABS.
ANKARA-TURKEYAttachments:
-
-
Accepted Answer
By: MichaelHello Bahri,
What version of TinyOS are you using? What Operating System are you using? Will you please copy/paste the output of the blink installation command and the RadarDataCollect installation command running in the same environment?
Sincerely,
Michael -
Accepted Answer
By: Bahri cagliyanThank you for your reply Micheal,
We have installed the FTDI driver .PC knows the Telosb as USB Serial Driver.But the result is the same .we cannot burn the program to the Telosb.
I think the problem is that we are using 64 bit operating system. We have done the same procedures with the 32 bit operating system and everything were fine.
Now we have another problem.We can install the Blink software in to the Telosb. But when we are trying to compile and burn the program "RadarDataCollect" we are having problem.Program can not be compiled and burned to the Telosb.We took all the radar programs from your website.
I wonder did anyone have the same problem.What should we do about maintaining this problem?
Sincerely,
Bahri Çağlıyan
TOBB ETU RADAR SYSTEMS LABS.
ANKARA-TURKEY
Your Reply
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »