Hi Jason
Looks like a nice app.
Gerry
On 8/29/2012 8:32 AM, Jason Castro wrote:
This may be helpful to someone. I've written a LabVIEW KATCP -
interface. I attached a screen shot. Like everything, it's a work in
progress, but it has a lot of basic functionality that I find useful.
You can can load a .bof file from a list of all .bof files on a ROACH,
you can delete.bof files, check the clock rate, send any command with
parameters that is listed in the "help" command. Feel free to
contact me with any questions. The source files, a windows installer
and the LabVIEW executable can be downloaded here:
ftp://ftp.cv.nrao.edu/NRAO-staff/jcastro/CASPER/LabVIEW/
Thanks,
Jason Castro
NRAO
On 8/29/2012 5:47 AM, [email protected] wrote:
Send casper mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://calmail.berkeley.edu/manage/list/listinfo/[email protected]
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 casper digest..."
Today's Topics:
1. Re: ROACH memory-mapped IO (Jason Manley)
2. Re: ROACH memory-mapped IO (Tom Kuiper)
3. ROACH 2 Mechanical Drawing and CAD (Vaughan Moss)
4. Re: ROACH memory-mapped IO (Jason Manley)
5. Re: ROACH memory-mapped IO (Tom Kuiper)
6. Re: ROACH memory-mapped IO (Jason Manley)
----------------------------------------------------------------------
Message: 1
Date: Wed, 29 Aug 2012 10:09:44 +0200
From: Jason Manley<[email protected]>
Subject: Re: [casper] ROACH memory-mapped IO
To: Adam Barta<[email protected]>
Cc: LIST CASPER<[email protected]>
Message-ID:<[email protected]>
Content-Type: text/plain; charset=us-ascii
On 29 Aug 2012, at 02:44, Adam Barta wrote:
You could also try an ssh port forward to the katcp port ssh -vNL
7147:roach:7147 gateway
Then use the katcp interface to read / write the registers. There is
a katcp_wrapper.py in the corr library
I would like to re-inforce this suggestion if you need SSH tunnelling
through a firewall. A general word of warning to the CASPER
community, which we also explained at the recent workshop...
MeerKAT will not be supporting filesystem-level access in future
boards (quite possibly starting with ROACH-2 already) and so, unless
someone else in the collaboration picks it up, you'll be on your own
if you write custom software to run on the PPC/BORPH because new
platforms might not even run BORPH at all. There are a number of
reasons for this decision, one being that we've run into performance
limitations with BORPH, but also that it's a big overhead to port and
debug and to keep it running reliably.
The only interface supported by SKA-SA will be through KATCP. So if
you start using the KATCP interface now, you'll have a transparent
upgrade path to future boards. I'd suggest you don't worry yourself
too much with the low-level detail... this is part of what CASPER
tries to abstract away to ease your life as an instrument designer.
If you don't want to write your own KATCP interface (and who does?!),
consider using one of the existing ones. The best developed ones are
in c (which includes a command-line executable for a single-line,
ipython-like interactive experience from the shell prompt if you just
want to call a shell script with a bunch of commands), available at
https://github.com/ska-sa/katcp_devel, or a number of CASPER
collaborators are using the python wrapper from corr if you want to
build a higher-level GUI application. You can find a one-page getting
started guide here: https://casper.berkeley.edu/wiki/Corr
Jason
------------------------------
Message: 2
Date: Wed, 29 Aug 2012 02:19:07 -0700
From: Tom Kuiper<[email protected]>
Subject: Re: [casper] ROACH memory-mapped IO
To: Jason Manley<[email protected]>
Cc: LIST CASPER<[email protected]>
Message-ID:<[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Thanks for that, Jason! It is very timely. The reason I went down this
path is because I have a spectrometer design, by Joseph Trinh, which
takes a slightly different approach to bram access and so I could not
use the katcp_wrapper which I'd been using with your 16K spectrometer.
He'd offered to modify it but I thought it cool to try the file access
I/O. I think as a result of this exchange, I'll ask Joseph to modify
his design and I'll start using pyro.
I hope he can squeeze it into a ROACH-1. He's got a 2x1024 spectrometer
design for me now but had to drop the PFBs because of insufficient
resources. I'm asking him to try 2x512 with PFBs. Does anyone already
have something like that?
Next time around we'll use ROACH-2 but at the time we placed the orders
we weren't sure that the support for that would evolve fast enough to
meet our deadline (next month).
Cheers
Tom
On 08/29/2012 01:09 AM, Jason Manley wrote:
On 29 Aug 2012, at 02:44, Adam Barta wrote:
You could also try an ssh port forward to the katcp port ssh -vNL
7147:roach:7147 gateway
Then use the katcp interface to read / write the registers. There
is a katcp_wrapper.py in the corr library
I would like to re-inforce this suggestion if you need SSH
tunnelling through a firewall. A general word of warning to the
CASPER community, which we also explained at the recent workshop...
MeerKAT will not be supporting filesystem-level access in future
boards (quite possibly starting with ROACH-2 already) and so, unless
someone else in the collaboration picks it up, you'll be on your own
if you write custom software to run on the PPC/BORPH because new
platforms might not even run BORPH at all. There are a number of
reasons for this decision, one being that we've run into performance
limitations with BORPH, but also that it's a big overhead to port
and debug and to keep it running reliably.
The only interface supported by SKA-SA will be through KATCP. So if
you start using the KATCP interface now, you'll have a transparent
upgrade path to future boards. I'd suggest you don't worry yourself
too much with the low-level detail... this is part of what CASPER
tries to abstract away to ease your life as an instrument designer.
If you don't want to write your own KATCP interface (and who
does?!), consider using one of the existing ones. The best developed
ones are in c (which includes a command-line executable for a
single-line, ipython-like interactive experience from the shell
prompt if you just want to call a shell script with a bunch of
commands), available at https://github.com/ska-sa/katcp_devel, or a
number of CASPER collaborators are using the python wrapper from
corr if you want to build a higher-level GUI application. You can
find a one-page getting started guide here:
https://casper.berkeley.edu/wiki/Corr
Jason
--
----------------------
Gerald R. Harp, Ph.D.
Director, Center for SETI Research
SETI Institute
