Hi CASPER,
Sorry for the spam, but since my original message was sent at the worst hour of
the week (Friday evening), I would like to give it another try:
Our lab just got a new server which will be our data taking computer, and it
has trouble connecting to our ROACH 2 through python katcp.
Hi, Jeff,
That sounds like a weird one! Here are some ideas to try:
1) Check the output of dmesg on the roach2 after the problem occurs.
2) Watch the network traffic between the problematic machine and the roach2
using tcpdump or wireshark.
3) Verify that the problematic computer is using
Hey Katty,
This error is telling you that there is no register in your model with name
cnt_rst. There still may be a register that serves the same purpose, but
simply goes by different spelling.
If you produced this bof file from a Simulink model, you can look in the
model to find the correct
Hey Katty, Laura
If you produced this bof file from a Simulink model, you can look in the
model to find the correct register.
Alternatively, you can log into your roach and run your .bof file as an
executable. When you see the process id, you can actually navigate to a
folder that will
Hi, Katty,
As you discovered the hard way, the python script and bof file that you
attached are not compatible with each other. Where did you get this tutorial?
Thanks,
Dave
On May 20, 2013, at 9:47 AM, katherine viviana cortes urbina wrote:
Hi all,
I am sorry but still I can not solve
Hi, Ryan,
Everything seems OK. Were you root or a member of the dialout group when you
tried connecting? I use screen instead of minicom, so I can't offer any extra
ideas regarding minicom itself.
FWIW, /dev/ttyUSB2 is the one that usually works for me.
Dave
On May 20, 2013, at 11:34 AM,
Hey David,
We noticed the dialout group thing, and have tested it with me being
both root (via sudo minicom USBTTY2) and dialout. Thanks!
--Ryan Monroe
626.773.0805
On 05/20/2013 11:46 AM, David MacMahon wrote:
Hi, Ryan,
Everything seems OK. Were you root or a member of the dialout group
Hi, Ryan,
Just for something else to try, this is the exact command that I use:
screen /dev/ttyUSB2 115200
When finished, I use cmdk to close the screen session (cmd is the screen
command character, which defaults to CTRL-A but I remap to CTRL-Z in my
.screenrc file).
Have you tried a known
Hi Ryan,
What machine you are using? FWIW, we had hard time time connecting from
RedHat, it just worked smoothly with Windows and Ubuntu.
Thanks,
Nimish
On Mon, May 20, 2013 at 2:56 PM, David MacMahon
dav...@astro.berkeley.eduwrote:
Hi, Ryan,
Just for something else to try, this is the
Hi Ryan,
What machine you are using? FWIW, we had hard time time connecting from
RedHat, it just worked smoothly with Windows and Ubuntu.
This reminded me that I that our sysadmin installed a udev rule for this
in my redhat 6 laptop:
Yes, Master1000 more /etc/udev/rules.d/99-ftdi.rules
We had problems even after installing the rule and still continue to have,
though we do not need to use RedHat to talk to Roaches now.
On Mon, May 20, 2013 at 3:29 PM, John Ford jf...@nrao.edu wrote:
Hi Ryan,
What machine you are using? FWIW, we had hard time time connecting from
RedHat,
11 matches
Mail list logo