Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default write buffer size can break communication with Roach2 boards. #74

Open
baileyji opened this issue Jul 25, 2018 · 0 comments
Open

Comments

@baileyji
Copy link

Hi Folks,
We've found that to get casperfpga working with our roach2 based system we need to add the additional patch of:

if hasattr(katcp.CallbackClient, 'MAX_WRITE_BUFFER_SIZE'):
    setattr(katcp.CallbackClient, 'MAX_WRITE_BUFFER_SIZE',
            katcp.CallbackClient.MAX_WRITE_BUFFER_SIZE * 10)

in katcp_fpga.py (v0.4.2) or probably in transport_katcp.py for v3.1 (untested). We aren't keen on this because it means forking and diving into internals.

Is there an undocumented way of perhaps calling casperfpga.katcp_fpga.KatcpFpga with a MAX_MESSAGE_LEN argument or some such so we can both avoid the write buffer overflow and mucking around with or forking the repo?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant