Re: [Tinyos-help] Serial Forwarder and Listen
Michael Schippling wrote: The messages are not in ASCII format, which I think you are hoping for by inference from your question. They are in the same TOS_Msg format as received from the TOSBase Mote. They are fixed length binary, but if you use the Java Packetizer class or the C equiv in the tools directory (in T1) you shouldn't have to know. Are you talking about the serialforwarder written in C? Because it doesn't understand the message format, it just replies the byte received from the serial to a given port. Or do you really mean that there is a C program which understand the message format and creates a C data structure to store them (like the Java Packetizer does)? This could be very useful to me (I'm not so skilled with java, I prefer C), but I cannot find any such application in the tools dir. Can you help me? Fabrizio Stefani MS Ian Welch wrote: When serial forwarder forwards the packets to a designated are the each terminate by a "Carage Return Line Feed"? The reason I ask is because I'm writing a program to listen to the SF port to save Mote data packets. Every now and again the data on the port comes out a different size and throws my program. If there is a termination character at the end of each packet I could resolve this problem. Also, I don't know Java so looking through the tools source code doesn't really help. Thanks, Ian ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ This email has been ClamScanned by ArsLogica antivirus server ! www.clamav.net _______ -- Fabrizio Stefani, Ph.D. Researcher ArsLogica S.r.l. IT Laboratories Business Innovation Centre Unit 6 - 1st floor BIC, Via Trento, 117 38017 Mezzolombardo (TN), Italy Email: [EMAIL PROTECTED] Skype: fabrizio.stefani Phone: +39 0461 600253 Fax: +39 0461 603250 Web Site: www.arslogica.it _ This email has been ClamScanned ! www.clamav.net _ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] SerialForwarder can't read from /dev/ttyUSB0
I've had the same problem on my Ubuntu 6.06. Twice. The first time I solved reinstalling Java (the JDK 5.0 from Sun, Ubuntu packages). After some tweaking and playing around with the code and the system the problem reappeared and this time I solved reinstalling only the TOScomm (and maybe the javacomm, I'm not sure). My 5 cents, Fabrizio Philip Levis wrote: On Oct 23, 2006, at 10:58 AM, Avgoustinos Filippoupolitis wrote: I am using tmote sky on an Ubuntu Dapper machine. I can program the mote without problems. But when I try to use SerialForwarder, it cannot acces the /dev/ttyUSB0. I have created a symlink from ttyUSB0 to ttyS0 but the problem remains. Serialforwarder's GUI starts, but it prompts: " serial@/dev/ttyS0:19200 died - restarting (java.io.IOException: Couldn't configure /dev/ttyS0)" When I try to run Listen with MOTECOM=serial@/dev/ttyS0:19200 it also fails and prompts: "Error on serial@/dev/ttyS0:19200: java.io.IOException: Couldn't configure /dev/ttyS0" I have checked if the mote actually sends data to /dev/ttyUSB0 by using: stty 19200 raw < /dev/ttyUSB0 od -x < /dev/ttyUSB0 and I could see raw data being sent to the port. I also tried that with /dev/ttyS0 and it worked. I have also tried BlackBox and it also works (it displays raw data in it's GUI's box). Does anyone has something to suggest? I am usgin Java.comm 3.0 from Sun. I have encountered similar Java problems with serial ports under Ubuntu. My solution is to use the C-based serial forwarder. Phil _ This email has been ClamScanned ! www.clamav.net _ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Tmote Internal Voltage Measurement
Hi,
I've modified the oscilloscope application to read the voltage level
of the batteries of a Tmote Sky.
So I have included the InternalVoltageC in the
apps/Oscilloscope/Oscilloscope.nc file:
includes OscopeMsg;
configuration Oscilloscope { }
implementation
{
components Main
, OscilloscopeM as Scope
, InternalVoltageC // added for MSP430 internal voltage sensor
, TimerC
, LedsC
//, DemoSensorC as Sensor // removed because not using ext sensors
, UARTComm as Comm;
Main.StdControl -> Scope;
Main.StdControl -> TimerC;
Scope.Timer -> TimerC.Timer[unique("Timer")];
Scope.Leds -> LedsC;
//Scope.SensorControl -> Sensor; // removed
Scope.ADC -> InternalVoltageC;
Scope.CommControl -> Comm;
Scope.ResetCounterMsg -> Comm.ReceiveMsg[AM_OSCOPERESETMSG];
Scope.DataMsg -> Comm.SendMsg[AM_OSCOPEMSG];
}
And then in the corresponding module (OscilloscopeM.nc) I've just
removed the commands to turn on and start the external (not embedded in
the MSP430) sensors:
//call SensorControl.init();
and
//call SensorControl.start();
The application compiles and works, and I can read value, for example,
using the oscilloscope java application.
The problem comes trying to convert ADCcounts to Voltage values.
In the MSP430 Datasheet (and also reported in the Tmote Sky datasheet,
pag. 23) I can see this conversion formula:
DVcc = (ADCCounts/4096)*Vref*2R/R
My question is, which is the Vref value?
It should be 1.5V or 2.5V (see MSP430F1611 datasheet pag 349) but using
this values the conversion gives me wrong results.
For example:
Attaching the mote to a USB port, with the java oscilloscope I should
read 3 V, and the ADCcounts spans between 973 and 975.
If I take Vref = 1.5 V => DVcc = ADCCounts*2*Vref/4096 = 975*3/4096 =
0.714 V
If Vref = 2.5 V => DVcc = ADCCounts*2*Vref/4096 = 975*6/4096 = 1.428 V
So the right result should come from Vref = 6.301 => DVcc =
ADCCounts*2*Vref/4096 = 975*6/4096 = 2.9997 V
Where is my error?
Thank you all,
Fabrizio
_
This email has been ClamScanned !
www.clamav.net
_
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Bug in NesC or a simple error.........???
You are right, with 2 bytes (uint16_t) you can represent signed numbers up to 32767, so every number greater than that value must be an unsigned value. This is why the compiler warns you. If you use just unsigned values you can ignore the warnings. Fabrizio. Miguel Pereira wrote: Hi, I already figure out what is the problem but there is something wrong with nesC compiler. The problem is the number 65535. When I put this number in one variable uint16_t, one warning fire, which is comprehensible because besides I'm using the uint16_t the range could be of -32767 to 32767. If I put the number 32767, all OK, but if I put 32768 all became wrong again. To resolve the problem I thing in use the uint32_t type but happens exactly the same. If I put uint32_t number = 32767 there is no problem but if I put uint32_t number = 32768 the warning "decimal constant is so large that it is unsigned" fire and I think this shouldn't happen. Thanks for any help. Miguel Pereira ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Fabrizio Stefani, Ph.D. Researcher ArsLogica S.r.l. IT Laboratories Business Innovation Centre Unit 6 - 1st floor BIC, Via Trento, 117 38017 Mezzolombardo (TN), Italy Email: [EMAIL PROTECTED] Skype: fabrizio.stefani Phone: +39 0461 600253 Fax: +39 0461 603250 Web Site: www.arslogica.it _ This email has been ClamScanned ! www.clamav.net _ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Re: hardware
As far as I know there are also: www.maxfor.co.kr (telosb clones) www.cratlon.com (telos clones without TinyOS) www.sensinode.com (cc2430 based, no TinyOS) www.intel.com/research/exploratory/motes.htm Fabrizio Tony Mancill wrote: Ted Carter wrote: Ken Peirce yahoo.com> writes: I am looking to get a couple of motes to use in real world testing of my code. I see that Crossbow sells them. However, they appear to have a licensed tool chain. I assume the tinyOS code and tool chain works just fine on them and that the licensed tool chain is something else. Does anyone else make mote hardware?Cheers,Ken [garage research disclaimer] www.xbow.com www.moteiv.com www.jennic.org www.millennialnet.com www.shockfish.com www.meshnetics.com www.btnode.ethz.ch www.dustnetworks.com www.ember.com No assumptions on toolchains. If price point is a concern, thus far I've found that xbow wins on pricing. Xbow sells their TelosB mote w/sensor suite for 130USD. No relation, no endorsement, just one more to add to the list: www.cirronet.com They have a model with a +18dBm transmitter if you need that kind of transmit power. However, the toolchain appears to be closed. tony ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ This email has been ClamScanned by ArsLogica antivirus server ! www.clamav.net ___ _ This email has been ClamScanned ! www.clamav.net _ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Tuning the radio Ouput power
Use the CC2420RadioC component and connect it to your application (say myApp): myAppM.CC2420Control -> CC2420RadioC.CC2420Control; and then, in your myAppM.nc use call CC2420Control.SetRFPower(val); // set TX power where val = 1..31 (-25 dBm to 0 dBm) Done. Fabrizio Romain Thouvenin wrote: Hello, I'd like to modify the radio output power of my telosb motes (cc2420 chip). According to the telosb manual, this can be done by setting the TXCRTL register with a value from 0xa0e3 to 0xa0ff. But the write() command of the CC2420Register interface takes a uint16_t value... how can I know and choose the 16-bit word to set ? Thanks for your help, Romain _ This email has been ClamScanned ! www.clamav.net _ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Tuning the radio Ouput power
Romain Thouvenin wrote:
Thanks for the reply, but isn't that for TinyOS 1.x only ?
I am using TinyOS 2 (true, I didn't say that at first) and didn't find
any CC2420Control interface in the nesdoc nor in my files.
Yes, I was talking about TinyOS 1.x.
I don't know for T2, sorry.
(I know, I know, I have to switch to T2, ...sooner or later...)
There is a CC2420Power interface, and its documentation says "see
CC2420Config" for controlling the transmit power. But CC2420Config
doesn't mention that... is it the get and setChannel commands ?
I don't think so, (at least in T1) the setChannel is to choose the
channel, not the power.
Also, I've found a CC2420Packet.setPower(message_t *, uint8_t), but it
only applies to one packet.
Changing power for each packet?
Interesting... streams... power modulation depending on data value...
low-power audio/video tx...
Stop! wake up!
Sorry, just playing with some ideas...
And what about setting the value once?
I don't think that it is resetted after each packet transmission.
Fabrizio
Romain
On 4/18/07, Fabrizio Stefani <[EMAIL PROTECTED]> wrote:
Use the CC2420RadioC component and connect it to your application (say
myApp):
myAppM.CC2420Control -> CC2420RadioC.CC2420Control;
and then, in your myAppM.nc use
call CC2420Control.SetRFPower(val); // set TX power
where val = 1..31 (-25 dBm to 0 dBm)
Done.
Fabrizio
Romain Thouvenin wrote:
> Hello,
>
> I'd like to modify the radio output power of my telosb motes (cc2420
> chip). According to the telosb manual, this can be done by setting the
> TXCRTL register with a value from 0xa0e3 to 0xa0ff.
>
> But the write() command of the CC2420Register interface takes a
> uint16_t value... how can I know and choose the 16-bit word to set ?
>
> Thanks for your help,
>
> Romain
_
This email has been ClamScanned !
www.clamav.net
_
___
This email has been ClamScanned by ArsLogica antivirus server !
www.clamav.net
___
--
Fabrizio Stefani, Ph.D.
Researcher
ArsLogica S.r.l.
IT Laboratories
Business Innovation Centre
Unit 6 - 1st floor
BIC, Via Trento, 117
38017 Mezzolombardo
(TN), Italy
Email: [EMAIL PROTECTED]
Skype: fabrizio.stefani
Phone: +39 0461 600253
Fax: +39 0461 603250
Web Site: www.arslogica.it
_
This email has been ClamScanned !
www.clamav.net
_
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Problems with javacomm
Hi all, I'm using Ubuntu 6.06, TinyOS 1.1, Java 1.5.0_06, JavaComm 3.0, GCC 4.0.3, Tmote tools 2.0.2. To install all I followed this guides: http://www.chadmetcalf.com/tinyos-1x-on-ubuntu/ http://www.moteiv.com/community/Tmote_Linux_install I can program the tmotes, but I'm having some problems with the javacomm because trying to test the Oscilloscope application the program gives me an error and stops. $ motelist Reference Device Description -- --- M4A9N70Z /dev/ttyUSB0 Moteiv tmote sky $ export MOTECOM=serial@/dev/ttyUSB0:tmote $ java net.tinyos.tools.Listen Error on serial@/dev/ttyUSB0:57600: java.io.IOException: Couldn't configure /dev/ttyUSB0 If I try to use some other java applications for testing the serial port, such as BlackBox, it seems to work. $ export CLASSPATH BlackBox.jar:$CLASSPATH $ java BlackBox -p /dev/ttyUSB0 Opening port /dev/ttyUSB0 /dev/ttyUSB0: PORT_OWNED [by this application] and the GUI opens giving me informations on that port. So what's happening with the serial connection with the tmote? Can you help me? Thanks, Fabrizio _ This email has been ClamScanned ! www.clamav.net _ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Problems with javacomm
Claro Noda wrote: Frabrizio: did you sorted out the FTDI drivers correctly? remember there is a serial<->USB interface on the Tmote. the drivers are probably part of the kernel and the motelist output make me guess you did. FTDI drivers are in the kernel, no problems with them. but, besides, the javacomm, in linux uses the RXTX. You might be willing to check: http://wass.homelinux.net/howtos/Comm_How-To.shtml I'm not sure if this applies to the Tmote, though. There is no reference to it in: http://www.moteiv.com/community/Tmote_Linux_install Maybe somebody else in the list can advise. we are entertaining the idea of moving to ubuntu, so i might keep an eye on this thread :) Yesterday two coworkers of mine made the same installation and javacomm works OK for them. They have not installed the RXTX things. I'll try to compare their system configuration with mine... On 02/08/06, *Fabrizio Stefani* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: Hi all, I'm using Ubuntu 6.06, TinyOS 1.1, Java 1.5.0_06, JavaComm 3.0, GCC 4.0.3, Tmote tools 2.0.2. To install all I followed this guides: http://www.chadmetcalf.com/tinyos-1x-on-ubuntu/ http://www.moteiv.com/community/Tmote_Linux_install I can program the tmotes, but I'm having some problems with the javacomm because trying to test the Oscilloscope application the program gives me an error and stops. $ motelist Reference Device Description -- --- M4A9N70Z /dev/ttyUSB0 Moteiv tmote sky $ export MOTECOM=serial@/dev/ttyUSB0:tmote $ java net.tinyos.tools.Listen Error on serial@/dev/ttyUSB0:57600: java.io.IOException: Couldn't configure /dev/ttyUSB0 If I try to use some other java applications for testing the serial port, such as BlackBox, it seems to work. $ export CLASSPATH BlackBox.jar:$CLASSPATH $ java BlackBox -p /dev/ttyUSB0 Opening port /dev/ttyUSB0 /dev/ttyUSB0: PORT_OWNED [by this application] and the GUI opens giving me informations on that port. So what's happening with the serial connection with the tmote? Can you help me? _ This email has been ClamScanned ! www.clamav.net _ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Problems with javacomm
Anton Riedl wrote: I'm not quite sure if it's the same for Tmotes, but for micaz I use /dev/ttyUSB0 for programming and /dev/ttyUSB1 for communication (on Ubuntu with TinyOS 2.x, though). Anton $ export MOTECOM=serial@/dev/ttyUSB0:tmote $ java net.tinyos.tools.Listen Error on serial@/dev/ttyUSB0:57600: java.io.IOException: Couldn't configure /dev/ttyUSB0 $ export MOTECOM=serial@/dev/ttyUSB1:tmote $ java net.tinyos.tools.Listen Error on serial@/dev/ttyUSB1:57600: java.io.IOException: Invalid port. Known serial ports: - /dev/ttyS0 - /dev/ttyS1 - /dev/ttyUSB0 So the ttyUSB0 is the correct port. But, for some reason, java cannot configure it. You know of any other kind of tests I can do to the serial port to diagnose the problem? Thanks, Fabrizio On Aug 2, 2006, at 1:40 PM, Claro Noda wrote: Frabrizio: did you sorted out the FTDI drivers correctly? remember there is a serial<->USB interface on the Tmote. the drivers are probably part of the kernel and the motelist output make me guess you did. but, besides, the javacomm, in linux uses the RXTX. You might be willing to check: http://wass.homelinux.net/howtos/Comm_How-To.shtml I'm not sure if this applies to the Tmote, though. There is no reference to it in: http://www.moteiv.com/community/Tmote_Linux_install Maybe somebody else in the list can advise. we are entertaining the idea of moving to ubuntu, so i might keep an eye on this thread :) Claro. On 02/08/06, *Fabrizio Stefani* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: Hi all, I'm using Ubuntu 6.06, TinyOS 1.1, Java 1.5.0_06, JavaComm 3.0, GCC 4.0.3, Tmote tools 2.0.2. To install all I followed this guides: http://www.chadmetcalf.com/tinyos-1x-on-ubuntu/ http://www.moteiv.com/community/Tmote_Linux_install I can program the tmotes, but I'm having some problems with the javacomm because trying to test the Oscilloscope application the program gives me an error and stops. $ motelist Reference Device Description -- --- M4A9N70Z /dev/ttyUSB0 Moteiv tmote sky $ export MOTECOM=serial@/dev/ttyUSB0:tmote $ java net.tinyos.tools.Listen Error on serial@/dev/ttyUSB0:57600: java.io.IOException: Couldn't configure /dev/ttyUSB0 If I try to use some other java applications for testing the serial port, such as BlackBox, it seems to work. $ export CLASSPATH BlackBox.jar:$CLASSPATH $ java BlackBox -p /dev/ttyUSB0 Opening port /dev/ttyUSB0 /dev/ttyUSB0: PORT_OWNED [by this application] and the GUI opens giving me informations on that port. So what's happening with the serial connection with the tmote? Can you help me? ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU <mailto:Tinyos-help@Millennium.Berkeley.EDU> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help --- ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help _ This email has been ClamScanned ! www.clamav.net _ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] motelist
Sudha Krishna wrote: Hi, I am getting the following error when I execute the "motelist" command: error, could not open key HKLM\SYSTEM\CurrentControlSet\Enum\FTDIBUS I suppose that you are working with telosb/tmotes. On the tmotes there is an FTDI's FT232BM USB to Serial converter. It enables to program the tmote using a PC USB port as an additional - virtual - COM port (VCP). The drivers for the FT232BM are included in Linux kernel 2.4.20 or greater. Check for a file named ftdi_sio.o (probably under /lib/modules/2.6./kernel/drivers/usb/serial). Plug in a tmote and check to see if the right driver was loaded: $ lsmod | grep ftdi You should see something like: usbserial 33224 1 ftdi_sio usbhid 42752 0 usbcore 139076 6 ftdi_sio,usbserial,usbhid,ehci_hcd,uhci_hcd If the ftdi_sio driver is not loaded when inserting a tmote, you need to update your kernel. *Or* you can download the drivers from the FTDI web site http://www.ftdichip.com/Drivers/VCP.htm. Then, to install the ftdi_sio driver use the following steps: 1. Create a temporary folder in your linux machine. $ cd $HOME $ mkdir tmpftdi $ cd tmpftdi $ wget http://www.ftdichip.com/Drivers/VCP/Linux/ftdi_sio.tar.gz 2. Extract the files from ftdi_sio.tar.gz file to your temporary folder $ gunzip ftdi_sio.tar.gz $ tar -xvf ftdi_sio.tar 3. Build the driver $ make 4. Plug in your ftdi device 5. Check to see if default driver was loaded $ lsmod you will see ftdi_sio if a driver is loaded 6. Remove the default installed driver $ sudo rmmod ftdi_sio 7. Install the newly built driver $ sudo insmod ftdi_sio.o Note that I have not tested this steps because on my system (Ubuntu 6.06) the VCP worked out of the box. Hope this helps, Fabrizio _ This email has been ClamScanned ! www.clamav.net _ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] motelist
Just now I note that you are working under Windows. Then my previous reply is not useful for you. You should install the VCP drivers form the FTDI web site. Fabrizio Fabrizio Stefani wrote: Sudha Krishna wrote: Hi, I am getting the following error when I execute the "motelist" command: error, could not open key HKLM\SYSTEM\CurrentControlSet\Enum\FTDIBUS I suppose that you are working with telosb/tmotes. On the tmotes there is an FTDI's FT232BM USB to Serial converter. It enables to program the tmote using a PC USB port as an additional - virtual - COM port (VCP). The drivers for the FT232BM are included in Linux kernel 2.4.20 or greater. Check for a file named ftdi_sio.o (probably under /lib/modules/2.6./kernel/drivers/usb/serial). Plug in a tmote and check to see if the right driver was loaded: $ lsmod | grep ftdi You should see something like: usbserial 33224 1 ftdi_sio usbhid 42752 0 usbcore 139076 6 ftdi_sio,usbserial,usbhid,ehci_hcd,uhci_hcd If the ftdi_sio driver is not loaded when inserting a tmote, you need to update your kernel. *Or* you can download the drivers from the FTDI web site http://www.ftdichip.com/Drivers/VCP.htm. Then, to install the ftdi_sio driver use the following steps: 1. Create a temporary folder in your linux machine. $ cd $HOME $ mkdir tmpftdi $ cd tmpftdi $ wget http://www.ftdichip.com/Drivers/VCP/Linux/ftdi_sio.tar.gz 2. Extract the files from ftdi_sio.tar.gz file to your temporary folder $ gunzip ftdi_sio.tar.gz $ tar -xvf ftdi_sio.tar 3. Build the driver $ make 4. Plug in your ftdi device 5. Check to see if default driver was loaded $ lsmod you will see ftdi_sio if a driver is loaded 6. Remove the default installed driver $ sudo rmmod ftdi_sio 7. Install the newly built driver $ sudo insmod ftdi_sio.o Note that I have not tested this steps because on my system (Ubuntu 6.06) the VCP worked out of the box. Hope this helps, Fabrizio _ This email has been ClamScanned ! www.clamav.net _ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ This email has been ClamScanned by ArsLogica antivirus server ! www.clamav.net ___ -- Dr. Fabrizio Stefani Researcher ArsLogica S.r.l. IT Laboratories Business Innovation Centre Via Trento, 117 38017 Mezzolombardo (Trento), Italy Email: [EMAIL PROTECTED] Phone: +39 0461 600253 Fax: +39 0461 603250 Web Site: www.arslogica.it _ This email has been ClamScanned ! www.clamav.net _ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Problems with javacomm
OK, I solved reinstalling java as explained in https://jdk-distros.dev.java.net/ubuntu-dev.html and then repeating the steps "Compile Java Tools", "TOSCOmm" and "JNI" in http://www.chadmetcalf.com/tinyos-1x-on-ubuntu/ Now java programs work properly with a tmote attached to the /dev/ttysUSB0 virtual com port. Fabrizio Fabrizio Stefani wrote: Hi all, I'm using Ubuntu 6.06, TinyOS 1.1, Java 1.5.0_06, JavaComm 3.0, GCC 4.0.3, Tmote tools 2.0.2. To install all I followed this guides: http://www.chadmetcalf.com/tinyos-1x-on-ubuntu/ http://www.moteiv.com/community/Tmote_Linux_install I can program the tmotes, but I'm having some problems with the javacomm because trying to test the Oscilloscope application the program gives me an error and stops. $ motelist Reference Device Description -- --- M4A9N70Z /dev/ttyUSB0 Moteiv tmote sky $ export MOTECOM=serial@/dev/ttyUSB0:tmote $ java net.tinyos.tools.Listen Error on serial@/dev/ttyUSB0:57600: java.io.IOException: Couldn't configure /dev/ttyUSB0 If I try to use some other java applications for testing the serial port, such as BlackBox, it seems to work. $ export CLASSPATH BlackBox.jar:$CLASSPATH $ java BlackBox -p /dev/ttyUSB0 Opening port /dev/ttyUSB0 /dev/ttyUSB0: PORT_OWNED [by this application] and the GUI opens giving me informations on that port. So what's happening with the serial connection with the tmote? Can you help me? Thanks, Fabrizio _ This email has been ClamScanned ! www.clamav.net _ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ This email has been ClamScanned by ArsLogica antivirus server ! www.clamav.net _______ -- Fabrizio Stefani, Ph.D. Researcher ArsLogica S.r.l. IT Laboratories Business Innovation Centre Unit 6 - 1st floor BIC, Via Trento, 117 38017 Mezzolombardo (TN), Italy Email: [EMAIL PROTECTED] Skype: fabrizio.stefani Phone: +39 0461 600253 Fax: +39 0461 603250 Web Site: www.arslogica.it _ This email has been ClamScanned ! www.clamav.net _ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
