Hi, Jeff,
No clues yet. How about if you telnet from the non-working computer to the
ROACH2 using port 7147:
telent 10.0.0.200 7147
Does it connect and stay connected? If it stays connected, does it return a
bunch of help text when you enter this command:
?help
If that all works over
Hi David,
Direct telnet works fine, and I get this message on telnet terminal when I try
the python katcp connect:
#log info 946685931331 raw new\_client\_connection\_10.0.0.11:44001
#client-connected 10.0.0.11:44001
#client-disconnected 10.0.0.11:44001
I did make sure the version is the same.
I understand you are running the same Python/KATCP version, but are you also
running the same Python version on both a working and the non-working machines?
Are you running the same Linux distro on both a working and the non-working
machines?
Dave
On May 21, 2013, at 2:01 PM, Haoxuan Zheng
On Tue, May 21, 2013 at 1:36 PM, Haoxuan Zheng jef...@mit.edu wrote:
Hi David,
I tried everything you suggested, and here's what I got:
1) I don't see any new messages with dmesg on ROACH2 after the attempted
connection; maybe I did something wrong? I have never used dmesg before.
2) I
The working one has lots of interleaved connections. Can you make
sure that everything using katcp is off, then start capturing, then
start katcp again.
--Andy
On Tue, May 21, 2013 at 2:41 PM, Haoxuan Zheng jef...@mit.edu wrote:
Hi Andy,
Here are the wireshark files from the working computer
Hi Andy,
Here are the tidied up versions.
Thank you so much!
Jeff
From: aml...@gmail.com [aml...@gmail.com] on behalf of Andrew Lutomirski
[l...@mit.edu]
Sent: Tuesday, May 21, 2013 5:54 PM
To: Haoxuan Zheng
Cc: David MacMahon; casper@lists.berkeley.edu
Problem (semi) solved:
As David suggested, it is a version difference. I originally checked my version
for corr, but not for katcp. It turns out that katcp 0.5.2 won't work with our
ROACH2, but going back to katcp 0.3.4 worked. I say it's semi solved because I
don't know how to fix the problem
7 matches
Mail list logo