Send USRP-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of USRP-users digest..."
Today's Topics:
1. Send command to USRP internal GPSDO (Damien Serant)
2. Re: Send command to USRP internal GPSDO (Josh Blum)
3. Re: Send command to USRP internal GPSDO (Damien Serant)
4. Re: Send command to USRP internal GPSDO (Josh Blum)
5. GUI to communicate remotely with USRPE110
(Julio Hector Aguilar Renteria)
6. is there any daughterboard which has two TX ports? (gang li)
7. Re: is there any daughterboard which has two TX ports?
(Matt Ettus)
----------------------------------------------------------------------
Message: 1
Date: Fri, 29 Mar 2013 00:34:02 +0100
From: Damien Serant <[email protected]>
To: USRP List <[email protected]>
Subject: [USRP-users] Send command to USRP internal GPSDO
Message-ID:
<CAM=tNLkCLSPptemqdRCkzwWqU=evnpcwauwjq8c9vd+ufqn...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi list,
I'm trying to send commands to the Firefly GPSDO through the Ethernet
connection. From that i learnt in uhd source code, the uart communication
to the firefly is pass through the UDP port 49172.
Two questions:
- This port is used for both sending command and receiving answer ? If not
what is the other port ?
- For simplicity i tried to find a MS Windows terminal that could send
uart command through UDP, without success. Do you know such a software ?
The simplest solution that i found right now is to use 3 softwares :
CommTunnel to redirect UDP to a virtual COM created with VSPE, and TeraTerm
to read/write on this virtual COM.
Thanks,
Damien
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20130329/e186bd90/attachment-0001.html>
------------------------------
Message: 2
Date: Thu, 28 Mar 2013 18:38:53 -0500
From: Josh Blum <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] Send command to USRP internal GPSDO
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 03/28/2013 06:34 PM, Damien Serant wrote:
> Hi list,
>
> I'm trying to send commands to the Firefly GPSDO through the Ethernet
> connection. From that i learnt in uhd source code, the uart communication
> to the firefly is pass through the UDP port 49172.
> Two questions:
> - This port is used for both sending command and receiving answer ? If not
> what is the other port ?
The GPSDO will reply to the last socket it communicated with. Make a
normal connected udp socket and initiate a communication, it should send
back to you.
> - For simplicity i tried to find a MS Windows terminal that could send
> uart command through UDP, without success. Do you know such a software ?
> The simplest solution that i found right now is to use 3 softwares :
> CommTunnel to redirect UDP to a virtual COM created with VSPE, and TeraTerm
> to read/write on this virtual COM.
>
I dont know of any software. I recommend just making a udp socket in
python. Try sending "Something\r\n" and see whats comes on the recv end
of the socket.
-josh
> Thanks,
>
> Damien
>
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
------------------------------
Message: 3
Date: Fri, 29 Mar 2013 01:01:56 +0100
From: Damien Serant <[email protected]>
To: [email protected]
Cc: USRP List <[email protected]>
Subject: Re: [USRP-users] Send command to USRP internal GPSDO
Message-ID:
<CAM=tnln67zobuku0uo_sn38yfqtticzfmedtyiepkkodpbq...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Thanks for the very quick answer !
When you say " I recommend just making a udp socket in python. Try sending
"Something\r\n" and see whats comes on the recv end of the socket. " you
mean that i can directly send command strings through UDP without applying
an UART formatting ? So the firmware make the UART translation ? My
question sounds may be stupid, but i was thinking this because of the
make_uart method of the udp_simple class that is call when the udp socket
of the GPSDO is created (cf uhd source code).
If it is just sending strings through UDP a simple terminal will be OK. I'm
not against using python but i don't know this language (i'm using c++ to
develop with UHD)
2013/3/29 Josh Blum <[email protected]>
>
>
> On 03/28/2013 06:34 PM, Damien Serant wrote:
> > Hi list,
> >
> > I'm trying to send commands to the Firefly GPSDO through the Ethernet
> > connection. From that i learnt in uhd source code, the uart communication
> > to the firefly is pass through the UDP port 49172.
> > Two questions:
> > - This port is used for both sending command and receiving answer ? If
> not
> > what is the other port ?
>
> The GPSDO will reply to the last socket it communicated with. Make a
> normal connected udp socket and initiate a communication, it should send
> back to you.
>
>
> > - For simplicity i tried to find a MS Windows terminal that could send
> > uart command through UDP, without success. Do you know such a software ?
> > The simplest solution that i found right now is to use 3 softwares :
> > CommTunnel to redirect UDP to a virtual COM created with VSPE, and
> TeraTerm
> > to read/write on this virtual COM.
> >
>
> I dont know of any software. I recommend just making a udp socket in
> python. Try sending "Something\r\n" and see whats comes on the recv end
> of the socket.
>
> -josh
>
> > Thanks,
> >
> > Damien
> >
> >
> >
> > _______________________________________________
> > USRP-users mailing list
> > [email protected]
> > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
> >
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20130329/d7006436/attachment-0001.html>
------------------------------
Message: 4
Date: Thu, 28 Mar 2013 19:12:59 -0500
From: Josh Blum <[email protected]>
To: Damien Serant <[email protected]>
Cc: USRP List <[email protected]>
Subject: Re: [USRP-users] Send command to USRP internal GPSDO
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 03/28/2013 07:01 PM, Damien Serant wrote:
> Thanks for the very quick answer !
> When you say " I recommend just making a udp socket in python. Try sending
> "Something\r\n" and see whats comes on the recv end of the socket. " you
> mean that i can directly send command strings through UDP without applying
> an UART formatting ? So the firmware make the UART translation ? My
> question sounds may be stupid, but i was thinking this because of the
> make_uart method of the udp_simple class that is call when the udp socket
> of the GPSDO is created (cf uhd source code).
Yea, sorry. The soft CPU in the FPGA is acting as a bridge between the
GPSDO's uart and a UDP socket, so you can basically interact with it
directly. Bytes on the socket == bytes to the uart.
> If it is just sending strings through UDP a simple terminal will be OK. I'm
> not against using python but i don't know this language (i'm using c++ to
> develop with UHD)
You can actually use the same utilities that UHD is using internally to
do the access. See the make_uart
https://github.com/EttusResearch/uhd/blob/master/host/include/uhd/transport/udp_simple.hpp#L65
-josh
>
>
> 2013/3/29 Josh Blum <[email protected]>
>
>>
>>
>> On 03/28/2013 06:34 PM, Damien Serant wrote:
>>> Hi list,
>>>
>>> I'm trying to send commands to the Firefly GPSDO through the Ethernet
>>> connection. From that i learnt in uhd source code, the uart communication
>>> to the firefly is pass through the UDP port 49172.
>>> Two questions:
>>> - This port is used for both sending command and receiving answer ? If
>> not
>>> what is the other port ?
>>
>> The GPSDO will reply to the last socket it communicated with. Make a
>> normal connected udp socket and initiate a communication, it should send
>> back to you.
>>
>>
>>> - For simplicity i tried to find a MS Windows terminal that could send
>>> uart command through UDP, without success. Do you know such a software ?
>>> The simplest solution that i found right now is to use 3 softwares :
>>> CommTunnel to redirect UDP to a virtual COM created with VSPE, and
>> TeraTerm
>>> to read/write on this virtual COM.
>>>
>>
>> I dont know of any software. I recommend just making a udp socket in
>> python. Try sending "Something\r\n" and see whats comes on the recv end
>> of the socket.
>>
>> -josh
>>
>>> Thanks,
>>>
>>> Damien
>>>
>>>
>>>
>>> _______________________________________________
>>> USRP-users mailing list
>>> [email protected]
>>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>>
>>
>> _______________________________________________
>> USRP-users mailing list
>> [email protected]
>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>
>
------------------------------
Message: 5
Date: Thu, 28 Mar 2013 20:24:05 -0500
From: Julio Hector Aguilar Renteria <[email protected]>
To: [email protected], [email protected]
Subject: [USRP-users] GUI to communicate remotely with USRPE110
Message-ID:
<cacbki8fziwd0bdq1vehdbujjyiffv5ozjnrb66kn++uyiuu...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Cordial Saludo
Hello, I'm working on a GUI to communicate remotely with USRPE110, there
are other alternatives to XMLRPC, which is the best option?
Muchas Gracias
Atentamente,
*Julio Hector Aguilar Renteria
*Celular: 315 331 7344
Skype: jharvao
MSN: [email protected]
Cali - Colombia
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20130328/7880f8cc/attachment-0001.html>
------------------------------
Message: 6
Date: Fri, 29 Mar 2013 11:54:37 -0400
From: gang li <[email protected]>
To: [email protected]
Subject: [USRP-users] is there any daughterboard which has two TX
ports?
Message-ID:
<CAKro2L2DUt=6cexm_rhsh+uuezdtheazjht3hq+cfeyigik...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hi, all,
I am wondering whether there are any daughterboards with more than one
TX ports which can transmit simultaneously? Or i have to install two
daughterboards to get two TX ports on one USRP? Which is feasible?
Thanks.
Best,
Gang
------------------------------
Message: 7
Date: Fri, 29 Mar 2013 08:59:09 -0700
From: Matt Ettus <[email protected]>
To: gang li <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] is there any daughterboard which has two TX
ports?
Message-ID:
<CAN=1kn_i4akyb90o-oax3shsmgwec2hogrknuh9dsq_vfxq...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Only the LFTX and BasicTX have two transmit ports.
Matt
On Fri, Mar 29, 2013 at 8:54 AM, gang li <[email protected]> wrote:
> Hi, all,
>
> I am wondering whether there are any daughterboards with more than one
> TX ports which can transmit simultaneously? Or i have to install two
> daughterboards to get two TX ports on one USRP? Which is feasible?
> Thanks.
>
> Best,
> Gang
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20130329/47bcf535/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
------------------------------
End of USRP-users Digest, Vol 31, Issue 28
******************************************
